The CompanyOur client is a very large semiconductor chip manufacturing organization in the world. To keep track of the different artifacts associated with their software product lifecycles they had been using a few multi-vendor and some homegrown proprietary ALM tools. To solve the issues of good interconnectivity between these tools and prevent information and execution silos, the Company had for some time, decided on and implemented a point – to – point (P2P) integration model and create pairs of integrated enterprise tools or bridges. As the projects to be integrated grew into hundreds, they found it difficult to manage this workload and support and be responsive to their end users who had integration customization needs for different projects every time they started a new project or adopted new tools. This is when they started looking for a better and more efficient integration solution.
P2P Solution and their drawbacksThe P2P solution was a good start but slowly it started having problems. This architecture and implementation lacked efficiency, flexibility and speed. Some key issues were:
- The point to point integration solution is a complex tightly coupled system and thus each enterprise tool pair required an average of few months to setup.
- The long initial integration setup time resulted in additional effort and cost for each pair.
- The other reason for the above complexity was the hardcoded nature of the P2P application. Each configuration setup required dozens of configuration files mostly in *.xml formats to be changed and tailor made to fit the integration logic. For a generic user, to setup and maintain such a setup was an immensely difficult task. The headcount for creating new integration bridges kept rising.
- The system eventually reached a complexity level that required developers to support and fix in case some component went down.
- Besides this, the P2P solution suffered from the same negativities that plague any other P2P solution today –lack of flexibility and scalability. With a hardcoded P2P solution, any change ranging from a simple change in URL of the tool to a version / API changes of any of the tools required the P2P solution’s configuration files to be re-configured if not changed as a whole.
Figure 1: Integrating 2 Instances of 3 tools using exclusive P2P Integration Solution Such problems with the P2P Integration Solution made the company rethink their strategy and explore a less complex yet scalable solution. Among several Integration options the Enterprise Service Bus – ESB approach is currently the most flexible and hence the coveted one. Kovair with its Omnibus ESB Integration Platform is one of the leading Integration vendors and has been helping organizations globally with their application tools integration needs. Kovair Omnibus Integration Platform was the choice of this customer after a very extensive and thorough review that matched their criteria of flexibility, high productivity, scalability and end user’s accessibility and most importantly a low coupling architecture. Besides this, Kovair’s Omnibus Integration Platform has been proving its worth across multiple enterprises in various industry verticals including networking, telecom, manufacturing and financial organizations.
The Kovair SolutionKovair Omnibus Integration Platform was installed on premise in the customer’s servers. Kovair Omnibus n-tier architecture allowed separate VMs to be used for the installation of the different components like database, application and the adapter / connectors for connecting the tools with the ESB integration hub. The infrastructure provisioning and installation was followed by the initial Integration configuration to setup a few bridges by the Kovair team. The integration is very much like a plug-n-play mechanism with the adapters being used to hook the tools into the Omnibus Integration platform. The configuration for the first integration pair/bridge was completed within a week’s time which also included Service Account provisioning and other infrastructure level preparations. The configuration in contrast to the hard coded nature of the previous P2P system was entirely a UI based point and click approach. This allowed the organizational stakeholders to quickly find their way around the application and get started all by themselves. It gave a lot of confidence to the customer engineering teams that Kovair Omnibus was very intuitive and easy to use and new team members were onboarding on their own. Within a few days team members were able to configure bridges in 1-2 hours. Other than this, there are quite a few other benefits of using Kovair as listed below:
- Nearly, 90% of the configuration can be managed right from a web based interactive UI. The other 10% comprises of the integration logic which was not a part of the generic omnibus integration behavior and can be overridden with some minimum work in the configuration files.
- Multiple disparate bridges that had to be separately maintained and managed previously can now be managed from inside a single ubiquitous application interface.
- Each bridge installation setup time is reduced from 6 months to 16 – 32 hours depending on the complexity of the bridge. In dollar terms, this amounts to a saving of about $48,000 per integration. The company has hundreds of integrations and as such the dollar savings can run into a few million dollars for 500 projects over a period of two years.
- In terms of flexibility and scalability too, the Omnibus proved to be beneficial. The neatly distributed n-tier architecture of Omnibus made it trivial or major changes like the change in any integration logic or changing the tool / adapter details from the view level of the application. This spared the user the pain of directly interacting with the “middleware” as was the case with the P2P solution where the user needed direct interaction and changes at the architectural level of the solution.
- Monitoring and troubleshooting too is made easy with Omnibus, since the built in monitoring reports and dashboards allow the user to have graphical and textual view of the integration process both on a discreet record level or a holistic bridge level.
- Within a quarter of introduction of Omnibus, nearly 80 bridges have been setup in the Development environment and they are being successfully deployed in production based on the priorities.
Figure 2: Integration of the 6 Tool Instances after the introduction of Kovair Omnibus Integration Platform