This section describes how to start and stop Systemwalker Operation Manager in the Oracle Solaris Cluster system.
Starting daemons
This section describes the procedure for starting the Systemwalker Operation Manager daemons.
On all servers on both the active and standby nodes, execute the soperationmgr command to start any Systemwalker Operation Manager daemons that are not registered with Oracle Solaris Cluster.
# /opt/systemwalker/bin/soperationmgr
Start the Systemwalker Operation Manager daemons that are registered with the cluster system by varying online the Systemwalker Operation Manager resource groups registered with the cluster system.
# /usr/cluster/bin/scswitch -Z -g resource group name[Example]
# /usr/cluster/bin/scswitch -Z -g OMGR_rg
Stopping daemons
This section describes the procedure for stopping the Systemwalker Operation Manager daemons.
Stop the Systemwalker Operation Manager daemons that are registered with the cluster system by varying offline the Systemwalker Operation Manager resource groups registered with the cluster system.
# /usr/cluster/bin/scswitch -F -g resource group name[Example]
# /usr/cluster/bin/scswitch -F -g OMGR_rg
On all servers on both the active and standby nodes, execute the poperationmgr command to stop any Systemwalker Operation Manager daemons that are not registered with Oracle Solaris Cluster.
# /opt/systemwalker/bin/poperationmgr
Note
Do not move the current directory to the shared disk when executing the soperationmgr command or the poperationmgr command. Otherwise, a failover may not be performed correctly.
Do not start or stop any services using the Service control section in the Systemwalker Operation Manager Environment Setup window.
Any resource groups where the Systemwalker Operation Manager data service resource has been registered must be stopped before Systemwalker Operation Manager is stopped (if Systemwalker Operation Manager has been registered with a cluster system).
As a result, the shared disk and logical IP address registered with any such resource group will also stop, along with the Operation Manager data service and any applications (such as Oracle or Interstage) registered with it. Any data service resources for fault monitor created and registered with the resource group will also stop.
In order for the Jobscheduler daemon to operate, the calendar daemon must be activated before the Jobscheduler daemon.