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. Log in to the Oracle WebLogic Server Administration Console. In the Domain

Managing the Topology 12-21 hyperlink in the Names column of the table. The Settings page for SOAJMSModule appears. Click the SubDeployments tab. The subdeployment module for SOAJMS appears. Click the SOAJMSServerXXXXXX subdeployment. Add the new JMS server for SOA called SOAJMSServer_N to this subdeployment. Click Save. f. Update the subdeployment targets for the UMSJMSSystemResource to include the recently created UMS JMS server. To do this, expand the Services node in the Oracle WebLogic Server Administration Console and then expand the Messaging node. Choose JMS Modules in the Domain Structure window. The JMS Modules page appears. Click UMSJMSSystemResource represented as a hyperlink in the Names column of the table. The Settings page for UMSJMSSystemResource appears. Click the SubDeployments tab. The subdeployment module for UMSJMS appears. Click the UMSJMSServerXXXXXX subdeployment. Add the new JMS server for UMS called UMSJMSServer_N to this subdeployment. Click Save. 12. Configure a TX persistent store for the new server. This should be a location visible from other nodes as indicated in the recommendations about shared storage see Section 2.3, Shared Storage and Recommended Directory Structure . From the Administration Console, select the server name in 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. 13. 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 setting 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.

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. Note: This subdeployment module name is a random name in the form of SOAJMSServerXXXXXX resulting from the Configuration Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_SOA2. Note: This subdeployment module name is a random name in the form of UCMJMSServerXXXXXX resulting from the Configuration Wizard JMS configuration for the first two servers WLS_SOA1 and WLS_SOA2. 12-22 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite

f. Expand the Advanced section of the page.

g. Click Lock Edit.

h. Set host name verification to None.

i. Click Save.

14. Start Node Manager on the new node. To start Node Manager, use the installation in shared storage from the already existing nodes and then start Node Manager by passing the host name of the new node as a parameter as follows: SOAHOSTn WL_HOMEserverbinstartNodeManager.sh New_Node_IP 15. 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. 16. Configure server migration for the newly added 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. c. 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 opens.

d. Open the Migration subtab.