Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page appears. Select WLS_SOAn in the Names column of the table. The Settings page for the Click Advanced. Set Hostname Verification to None. Click Save. In t

5-136 Oracle Fusion Middleware High Availability Guide 6. Configure TX persistent store for the new server. This should be a location visible from other nodes as indicated in the recommendations about shared storage. From the Administration Console, select Server_name Services tab. Under Default Store , in Directory, enter the path to the folder where you want the default persistent store to store its data files. 7. Disable host name verification for the new managed server. Before starting and verifying the WLS_SOAn managed server, you must disable host name verification. You can re-enable it after you have configured server certificates for the communication between the Oracle WebLogic Administration Server and the Node Manager in SOAHOSTn. 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_SOAn 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.

8. 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_SOAn, is up. c. Access the application on the newly created managed server http:vip:portsoa-infra. The application should be functional. 9. 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. 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 SOA managed server should also be already present. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-137

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 SOAHOST1, which is already running WLS_SOA1, select SOAHOST2. For new managed servers on SOAHOST2, which is already running WLS_SOA2, select SOAHOST1. 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.