Choose Servers. The Summary of Servers page opens. Select WLS_SOA1 and then click Start. Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility

Extending the Domain with SOA Components 6-11

6.6 Disabling Host Name Verification for the WLS_SOA Managed Servers

This step is required if you have not set up the appropriate certificates to authenticate the different nodes with the administration server see Chapter 9, 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 EDG topology configuration is complete as described in Chapter 9, Setting Up Node Manager. Perform these steps to disable host name verification: 1. Log in to Oracle WebLogic Server Administration Console.

2. Click Lock Edit.

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

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

5. Select WLS_SOA1 in the Names column of the table. The settings page for the

server opens. 6. Open the SSL tab.

7. Expand the Advanced section of the page.

8. Set host name verification to None.

9. Click Save.

10. Repeat steps 4 through 8 for the WLS_SOA2 managed server. 11. Save and activate the changes. 12. Restart Node Manager: a. Stop Node Manager by stopping the process associated with it. If it is running in the foreground in a shell, simply use Ctrl+c. 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 b. Start Node Manager: SOAHOST1 .startNodeManager.sh

6.7 Starting and Validating the WLS_SOA1 Managed Server on SOAHOST1

Perform these steps to start the WLS_SOA1 managed server and check that it is configured correctly: 1. Start the WLS_SOA1 managed server using the Oracle WebLogic Server Administration Console as follows: a. Expand the Environment node in the Domain Structure window.

b. Choose Servers. The Summary of Servers page opens.

6-12 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle ECM Suite c. Click the Control tab.

d. Select WLS_SOA1 and then click Start.

2. Verify that the server status is reported as Running in the Administration Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported such as Admin or Failed, check the server output log files for errors. See Section 12.8, Troubleshooting for possible causes. 3. Access the following URLs: ■ Access http:SOAHOST1VHN1:8001soa-infra to verify the status of WLS_ SOA1. ■ Access http:SOAHOST1VHN1:8001wsm-pm to verify the status of Web Services Manager. Click Validate Policy Manager. A list of policies and assertion templates available in the data store opens. ■ Access http:SOAHOST1VHN1:8001integrationworklistapp to verify the status of the worklist application.

6.8 Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility

Perform these steps to propagate the domain configuration: 1. Run the following command on SOAHOST1 to copy the template file created in Section 6.4, Creating a Separate Domain Directory for Managed Servers in the Same Node as the Administration Server : SOAHOST1 cd ORACLE_BASEproductfmworacle_commoncommonbin SOAHOST1 scp edgdomaintemplate.jar oracleSOAHOST2:ORACLE_BASEproductfmw oracle_commoncommonbin 2. Run the unpack command on SOAHOST2 to unpack the propagated template. SOAHOST2 cd ORACLE_COMMON_HOMEcommonbin SOAHOST2 .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_name -template=edgdomaintemplate.jar -app_dir=ORACLE_BASEadmindomain_namemserver applications Note: The configuration is incorrect if no policies or assertion templates appear. Note: Run unpack from the ORACLE_COMMON_HOME commonbin directory, not from WL_HOMEcommonbin. Note: The ORACLE_BASEadmindomain_namemserver directory must exist before running unpack. In addition, the ORACLE_BASE admindomain_namemserverapplications must be empty. Extending the Domain with SOA Components 6-13

6.9 Starting Node Manager on SOAHOST2