Click the Migration tab. In the Available field, located in the Migration Configuration section, select Select Environment - Servers from the Administration Console. Select Clone.

5-130 Oracle Fusion Middleware High Availability Guide a. In the left pane of Oracle WebLogic Server Administration Console, expand Environment and select Servers. b. Select the server for which you want to configure migration.

c. Click the Migration tab.

d. In the Available field, located in the Migration Configuration section, select

the machines to which to allow migration and click the right arrow. For WLS_ SOA1 , select SOAHOST2. For WLS_SOA2, select SOAHOST1. e. Select the checkbox for Automatic Server Migration Enabled. This enables the Node Manager to start a failed server on the target node automatically.

f. Click Save and activate the changes.

g. These changes require restart of the servers and Node Managers to be effective. Step 6 Test Server Migration To verify that Server Migration is working properly, follow these steps: From SOAHOST1: 1. Force stop the WLS_SOA1 managed server. To do this, run this command: SOAHOST1 kill -9 pid pid specifies the process ID of the managed server. You can identify the pid in the node by running this command: SOAHOST1 ps -ef | grep WLS_SOA1 2. Watch the Node Manager console: you should see a message indicating that WLS_ SOA1’s floating IP has been disabled. 3. Wait for the Node Manager to try a second restart of WLS_SOA1. Node Manager waits for a fence period of 30 seconds before trying this restart. 4. 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. From SOAHOST2: 1. Watch the local Node Manager console. After 30 seconds since the last try to restart WLS_SOA1 on Node 1, Node Manager on Node 2 should prompt that the 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_SOA1 Managed Server. MW_HOME\jrockit_160_20_D1.0.1-2124\bin\jps -l -v Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-131 floating IP for WLS_SOA1 is being brought up and that the server is being restarted in this node. 2. Access the soa-Service Infrastructure console in the same IP. Migration can also be verified in Oracle WebLogic Server Administration Console: 1. Log into Oracle WebLogic Server Administration Console.

2. Click on Domain on the left pane.

3. Click on the Monitoring tab and then on the Migration sub-tab.

The Migration Status table provides information on the status of the migration. Figure 5–46 Migration Status Screen in Oracle WebLogic Server Administration Console 5-132 Oracle Fusion Middleware High Availability Guide

5.13.22 Scaling the Topology

You can scale out or scale up this 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.

5.13.22.1 Scaling Up the Topology 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_SOA servers. There is no need to install 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 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_SOA1.

c. Select Clone.

Note: On Windows, when you manually shut down multiple servers at the same time, on the same machine, and then, on another machine, attempt to start one of the servers that was shut down, the IP bind may not work. This happens because the original machine still has claim to the IP address, even though netsh has reported that the IP address has been removed. To resolve this, you must check the network configuration either by using the ipconfig utility or Windows Network Configuration. Either of these may show that one of the virtualfloating IP addresses is still configured even though the servers have been shut down. You can then use Windows Network Configuration to remove the IP address using the following procedure: 1. From Windows Control Panel, select Network Connections. 2. Select the appropriate network interface, right-click, and select Properties . 3. Select Internet Protocol TCPIP and click the Properties button. 4. Select Advanced. 5. Select the appropriate IP address and click the Remove button. 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. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-133 Name the new managed server 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 SOAHOST1, which is already running WLS_SOA1. 2. 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.