Omnibus Integrations Middleware is the only multi-vendor ALM/SDLC tools integration technology that is based on the Enterprise Service Bus (ESB) Architecture. Serving as the single data repository of all essential ALM/SDLC services such as collaboration, traceability, process automation, security, reporting and analytics, Omnibus integrates multiple tools for multiple functions using tool-specific Adapters.


Omnibus Integration Framework is SOA-based. It has denied a common interface model to expose the objects tracked or managed within an ALM/IT tool along with the object metadata, events, actions and relations between the objects. This interface provides mechanism to collect events raised within a tool and also to perform actions on the objects. This common interface is implemented as a Web Service and named as Omnibus Adapter. Each tool requires an Omnibus Adapter built specifically for that tool to hook to Omnibus Integration Framework.

Omnibus Framework has a Conigurator tool and an Execution Engine. Conigurator tool offers an easy drag-drop presentation to setup integration lows between participating tools. This tool facilitates establishing and customizing integration rules as per organization needs. Omnibus Execution Engine is the central component responsible for retrieving the event messages collected by Adapters, processing those event messages according to Integration lows and then sending action messages to target tools through Adapters.


Ability to integrate multiple tools on the bus for the entire development & IT Lifecycle
Service Oriented Architecture (SOA) based Enterprise Service Bus Architecture
Supports 2-way Synchronization and Federation
Thin Adapters – no hard-coded business rules
High level ‘Tool Class’- specific API
Synchronization of data and relations between Objects
Conflict Detection and Mediation
Omnibus augments integrated tools’ capabilities for Process & Traceability
Comprehensive and user-friendly Web interface

Being ESB-based, cost-effective, flexible and user-friendly, Omnibus does away with complex and costly tools integrations, overcoming limitations of the existing point-to-point and single-vendor tools integrations. Its distinct advantages have been explained as under:

Significantly Simpler Development:

A point-to-point integration between every pair of n tools, we need n x (n-1) / 2 number of integrations. Accordingly, for a simple case of 5 tools, this amounts to 10 integrations and just by doubling the number of tools to 10 will result in a 4.5 fold increase in number of integrations to 45. On the contrary, Omnibus is based on the Enterprise Service Bus architecture which needs 5 and 10 adapters, just one per tool! Moreover, replacement of one of 5 and 10 tools needs replacement of just one adapter, a far cry from the redevelopment of 4 and 9 integration codes respectively.

Best-of-breed Tools for Best Functions:

Omnibus Integration allows integration of multiple third party tools from different vendors (for eg.  VSTS Designer, Rational, Eclipse, Subversion, TFS, ANT, J Unit, Quick Test Pro, Clarity etc.)  for the same function. What is even better, it can support simultaneous usage of multiple tools from multiple vendors in a single tool ecosystem. This allows organizations to select best-of-breed tools available in the market without locking themselves into a single-vendor solution Flexibility of Integration

Also Read more about IT service management