Click Save. Oracle Fusion Middleware Online Documentation Library

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-137

e. In the Available field, in the Migration Configuration section, select the

machines to which to allow migration and click the right arrow. Select the same migration targets as for the servers that already exist on the node. For example, for new managed servers on SOAHOST1, which is already running WLS_SOA1, select SOAHOST2. For new managed servers on SOAHOST2, which is already running WLS_SOA2, select SOAHOST1. 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. 10. 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_SOAn’s 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.

5.13.22.2 Scaling Out the Topology Adding Managed Servers to New Nodes

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: Note: For Windows, the Managed Server can be terminated by using the taskkill command. For example: taskkill f pid pid Where pid is the process Id of the Managed Server. To determine the process Id of the Managed Server run the following command and identify the pid of the WLS_SOAn Managed Server. MW_HOME\jrockit_160_20_D1.0.1-2124\bin\jps -l -v Note: After a server is migrated, to fail it back to its original nodemachine, stop the managed server from the Oracle WebLogic Administration Console and then start it again. The appropriate Node Manager will start the managed server on the machine to which it was originally assigned. 5-138 Oracle Fusion Middleware High Availability Guide ■ 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. 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 command: SOAHOSTncd ORACLE_BASEproductfmwsoa SOAHOSTn.attachHome.sh -jreLoc ORACLE_BASEfmwjrockit_160_20_D1.0.1-2124 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 and assign it to the new machine. Note: If there is no existing installation in shared storage, installing WebLogic Server and SOA in the new nodes is required. See 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. Note: These steps assume that you are adding a new server to node n, where no managed server was running previously. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-139 7. For the listen address, assign the virtual host name to use for this new managed server. If you are planning to use server migration as recommended for this server, this virtual host name will enable it to move to another node. The virtual host name should be different from the one used by the managed server that is already running. Perform these steps to set the managed server listen address: a. Log into the Oracle WebLogic Server Administration Console.

b. In the Change Center, click Lock Edit.