H OPMN Configuration for Standalone Agent

Oracle Process Monitor and Notification server (OPMN) 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.

H.1 Adding a Standalone Agent to OPMN

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 the agentcreate.properties file, you must use a forward slash (/) as a path separator for both UNIX and Windows operating systems.

See Table H-1 for a list of agentcreate.properties parameters. Note that the examples shown may differ from your system configuration.

Table H-1 Parameters in agentcreate.properties

Parameter Description Example (Your Configurations May Differ)

PORTNO

Startup port of the agent (as in agent.bat command line

PORTNO=9787

JMXPORTNO

JMX port of the agent (agent.bat command line

JMXPORTNO=9787

JAVA_HOME

Location of the JVM used by the agent

JAVA_HOME=/scratch/username/Oracle_ODIMAIN/Middleware/jdk160_11

ORACLE_OPMN_HOME

OPMN installation directory

ORACLE_OPMN_HOME=/scratch/username/oracle/product/11.1.1/as_1

ORACLE_ODI_HOME

Installation path of ODI

ORACLE_ODI_HOME=/scratch/username/odi_standalone

INSTANCE_HOME

Location of the OPMN instance into which the agent should be added

INSTANCE_HOME=/scratch/username/oracle/product/11.1.1/as_1/instances/instance1

COMPONENT_TYPE

Type of the component (should be odiagent)

COMPONENT_TYPE=odiagent

COMPONENT_NAME

Name of the agent to add. This will be its identification in OPMN

COMPONENT_NAME=INTERFACE

ODI_MASTER_DRIVER

JDBC driver used to connect the Master Repository.

ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver

ODI_MASTER_URL

JDBC URL used to connect the Master Repository.

ODI_MASTER_URL=jdbc:oracle:thin:adc6260039:1521:orcl

ODI_MASTER_USER

Database account used to connect the Master Repository.

ODI_MASTER_USER=SUPERVISOR

ODI_MASTER_ENCODED_PASS

Database account password. The password must be encoded with the "encode.[sh|bat] <password>" command.

ODI_MASTER_ENCODED_PASS=hpfatLEoMR6zAK3T1PoP5LXDS

ODI_SECU_WORK_REPO

Name of the Work Repository to connect. This Work Repository must be attached to the master repository.

ODI_SECU_WORK_REPO=WORKREP

ODI_SUPERVISOR_ENCODED_PASS

OracleDI supervisor user password. The password must be encoded with the "encode.[sh|bat] <password>" command.

ODI_SUPERVISOR_ENCODED_PASS=hpfatLEoMR6zAK3T1PoP5LXDS

Run the following script to add this agent to the OPMN configuration.

For UNIX operating systems:

ODI_HOME/oracledi/agent/bin/odi_opmn_addagent.sh

For Windows operating systems:

ODI_HOME/oracledi/agent/bin/odi_opmn_addagent.bat

H.2 Stopping the Agent

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

H.3 Starting the Agent and Agent Components

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

H.4 Determining the Status of Oracle HTTP Server

You can determine the status of Oracle HTTP Server using opmnctl:

opmnctl status

H.5 Deleting the Agent

Run the following script to delete this agent from the OPMN configuration.

For UNIX operating systems:

ODI_HOME/oracledi/agent/bin/odi_opmn_deleteagent.sh

For Windows operating systems:

ODI_HOME/oracledi/agent/bin/odi_opmn_deleteagent.bat