In the Oracle Enterprise Manager Console, select Oracle WebLogic Server 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. Click the SSL tab. Cl

5-142 Oracle Fusion Middleware High Availability Guide 11. Configure Oracle Coherence for deploying composites, as described in Section 5.13.8, Configuring Oracle Coherence for Deploying Composites. 12. 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. 13. 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 setting 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 server appears.

e. Click the SSL tab.

f. Click Advanced.

g. Set Hostname Verification to None.

h. Click Save.

14. Start the Node Manager on the new node. To start the Node Manager, use the installation in shared storage from the existing nodes, and start Node Manager by passing the host name of the new node as a parameter as follows: SOAHOSTN WL_HOMEserverbinstartNodeManager new_node_ip 15. Start and test the new managed server from the Oracle WebLogic Server Administration Console: a. Shut down all the existing managed servers in the cluster. b. Ensure that the newly created managed server, WLS_SOAn, is running. c. Access the application on the newly created managed server http:vip:portsoa-infra. The application should be functional. 16. Configure server migration for the new managed server. Note: Only the localhost field needs to be changed for the server. Replace the localhost with the listen address of the new server added, for example: Dtangosol.coherence.localhost=SOAHOSTnVHN1 Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-143 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 server represented as hyperlink for which you want to configure migration from the Names column of the table. The Setting page for that server appears.

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.

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