I was all set to detail connecting BusinessWorks (BW) 5.x to ActiveMQ, but someone got there first
. My only minor edit to the tutorial would be to add that the JAR to be included in your BW project's classpath has changed from activemq-core-5.7.0.jar to activemq-all-5.xx.x.jar.
Note: ActiveMQ cannot understand Tibco EMS specific acknowledgement modes like Tibco EMS Explicit.
. My only minor edit to the tutorial would be to add that the JAR to be included in your BW project's classpath has changed from activemq-core-5.7.0.jar to activemq-all-5.xx.x.jar.Note: ActiveMQ cannot understand Tibco EMS specific acknowledgement modes like Tibco EMS Explicit.
Why connect BusinessWorks to ActiveMQ?
As to why you would want to connect the two technologies - it can be strategic.
Suppose your enterprise is heavily invested in both Tibco BusinessWorks and EMS, but would like to migrate to a more modern, open-source backed integration stack. Where do you start? Especially when:
- Rewriting all your BW applications takes time, money and retraining.
- The day to day business cannot be halted waiting on all application rewrites to conclude.
In these cases, often the least disruptive path forward is to realize that both EMS and ActiveMQ leverage the JMS API. Consequently, one can almost be a drop-in replacement for the other. This offers a low-risk entry point into migration: The BusinessWorks applications need only be configured to communicate with ActiveMQ rather than EMS, with all other code and messaging formats remaining constant.
Once messaging is replaced, the enterprise can take their time planning the larger task of deciding which applications to modernize, when and how.
Once messaging is replaced, the enterprise can take their time planning the larger task of deciding which applications to modernize, when and how.
