This section includes the following topics:
When Oracle WebCenter Portal components are running on Oracle WebLogic Server, you can set Oracle HTTP Server (OHS) as the frontend to Oracle WebLogic Server. Some scenarios that require OHS as the frontend are:
For OSSO to function properly between Site Studio and Oracle Content Server. This is achieved through mod_osso of OHS.
The adequate distribution of load across the Oracle WebLogic Server cluster nodes. This is achieved through mod_wl of OHS.
OHS is required for OAM's WebGate component.
OHS is used as a reverse proxy.
In these cases, you must configure the mod_wl_ohs module to allow requests to be proxied from an OHS to Oracle WebLogic Server.
The default location of the mod_wl_ohs.conf file is: OHS_HOME/Oracle_WT1/instances/instance1/config/OHS/ohs1/mod_wl_ohs.conf. After you have configured the mod_wl_ohs module using the Fusion Middleware Control, the file mod_wl_ohs.conf file looks similar to the following sample code:
# WebCenter Portal Application <Location /webcenter> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8888 </Location> <Location /webcenterhelp> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8888 </Location> <Location /rss> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8888 </Location> <Location /rest> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8888 </Location> # Discussions <Location /owc_discussions> SetHandler weblogic-handler WeblogicHost discuss.example.com WeblogicPort 8890 </Location> # SES Search <Location /rsscrawl> SetHandler weblogic-handler WeblogicHost ses.example.com WeblogicPort 7777 </Location> <Location /sesUserAuth> SetHandler weblogic-handler WeblogicHost ses.example.com WeblogicPort 7777 </Location> # Portlets <Location /portalTools> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8889 </Location> <Location /wsrp-tools> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8889 </Location> <Location /pagelets> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8889 </Location> # UCM # Web server context root for Oracle WebCenter Content Server <Location /cs> SetHandler weblogic-handler WeblogicHost ucm.example.com WeblogicPort 16200 </Location> # Enables Oracle WebCenter Content Server authentication <Location /adfAuthentication> SetHandler weblogic-handler WeblogicHost ucm.example.com # Same as /cs entry WeblogicPort 16200 # Same as /cs entry </Location> # SAML SSO <Location /samlacs/acs> SetHandler weblogic-handler WeblogicHost ucm.example.com WeblogicPort 16200 </Location> # BPEL Server <Location /workflow> SetHandler weblogic-handler WeblogicHost soa.example.com WeblogicPort 8001 </Location>
SSL Directives
If you have configured SSL, then the following additional directives are required:
WLProxySSL ON
WLProxySSLPassThrough ON
For example, mod_wl_ohs.conf entries with SSL directives looks like the following:
# WebCenter Portal Application <Location /webcenter> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8888 WLProxySSL ON WLProxySSLPassThrough ON </Location> <Location /webcenterhelp> SetHandler weblogic-handler WeblogicHost webcenter.example.com WeblogicPort 8888 WLProxySSL ON WLProxySSLPassThrough ON </Location> ...
Frontend Listening Host and Frontend Listening Port
If the Oracle HTTP Server (OHS) frontend is also the site entry point, use the Oracle WebLogic Server Administration Console to set the FrontEnd Host and FrontEnd HTTP Port for each server that uses the OHS frontend.
Configuring an Error Page for a Cluster
Include the ErrorPage parameter in mod_wl_ohs.conf as follows:
<Location /webcenter>
WebLogicCluster
app1.mycompany.com:8888,app2.mycompany.com:8888,app3.company.com:8888
SetHandler weblogic-handler
ErrorPage http://mycompany.com/error.html
</Location>
Users are redirected to http://company.com/error.html if all the WC_Portal managed servers are down. When any managed server comes back online, users access WebCenter Portal as normal.