Difference between revisions of "Business Process Automation & Orchestration"

Latest revision as of 08:13, 17 July 2020

Home > Integration > Business Process Automation & Orchestration

Introduction

Hornbill provides a powerful Business Process workflow tool allowing Business Users to create / update and manage their business processes, with the introduction of the Cloud Automation the power of this tool has been increased to now position Business Process Orchestration as part of the Hornbill offering.

Hornbill iBridge

Hornbill Provides its own out of the box integrations with various cloud providers as part of our Integration Bridge service (iBridge), The Hornbill iBridge allows you to integrate Automated tasks within a Business Process without the need to install or configure any on premise software or make any firewall changes.

All Hornbill iBridge automations are provided with simple to use input and outputs that can easily be mapped into an existing Business Process with a completely code less design.
Hornbill iBridge Provides over 400 integrations across 16 different vendors out of the box.

Business Process Integration Connectors

In addition to Hornbills iBridge, Hornbill Provides integration connectors for use inside a Business Process with Microsoft Orchestrator and or HP Operations Orchestration.

These can be configured in the Admin Tool via System -> Settings -> BPM Integrations.

HP Operations Orchestration

Hornbill provides an Integration Connector with HP Operations Orchestration this allows you to plugin an existing flow from with your 'HPOO instance from our Cloud Automation Node allowing for your Business Process to run Orchestration flows within your network. Any number of HPOO Connectors are currently supported so if you multiple HP OO 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.

Microsoft Orchestrator

Hornbill provides a Integration Connector with Microsoft Orchestrator this allows you to plugin an existing Runbook from with your Orchestrator instance from our Cloud Automation 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.

Invoking Business Process Orchestration

Using Hornbill's Business Process Designer you can easily invoke iBridge automations, as well as any of your defined Orchestration flows from HP Operations Orchestration, or your Runbooks from Microsoft Orchestrator. To facilitate this Hornbill provides an Cloud Automation node in the Business process designer.

@@ Line 7: / Line 7: @@
 |style="width:73%"|
 ==Introduction==
