Configuring a Cluster for Oracle WebCenter Portal Applications

Configuring High Availability for Oracle ADF and WebCenter Applications 6-73 To use a port other than 8088 for WebCenter Coherence communications, specify a different port number using the -Dtangosol.coherence.wka1.port and -Dtangosol.coherence.wka2.port arguments in the example above. 3. Repeat steps 1 and 2 for WC_Collaboration2, setting the localhost parameter to Host2 instead. 4. Restart the WC_Collaboration1 servers. Step 2: Validate the changes To validate the changes: 1. Log on to the Discussions Forum Administration panel.

2. Select Cache Settings in the left pane.

3. At the bottom of the screen, ensure that Clustering is set to enabled.

4. Repeat steps 1 through 3 for all members of the cluster. As servers join the cluster they appear at the top of the screen.

6.5 Configuring High Availability for Oracle WebCenter Portal Applications

Oracle WebCenter Portal Applications are deployed on servers and clusters which have been provisioned with the necessary libraries. This provisioning occurs by applying a domain template to an existing WebCenter domain. The extension can be done only once per domain. This means that any Oracle WebCenter Portal Application Servers must be either created at one time or as clones of existing Oracle WebCenter Portal Application Servers.

6.5.1 Configuring a Cluster for Oracle WebCenter Portal Applications

The following are the necessary steps for configuring a cluster for deploying Oracle WebCenter Portal Applications:

1. Start Oracle Fusion Middleware Configuration Wizard from the ORACLE_

HOMEcommonbin directory using the following command: APPHOST1 .config.sh

2. In the Welcome screen, select Extend an Existing WebLogic Domain, and click

Next . 3. In the next screen, select your Weblogic Domain Directory.

4. In the next screen, choose Extend my Domain using an existing Extension

template . 5. Choose either of these two templates, depending on whether you are creating Custom Applications or Custom Producers: ■ For Custom applications: WC_ORACLE_HOMEcommontemplatesapplicationsoracle.wc_custom_portal_ template_11.1.1.jar ■ For Custom Producers: WC_ORACLE_HOMEcommontemplatesapplicationsoracle.wc_custom_services_ producer_template_11.1.1.jar 6-74 Oracle Fusion Middleware High Availability Guide 6. Configure the new data sources Custom Portal Activities, Custom Portal Webcenter, Custom Portal MDS as Oracle RAC by selecting all the data sources and then checking the RAC datasources checkbox. The Custom Apps use existing schemas. 7. Enter the Database connection information and proceed to check the status of the data sources.

8. In the Options Configuration Screen, select Managed Servers, Clusters and

Machines . 9. In the Managed Servers screen: ■ A managed server named WC_CustomPortal should appear. Rename this server to WC_CustomPortal1. ■ Click Add to create a new managed server and name it WC_CustomPortal2. Set the Listen Port to be the same as that of WC_CustomPortal1. 10. In the Configure Clusters screen, add a Cluster named WC_CustomPortalCluster. 11. In the Assign Servers to Clusters screen, add the two newly created servers to the Cluster. 12. In the Assign Server to Machines screen, place each of the two servers on separate machines.

13. Click Extend and then Done to Extend the Domain.

When you complete these steps, you can start the managed server using Oracle WebLogic Server Administration Console, and you can then deploy Oracle WebCenter Portal Applications. Deploy these Oracle WebCenter Portal Applications to the Cluster target, not the managed server target.

6.5.2 Adding More Oracle WebCenter Portal Applications Servers