Requirements and Technology – Automation
The dashboard of your monitoring system repeatedly displays errors and warnings for which you already know what to do next. However, you can automate this in such a way that you only have to worry about the exceptions.
Define the sensors and errors, which ScriptRunner should process for you, partially or fully automated, as you want it.
You already use ITSM in your company, but too much still runs manually. You can significantly enhance ITSM by linking it to ScriptRunner. Users can start predefined PowerShell actions in their familiar working environment. Central, policy-controlled, monitored, traceable. That way you have everything under control.
Business processes are often mapped with workflows. That would also be your ideal solution for IT operations. Connector allows you to start actions in ScriptRunner within a workflow and return the results. This enables you to separate the logic in the workflow from the technical implementation of individual steps with PowerShell. You use every system for what it does best.
There are also tasks from specialist applications that affect your field of work and trigger follow-up activities. You can also automate these directly via connector. To do this, connect the application backend to ScriptRunner and define the tasks that the users are to trigger in the application. You define the task in the script and leave the execution to ScriptRunner.
Automating with the web service connector via REST enables you to implement complex use cases in a variety of ways. There is always a calling instance, the web service client. This can be found in different forms on the source system.
In ScriptRunner, first configure the address of the calling source system with the web service client. Only REST calls from this address are accepted by connector. A separate connector is required for each system. For authentication, you specify which authorized account is to be used to call the web service connector in ScriptRunner. Then define which of the configured actions can be started via this connector. Only assigned actions can be started with a REST call.
Now configure the web service client on the source system so that a valid and authorized REST call can be executed with a JSON data object.
If the source system executes a REST call to the web service connector, connector first checks for source address. If this is valid, the authentication check is run afterwards. If the authentication is valid, the transmitted data is extracted. Before the action is started, it is determined whether it can be started by the connector. If so, the valid parameters are passed to the action and it starts. At the same time, an ID is transferred to the source system, with which the system can retrieve the results and reports of the action.
To start and process an action, convey the corresponding data to ScriptRunner using the REST call. The data is transmitted in JSON format.
Since not every application or service has a native web service client or a ScriptRunner template for it, the connector supports various options:
In the action script, REST calls can be made to the source system. This allows you to implement bidirectional communication with the application, e.g. to request further information, transfer comprehensive data to the application or trigger further processes on the source system depending on the ScriptRunner process.