Getting familiar with a Mule flow
Previously, we’ve built a simple Mule application consisting of the following:
- An HTTP Listener as an event source
- A Transform Message component and a Logger as an event processor
Here, the event source and event processor are the key elements of a Mule flow.
The Mule flow is responsible for the sequential execution of logical operations to achieve the desired outcomes, with the help of several Mule components and connectors.
You can consider it similar to a Salesforce flow.
A Mule flow is divided into two parts (see Figure 4.1):
- Event source
- It consists of an inbound endpoint that listens to the incoming request from the client or an event-based trigger and further forwards the request to event processors. It also receives a response in the end, which is returned to the client.
- Some of the commonly used message sources are HTTP, JMS, FTP, and Poller/Scheduler, based on a new event (for example, using Salesforce...
