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

Last updated on FEBRUARY 16, 2017

Applies to:

Oracle HTTP Server - Version: 10.1.3.0.0 to 10.1.3.5.0 - Release: AS10gR3 to AS10gR3
Oracle Containers for J2EE - Version: 10.1.3.0.0 to 10.1.3.5.0   [Release: AS10gR3 to 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 <>, 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:
<> 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:

  • We have the application App1 with context root /app1 deployed in an OC4J instance called blue and an application App2 with context root /app2 deployed in an OC4J instance called red.

  • We want users to access the App1 application using the URL http://myhost.mydomain:3456/app1 and the App2 application using the URL http://myhost.mydomain:7890/app2 , but we don't want the users to be able to access /app2 through port 3456 nor /app1 through port 7890.

    Note: The same example can be adapted to use name based virtualhosts, e.g. http://myname1.mydomain/app1 and http://myname2.mydomain/app2 . Just the VirtualHost definition in STEP III needs to be modified.



Solution

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