The following figure shows the overall procedure, from developing Automated Operation Processes through to operating them.
Design
Register the user or group, or connection information for connection to the Managed Server, in order to execute automated operations in Systemwalker Runbook Automation. Additionally, collect the configuration information if necessary.
This task is performed by the system operation manager.
Analyze the operation task procedure, and decide which operations to automate using Systemwalker Runbook Automation.
Additionally, search for Automated Operation Processes registered in the Management Server that can be applied to operations that are to be automated, and decide how much to customize them to suit the operations. If there are no Automated Operation Process templates that can be applied, create a new Automated Operation Process.
This task is performed by the developer.
Development
Create the Automated Operation Process definition on the development computer using Systemwalker Runbook Automation Studio.
This task is performed by the developer.
Download any Automated Operation Processes or operation components registered in the Management Server that can be reused. The downloaded Automated Operation Processes or operation components can be used as the basis for development.
This task is performed by the developer.
The operation components can be developed on the development computer or on another computer if necessary.
Operation components can be developed using either a text editor or a third-party Ruby or Perl development environment.
This task is performed by the developer.
Registration
The Automated Operation Process/operation component that has been developed must be registered on the Management Server before it can be used.
This task is performed by the Operation Administrator or developer.
Testing
To confirm that the Automated Operation Process that was created is the intended Automated Operation Process, its behavior must be checked by running a test operation.
Note that, in the Automated Operation Process test, the operation will actually be executed for the Managed Server. A separate testing environment must be prepared if there is any chance that the test could affect the system during operation.
This task is performed by the developer.
After confirming that there are no problems in the test operation, publish the Automated Operation Process so that the user can use it.
This task is performed by the Operation Administrator.
Schedules
To execute the Schedule Definition, the Schedule Definition settings can be configured easily registering and using the following two definition types:
Holiday calendar
Holidays can be set. Using a holiday calendar, if the Automated Operation Process startup day is a holiday, it is possible to defer the Automated Operation Process startup and start the Automated Operation Process on the previous or following day instead.
The holiday calendar is registered for the system, and can be used commonly for all Schedule Definitions.
The holiday calendar is registered by the Operation Administrator.
Schedule Pattern
The date and time on which the Automated Operation Process will be started can be registered as a pattern.
When executing the Schedule Definition, the Automated Operation Process startup day can be set by selecting a Schedule Pattern that has already been registered.
The Schedule Pattern is registered for a system or an Automated Operation Process Group.
The Schedule Pattern is registered by the Operation Administrator.
For an already published Automated Operation Process, set the Schedule Definition, such as startup day or start time, by specifying a Schedule Pattern or by specifying the item directly.
This task is performed by the Operation Administrator or operator.
Operations
Using the Automated Operation Process definition registered/published in the Management Server, execute the system operation task processing.
Additionally, check the status of the executed Automated Operation Process, then check the task results and status.
The Automated Operation Process execution/status confirmation can be performed in the Web console that is provided in the Management Server.
This task is performed by the operator.
Additionally, management and investigation of problems that cannot be resolved by the operator are performed by the Help Desk.