Part 3. ESB case studies

We have worked with small examples in the previous two parts to introduce the basic concepts and the core functionalities of Mule and ServiceMix. In this part we work with larger examples to provide more insight in how to implement larger integration solutions.

In addition to the case studies, we also introduce a pattern-based design approach using the Enterprise Integration Pattern of Hohpe and Woolf. To be able to implement complex integration solutions, we need to have a sound design for the integration developers to work with and to have a clear picture of what will be implemented for all involved parties. Based on a case study, we use this design approach and then implement the case study with Mule and ServiceMix

When an integration solution is implemented and after several testing stages has been deployed on a production environment, we need ways to manage and monitor the ESB environment. We therefore show how we can monitor Mule and ServiceMix with JMX and manage the environment based on management patterns like a wire tap and a detour.

At the end of this part we introduce another interesting topic related to an ESB, which is a process engine. Process engines offer functionality to support service interactions which span more than one request-response flow. We look at how to integrate the jBPM process engine with Mule and the Apache Ode process engine with ServiceMix. By the end of this part you will have gained a lot of knowledge about implementing and designing integration solutions with Mule and ServiceMix and you will be experienced in using process engines together with an open source ESB.