Systemwalker Operation Manager is a client-server type system. Before using Systemwalker Operation Manager functions, first turn on the power of the server where Systemwalker Operation Manager has been installed. When the power is turned on, the services for each of the Systemwalker Operation Manager functions will start up automatically.
After startup is complete, you can use any of these functions from Systemwalker Operation Manager client.
To manually start up a Systemwalker Operation Manager server after shutting down a Systemwalker Operation Manager server with the "poperationmgr" (service shutdown) command or stopping the Systemwalker Operation Manager services for some reasons such as maintenance, start up with the "soperationmgr" (service startup) command.
Service designated as "automatic" in the Services dialog box on the Control Panel can be started up with the soperationmgr command. If you need to individually start up a Systemwalker Operation Manager server for some reasons such as maintenance, start up the services using the Services dialog box of the Control Panel in the following order.
Display name of service | Function corresponding to each service |
|---|---|
Systemwalker ACL Manager | ACL Manager |
Systemwalker MpAosfP | Power Control (Power Control, Service/Application Startup) |
Systemwalker MpAosfX | Auto-Operation Support (Action Execution) |
Systemwalker MpAosfB | Auto-Operation Support (Event Monitoring, Action Management) |
Systemwalker MpJmSrv | Systemwalker Operation Manager Base |
Systemwalker MpNjsosv | Task Link |
Systemwalker MpMjes | Job Execution Control |
Systemwalker MpJmCal | Calendar |
Systemwalker MpJobsch | Jobscheduler |
Systemwalker MpPmonO | Process Monitoring |
These services can be started up in a batch with the soperationmgr command. For details on the "soperationmgr" command, see the "Shared Commands" section of the Systemwalker Operation Manager Reference Guide.
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 service
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/Print format 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/Print format 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. When the stop operation of the Job Execution Control services/daemons is not executed properly for some reason such as system downtime or power interruption, the Job Execution Control function is activated with the recovery mode. When activated with the recovery mode, the demand job, which was in execution and with no -nr option specified at the time the service/daemon was stopped, is automatically started up when the Job Execution Control service/daemon is restarted. 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.
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.
Start up the following Systemwalker Operation Manager services from the Services dialog box of the Control Panel.
Systemwalker MpMjes1
Systemwalker MpJobsch1
Note)
Make sure the Systemwalker MpJobsch1 is started up immediately after the Systemwalker MpMjes1 is started up.
For MpMjes and MpJobsch, start up the service with the same subsystem number.
Setting/canceling service execution suppression
To prevent the Systemwalker services from being started up automatically with the power on, use the service execution suppression command to suppress service execution. Use the service execution suppression canceling command to cancel it.
To suppress service execution, execute the following command on the server on which you want to suppress service execution.
Systemwalker installation directory: |
To cancel suppression of service execution, execute the following command on the server on which you want to cancel suppression of service execution.
Systemwalker installation directory: |
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 service execution suppression command.
On the master computer, run the advance setup program for the SystemcastWizard, and then specify the service 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.
