How to Configure Virtual Hosts on Oracle HTTP Server 10g for LBR Access or SSL Termination
(Doc ID 378003.1)
Last updated on MAY 01, 2018
Applies to:Oracle HTTP Server - Version 1.0.2 to 10.1.3.5.0 [Release 9iAS to AS10gR3]
Oracle Fusion Middleware - Version 10.1.2.0.2 to 10.1.4.3.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.
This document was written and tested with Oracle Application Server 10g use cases. The basic concepts apply to Oracle Fusion Middleware 11g and some updates have been made where a distinct change is required. This document will not transition into an 11g/12c document and it may be confusing to include information for all versions.
Update for new releases:
<Note 1569732.1> How to Terminate SSL at Load Balancer, Web Cache or OHS 11g - Including Steps for WLS Plugin (mod_wl_ohs)
Oracle Fusion Middleware Administering Oracle HTTP Server 12c (12.1.3)
8.6 Terminating SSL Requests
Oracle Fusion Middleware Administering Oracle HTTP Server 12c (12.2.1)
8.7 Terminating SSL Requests
<Note 2269377.1> How to Configure SSL to Terminate at Oracle HTTP Server Release 2 (12.2.1)? - with Oracle Forms Example
In this example, a Load Balancer (LBR) forwards requests to either Oracle HTTP Server (OHS), or through Oracle Web Cache (WC) to Oracle HTTP Server. The use of two external names forwarding to two different Oracle HTTP Server ports is desired. This document explains the basic concepts in order to gain an understanding, and use an example configuration to set up virtual hosts. In this case, a LBR is used like a "reverse-proxy", only forwarding requests. There is no actual "load balancing" being configured in this article.
If using an LBR as a network entry point, this article provides the following example request flow:
User --> LBR --> OHS
User --> LBR --> WebCache --> OHS
There are other topologies that do not use a LBR, and are very similar in respect to the destination Oracle HTTP Server. (e.g., Including the default installed, User --> WebCache --> OHS). The following is an example where an apache-based reverse-proxy (RP) is used in front of the destination Oracle HTTP Server:
User --> Apache-RP --> OHS
User --> OHS-RP --> OHS
<Note:314381.1> How to Setup Oracle HTTP Server as a Virtual Host Reverse Proxy
The basic virtual host concepts are derived from this document, as well:
<Note 293697.1> Preparing and Configuring Virtual Hosts on Oracle Application Server 10g
It is important to understand your needs, your desired topology and request flow before deciding which actions to follow. Its equally important to understand the components in use with the an Oracle Fusion Middleware installation. Configuring for such topologies can create a need to re-configure other components because the protocol:name:port has changed. This article only configures the Oracle HTTP Server in a given topology. The Oracle HTTP Server must work before all else, but please plan for other component changes and testing.
- General VirtualHost Setup
The first part of this article steps through the basic configuration and testing of Apache-based Virtual Hosts, and the need to ensure they are independently accessible before using them for your application processing. It is often a hard problem to troubleshoot the application processing through a VirtualHost, if the cause is because of "virtual host overlap", where the request(s) do not use the intended VirtualHost.
- Ensure HTTPS Responses
The second part of this article gives an example usage of the virtual hosting, as applied to "terminating SSL". Then, a basic outline for other Oracle Application Server steps to perform because of the address change.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!