In the Change Center, click Lock Edit. Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page appears. Set the Listen Address to WCHOSTn where WCHOSTn is the DNS name of Click Save.

Managing the Topology 11-15

11.4.2.2 Scaling Out WebCenter

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 need to run pack and unpack to create a managed server domain. ■ WC_Spaces and WC_Utilities servers must be either both scaled out on the new node, or both not scaled out. This is because of the local affinity between WebCenter Spaces and the Analytics application. To scale 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 as the rest of the nodes in the domain do.

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_version 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.

5. Update the machines Node Managers address to map the IP address 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.

c. Expand the Environment node in the Domain Structure window.

d. Click Servers. The Summary of Servers page appears.

e. Select the managed server with the listen address you want to update in the Names column of the table. The Setting page for that managed server appears.

f. Set the Listen Address to WCHOSTn where WCHOSTn is the DNS name of

your new machine. 11-16 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

g. Click Save.

h. Save and activate the changes. The changes do not take effect until the managed server is restarted. 8. Run the pack command on SOAHOST1 to create a template pack and unpack onto WCHOSTn. These steps are documented in Section 6.7, Propagating the Domain Configuration to SOAHOST2, WCHOST1, and WCHOST2 Using the unpack Utility. 9. Start the Node Manager on the new node. To start the Node Manager, use the installation in shared storage from the existing nodes, and start Node Manager by passing the host name of the new node as a parameter as follows: WCHOSTn WL_HOMEserverbinstartNodeManager new_node_ip 10. If this is a new Collaboration managed server: a. Ensure that you have followed the steps in Section 6.15, Configuring Clustering for Discussions Server, to configure clustering for the new Discussions Server. b. Ensure also that the steps in Section 6.14, Converting Discussions Forum from Multicast to Unicast are performed, using the hostname of the new host for the coherence.localhost parameter. 11. If this is a new Utilities managed server, ensure that Activity Graph is disabled by following the steps in Section 6.17, Configuring Activity Graph. Ensure also that the steps for configuring a new Analytics Collector in Section 6.16, Configuring the Analytics Collectors have been followed for the Utilities and the local Spaces Server. 12. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Ensure that the newly created managed server, WLS_SOAn, is running. b. Access the application on the load balancer https:soa.mycompany.comsoa-infra. The application should be functional.

11.5 Performing Backups and Recoveries