Select the Automatic Server Migration Enabled option. This enables the Node Click Save.

Configuring High Availability for Identity Management Components 8-199 Make sure the appropriate resources are available to run the managed servers concurrently during migration.

f. Select the Automatic Server Migration Enabled option. This enables the Node

Manager to start a failed server on the target node automatically.

g. Click Save.

h. Restart the Administration Server, managed servers, and Node Manager. i. Repeat the steps in this list for configuring server migration for the newly created WLS_OIMn managed server. 9. Test server migration for this new server. Follow these steps from the node where you added the new server: a. Stop the WLS_SOAn managed server. To do this, run kill -9 pid on the PID of the managed server. You can identify the PID of the node using ps -ef | grep WLS_SOAn. b. Watch the Node Manager Console: you should see a message indicating that WLS_SOA1s floating IP has been disabled. c. Wait for the Node Manager to try a second restart of WLS_SOAn. Node Manager waits for a fence period of 30 seconds before trying this restart. d. Once Node Manager restarts the server, stop it again. Now Node Manager should log a message indicating that the server will not be restarted again locally.

8.9.3.19.2 Scaling Out Oracle Identity Manager When you scale out the topology, you add

new managed servers configured with SOA to new nodes. Before performing the steps in this section, check that you meet these requirements: ■ There must be existing nodes running managed servers configured with SOA within the topology. ■ The new node can access the existing home directories for WebLogic Server and SOA. Use the existing installations in shared storage for creating a new WLS_SOA or WLS_WSM managed server. You do not need to install WebLogic Server or SOA binaries in a new location but you do need to run pack and unpack to bootstrap the domain configuration in the new node. Note: If there is no existing installation in shared storage, installing WebLogic Server and SOA in the new nodes is required as described in Section 5.13, Configuring High Availability for Oracle SOA Service Infrastructure and Component Service Engines. Note: When an ORACLE_HOME or WL_HOME is shared by multiple servers in different nodes, Oracle recommends keeping the Oracle Inventory and Middleware home list in those nodes updated for consistency in the installations and application of patches. To update the oraInventory in a node and attach an installation in a shared storage to it, use ORACLE_HOMEouibinattachHome.sh. To update the Middleware home list to add or remove a WL_HOME, edit the user_homebeabeahomelist file. See the following steps. 8-200 Oracle Fusion Middleware High Availability Guide Follow these steps for scaling out the topology: 1. On the new node, mount the existing Middleware home, which should include the SOA installation and the domain directory, and ensure that the new node has access to this directory, just like the rest of the nodes in the domain. 2. To attach ORACLE_HOME in shared storage to the local Oracle Inventory, execute the following commands: SOAHOSTncd ORACLE_BASEproductfmwsoa SOAHOSTn.attachHome.sh -jreLoc ORACLE_BASEfmwjrockit_160_17_R28.0.0-655 To update the Middleware home list, create or edit, if another WebLogic installation exists in the node the MW_HOMEbeabeahomelist file and add ORACLE_BASEproductfmw to it. 3. Log in to the Oracle WebLogic Administration Console. 4. Create a new machine for the new node that will be used, and add the machine to the domain. 5. Update the machines Node Managers address to map the IP of the node that is being used for scale out. 6. Use the Oracle WebLogic Server Administration Console to clone WLS_SOA1 into a new managed server. Name it WLS_SOAn, where n is a number. 7. Assign the host name or IP to use for the new managed server for the listen address of the managed server. If you are planning to use server migration for this server which Oracle recommends, this should be the VIP also called a floating IP for the server. This VIP should be different from the one used for the existing managed server. 8. Create JMS servers for SOA, OIM if applicable, 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_namejmsSOAJMSFileStore_n 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 Note: These steps assume that you are adding a new server to node n, where no managed server was running previously. Note: This directory must exist before the managed server is started or the start operation fails. 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