Configuring Development and Test Environments Containing Independent OC4J Instances in Application Server 10g R3 (10.1.3.1)
(Doc ID 433297.1)
Last updated on AUGUST 20, 2020
Applies to:Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]
Oracle Fusion Middleware - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]
Oracle HTTP Server - Version 10.1.3.1.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.
Explain the changes introduced in Application Server 10g R3 (10.1.3.1) that allow for the creation of multiple independent OC4J instances. Version 10.1.3.1 exposes the ability to configure OPMN managed OC4J in a full Application Server installation to listen directly for the HTTP protocol. This differs from earlier releases where this functionality was only available in Standalone OC4J.
During development and testing this can be used for deploying different versions of the same Application to separate OC4J instances running from the same ORACLE_HOME. Even though the applications may share the same Web Context Root, they are independently addressable because they are accessed directly on their own HTTP ports.
This document is informational and intended for any Application Server administrator/developer with a non production cluster topology that includes Oracle HTTP Server and multiple OC4J Instances.
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