Business Process Automation & Orchestration
Business Process Orchestration
Currently Hornbill provides a powerful Business Process workflow tool allowing Business Users to create / update and manage their business processes, with the introduction of the Integration Node the power of this tool has been increased to now position Business Process Orchestration as part of the Hornbill offering.
Business Process Automation
Business Process Integration Connectors
Hornbill Provides three types of integration connectors for use inside a Business Process Hornbill iBridge , Microsoft Orchestrator and HP Operations Orchestration each of these can be configured in the Admin Tool via System -> Settings -> BPM Integrations.
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. No additional configuration is required for the Hornbill iBridge out of the box you will have access to our catalog of various integrations detailed here, new integrations can be requested on the Hornbill Forum and if accepted will be made available as part of our Continuous Delivery model. 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, if we do not provide an integration method or integration with a service you need then you can raise a request on our forum, we would like our customers to challenge us to provide all the necessary integrations they need from Hornbill Out of the Box and not require costly on site software deployments or consultancy.
Integration Services
The following Cloud Services are supported within the Hornbill iBridge:
- Amazon AWS
- Atlassian Jira Cloud
- BMC Remedyforce
- Cloudflare
- Freshbooks
- Freshdesk
- Freshservice
- GitHub
- Google Apps
- Google Translate
- Hornbill
- IFTTT
- Jive
- Pipedrive
- SalesForce
- Scoro
- ServiceNow
- Slack
- Yammer
- ZenDesk
Secure Credential Storage
All Hornbill iBridge integrations will require some form of Authentication, Hornbill provides a secure credential storage KeySafe which securely stores login credentials for all of the Hornbill iBridge Services.
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 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.
When creating a new Integration Connector if you chose the type HP Open Orchestrator you will get the following:
- 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 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 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.
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 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 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
- Port: 8443
Integration Call
Setting up a new Integration Call node within a Business Process is as follows:
1. Within the Business Process designer an Integration Call Node can be placed on the canvas.
2. You can then select one of your Integration Connectors , if you have not set any up Hornbill Integration Bridge will always be available.
3. Clicking the ellipsis on Method allows you to browse the content catalogue for the given Integration Connector and then to select a method to use within your Business Process.
4. Once a method has been selected you will need to select a Credential from the list these are controlled via KeySafe , the list is filtered based on the Authentication Type required by the Integration method.
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.