Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page appears. Click Advanced. Set Hostname Verification to None. Click Save. In the left pane, expand Environment and select Servers. In the Available field,

5-198 Oracle Fusion Middleware High Availability Guide the communication between the Oracle WebLogic Administration Server and the Node Manager in OSBHOSTn. If the source server from which the new one has been cloned had already disabled hostname verification, these steps are not required the hostname verification settings is propagated to the cloned server. To disable host name verification: a. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Administration Console.

b. Expand the Environment node in the Domain Structure window.

c. Click Servers. The Summary of Servers page appears.

d. Select WLS_OSBn in the Names column of the table. The Settings page for the server appears. e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

12. If it is not already started, start the Node Manager on the node. To start the Node Manager, use the installation in shared storage from the existing nodes as follows: OSBHOSTN WL_HOMEserverbinstartNodeManager 13. Start and test the new managed server from the Administration Console. a. Shut down the existing managed servers in the cluster. b. Ensure that the newly created managed server, WLS_OSBn, is up. c. Access the application on the newly created managed server http:vip:portsbinspection.wsil. 14. 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 name of the new managed server for which you want to configure migration. 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. Select the same migration targets as for the servers that already exist on the node. 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 is a scale-up operation, the node should already contain a Node Manager and environment configured for server migration. The floating IP for the new OSB managed server should also be already present. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-199 Make sure the appropriate resources are available to run the managed servers concurrently during migration. 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.