Propagating the Domain Configuration to WCHOST1 and WCHOST2 Using the unpack Utility Starting Node Manager on WCHOST1 and WCHOST2

9-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Click Next. 13. In the Assign Servers to Clusters screen, add the following. Do not modify the other assignments that appear in this screen; leave them as they are. ■ UCM_Cluster – WC_UCM1 – WC_UCM2 Click Next. 14. In the Configure Machines screen, click the Unix Machine tab and add the following two new machines: Leave all other fields to their default values. Click Next. 15. In the Assign Servers to Machines screen, assign servers to machines as follows: ■ Assign WC_UCM1 to WCHOST1. ■ Assign WC_UCM2 to WCHOST2. Click Next. 16. In the Target Deployments to Clusters or Servers screen, click Next. 17. In the Target Services to Clusters or Servers screen, click Next. 18. In the Configuration Summary screen, click Extend. 19. Click OK in the warning dialog about conflicts in ports for the domain. 20. In the Creating Domain screen, click Done. 21. Restart the Administration Server to make these changes to take effect. See Section 5.4, Restarting the Administration Server.

9.3 Propagating the Domain Configuration to WCHOST1 and WCHOST2 Using the unpack Utility

Perform these steps to propagate the domain configuration:

1. Run the following command on WCHOST1 to copy the template pack using the

following command: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmin domain_name aserverdomain_name -template=edgdomaintemplate.jar -template_ Table 9–2 Clusters Name Cluster Messaging Mode Multicast Address Multicast Port Cluster Address UCM_Cluster unicast na na Leave it empty. Table 9–3 Machines Name Node Manager Listen Address WCHOST1 WCHOST1 WCHOST2 WCHOST2 Installing and Configuring Oracle Universal Content Management 9-7 name=edgdomain_template 2. Run the unpack command on WCHOST1 to unpack the propagated template. WCHOST1 cd ORACLE_COMMON_HOMEcommonbin WCHOST1 .unpack.sh -domain=ORACLE_BASEadmindomain_name mserverdomain_name -template=edgdomaintemplate.jar -app_dir=ORACLE_BASE admindomain_namemserverapplications 3. Repeat steps 1 and 2 for WCHOST2.

9.4 Starting Node Manager on WCHOST1 and WCHOST2

Perform these steps to start Node Manager on WCHOST1 and WCHOST2 if Node Manager has not started already: 1. On each server, run the setNMProps.sh script, which is located in the ORACLE_ COMMON_HOMEcommonbin directory, to set the StartScriptEnabled property to true before starting Node Manager: WCHOSTn cd ORACLE_COMMON_HOMEcommonbin WCHOSTn .setNMProps.sh 2. Run the following commands on both WCHOST1 and WCHOST2 to start Node Manager: WCHOSTn cd WL_HOMEserverbin WCHOSTn .startNodeManager.sh Note: Make sure to run the unpack command from the ORACLE_ COMMON_HOMEcommonbin directory, not from WL_ HOMEcommonbin. Note: The ORACLE_BASEadmindomain_namemserver directory must exist before running unpack. In addition, the ORACLE_ BASEadmindomain_namemserverapplications must be empty. Note: You must use the StartScriptEnabled property to avoid class loading failures and other problems. Note: If the Oracle UCM server is sharing the MW_HOME in a local or shared storage with SOA, as suggested in the shared storage configuration described in Chapter 2, Database and Environment Preconfiguration, it is not required to run setNMProps.sh again. In this case, Node Manager has already been configured to use a start script. 9-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

9.5 Restarting the Administration Server