OPMN

OPMN(Oracle Process Manager and Notification Server)

R12 uses 10.1.3 fusion middle-ware AS stack, hence services in R12 is managed by OPMN(Oracle Process Manager and Notification Server).

OPMN COMPONENTS

OPMN consists of two main components 1) Oracle Process Manager 2) Oracle Notification Server

Oracle Process Manager is responsible for : 1) starting 2) stopping 3) restarting 4) monitoring the services it manages (this includes death detection and automatic restart of the process) Oracle Notification Server is the transport mechanism for failure, recovery, startup, and other related notifications between components in AS.

OPMN.XML
Single configuration file(opmn.xml) is used OPMN to manage the services. Config file location is given as $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml
http://docs.oracle.com/cd/B13597_05/core.904/b12057/common.htm#CACHJAGG

OPMN SERVICES
Services managed by opmn are (grep process-type opmn.xml) 1) HTTP_Server 2) oacore 3) forms

4) oafm Getting OPMN managed running process(es) status ===============================================================================

[apdev@catos-nrapdcl02 conf]$ adopmnctl.sh status You are running adopmnctl.sh version 120.6.12010000.5 Checking status of OPMN managed processes... Processes in Instance: DEV_catos-nrapdcl02.catos-nrapdcl02.mdsinc.com ---------------------------------+--------------------+---------+--------ias-component | process-type | pid | status ---------------------------------+--------------------+---------+--------OC4JGroup:default_group | OC4J:oafm | 21936 | Alive OC4JGroup:default_group | OC4J:forms | 21085 | Alive OC4JGroup:default_group | OC4J:oacore | 2052 | Alive HTTP_Server | HTTP_Server | 2160 | Alive adopmnctl.sh: exiting with status 0

===========================================================================================

Starting OPMN managed Services

Starting Complete OC4J container bash-2.05$ ./adopmnctl.sh startproc ias-component=OC4J Starting individual process-type(s) bash-2.05$ ./adopmnctl.sh startproc ias-component=OC4J process-type= oafm bash-2.05$ ./adopmnctl.sh startproc ias-component=OC4J process-type= forms bash-2.05$ ./adopmnctl.sh startproc ias-component=OC4J process-type= oacore Starting HTTP Server (Apache) bash-2.05$ ./adopmnctl.sh startproc ias-component=HTTP_Server

Stoping OPMN managed Services

Stoping Complete OC4J container bash-2.05$ ./adopmnctl.sh stopproc ias-component=OC4J Stoping individual process-type(s) bash-2.05$ ./adopmnctl.sh stopproc ias-component=OC4J process-type= oafm bash-2.05$ ./adopmnctl.sh stopproc ias-component=OC4J process-type= forms bash-2.05$ ./adopmnctl.sh stopproc ias-component=OC4J process-type= oacore Stoping HTTP Server (Apache) bash-2.05$ ./adopmnctl.sh stopproc ias-component=HTTP_Server

Benefits of OPMN
OPMN detects the death of the process which it manages and brings up in almost no time. 1) OS process is checked by OPMN for every 2 seconds. 2) forward ping: periodically OPMN pings the process for every 20 seconds and expects response 3) reverse ping: every 20 seconds managed process sends OPMN a ping notification