Documentation
    {{docApp.userSession.userId}}
    {{docApp.userSession.userName}}
    {{docApp.userSession.email}}
    Issuer : {{docApp.userSession.issuerInstance}}
    Expires : {{new Date(docApp.userSession.validUntil).toLocaleDateString()}}

{{docApp.title}}

{{docApp.description}}

INDEX

Documentation Library

Search for information on Hornbill Documentation.

{{docApp.searchError}}

{{docApp.searchResultFilteredItems.length}} results for "{{docApp.currentResultsSearchText}}" in {{docApp.searchFilterBySpecificBookTitle}}

Have questions about this site?

What is this site?

  • This website is Hornbill's new product documentation website and is currently under development.
  • It is intended that all existing and future public-facing documentation we produce will be available to search, browse and share.
  • Hornbill's current documentation is available at Hornbill Wiki but over time this content will be migrated to this documentation site.
  • Please feel free to have a look around at any time.

Why has Hornbill created this site?

  • Hornbill's products have moved on considerably since we introduced it almost 10 years ago. At the time, the MediaWiki tool was sufficient, but we have outgrown it.
  • Our customers are more enterprise focused and more self-sufficient than ever before, so for 2023 and beyond we have established a new documentation platform and team to drive our documentation initiative forwards.
  • We are aiming to deprecate the use of Hornbill Wiki for most Hornbill related documentation.
  • We want to enable our growing partner network with product resources and information, documentation beyond our Wiki approach is required.
  • We could definitely do with some help, and may even pay for some! If you have domain knowledge and would like to help, please check out our Hornbill Docs Contributor Guide and contact the Hornbill docs team at docs@hornbill.com.

What will this site be good for?

  • Community contribution will be facilitated, encouraged, and most welcome.
  • High quality documentation, will be kept up to date as rapidly as our products evolve.
  • Real-time content search and discovery.
  • Articles organized into books, books into libraries, creating a more natural and logical structure to our documentation.
  • Legacy API documentation and various other documentation sources will all be consolidated into a single unified documentation system.
  • Documentation available in browser as well as printable/viewable as PDF on demand.
  • Personalized documentation experience, allowing dark/light mode, article subscriptions, social media sharing and other useful features.
  • Almost all publicly available documentation on docs.hornbill.com will be open-source and available to fork on GitHub, allowing customers to derive their own custom documentation around Hornbill products should they wish to.

What is the timeline for this site?

  • We have taken the decision to publish and make available early, there is very little content at this time.
  • As and when we have completed/usable documentation, it will be published here.
  • We have a host of additional features we wish to add over time, so please watch this space.
  • We expect most of our existing documentation should be reviewed/migrated to docs.hornbill.com over the coming months.
  • The documentation project will be ongoing, will continue to expand, evolve and improve day-by-day.

{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

{{group.title || group.id}}

{{group.description}}

  1. {{book.title}}

{{group.title}}

{{book.title}}
More...

Integration Connectors

Hornbill provides integration connectors with HP Operations Orchestration and Microsoft Orchestrator. This allows you to plugin with your 'HP Operations Orchestration or Microsoft Orchestrator from a Hornbill workflow using the Cloud Automation node.

HP Operations Orchestration Content Pack

Configuration

You can configure the connection to your HP Operations Orchestration 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 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
    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 Cloud Automation Node.

Firewall

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

Hornbill Data Center Outbound IP Address Port
Europe 87.117.243.10 8443
North American 69.174.241.48 8443

Invoking Orchestration Flows

Using the Business Process Designer and the Cloud Automation node you can invoke any of your defined Orchestration Flows from your configured HP Operations Orchestration instances within your business processes.

Content Pack

As well as having the option to invoke your Runbooks from a business process we have provided a Content Pack for HPE Operations Orchestration 10.50+, to demonstrate integration with the Hornbill Collaboration platform and Service Manager application.

This can be used to enable HPEOO administrators to include Hornbill Collaboration and Service Manager automations in their flow orchestrations.

Download the Hornbill Content Pack following the instructions in the HP Operations Orchestration Content Pack from the Related Articles Section.

Note

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

Configuration

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 Cloud Automation Node.

Firewall

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

Hornbill Data Center Outbound IP Address Port
Europe 87.117.243.10 8443
North American 69.174.241.48 8443

Invoking Microsoft Orchestrator Runbooks

Using the Business Process Designer and the Cloud Automation node you can invoke any of your defined Runbooks from your configured Microsoft Orchestrator instances within 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.

  • Version {{docApp.book.version}}
  • Node {{docApp.node}} / {{docApp.build}}
In This Document