Install Systemwalker Operation Manager on the active and standby nodes.
Refer to the Systemwalker Operation Manager Installation Guide for details on how to install Systemwalker Operation Manager on each type of node.
Note
Do not install Systemwalker Operation Manager on the shared disk.
If the Systemwalker Operation Manager users are controlled by selecting the Restrict so that only users included in the swadmin group can start demand jobs, start jobnet Job execution control attributes or use the Jobscheduler command functions. option in the Define Operation Manager Shared Parameter window, define user restrictions on the active and standby nodes after installing Systemwalker Operation Manager.
Note that the users are restricted (the user restriction definition option is enabled) by default for new installation in V17.0.0 or later.
Refer to the Systemwalker Operation Manager Installation Guide for details.
Note
The user restriction definitions cannot be changed after registering Systemwalker Operation Manager with a cluster system.
Be sure to set the definition before registering Systemwalker Operation Manager with the cluster system.
Information
It is easy to register Systemwalker Operation Manager with a cluster system if state transition procedures for registering Systemwalker Operation Manager with a cluster system are created in advance by using an installation sample.
For details, refer to the article of "Creating state transition procedures" that is cluster-system specific procedure.
The terminology of "state transition procedure" varies from cluster system to cluster system. So, it should be interpreted as explained below:
PRIMECLUSTER: state transition procedure
Oracle Solaris Cluster
MC/ServiceGuard: script
HACMP: application
Create subsystem environments
A prerequisite for 1:1 active/standby configurations (with subsystems), 1:1 active/standby configurations (with subsystems and partial cluster operation), and dual node mutual standby configurations is that the subsystem environment must be created in advance so that multiple subsystems can run on the cluster system. Additionally, create the same subsystem environment on both the active node and the standby node for the 1:1 active/standby configuration (with subsystems), or the N:1 active/standby configuration.
Create the subsystem environment
Execute the createsubsystem.sh command on both the active node and the standby node. Refer to "Creating Subsystem Environments" in the Systemwalker Operation Manager Installation Guide for details.
Set port numbers for subsystems
Set port numbers for the subsystems used by the Jobscheduler on both the active node and the standby node. Refer to "Assigning Subsystem Port Numbers" in the Systemwalker Operation Manager Installation Guide for details.
Set port numbers for network jobs
These settings are required only if the execution server for network jobs uses a multiple subsystem configuration and the own server (schedule server) uses a multiple subsystem configuration where a job that spans multiple subsystems is submitted.
Set port numbers for network jobs on all the nodes on the cluster system and also on the execution server for network jobs. Refer to "Assigning Subsystem Port Numbers" in the Systemwalker Operation Manager Installation Guide for details.
Restart Systemwalker Operation Manager
