Mule Configuration

´Ø Spring based

´Ø mule-config.xml

´(default)

´Ø Multiple config files

´using import

´Architecture is based on concepts discussed

´in Enterprise Integration Patterns

 

Why choose Mule

´Ø No prescribed message format

´– XML, CSV, Binary, Streams, Record, Java Objects

´– Mix and match

´Ø Zero code intrusion

´– Mule does not impose an API on service objects

´– Objects are fully portable

´Ø Existing objects can be managed

´– POJOs, IoC Objects, EJB Session Beans, Remote Objects

´– REST & Web Services

´Ø Easy to test

´– Mule can be run easily from a JUnit test case

´– Framework provides a Test compatibility kit

´– Scales down as well as up

Mule Components

´Ø Endpoint

´– Channel, MessageReceiver, Connector

´Ø Transformer

´– Message transformation / enhancement

´Ø Router

´– Message flow control (inbound/outbound)

´Ø Service Component

´– Your integration logic lives here

Why use Mule ESB

´Ø Decouples Business Logic

´Ø Location Transparency

´Ø Transport Protocol

´Conversion

´Ø Message Transformation

´Ø Message Routing

´Ø Message Enhancement

´Ø Reliability (Transactions)

´Ø Security

´Ø Scalability

Mule: Lightweight and Adaptive Adaptive integration

´• Standards-based and vendor-neutral

´• Seamless integration with existing infrastructure

´• Plug-in architecture allows for building block

´approach

´• Use with any application server or standalone

´Development

´simplicity

´• Simplifi ed programming model

´• Ease of use through confi guration and control

´• Rapid development and deployment through

´code reuse

´Open source

´advantage

´• No expensive up-front license commitments

´• Access to source code allows customization and

´lowers risk

´• Vibrant developer community delivering best

´practices and modules

What Mule ESB isn’t

´Ø It does not place restrictions on your environment

´Ø It is not message queuing, it uses other (JMS

´capable) products

´– And, it does not require message queues

´Ø It is not complex

´Ø It does not need to be “the grand master of all

´integration endpoints across the enterprise”

´– Think big, start small

´– It plays nicely with other ESBs

What is Mule ESB? part 2

´Service creation and hosting • Expose transport end-points, EJBs, Spring beans, and POJOs as

´modular and reusable services

´• Host services as a lightweight service container

´Service mediation • Separate business logic from messaging

´• Shield service components from message formats and protocols

´• Enable location-independent service calls

´Message routing • Route messages based on content and complex rules

´• Filter, aggregate and re-sequence in-bound messages

´Data transformation • Exchange data across applications with varying data formats

´• Transform data as needed, based on need

´• Format messages across heterogeneous transport protocols