Start the WLS_SOA2 managed server using Oracle WebLogic Server When WLS_SOA2 starts, the following URLs become available:

5-172 Oracle Fusion Middleware High Availability Guide SOAHOST2 .unpack.sh -domain=ORACLE_BASEproductfmwuser_projectsdomainssoadomain -template=soadomaintemplate.jar 4. Repeat the steps above for OSBHOST1 and OSBHOST2.

5.14.13 Extracting XEngine Files in the Second Node

To enable B2Bs XEngine in the second node, you must extract ZEngine tar content manually: SOAHOST2cd ORACLE_HOMEsoathirdpartyedifecs SOAHOST2tar xzvf XEngine.tar.gz

5.14.14 Starting the System in SOAHOST2, OSBHOST1, and OSBHOST2

This section describes procedures for starting the system in SOAHOST2.

5.14.14.1 Starting Node Manager on SOAHOST2, OSBHOST1, and OSBHOST2

To start the Node Manager on SOAHOST2, OSBHOST1, and OSBHOST2, repeat the steps from Section 5.14.11.1, Starting Node Manager on SOAHOST1 on those nodes.

5.14.14.2 Starting and Validating the WLS_SOA2, WLS_OSB1, and WLS_OSB2 Managed Server

To start the WLS_SOA2 managed server and verify that it is configured correctly:

1. Start the WLS_SOA2 managed server using Oracle WebLogic Server

Administration Console. Watch for errors in the server’s output file while it starts.

2. When WLS_SOA2 starts, the following URLs become available:

■ http:SOAHOST2VHN1:8001b2b Verify login to B2B console ■ http:SOAHOST2VHN1:8001integrationworklistapp Verify login to worklist console ■ http:SOAHOST2VHN1:8001wsm-pm Verify the policy validator link ■ http:SOAHOST2VHN1:8001soacomposer ■ http:SOAHOST2VHN1:8001soa-infra To start the WLS_OSB1 managed server and verify that it is configured correctly: Note: When you run the Fusion Middleware Configuration Wizard after a packunpack procedure, products already in the original domain that appear in the Select Extension Source screen are not selected or greyed out. Templates that you create with the pack command are considered user-created templates and treated differently than default templates. User-created templates are self-contained and do not have any information related to the creation of the original domain. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-173 1. Start the WLS_OSB1managed server using Oracle WebLogic Server Administration Console. Watch for errors in the server´s output file while it starts. 2. When WLS_OSB1 is started, the following URL becomes available: http:OSBHOST1VHN1:8011sbinspection.wsil An HTTP reply like the following should be seen: ?xml version=1.0 encoding=UTF-8 ? ins:inspection xmlns:ins=http:schemas.xmlsoap.orgws200110inspection ins:link referencedNamespace=http:schemas.xmlsoap.orgws200110inspection location=http:OSBHOSTVHN1:8011sbinspection.wsil?refpath=default ins:abstractdefaultins:abstract ins:abstractLinkType: Projectins:abstract ins:link ins:inspection Repeat these steps for WLS_OSB2. 5.14.15 Configuring Oracle HTTP Servers for the Administration Server, WLS_SOAn, and WLS_OSBn Managed Servers To enable Oracle HTTP Server to route to the SOA Cluster contains the WLS_SOAn managed servers, set the WebLogicCluster parameter to the list of nodes in the cluster: 1. On WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_ BASEadmininstance_nameconfigOHScomponent_namemod_ wl_ohs.conf file: WSM-PM Location wsm-pm SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001, SOAHOST2VHN1:8001 Location SOA soa-infra app Location soa-infra SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location SOA inspection.wsil Location inspection.wsil SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location Worklist Location integration SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location B2B Location b2b SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location 5-174 Oracle Fusion Middleware High Availability Guide Location b2bconsole SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location UMS Location sdpmessaging SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location UMS WS Location ucsmessagingwebservice SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location Default to-do taskflow Location DefaultToDoTaskFlow SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location Workflow Location workflow SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location Required if attachments are added for workflow tasks Location ADFAttachmentHelper SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location SOA composer application Location soacomposer SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location OSB wsil Location sbinspection.wsil SetHandler weblogic-handler WebLogicCluster OSBHOST1VHN1:8011,OSBHOST2VHN2:8011 Location OSB resource Location sbresource SetHandler weblogic-handler WebLogicCluster OSBHOST1VHN1:8011,OSBHOST2VHN2:8011 Location 2. Make sure the httpd.conf file located in the same directory as the mod_wl_ohs file contains the following lines: NameVirtualHost :7777 VirtualHost :7777 ServerName https:soa.mycompany.com:443 ServerAdmin youyour.address Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-175 RewriteEngine On RewriteOptions inherit VirtualHost NameVirtualHost :7777 VirtualHost :7777 ServerName admin.mycompany.com:80 ServerAdmin youyour.address RewriteEngine On RewriteOptions inherit VirtualHost 3. Perform the same steps for the Oracle HTTP Server on WEBHOST2. 4. Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2: WEBHOST1 ORACLE_BASEadmininstance_namebinopmnctl restartproc ias-component=ohs1 WEBHOST2 ORACLE_BASEadmininstance_namebinopmnctl restartproc ias-component=ohs2

5.14.16 Validating Access Through Oracle HTTP Server