TIBCO BusinessWorks 5.x to 6.x Service Transformation

WodenSoft can help your company for transformation of your integration services from TIBCO BusinessWorks 5 to BusinessWorks 6.

Why do we need TIBCO BusinessWorks 6 transformation ?

  • Tibco BusinessWorks 6 is a modern integration and service delivery platform ready for modern concepts such Mobile, Cloud, Internet of Things or Microservices.
  • Tibco BusinessWorks 5.x doesn’t support cloud technology.
  • Technical support for various Tibco BusinessWorks 5.x versions has ended and the rest will not be available shortly. Please check support status of your Tibco version from here.

Key Insight

  • With TIBCO BusinessWorks 6, Service and API implementation is easy. Easy process, service, and API implementation is necessary to adapt integration problems in a fast and agile way.
  • TIBCO BusinessWorks 6  is a modular lightweight platform for integration projects.
  • It has unified view for central management and monitoring.
  • SOAP and REST services can also be implemented within one single process implementation. Of course, within an operation, you can call several different REST, SOAP and/or BusinessWorks processes.
  • TIBCO BusinessWorks 6 supports all stages such as development, debugging, testing, and deployment based on the Eclipse ecosystem.
    • Tibco BusinessWorks 6 supports continious integration with  Jenkins and End-to-end automated test automation with JUnit plugin because it is based on Eclipse IDE. This capability enables to test the impact of a change to all related services with one button click.
  • With TIBCO BusinessWorks 6 cloud support, engines load can be scalable in busy days such as monday campaings.

BusinessWorks 6 vs. BusinessWorks 5

  • Easy process, service, and API implementation is necessary to adapt integration problems in a fast and agile way.
  • Support for Complete Development Lifecycle
  • Modular Lightweight Platform
  • Unified View for Central Management and Monitoring

Intelligent Canvas

  • As usual, you can drag and drop either an activity (e.g. mapper) or a connector (e.g. SAP or Salesforce) to the workspace.
  • In addition, you can also drag and drop other artifacts.

For example, dragging a CSV file creates a popup where you can select one of several File activities such as a FilePoller. This step also automatically adds configuration such as the file name. The same is possible for parsing a XML Schema, sending a SQL statement to a relational database, calling SOAP/REST services or BusinessWorks processes, and others.

  • Thereby, mappings can use data from all previous activities as input instead of just the last activity or using a workaround such as storing information into a variable.
  • The intelligent mapper includes auto-complete features (e.g. adding parentheses or commas between different inputs in a function), automatic warnings (e.g. if 0 is used for an 1-based array index) or quick fixes (e.g. for type conversion).

Multi-Operation Modeling

In most tools, you have to implement each SOAP or REST service operation in a single process. This gets really confusing in more complex services and projects. In TIBCO ActiveMatrix BusinessWorks 6, all operations of a service can be implemented in one single process. Each operation can be shown or minimized. SOAP and REST services can also be implemented within one single process implementation. Of course, within an operation, you can call several different REST, SOAP and/or BW processes.

Stateless vs. Stateful Services and Processes

While REST services are always stateless by definition, SOAP services and BusinessWorks processes can also be stateful.  The IDE allows you to select a stafeful checkbox and makes your life easier for implementing stateful services, for example not allowing implementing a REST service or storing state in-memory instead of needing an external persistence store.

The conversation feature creates correlation IDs and the BusinessWorks engine helps to correlate everything automatically without coding. Conversations represent two or more related message exchanges in the same process, which are correlated by the engine.

For example, a conversation between a process and its clients, or between a process and its backend service.

Compensation Handler and Exception Handling

Transactions are complex and an anti-pattern for modern architectures, especially in distributed systems. Two-Phase-Commit (aka XA) transactions are even worse. Many technologies do even not support transactions at all. SOA introduced the concept of compensations to revert actions after an exception occurs. BusinessWorks 6 offers compensation handlers and a sophisticated, but easy model to define scopes with activities and exception handlers.

Support for Complete Development Lifecycle

Support for the complete development lifecycle within one single IDE is important for agile projects. TIBCO BusinessWorks 6 supports all stages such as development, debugging, testing, and deployment based on the Eclipse ecosystem.

Combination of BusinessWorks Processes and Java Coding

