Operation components are the Ruby or Perl is script that are called from operation activities in Automated Operation Processes, in order to automate operations on ICT systems. Operation components issue instructions to servers and linked products, automating tasks that were previously performed manually, such as checking whether a service has started, or monitoring a process.
Operation components absorb differences between systems (such as platform differences) by obtaining configuration information from the CMDB. This means that operation components can be used without having to be aware of system differences, making them easy to use even without detailed knowledge about system management tools and operating system commands. Operation components can be used repeatedly from the same Automated Operation Process, or shared between different Automated Operation Processes.
If the standard operation components provided by Systemwalker Runbook Automation do not meet the requirements, Systemwalker Runbook Automation can be used to create the required operation components.
You can call the Ruby library that is provided as standard in Systemwalker Runbook Automation, and you can also reuse the library to create the operation component.
Refer to the Systemwalker Runbook Automation Reference Guide for information on the Ruby library.
Custom operation components that have been developed can be used in the same way as the standard operation components provided by Systemwalker Runbook Automation.
Note that further steps are required to actually use the operation component once it has been created. After it has been created, the operation component must be exported from the Development Computer and then registered on the Management Server using the Web console. The registration task is performed by either an administrator or a developer.
