Command Line Administration in OAS 10.1.3.x is very powerful

Today a customer asked me how they could stop an application on a remote OAS server which was part of cluster, but only using opmnctl command. I know it can be done wit admin_client.jar but they insisted they only wanted to use opmnctl. I wasn't sure if it was possible but found it was in the end.

Setup:

2 OAS 10.1.3.x installs, but only had access to one of them from the command line

eg:

Processes in Instance: 10132linux_pink.papicell-au2.au.oracle.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ASG                              | ASG                |     N/A | Down
OC4JGroup:pas_group              | OC4J:pas_oc4j      |   28416 | Alive
OC4JGroup:default_group          | OC4J:OC4J_WebCent~ |     N/A | Down
OC4JGroup:default_group          | OC4J:home          |   16758 | Alive
HTTP_Server                      | HTTP_Server        |   19568 | Alive

Processes in Instance: 10132linux_green.papicell-au2.au.oracle.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ASG                              | ASG                |     N/A | Down
OC4JGroup:default_group          | OC4J:OC4J_WebCent~ |     N/A | Down
OC4JGroup:default_group          | OC4J:home          |   30049 | Alive

In this case we only have access to the oracle_home "10132linux_green". The requirement was to shutdown ascontrol remotely on the instance "10132linux_pink". With opmnctl this is easily done as long as the instances are clustered together it's a command as simple as this, where we specify exactly which instance to execute the command on.

- opmnctl @instance:10132linux_pink.papicell-au2.au.oracle.com stopproc process-type=home application=ascontrol

To then restart it when it needs to be running again remotely we use a command as follows

- opmnctl @instance:10132linux_pink.papicell-au2.au.oracle.com startproc process-type=home application=ascontrol

The process-type switch ensures we only stop/start the application on a specific OC4J instance which for ascontrol is vital as we only need it running on one node within the cluster.