Click Save and activate the changes. In the Domain Structure window, expand the Environment node and click Expand the Advanced section of the pag Click Lock Edit. Click Save. In the Domain Structure window, expand the Environment node and then In the Dom

Managing the Topology 12-7 ORACLE_BASE admindomain_nameipm_cluster_nametlogs

g. Click Save and activate the changes.

5. Disable host name verification for the new managed server. Before you can start and verify the WLS_IPMn 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 ECMHOSTn. 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. In the Domain Structure window, expand the Environment node and click

Servers . The Summary of Servers page opens. c. Click WLS_IPMn represented as a hyperlink in the Name column of the table. The settings page for the WLS_IPMn server opens with the Configuration tab active. d. Open the SSL tab. e. Expand the Advanced section of the page.

f. Click Lock Edit.

g. Set host name verification to None.

h. Click Save.

6. Start the newly created managed server WLS_IPM: 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. c. Open the Control tab, and shut down all existing WLS_IPMn managed servers in the cluster. d. Ensure that the newly created managed server, WLS_IPMn, is running. 7. 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: This directory must exist before the managed server is started or the start operation will fail. 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 Oracle IPM server should also be already present. 12-8 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 ECMHOST1, which is already running WLS_IPM1, select ECMHOST2. For new managed servers on ECMHOST2, which is already running WLS_IPM2, select ECMHOST1.

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