The Kelverion Runbook Studio provides rich graphical authoring of Azure Automation Runbooks without the need for a permanent internet connection. The Runbook Studio is aimed firmly at IT professionals who do not have much experience or knowledge of PowerShell but still want to leverage the power of Microsoft’s cloud based Azure Automation service. For experienced PowerShell users the Runbook Studio increases your productivity and makes your solution more supportable in the longer term. On going maintenance and operation does not need detailed PowerShell knowledge.
The Runbook Studio enables users to create Runbooks using the same script free, code free, graphical authoring approach they have become used to with System Center Orchestrator. Once the Runbook design is complete the tool will automatically generate Azure Automation Graphical Runbooks for upload and execution from Azure Automation. The Runbook Studio also provides a workspace to manage all of your Assets across multiple Automation Accounts and even multiple Azure Subscriptions from within one view. Within those Automation Accounts Create, Edit and Delete; Runbooks Variables Certificates Credentials Connections
One of the biggest challenges with leveraging PowerShell as an integration mechanism is the need for you as the designer to define exactly what target form, fields, data type and values you want when you come to call the commandlet. This means you need to have a deep working knowledge of the configuration of the target system. The Runbook Studio also has full integration with Kelverion’s growing library of Integration Modules for Azure Automation.
These Kelverion Integration Modules offer a unique discovery API which allows the modules to interrogate the target third party system and dynamically discover its configuration and setup, in exactly the same way that Kelverion’ existing Orchestrator Integration Packs operate. At Runbook design time the Runbook Studio hooks in to this discovery API and dynamically configures the commandlet inputs and outputs based on the data returned from the target system.
For example when you want to create an Incident Ticket in BMC Remedy ARS the Integration Module will query Remedy for a list of available forms. Once you select an Incident Ticket form, the Integration Module queries the form and automatically configures each field in the Remedy form as an input parameter for use in the Runbook Studio.
As a designer you no longer need to be an expert in the target system to build Azure Automation Runbooks, significantly reducing build time and increasing supportability of your automation solutions.