Normally, when performing the release of an application to the business system, there are multiple processes, such as drafting and testing release plans. These can be seen as a single process that continues until the release is completed, or can be seen as a collection of processes divided among each phase.
With Systemwalker Runbook Automation, this kind of task, where people have to intervene, can be created as an Automated Operation Process. It is also possible to invoke from this Automated Operation Process further Automated Operation Processes where each of the phases is automated.
Figure 7.13 Automating the release process
Also, by using the operation components provided with Systemwalker Runbook Automation, it is possible to set the schedule for each of the Automated Operation Processes.
Operation component names | Purpose |
|---|---|
Register Schedule Definition | Registers the schedule in accordance with the specified conditions. |
Delete Schedule Definition | Deletes specified schedules. |
The subsequent chapter explains how to customize the release automation template including the operation components mentioned above.
By using the "Register Schedule Definition" component with the Automated Operation Process that brings together each process of the release, it is possible to schedule execution of the release tasks in accordance with the release plan.
The "Register Schedule Definition " component registers Schedule Definitions in accordance with specified conditions. It is possible to operate the registered Schedule Definitions from the Schedule Definitions list window.
As a result, it is also possible to check the execution schedule and progress status of the release task processes in the process status window. In this way, it is possible for the release tasks to manage performance in combination with other administrative tasks.
Figure 7.14 Scheduled release task
Also, by deploying the "Delete Schedule Definition" component in the same process definition, it is possible to cancel an already registered schedule.
Retrieve the release package from the SCM server where the release package is archived. Use the "Execute arbitrary command" operation component to retrieve the release package. In this way, it is possible to automate the handover of the release package from developer to operation administrator as an Automated Operation Process.
Operation component name | Parameter name | Input value |
|---|---|---|
Execute arbitrary command | commandline | Set the command for retrieving the release package provided by the SCM server. |
By customizing the release automation template it is possible to release the release package to multiple release targeted server.
Add as many "Transfer files", "Collect fingerprint", and "Delete files" operation components as the number of release targeted server to release the release packages to multiple release targeted server.
Figure 7.15 Releasing to multiple release targeted server
