In the left pane, expand Environment and select Servers. Click the Migration tab. In the Available field, in the Migration Configuration section, select the Select the Automatic Server Migration Enabled option. This enables the Node Click Save.

5-206 Oracle Fusion Middleware High Availability Guide

d. Select WLS_OSBn in the Names column of the table.

The Settings page for server appears.

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

18. Start the Node Manager on the new node. To start the Node Manager, use the installation in shared storage from the existing nodes, and start Node Manager by passing the host name of the new node as a parameter as follows: OSBHOSTN WL_HOMEserverbinstartNodeManager new_node_ip 19. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Shut down all the existing managed servers in the cluster. b. Ensure that the newly created managed server, WLS_OSBn, is running. c. Access the application on the newly created managed server http:vip:portsbinspection.wsil. The application should be functional. 20. Configure server migration for the new managed server. Configure server migration following these steps: a. Log into the Administration Console.

b. In the left pane, expand Environment and select Servers.

c. Select the server represented as hyperlink for which you want to configure migration from the Names column of the table. The Setting page for that server appears.

d. Click the Migration tab.

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

machines to which to allow migration and click the right arrow. For example, for new managed servers on OSBHOST1, which is already running WLS_OSB1, select OSBHOST2. For new managed servers on OSBHOST2, which is already running WLS_OSB2, select OSBHOST1. Note: Since this new node is using an existing shared storage installation, the node is already using a Node Manager and an environment configured for server migration that includes netmask, interface, wlsifconfig script superuser privileges. The floating IP for the new OSB Managed Server is already present in the new node. Note: It is recommended to specify the least-loaded machine as the migration target for the new server. The required capacity planning must be completed so that this node has enough available resources to sustain an additional managed server. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-207

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. 21. Test server migration for this new server. Follow these steps from the node where you added the new server: a. Abruptly stop the WLS_OSBn 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_OSBn. b. Watch the Node Manager Console: you should see a message indicating that WLS_OSBns floating IP has been disabled. c. Wait for the Node Manager to try a second restart of WLS_OSBn. 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.15 Configuring High Availability for Oracle BAM