http://docs.oracle.com/cd/E29597_01/doc.1111/e15483/extend_ucm.htm
10.14 Configuring Oracle HTTP Server for the WLS_WCC Managed Servers
To enable Oracle HTTP Server to route to WCC_Cluster, which contain the WLS_WCC1 and WLS_WCC2 managed servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster:
On WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_BASE/admin/instance_name/config/OHS/component_name/mod_wl_ohs.conf file:
# UCM
<Location /cs>
WebLogicCluster 192.138.1.161:16200,192.168.1.161:16200
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
<Location /adfAuthentication>
WebLogicCluster 192.138.1.161:16200,192.168.1.161:16200
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
<Location /_ocsh>
WebLogicCluster 192.138.1.161:16200,192.168.1.161:16200
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
<Location /console>
WebLogicCluster 192.138.1.161:7001,192.168.1.161:7001
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2:
ORACLE_BASE/admin/instance_name/bin/opmnctl restartproc ias-component=ohsX
For WEBHOST1, use ohs1 for ias-component and for WEBHOST2 use ohs2.
10.15 Validating Access Through Oracle HTTP Server
You should verify URLs to ensure that appropriate routing and failover is working from Oracle HTTP Server to WCC_Cluster. To verify the URLs:
While WLS_WCC2 is running, stop WLS_WCC1 using the WebLogic Server Administration Console.
Access http://WEBHOST1:7777/cs to verify it is functioning properly.
Start WLS_WCC1 from the WebLogic Server Administration Console.
Stop WLS_WCC2 from the WebLogic Server Administration Console.
Access http://WEBHOST1:7777/cs to verify it is functioning properly.
10.14 Configuring Oracle HTTP Server for the WLS_WCC Managed Servers
To enable Oracle HTTP Server to route to WCC_Cluster, which contain the WLS_WCC1 and WLS_WCC2 managed servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster:
On WEBHOST1 and WEBHOST2, add the following lines to the ORACLE_BASE/admin/instance_name/config/OHS/component_name/mod_wl_ohs.conf file:
# UCM
<Location /cs>
WebLogicCluster 192.138.1.161:16200,192.168.1.161:16200
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
<Location /adfAuthentication>
WebLogicCluster 192.138.1.161:16200,192.168.1.161:16200
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
<Location /_ocsh>
WebLogicCluster 192.138.1.161:16200,192.168.1.161:16200
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
<Location /console>
WebLogicCluster 192.138.1.161:7001,192.168.1.161:7001
SetHandler weblogic-handler
WLCookieName JSESSIONID
WLProxySSL ON
WLProxySSLPassThrough ON
</Location>
Restart Oracle HTTP Server on both WEBHOST1 and WEBHOST2:
ORACLE_BASE/admin/instance_name/bin/opmnctl restartproc ias-component=ohsX
For WEBHOST1, use ohs1 for ias-component and for WEBHOST2 use ohs2.
10.15 Validating Access Through Oracle HTTP Server
You should verify URLs to ensure that appropriate routing and failover is working from Oracle HTTP Server to WCC_Cluster. To verify the URLs:
While WLS_WCC2 is running, stop WLS_WCC1 using the WebLogic Server Administration Console.
Access http://WEBHOST1:7777/cs to verify it is functioning properly.
Start WLS_WCC1 from the WebLogic Server Administration Console.
Stop WLS_WCC2 from the WebLogic Server Administration Console.
Access http://WEBHOST1:7777/cs to verify it is functioning properly.
No comments:
Post a Comment