My Oracle Support Banner

How To Restrict Web Application Access By VirtualHost Using Dynamic Mount Points (Doc ID 739881.1)

Last updated on AUGUST 19, 2019

Applies to:

Oracle HTTP Server - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
Checked for relevance on 14-Apr-2011


Goal

The goal of this note is to provide an step-by-step guide to implement access restriction to an application based on virtual hosts as described in <note 389819.1>, but this time using the dynamic mount points provided in Oracle Application Server 10g Release 3 (10.1.3), i.e. avoiding the use of Oc4jMount directives.

Reference:
<Note 389819.1> How To Create Virtual Host Specific OC4J Applications


Added functionality in version 10.1.3 allows us to minimize the Oracle HTTP Server downtime as new applications can be dynamically discovered once deployed, giving us more flexibility. This document implements the following scenario:



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
 STEP I: Modify $ORACLE_HOME/Apache/Apache/conf/mod_oc4j.conf
 STEP II: Modify the $ORACLE_HOME/opmn/conf/opmn.xml file
 STEP III: Create the Virtual Host Definitions
 STEP IV: Restart Application Server Components and Test /oc4j-status
 STEP V: Verify the Configuration Works as Desired
References

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