5-14 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
5.13 Restarting Node Manager on SOAHOST2
Perform the steps in Section 5.8, Restarting the Node Manager on SOAHOST1
on SOAHOST2.
5.14 Starting and Validating the WLS_SOA2 Managed Server
Perform these steps to start the WLS_SOA2 managed server and check that it is configured correctly:
1.
Start the WLS_SOA2 managed server using the Administration Console.
2.
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.
3.
Access http:SOAHOST2VHN1:8001soa-infra.
4.
Access http:SOAHOST2VHN1:8001b2bconsole to verify status of B2B.
5.
Access http:SOAHOST2VHN1:8001integrationworklistapp to verify status of the worklist application. Before verifying access is granted, ensure
that at least one of the managed servers WLS_WSM1 or WLS_WSM2 is up and running.
5.15 Configuring Oracle HTTP Server for 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_BASE admininstance_nameconfigOHScomponent_namemod_wl_ohs.conf file:
SOA soa-infra app Location soa-infra
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
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.
Note: 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.
Extending the Domain for SOA Components 5-15
SOA inspection.wsil Location inspection.wsil
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
Worklist Location integration
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
B2B Location b2bconsole
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
UMS prefs Location sdpmessaginguserprefs-ui
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
Default to-do taskflow Location DefaultToDoTaskFlow
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
Workflow Location workflow
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
UMS parlay Location sdpmessagingparlayx
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
UMS WS Location ucsmessagingwebservice
SetHandler weblogic-handler
5-16 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter
WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001 WLProxySSL ON
WLProxySSLPassThrough ON Location
Required if attachments are added for workflow tasks Location ADFAttachmentHelper
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
SOA composer application Location soacomposer
SetHandler weblogic-handler WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
WLProxySSL ON WLProxySSLPassThrough ON
Location
2.
Restart Oracle HTTP Server on WEBHOST1 and WEBHOST2: WEBHOST1 ORACLE_BASEadmininstance_namebinopmnctl restartproc
ias-component=ohs1 WEBHOST2 ORACLE_BASEadmininstance_namebinopmnctl restartproc
ias-component=ohs2
The servers specified in the WebLogicCluster parameter are only important at startup time for the plug-in. The list needs to provide at least one running cluster
member for the plug-in to discover other members of the cluster. Note that the listed cluster member must be running when
Oracle HTTP Server
is started. Oracle WebLogic Server and the plug-in work together to update the server list automatically
with new, failed, and recovered cluster members. Sample scenarios:
■
Example 1: If you have a two-node cluster and then add a third member, you do not need to update the configuration to add the third member. The third member
will be discovered on the fly at runtime.
■
Example 2: You have a three-node cluster but only two nodes are listed in the configuration. However, if both listed nodes are down when you start Oracle
HTTP Server, then the plug-in would fail to route to the cluster. You must ensure that at least one of the listed nodes is running when you start Oracle HTTP Server.
If you list all members of the cluster, then you guarantee you can route to the cluster, assuming at least one member is running when Oracle HTTP Server is
started.
For more information on configuring the WebLogic Server plug-in, see the Oracle Fusion Middleware Using Web Server Plug-Ins with Oracle WebLogic Server guide.
Note: The entry for workflow is optional. It is for workflow tasks
associated with ADF task forms. The workflow URL itself can be a different value, depending on the form.
Extending the Domain for SOA Components 5-17
5.16 Validating Access Through
