The following diagram shows the flow of registering an Automated Operation Process and operation components.
An outline of the tasks shown in this diagram is given below.
Registering an Automated Operation Process
The Automated Operation Process is registered using one of the methods shown below:
Using Studio
Systemwalker Runbook Automation Studio is operated as follows:
Upload the application project.
The development computer process definition will be uploaded to the Management Server.
Using the Web console
Systemwalker Runbook Automation Studio is operated as follows:
Export the workflow application project.
The files for the registration of the process definition in the Management Server are created in the development computer.
The Web console is operated as follows:
Create the Automated Operation Process group space.
Update the Automated Operation Process group.
The process definition will be registered in the Management Server.
Registering operation components
If new operation components have been developed, register the operation components in the Management Server using either of the following methods:
Registering from Systemwalker Runbook Automation Studio:
Upload the operation components.
The operation components of the Development Computer will be uploaded to the Management Server.
Registering from a Web console
In Systemwalker Runbook Automation Studio, export the operation components.
A file for registering the developed operation components in the Management Server will be created in the Development Computer.
In the Web console, import the operation components.
The operation components of the Development Computer will be uploaded to the Management Server.
Giving an Automated Operation Process Group online status
An online state will be necessary in order to use the Automated Operation Process that was registered.
