Microsoft System Center Orchestrator Integration

From Hornbill
Revision as of 09:06, 3 August 2017 by SteveGoldthorpe (talk | contribs) (→‎Installation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Microsoft System Center Orchestrator Integration

Overview

We've provided a collection of runbooks for Microsoft System Center Orchestrator 2012 R2, to demonstrate runbook automation and integration with the Hornbill Collaboration platform and Service Manager application.

Open Source

The System Center Orchestrator Integration is provided open source under the Hornbill Community Licence and can be found Here on GitHub

Installation

Download the Runbook Export from the Github repository, and place on your System Center server.

The file supplied is an export of a collection of runbooks, developed in SCOrch 2012 R2. This can be imported in to SCOrch by right-clicking on the Runbooks folder of your choice within the Orchestrator Runbook Designer, and click Import.

The runbooks use three global variables to identify the Hornbill instance and API key to use to invoke Hornbill API calls. These variables should be populated as so:

  • Hornbill\Hornbill API Key : This is the API key for the user account that should be used to perform the Hornbill API calls
  • Hornbill\Hornbill Instance ID : This is the (case sensitive) ID of your Hornbill instance (the yourinstancename part of your Hornbill URL: http://live.hornbill.com/yourinstancename)
  • Hornbill\Hornbill Instance Zone : This is the zone where your Hornbill instance resides:
    • eur - If your instance resides in the European zone
    • nam - If your instance resides in the North American zone

Once the runbooks have been imported, and the global variables have been configured, please see the description against each for more information about the runbook, and the APIs that they use.