Choose the Automatic Server Migration Enabled option. This enables the Click Save. In the Administration Console, select Environment, and then Cluster. Click the SOA_Cluster server. Click Lock and Edit. Add the new server’s address and port to the Cluster

Managing the Topology 11-7 b. 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 appears.

c. Click the Migration subtab.

d. In the Migration Configuration section, select the servers that participate in migration in the Available window by clicking 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.

e. Choose the Automatic Server Migration Enabled option. This enables the

Node Manager to start a failed server on the target node automatically.

f. Click Save.

g. Restart the Administration Server, managed servers, and Node Manager. To restart the Administration Server, use the procedure in Section 4.7, Starting the Administration Server on SOAHOST1. 9. Update the cluster address to include the new server:

a. In the Administration Console, select Environment, and then Cluster.

b. Click the SOA_Cluster server.

The Settings screen for the SOA_Cluster appears.

c. Click Lock and Edit.

d. Add the new server’s address and port to the Cluster address field. For example: ADMINVHN:8011,SOAHOST2VHN1:8011,SOAHOST1VHN1:8001 e. Save and activate the changes. 10. Test server migration for this new server. To test migration, perform the following 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. Monitor the Node Manager Console for a message indicating that WLS_ SOA1’s floating IP has been disabled. c. Wait for the Node Manager to attempt 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. The Node Manager should log a message indicating that the server will not be restarted again locally. Note: The appropriate resources must be available to run the managed servers concurrently during migration. 11-8 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

11.4.1.2 Scaling Up WebCenter

In this case, you already have a node that runs a managed server configured with Oracle WebCenter components. The node contains a Middleware home and a WebCenter directory in shared storage. You can use the existing installations Middleware home, and domain directories for creating new Oracle WebCenter managed servers. You do not need to install WebCenter binaries in a new location, or run pack and unpack commands. To scale up the topology:

1. Using the Administration Console, clone WC_Spaces1 or WC_Portlet1 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. In the Administration Console, select Environment, and then Servers.