Systemwalker Operation Manager is a client-server type system. Before using the Systemwalker Operation Manager functions, turn on the power to the Systemwalker Operation Manager server. When the power is turned on, the daemons for each of the Systemwalker Operation Manager functions will start up automatically.
If multiple subsystems are operated, all the subsystems are started up automatically.
After startup is complete, you can use any of these functions from any Systemwalker Operation Manager client.
Information
After startup of Systemwalker Operation Manager, you can confirm whether the daemon of each function is properly operating by checking whether the process names shown below exist.
Process name | Function corresponding to each process |
|---|---|
MpFwsec | ACL Manager |
f3crhcs2 | Calendar/Power Control |
mpjmsrv | Systemwalker Operation Manager Base |
mjsdaemon | Job Execution Control |
tskmnsrv | Jobscheduler |
mppmon | Process Monitoring |
Note
Operation startup modes for the Job Execution Control
The Job Execution Control starts its operation when the following two processes are completed in sequence.
Activating the Job Execution Control daemon
Starting Job Execution Control operations
Process (a) is automatically activated when the Systemwalker Operation Manager server starts, followed by automatic activation of process (b). While the following startup modes are available for the Job Execution Control operations, the continuation mode is usually used.
In this mode, the definitions (i.e., initialization file details) from the Operating control sheet/Logging sheet/Options sheet/Backward compatibility sheet/Cluster settings sheet/Network sheet of the Define Operation Data window cannot be read. Consequently, operation is started using the previous operation environments.
In this mode, the definitions (i.e., initialization file details) from the Operating control sheet/Logging sheet/Options sheet/Backward compatibility sheet/Cluster settings sheet/Network sheet of the Define Operation Data window can be read, and restructure a queue configuration and so on. Consequently, all jobs remaining from the previous operations are deleted.
This mode is automatically adopted in situations where the system has become inoperable due to system downtime or interruption of the power supply. It is not possible for operators to specify the implementation of this mode.
If the Define Operating Information has been changed, the next Job Execution Control operation is activated with the initialization mode.
Note
Stopping the daemons when restarting in Red Hat Enterprise Linux 7
In Red Hat Enterprise Linux 7, the operating system may need to be stopped or restarted in the cases below even if the daemons are configured to stop automatically when the operating system is stopped. In these cases, manually execute the poperationmgr service/daemon termination in advance to stop the Systemwalker Operation Manager daemons.
The daemons were manually restarted (using the poperationmgr/soperationmgr command, for example).
The daemons were restarted using daemon control in the environment setup window.
The backup command was executed.
A policy was distributed with "Apply once" specified.
How to start up manually
The daemons of Systemwalker Operation Manager can be activated manually with the soperationmgr (daemon activation) command. To activate the Systemwalker Operation Manager daemon manually for some reasons such as maintenance work, execute the "soperationmgr" command. For details on the "soperationmgr" command, see the "Shared Commands" section of the Systemwalker Operation Manager Reference Guide.
How to start up multiple subsystems manually
With Systemwalker Operation Manager Enterprise Edition version, multiple subsystems can be started up. To start up subsystems with corresponding subsystem numbers manually, follow the example below.
Example 1: To start up subsystem 1
/bin/sh /etc/opt/FJSVMJS/etc/rc3.d/S99MJS -sys 1 |
Note)
Make sure S99JOBSCH is executed immediately after S99MJS is executed.
For the -sys option of S99MJS and S99JOBSCH, specify the same subsystem number.
Example 2: To start up all the subsystems
/bin/sh /etc/opt/FJSVMJS/etc/rc3.d/S99MJS -sys all |
Information
S99MJS and S99JOBSCH storage paths
The path to the S99MJS and S99JOBSCH storage varies depending on the OS used as follows. Change those paths according to the OS you are using.
[S99MJS]
Solaris | /etc/opt/FJSVMJS/etc/rc3.d |
HP-UX system: | /opt/FHPMJS/usr/lib/mjes |
AIX | /opt/FAIXMJS/usr/lib/mjes |
Linux | /etc/opt/FJSVMJS/etc/rc3.d |
[S99JOBSCH]
Solaris | /opt/FJSVJOBSC/etc/rc3.d |
HP-UX system: | /opt/FHPJOBSCH/bin |
AIX | /usr/FAIXJOBSC/bin |
Linux | /opt/FJSVJOBSC/etc/rc3.d |
Setting/canceling daemon execution suppression
To prevent the Systemwalker daemons from being started up automatically with the OS startup, use the service execution suppression command to suppress daemon execution. Use the daemon execution suppression canceling command to cancel it.
To suppress daemon execution, execute the following command on the server on which you want to suppress daemon execution.
/opt/FJSVftlo/bin/swstop |
To cancel suppression of daemon execution, execute the following command on the server on which you want to cancel suppression of daemon execution.
/opt/FJSVftlo/bin/swstart |
For the command details, see the Systemwalker Operation Manager Reference Guide.
Point
Linking with SystemcastWizard
Using SystemcastWizard Professional, it is possible to back up the master computer disk contents and distribute them to multiple target computers in a batch. This enables identical OS/Systemwalker Operation Manager environments to be constructed in a short time. Also, IP address and computer name are automatically changed.
How to link with SystemcastWizard is shown below.
On the master computer, install Systemwalker.
On the master computer, set up each function.
On the master computer, execute the daemon execution suppression command.
On the master computer, run the advance setup program for the SystemcastWizard, and then specify the daemon execution suppression canceling command for the module to be executed after login.
Perform restoration to the target computer.
See the SystemcastWizard Professional User's Guide for more information.
