The following figure shows the overall procedure, from designing Automated Operation Processes through to operating them.
Designing
Design tasks involve system administrators making environment settings for automated operations and Automated Operation Processes.
The developer analyzes the current operation procedure, decides which operations to automate using Systemwalker Runbook Automation, and designs Automated Operation Processes.
Development
The developer uses Systemwalker Runbook Automation Studio on a Development Computer to create definitions for Automated Operation Processes. Automated Operation Processes can also be created by reusing existing Automated Operation Processes or by using the templates that come with the product.
If necessary, develop operation components by using a text editor or an external Perl or Ruby development environment.
These tasks are performed by developers.
Registration
Registration tasks involve either an administrator or a developer registering the Automated Operation Processes or operation components that have been developed on the Management Server.
Testing
Testing tasks involve performing test operations for the Automated Operation Processes that have been created, and checking their behavior.
These tasks are performed by developers.
Once it has been confirmed that there are no problems with the test operations, the administrator publishes the Automated Operation Process so that it can be used by system users.
Scheduling
To start an Automated Operation Process on a pre-determined date or at a pre-determined time, set the Schedule Definition for the Automated Operation Process.
The Operation Administrator or operator configures the Schedule Definition settings.
Note that, to execute the Schedule Definition, the Schedule Definition settings can be configured easily using the following two definition types:
Holiday Calendar
Holidays can be set. The holiday calendar is registered for the system, and can be used commonly from 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. The Schedule Pattern is registered for a system or an Automated Operation Process Group.
The Schedule Pattern is registered by the Operation Administrator.
Operation
Operation tasks involve operators executing Automated Operation Processes.
The Web Console provided by the Management Server can be used to check the status of the Automated Operation Processes that have been executed, and to check task results.
