Best Practices for Managing OC4J Dynamic Port Allocations via OPMN
(Doc ID 1392636.1)
Last updated on OCTOBER 12, 2020
Applies to:Oracle Containers for J2EE - Version 184.108.40.206.0 to 10.1.3.5.0 [Release 9iAS to AS10gR3]
Information in this document applies to any platform.
Over and above the static allocation of HTTP, RMI and JMS ports supported by
"standalone" instances of Oracle Containers for J2EE (OC4J), when running in
the fuller, enterprise facing context of Oracle Application Server (9iAS & 10g AS)
these assignments are made dynamically as the OC4J instance is started.
Whilst this additional flexibility is highly beneficial to any application
wishing to exploit AS features for improved scalability and availability,
this can be less convenient for simpler applications coded to use a fixed RMI
or JMS port.
This document suggests some best practices for managing the range of AJP, RMI
and JMS port assignments that the Oracle Process Manager (OPMN) component
within AS releases (9.0.3.x to 10.1.3) will assign to OC4J instances.
The documented is intended for AS system administrators as well as J2EE
application developers and deployers who would need to be aware of the actual
port values (AJP/RMI/JMS) assigned to OC4J instances at runtime.
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