In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page appears. Select WLS_SOAn in the Names column of the table. The Settings page for

20-20 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management Click the BPMJMSServerXXXXXX subdeployment. Add the new JMS Server for BPM called BPMJMSServer_N to this subdeployment. Click Save. l. Update the SubDeployment targets for OIMJMSModule to include the recently created Oracle Identity Manager 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 OIMJMSModule 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. Click the OIMJMSServerXXXXXX subdeployment. Add the new JMS Server for Oracle Identity Manager called OIMJMSServer_N to this subdeployment. Click Save. 4. Configure Oracle Coherence, as described in Section 14.6.1, Updating the Coherence Configuration for the SOA Managed Server. 5. 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 the 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. 6. 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 host name verification, these steps are not required the host name 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.

c. Click Servers. The Summary of Servers page appears.

d. Select WLS_SOAn in the Names column of the table. The Settings page for the

server appears.

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

7. Repeat Steps 6a through 6h to disable host name verification for the WLS_OIMn Managed Servers. In Step d, select WLS_OIMn in the Names column of the table. Note: This subdeployment module name is a random name in the form of OIMJMSServerXXXXXX resulting from the Configuration Wizard JMS configuration for the first two servers WLS_OIM1 and WLS_OIM2. Managing Enterprise Deployments 20-21

8. Click Activate Changes from the Change Center menu.

9. Update the SOA host and port using Oracle Enterprise Manager Fusion Middleware Control. Follow these steps: a. Open a browser and go to Oracle Enterprise Manager Fusion Middleware Control at: http:admin.mycompany.comem b. Log in to Oracle Enterprise Manager Fusion Middleware Control using the Admin user credentials.

c. Navigate to Identity and Access, and then oim.