Click the OIMMSServerXXXXXX subdeployment. Add the new JMS Server

8-202 Oracle Fusion Middleware High Availability Guide page for UMSJMSSystemResource appears. Click the SubDeployments tab. The subdeployment module for UMSJMS appears.

j. Click the UMSJMSServerXXXXXX subdeployment. Add the new JMS Server

for UMS called UMSJMSServer_n to this subdeployment. Click Save. k. Update the SubDeployment targets for OIMJMSModule to include the recently created OIM 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 OIMJMSSystemResource represented as a hyperlink in the Names column of the table. The Settings page for OIMJMSSystemResource appears. Click the SubDeployments tab. The subdeployment module for OIMJMS appears.

l. Click the OIMMSServerXXXXXX subdeployment. Add the new JMS Server

for OIM called OIMJMSServer_n to this subdeployment. Click Save. 9. 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 10. Configure Oracle Coherence for deploying composites, as described in Section 5.13.8, Configuring Oracle Coherence for Deploying Composites. Note: This subdeployment module name is a random name in the form of UCMJMSServerXXXXXX resulting from the Config Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_ SOA2. Note: This subdeployment module name is a random name in the form of OIMJMSServerXXXXXX resulting from the Config Wizard JMS configuration for the first two servers WLS_OIM1 and WLS_ OIM2. Configuring High Availability for Identity Management Components 8-203 11. Configure the transaction persistent store for the new server. This should be a shared storage location visible from other nodes. 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. 12. 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 settings is propagated to the cloned server. To disable host name verification: a. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Administration Console.

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