A OPMN Commands

Oracle Process Manager and Notification Server (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 started.

The following attributes and values can be used with 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, the command is applied to all OPMN-managed processes.
mode: The value can be either sync or async. The default value is sync. The sync value 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 restartproc or stopproc command request until the operation is finished.

The async value 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. To obtain this value, enter the following command and look for the unique ID for the component in the uid column of the generated output:
```
opmnctl status -l
```

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

When you use the opmnctl startproc command with a specified scope and attributes, you can control specific processes in your enterprise. You can execute the opmnctl startproc command at the ias-component, process-type, and process-set level.

For example, the following command starts OracleAS Wireless at the process-set level:

opmnctl startproc ias-component=wireless process-type=alert_server process-set=alert_instance_1

stopproc

Syntax: opmnctl [scope] stopproc [attr=value]...

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

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:

opmnctl stopproc ias-component=HTTP_Server

status

Syntax: opmnctl [scope] status [options]...

Provides 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 Oracle Application Server instance in an entire farm:

opmnctl @farm status