This section describes how to start and stop Systemwalker Operation Manager daemons in the PRIMECLUSTER 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 not registered with PRIMECLUSTER. In the case of a 1:1 active/standby configuration (with subsystems and partial cluster operation), the Jobscheduler and Job Execution Control daemons of subsystems not registered with a cluster system will also start.
# /opt/systemwalker/bin/soperationmgr
Start the Systemwalker Operation Manager daemons registered with the cluster system by varying the application registered with the cluster system online.
Select Global Cluster Services from the top menu of the PRIMECLUSTER's Web-Based Admin View, and then select Cluster Admin from the window that is displayed.
A pop-up menu will be displayed for selecting the node to connect to.
Select the node from the pop-up menu.
The RMS main window will be displayed.
Right-click on the Systemwalker Operation Manager cluster application to be started from the RMS tree in the RMS main window, and then select [Online] from the pop-up menu.
The Systemwalker Operation Manager cluster application (i.e., the Systemwalker Operation Manager daemon managed by the cluster system) will start.
Stopping daemons
This section describes the procedure for stopping the Systemwalker Operation Manager daemons.
Stop Systemwalker Operation Manager daemons registered with the cluster system by varying the application registered with the cluster system offline.
Select Global Cluster Services from the top menu of the PRIMECLUSTER's Web-Based Admin View, and then select Cluster Admin from the window that is displayed.
A pop-up menu will be displayed for selecting the node to connect to.
Select the node from the pop-up menu.
The RMS main window will be displayed.
Right-click on the Systemwalker Operation Manager cluster application to be stopped from the RMS tree in the RMS main window, and then select Offline from the pop-up menu.
The Systemwalker Operation Manager cluster application (i.e., the Systemwalker Operation Manager daemon managed by the cluster system) will stop.
On all servers on both the active and standby nodes, execute the poperationmgr command to stop any Systemwalker Operation Manager daemons not registered with PRIMECLUSTER. In the case of a 1:1 active/standby configuration (with subsystems and partial cluster operation), the Jobscheduler and Job Execution Control daemons of subsystems not registered with a cluster system will also stop.
# /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, failover may not be performed normally.
Do not start or stop any services with the Service control section of the Systemwalker Operation Manager Environment Setup window.
Any cluster application where the Systemwalker Operation Manager resources have 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 cluster application will also stop, along with the Operation Manager resources and any applications (such as Oracle or Interstage) registered with it. Resources created for state transition procedures that monitor daemons and registered with the cluster application will also stop.
In order for the Jobscheduler daemon to operate, the calendar daemon must be activated before the Jobscheduler daemon.
