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

12-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite c. Click the name of the new managed 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. e. In the Migration Configuration section, select the servers that participate in migration in the Available window 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 ECMHOST1, which is already running WLS_IPM1, select ECMHOST2. For new managed servers on ECMHOST2, which is already running WLS_IPM2, select ECMHOST1.

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. 8. 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_IPMn 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_IPMn ■ Watch the Node Manager Console for a message indicating that WLS_IPM1s floating IP has been disabled. ■ Wait for Node Manager to attempt a second restart of WLS_IPMn. 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.6.1.2 Scale-up Procedure for Oracle UCM

Only one UCM managed server per node per domain is supported by Oracle Fusion Middleware. To add additional UCM managed servers, follow the steps in Section 12.6.2.2, Scale-out Procedure for Oracle UCM to add a UCM managed server to a new node. Note: The appropriate resources must be available to run the managed servers concurrently during migration. Note: After a server is migrated, to fail it back to its original node or machine, 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. Managing the Topology 12-9

12.6.1.3 Scale-up Procedure for SOA

Perform these steps for scaling up the SOA servers in the topology:

1. Using the Oracle WebLogic Server Administration Console, clone WLS_SOA1 to 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. Perform these steps to clone a managed server:

a. In the Domain Structure window of the Oracle WebLogic Server