The opmn.xml File 3-1
3
The opmn.xml File
This chapter provides an overview of the opmn.xml file for Oracle Fusion Middleware. It features the following topics:
■
opmn.xml
■
Automatic Restart
■
OPMN Log Files
■
Security
■
IPv6 Support
3.1 opmn.xml
The ORACLE_INSTANCEconfigOPMNopmnopmn.xml file is the main configuration file for OPMN. The opmn.xml file contains information for PM and
system component specific configuration. The opmn.xml file shows you which system components OPMN is managing on your system.
The opmn.xml file is divided into three main sections: log files, notification-server, and process-manager.
■
log files : The log files configuration by default fully enables the standard log but
disables the debug log
■
notification server:
The notification-server configuration includes the OPMN listener ports as well as secure connection definition. Optional topology
opmn.xml file element can be manually added for OPMN discovery.
■
process manager
: The process-manager configuration includes all information required for each managed component.
The opmn.xml file does not contain component-specific element names. Component specific management code is located in the PM modules which are loaded by OPMN
at startup according to what has been specified in the modules section of the opmn.xml file.
Each level has a specific set of configurations. In addition, there are several configuration elements that are accepted at more than one level to provide the
flexibility of applying a configuration across an entire system component or just part of a component.
ias-component process-type
process-set
3-2 Oracle Fusion Middleware Oracle Process Manager and Notification Server Administrators Guide
ias-component: This entry represents the system component. It enables management of the component for processes such as starting and stopping.
process-type: This subcomponent of the ias-component entry declares the type of process to run by association with a specific PM module.
process-set: This sub-subcomponent of the ias-component entry enables you to declare different sets of optional runtime arguments and environments for the
system component. process-set is an optional configuration element.
The opmn.xml file contains system component entries arranged in the hierarchical structure shown in the following
Example 3–1 .
Example 3–1 Element Entries in opmn.xml File
ias-component id=ohs1 process-type id=OHS
process-set id=OHS....
3.2 Automatic Restart
OPMN gives the user control over automatic death detection and restart of components; you can configure the parameters by which OPMN determines a process
has died and disable automatic restart for individual components.
OPMN monitors the operation of its managed processes by the following methods:
■
Operating system level detection of system process death
■
Periodic ping requests to system processes
■
Periodic status notification from system processes reverse-ping The ping and notification functionality is only used where appropriate according to
the functionality of the system component. OPMN automatically restarts system components that terminate unexpectedly. OPMN
also restarts processes that are unresponsive according to the result of notification and ping operations.
3.3 OPMN Log Files
The log files generated by OPMN provide important information that can help you identify and diagnose performance and configuration issues. The Fusion Middleware
Control Console makes reviewing these log files easier by helping you locate and view system component log files.
See Also: Chapter 6
for more information about the common configuration of the opmn.xml file.
See Also:
■
Oracle Fusion Middleware Administrators Guide for additional diagnostic utilities
■
Section B.2.1 for more information about OPMN log files
The opmn.xml File 3-3
