1 What's New in OPMN?

Integration with Oracle Instance

Each ORACLE_HOME can support multiple instances, each with its own configuration and diagnostic directory tree (ORACLE_INSTANCE). OPMN now operates from within an ORACLE_INSTANCE.

There are two basic subdirectories within the ORACLE_INSTANCE base directory: ORACLE_INSTANCE/config and ORACLE_INSTANCE/diagnostics/logs. Within each of these two directories each component has a specific directory tree with the format: component type/component name where component type is either the OPMN type value configured for the ias-component or the process-type id for the component, and component name is the id value configured for the ias-component.

For example, the default Oracle HTTP Server (OHS) install log configuration directory would therefore be:

ORACLE_INSTANCE/config/OHS/ohs1 (UNIX)

ORACLE_INSTANCE\config\OHS\ohs1 (Microsoft Windows)

The OPMN component type is always OPMN and component name is always opmn.

Support with Oracle WebLogic Server

<There is OPMN support on the admin server, which runs as a remote WebLogic Server, and perhaps something should be added here about that.> See the document scoped notes for an overview and details about OPMN and WebLogic

In most Oracle Fusion Middleware installations an Oracle instance is associated with a Oracle WebLogic Server domain for management of system components using the Oracle Enterprise Manager Fusion Middleware Control Console (Fusion Middleware Control Console). In these deployments, OPMN is integrated with the WebLogic domain to provide remote management of system components.

Unlike prior releases of Oracle Fusion Middleware, OPMN not only manages system components in the local Oracle instance but it is also integrated with the WebLogic domain to provide remote system component management using either the Fusion Middleware Control Console and or the WLST command line.