Disabling Host Name Verification for the WLS_SOAn Managed Server Restarting the Node Manager on SOAHOST1 Propagating the Domain Changes to the Managed Server Domain Directory

Extending the Domain for SOA Components 5-11

2. In the Domain Structure window, expand the Services node, and then the

Messaging node.

3. Click JMS Modules, and then SOAJMSModule.

4. Click Lock and Edit.

5. Click the dist_B2BEventQueue_auto, Configuration, and the General tab, and

then click Advanced. 6. In the Create Destination Identifier field, add the following jndi name for the queue: jmsb2bB2BEventQueue 7. Repeat these steps, creating the following Create Destination Identifiers for the queues listed below: ■ dist_B2B_OUT_QUEUE_auto : jmsb2bB2B_OUT_QUEUE ■ dist_B2B_IN_QUEUE_auto : jmsb2bB2B_IN_QUEUE ■ dist_B2BBroadcastTopic_auto : jmsb2bB2BBroadcastTopic ■ dist_XmlSchemaChangeNotificationTopic_auto : jmsfabricXmlSchemaChangeNotificationTopic

8. Click Save and Active Changes.

5.7 Disabling Host Name Verification for the WLS_SOAn Managed Server

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the Administration Server see Chapter 7, Setting Up Node Manager . If you have not configured the server certificates, you will receive errors when managing the different WebLogic Servers. To avoid these errors, disable host name verification while setting up and validating the topology, and enable it again once the Enterprise Deployment topology configuration is complete as described in Chapter 7, Setting Up Node Manager. To disable host name verification, complete these steps: 1. Log in to Oracle WebLogic Server Administration Console.

2. Click Lock and Edit.

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

4. Click Servers. The Summary of Servers page appears.

5. Select WLS_SOA1 represented as a hyperlink from the Names column of the

table. The Settings page appears.

6. Select the SSL tab.

7. Expand the Advanced section of the page.

8. Set Hostname Verification to None.

9. Click Save.

10. Repeat these steps for the WLS_SOA2 managed server. 11. Save and activate the changes. 5-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

5.8 Restarting the Node Manager on SOAHOST1

To restart the Node Manager on SOAHOST1: 1. Stop Node Manager by stopping the process associated with it: a. If it is running in the foreground in a shell, simply use CTRL+C. b. If it is running in the background in the shell, find the associate process and use the kill command to stop it. For example: SOAHOST1 ps -ef | grep NodeManager orcl 9139 9120 0 Mar03 pts6 00:00:00 binsh .startNodeManager.sh SOAHOST1kill -9 9139 2. Start Node Manager: SOAHOST1 .startNodeManager.sh

5.9 Propagating the Domain Changes to the Managed Server Domain Directory

To propagate the start scripts and classpath configuration from the Administration Server’s domain directory to the managed server domain directory: 1. Create a copy of the managed server domain directory and the managed server applications directory. 2. Run the pack command on SOAHOST1 to create a template pack using the following commands: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEadmindomain_ nameaserverdomain_name -template=soadomaintemplateExtSOA.jar -template_name=soa_domain_templateExtSOA 3. Run the unpack command on SOAHOST1 to unpack the propagated template to the domain directory of the managed server using the following command: SOAHOST1 .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_ name -overwrite_domain=true -template=soadomaintemplateExtSOA.jar -app_dir=ORACLE_BASEadmindomain_namemserverapplications

5.10 Starting the WLS_SOA1 Managed Server on SOAHOST1