-Hornbill provides a powerful [[Business_Process_Designer | Business Process]] workflow tool allowing Business Users to create / update and manage their business processes, with the introduction of the [[#Integration Call| Integration Node]] the power of this tool has been increased to now position '''Business Process Orchestration''' as part of the Hornbill offering.
+Hornbill provides a powerful [[Business_Process_Designer | Business Process]] workflow tool allowing Business Users to create / update and manage their business processes, with the introduction of the [[Cloud Automation]] the power of this tool has been increased to now position '''Business Process Orchestration''' as part of the Hornbill offering.
 |style="width:5%"|
 |
@@ Line 13: / Line 13: @@
 == Related Articles ==
-:* [[Hornbill_KeySafe|KeySafe]]
 :* [[Hornbill iBridge]]
+:* [[IT Operations Management|Hornbill ITOM]]
+:* [[Auto Tasks]]
+:* [[HP Operations Orchestration]]
+:* [[Microsoft Orchestrator]]
 :* [[Business_Process_Designer|Business Process Designer]]
+:* [[Cloud Automation]]
 |}
-=== Business Process Integration Connectors ===
+==[[Hornbill iBridge]]==
-[[File:Hornbill-BPM-Integration-Connectors.png|400px|right]]
+Hornbill Provides its own out of the box integrations with various cloud providers as part of our '''Integration Bridge service (iBridge)''', The Hornbill iBridge allows you to integrate Automated tasks within a Business Process without the need to install or configure any on premise software or make any firewall changes.
-Hornbill Provides three types of integration connectors for use inside a Business Process [[Hornbill iBridge]], [[#Microsoft Orchestrator|'''Microsoft Orchestrator''']] and [[#HP Operations Orchestration|'''HP Operations Orchestration''']] each of these can be configured in the [[Administration | Admin Tool]] via '''System -> Settings -> BPM Integrations'''.
+* All Hornbill iBridge automations are provided with simple to use input and outputs that can easily be mapped into an existing Business Process with a completely code less design.
+* Hornbill iBridge Provides over 400 integrations across 16 different vendors out of the box.
+==Business Process Integration Connectors ==
+[[File:Hornbill-BPM-Integration-Connectors.png|500px|right]]
+In addition to Hornbills iBridge, Hornbill Provides integration connectors for use inside a Business Process with '''Microsoft Orchestrator''' and or '''HP Operations Orchestration'''.
+* These can be configured in the [[Administration | Admin Tool]] via '''System -> Settings -> BPM Integrations'''.
+<BR>
+<BR>
+<BR>
+<BR>
 ==== [[HP Operations Orchestration]] ====
-Hornbill provides an Integration Connector with [https://saas.hpe.com/en-us/software/operations-orchestration-it-process-automation HP Operations Orchestration] this allows you to plugin an existing flow from with your '''HPOO'' instance from our [[#Integration Call| Integration Node]] allowing for your Business Process to run Orchestration flows within your network. Any number of HPOO Connectors are currently supported so if you multiple HP OO 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.
+Hornbill provides an Integration Connector with [https://saas.hpe.com/en-us/software/operations-orchestration-it-process-automation HP Operations Orchestration] this allows you to plugin an existing flow from with your '''HPOO'' instance from our [[Cloud Automation]] Node allowing for your Business Process to run Orchestration flows within your network. Any number of HPOO Connectors are currently supported so if you multiple HP OO 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.
-When creating a new [[#Business Process Integration Connectors| Integration Connector]] if you chose the type '''HP Open Orchestrator''' you will get the following:
-[[File:HP-OO-Create-Connector.png|900px|center|text-right]]
-* HTTP Endpoint - API Endpoint for HPP which contains a publicly accessible domain name i.e hp.mydomain.com, the port must be 8443 as we send all connectors through this port followed by /oo/rest/v2
-*Username - HPOO Basic Authentication Username
-*Password - HPOO Basic Authentication Password
-* SSL Verify Host / Peer - Occationaly 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 Call| Integration Node]].
-===== Firewall =====
-Typically a Firewall change will be needed for your Instance to communicate back to your HPOO instance:
-* '''Our outbound IP address: '''
-** European Data Center - 87.117.243.10
-** North American Data Center - 69.174.241.48
-* '''Port:''' 8443
-==== Microsoft Orchestrator ====
-Hornbill provides a Integration Connector with [https://technet.microsoft.com/en-us/library/hh237242(v=sc.12).aspx Microsoft Orchestrator] this allows you to plugin an existing Runbook from with your '''Orchestrator''' instance from our [[#Integration Call| 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.
-When creating a new [[#Business Process Integration Connectors| Integration Connector]] if you chose the type '''Microsoft System Center Orchestrator''' you will get the following:
-[[File:MS-O-Create-Connector.png|900px|center|text-right]]
-* 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 machinename preceding the username
-*Password - Orchestrator Basic Authentication Password
-* SSL Verify Host / Peer - Occationaly 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 Call| Integration Node]].
-===== Firewall =====
-Typically a Firewall change will be needed for your Instance to communicate back to your Microsoft Orchestrator instance:
+==== [[Microsoft Orchestrator]] ====
-* '''Our outbound IP address: '''
+Hornbill provides a Integration Connector with [https://technet.microsoft.com/en-us/library/hh237242(v=sc.12).aspx Microsoft Orchestrator] this allows you to plugin an existing Runbook from with your '''Orchestrator''' instance from our [[Cloud Automation]] 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.
-** European Data Center - 87.117.243.10
-** North American Data Center - 69.174.241.48
-** Beta Data Center - 195.188.254.61
-* '''Port:''' 8443
-=== Integration Call ===
+==Invoking Business Process Orchestration==
-Setting up a new '''Integration Call''' node within a [[Business_Process_Designer | Business Process]] is as follows:
-<div>
+Using Hornbill's Business Process Designer you can easily invoke iBridge automations, as well as any of your defined Orchestration flows from '''HP Operations Orchestration''', or your Runbooks from '''Microsoft Orchestrator'''.
- [[File:Integration-Call-1.png|left|thumb]]
+To facilitate this Hornbill provides an '''[[Cloud Automation]]''' node in the Business process designer.
-. Within the [[Business_Process_Designer | Business Process]] designer an Integration Call Node can be placed on the canvas.
-</div>
-<br clear=all>
-<div>
-[[File:Integration-Call-2.png|left|thumb]]
-. You can then select one of your[[#Business Process Integration Connectors| Integration Connectors]] , if you have not set any up '''Hornbill Integration Bridge''' will always be available.
-</div>
-<br clear=all>
-<div>
-[[File:Integration-Call-3.png|left|thumb]]
-. Clicking the ellipsis on '''Method''' allows you to browse the content catalogue for the given [[#Business Process Integration Connectors| Integration Connector]]  and then to select a method to use within your Business Process.
-</div>
-<br clear=all>
-<div>
-[[File:Integration-Call-4.png|left|thumb]]
-. Once a method has been selected you will need to select a Credential from the list these are controlled via [[Hornbill KeySafe | KeySafe]] , the list is filtered based on the Authentication Type required by the Integration method. If the list is empty the type of credential is shown by hovering the mouse over the '''i''' against the credential.
-Request Parameters marked with the red Mandatory marker must be populated and you will be able to see any Response Parameters that will be exposed to the Business Process on completion of this method.
-</div>
-<br clear=all>
 [[Category:Integration]]