Mule is a lightweight Java-based ESB and integration platform that allows applications to connect and exchange data through message processing. Flows link together individual message processing elements to handle message receipt, processing, and routing. At its simplest, a flow is a sequence of message processing events where a message passing through may be transformed or have other operations performed. Flows support various configurations including subflows, synchronous flows, asynchronous flows, and batch jobs. Transformers convert message formats between different destinations and can rearrange or modify message fields using tools like DataWeave. Connectors function as endpoints to send and receive messages between flows and external data sources.

2. • Mule, the runtime engine of Anypoint Platform, is a
lightweight Java-based enterprise service bus (ESB) and
integration platform that allows developers to connect
applications together quickly and easily, enabling them to
exchange data.
• Mule applications accept and process events
as messages through several message processors plugged
together in a flow.

3. A flow is the construct within which you link together several
individual elements to handle the receipt, processing, and
eventual routing of a message.
How flows look like?

4. • Select From mule pallete flow.
• Drag flow icon from mule pallete to message flow.
• Its looks like something

5. AT THE SIMPLEST LEVEL, FLOWS ARE SEQUENCES OF
MESSAGE-PROCESSING EVENTS. A MESSAGE THAT
ENTERS A FLOW MAY PASS THROUGH A WIDE
VARIETY OFPROCESSORS.

6. FLOW
. In general, a building block corresponds to an icon in the Anypoint Studio
GUI, which in turn represents a message source, processor, or component.

7. • Subflow
• Synchronous Flow
• Asynchronous Flow

8. Subflows, which always run synchronously, inherit both the
processing strategy and exception strategy of the flow that
triggered its execution.

9. •

10. Asynchronous flows begin processing a message when triggered
by another flow. Since this type of flow does not need to return
data to the flow which triggered it, it can execute simultaneously
to its triggering flow.

11. A batch job is a top-level element in Mule which exists outside all Mule flows.
Batch jobs split large messages into records which Mule processes
asynchronously; just as flows process messages, batch jobs process records.

12. Again Search in pallete for batch.
Drag it to message flow.

13. Transformers convert message payloads to formats expected by
their destinations. Mule ESB provides many standard
transformers, which you configure using predefined elements and
attributes in your Mule XML configuration file
The most powerful tool for transforming a message is
the DataWeave Transformer, which can not only change the
format of the message, but also rename, aggregate, split or
rearrange the fields in it in any way you desire.

14. CONFIGURING TRANSFORMERS-:YOU CAN
CONFIGURE A
transformer locally or globally. You configure a local transformer right
on the endpoint or in a flow or where you want to apply it, whereas you
configure a global transformer before
any <model> or <flow> elements in your Mule configuration file and
then reference it.
Chaining Transformers-:You can chain transformers together so
that the output from one transformer becomes the input for the next.
To chain transformers, you create a space-separated list of transformers
in thetransformer-refs or responseTransformer-refs attributes or by
creating multiple <transformer>elements as shown above.
TRANSFORMERS

15. ObjectToOutputHandler-: Converts a byte array into a String.
ObjectToString-: Returns human-readable output for various kinds of objects.
Useful for debugging.
StringAppendTransformer-: Appends a string to an existing string.
StringToObjectArray-: Converts a string to an object array. Use the
configuration element <string-to-byte-array-transformer>

16. •

17. CONNECTOR
All connectors can function as endpoints by sending and
receiving messages between flows or between a flow and some
other data source outside of Mule. Some connectors
are endpoint-based, meaning that you configure them either as
inbound or outbound endpoints in your flow, then specify other
operation logic within the configuration of that endpoint. Some
connectors are operation-based, meaning that they allow you to
invoke specific actions against an API, Web service, or database.