My Oracle Support Banner

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, 2023

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.

Goal

Important:
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:

11g:
<Note 1569732.1> How to Terminate SSL at Load Balancer, Web Cache or OHS 11g - Including Steps for WLS Plugin (mod_wl_ohs)

12c:
Oracle Fusion Middleware Administering Oracle HTTP Server 12c (12.1.3)
8.6 Terminating SSL Requests
https://docs.oracle.com/middleware/1213/webtier/administer-ohs/man_logs.htm#HSADM1265

Oracle Fusion Middleware Administering Oracle HTTP Server 12c (12.2.1)
8.7 Terminating SSL Requests
https://docs.oracle.com/middleware/12213/webtier/administer-ohs/security.htm#HSADM1327
AND
<Note 2269377.1> How to Configure SSL to Terminate at Oracle HTTP Server Release 2 (12.2.1)? - with Oracle Forms Example


10g

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
or
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
or
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.

 



Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Basic Setup of Oracle HTTP Server for ServerName, Listen, and Port
 Virtual Hosting with Oracle HTTP Server
 SSL Terminated at Oracle Web Cache or Load Balancer - SSL Accelerator
 Oracle Application Server 10g Specific Information
 Configuring Oracle Application Server 10g Components for Address Changes
 After Any Address Change, Always Ensure SSO is Working First
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.