In the Change Center, click Lock Edit. Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page is displaye Click Save.

Configuring High Availability for Oracle ADF and WebCenter Applications 6-29

a. Select Environment Servers from the Administration Console.

b. Select the managed server that you want to clone.

c. Select Clone.

Name the new managed server WLS_ADFn, 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. 3. Ensure that the port number for this managed server is available on this node. 4. Reconfigure the Oracle HTTP Server module with the new member in the cluster. See Section 6.2.9.5, Configuring Oracle HTTP Server for the Administration Server and Oracle WebCenter Managed Servers.

6.2.10.2 Scaling Out the Topology Adding Managed Servers to New Nodes

In scaling out your topology, you add new managed servers configured with Oracle ADF 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 ADF applications. ■ ADF managed servers are clustered and the new managed server will also be part of that cluster. ■ The new node can access the existing home directories for WebLogic Server. You use the existing installations in shared storage for creating a new managed server. There is no need to install WebLogic Server 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, and ensure that the new

node has access to this directory, just like the rest of the nodes in the domain.

2. 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 of the node that is being used for scale out. 6. Use the Oracle WebLogic Server Administration Console to clone WLS_ADF1 into a new managed server. Name it WLS_ADFn, 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.

6-30 Oracle Fusion Middleware High Availability Guide d. Click Servers. The Summary of Servers page is displayed. e. Select the managed server whose listen address you want to update in the Names column of the table. The Setting page for that managed server is displayed. f. Set the Listen Address to APPHOSTn where APPHOSTn is the DNS name of your new machine.

g. Click Save.

h. Save and activate the changes. The changes will not take effect until the managed server is restarted. 8. Run the pack command on APPHOST1 to create a template pack as follows: APPHOST1 cd ORACLE_COMMON_HOMEcommonbin APPHOST1 .pack.sh -managed=true -domain=MW_HOMEuser_projectsdomains adfdomain -template=adfdomaintemplateScale.jar -template_name=adf_domain_templateScale Run the following command on APPHOST1 to copy the template file created to APPHOSTn: APPHOST1 scp adfdomaintemplateScale.jar oracleAPPHOSTN: ORACLE_COMMON_HOME commonbin Run the unpack command on APPHOSTn to unpack the template in the managed server domain directory as follows: APPHOSTn cd ORACLE_COMMON_HOMEcommonbin APPHOSTN .unpack.sh -domain=ORACLE_BASEproductfmwuser_projectsdomainsadfdomain -template=adfdomaintemplateScale.jar 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: APPHOSTn WL_HOMEserverbinstartNodeManager new_node_ip 10. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Shut down all the existing managed servers in the cluster. b. Ensure that the newly created managed server is running. c. Access the application on the newly created managed server. The application should be functional.

6.3 Oracle WebCenter and High Availability Concepts