Converting Discussions from Multicast to Unicast

6-72 Oracle Fusion Middleware High Availability Guide 6. Enable Debug. Check the server logs for any unusual messages on managed server startup. In particular, if the managed server is unable to locate other members of the cluster. The server logs are located in the DOMAIN_HOMEserversSERVER_NAMElogs directory. For further debugging, enable the flags DebugCluster, DebugClusterAnnouncements, DebugFailOver, DebugReplication, and DebugReplicationDetails. Each flag can be enabled with the weblogic.Admin utility: java weblogic.Admin -url Adminhost:7001 -username username -password password SET -type ServerDebug -property DebugCluster true

6.4.20.3 Troubleshooting Lost Changes to Policies

Policies are refreshed at an interval defined in jps-config.xml by the variable oracle.security.jps.ldap.policystore.refresh.interval. By default, this interval is ten minutes. If a server is lost, requests are routed to another server in the cluster where the original policies are cached. Recent policy changes that occurred since the last refresh may appear to be lost. For example, roles created immediately before the failover may be seen as unavailable. The policies are still in the back-end policy store. Refresh the cache to restore policy information. Re-try after a few minutes, or log in and log out of the application to force a policy cache refresh.

6.4.20.4 Troubleshooting JOC Configuration

If attempts to start a Managed Server that uses the Java Object Cache, such as OWSM or WebCenter Spaces Managed Servers, fail, and the following errors appear in the logs: J2EE JOC-058 distributed cache initialization failure J2EE JOC-043 base exception: J2EE JOC-803 unexpected EOF during read. Another process is using the same port that JOC is attempting to obtain. To solve this problem, either stop that process, or reconfigure JOC for this cluster to use another port in the recommended port range.

6.4.21 Converting Discussions from Multicast to Unicast

To convert Discussions from multicast to unicast: Step 1: Add the startup parameters To add the relevant startup parameters:

1. In the Oracle WebLogic Server Administration Console, select Servers, WC_

Collaboration1 , Configuration, and then Server Start. 2. In the Arguments box, add the following: -Dtangosol.coherence.wka1=Host1 -Dtangosol.coherence.wka2=Host2 -Dtangosol.coherence.localhost=Host1 -Dtangosol.coherence.wka1.port=8088 -Dtangosol.coherence.wka2.port=8088 Where Host1 is where WC_Collaboration1 is running. 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