Weblogic - OPMN (Opmnctl) - System component manager
Table of Contents
About
OPMN is a process management tool that:
- manages the system components (such as Oracle Business Intelligence)
- supports both local and distributed process management, automatic process recycling, and the communication of process state (up, down, starting, stopping).
OPMN detects process unavailability and automatically restarts processes.
Fusion Middleware Control is the recommended approach for starting, stopping, and viewing the status of components. However, following a reboot on Linux you must use the opmnctl start, or startall command. OPMN is suitable only for advanced users.
OPMN provides the following functionality to manage the Oracle Business Intelligence system components:
- A command-line interface (opmnctl) for advanced users to control Oracle Fusion Middleware components.
- Automatic restart of processes when they become unresponsive or terminate unexpectedly.
- An integrated way to manage Oracle Fusion Middleware components.
The main configuration file for OPMN is opmn.xml.
Articles Related
Opmnctl
Where it is ?
In the midellware stack,The OPMN command line control script 'opmnctl' resides in
ORACLE_HOME/opmn/bin
and
ORACLE_INSTANCE/bin
You can run 'opmnctl' from either directory, but if you use the ORACLE_HOME/opmn/bin location you must set the ORACLE_INSTANCE environment variable.
set ORACLE_INSTANCE=E:\MiddelwareHome\instances\instance1\
How to start the process OPMN in background
- from the command line:
opmnctl start
- or start the windows service “Oracle Process Manager (instance1)”
Command
Help
./opmnctl help
usage: opmnctl [verbose] [<scope>] <command> [<options>]
verbose: print detailed execution message if available
Permitted <scope>/<command>/<options> combinations are:
scope command options
------- --------- ---------
start - Start opmn
startall - Start opmn & all managed processes
stopall - Stop opmn & all managed processes
shutdown - Shutdown opmn & all managed processes
[<scope>] startproc [<attr>=<val> ..] - Start opmn managed processes
[<scope>] restartproc [<attr>=<val> ..] - Restart opmn managed processes
[<scope>] stopproc [<attr>=<val> ..] - Stop opmn managed processes
[<scope>] reload - Trigger opmn to reread opmn.xml
[<scope>] status [<options>] - Get managed process status
[<scope>] metric [<attr>=<val> ..] - Get DMS metrics for managed processes
[<scope>] dmsdump [<dmsargs>] - Get DMS metrics for opmn
[<scope>] debug [<attr>=<val> ..] - Display opmn server debug information
[<scope>] set [<attr>=<val> ..] - Set opmn log parameters
[<scope>] query [<attr>=<val>] - Query opmn log parameters
launch [<attr>=<val> ..] - Launch a configured target process
phantom [<attr>=<val> ..] - Register phantom processes
ping [<max-retry>] - Ping local opmn
validate [<filename>] - Validate the given opmn xml file
help - Print brief usage description
usage [<command>] - Print detailed usage description
createinstance - Create an Oracle Instance
createcomponent - Create a specified component
deleteinstance - Delete an instance and components
deletecomponent - Delete a specified component
registerinstance - Register with admin server
redeploy - Redeploy the admin server application
unregisterinstance - Unregister with admin server
updateinstanceregistration - Update instance registration
updatecomponentregistration - Update component registration
Process Management
To start, stop, restart, and view the status of Oracle Business Intelligence system components on the Managed Server:
- verfiy that the bi_server1 (Managed Server) is running.
- go to the following directory: ORACLE_INSTANCE/bin
- Run the OPMN tool using the appropriate opmnctl command (for UNIX use the command ./opmnctl).
Command | Description |
---|---|
opmnctl status | Shows the component names and the status of all system components |
opmnctl startall | Starts OPMN and all Oracle Business Intelligence system components. |
opmnctl start | Starts OPMN only |
opmnctl startproc ias-component= <component_name> | Starts a particular system component. For example, where coreapplication_obips1 is the Oracle BI Presentation Server: opmnctl startproc ias-component=coreapplication_obips1 |
opmnctl stopall | Stops all managed system components |
opmnctl stopproc ias-component= <component_name> | Stops a particular system component |
opmnctl restartproc ias-component= <component_name> | Restarts a particular system component |
opmnctl shutdown | Stops opmn and all managed system components |
The component name can be get with the status command:
opmnctl status
Processes in Instance: instance1
---------------------------------+--------------------+---------+---------
ias-component | process-type | pid | status
---------------------------------+--------------------+---------+---------
coreapplication_obiccs1 | OracleBIClusterCo~ | 5868 | Alive
coreapplication_obisch1 | OracleBIScheduler~ | 4616 | Alive
coreapplication_obijh1 | OracleBIJavaHostC~ | 2116 | Alive
coreapplication_obips1 | OracleBIPresentat~ | N/A | Down
coreapplication_obis1 | OracleBIServerCom~ | 5892 | Alive
The pid correspond to the process number and you can then retrieve the following executables:
- nqsclustercontroller.exe
- nqscheduler.exe
- java.exe
- nqsserver.exe
- sawserver.exe
Metrics
The opmcntl application can also be used to retrieve Dms Metrics for monitoring purpose: Weblogic - How to get DMS metrics with Opmnctl ?
Support
Verbose
The opmnctl verbose option enables you to obtain detailed information about the command you are executing.
opmnctl verbose command
log
opmn.log | ORACLE_INSTANCE\diagnostics/logs/OPMN/opmn |
debug.log | ORACLE_INSTANCE\diagnostics/logs/OPMN/opmn |
logquery.log | ORACLE_INSTANCE\diagnostics/logs/OPMN/opmn |
service.log | ORACLE_INSTANCE\diagnostics/logs/OPMN/opmn |
opmn.out | ORACLE_INSTANCE\diagnostics/logs/OPMN/opmn |