Configuring Activity Graph Click Start.

6-66 Oracle Fusion Middleware High Availability Guide Application Replication Applications must also have replication enabled. Oracle WebLogic Server allows several types of persistent stores for replication. For more information on persistent stores, see Oracle Fusion Middleware Using Clusters for Oracle WebLogic Server. For Oracle WebCenter, applications are enabled by default with the following setting in the weblogic.xml file: session-descriptor persistent-store-typereplicated_if_clusteredpersistent-store-type session-descriptor The replicated_if_clustered setting disables replication for stand-alone application environments, and uses in-memory replication within a cluster environment. Ensure that any Oracle WebCenter Portal Application is configured for in-memory replication.

6.4.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. Because the Collectors are configured by default, the only task you must complete is to configure WebCenter Spaces.

6.4.16.1 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, APPHOST1:8888 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.4.17 Configuring Activity Graph

The Activity Graph Engines application should run as a singleton. In a cluster environment, all instances of the Activity Graph Engines application should be disabled except for one. To disable the Activity Graph Engines application: 1. Log on to the Oracle WebLogic Administration Console.

2. Select Deployments.

3. In the Change Center, click Lock Edit.

4. Alter the target for the activitygraph-engines 11.1.1.5.0 deployment as follows: Configuring High Availability for Oracle ADF and WebCenter Applications 6-67 a. Select the deployment. b. Select the Targets tab.

c. Click on Change Targets.

d. Ensure that the deployment is only targeted to Part of the Clusterone of the

Managed Servers .

e. Click OK to save the changes.

f. Click Activate All Changes.

Since Activity Graph is only running on one node, if this node is lost or the Managed Server is not available, then Activity Graph will be unavailable. In these cases, Activity Graph should be deployed on an active Managed Server. This process can also be automated by configuring Service Migration. For an example of configuring server migration for SOA Managed Servers, see Section 5.13.21, Configuring Server Migration for the WLS_SOA Servers.

6.4.18 Configuring Clustering for Discussion Server

If this is a Unicast cluster, first ensure that the steps in Section 6.4.21, Converting Discussions from Multicast to Unicast are performed first. Ensure that all members of the Discussion Server cluster can communicate with each other using the Discussion Server Administration Console: 1. Log into each member of the cluster at: http:host:portowc_discussionsadmin

2. Go to Cache Settings.

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.

6.4.19 Scaling the Topology

You can scale out and scale up an Oracle WebCenter topology. When you scale up the topology, you add new managed servers to nodes that are already running one or more managed servers. When you scale out the topology, you add new managed servers to new nodes.

6.4.19.1 Scaling Up the Topology Adding Managed Servers to Existing Nodes

In this case, you already have a node that runs a managed server configured with WebCenter components. The node contains a Middleware home and a WebCenter directory in shared storage. You can use the existing installations Middleware home, and domain directories for creating new Oracle WebCenter managed servers. There is no need to install WebCenter binaries in a new location, or to run pack and unpack. Running multiple managed servers on one node is only supported for the WC_Spaces servers and the WC_Portlet servers. Follow these steps for scaling up the topology: