Set up the Master Schedule Management function if it is to be used. The Master Schedule Management function does not need to be set up if it is not to be used or if a 1:1 active/standby configuration (with subsystems and partial cluster operation) is to be used and subsystems are not to be registered with a cluster system.
If the Master Schedule Management function is to be used, refer to the Systemwalker Operation Manager User's Guide - Master Schedule Management, and determine in advance which server to use as the management server and which server to use as the schedule server, including issues such as which servers will be used with a cluster configuration.
Create an environment for the Master Schedule Management function.
Create an environment for the Master Schedule Management function by executing the stemenvset environment setup command on all management servers and schedule servers that will use the Master Schedule Management function. If the management server or the schedule server is using a cluster configuration, create environments for the Master Schedule Management function on all the nodes (active and standby) on the cluster system by executing the stemenvset environment setup command for Master Schedule Management on each node.
# /opt/FJSVstem/bin/stemenvset.sh -set |
For details on the stemenvset environment setup command, refer to the Systemwalker Operation Manager Reference Guide.
Set up Schedule by dates mode.
Execute the soperationmgr command to start the Systemwalker Operation Manager infrastructure daemon in advance.
[If the management server is in a cluster system configuration]
Connect to the active node, then specify either Daily schedule management or Daily schedule management (Test mode) as the mode in the Master Schedule Management Environment Setup dialog box.
[If the schedule server is in a cluster system configuration]
In the Add Schedule Server dialog box of the Master Schedule Management Environment Setup dialog box for the management server connected, specify the physical IP address of the active node in the IP address field in order to register the active node as a schedule server.
Note
A message will appear asking whether to restart the Jobscheduler daemon. Select No not to restart the Jobscheduler daemon.
Refer to the Systemwalker Operation Manager User's Guide - Master Schedule Management for details on the Master Schedule Management environment settings.
Set up a logical IP address.
Use the following procedure to set logical IP address for the subsystems for which the Schedules by dates mode has been set up:
[If the management server is in a cluster system configuration]
Set a logical IP address for the management server by executing the stemConfig Master Schedule Management environment setup command [UNIX] on the active node management server and schedule servers.
Settings for 1:1 active/standby (without subsystems), N:1 active/standby and cascading configuration
In the following example, the logical IP address for the management server is xxx.xxx.xxx.1.
# /opt/FJSVstem/bin/stemConfig set -m -ip xxx.xxx.xxx.1
Settings for 1:1 active/standby (with subsystems)
In the following example, the logical IP address for the management server is xxx.xxx.xxx.1 and Subsystem 0 and Subsystem 1 with the Schedule by dates mode specified.
# /opt/FJSVstem/bin/stemConfig set -m -ip xxx.xxx.xxx.1 -sys 0 # /opt/FJSVstem/bin/stemConfig set -m -ip xxx.xxx.xxx.1 -sys 1
Settings for 1:1 active/standby configuration (with subsystems and partial cluster operation)
In the following example, the logical IP address for the management server is xxx.xxx.xxx.1, only Subsystem 1 is used in cluster operation, and Subsystem 1 is configured for Schedule by Dates mode:
# /opt/FJSVstem/bin/stemConfig set -m -ip xxx.xxx.xxx.1 -sys 1
Settings for dual node mutual standby configuration
In the following example, the logical IP address for Subsystem 1 on the management server is xxx.xxx.xxx.1.
# /opt/FJSVstem/bin/stemConfig set -m -ip xxx.xxx.xxx.1 -sys 1
In the following example, the logical IP address for Subsystem 2 on the management server is xxx.xxx.xxx.2.
# /opt/FJSVstem/bin/stemConfig set -m -ip xxx.xxx.xxx.2 -sys 2
[If the schedule server is in a cluster system configuration]
Set the logical IP address for the schedule server that will run as a cluster system by executing the stemConfig Master Schedule Management environment setup command [UNIX] on the management server.
Settings for 1:1 active/standby (without subsystems), N:1 active/standby and cascading configuration
In the following example, the logical IP address for the schedule server (server1) is xxx.xxx.xxx.3.
# /opt/FJSVstem/bin/stemConfig set -h server1 -ip xxx.xxx.xxx.3
Settings for 1:1 active/standby (with subsystems)
In the following example, the logical IP address for the schedule server (server 1) is xxx.xxx.xxx.3 and Subsystem 0 and Subsystem 1 with the Schedule by dates mode specified.
# /opt/FJSVstem/bin/stemConfig set -h server1 -ip xxx.xxx.xxx.3 -sys 0 # /opt/FJSVstem/bin/stemConfig set -h server1 -ip xxx.xxx.xxx.3 -sys 1
Settings for 1:1 active/standby configuration (with subsystems and partial cluster operation)
In the following example, the logical IP address for the schedule server (server1) is xxx.xxx.xxx.3, only Subsystem 1 is used in cluster operation, and Subsystem 1 is configured for Schedule by Dates mode:
# /opt/FJSVstem/bin/stemConfig set -h server1 -ip xxx.xxx.xxx.3 -sys 1
Settings for dual node mutual standby configuration
In the following example, the logical IP address for Subsystem 1 on the schedule server (server1) is xxx.xxx.xxx.3.
# /opt/FJSVstem/bin/stemConfig set -h server1 -ip xxx.xxx.xxx.3 -sys 1
In the following example, the logical IP address for Subsystem 2 on the schedule server (server1) is xxx.xxx.xxx.4.
# /opt/FJSVstem/bin/stemConfig set -h server1 -ip xxx.xxx.xxx.4 -sys 2
Refer to the Systemwalker Operation Manager Reference Guide for details on the stemenvset environment setup command and the stemConfig Master Schedule Management environment setup command [UNIX].
