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. Select Environment - Cluster from the Administration Console. In the Change Center, clic

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-139 7. For the listen address, assign the virtual host name to use for this new managed server. If you are planning to use server migration as recommended for this server, this virtual host name will enable it to move to another node. The virtual host name should be different from the one used by the managed server that is already running. 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 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 SOAHOSTnVHN1.

g. Click Save.

h. Save and activate the changes. The changes will not take effect until the managed server is restarted. 8. Update the cluster address to include the new server:

a. Select Environment - Cluster from the Administration Console.

b. Click on the SOA_Cluster server. The Settings Screen for the SOA_Cluster appears.

c. In the Change Center, click Lock Edit.

d. Add the new servers address and port to the Cluster Address field. For example: SOAHOST1VHN1:8001,SOAHOST2VHN1:8001,SOAHOSTNVHN1:8001 9. Create JMS servers for SOA, BPM if applicable, and UMS on the new managed server. a. Use the Oracle WebLogic Server Administration Console to create a new persistent store for the new SOAJMSServer and name it, for example, SOAJMSFileStore_N. Specify the path for the store. This should be a directory on shared storage as recommended in Section 5.13.1.3, Shared Storage Prerequisites. ORACLE_BASE admindomain_namecluster_namejmsSOAJMSFileStore _N b. Create a new JMS Server for SOA, for example, SOAJMSServer_N. Use the SOAJMSFileStore_N for this JMSServer. Target the SOAJMSServer_N Server to the recently created managed server WLS_SOAn. c. Create a new persistence store for the new UMSJMSServer, and name it, for example, UMSJMSFileStore_N. Specify the path for the store. This should be a Note: This directory must exist before the managed server is started or the start operation fails. 5-140 Oracle Fusion Middleware High Availability Guide directory on shared storage as recommended in Section 5.13.1.3, Shared Storage Prerequisites. ORACLE_BASE admindomain_namecluster_namejmsUMSJMSFileStore _N d. Create a new JMS Server for UMS: for example, UMSJMSServer_N. Use the UMSJMSFileStore_N for this JMS Server. Target the UMSJMSServer_N Server to the recently created managed server WLS_SOAn. e. ONLY FOR BPM Systems Create a new persistence store for the new BPMJMSServer, and name it, for example, BPMJMSFileStore_N. Specify the path for the store. This should be a directory on shared storage as recommended in Section 5.13.1.3, Shared Storage Prerequisites. ORACLE_BASE admindomain_namecluster_namejmsBPMJMSFileStore _N f. ONLY FOR BPM Systems Create a new JMS Server for BPM: for example, BPMJMSServer_N. Use the BPMJMSFileStore_N for this JMS Server. Target the BPMJMSServer_N Server to the recently created managed server WLS_ SOAn. g. Update the SubDeployment targets for the SOA JMS Module to include the recently created SOA JMS Server. To do this, expand the Services node and then expand the Messaging node. Choose JMS Modules from the Domain Structure window of the Oracle WebLogic Server Administration Console. The JMS Modules page appears. Click SOAJMSModule represented as a hyperlink in the Names column of the table. The Settings page for SOAJMSModule appears. Open the SubDeployments tab. The subdeployment module for SOAJMS appears. Note: This directory must exist before the managed server is started or the start operation fails. Note: It is also possible to assign SOAJMSFileStore_N as the store for the new UMS JMS Servers. For the purpose of clarity and isolation, individual persistent stores are used in the following steps. Note: This directory must exist before the managed server is started or the start operation fails. Note: It is also possible to assign SOAJMSFileStore_N as the store for the new BPM JMS Servers. For the purpose of clarity and isolation, individual persistent stores are used in the following steps. Note: This subdeployment module name is a random name in the form of SOAJMSServerXXXXXX resulting from the Config Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_ SOA2. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-141 Click the SOAJMSServerXXXXXX subdeployment. Add the new JMS Server for SOA called SOAJMSServer_N to this subdeployment. Click Save. h. Update the SubDeployment targets for UMSJMSSystemResource to include the recently created UMS JMS Server. To do this, expand the Services node and then expand the Messaging node. Choose JMS Modules from the Domain Structure window of the Oracle WebLogic Server Administration Console. The JMS Modules page appears. Click UMSJMSSystemResource represented as a hyperlink in the Names column of the table. The Settings page for UMSJMSSystemResource appears. Open the SubDeployments tab. The subdeployment module for UMSJMS appears Click the UMSJMSServerXXXXXX subdeployment. Add the new JMS Server for UMS called UMSJMSServer_N to this subdeployment. Click Save. i. ONLY FOR BPM Systems Update the SubDeployment Targets for BPMJMSModule to include the recently created BPM JMS Server. To do this, expand the Services node and then expand the Messaging node. Choose JMS Modules from the Domain Structure window of the Oracle WebLogic Server Administration Console. The JMS Modules page appears. Click BPMJMSSystemResource represented as a hyperlink in the Names column of the table. The Settings page for BPMJMSSystemResource appears. Click the SubDeployments tab. The subdeployment module for BPMJMS appears. Click the BPMJMSXXXXXX subdeployment. Add the new JMS Server for BPM called BPMJMSServer_N to this subdeployment. Click Save. 10. Run the pack command on SOAHOST1 to create a template pack as follows: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=MW_HOMEuser_ projectsdomainssoadomain -template=soadomaintemplateScale.jar -template_name=soa_domain_templateScale Run the following command on SOAHOST1 to copy the template file created to SOAHOSTN: SOAHOST1 scp soadomaintemplateScale.jar oracleSOAHOSTN: ORACLE_ BASE productfmwsoacommonbin Run the unpack command on SOAHOSTN to unpack the template in the managed server domain directory as follows: SOAHOSTN cd ORACLE_BASEproductfmwsoacommonbin SOAHOSTN .unpack.sh -domain=ORACLE_BASEproductfmwuser_ projectsdomainssoadomain -template=soadomaintemplateScale.jar Note: This subdeployment module is a random name in the form of UMSJMSServerXXXXXX resulting from the Config Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_SOA2. Note: This subdeployment module is a random name in the form of BPMJMSServerXXXXXX resulting from the Config Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_SOA2. 5-142 Oracle Fusion Middleware High Availability Guide 11. Configure Oracle Coherence for deploying composites, as described in Section 5.13.8, Configuring Oracle Coherence for Deploying Composites. 12. Configure TX persistent store for the new server. This should be a location visible from other nodes as indicated in the recommendations about shared storage. From the Administration Console, select Server_name Services tab. Under Default Store , in Directory, enter the path to the folder where you want the default persistent store to store its data files. 13. Disable host name verification for the new managed server. Before starting and verifying the WLS_SOAN managed server, you must disable host name verification. You can re-enable it after you have configured server certificates for the communication between the Oracle WebLogic Administration Server and the Node Manager in SOAHOSTn. If the source server from which the new one has been cloned had already disabled hostname verification, these steps are not required the hostname verification setting is propagated to the cloned server. To disable host name verification:

a. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server