Insights from our project where we implemented TIBCO
October 25, 2021
Cezar Ginta

In our article series built around TIBCO, we discussed the importance of integration tools such as BusinessWorks 6 (, and we gained some insights on the benefits of using TIBCO for both enterprises and users (  

In today's article, we will focus on our success story where TIBCO BusinessWorks 6 helped us create an environment where new technologies can be implemented, but there is also room for older technologies needed in one singular platform.

Together with our client, we connected two agile teams to work as one to migrate high-quality software components promptly. We could simply stick to the migration strategy and maintain business continuity by using concepts such as CI/CD pipelines, delta deployments, and comprehensive end-to-end testing.

As a result, new services were integrated while supporting the legacy ones until decommission.

What were our goals?

The main goal was to get a step closer to a microservices-oriented architecture. With the help of TIBCO BusinessWorks, which facilitates the development of applications that fit inside this type of architecture, we created an ecosystem where we made the best of both worlds, new services and supporting the legacy one.  

Our secondary goal came as a result of our existing challenge. In this part, we needed to redesign and remove the redundant code to support a business logic that genuinely belongs to the integration layer. Migration by itself was not enough, and in this scenario, we understood that the next thing in our progress is to analyze current flows and propose redesign sessions. We successfully replaced SOAP web service implementations with lightweight and reusable services by applying the REST API pattern.

Join our upcoming webinar, Insights on TIBCO BusinessWorks 6 to find actionable insights about how TIBCO can impact your business.

Click here:

Taking advantage of innovative solutions that are available inside BusinessWorks 6

ActiveMatrix BusinessWorks 6 exposes a complete API. The same API can be used to construct a standard collection of custom components that can be utilized on subsequent projects.

By using TIBCO BusinessWorks 6 as an integration solution, we benefited from the out-of-the-box functionalities available in order to implement the required service security concerns. We matched the security concerns of our client with the answers that TIBCO provided. We know that every integration tool is as good as the solutions it can bring, by using the latest HTTPS protocols, user authentication, authorization mechanisms and administered access to integration APIs (Application Programming Interface) in a secure way using user management at the platform level.


Acting as an implementation partner, we supported the customer in achieving its migration goals. Our objective was to make the required changes with minimal impact on the business of the customer. We successfully integrated a new platform in the existing landscape and the migration to TIBCO. The value brought by using TIBCO as an integration platform was measured in the ease of adapting to changes and the integration of new business requirements.

More than 200 ESB interfaces have been successfully migrated to an API-first architecture, creating an ecosystem of applications that are modular and reusable, an ideal prerequisite for microservices.


The migration to TIBCO BusinessWorks 6 proved to be a great solution for moving to a singular integration platform and taking advantage of modern features and concepts, such as API-first architecture, containerization, and custom integration plugins development.

Check our FREE Case Study of Integration Platform Migration to TIBCO Business Works 6, where you can find out how we successfully migrated the legacy integration platform with ESB architecture towards TIBCO BusinessWorks 6 and a lean, microservices-based architecture.

Click to Download:

Talk to the team