Difference between revisions of "Microsoft Orchestrator"

Revision as of 08:00, 4 August 2017

Home > Integration > Business Process Automation & Orchestration > Microsoft Orchestrator

Introduction

Hornbill provides a Integration Connector with Microsoft Orchestrator this allows you to plugin an existing Runbook from with your Orchestrator instance from our Integration Node allowing for your Business Process to run Orchestration flows within your network. Any number of Orchestrator Connectors are currently supported so if you multiple Microsoft Orchestrator Servers you need to connect to these can all be added just make sure to give each one an identifiable title so that they are easily selected from the Integration Node.

Configuration

You can configure the connection to your Microsoft Orchestrator instance/s in the admin tool under System > Settings > BPM Integrations and the + icon

When creating a new Integration Connector if you chose the type Microsoft System Center Orchestrator you will get the following:

HTTP Endpoint - API Endpoint for Orchestrator which contains a publicly accessible domain name i.e mydomain.com, the port must be 8443 as we send all connectors through this port followed by /Orchestrator2012/Orchestrator.svc
Username - Orchestrator Basic Authentication Username typically with the domain or machine name preceding the username
Password - Orchestrator Basic Authentication Password
SSL Verify Host / Peer - Occasionally when testing a machine that only has a self signed certificate these need to be unchecked.

Once created a Test Connection button will appear allowing you to test the connection details before using them inside an Integration Node.

Firewall

Typically a Firewall change will be needed for your Instance to communicate back to your Microsoft Orchestrator instance:

Our outbound IP address:
- European Data Center - 87.117.243.10
- North American Data Center - 69.174.241.48
- Beta Data Center - 195.188.254.61
Port: 8443

Invoking Microsoft Orchestrator Runbooks

Using the Business Process Designer and the Integration Call node you can invoke any defined Runbooks from your configured Microsoft Orchestrator instances into your business processes

Content Pack

As well as having the option to invoke your Runbooks from a business process, we have also provided a collection of our own runbooks for Microsoft System Center Orchestrator 2012 R2, to demonstrate runbook automation and integration with the Hornbill Collaboration platform and Service Manager application.

Download the Hornbill Runbooks following the instructions in the Microsoft Orchestrator Content Pack from the Related Articles Section.

@@ Line 47: / Line 47: @@
 ==Content Pack==
-As well as having the option to invoke Runbooks from a business process, we have also provided a collection of our own runbooks for Microsoft System Center Orchestrator 2012 R2, to demonstrate runbook automation and integration with the Hornbill Collaboration platform and Service Manager application.
+As well as having the option to invoke your Runbooks from a business process, we have also provided a collection of our own runbooks for Microsoft System Center Orchestrator 2012 R2, to demonstrate runbook automation and integration with the Hornbill Collaboration platform and Service Manager application.
 * Download the Hornbill Runbooks following the instructions in the '''Microsoft Orchestrator Content Pack''' from the '''Related Articles''' Section.
 [[Category:Integration]]