Mule Flow Part 2

1. Mule Flow
Architecture Part 2

2. Message Processing Blocks
• Composite source scope allows you to embed
into a single message source two or more
Anypoint Connectors
• Whenever one of these listeners receives an
incoming message, it triggers a flow instance
and starts the message through the message
processing sequence

3. Message Processing Blocks
• Building blocks known as scopes provide
multiple ways to combine message
processors:
– Make your XML code much easier to read
– Implement parallel processing
– Create reusable sequences of building blocks

4. Exchange Patterns

5. Processing Strategies

6. Exception Strategies
• Determines how Mule responds if and when an error occurs
during the course of message processing
• Configure a custom exception strategy to respond in a variety of ways to a
variety of conditions
• Studio provides four pre-packaged error handling strategies to handle
exceptions thrown at various points during the message processing
sequence

7. Flow Architecture

8. Flow Architecture
• You could embed the filter and the
transformers inside the inbound endpoint:

9. Flow Architecture
• You could embed the filter and the
transformers inside the inbound endpoint:

10. Flow Configuration
• A typical flow might utilize the following
sequence:
– A message source consisting of one or more
inbound endpoints or other streaming connectors
triggers the flow each time it receives a message
– A filter may identify invalid messages and decline
to pass them to the rest of the flow for processing
– A transformer can convert the incoming message
into a data format consumable by the other
message processors in the flow

11. Flow Configuration
• Throughout the flow, you can do the
following:
– Send messages to queues
– Specify threading models
– Call various other flows

12. Question and answer