Select Environment - Servers from the Administration Console. Select Clone.

Configuring High Availability for Identity Management Components 8-195 Although this exception is received, the user is created fine.

8.9.3.19 Scaling Up and Scaling Out the Oracle Identity Manager Topology

You can scale out or scale up the Oracle Identity Manager high availability topology. When you scale up the topology, you add new managed servers to nodes that are already running one or more managed servers. When you scale out the topology, you add new managed servers to new nodes.

8.9.3.19.1 Scaling Up Oracle Identity Manager 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 OIM and SOA 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. Select the managed server that you want to clone for example, WLS_OIM1 or WLS_SOA1.

c. Select Clone.

d. Name the new managed server WLS_OIMn or WLS_SOAn, where n is a number to identity 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 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, OIM, BPM, 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. ORACLE_BASE admindomain_namecluster_namejms Note: This directory must exist before the managed server is started or the start operation fails. 8-196 Oracle Fusion Middleware High Availability Guide 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, for example, UMSJMSFileStore_n Specify the path for the store. This should be a directory on shared storage. ORACLE_BASE admindomain_namecluster_namejmsUMSJMSFileStore_n 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. 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. Configuring High Availability for Identity Management Components 8-197

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