Extending the Domain for WebCenter Components 6-11
Enter Cluster Name : Spaces_Cluster .
Enter Discover Port : 9988 .
Enter Distribute Mode true|false true : true .
Do you want to exclude any servers from JOC configuration yn n n
The script can also be used to perform the following JOC configurations:
■
Configure JOC for all specified managed servers. Enter n when the script prompts whether you want to specify a cluster name, and
also specify the managed server and discover port, when prompted. For example: Do you want to specify a cluster name yn yn
Enter Managed Server and Discover Port eg WC_Spaces1:9988, WC_Spaces2:9988 : WC_Spaces1:9988,WC_Spaces2:9988
■
Exclude JOC configuration for some managed servers. The script allows you to specify the list of managed servers for which the JOC
configuration DistributeMode will be set to ’false’. Enter y when the script prompts whether you want to exclude any servers from JOC configuration, and
enter the managed server names to be excluded, when prompted. For example:
Do you want to exclude any servers from JOC configuration yn ny Exclude Managed Server List eg Server1,Server2 : WC_Spaces1,WC_Spaces3
■
Disable the distribution mode for all managed servers. The script allows you to disable the distribution to all the managed servers for a
specified cluster. Specify ’false’ when the script prompts for the distribution mode. By default, the distribution mode is set to ’true’.
Verify JOC configuration using the CacheWatcher utility. See Oracle Fusion Middleware High Availability Guide.
You can configure the Java Object Cache JOC using the HA Power Tools tab in the Oracle WebLogic Administration Console as described in the Oracle Fusion Middleware
High Availability Guide.
6.14 Converting Discussions Forum from Multicast to Unicast
To convert Discussions Forum from multicast to unicast, 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=WCHost1 -Dtangosol.coherence.wka2=WCHost2
-Dtangosol.coherence.localhost=WCHost1 -Dtangosol.coherence.wka1.port=8089 -Dtangosol.coherence.wka2.port=8089 -Dtangosol.coherence.localport=8089
Where WCHost1 is where WC_Collaboration1 is running.
Port 8089 is a port reserved for WebCenter Coherence communications.
3.
Repeat steps 1 and 2 for WC_Collaboration2, swapping WCHost1 for WCHost2 and WCHost2 for WCHost1.
6-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
4.
Restart the WC_Collaboration servers.
6.15 Configuring Clustering for Discussions Server
If this is a Unicast cluster, first ensure that the steps in Section 6.14, Converting
Discussions Forum from Multicast to Unicast are performed first.
Ensure that all members of the Discussions Server cluster can communicate with each other using the Discussions Server Administration Console:
1.
Login to each member of the cluster at: http:host:portowc_discussionsadmin
2. Go to Cache Settings.
Figure 6–1 Cache Settings Section
Discussions Server Administration Console
3. At the bottom of the page, in the Cache Features section, ensure that Clustering is
set to Enabled.
The top of the page should now list all members of the cluster.
4. Again, towards the end of the page, under the Cache Tools section, do Cluster
wide cache reset and the Cache warm up Task . Repeat the Cache warm up task
on all members of the cluster.
Figure 6–2 Cache Tools Section
Discussions Server Administration Console
Extending the Domain for WebCenter Components 6-13
6.16 Configuring the Analytics Collectors
The Analytics Collectors must be configured to communicate with WebCenter Spaces. Each Collector is configured to only communicate with the local WebCenter Spaces in
a 1-1 relationship.
6.16.1 Configure the Collectors
The Collectors do not need to be configured. By default they are listening on localhost. You must configure only the WebCenter Spaces clients to send their messages to
localhost.
6.16.2 Configure the WebCenter Spaces Servers
1.
Open the WLST shell: ORACLE_HOME
commonbinwlst.sh
2.
Connect to WLS Server: connectweblogic_admin_username, weblogic_admin_pwd, WCHOST1:9000
Note that you are connecting to the host and port of the Spaces Server.
3.
Create the Analytics Collector connection and make it the default connection: createAnalyticsCollectorConnectionwebcenter,HAConn1,isUnicast=1,
collectorHost=localhost,collectorPort=31314,isEnabled=1,timeout=30,default=1
4.
List the changes made: listDefaultAnalyticsCollectorConnectionwebcenter
6.17 Configuring Activity Graph
Activity Graph should run as a singleton. In a cluster environment, all but one instance of Activity Graph should be disabled.
To disable Activity Graph:
1.
Log in to the Administration Console.
2.
Shut down the WC_Spaces and WC_Utilities servers.
3. Select Deployments
4. Click Lock Edit.
5.
Alter the targets for these three deployments:
■
activitygraph-engines 11.1.1.4.0
■
oracle.webcenter.activitygraph.enginelib 11.1.1,11.1.1
■
oracle.webcenter.activitygraph.lib 11.1.1,11.1.1
6.
For each of the deployments above:
a.
Select the deployment.
Note: Clustered Analytics Collectors are not supported for collecting
WebCenter events.
6-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
b. Select the Targets tab.
