OPMN or Oracle Process Monitor and Notification server is used to stop, start and get process status.
The standalone agent is a standalone Java process started from a command line interface. This agent is typically deployed locally on the source or target machines for optimal integration flow performances. You can use OPMN to start, stop and protect the standalone agent in this situation.
To add a standalone agent to OPMN, edit the agentcreate.properties
contained in the ODI_HOME/oracledi/agent/bin/
directory to match your agent and OPMN configuration.
Note:
When editing theagentcreate.properties
file, you must use a forward slash (/) as a path seperator for both UNIX and Windows operating systems.See Table I-1 for a list of
agentcreate.properties
parameters. Note that the examples shown may differ from your system configuration.
Table I-1 Parameters in agentcreate.properties
Parameter | Description | Example (Your Configurations May Differ) |
---|---|---|
|
Startup port of the agent (as in agent.bat command line |
|
|
JMX port of the agent (agent.bat command line |
|
|
Location of the JVM used by the agent |
|
|
OPMN installation directory |
|
|
Installation path of ODI |
|
|
Location of the OPMN instance into which the agent should be added |
|
|
type of the component (should be odiagent) |
|
|
name of the agent to add. This will be its identification in OPMN |
|
Run the script to add this agent to the OPMN configuration.
For UNIX operating systems:
ODI_HOME/oracledi/agent/bin/opmn_addagent.sh
For Windows operating systems:
ODI_HOME/oracledi/agent/bin/opmn_addagent.bat
To stop all agent components in an Oracle instance using opmnctl
opmnctl stopproc process-type= odiagent
To stop a specific agent component, such as odiagent1, using opmnctl
opmnctl stopproc ias-component= odiagent1
To start all agent components in an Oracle instance using opmnctl:
opmnctl startproc process-type= odiagent
To start a specific agent component, such as odiagent1, using opmnctl:
opmnctl startproc ias-component=odiagent1