Mule is an open source lightweight ESB that uses ActiveMQ for asynchronous messaging. It supports both synchronous and asynchronous communication through JMS. Mule implements a "JMS Back Channel" approach where it uses JMS for synchronous communication differently than the normal JMS perception. Mule configurations define inbound and outbound JMS endpoints and flows that automatically create queues, invoke queries, transform messages, and send responses to clients via temporary queues.

1. Mule with ActiveMQ

2. Mule and ActiveMQ
● ActiveMQ is open source messaging
● Mule a lightweight Enterprise Service Bus (ESB)
● Enterprise Service Bean, A Interaction point of Software Application.
●Help to develop loose coupling
●No need to provide implementation details

3. Messaging Model
●Two Communication Model i.e. Synchronous and Asynchronous
● Messaging APIs handle Asynchronous communication like JMS
●Synchronous holds the connection(Web Service , RMI)
●Mule ESB works on “JMS Back Channel” theory
●“JMS Back Channel” is type of JMS Synchronous communication, a different from normal JMS
perception.

4. JMS Endpoint
• Inbound
• Outbound

5. Configuration file

6. About Flow
●Queues get created automatically
●Folder get created
●Query getting invoked as per Poller configured frequency.
●DataWeaver (Transform Message) transfer message in required format.
●Response is sent to the client via a temporary queue. to be sent.
●The response queue is created for every message exchange and is destroyed immediately after the
client receives the response.