Select WC_Spaces1, WC_Spaces2, WC_Portlet1 and WC_Portlet2. Click on Change Targets. Ensure that the deployment is only targeted to Part of the Clusterone of the Click OK to save the changes. Select Environment - Servers from the Administration Console. S

6-64 Oracle Fusion Middleware High Availability Guide Location rest Deny from all Location VirtualHost 3. Ensure that the new virtual hosts webtier-pageletproducer and webtier-spaces have been added to DNS.

6.4.11.1.2 Additional Configuration In case of Virtual Host setup, you must configure

additional properties to use applications routed via virtual host. Sharepoint For single sign-on setups, including integration with Oracle Access Manager 10g or Oracle Access Manager 11g, see the Oracle® Fusion Middleware Administrators Guide for Oracle WebCenter. Oracle Pagelet Producer To access Oracle Pagelet Producer, use webtier-pageletproducer.example.com. For example, when you register Oracle Pagelet Producer in WebCenter Spaces or a custom application, it should use the virtual host for Oracle Pagelet Producer. Similarly, access to Oracle Pagelet Producer and any Pagelet Producer resources should be by means of Virtual Host. Please refer to Oracle Pagelet Producer documentation for additional information.

6.4.11.2 Validating Access through Oracle HTTP Server

Verify the URLS to ensure that appropriate routing and failover is working from the HTTP Server to Oracle WebCenter cluster. 1. Start WC_Spaces1, WC_Spaces2, WC_Portlet1 and WC_Portlet2 from the WebLogic Server Administration Console as follows: a. Access the Administration Console at the following URL http:APHHOST1console

b. Click Servers.

c. Open the Control tab.

d. Select WC_Spaces1, WC_Spaces2, WC_Portlet1 and WC_Portlet2.

e. Click Start.

f. Verify direct access to the managed servers using the following URLs: apphost1:8888webcenter apphost2:8888webcenter apphost1:8889portalTools apphost2:8889portalTools 2. While WC_Spaces2 and WC_Portlet2 are running, stop WC_Spaces1 and WC_ Portlet1 from Oracle WebLogic Server Administration Console. 3. Access the following URLs and verify the appropriate functionality: ■ WebHost1:7777webcenter ■ WebHost1:7777portalTools Configuring High Availability for Oracle ADF and WebCenter Applications 6-65 4. Start WC_Spaces1 and WC_Portlet1 from the WebLogic Server Administration Console. 5. Stop WC_Spaces2 and WC_Portlet2. 6. Access the following URLs and verify the appropriate functionality: ■ WebHost1:7777webcenter ■ WebHost1:7777portalTools

6.4.12 Configuring Manual Failover of the Administration Server to APPHOST2

For information about configuring the Administration Server for high availability, see Section 12.4, Transforming the Administration Server in an Existing Domain for Cold Failover Cluster.

6.4.13 Configuring the Java Object Cache

The Java Object Cache JOC should be configured among all the servers running WebCenter Spaces. This local cache is provided to increase the performance of Oracle WebCenter Spaces. For instructions on configuring the Java Object Cache among all the servers running Oracle WebCenter Spaces, see Section F.1, Configuring the Java Object Cache.

6.4.14 Configuring the Distributed Notifications for the MDS Repository

In high availability environments, Oracle recommends that you configure distributed notifications for the MDS repository. For instructions on configuring distributed notifications for the MDS repository, see Appendix G, Configuring Distributed Notifications for MDS.

6.4.15 Configuring Oracle WebCenter for Replication

Use the procedures in this section to configure Oracle WebCenter for replication. Clustering Requirement The application must be deployed to an Oracle WebLogic Cluster. This automatically establishes a replication channel for the multiple instances of the application. Oracle ADF Replication Oracle WebCenter relies on Oracle ADF components, therefore, essential that Oracle ADF is configured properly. The following tag should be present in the adf-config.xml file, one of the Application Resources, for a stateful application: adfc:adf-controller-config adfc:adf-scope-ha-supporttrueadfc:adf-scope-ha-support adfc:adf-controller-config In WebCenter applications, this is already been enabled by default. Note: In a Unicast cluster, the default replication channel is configured using the Listen address of each managed server. Therefore, the Listen address should be configured to be a specific IP address or host name, instead of being configured to listen on Any. 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: 6-68 Oracle Fusion Middleware High Availability Guide 1. Using the Administration Console, clone WC_Spaces1 or WC_Portlet1 into a new managed server. The source managed server to clone should be one that already exists on the node where you want to run the new managed server. To clone a managed server:

a. Select Environment - Servers from the Administration Console.

b. Select the managed server that you want to clone for example, WC_Spaces1 or WC_Portlet1.

c. Select Clone.

Name the new managed server SERVER_NAMEn, where n is a number to identify the new managed server. 2. For the listen address, assign the host name or IP to use for this new managed server. Ensure the port number for this managed server is available on this node. 3. Add the new managed server to the Java Object Cache Cluster see Section 6.4.13, Configuring the Java Object Cache . 4. Reconfigure the Oracle HTTP Server module with the new member in the cluster. See Section 6.4.11, Configuring Oracle HTTP Server for the Administration Server and Oracle WebCenter Managed Servers.

6.4.19.2 Scaling Out the Topology Adding Managed Servers to New Nodes

In scaling out your topology, you add new managed servers configured with Oracle WebCenter applications to new nodes. Before performing the steps in this section, check that you meet these requirements: ■ In your topology, there are existing nodes running managed servers configured with WebCenter applications. ■ The new node can access the existing home directories for WebLogic Server and Oracle WebCenter. You use the existing installations in shared storage for creating a new managed server. There is no need to install WebLogic Server or WebCenter binaries in a new location, although you must run pack and unpack to create a managed server domain. Follow these steps for scaling out the topology: 1. On the new node, mount the existing Middleware home, which should include the WebCenter installation and the domain directory, and ensure that the new node has access to this directory, just like the rest of the nodes in the domain. 2. To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute the following commands: WCHOSTn cd ORACLE_BASEproductfmwwc WCHOSTn .attachHome.sh -jreLoc ORACLE_BASEfmwjrockit_160_20_D1.0.1-2124 To update the Middleware home list, create or edit, if another WebLogic installation exists in the node the MW_HOMEbeabeahomelist file and add ORACLE_BASEproductfmw to it. 3. Log into the Oracle WebLogic Administration Console. 4. Create a new machine for the new node that will be used, and add the machine to the domain. Configuring High Availability for Oracle ADF and WebCenter Applications 6-69 5. Update the machines Node Managers address to map the IP of the node that is being used for scale out. 6. Use the Oracle WebLogic Server Administration Console to clone either WC_ Spaces1 or WC_Portlet1 or WC_Collaboration1 or WC_Utilities1 into a new managed server. Name it WLS_XXXn, where n is a number and assign it to the new machine. 7. For the listen address, assign the host name or IP to use for the new managed server. Perform these steps to set the managed server listen address: a. Log into the Oracle WebLogic Server Administration Console.

b. In the Change Center, click Lock Edit.