A Listing of OPMN Commands

OPMN is installed and configured with every Oracle Application Server installation type and is essential for running Oracle Application Server. This appendix lists the key OPMN commands and illustrates their usage.

Start

Syntax: opmnctl start

Starts the OPMN server for a local Oracle Application Server instance without starting OPMN-managed processes.

Startall

Syntax: opmnctl startall [timeout=<seconds>]

Starts OPMN and OPMN-managed processes for a local instance. This is equivalent to the start command and the startproc command without arguments. Oracle recommends using the start or startproc command.

This command operates synchronously and waits for the operation to complete before returning. To set a timeout for the request, specify the timeout value in seconds.

Stopall

Syntax: opmnctl stopall

Shuts down the OPMN server and OPMN-managed processes for the local instance. This request operates synchronously and waits for the operation to complete before returning.

Startproc

Syntax: opmnctl [<scope>] startproc [<attr>=<value>...]

Starts OPMN-managed processes in the requested scope. The OPMN server for the instance must be up and running.

The following attributes and values can be used with the startproc:

ias-component, process-type, and process-set: The values for these attributes should be the same as the id value specified in the opmn.xml file. If no attribute is supplied, then the command is applied to all OPMN-managed processes.
mode: The mode attribute value can be either sync or async. The default value is sync. The sync value for mode causes the opmnctl command to operate synchronously and wait for the command to be executed completely before a return prompt is displayed. The timeout element can only be specified when the value of mode is sync. The value is specified in number of seconds. After the specified timeout expires, the operation is aborted for startproc but not for restartproc or stopproc. The opmnctl command prompt returns, the OPMN server continues to perform the opmnctl restartproc or stopproc command request until the operation is finished.

The async value for mode causes the return prompt to be displayed immediately, while the OPMN server continues to perform the opmnctl command request until the operation is finished.
uniqueid: This value is assigned by OPMN after starting up. You can use this value when you execute the restartproc and stopproc commands. You can obtain this value by entering the following command and obtaining the unique number for the component in the uid column of the generated output.

prompt > opmnctl status -l

Attribute names other than the those listed may be specified for some types of processes managed by OPMN. Unique attribute name should be specific to each type of process.

Using the opmnctl startproc command with a specified scope and attributes enables control of specific processes in your enterprise. You can execute the opmnctl startproc command at the <ias-component>, <process-type> and the <process-set> level.

For example, the following command starts OracleAS Wireless at the <process-set> level:prompt > opmnctl startproc ias-component=wireless process-type=alert_server process-set=alert_instance_1

Stopproc

Syntax: opmnctl [<scope>] restartproc [<attr>=<value>...]

Use this command to start OPMN-managed processes in the requested scope. The OPMN server for the instance must be up and running.

The attributes and values of the stopproc command are identical to those of the startproc command.

For example, the following command stops Oracle HTTP Server at the <ias-component> level:

prompt > opmnctl stopproc ias-component=HTTP_Server

Status

Syntax: opmnctl [<scope>] status [<options>]

The status command enables you to obtain information about the processes managed by OPMN.

You can use the opmnctl status command with <scope> to obtain additional detailed information. For example, the following command gives you the status of every process of every component of every OracleAS Instance in an entire farm:

prompt > opmnctl @farm status