15 Extending the Domain with Oracle WebCenter Portal
- Support for Dynamic Clusters in Oracle WebCenter Content
Oracle WebCenter Portal supports two different topologies: static clusters-based topology and dynamic clusters-based topology. When choosing the dynamic cluster topology, there are some differences with respect to the conventional static clusters configuration. - Variables Used When Extending the Domain for WebCenter Portal
As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section. - Installing the Software for an Enterprise Deployment
The procedure to install the software for an enterprise deployment is explained in this section. - Creating the Oracle WebCenter Portal Database Schemas
Before you can configure an Oracle WebCenter Portal domain, you must install the required schemas on a certified database for use with this release of Oracle Fusion Middleware. - Extending the Enterprise Deployment Domain with Oracle WebCenter Portal
- Propagating the Extended Domain to the Domain Directories and Machines
- Restoring customizations to setDomainEnv.sh after Unpacking the Domain
If any customizations have been made earlier to thesetDomainEnv.sh
files in ASERVER_HOME and MSERVER_HOME, then these customizations will need to be repeated after any domain extension. - Updating the NodeManager Configuration After Unpacking the Domain
When extending a domain, thenodemanager.properties
file in MSERVER_HOME may be overwritten with some values from thenodemanager.properties
file for ASERVER_HOME. Specifically, theListenAddress
and/orCustomIdentityAlias
values can be reset. - Restarting and Validating Pre-existing Managed Servers
- Modifying the Upload and Stage Directories to an Absolute Path in an Enterprise Deployment
After you configure the domain and unpack it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters. Also, update the upload directory for the AdminServer to have the same absolute path instead of relative, otherwise deployment issues can occur. If you implement dynamic clusters, the configuration of the server template assigned to each newly added cluster should be verified and updated, otherwise, verify and update every statically-defined Managed Server for the newly added clusters. - Configuring Listen Addresses When Using Dynamic Clusters
- Starting the Node Manager on WCPHOST1
After you unpack the extended domain on WCPHOST1, you can start the Node Manager from the Managed Server directory on WCPHOST1. - Starting the Node Manager on WCPHOST2
After you have propagated the domain configuration to WCPHOST2, you can start the Node Manager for the MSERVER_HOME domain directory. - Starting and Validating the WC_Portal1 and WC_Portlet1 Managed Servers
- Enabling SSL Communication Between the WebCenter Portal and Portlet Managed Servers and the Hardware Load Balancer
After you extend the domain with Oracle WebCenter Portal, ensure that the Administration Server and Managed Servers can access the front-end, SSL URL of the hardware load balancer. - Configuring Session Persistence for WebCenter Portal
Applications that are deployed to a cluster in WebLogic Server can optionally take advantage of HTTP session persistence and replication to provide high-availability for the user's experience (their session data) in case of the loss or outage of one or more application server instances within the cluster. This additional session state replication between server instances incurs a performance penalty for the application. - Configuring Analytics
- Confirming REST API Configuration
This section describes the procedure to configure REST APIs. - Configuring Oracle HTTP Server for the Extended Domain
The following sections describe how to configure the Oracle HTTP Server instances so they route requests for both public and internal URLs to the proper clusters in the enterprise topology. - Configuring WebCenter Portal for External Services
- Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
Parent topic: Configuring the Enterprise Deployment
Support for Dynamic Clusters in Oracle WebCenter Content
Oracle WebCenter Portal supports two different topologies: static clusters-based topology and dynamic clusters-based topology. When choosing the dynamic cluster topology, there are some differences with respect to the conventional static clusters configuration.
Static clusters, also called configured clusters, are conventional clusters where you manually configure and add each server instance. A dynamic cluster includes a new "server-template" object that is used to define a centralized configuration for all generated (dynamic) server instances. When you create a dynamic cluster, the dynamic servers are preconfigured and automatically generated for you. This feature enables you to scale up the number of server instances in the dynamic cluster when you need additional server capacity. You can simply start the dynamic servers without having to first manually configure and add them to the cluster.
-
The Configuration Wizard process may differ for each case. For example, you should define server templates for dynamic clusters instead of servers.
-
For dynamic clusters, you should perform the server-specific configurations such as setting the listen address, configuring the upload and staging directories, or configuring the keystores in the server template instead of in the server.
-
Service migration is configured in a different way for dynamic clusters. Dynamic clusters do not use migratable targets, instead the JMS resources are targeted to the cluster. Specific procedure for configuring service migration for dynamic clusters is included in this guide.
Mixed clusters (clusters that contains both dynamic and configured server instances) are not supported in the Oracle WebCenter Portal enterprise deployment.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Variables Used When Extending the Domain for WebCenter Portal
As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section.
The following directory variables, which are defined in File System and Directory Variables Used in This Guide.
-
ORACLE_HOME
-
ASERVER_HOME
-
APPLICATION_HOME
-
DEPLOY_HOME
-
WEB_CONFIG_DIR
-
JAVA_HOME
In addition, you'll be referencing the following virtual IP (VIP) addresses and host names defined in Physical and Virtual IP Addresses Required by the Enterprise Topology:
-
ADMINVHN
-
WCPHOST1
-
WCPHOST2
-
DBHOST1
-
DBHOST2
-
SCAN Address for the Oracle RAC Database (DB-SCAN.examle.com)
Parent topic: Extending the Domain with Oracle WebCenter Portal
Installing the Software for an Enterprise Deployment
The procedure to install the software for an enterprise deployment is explained in this section.
- Starting the Oracle WebCenter Portal Installer on WCCHOST1
- Navigating the Installation Screens
- Installing Oracle WebCenter Portal on WCCHOST2
Parent topic: Extending the Domain with Oracle WebCenter Portal
Starting the Oracle WebCenter Portal Installer on WCCHOST1
To start the installation program:
When the installation program appears, you are ready to begin the installation.
Parent topic: Installing the Software for an Enterprise Deployment
Navigating the Installation Screens
The installation program displays a series of screens, in the order listed in the following table.
If you need additional help with any of the installation screens, click the screen name.
Screen | Description |
---|---|
This screen introduces you to the product installer. |
|
Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization. |
|
Use this screen to specify the location of your Oracle home directory. For more information about Oracle Fusion Middleware directory structure, see Selecting Directories for Installation and Configuration in Planning an Installation of Oracle Fusion Middleware. |
|
Use this screen to select the type of installation and consequently, the products and feature sets you want to install. Select WebCenter Portal, then click Next. Notes:
|
|
This screen verifies that your system meets the minimum necessary requirements. If there are any warning or error messages, you can refer to one of the following documents in the Roadmap for Verifying Your System Environment section in Planning Your Oracle Fusion Middleware Infrastructure Installation. |
|
Use this screen to verify the installation options you selected. Click Install to begin the installation. |
|
This screen allows you to see the progress of the installation. Click Next when the progress bar reaches 100% complete. |
|
Review the information on this screen, then click Finish to dismiss the installer. |
Parent topic: Installing the Software for an Enterprise Deployment
Installing Oracle WebCenter Portal on WCCHOST2
If you have followed the EDG shared storage recommendations, there is a separate shared storage volume for product installations mounted on the *HOST2
hosts. You must also install the software on to the second products volume. It is recommended to execute the installs consistently from the WCCHOSTn
hosts. See Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
Parent topic: Installing the Software for an Enterprise Deployment
Creating the Oracle WebCenter Portal Database Schemas
Before you can configure an Oracle WebCenter Portal domain, you must install the required schemas on a certified database for use with this release of Oracle Fusion Middleware.
The following topics describe how to install the required schemas.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Starting the Repository Creation Utility (RCU)
To start the Repository Creation Utility (RCU):
Parent topic: Creating the Oracle WebCenter Portal Database Schemas
Navigating the RCU Screens to Create the Schemas
Schema creation involves the following tasks.
- Task 1 Introducing RCU
-
Click Next.
- Task 2 Selecting a Method of Schema Creation
-
If you have the necessary permission and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have the necessary privileges.
If you do not have the necessary permission or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option will generate a SQL script, which can be provided to your database administrator. See "Understanding System Load and Product Load" in Creating Schemas with the Repository Creation Utility.
- Task 3 Providing Database Connection Details
-
Provide the database connection details for RCU to connect to your database.
In the Host Name field, enter the SCAN address of the Oracle RAC Database.
Enter the DBMS/Service details.
Enter the Schema Owner and Schema Password details.
Click Next to proceed, then click OK on the dialog window confirming that connection to the database was successful.
- Task 4 Specifying a Custom Prefix and Selecting Schemas
-
Select Select existing prefix, and then select the prefix you used when you created the initial domain in Creating the Initial Infrastructure Domain for an Enterprise Deployment.
From the list of schemas, select WebCenter Portal . This will automatically select the required WebCenter Portal schemas. In addition, the following dependent schemas have already been installed with the Infrastructure and are grayed out:
-
Metadata Services
-
Audit Services
-
Audit Services Append
-
Audit Services Viewer
-
Oracle Platform Security Services
-
User Messaging Service
The custom prefix is used to logically group these schemas together for use in this domain only; you must create a unique set of schemas for each domain as schema sharing across domains is not supported.
Tip:
For more information about custom prefixes, see "Understanding Custom Prefixes" in Creating Schemas with the Repository Creation Utility.
For more information about how to organize your schemas in a multi-domain environment, see "Planning Your Schema Creation" in Creating Schemas with the Repository Creation Utility.
Click Next to proceed, then click OK on the dialog window confirming that prerequisite checking for schema creation was successful.
-
- Task 5 Specifying Schema Passwords
-
Specify how you want to set the schema passwords on your database, then specify and confirm your passwords.
Tip:
You must make a note of the passwords you set on this screen; you will need them later on during the domain creation process.
- Task 6 Specifying Custom Variables
-
For an enterprise deployment, Oracle recommends that you enter “Y” to enable partitioning of the Analytics data.
This feature partitions the analytics data by month. In a partitioned environment, the recommended method for purging data is simply to drop the month-based partitions that are no longer required.
For information about partitioning analytics data, see "Partitioning Oracle WebCenter Portal's Analytics Data" in the Oracle Fusion Middleware Administrator's Guide.
- Task 7 Verifying the Tablespaces for the Required Schemas
-
On the Map Tablespaces screen, review the information, and then click Next to accept the default values.
Click OK in the confirmation dialog box.
- Task 8 Completing Schema Creation
-
Navigate through the remainder of the RCU screens to complete schema creation. When you reach the Completion Summary screen, click Close to dismiss RCU.
- Task 9 Verifying the Schema Creation
-
To verify that the schemas were created successfully, and to verify the database connection details, use SQL*Plus or another utility to connect to the database, using the WCPINFRA schema name and the password you provided.
For example:
sqlplus SQL*Plus: Release 12.1.0.1.0 Production on Wed Aug 31 05:41:31 2016 Copyright (c) 1982, 2013, Oracle. All rights reserved. Enter user-name: FMW1221_WEBCENTER Enter password: schema_password Connected to: Oracle Database 11g Enterprise Edition Release 12.1.0.1.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL>
Parent topic: Creating the Oracle WebCenter Portal Database Schemas
Extending the Enterprise Deployment Domain with Oracle WebCenter Portal
Extending the domain involves the following:
- Starting the Configuration Wizard
Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain. - Navigating the Configuration Wizard Screens to Extend the Domain with WebCenter Portal
Parent topic: Extending the Domain with Oracle WebCenter Portal
Starting the Configuration Wizard
Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain.
Note:
If you added any customizations directly to the start scripts in the domain, those are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh
and configure it, for example, add custom libraries to the WebLogic Server classpath, specify Additional JAVA command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack
and unpack
commands.
For more information about using the setUserOverridesLate
script with this Enterprise Deployment Guide, see Customizing Server Parameters with the setUserOverridesLate Script.
To start the Configuration Wizard:
Navigating the Configuration Wizard Screens to Extend the Domain with WebCenter Portal
Follow the instructions in the following sections to create and configure the domain for the topology, with static or dynamic clusters.
Extending the Domain with Static Clusters
Follow the instructions in this section to create and configure the domain for the topology with static clusters.
Note:
You can use the same procedure described in this section to extend an existing domain with static clusters. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.
Domain creation and configuration includes the following tasks.
-
Task 1, "Selecting the Domain Type and Domain Home Location"
-
Task 3, "Providing the GridLink Oracle RAC Database Connection Details for Custom Data Sources"
-
Task 4, "Testing the JDBC Connections for Custom Data Sources"
-
Task 7, "Providing the GridLink Oracle RAC Database Connection Details"
-
Task 23, "Reviewing Your Configuration Specifications and Configuring the Domain"
-
Task 24, "Writing Down Your Domain Home and Administration Server URL"
- Task 1 Selecting the Domain Type and Domain Home Location
-
On the Configuration Type screen, select Update an existing domain.
In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment.
For more information about the directory location variables, see File System and Directory Variables Used in This Guide
Tip:
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
- Task 2 Selecting the Configuration Template
-
On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:
-
Oracle WebCenter Portal – 12.2.1.3.0 [wcportal]
-
Oracle WebCenter Pagelet Producer – 12.2.1.3.0 [wcportal]
-
Oracle WebCenter Portlet Producers - 12.2.1.3.0 [wcportal]
-
Oracle WebCenter Analytics Collector - 12.2.1.3.0 [wcportal]
In addition, the following additional templates should already be selected, because they were used to create the initial domain in Creating the Initial Infrastructure Domain for an Enterprise Deployment:
-
Oracle Enterprise Manager - 12.2.1.3.0 [em]
-
Oracle WSM Policy Manager - 12.2.1.3.0 [oracle_common]
-
Oracle JRF - 12.2.1.3.0 [oracle_common]
-
WebLogic Coherence Cluster Extension - 12.2.1.3.0 [wlserver]
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 3 Providing the GridLink Oracle RAC Database Connection Details for Custom Data Sources
-
The configuration wizard requires additional tasks if data sources have been added to the domain outside of the configuration wizard. This task and the next will appear if the Creating a GridLink Data Source for Leasing and Using Persistent Stores for TLOGs and JMS in an Enterprise Deployment have been completed at the end of the Extending the Domain with Oracle SOA Suite section.
Confirm the GridLink data source configuration details for the following data sources:-
Leasing
-
TLOG
-
JMS
Note:
The names of these data sources may have been customized during execution and may not match this example.If the values for these data sources do not appear complete, see the Task 6, "Specifying JDBC Component Schema Information" section for more details.
-
- Task 4 Testing the JDBC Connections for Custom Data Sources
-
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Tip:
For more information about the other options on this screen, see Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
- Task 5 Specifying the Database Configuration Type
-
On the Database Configuration Type screen, select RCU Data.
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.
Verify and ensure that credentials in all the fields are the same that you have provided while configuring Oracle Fusion Middleware Infrastructure.
Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operation succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the RCU Data option, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.
For more information about the other options on this screen, see Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.
- Task 6 Specifying JDBC Component Schema Information
-
On the JDBC Component Schema screen, select all the WebCenter Portal schemas in the table.
When you select the schemas, the fields on the page are activated and the database connection fields are populated automatically.
Click Convert to GridLink and click Next.
- Task 7 Providing the GridLink Oracle RAC Database Connection Details
-
On the GridLink Oracle RAC Component Schema screen, provide the information required to connect to the RAC database and component schemas, as shown in the following table.
Table 15-1 Information to Connect to the RAC Database and Component Schemas
Element Description and Recommended Value SCAN, Host Name, and Port
Select the SCAN check box.
In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.
In the Port field, enter the SCAN listening port for the database (for example,
1521
)ONS Host and Port
In the ONS Host field, enter the SCAN address for the Oracle RAC database.
In the Port field, enter the ONS Remote port (typically,
6200
).Enable Fan
Select the Enable Fan check box to receive and process FAN events,
- Task 8 Testing the JDBC Connections
-
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Tip:
For more information about the other options on this screen, see Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard
- Task 9 Selecting Advanced Configuration
-
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
-
Topology
-
Deployments and Services
-
- Task 10 Configuring Managed Servers
-
On the Managed Servers screen, new Managed Servers for Oracle WebCenter Portal, Portlets, and Collaboration appear in the list of servers along with the other Managed Servers that were created earlier. These servers are created automatically by the Oracle WebCenter Portal configuration template you selected earlier in the Configuration Wizard session.
Perform the following tasks to modify the default Managed Servers and create a second Managed Server for each server type:
-
Select WC_Portal and rename it to WC_Portal1.
-
Select Clone to create another managed server. Rename the new server to WC_Portal2.
-
Repeat the above two steps to edit and create WC_Portlet1 and WC_Portlet2.
Tip:
More information about the options on the Managed Server screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
Table 15-2 New Managed Server Properties
Server Name Listen Address Listen Port Enable SSL SSL Listen Port Server Groups WC_Portal1
WCPHOST1
9001
No
Disabled
WebCenter Portal Managed Server
WebCenter Portal Analytics Managed Server
WC_Portal2
WCPHOST2
9001
No
Disabled
WebCenter Portal Managed Server
WebCenter Portal Analytics Managed Server
WC_Portlet1
WCPHOST1
9002
No
Disabled
WebCenter Portal Pagelet Producer Managed Server
WebCenter Portal Portlet Producer Managed Server
WC_Portlet2
WCPHOST2
9002
No
Disabled
WebCenter Portal Pagelet Producer Managed Server
WebCenter Portal Portlet Producer Managed Server
-
- Task 11 Assign Servers to Clusters
-
Confirm that all static configured Managed Servers are assigned to the correct Clusters.
Note:
When configuring WebCenter Portal by using dynamic clusters, there will be no additional servers to assign here.Click Next to proceed to the next screen.
- Task 12 Configuring Clusters
-
In the Configure Clusters screen, add the following new clusters:
-
Portal_Cluster
-
Portlet_Cluster
For all three clusters, leave the default values for Cluster Address, Frontend Host, and Port.
Note:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 13 Assigning Server Templates
-
Click Next to proceed to the next screen.
- Task 14 Configuring Dynamic Servers
-
Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.
-
Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.
-
Confirm the Server Template selection is Unspecified.
-
Click Next.
-
- Task 15 Assigning Managed Servers to the Cluster
-
Use the Assign Servers to Clusters screen to assign Managed Servers to their respective cluster:
-
In the Clusters pane, select the cluster to which you want to assign the servers; in this case,
Portal_Cluster
. -
In the Servers pane, assign WC_Portal1 to
Portal_Cluster
by doing one of the following:-
Click once on
WC_Portal1
Managed Server to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane. -
Double-click on
WC_Portal1
to move it beneath the selected cluster in the clusters pane.
-
-
Repeat to assign
WC_Portal2
toPortal_Cluster
. -
Repeat steps 1-3 to assign
WC_Portlet1
andWC_Portlet2
toPortlet_Cluster
.
Tip:
More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 16 Configuring Coherence Clusters
-
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the port number value at 9991, as it was defined during the initial Infrastructure domain creation.
Note:
For Coherence licensing information, see Oracle Coherence Products in Oracle Fusion Middleware Licensing Information User Manual.
- Task 17 Verifying the Existing Machines
-
Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.
Click Next to proceed.
- Task 18 Assigning Servers to Machines
-
Use the Assign Servers to Machines screen to assign the Managed Servers you just created to the corresponding machines in the domain.
Assign
WC_Portal1
,WC_Portlet1
toWCPHOST1
.Assign
WC_Portal2
,WC_Portlet2
toWCPHOST2
.Tip:
More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
- Task 19 Configuring Virtual Targets
-
Click Next to proceed to the next screen.
- Task 20 Configuring Partitions
-
Click Next to proceed to the next screen.
- Task 21 Deployments Targeting
-
With the Oracle Web Services Manager Policy Manager deployed to a separate cluster, the default targeting of the WSM-PM application to the Portal and Portlet clusters should be removed.
For each of the Portal_Cluster and Portlet_Cluster in the Targets panel:
Select the wsm-pm application entry within the Application folder and click the left arrow button to remove it from the targets list.
- Task 22 Services Targeting
-
With the Oracle Web Services Manager Policy Manager deployed to a separate cluster, the default targeting of the service resources needed by the WSM-PM application can be removed from the Portal and Portlet clusters.
For each of the Portal_Cluster and Portlet_Cluster in the Targets panel:
Select and remove the following resource from the targets list:
-
mds-owsm
-
- Task 23 Reviewing Your Configuration Specifications and Configuring the Domain
-
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Click Update to execute the domain extension.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
- Task 24 Writing Down Your Domain Home and Administration Server URL
-
The Configuration Success screen will show the following items about the domain you just configured:
-
Domain Location
-
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the configuration wizard.
-
- Task 25 Start the Administration Server
-
Start the Administration Server to ensure the changes you have made to the domain have been applied.
After you have completed extending the domain with static clusters, go to Propagating the Extended Domain to the Domain Directories and Machines.
Extending the Domain with Dynamic Clusters
Follow the instructions in this section to extend the domain for the topology with dynamic clusters.
Note:
This procedure assumes that you are extending an existing domain. If your needs do not match the instructions given in the procedure, ensure that you make your selections accordingly, or refer to the supporting documentation for additional details.
Domain extension and configuration includes the following tasks:
-
Task 1, "Selecting the Domain Type and Domain Home Location"
-
Task 3, "Providing the GridLink Oracle RAC Database Connection Details for Custom Data Sources"
-
Task 4, "Testing the JDBC Connections for Custom Data Sources"
-
Task 7, "Providing the GridLink Oracle RAC Database Connection Details"
-
Task 22, "Reviewing Your Configuration Specifications and Configuring the Domain"
-
Task 23, "Writing Down Your Domain Home and Administration Server URL"
- Task 1 Selecting the Domain Type and Domain Home Location
-
On the Configuration Type screen, select Update an existing domain.
In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration domain home you created as part of the initial domain.
For more information about the directory location variables, see File System and Directory Variables Used in This Guide.
Tip:
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
- Task 2 Selecting the Configuration Template
-
On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:
-
Oracle WebCenter Portal – 12.2.1.3.0 [wcportal]
-
Oracle WebCenter Pagelet Producer – 12.2.1.3.0 [wcportal]
-
Oracle WebCenter Portlet Producers - 12.2.1.3.0 [wcportal]
-
Oracle WebCenter Analytics Collector - 12.2.1.3.0 [wcportal]
In addition, the following additional templates should already be selected, because they were used to create the initial domain in Creating the Initial Infrastructure Domain for an Enterprise Deployment:
-
Oracle Enterprise Manager - 12.2.1.3.0 [em]
-
Oracle WSM Policy Manager - 12.2.1.3.0 [oracle_common]
-
Oracle JRF - 12.2.1.3.0 [oracle_common]
-
WebLogic Coherence Cluster Extension - 12.2.1.3.0 [wlserver]
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 3 Providing the GridLink Oracle RAC Database Connection Details for Custom Data Sources
-
The configuration wizard may present additional tasks if data sources have been added to the domain outside of the configuration wizard. This task and the next will appear if the Creating a GridLink Data Source for Leasing and Using Persistent Stores for TLOGs and JMS in an Enterprise Deployment have been completed at the end of the Extending the Domain with Oracle SOA Suite section. If you have chosen the option to reuse the
WLSSchemaDatasource
for leasing and JMS/TLOG persistent stores, this step and the next step will not appear.Confirm the GridLink data source configuration details for the following data sources:-
Leasing
-
TLOG
-
JMS
Note:
The names of these data sources may have been customized during execution and may not match this example.If the values for these data sources do not appear complete, see the Task 6, "Specifying JDBC Component Schema Information" section for more details.
-
- Task 4 Testing the JDBC Connections for Custom Data Sources
-
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Tip:
For more information about the other options on this screen, see Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
- Task 5 Specifying the Database Configuration Type
-
On the Database Configuration Type screen, select RCU Data.
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.
Verify and ensure that credentials in all the fields are the same that you have provided while configuring the Oracle Fusion Middleware Infrastructure.
Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the RCU Data option, see Understanding the Service Table Schemain Creating Schemas with the Repository Creation Utility.
For more information about the other options on this screen, see Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.
- Task 6 Specifying JDBC Component Schema Information
-
On the JDBC Component Schema screen, select all of the new schemas (for WebCenter Portal components) in the table.
When you select the schemas, the fields on the page are activated and the database connection fields are populated automatically.
Click Convert to GridLink and click Next.
- Task 7 Providing the GridLink Oracle RAC Database Connection Details
-
On the GridLink Oracle RAC Component Schema screen, provide the information that is required to connect to the RAC database and component schemas, as shown in the following table.
Element Description and Recommended Value SCAN, Host Name, and Port
Select the SCAN check box.
In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.
In the Port field, enter the SCAN listening port for the database (for example,
1521
).ONS Host and Port
In the ONS Host field, enter the SCAN address for the Oracle RAC database.
In the Port field, enter the ONS Remote port (typically,
6200
).These values are required when connecting to Oracle 11g databases but optional when connecting to Oracle database 12c and higher. If you are using an Oracle 12c database, the ONS list is automatically provided from the database to the driver.
Enable Fan
Verify that the Enable Fan check box is selected, so the database can receive and process FAN events.
- Task 8 Testing the JDBC Connections
-
Use the JDBC Component Schema Test screen to test the data source connections you have just configured.
A green check mark in the Status column indicates a successful test. If you encounter any issues, see the error message in the Connection Result Log section of the screen, fix the problem, then try to test the connection again.
Tip:
For more information about the other options on this screen, see Test Component Schema in Creating WebLogic Domains Using the Configuration Wizard.
- Task 9 Selecting Advanced Configuration
-
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
-
Topology
-
Deployments and Services
Note:
JMS JDBC stores are recommended and were advised to be selected in the WebCenter Content Extension section Task 3, "Configuring High Availability Options" so there is no need to configure File Stores.
If you have chosen the JMS File Stores option in Task 3, "Configuring High Availability Options" during the initial domain extension for WebCenter Content, you have to select the File Stores option now to confirm the configuration of the file stores in a shared location at
ORACLE_RUNTIME/domain_name/cluster_name/jms
. A shared location is required if using file stores to resume JMS and HA in a failover scenario. If using JDBC stores, do not select the File Store advanced configuration option here. -
- Task 10 Configuring Managed Servers
-
On the Managed Servers screen, multiple new Managed Servers for Oracle WebCenter Portal and Portlet appear in the list of static configured Managed Servers along with the existing WebCenter Content IBR servers, if installed.
Static Managed Server definitions are not needed for dynamic cluster configurations.
Delete the default
WC_Portlet
andWC_Portal
Managed Servers by completing the following steps:-
Click on the Server Name field for the Managed Server definition to be deleted.
-
Click Delete.
-
Repeat for each Managed Server to be removed.
-
Click Next to proceed to the next screen.
-
- Task 11 Configuring Clusters
-
In this task, you create multiple clusters to which you can target the Oracle WebCenter Portal software.
In the Configure Clusters screen, add the following new clusters with the corresponding Dynamic Server Groups:Cluster Name Dynamic Server Group Selection Portal_Cluster
PORTAL-ANALYTICS-DYN-CLUSTER
Portlet_Cluster
PORTLET-PAGELET-DYN-CLUSTER
-
Click Add.
-
Specify the Cluster Name field value appropriately.
-
Leave the Cluster Address field and Frontend Host fields blank.
-
Select the appropriate value from the Dynamic Server Groups drop-down list as indicated in the previous table.
Note:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to Considerations for Choosing Unicast or Multicast in Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
-
Click Next to proceed to the next screen.
-
- Task 12 Assigning Server Templates
-
Use the Server Templates screen to configure and assign the new server templates as indicated.
Note:
With Dynamic Clusters for product components that can scale-up and scale-out, it is important to assure that sufficient port ranges are reserved without overlap to allow a dynamic cluster to auto-calculate assigned listen ports for the maximum allowable number of dynamic managed servers needed. The Dynamic Clusters Calculated Listen Ports feature will increment the port number by one for each dynamic managed server. Adjust the ranges between the Listen Ports for the various services according to your scalability requirements with some room for growth. The first managed server will be assigned this designated listen port value+1
.In the Configure Clusters screen, add the following new clusters with the corresponding Dynamic Server Groups:Name Listen Port SSL Listen Port Enable SSL portal-server-template
9010
9110
unchecked
portlet-server-template
9020
9120
unchecked
-
Update the listen port values per recommendations.
-
Leave the Enable SSL option unchecked.
-
Update the SSL Listen Port values accordingly to prevent overlapping configuration values.
-
Click Next to proceed to the next screen once all values are correct.
-
- Task 13 Configuring Dynamic Servers
-
Use the Dynamic Servers screen to configure properties controlling how the dynamic Managed Servers are created and scaled. See Dynamic Clusters in Administering Clusters for Oracle WebLogic Server.
Configure the new WebCenter Portal and Portlet cluster settings as follows:
-
Verify that the Cluster Name values match as configured earlier.
-
Verify that the Server Name Prefix values are as follows:
-
Portal Cluster: WC_Portal
-
Portlet_Cluster: WC_Portlet
-
-
Verify that the correct Server Template is selected from the Server Template drop-down list:
-
Portal Cluster: portal-server-template
-
Portlet_Cluster: portlet-server-template
-
-
Specify the Dynamic Cluster Size for the new clusters.
At a minimum, set the size equal to the number of
WCPHOSTn
machines configured in the domain to achieve simple horizontal scale-out redundancy. For the baseline EDG topology, this would be a value of2
.Note:
The cluster size can be tuned as necessary to meet the scalability needs, taking into account the available listen port range specified earlier, the number of
WCPHOSTn
machines available, and any hardware resource limitations.This setting effects the current size of the cluster and may not configure the Maximum Dynamic Server Count.
If the Dynamic Cluster Size is set greater than the number of machines available that match the Machine Name Match Expression, then multiple managed servers will be created on the machines in a vertical scale-up topology.
Scalability check: After extending the domain, confirm the Maximum Dynamic Server Count is no greater than the number of available listen ports as declared in the previous task, if the Calculated Listen Port option is selected for each cluster. If the Maximum Dynamic Server count is higher than the number of available ports between the cluster port ranges, problems can occur when scaling the cluster.
-
Specify
WCPHOST*
in the Machine Name Match Expression field for the new clusters.Note:
If you have customized your WebLogic Machine Name configurations, ensure that they have a unique and consistent prefix to use in the match expression. -
Select the Calculated Machine Names, Calculated Listen Ports, and Dynamic Cluster fields as follows:
-
Portal Cluster: check all the three fields
-
Portlet_Cluster: check all the three fields
-
-
Confirm all settings for pre-existing clusters and fix any extra configuration selections that may have been changed unexpectedly by the Configuration Wizard.
For example: Ensure that any static clusters, like
IBR_Servers
do not have the Calculated Listen Ports or Dynamic Cluster checkboxes selected. -
Click Next to proceed to the next screen.
-
- Task 14 Assign Servers to Clusters
-
Confirm all static configured Managed Servers are assigned to the correct Clusters.
Note:
This screen will be presented only if there are static clusters or managed servers defined in the domain.
When configuring WebCenter Portal by using dynamic clusters, no managed servers are created during configuration to be assigned here. Only pre-existing managed servers will appear, and no changes are necessary.
Click Next to proceed to the next screen.
- Task 15 Configuring Coherence Clusters
-
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Validate the port number is set as expected based on the initial domain creation, then click Next.
Note:
For Coherence licensing information, refer to Oracle Coherence in Oracle Fusion Middleware Licensing Information.
- Task 16 Verifying the Existing Machines
-
Complete the following steps:
-
Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.
Table 15-3 Values to Use When Creating Unix Machines
Name Node Manager Listen Address Node Manager Listen Port ADMINHOST
Enter the value of the ADMINVHN variable.
5556
WCCHOST1
The value of the WCCHOST1 host name variable. For example,
WCCHOST1.example.com
.5556
WCCHOST2
The value of the WCCHOST2 host name variable. For example,
WCCHOST2.example.com
.5556
WCPHOST1
The value of the WCPHOST1 host name variable. For example,
WCPHOST1.example.com
.5556
WCPHOST2
The value of the WCPHOST2 host name variable. For example,
WCPHOST2.example.com
.5556
-
Click Next to proceed.
-
- Task 17 Assigning Servers to Machines
-
Click Next to proceed to the next screen.
- Task 18 Configuring Virtual Targets
-
Click Next to proceed to the next screen.
- Task 19 Configuring Partitions
-
Click Next to proceed to the next screen.
- Task 20 Deployments Targeting
-
With the Oracle Web Services Manager Policy Manager deployed to a separate cluster, the default targeting of the WSM-PM application to the Portal and Portlet clusters should be removed.
-
In the Deployment Targets panel, scroll to locate the
wsm-pm
application deployment for the Portal_Cluster. -
Click on the
wsm-pm
application deployment for the Portal_Cluster. -
Click the left-arrow button to remove the wsm-pm application deployment from the Portal_Cluster in the Deployment Targets list.
-
Repeat this procedure for the
wsm-pm
application deployment for the Portlet_Cluster.
-
- Task 21 Services Targeting
-
With the Oracle Web Services Manager Policy Manager deployed to a separate cluster, the default targeting of the service resources needed by the WSM-PM application can be removed from the Portal and Portlet clusters.
-
In the Deployment Targets panel, scroll to locate the
mds-owsm
JDBCSystemResource for the Portal_Cluster. -
Click on the
mds-owsm
resource for the Portal_Cluster. -
Click the left-arrow button to remove the
mds-owsm
resource deployment from the Portal_Cluster. -
Repeat this procedure for the
mds-owsm
JDBCSystemResource deployment for the Portlet_Cluster.
-
- Task 22 Reviewing Your Configuration Specifications and Configuring the Domain
-
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Click Update to execute the domain extension.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
- Task 23 Writing Down Your Domain Home and Administration Server URL
-
The Configuration Success screen will show the following items about the domain you just configured:
-
Domain Location
-
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the configuration wizard.
-
- Task 24 Start the Administration Server
-
Start the Administration Server, login, and then verify the clusters and servers views to ensure that the changes made to the domain have been applied.
Propagating the Extended Domain to the Domain Directories and Machines
Parent topic: Extending the Domain with Oracle WebCenter Portal
Restoring customizations to setDomainEnv.sh after Unpacking the Domain
If any customizations have been made earlier to the setDomainEnv.sh
files in ASERVER_HOME and MSERVER_HOME, then these customizations will need to be repeated after any domain extension.
Note:
Modifying the setDomainEnv
script is not recommended. For more information, see Customizing Domain Wide Server Parameters in Administering Server Startup
and Shutdown for Oracle WebLogic Server.
For WebCenter Enterprise Deployments, see Customizing Server Parameters with the setUserOverridesLate Script.
On WCCHOST1:
Parent topic: Extending the Domain with Oracle WebCenter Portal
Updating the NodeManager Configuration After Unpacking the Domain
When extending a domain, the nodemanager.properties
file in MSERVER_HOME may be overwritten with some values from the nodemanager.properties
file for ASERVER_HOME. Specifically, the ListenAddress
and/or CustomIdentityAlias
values can be reset.
Notes::
-
The
ListenAddress
may typically get reset on the MSERVER_HOME nodemanager residing on the same host as the ASERVER_HOME nodemanager. In this topology, WCCHOST1. -
For domain extensions prior to Enabling SSL Communication Between the SOA Servers and the Hardware Load Balancer, steps 2 through 4 regarding the
CustomIdentityAlias
may not be applicable.
MSERVER_HOME/nodemanager/nodemanager.properties
file on each host:
Note:
For more information about theCustomIdentityAlias
parameter, see Configuring Node Manager to Use the Custom Keystores.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Restarting and Validating Pre-existing Managed Servers
Parent topic: Extending the Domain with Oracle WebCenter Portal
Modifying the Upload and Stage Directories to an Absolute Path in an Enterprise Deployment
After you configure the domain and unpack it to the Managed Server domain directories on all the hosts, verify and update the upload and stage directories for Managed Servers in the new clusters. Also, update the upload directory for the AdminServer to have the same absolute path instead of relative, otherwise deployment issues can occur. If you implement dynamic clusters, the configuration of the server template assigned to each newly added cluster should be verified and updated, otherwise, verify and update every statically-defined Managed Server for the newly added clusters.
This step is necessary to avoid potential issues when you perform remote deployments and for deployments that require the stage mode.
To update the directory paths for the Deployment Stage and Upload locations, complete the following steps:
-
Log in to the Oracle WebLogic Server Administration Console.
-
In the left navigation tree, expand Domain, and then Environment.
-
Click Lock & Edit.
-
Navigate to and edit the appropriate objects for your cluster type.
-
For Static Clusters, navigate to Servers and click the name of the Managed Server you want to edit.
-
For Dynamic Clusters, navigate to Clusters > Server Templates, and click on the name of the server template to be edited.
-
-
For each new Managed Server or Server Template to be edited:
-
Click the Configuration tab, and then click the Deployment tab.
-
Verify that the Staging Directory Name is set to the following:
MSERVER_HOME/servers/server_or_template_name/stage
Replace
MSERVER_HOME
with the full path for theMSERVER_HOME
directory.If you use static clusters, update with the correct name of the Managed Server that you are editing.
If you use dynamic clusters, leave the template name intact. For example:
/u02/oracle/config/domains/
wcpedg_domain
/servers/XYZ-server-template/stage -
Update the Upload Directory Name to the following value:
ASERVER_HOME/servers/AdminServer/upload
Replace
ASERVER_HOME
with the directory path for the ASERVER_HOME directory. -
Click Save.
-
Return to the Summary of Servers or Summary of Server Templates screen as applicable.
-
-
Repeat the previous steps for each of the new managed servers or dynamic cluster server templates.
-
Navigate to and update the Upload Directory Name value for the AdminServer:
-
Navigate to Servers, and select the AdminServer.
-
Click the Configuration tab, and then click the Deployment Tab.
-
Verify that the Staging Directory Name is set to the following absolute path:
ASERVER_HOME/servers/AdminServer/stage
-
Update the Upload Directory Name to the following absolute path:
ASERVER_HOME/servers/AdminServer/upload
Replace
ASERVER_HOME
with the directory path for theASERVER_HOME
directory. -
Click Save.
-
-
When you have modified all the appropriate objects, click Activate Changes.
Note:
If you continue directly with further domain configurations, a restart to enable the stage and upload directory changes is not strictly necessary at this time.Parent topic: Extending the Domain with Oracle WebCenter Portal
Configuring Listen Addresses When Using Dynamic Clusters
The default configuration for dynamic managed servers in dynamic clusters is to listen on all available network interfaces. In most cases, the default configuration may be undesirable. To limit the listen address to a specific address when you use dynamic clusters, see Configuring Listen Addresses in Dynamic Cluster Server Templates. Reverify the test URLs that are provided in the previous sections after you change the listen address and restart the clustered managed servers.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Starting the Node Manager on WCPHOST1
After you unpack the extended domain on WCPHOST1, you can start the Node Manager from the Managed Server directory on WCPHOST1.
For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Starting the Node Manager on WCPHOST2
After you have propagated the domain configuration to WCPHOST2, you can start the Node Manager for the MSERVER_HOME domain directory.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Starting and Validating the WC_Portal1 and WC_Portlet1 Managed Servers
Now that you have extended the domain, restarted the Administration Server, and propagated the domain to the other hosts, you can start the newly configured Oracle WebCenter Portal servers.
This process involves three tasks:
- Starting the Managed Servers on WCPHOST1
- Adding the WCPAdmin Role to the Portal Administrators Group
- Validating WebCenter Portal on WCPHOST1
- Starting and Validating the Managed Servers on WCPHOST2
Parent topic: Extending the Domain with Oracle WebCenter Portal
Adding the WCPAdmin Role to the Portal Administrators Group
Before you validate the Oracle WebCenter Portal configuration on WC_Portal1 Managed Server, grant the WebCenter Portal administrator role to the WCPAdministrators
LDAP group.
To perform this task, refer to Configuring Roles for Administration of Oracle WebCenter Portal Products.
- Granting the Administrator Role for WebCenter Portal Using WLST
This section describes how to grant WebCenter Portal's Administrator role using WLST. - Granting the Administrator Role for WebCenter Portal Using Fusion Middleware Control
This section describes how to grant WebCenter Portal's Administrator role to a user account other than the default weblogic account.
Granting the Administrator Role for WebCenter Portal Using WLST
This section describes how to grant WebCenter Portal's Administrator role using WLST.
Validating WebCenter Portal on WCPHOST1
Once the Portal and Portlet managed servers are started on WCPHOST1, validate that the web applications respond using following application URLs:
Notes:
-
Authenticate as
weblogic_wcp
as necessary. -
Update port numbers accordingly if using Dynamic Clustering with the Calculated Listen Port feature enabled. See the WebCenter Portal Listen Port Summary by Cluster Type table for example port assignments.
Table 15-4 WebCenter Portal Listen Port Summary by Cluster type
Managed Server | Listen Port Static Cluster | Listen Port Dynamic Cluster |
---|---|---|
WC_Portal1 | 9001 | 9011 |
WC_Portal2 | 9001 | 9012 |
WC_Portlet1 | 9002 | 9021 |
WC_Portlet2 | 9002 | 9022 |
Starting and Validating the Managed Servers on WCPHOST2
After you have validated the successful configuration and startup of the Managed Servers on WCPHOST1, you can then start and validate the new Managed Servers on WCPHOST2, using the procedure in Starting and Validating the WC_Portal1 and WC_Portlet1 Managed Servers.
Note:
-
Authenticate as
weblogic_wcp
as necessary. -
Update port numbers accordingly if using Dynamic Clustering with the Calculated Listen Port feature enabled. See the WebCenter Portal Listen Port Summary by Cluster Type table for example port assignments.
Once the Portal and Portlet managed servers are started on WCPHOST2, validate that the web applications respond using following application URLs:
Enabling SSL Communication Between the WebCenter Portal and Portlet Managed Servers and the Hardware Load Balancer
After you extend the domain with Oracle WebCenter Portal, ensure that the Administration Server and Managed Servers can access the front-end, SSL URL of the hardware load balancer.
This allows applications and web services to invoke callbacks and other communications with the front-end, secure URL.
See Enabling SSL Communication Between the Middle Tier and the Hardware Load Balancer.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Configuring Session Persistence for WebCenter Portal
Applications that are deployed to a cluster in WebLogic Server can optionally take advantage of HTTP session persistence and replication to provide high-availability for the user's experience (their session data) in case of the loss or outage of one or more application server instances within the cluster. This additional session state replication between server instances incurs a performance penalty for the application.
By default, the HTTP session persistence is disabled in WebCenter Portal, and can be enabled if required.
For technical reference, see Using Sessions and Session Persistence in Developing Web Applications, Servlets, and JSPs for Oracle WebLogic Server, and HTTP State Replication in Administering Clusters for Oracle WebLogic Server.
-
Create a new deployment plan XML file for the webcenter portal application. The deployment plan should be in DEPLOY_PLAN_HOME on the shared filesystem available to all hosts. Set the example path/filename to:
DEPLOY_PLAN_HOME/DOMAIN_NAME/webcenterPlan.xml
Note:
Substitute the full path to DEPLOY_PLAN_HOME and DOMAIN_NAME in the <config-root> element value.<?xml version='1.0' encoding='UTF-8'?> <deployment-plan xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-deployment-plan.xsd" global-variables="false"> <application-name>webcenter</application-name> <variable-definition> <variable> <name>addPersistentStore</name> <value>replicated_if_clustered</value> </variable> </variable-definition> <module-override> <module-name>spaces.war</module-name> <module-type>war</module-type> <module-descriptor external="false"> <root-element>weblogic-web-app</root-element> <uri>WEB-INF/weblogic.xml</uri> <variable-assignment> <name>addPersistentStore</name> <xpath>/weblogic-web-app/session-descriptor/persistent-store-type</xpath> <operation>add</operation> </variable-assignment> </module-descriptor> </module-override> <config-root>DEPLOY_PLAN_HOME/DOMAIN_NAME/webcenterPlan.xml</config-root> </deployment-plan>
Note:
DEPLOY_PLAN_HOME and DOMAIN_NAME are placeholder substitution values. Provide the actual paths or names as required.The DEPLOY_PLAN_HOME value should be replaced with the full path to a shared filesystem directory as specified in Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
-
Sign in to the WebLogic Server Console as an administrative user. For example:
weblogic_wcp
. -
Click Deployments in the Domain Structure panel.
-
Click Lock & Edit.
-
Select the checkbox for the webcenter application.
-
Click Update.
-
Observe the current Deployment Plan Path value as (no value specified).
Note:
If a custom deployment plan has previously been specified, then integrate the differences based on the code in step 1 into the existing deployment plan file instead to preserve any pre-existing deployment customizations. -
Click Change Path associated with the Deployment plan path field.
-
Enter the full and complete path to the custom deployment plan XML file, and click Next.
DEPLOY_PLAN_HOME/DOMAIN_NAME/webcenterPlan.xml
-
Click Finish. The WebCenter Portal application deployment must be redeployed and cannot be updated in-place. Do not change the selection of the redeploy option.
-
Click Activate Changes in the Change Center panel.
-
Restart all managed servers in the
Portal_Cluster
. -
Validate the updated plan enhancements are listed in the webcenter application deployment section of
ASERVER_HOME/config/config.xml
. Look for the <plan-dir> and <plan-path> elements.For example:<app-deployment> <name>webcenter</name> <target>WC_Portal</target> <module-type>ear</module-type> <source-path>/u01/oracle/products/fmw/wcportal/archives/applications/webcenter.ear</source-path> <deployment-order>400</deployment-order> <plan-dir xsi:nil="true"></plan-dir> <plan-path>/u01/oracle/config/wcpedg_domain/webcenterPlan.xml</plan-path> <security-dd-model>DDOnly</security-dd-model> <staging-mode>nostage</staging-mode> <parallel-deploy-modules>false</parallel-deploy-modules> </app-deployment>
Parent topic: Extending the Domain with Oracle WebCenter Portal
Configuring Analytics
In the enterprise deployment reference architecture, analytics collectors are usually configured to communicate with the local WebCenter Portal application in a 1-1 relationship (the collectors listen on localhost on the default port). Additional analytics collector configuration is required if the Portal_Cluster will be scaled-up vertically with multiple managed servers per WCPHOST, either manually with traditional cluster configuration or through the use of the WebLogic Server Dynamic Clustering features.
While multiple collectors on the same host can be configured to avoid port conflicts to allow vertical scale-up of Portal and analytics services, there can be only one active common Analytics collector registration in the portal. This active registration can reference only a single hostname and port combination. As such, it remains recommended to configure the WebCenter Portal applications to send event messages to localhost with the default analytics collector port.
Note:
Clustered analytics collectors are not supported for collecting WebCenter Portal events.
Additional configuration to avoid analytics collector port conflicts would be required if scaling-up more than one portal managed server per host. In this case, for more information about configuring collector maximum port values, see Configuring Analytics Collector Settings in the Administering Oracle WebCenter Portal guide.
Portal run-time configuration only supports a single active Analytics collector service registration with a single port. Only the collector started per host using the port matching the portal registration will collect data. If that collector or managed server is down, Analytics event collection will not occur for any of the remaining portal servers on that host.
Use of the local hardware load balancer to centrally distribute analytics traffic across co-located collectors in scale-up scenarios has not been validated as of this Enterprise Deployment Guide release. Use of this potential topology option should be thoroughly tested in a non-production environment before finalizing your architecture in this regard.
- Registering a Default Analytics Connection for WebCenter Portal
Connect the WebCenter Portal application to the analytics collector. - Configuring Analytics to Support Scale-Up of the Portal Managed Servers
Additional configuration and management processes may be needed for Analytics if Portal managed servers are to be scaled-up beyond one managed server per host. Scale-up operations may be manual in the case of traditional static clusters. Scale-up may be manual or elastic (policy-based) when using Dynamic Cluster features of the WebLogic Server.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Registering a Default Analytics Connection for WebCenter Portal
Connect the WebCenter Portal application to the analytics collector.
To connect the WebCenter Portal application to the analytics collector, complete the following steps:
Parent topic: Configuring Analytics
Configuring Analytics to Support Scale-Up of the Portal Managed Servers
Additional configuration and management processes may be needed for Analytics if Portal managed servers are to be scaled-up beyond one managed server per host. Scale-up operations may be manual in the case of traditional static clusters. Scale-up may be manual or elastic (policy-based) when using Dynamic Cluster features of the WebLogic Server.
Note:
This section applies only when there are multiple portal managed servers per host.
If the topology follows the default enterprise deployment guide reference architecture with only one portal managed server per host, or is enhanced to include only horizontal scale-out scenarios, then this section does not apply and can be skipped.
-
The Analytics Collector Port range must be set to allow multiple collector services to run on a single host and listen on separate unique ports.
-
WebCenter Portal registrations for the additional collectors will need to be added. These registrations can be quickly activated later and portal servers restarted if the Analytics Collector on the default port is unavailable. Once restarted, the portal servers will attempt to use the newly activated collector registration.
-
There must be an Analytics collector process listening on the port specified in the default and active registration within the portal.
-
There must be an Analytics collector process available on each port within the configured Analytics Collector port range on every WCPHOST.
-
Every WCPHOST must have an identical number of scaled-up portal managed servers, otherwise some portal servers may not find the collector on the currently default/active port on localhost for the selected registration.
The following sections advise on the additional configuration required for analytics when accommodating for scale-up:
- Configuring the Analytics Collector Port Range
The Analytics collector settings are environment-wide and cannot be customized on a server-by-server basis. The maxPort parameter provides an effective range above the defaultPort for multiple Analytics Collector instances to use unique ports on a per-host basis. If a collector process cannot bind to the default port, it retries every port number until it reaches the maxPort value. If no ports are available, the portal managed server will not start correctly. - Registering additional Analytics Collectors in WebCenter Portal
For each port in the configured Analytics Collector port range, register additional non-default collectors with unique connection names and ports based on the port-range assigned in the Analytics Collector configuration. This will allow for a simplified maintenance process to swap collector registrations in a persistent, well-qualified manner. - Failing-over the Portal's Default Analytics Registration
In the case of a failure of a portal managed server that includes the Analytics Collector service listening on the default port, an alternate analytics connection should be selected in the portal configuration as the default connection and the surviving portal servers restarted as soon as possible.
Parent topic: Configuring Analytics
Configuring the Analytics Collector Port Range
The Analytics collector settings are environment-wide and cannot be customized on a server-by-server basis. The maxPort parameter provides an effective range above the defaultPort for multiple Analytics Collector instances to use unique ports on a per-host basis. If a collector process cannot bind to the default port, it retries every port number until it reaches the maxPort value. If no ports are available, the portal managed server will not start correctly.
To update the Analytics maxPort value, use the following WLST method when connected to the administration server for the domain:
Registering additional Analytics Collectors in WebCenter Portal
For each port in the configured Analytics Collector port range, register additional non-default collectors with unique connection names and ports based on the port-range assigned in the Analytics Collector configuration. This will allow for a simplified maintenance process to swap collector registrations in a persistent, well-qualified manner.
createAnalyticsCollectorConnection(appName="webcenter", server="WC_Portal1", connectionName="NAME", collectorPort=PORTNUMBER, isEnabled=1, default=0, isUnicast=1, collectorHost="localhost", timeout=30)
Complete the following steps:
Failing-over the Portal's Default Analytics Registration
In the case of a failure of a portal managed server that includes the Analytics Collector service listening on the default port, an alternate analytics connection should be selected in the portal configuration as the default connection and the surviving portal servers restarted as soon as possible.
Until this occurs, analytics collection for the remaining portal instances on that machine will not be able to contact the collector on the default port to log analytics metrics. Only one registration is default and actively used at a time.
The fail-over of the default analytics registration is a manual process. The change will be environment-wide but will only take effect when each portal server instance is restarted.
Note:
This section is applicable only when there are multiple portal managed servers per host.
This sections is not applicable if the topology follows the default enterprise deployment guide reference architecture with only one portal managed server per host or is enhanced to include only horizontal scale-out scenarios.
To change the default Analytics registration, complete the following steps:
Confirming REST API Configuration
This section describes the procedure to configure REST APIs.
If you want to confirm the seed entries in the credential store that enable the REST security tokens to function properly, run the following WLST commands:
Note:
If the credential maps already exist, JPS-01007 exceptions messages will be returned. This confirms the configuration.Parent topic: Extending the Domain with Oracle WebCenter Portal
Configuring Oracle HTTP Server for the Extended Domain
The following sections describe how to configure the Oracle HTTP Server instances so they route requests for both public and internal URLs to the proper clusters in the enterprise topology.
- Configuring Oracle HTTP Server for the Oracle WebCenter Portal Clusters
- Validating the Oracle WebCenter Portal Public Services URLs Through the Load Balancer
- Configuring HTTP Server for Internal WebCenter Services
- Validating the Oracle WebCenter Portal Internal Services URLs Through the Load Balancer
Parent topic: Extending the Domain with Oracle WebCenter Portal
Configuring Oracle HTTP Server for the Oracle WebCenter Portal Clusters
To configure the Oracle HTTP Server instances in the Web tier so they route requests correctly to the Oracle WebCenter Portal clusters, use the following procedure to create an additional Oracle HTTP Server configuration file that creates and defines the parameters of the wcp.example.com
virtual server.
This procedure assumes you performed the Oracle HTTP Server configuration tasks described in Configuring Oracle HTTP Server to Route Requests to the Application Tier.
Complete the following steps to update the virtual host configuration file so that requests are routed properly:
Parent topic: Configuring Oracle HTTP Server for the Extended Domain
Validating the Oracle WebCenter Portal Public Services URLs Through the Load Balancer
To validate the configuration of the Oracle HTTP Server virtual hosts and to verify that the hardware load balancer can route public service requests through the Oracle HTTP Server instances to the application tier:
Parent topic: Configuring Oracle HTTP Server for the Extended Domain
Configuring HTTP Server for Internal WebCenter Services
To configure the Oracle HTTP Server instances in the Web tier so they route requests correctly to the internal Oracle WebCenter services, use the following procedure to edit existing wcpinternal_vh.conf
file.
This procedure assumes you performed the Oracle HTTP Server configuration tasks described in Configuring Oracle HTTP Server to Route Requests to the Application Tier.
Complete the following steps to update the virtual host configuration file so that requests are routed properly:
Parent topic: Configuring Oracle HTTP Server for the Extended Domain
Validating the Oracle WebCenter Portal Internal Services URLs Through the Load Balancer
To validate the configuration of the Oracle HTTP Server virtual hosts and to verify that the hardware load balancer can route internal service requests through the Oracle HTTP Server instances to the application tier:
Parent topic: Configuring Oracle HTTP Server for the Extended Domain
Configuring WebCenter Portal for External Services
This section describes how to configure external tools and services for WebCenter Portal applications by using Fusion Middleware Control or WLST commands. For most external services, you must set up a connection between the WebCenter Portal application and the backend server.
Each of the following service configurations require various Managed Servers to be restarted for the changes take effect. Some of the restarts are required at the point during the process as indicated. Other restarts may be optionally delayed to the end of the section if completing this section from start-to-finish, otherwise all restarts should be done within the individual subtopics. Restarts that may be delayed to the end of the service configurations section are mentioned as a note.
- Configuring Default Web Service Policies for WebCenter Portlet Producer Applications
- Registering Portlet Producers
- Registering the Pagelet Producer
- Configuring Search Services
- Configuring Oracle WebCenter Portal Notifications for the SMTP Mail Server
- Configuring the Content Server Connection
Oracle WebCenter Portal supports content management and storage capabilities, including file upload, file and folder creation and management, file check out, and versioning. - Restarting the Portal Managed Servers to Activate all Service Configuration Changes
If the optional restarts in the sections above have been deferred, restart the portal managed servers now.
Parent topic: Extending the Domain with Oracle WebCenter Portal
Configuring Default Web Service Policies for WebCenter Portlet Producer Applications
After installing Oracle WebCenter Portal, you must attach the default Oracle Web Services Manager (OWSM) security policy to the following:
-
WSRP Tools Producer (wsrp-tools)
These steps are required because security policies for these Web service end points are not configured out-of-the-box.
Parent topic: Configuring WebCenter Portal for External Services
Registering Portlet Producers
Several out-of-the-box portlet producers can be registered with the WebCenter Portal application. In the WebCenter Portal Enterprise Deployment, the required producer URLs are as follows:
-
WSRP Producer URL: http://wcpinternal.example.com/wsrp-tools/portlets/wsrp2?WSDL
-
WebClipping Producer URL: http://wcpinternal.example.com/portalTools/webClipping/providers
-
OmniPortlet Producer URL: http://wcpinternal.example.com/portalTools/omniPortlet/providers
You can register portlet producers using Fusion Middleware Control or WLST commands.
- Registering Out-of-the-Box Portlet Producers using Fusion Middleware Control
- Registering Out-of-the-Box Portlet Producers Using WLST
Parent topic: Configuring WebCenter Portal for External Services
Registering Out-of-the-Box Portlet Producers using Fusion Middleware Control
For details on how to register portlet producers using Fusion Middleware Control, see Managing Portlet Producers in Administering Oracle WebCenter Portal.
Parent topic: Registering Portlet Producers
Registering Out-of-the-Box Portlet Producers Using WLST
Parent topic: Registering Portlet Producers
Registering the Pagelet Producer
If you want to expose WSRP and Oracle JPDK portlets and OpenSocial gadgets as pagelets in WebCenter Portal, you must register the pagelet producer. In the WebCenter Portal Enterprise Deployment, the required pagelet producer URL is:
http://wcpinternal.example.com/pagelets
You can register the pagelet producer using Fusion Middleware Control or WLST commands.
- Registering Pagelet Producer Using Fusion Middleware Control
- Registering Pagelet Producer Using WLST
Parent topic: Configuring WebCenter Portal for External Services
Registering Pagelet Producer Using Fusion Middleware Control
To register Pagelet Producer using Fusion Middleware Control:
-
Sign-in to the Fusion Middleware Control by using the administrator's account (for example:
weblogic_wcp
), and navigate to the WebCenter Portal home page.Note:
When administering WebCenter resources in the Enterprise Manager Fusion Middleware Control, it is recommended to use the WebCenter-specific administrative user created in the remote LDAP authenticator (for example,
weblogic_wcp
). See Configuring Roles for Administration of an Enterprise Deployment.See Navigating to the Home page for WebCenter Portal in Administering Oracle WebCenter Portal .
-
From the WebCenter Portal menu, select Register Producer.
-
Enter connection details for Pagelet Producer, as shown in the following table.
Field Description Connection Name
A unique name to identify this Pagelet Producer instance within the application. The name must be unique across all WebCenter Portal connection types. The name specified here appears in Composer under the UI Components > Pagelet Producers folder (by default).
Producer Type
Select Pagelet Producer.
Server URL
The URL to Pagelet Producer. The URL must include a fully-qualified domain name. Use the following syntax:
<protocol>://
<host_name>
:
<port_number>
/pagelets/
For example:
http://wcpinternal.example.com/pagelets/
If pagelets contain secure data, the registered URL must use the
https
protocol. For example:https://wcp.example.com/pagelets/
The context root can be changed from /pagelets/ if necessary; for details, see “Redeploying Pagelet Producer to a Different Context” in Administering Oracle WebCenter Portal.
Note: In WebCenter Portal, if the Pagelet Producer URL is protected by OAM, the URL to the pagelet catalog must be excluded (mapped directly without access control), or the catalog will appear to be empty when using REST. The pagelet catalog URL is
http://
<host_name>:<port_number>
/pagelets/api/v2/ensemble/pagelets
-
Click OK. The new producer appears in the connection table.
Parent topic: Registering the Pagelet Producer
Registering Pagelet Producer Using WLST
To register out-of-the-box pagelet producers using WLST:
-
Start the WebLogic Scripting Tool:
WCPHOST1> ORACLE_COMMON_HOME/common/bin/wlst.sh
-
In WLST, connect as the administrator.
For example,
connect("weblogic_wcp","admin password","t3://ADMINVHN:7001",server="WC_Portal1")
-
Register the pagelet producer by entering the following command.
registerPageletProducer(appName='webcenter', name='PageletProducer', url='http://wcpinternal.example.com/pagelets', server='WC_Portal1')
For command syntax and examples, see registerPageletProducer
in WebCenter WLST Command Reference.
You can also use WLST to list or edit the current connection details.
For information on how to run WLST commands, see Running Oracle WebLogic Scripting Tool (WLST) Commands in Administering Oracle WebCenter Portal.
Parent topic: Registering the Pagelet Producer
Configuring Search Services
You can configure Oracle Secure Enterprise Search (Oracle SES) services and crawlers using procedures in the Managing Oracle Secure Enterprise Search in WebCenter Portal section in Administering Oracle WebCenter Portal.
Note:
WebCenter Portal provides basic integration with Elasticsearch. The configuration of a robust highly-available Elasticsearch deployment with the WebCenter Enterprise Deployment topology has not been fully tested as of this release. For basic configuration, see Managing Search in WebCenter Portal with Elasticsearch in Administering Oracle WebCenter Portal. Significant additional analysis and configuration related to clustering, HA, and security/accessibility is needed for use a WebCenter Enterprise Deployment Guide topology.Ensure that:
-
Oracle Secure Enterprise Search is registered with Oracle Internet Directory and the WebCenter Portal application is configured as an Oracle SES trusted entity, as described in the Managing Oracle Secure Enterprise Search in WebCenter Portal section in Administering Oracle WebCenter Portal.
-
Connection exists between the WebCenter Portal application and Oracle Secure Enterprise Search, as described in the Setting Up Oracle SES Connections section in Administering Oracle WebCenter Portal.
Add the following additional URL location paths for the wcpinternal.example.com
virtual host in the wcinternal_vh.conf
file, and then restart each OHS service.
<Location /rsscrawl>
WLSRequest ON
WebLogicCluster WCPHOST1:9001,WCPHOST2:9001
WLProxySSL OFF
WLProxySSLPassThrough OFF
</Location>
<Location /sesUserAuth>
WLSRequest ON
WebLogicCluster WCPHOST1:9001,WCPHOST2:9001
WLProxySSL OFF
WLProxySSLPassThrough OFF
</Location>
Parent topic: Configuring WebCenter Portal for External Services
Configuring Oracle WebCenter Portal Notifications for the SMTP Mail Server
In a WebCenter Portal Enterprise Deployment, if you choose to send notifications using mail, you must configure a connection to your corporate mail server and specify several unique parameters for the sent emails to appear correctly.
To ensure sufficient configuration for your mail server and business requirements, before completing this task, review Managing Mail in Administering Oracle WebCenter Portal for details on the required and optional configurations and parameters.
You can register a mail server using Fusion Middleware Control or WLST commands:
Parent topic: Configuring WebCenter Portal for External Services
Registering Mail Servers Using Fusion Middleware Control
For details on how to register a mail server using Fusion Middleware Control, see Registering Mail Servers Using Fusion Middleware Control in Administering Oracle WebCenter Portal.
Configuring the Content Server Connection
Oracle WebCenter Portal supports content management and storage capabilities, including file upload, file and folder creation and management, file check out, and versioning.
To provide content integration in WebCenter Portal, you must configure at least one WebCenter Content Server connection and mark it as the default connection (sometimes referred to as the active or primary connection). For more information on the requirements, see the Oracle WebCenter Content Server Requirements section in the Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Portal guide.
Additional configuration is needed to assure high-availablity for the WebCenter Portal Content Manager component file uploads.
- Registering Oracle WebCenter Content with the WebCenter Portal Application
Provides steps to register Oracle WebCenter Content Server with the WebCenter Portal application. - Configure WebCenter Portal Content Manager MBeans for High Availability
The WebCenter Portal Content Manager component and task flows utilize the WebCenter Content remote UI (RUI) APIs to provide content integration capabilities. While these libraries are directly included with the Portal installation, specific MBean configuration settings need to be modified for fail-safe runtime within a High Availability architecture.
Parent topic: Configuring WebCenter Portal for External Services
Registering Oracle WebCenter Content with the WebCenter Portal Application
Provides steps to register Oracle WebCenter Content Server with the WebCenter Portal application.
Note:
For more information about Content Server registration, see the Configuring Back-end Data Repositories for Tools and Services section in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter Portal.
Parent topic: Configuring the Content Server Connection
Configure WebCenter Portal Content Manager MBeans for High Availability
The WebCenter Portal Content Manager component and task flows utilize the WebCenter Content remote UI (RUI) APIs to provide content integration capabilities. While these libraries are directly included with the Portal installation, specific MBean configuration settings need to be modified for fail-safe runtime within a High Availability architecture.
Modify and validate the following attributes for the ADFConfig:WccAdfConfiguration
and ADFConfig:ADFcConfig
application-defined MBeans on the webcenter application:
-
Application: webcenter:
-
ADFConfig: ADFcConfig
-
AdfScopeHaSupport
-
-
ADFConfig:WccAdfConfiguration:
-
ClusterCompatible
-
TemporayDirectory
-
-
The upload temporary directory specified must be configured to a common directory location on a shared disk volume across all portal nodes when the portal is clustered in a High Availability environment.
Parent topic: Configuring the Content Server Connection
Restarting the Portal Managed Servers to Activate all Service Configuration Changes
If the optional restarts in the sections above have been deferred, restart the portal managed servers now.
Parent topic: Configuring WebCenter Portal for External Services
Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.
For information about backing up your configuration, see Performing Backups and Recoveries for an Enterprise Deployment.
Parent topic: Extending the Domain with Oracle WebCenter Portal