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

Configuring High Availability for Identity Management Components 8-201 d. Create a new JMS Server for UMS, for example, UMSJMSServer_n. Use the UMSJMSFileStore_n for this JMSServer. Target the UMSJMSServer_n Server to the recently created managed server WLS_SOAn. e. Create a new persistence store for the new OIMJMSServer, for example, OIMJMSFileStore_n. Specify the path for the store. This should be a directory on shared storage. ORACLE_BASE admindomain_namecluster_namejmsOIMJMSFileStore_n f. Create a new JMS Server for OIM, for example, OIMJMSServer_n. Use the OIMJMSFileStore_n for this JMSServer. Target the OIMJMSServer_n Server to the recently created Managed Server WLS_OIMn. 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. Click the SubDeployments tab. The subdeployment module for SOAJMS appears.

h. Click the SOAJMSServerXXXXXX subdeployment. Add the new JMS Server

for SOA called SOAJMSServer_n to this subdeployment. Click Save. i. Update the SubDeployment targets for the 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 Note: This directory must exist before the managed server is started or the start operation fails. You can also assign SOAJMSFileStore_n as 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. You can also assign SOAJMSFileStore_n as store for the new OIM 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. 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