Use the following procedure to distribute and apply Systemwalker Operation Manager policy information to cluster system:
Distribute a policy to the active nodes.
Distribute a policy to the active nodes by specifying the host name for the active node in the Specify Distribution Subsystem window. Select Apply at the next service startup in the Apply Policy dialog box.
Stop the daemons on the active nodes.
Stop all the Systemwalker Operation Manager daemons running on the active nodes. Refer to "3.2 Starting and Stopping Daemons in Cluster Systems" for details on how to stop daemons.
Start the daemons on the active nodes.
Start all the Systemwalker Operation Manager daemons for the active nodes. Refer to "3.2 Starting and Stopping Daemons in Cluster Systems" for details on how to start daemons.
The distributed policy information will be applied when the daemons start up.
Reflect security information on the shared disk.
Reflect security information for the active nodes on the shared disk by executing the following command. Before executing this command, mount the shared disk for each active node.
[1:1 active/standby, N:1 active/standby, and cascading configuration]
mpcssave
[Dual node mutual standby configuration]
mpcssave -s subsystem number for the active node
Copy information to the standby node.
Copy the following information from an active node to the standby node. Refer to "2.9.3 Standardizing Systemwalker Operation Manager environment definitions" for details on when and how to copy this information.
Monitoring host definition information
Password management list information/host information definitions
Job folder information
Web Console definition information
Note
If cluster operation is being used, select Apply at the next service startup. Do not select Apply at once (Restart the service).
Accordingly, to distribute the policy changed on the active node immediately, restart the daemons. Refer to "3.2 Starting and Stopping Daemons in Cluster Systems" for details on how to restart daemons.
The policy distributed to the standby node will be applied on the next failover.
Note
If Systemwalker Operation Manager is operating as a cluster system, do not distribute Shared Parameter policy.
Note
Policy information does not include the following cluster operation information for calendar information, so this information must be set on each node.
Information registered with the calsetcluster command
Information in the calendar reflection host definition file
Note
Distribute the information set in Job control in the Registration Information window as a policy to the active node. Do not distribute it to the standby node. Since this information is managed by the shared disk, the same information is retained even in the event of failover.
Note
Refer to the Logging tab in the Define Operating Information window and check the saved location of the job execution history information and the operation record information of the extraction source server. Check if this saved location is a server where the system performs cluster operations. If it is not, create a directory in a system that performs cluster operations so that the saved location of the directory is the same as the extraction source server. Perform this step before distributing the operation information.
