Mule esb

2. 2
Mule Enterprise Service Bus
Support for more than 30 protocols and technologies
Simplified POJO-based programming model leveraging existing developer skill-sets for
fast deployment
Support for multiple access points such as JMS, JDBC, and SOAP
No reliance on vendor-specific proprietary protocols
Ease of use – services can be configured easily in one configuration file.
Extensive data transformations out of the box
Small footprint: memory and disk, no application server required
Integration platform model: highly modular, easily extensible codebase - implement
proven patterns and build streamlined solutions to unique challenges
The open source advantage: large community of real-world integration experts and
developers using Mule and contributing to codebase

3. Mule ESB Flow
Mule ESB 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 ESB enables easy integration of
existing systems, regardless of the different technologies that the applications
use, including JMS, Web Services, JDBC, HTTP, and more.
The key advantage of an ESB is that it allows different applications to
communicate with each other by acting as a transit system for carrying data
between applications within your enterprise or across the Internet. Mule ESB
includes powerful capabilities that include:

4. 4
Prerequisite
Build Tool
You must also install the Mule IDE with Eclipse (recommended), Maven, or Ant,
depending on which tool you want to use to build and run your projects.
Mule IDE
If you will install the Mule IDE, you install it after installing Mule--see Installing
Mule IDE.
Maven
If you do not want to use the Mule IDE, or if you will be using the Maven archetypes
to create a new transport or module, install Maven.

5. Mule Component Overview

6. Mule use to transport to receive and send message from and to all kind of source
including Java Messaging service (JMS), HTTP, FTP, TCP/IP,SMTP,POP3 and file.
Another important concept of mule is the service definitions which consist some
specific layers that can be solve the integration of multiple protocol and
application’s communication problems.
Application
Channel
Message Receiver
Connector
Transformers
Inbound Routers
Component
Outbound Routers
Message Dispatcher
Mule Component Overview

7. Application:
This identified the application we are integrating with Mule. It can any thing an
old legacy COBOL system, a .net application, a j2ee application, or even another
mule instance.
Channel:
Channels (an enterprise integration pattern) provide a way for external application
to communicate with mule. channel can also be used to inside mule to wire service
together.
Message Receiver:
This component can receive info from a certain channel
Connector:
Connector under how to send and receive data from certain channel, and connect
present to both of side sender and receiver end.
Connector have two components.

8. Message Receiver
Message Dispatcher
Transformers: Transformers transform the data one form to other form .
Inbound Router: it can determine what to do with a message once it’s receive from
channel.
Component: The component is the logic place with mule architecture to implement
integration logic not provided by other mule parts. a component can be
implemented with a no. of technologies like POJO(plane old java objects), groovy
script, REST services, BPM and among others.
Outbound Router: this is much same as the inbound routers but component
determines where a message is sent after it’s proceed by component.

9. Configuration Terms Of Mule ESB
Model :The first logical layer is the model layer. A Mule model represents the runtime
environment that hosts services. It defines the behaviour of Mule when processing requests
handled by these services. the model provides services with supporting features, like
exception listeners. It also provides services with default values that simplifies their
configuration.

10. Service: A Mule service is constituted of all the Mule entities involved in processing
particular requests in predefined manners, To come to life, a service is defined by a specific
configuration. This configuration determines the different elements, from the different
layers of responsibility, that will be mobilized to process the requests that it will be open to
receive. Depending on the type of input channel it uses, a service may or may not be
publicly accessible outside of the ESB.

11. Transport: The transport layer is in charge of receiving or sending messages. This is why it
is involved both for inbound and outbound communications.