We’ve just rolled out a new upgrade to the WSO2 ESB; version 4.9. While 4.9 is not a major release, we feel that there’s enough of a leap in functionality that a bit of reading might be required. As Chanaka Fernando puts it, it brings over 100 improvements and 600+ bug fixes, including the addition of inbound endpoints to make the ESB the ultimate integration engine.
To help you out, our engineers have compiled a number of blog posts that will bring you up to speed on what you need to know.
- What’s new in the WSO2 ESB We’d recommend starting with Chanaka Fernando’s piece on what’s new, what’s improved and and how all of this ties in to make the 4.9 release important.
- Understanding the Failover Message Processor The Failover Message Processor is a nifty addition that helps guarantee message delivery when your usual message stores are down. Prabath’s Ariyarantha’s extremely detailed blogpost runs you through the theory of how this useful message delivery mechanism works and how to deploy it in your solution.
- How to get JMS Inbound Coordination running The concept of inbound endpoints now allows the WSO2 ESB to support many more transports in a multi-tenanted environment. Jagath Ariyarathne writes about using an inbound endpoint for coordinating inbound messages from the Java Message Service.
- Using worker / manager clusters without a load balancer Worker / manager cluster setups are quite common, especially when it comes to scaling applications. Ravindra Ranwala describes how to set up, configure and deploy such a cluster without using a load balancer. If you do have a worker / manager cluster set up, Ravindra’s next tutorial is about Message Processor Coordination support and its two main use cases.
- Everything MQTT MQTT and MQTT support is a topic in its own right. We’d recommend starting with Sriashalya Srivathsan’s concise introduction to MQTT, followed up with Elilmatha Sivanesan’s short post about how the WSO2 ESB supports MQTT. Then it’s back to Sriashalya on configuring Axis2 MQTT. Following up with improvements in the RabbitMQ space (listed on Maheeka Jayasuriya’s blogpost), we recommend Ravindra Ranwala’s writeup on the technical wizardry of getting the WSO2 ESB to use RabbitMQ, both as a producer and as a consumer. Then of course, there’s Kafka. In Kafka Inbound use cases, Kathees Rajendram writes on various ways to use the WSO2 ESB’s Kafka support to consume messages from Kafka brokers.
- Last, but not least: on preserving HTTP Headers The previous version of our WSO2 ESB had limited support for preserving HTTP header fields, but with new ESB 4.9.0 introduces new tools for this task. See Prabath’s blog for a short list of what those properties are.