How to Configure mod_wl_ohs with Oracle HTTP Server and Oracle WebLogic Server
Last updated on JUNE 16, 2017
Applies to:Oracle WebLogic Server - Version 10.3.2 and later
Oracle HTTP Server - Version 184.108.40.206.0 and later
Oracle Fusion Middleware - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Originally written for 11g but also applies to 12c. See Documentation links at bottom.
Oracle HTTP Server (OHS) may be used in front of Oracle WebLogic Server (WLS) with the use of the Oracle Fusion Middleware 11g/12c installed mod_wl_ohs. This document will outline the basic steps to set this up using a standard and best practice configuration. Once this is working, you can configure more advanced configurations and/or configure using the Oracle Fusion Middleware Control.
This document will guide you to a standard setup using a single instance and a cluster for use with custom Java applications deployed on Oracle WebLogic Server. Different installation types may have this configured for you, but on the basic level (or on an Oracle Web-Tier installation), it is not configured by default and you should know how the different parts work together and different options.
- This document is for the configuration of the OHS 11g/12c with the Oracle HTTP Server 11g/12c installed mod_wl_ohs. In 11g, this is also referred to as WLS Plugin 1.1, but also 11.1.1.x. It is important to differentiate the products and plugins to avoid crossing over the intended usage. Known compatibility issues can arise between OHS/Apache, Plug-In module, and WLS versions.
- When using WLS with generic Apache 2.2, the correct module to use is mod_wl from the WLS Plug-In 1.1 distribution, (and is downloadable as an 11.1.1.x or 12.1.x version to align with FMW releases). If you are using Apache 2.0, use mod_wl_20 from the WLS Plug-In 1.0 distribution. (See <Note 1111903.1>).
Direction of Support
- MOD_PROXY: It would not be supported to use mod_proxy with OHS or Apache to process applications deployed to Oracle WebLogic Server. Use OHS/mod_wl_ohs or Apache/mod_wl. In addition, it is recommended to configure the WLS modules to use existing features such as MatchExpression, PathTrim, or PathPrepend instead of mod_rewrite (which uses mod_proxy). Other features not available with the WLS Proxy Plug-In, (e.g. rewrite rules and redirection) are more effectively handled before reaching the WLS Proxy Plug-In Location handler.
- OHS 10g: It would not be certified/supported to use mod_wl_ohs or mod_wl with OHS 10g. If you are using OC4J and WLS applications, the recommendation is to maintain two Oracle HTTP Server installations until the migration to 11g or 12c is completed.
- 11g/12c MIX: For information on the certification/compatibility between mixed 11g/12c environments, see <Note 1576554.1>, "Oracle Fusion Middleware Certification/Compatibility Between 11g and 12c". Note however this is by having OHS 11g or 12c in front of another WLS 10.3.6 or 12c installation. It is not supported to interchange the module files within OHS (e.g., update files from another 11.1.1.x version to another, or use WLS Plugin files designed for Apache on OHS). The updates of mod_wl_ohs must be done by applying a Patch Set or one-off patch (via OPatch) to OHS. There are new dependencies beginning with WLS Plugin 1.1/11.1.1.x versions.
- 12c: This document was originally written for 11g where the Oracle Documentation was originally missing for mod_wl_ohs. Doc Bugs have been filed and some information has been added for 11g. Since the module works the same way in 12c, the instructions within are also applicable to 12c, but please refer to the 12c Oracle Documentation and report issues accordingly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms