Chapter 1. Discovering Mule
Figure 1.1. Point-to-point integration approach: everyone must speak the language of everyone.
Figure 1.2. Application-invasive integration broker approach: everyone must speak the language of the broker.
Figure 1.3. Enterprise service bus approach: the bus speaks the language of everyone.
Figure 1.4. ESB nodes distributed at strategic network locations
Figure 1.5. Mule ESB acting as a mediator between an authoring tool and a publication application
Figure 1.6. A Mule model is the runtime environment into which services are hosted.
Figure 1.7. A Mule service mobilizes different moving parts to process requests.
Figure 1.8. A Mule transport provides all the ESB elements required for receiving, sending, and transforming messages for a particular protocol.
Figure 1.9. Transformers can be chained to cumulate their effects.
Figure 1.10. A router can leverage filters to dispatch messages based on their properties.
Figure 1.11. The different Mule moving parts involved in the Publication application configuration
Figure 1.12. Standard event processing in a Mule service
Chapter 2. Configuring Mule
Figure 2.1. Moving parts and message flow of the echo example
Figure 2.2. Configuration structure defined by Mule’s XML core schema
Figure 2.3. Locating the XML schema of the VM transport
Figure 2.4. A Mule instance can load independent XML configuration files and properties files.