Select Environment - Servers from the Administration Console. From the Change Center menu, click Lock and Edit. Select Clone.

Managing Enterprise Deployments 20-17

6. Click Apply.

7. Click Coherence tab.

Set Local Port to a unique value on the host. 8. Click Apply. You can now start the Oracle Access Manager server. In order for the server to be used, however, you must inform all WebGates of its existence. You do this as follows: 1. Log in to the OAM console at http:admin.mycompany.comoamconsole as the oamadmin user.

2. Click the System Configuration tab

3. Expand Agents - OAM Agents - 10g Agents.

4. Double click the WebGate you want to change. 5. Add the new server to either the Primary or Secondary server list by clicking +. 6. Select the server name from the list.

7. Click Apply.

20.3.1.2.4 Scaling Up Oracle Identity Manager Adding Managed Servers to Existing Nodes In

this case, you already have a node that runs a Managed Server configured with SOA components. The node contains a Middleware home, an Oracle home SOA and a domain directory for existing Managed Servers. You can use the existing installations the Middleware home, and domain directories for creating new WLS_OIM and WLS_SOA servers. There is no need to install the Oracle Identity Manager and Oracle SOA Suite binaries in a new location, or to run pack and unpack. Follow these steps for scaling up the topology: 1. Using the Administration Console, clone either the WLS_OIM1 or the WLS_SOA1 into a new Managed Server. The source Managed Server to clone should be one that already exists on the node where you want to run the new Managed Server. To clone a Managed Server:

a. Select Environment - Servers from the Administration Console.

b. From the Change Center menu, click Lock and Edit.

c. Select the Managed Server that you want to clone for example, WLS_OIM1 or WLS_SOA1.

d. Select Clone.

Name the new Managed Server WLS_OIMn or WLS_SOAn, where n is a number to identify the new Managed Server. The rest of the steps assume that you are adding a new server to OIMHOST1, which is already running WLS_SOA1 and WLS_OIM1. 2. For the listen address, assign the host name or IP address to use for this new Managed Server. If you are planning to use server migration as recommended for this server, this should be the VIP also called a floating IP to enable it to move to another node. The VIP should be different from the one used by the Managed Server that is already running. 3. Create JMS Servers for SOA, Oracle Identity Manager, UMS, and BPM on the new Managed Server. 20-18 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 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 2.4, Shared Storage and Recommended Directory Structure. ORACLE_BASE adminDOMAIN_NAMEcluster_namejmsSOAJMSFileStore_N b. Create a new JMS server for SOA, for example, SOAJMSServer_auto_N. Use the SOAJMSFileStore_N for this JMSServer. Target the SOAJMSServer_ auto_N server to the recently created Managed Server WLS_SOAn. c. Create a new JMS server for BPM, for example, BPMJMSServer_auto_N. Use the BPMJMSServer_auto_N for this JMSServer. Target the BPMJMSServer_ auto_N server to the recently created Managed Server WLS_SOAn. d. Create a new persistence store for the new BPMJMSServer for example, BPMJMSFileStore_N. Specify the path for the store. This should be a directory on shared storage, as recommended in Section 2.4, Shared Storage and Recommended Directory Structure. e. Create a new persistence store for the new UMSJMSServer, for example, UMSJMSFileStore_N Specify the path for the store. This should be a directory on shared storage as recommended in Section 2.4, Shared Storage and Recommended Directory Structure. ORACLE_BASE admindomain_namecluster_namejmsUMSJMSFileStore_N. f. 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. g. 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 as recommended in Section 2.4, Shared Storage and Recommended Directory Structure. ORACLE_BASEadmindomain_namecluster_namejmsOIMJMSFileStore_N Note: This directory must exist before the Managed Server is started or the start operation fails. 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 Oracle Identity Manager JMS Servers. For the purpose of clarity and isolation, individual persistent stores are used in the following steps. Managing Enterprise Deployments 20-19 h. Create a new JMS Server for Oracle Identity Manager, for example, OIMJMSServer_N. Use the OIMJMSFileStore_N for this JMSServer. Target the OIMJMSServer_N server to the recently created Managed Server WLS_ OIMn. i. 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. Click the SOAJMSServerXXXXXX subdeployment. Add the new JMS Server for SOA called SOAJMSServer_N to this subdeployment. Click Save. j. 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 page for UMSJMSSystemResource appears. Click 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. k. Update the SubDeployment targets for the BPMJMSSystemResource 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. Note: This subdeployment module name is a random name in the form of SOAJMSServerXXXXXX resulting from the Configuration 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 UCMJMSServerXXXXXX resulting from the Configuration 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 BPMJMSServerXXXXXX resulting from the Configuration Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_SOA2. 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