Documentation

{{docApp.title}}

{{docApp.description}}

How can we help?

{{docApp.searchError}}
{{product.name}}

Searching in {{docApp.searchFilterBySpecificBookTitle}}

{{docApp.searchResultFilteredItems.length}} results for: {{docApp.currentResultsSearchText}} in {{docApp.searchFilterBySpecificBookTitle}}
Search results have been limited. There are a total of {{docApp.searchResponse.totalResultsAvailable}} matches.

You have an odd number of " characters in your search terms - each one needs closing with a matching " character!

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

{{docApp.libraryHomeViewProduct.description}}

  1. {{book.title}}

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

{{group.description}}

  1. {{book.title}}

{{group.title}}

Data Polling

Polling Data for System Integration

With some types of integrations, customers will have asked if they can poll our application data source in order to detect change conditions, in order to simulate change events to fire integrations for other systems. While this is simple to implement conceptually, it’s a very inefficient approach, especially when large data sets are concerned, and short polling times are needed to simulate near-real-time integrations. Dataset sizes in Hornbill are hugely variable and tend to grow over time so something that might work today may well become a problem in the future.

Hornbill is fundamentally a transactional system, the underlying application database prioritizes optimization for transactional performance over data query performance, in essence, the application database is not designed or optimized for large dataset queries. Through the user interface, datasets are always managed, and queries are paged and kept small in order to keep user responsiveness optimal.

Warning

If you do need direct database access for on-demand bulk data queries and/or data extraction, this is possible using our Direct Database Access(DDA) Service service. This service is designed for those organizations that wish to use a data warehouse and/or external analytics tools. The DDA Service is designed for this exact purpose, it provides an isolation barrier between your application database and your data extract needs, ensuring large data extractions or complex queries, no matter how frequent, do not have a direct impact on your instances main database that would otherwise impact the responsiveness of your Hornbill instance.

When asked, we will always look at the merit of each request to perform this type of integration, but as a general rule we will not allow large dataset polling of your instance main database, there is no direct database connection to your instance (unless you have access to the DDA Service, and our APIs are generally restricted in the spirit of “fair use”, in our case fair use means, largely transactional integrations.

As an alternative to polling, the Hornbill platform provides a comprehensive set of integration capabilities that are available to customers, these are focused primarily on transactional events. Hornbill can call out to any other system via APIs through our iBridge and ITOM integration capabilities, while any third-party system can call into Hornbill via our comprehensive web service APIs. This is a far better, and far more supportable solution to systems integration.

General Guidelines for inbound (third party to Hornbill) and outbound (Hornbill to third-party) Integrations

  • APIs are available and free to use for transactional inbound integration needs
  • iBridge provides a comprehensive library of ready-made cloud integrations
  • ITOM DevOps edition provides an environment for you to build behind-the-firewall or in-the-cloud custom outbound integrations.
  • Webhooks for system integration

The above also applies to large data set extraction through reports\CSV or other methods including direct Query APIs. Hornbill provides a DDA Service that is far better suited for these requirements and all reporting needs.

In This Document