How To Limit /Restricting Acess To Deployed Applications With Enabling OC4J Mount Static Routing
(Doc ID 551725.1)
Last updated on AUGUST 20, 2019
Applies to:Oracle HTTP Server - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
- How To Create Virtual Host Specific for OC4J Applications and get the EM/ ASControl working for specific Virtual Hosts only. As found that in Oracle Application Server 10g Release 3 (10.1.3.x.x), OC4JMount is configured dynamically by default to assign the requested application an OC4J to serve the request.
- This note is also concerned for achieving the creation of virtual hosts and restricting access to deployed applications for specifics virtual hosts while applying oc4j mount static routing to manually control and balance the load of applications on the current available OC4Js instances. The way to achieve this is to apply the OC4J static routing instead of dynamic one. and this could be done using "Oc4jRoutingMode Static".
- By applying this configuration , you will have to start using "static" mount points, which has some consequences.
One of the consequences is that without defining a static mount point to EM ( enterprise manager application ) that application will not be working (and access to http://host:port/em will not work ). This EM failure is expected because of using "Oc4jMountCopy off" which will remove all the dinamically defined mount points.
The second of the consequences is that new deployed applications will require you to manually add the Oc4jMount rule for them in the appropiate VirtualHost, because the deployment process will not make that for you.
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