Click Save. Oracle Fusion Middleware Online Documentation Library

20-36 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management 19. Start and test the new Managed Server from the Oracle WebLogic Server Administration Console: 1. Shut down all the existing Managed Servers in the cluster. 2. Ensure that the newly created Managed Server, WLS_SOAn, is running. 3. Access the application on the newly created Managed Server http:vip:portsoa-infra. The application should be functional. 20. Configure server migration for the new Managed Server. Configure server migration following these steps: a. Log in to 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 enable migration and click the right arrow.

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. i. Test server migration for this new server. Follow these steps from the node where you added the new server:

1. Abruptly stop the WLS_SOAn Managed Server.

2. 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 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 address for the new SOA Managed Server is already present in the new node. Note: 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. Managing Enterprise Deployments 20-37

3. Watch the Node Manager Console. You should see a message indicating

that floating IP address for WLS_SOA1 has been disabled.

4. Wait for the Node Manager to try a second restart of WLS_SOAn. Node

Manager waits for a fence period of 30 seconds before trying this restart.

5. 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.

20.3.2.3 Scaling Out the Web Tier

The web tier has two nodes each running an instance of the Oracle HTTP Server. The Oracle HTTP Server components can be scaled out by adding a new node configured to run Oracle HTTP Server to the web tier. To scale out Oracle HTTP Server, proceed as follows:

1. Follow the steps in

Section 4.4, Installing Oracle HTTP Server. Alternatively, on the new node, mount the existing Middleware home, if you are using shared storage.

2. Follow the steps in

Chapter 5, Configuring the Web Tier.

3. Copy all files created in ORACLE_

INSTANCE configOHScomponentmoduleconf from the existing web tier configuration to the new one.

4. If you have enabled Single Sign-on in the topology, you must update the WebTier

configuration for Single Sign-on as described in Section 19.5, Installing and Configuring WebGate.

5. Register the new Oracle HTTP Server instance as described in

Section 6.10, Registering Oracle HTTP Server with WebLogic Server.

6. Reconfigure the load balancer with the host and port information of the new

Oracle HTTP Server instance.

20.4 Performing Backups and Recoveries