Mule is an open-source ESB that uses a Staged Event-Driven Architecture (SEDA) to decompose applications into stages connected by queues. This avoids overhead from thread-based concurrency and decouples event and thread scheduling from application logic. Mule can transport data between different endpoints like files, queues, and memory in a flexible way. XML pipelines in Mule can perform operations like validation, transformation, splitting, and merging on XML files as they flow through approval processes.

1. 1
By Vamsi Krishna M

2. What is Mule?
How do you use Mule?
What are the core Mule concepts?
Learning mule with File endpoints
2

3.  Mule is an open-source Enterprise Service Backbone
(ESB)
3

4. SEDA
 Staged Event-Driven Architecture
Java NIO
 Java New Input/output
4

5.  SEDA decomposes a complex, event-driven software application
into a set of stages connected by queues
 This design avoids the high overhead associated with thread-
based concurrency models, and decouples event and thread
scheduling from application logic
 By performing admission control on each event queue, the
service can be well-conditioned to load, preventing resources
from being overcommitted when demand exceeds service
capacity
 SEDA employs dynamic control to automatically tune runtime
parameters (such as the scheduling parameters of each stage)
as well as to manage load, for example, by performing adaptive
load shedding
 Decomposing services into a set of stages also enables
modularity and code reuse, as well as the development of
debugging tools for complex event-driven applications
5

6.  NIO is a collection of Java programming language APIs
that offer advanced features for intensive I/O operations
 NIO facilitates an implementations that can directly use
the most efficient operations of the underlying platform
 NIO includes:
 Buffers for data of primitive types
 Character set encoders and decoders
 A pattern-matching facility based on Perl-style regular
expressions (in package java.util.regex)
 Channels, a new primitive I/O abstraction
 A file interface that supports locks and memory
mapping
 A multiplexed, non-blocking I/O facility for writing
scalable servers
6

7. Folder to folder
Queue to queue
Shared memory to shared memory
Using different types of transports
In a flexible way
7

8.  An XML pipeline is a series of operation that are
performed on one or more XML files
 Examples include:
 validate
 transform
 prune (remove nodes)
 split (break a single XML file into many files)
 merge (join two or more files together)
8

9. Flow of XML document through approval processes
9
Submit
CRV
Deed
Matched
CRV
SSN
Stripped
CRV
Income
Tax
Audit
County
Audit
County
Approval
State
Audit
State
Approval

10.  Example of XML Operations used on CRV
10
Validate Split
Remove
SSN
Element
Store
Modify
Value
Add
Element
Modify
Value
Add
Element

11. Focus on specifying "What" not "How"
Empower business analysis to write machine-readable
specifications
Hide the "How" behind services with clear interfaces (SOA)
11

12. Mule Manager
Mule Model
Universal Message Object (UMO)
Endpoints
External Applications
12

13. <?xml version="1.0" encoding="UTF-8"?>
<Data>
<Element1>Hello World!</Element1>
<Element2>String</Element2>
<Element3>String</Element3>
<DansInvalidDataElement>This is Dans invalid data element</DansInvalidDataElement>
</Data>
13
XML Schema validation will generate an error message
when it gets to the fourth invalid data element:
Given the following XML Schema file:

14. <outbound-router>
<router
className="org.mule.routing.outbound.FilteringXmlMessageSplitter">
<endpoint
address="file:///c:/mule-class/out?outputPattern=$[ORIGINALNAME]"/>
<properties>
<property name="validateSchema" value="true"/>
<property name="externalSchemaLocation"
value="file:///c:/mule-class/labs/07-validate/my-
schema.xsd"/>
</properties>
</router>
</outbound-router>
14
To validate the XML Schema, just add two properties:
1) tell it to validate the document
2) tell it what file to use and where to find it

15. document : cvc-complex-type.2.4.d: Invalid content was found
starting with element 'DansInvalidDataElement'. No child
element is expected at this point.
15
This error message is generated on the Mule console when
an invalid data element is found. But what should we do
with it? How do we redirect it to the appropriate user?

16. 16