Mule

1. Mule ESB 2

2. Outbound Endpoint
Mapping message headers to transport headers

3. Mapping transport headers to message headers
Inbound Endpoint

4. Mule Message Variables
 Variables are user-defined metadata about a
message.
 Variables have three scopes:
Flow variables apply only to the flow in which they
exist.
Session variables apply across all flows within the
same application.

5. Mule Message Properties and Variables
 Message header consists of properties which
provide useful information about the message
 variables represent data about a message
 Properties have two main
scopes: inbound and outbound.Inbound Property

7. Transformation Types
 3 Types of Transformers
Type transformation - involves converting the ‘type’ of the
message, for example; converting a byte stream to a string or
converting a JMS Message to a Java object.
Message transformation involves converting the message itself,
for example; converting a BookingRequest object into an
AirlineTicket object.
Property Transformations involves the properties on a message.
Each message may contain properties, usually related to
the transport used. For example, a message sent to an
SMTP server would have ‘To’, ‘From’ and ‘CC’ properties

8. SplitterExample
<flow name="SplitterExampleFlow1" doc:name="SplitterExampleFlow1">
<http:inbound-endpoint exchange-pattern="request-response"
host="localhost" port="8081" doc:name="HTTP"/>
<splitter expression="#[xpath('//actor')]" doc:name="Splitter"
enableCorrelation="IF_NOT_SET"/>
<logger message="#[message.payload]" level="INFO"
doc:name="Logger"/>
</flow>

9. Mule Aggregator
Mule aggregators use the MULE_CORRELATION_ID and
MULE_CORRELATION_GROUP_SIZE to reassemble a split
message.

10. <flow name="aggregateLineItems">
<jms:inbound-endpoint queue="lineitem.complete“ connector-
ref="jmsConnector"/>
<collection-aggregator timeout="60000“ failOnTimeout="true" />
<custom-transformer
class="com.prancingdonkey.transformer.LineItemsToOrderTransformer"/>
<component
class="com.prancingdonkey.service.OrderProcessingService"/>
</flow>
Mule Aggregator Example

11. Resequencer
If fractions of the message are being processed in
parallel in different servers, there's a good chance
that they may take different lengths of time to be
processed, and consequently fall out of order.

12.  The Resequencer will wait for all of the messages in
the group to arrive (keeping track
of MULE_CORRELATION_ID and
MULE_CORRELATION_GROUP_SIZE )
 Reorder them according to their
MULE_CORRELATION_SEQUENCE index.
 The Resequencer outputs will be in distinct
messages,

13. THANK YOU