Starting the WLS_SOA1 Managed Server on SOAHOST1 Validating the WLS_SOA1 Managed Server Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility

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

To start the WLS_SOA1 managed server on SOAHOST1, complete these steps: 1. Access the Administration Console at http:ADMINVHN:7001console. Note: The -overwrite_domain option in the unpack command, allows unpacking a managed server template into an existing domain and existing applications directories. For any file that is overwritten, a backup copy of the original is created. If any modifications had been applied to the start scripts and ear files in the managed server domain directory, they must be restored after this unpack operation. Extending the Domain for SOA Components 5-13

2. Click Servers.

3. Open the Control tab.

4. Select WLS_SOA1.

5. Click Start.

5.11 Validating the WLS_SOA1 Managed Server

To validate the WLS_SOA1 managed server, complete these steps:

1. Verify that the server status is reported as Running in the Admin 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 11.6, Troubleshooting for possible causes. 2. Access http:SOAHOST1VHN1:8001soa-infra to verify status of WLS_ SOA1. 3. Access http:SOAHOST1VHN1:8001b2bconsole to verify status of B2B. 4. Access http:SOAHOST1VHN1:8001integrationworklistapp to verify status of the worklist application. Before verifying access is granted, ensure that the WLS_WSM1 managed server is up and running.

5.12 Propagating the Domain Configuration to SOAHOST2 Using the unpack Utility

To propagate the domain configuration, complete these steps: 1. Run the following command on SOAHOST1 to copy the template file created in the previous step to SOAHOST2. SOAHOST1 cd ORACLE_HOMEcommonbin SOAHOST1 scp soadomaintemplateExtSOA.jar oraclenode2:ORACLE_HOMEcommonbin 2. Run the unpack command on SOAHOST2 to unpack the propagated template. SOAHOST2 cd ORACLE_HOMEcommonbin .unpack.sh -domain=ORACLE_BASEadmindomain_namemserverdomain_name -template=soadomaintemplateExtSOA.jar -overwrite_domain=true -app_dir=ORACLE_BASEadmindomain_namemserverapplications Note: ADMINVHN is the virtual host name that maps to the virtual IP where the Administration Server is listening in SOAHOST1. Note: Notice that, although the WLS_SOA1 server may be up, some applications may be in a failed state. Therefore, Oracle recommends verifying the URLs above and watch for errors pertaining each individual application in the servers output file. 5-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter

5.13 Restarting Node Manager on SOAHOST2