Expand the Environment node in the Domain Structure window. Click Servers. The Summary of Servers page opens. Expand the Advanced section of the page. Click Lock Edit. Click Save. In the Domain Structure window, expand the Environment node and then

Managing the Topology 12-11 6. Disable host name verification for the new managed server. Before you can start and verify 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 Node Manager in SOAHOSTn. If the source server from which the new one has been cloned had already disabled host name verification, these steps are not required the host name verification settings is propagated to the cloned server. Perform these steps to disable host name verification: a. In the Oracle Enterprise Manager Console, select Oracle WebLogic Server Administration Console, and log in.

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

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

d. Select WLS_SOAn in the Names column of the table. The settings page for the server opens. e. Open the SSL tab.

f. Expand the Advanced section of the page.

g. Click Lock Edit.

h. Set host name verification to None.

i. Click Save.

7. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Ensure that the newly created managed server, WLS_SOAn, is running. b. Access the application on the LBR https:ecm.mycompany.comsoa-infra. The application should be functional. 8. Configure server migration for the new managed server. Perform these steps to configure server migration: a. Log in to the Oracle WebLogic Server Administration Console.

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

click Servers. The Summary of Servers page opens. Note: The HTTP Servers in the topology should round-robin requests to the new added server a few requests, depending on the number of servers in the cluster, may be required to hit the new server. Its is not required to add all servers in a cluster to the WebLogicCluster directive in Oracle HTTP Servers mod_wl_ ohs.conf file. However routing to new servers in the cluster will take place only if at least one of the servers listed in the WebLogicCluster directive is running. 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 managed SOA server should also be already present. 12-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite c. Click the name of the new managed 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 opens. d. Open the Migration subtab. e. In the Migration Configuration section, select the servers that participate in migration in the Available window 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.

f. Choose the Automatic Server Migration Enabled option. This enables Node