Development, debugging, testing, and deployment are possible in one single environment. Seamlessly implement BusinessWorks processes and Java code using native Eclipse features such as its source code editor or debugger. Deployment, execution, and debugging can be done locally or on a remote server on premise or in the cloud. End-to-end automated testing both at unit and project level are supported by using BusinessWorks JUnit plugin and Eclipse SDK.

Configuration on Different Levels at Design Time & Runtime

Application configuration profiles offer customizable alternatives to choose from at design and runtime. Application properties can be configured at runtime via command line or web user interface. Process variables exist in one process instance while process properties exist for all process instances.

Modular Lightweight Platform

Now, it is time for a “must-mention” buzzword: Microservices. BusinessWorks 6 supports Microservices.

Let’s, done SOA right! This can means a lightweight platform, first-class support for rest services, independent development and deployment, continuous integration and continuous delivery, and cloud-readiness.

First-Class REST Support

The creation of a REST service is very simple and Swagger is used for testing REST services. Swagger documentation is auto-generated, and provided for any REST endpoint build and deployed using BW6.

API Exchange can be leveraged to make this REST service available as Open API via the Swagger-generated document. Of course, “old” standards such as SOAP or JMS are supported implicitly within BusinessWorks 6 and API Exchange, too.

Lightweight Platform

TIBCO ActiveMatrix BusinessWorks 6 uses a scalable runtime with low hardware footprint. Each service is managed, deployed, and scaled independently from each other. Thus, new features, change request, and scalability can be adapted very flexible due to changing business requirements without re-deploying complete applications or large enterprise archives. Different services can be deployed to a single BusinessWorks engine or scaled out to several different runtimes.

Continuous Integration and Continuous Delivery

Another part of modern software development—call it Microservices, agile, or whatever—is Continuous Integration and Continuous Delivery to enable quick releases, bug fixes, and change requests of services.

TIBCO BusinessWorks 6 offers a specific Maven plugin (optimized for BusinessWorks), but also supports any other framework such SVN or Git for version control management,

ANT or Gradle for build management, or Jenkins for continuous integration. Many TIBCO customers use SilverFabric for Continuous Delivery and elastic on-premise, cloud, and hybrid deployment.

Besides, you can also use other tools such as Chef, Puppet or Docker as standalone framework or in combination with TIBCO SilverFabric.

Support for Mobile Devices and Internet of Things

TIBCO BusinessWorks 6 is ready for the future, i.e. mobile devices and Internet of Things.

Use the mobile plugin to send push messages to mobile devices such as Apple or Android operating systems and receive them in Mobile Apps using Java, ObjectiveC, Swift, and other technologies.

Cloud Readiness

Most TIBCO customers still use on-premise deployments based on classical servers or virtual machines. However, BusinessWorks 6 is ready for the cloud and container-based development.

Whether you want to keep the classical strategy or move to new concepts such as private, public or hybrid cloud using solutions such as SilverFabric, CloudFoundry, Amazon Web Services, or anything else…

Whether or not you keep a classical development lifecycle using development, test and deployment in different stages or move to Microservices, “containerization” with Docker, or Continuous Delivery/DevOps.

Unified View for Central Management and Monitoring

TIBCO products such as BusinessWorks, API Exchange, EMS, BusinessEvents, StreamBase, MDM, LogLogic, Hawk, etc. are loosely coupled, but highly integrated.

Migration Path for BusinessWorks 5

Last, but not least, an important message for existing TIBCO customers: Thousands of TIBCO customers use TIBCO BusinessWorks 5.x in mission-critical systems. Our recommendation is to use BusinessWorks 6 and all its great new features for new projects. Only migrate old projects right now if you can create added business value or if technical reasons require it.

TIBCO ActiveMatrix BusinessWorks 6 Is Ready for Prime Time

TIBCO ActiveMatrix BusinessWorks 6 is a leading Integration and Service Delivery Platform. Many TIBCO customers are already starting new projects with it. Several deployments are already in production.

TIBCO BusinessWorks 6 is a modern platform ready for Mobile, Cloud, Internet of Things and Microservices.

The combination of these features in a single solution is unique and makes every user happy, whether it’s an integration designer, hardcore developer, tester or administrator.


TIBCO BusinessWorks 5.x to 6.x service transformation can be done with several phases. This transformation does not bring additional hardware costs, because existing servers can be used.

For instance, TIBCO BusinessWorks 5 can be replaced with TIBCO BusinessWorks 6 on an existing server and TIBCO BusinessWorks 6 services can be deployed on this server.

Also, TIBCO servers support more than one version on the same machine in different directories.