Propagating the Domain Configuration to SOAHOST2 with packunpack Utilities Extracting XEngine Files in the Second Node Validating Access Through Oracle HTTP Server

Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-117 ■ http:SOAHOST1VHN1:8001soacomposer ■ http:SOAHOST1VHN1:8001soa-infra ■ http:SOAHOST1VHN1:8001bpmcomposer ONLY FOR BPM Systems ■ http:SOAHOST1VHN1:8001bpmworkspace ONLY FOR BPM Systems

5.13.11 Propagating the Domain Configuration to SOAHOST2 with packunpack Utilities

Follow these steps to propagate the domain configuration to SOAHOST2 using packunpack utilities: 1. Run the following pack command on SOAHOST1 to create a template pack: SOAHOST1 cd ORACLE_COMMON_HOMEcommonbin SOAHOST1 .pack.sh -managed=true -domain=ORACLE_BASEproductfmwuser_projectsdomainssoadomain -template=soadomaintemplate.jar -template_name=soa_domain_template 2. Run the following command on SOAHOST1 to copy the template file created in the previous step to SOAHOST2: SOAHOST1 scp soadomaintemplate.jar oraclenode2:ORACLE_COMMON_HOMEcommonbin 3. Run the unpack command on SOAHOST2 to unpack the propagated template: SOAHOST2 cd ORACLE_COMMON_HOMEcommonbin SOAHOST2 .unpack.sh -domain=ORACLE_BASEproductfmwuser_projectsdomainssoadomain -template=soadomaintemplate.jar

5.13.12 Extracting XEngine Files in the Second Node

To enable B2Bs XEngine in the second node, it is required to extract the content of the ZEngine tar manually: SOAHOST2cd ORACLE_HOMEsoathirdpartyedifecs SOAHOST2tar xzvf XEngine.tar.gz

5.13.13 Starting the System in SOAHOST2

This section describes procedures for starting the system in SOAHOST2. Note: When you run the Fusion Middleware Configuration Wizard after a packunpack procedure, products that already exist in the original domain and appear in the Select Extension Source screen, are not selected or greyed out. Templates created with the pack command are considered user-created templates. They are treated differently from default templates. User-created templates are self-contained and do not contain any information related to the creation of the original domain. 5-118 Oracle Fusion Middleware High Availability Guide

5.13.13.1 Starting Node Manager on SOAHOST2

To start the Node Manager on SOAHOST2, repeat the steps from Section 5.13.10.1, Starting Node Manager on SOAHOST1 on SOAHOST2.

5.13.13.2 Starting and Validating the WLS_SOA2 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 2. When WLS_SOA2 is started, 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 ■ http:SOAHOST2VHN1:8001bpmcomposer ONLY FOR BPM Systems ■ http:SOAHOST2VHN1:8001bpmworkspace ONLY FOR BPM Systems 5.13.14 Configuring Oracle HTTP Servers for the Administration Server and the WLS_ SOAn Managed Servers To enable Oracle HTTP Server to route to the SOA Cluster, which contains the WLS_ SOAn managed servers, you must 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 Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-119 SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location B2B Location b2b SetHandler weblogic-handler WebLogicCluster SOAHOST11VHN1:8001,SOAHOST2VHN1:8001 Location 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 BPM composer ONLY FOR BPM Systems Location bpmcomposer SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 Location BPM workspace ONLY FOR BPM Systems Location bpmworkspace SetHandler weblogic-handler 5-120 Oracle Fusion Middleware High Availability Guide WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 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 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.13.15 Validating Access Through Oracle HTTP Server

Verify that the SOA Servers 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. Verify that you can access these URLS: ■ http:WEBHOST1:7777wsm-pm ■ http:WEBHOST2:7777wsm-pm ■ http:WEBHOST1:7777soa-infra ■ http:WEBHOST2:7777soa-infra ■ http:WEBHOST1:7777soacomposer ■ http:WEBHOST2:7777soacomposer ■ http:WEBHOST1:7777integrationworklistapp ■ http:WEBHOST2:7777integrationworklistapp Note: Values such as soa.mycompany.com:443, 7777, admin.mycompany:80, and youyouraddress that are noted in this document serve as examples only. Enter values based on the actual environment. Configuring High Availability for Oracle Fusion Middleware SOA Suite 5-121 ■ http:WEBHOST1:7777sdpmessaginguserprefs-ui ■ http:WEBHOST2:7777sdpmessaginguserprefs-ui ■ http:WEBHOST1:7777b2bconsole ■ http:WEBHOST2:7777b2bconsole ■ http:WEBHOST1:7777bpmcomposer ONLY FOR BPM Systems ■ http:WEBHOST2:7777bpmcomposer ONLY FOR BPM Systems ■ http:WEBHOST1:7777bpmworkspace ONLY FOR BPM Systems ■ http:WEBHOST2:7777bpmworkspace ONLY FOR BPM Systems Verify these URLs also using your load balancing router address: ■ http:soa.mycompany.com:80wsm-pm ■ http:soa.mycompany.com:80soa-infra ■ http:soa.mycompany.com:80soacomposer ■ http:soa.mycompany.com:80integrationworklistapp ■ http:soa.mycompany.com:80sdpmessaginguserprefs-ui ■ http:soa.mycompany.com:80b2bconsole ■ http:soa.mycompany.com:80bpmcomposer ONLY FOR BPM Systems ■ http:soa.mycompany.com:80bpmworkspace ONLY FOR BPM Systems Follow these instructions to ensure that routing and failover from the HTTP Server to the SOA_CLuster is working correctly: 1. While WLS_SOA2 is running, stop WLS_SOA1 from Oracle WebLogic Server Administration Console. 2. Access the following URLs and verify the appropriate functionality: ■ WEBHOST1:7777wsm-pm ■ WEBHOST1:7777soa-infra ■ WEBHOST1:7777soacomposer ■ WEBHOST1:7777integrationworklistapp ■ WEBHOST1:7777sdpmessaginguserprefs-ui ■ WEBHOST1:7777b2bconsole ■ WEBHOST1:7777bpmcomposer ONLY FOR BPM Systems ■ WEBHOST1:7777bpmworkspace ONLY FOR BPM Systems 3. Start WLS_SOA1 from Oracle WebLogic Server Administration Console. 4. Stop WLS_SOA2. 5. Access the URLs in Step 2 above again and verify the appropriate functionality:

5.13.16 Configuring JMS Persistence Store as Shared Across the Servers