In the Oracle Fusion Middleware Enterprise Manager Console, select Oracle Expand the Environment node in the Domain Structure window. Click Servers. Select WLS_SOAn in the Names column of the table. Click the SSL tab. Click Advanced. Set Hostname Verifica

11-6 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter 6. Configure the persistent store for the new server. This should be a location visible from other nodes as recommended in Section 2.3, Shared Storage and Recommended Directory Structure. From the Administration Console, select the Server_name , and then the 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 Fusion Middleware 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 server appears.

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

8. Configure server migration for the new managed server. To configure server migration using the Oracle WebLogic Server Administration Console, complete these steps:

a. In the Domain Structure window, expand the Environment node and then

click Servers. The Summary of Servers page appears. Note: Only the localhost field must be changed for the server. Replace the localhost with the listen address of the new server added: Dtangosol.coherence.localhost=SOAHOST1VHNn Note: Because this is a scale-up operation, the node should already contain a Node Manager and environment configured for server migration that includes netmask, interface, wlsifconfig script superuser privileges, and so on. The floating IP for the new SOA managed server should also be already present. 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