Open the Migration subtab. In the Available field of the Migration Configuration section, select the Choose the Automatic Server Migration Enabled option. This enables Node Click Save.

12-22 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

f. Expand the Advanced section of the page.

g. Click Lock Edit.

h. Set host name verification to None.

i. Click Save.

14. Start Node Manager on the new node. To start Node Manager, use the installation in shared storage from the already existing nodes and then start Node Manager by passing the host name of the new node as a parameter as follows: SOAHOSTn WL_HOMEserverbinstartNodeManager.sh New_Node_IP 15. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Ensure that the newly created managed server, WLS_SOAn, is running. b. Access the application on the LBR https:ecm.mycompany.comsoa-infra. The application should be functional. 16. Configure server migration for the newly added server. Perform these steps to configure server migration:

a. Log in to the Oracle WebLogic Server Administration Console.

b. In the Domain Structure window, expand the Environment node and then

click Servers. The Summary of Servers page opens. c. Click the name of the server represented as a hyperlink in Name column of the table for which you want to configure migration. The settings page for the selected server opens.

d. Open the Migration subtab.

Note: If you used the paths shown in Chapter 3.3.1, Installing Oracle WebLogic Server and Creating the Fusion Middleware Home, WL_HOME would be ORACLE_BASEproductfmwwlserver_10.3. Note: The HTTP Servers in the topology should round-robin requests to the new added server a few requests, depending on the number of servers in the cluster, may be required to hit the new server. Its is not required to add all servers in a cluster to the WebLogicCluster directive in Oracle HTTP Servers mod_wl_ ohs.conf file. However routing to new servers in the cluster will take place only if at least one of the servers listed in the WebLogicCluster directive is running. Note: Since this new node uses an existing shared storage installation, the node already is using a Node Manager and an environment configured for server migration that includes netmask, interface, wlsifconfig script superuser privileges, and so on. The floating IP for the new managed SOA server is already present in the new node. Managing the Topology 12-23

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

machines to which to allow migration and click the right arrow.

f. Choose the Automatic Server Migration Enabled option. This enables 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. 17. Test server migration for the new server. To test migration, perform the following steps from the node where you added the new server: ■ Abruptly 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 the following command: ps -ef | grep WLS_SOAn ■ Watch the Node Manager Console for a message indicating that WLS_SOA1s floating IP has been disabled. ■ Wait for Node Manager to attempt a second restart of WLS_SOAn. Node Manager waits for a fence period of 30 seconds before trying this restart. ■ Once Node Manager restarts the server, stop it again. Node Manager should log a message indicating that the server will not be restarted again locally.

12.7 Performing Backups and Recoveries