2. TOPICS
• Mule ESB Overview
• Mule ESB Features
• Mule ESB Architecture
• Mule ESB Some Important Components
• Mule ESB Pro’s and Con’s
3. MULE ESB OVERVIEW
• Mule ESB is a lightweight and highly scalable Java-based enterprise
service bus (ESB) and integration platform provided by Mule Soft.
• ESB stands for Enterprise Service Bus which is basically a middleware
tool for integrating various applications together over a bus-like
infrastructure.
• Fundamentally, it is an architecture designed to provide a uniform
means of moving work among integrated applications.
• In this way, with the help of ESB architecture we can connect different
applications through a communication bus and enable them to
communicate without depending on one another.
4. MULE ESB OVERVIEW
• Mule ESB allows the developer to connect applications easily and
quickly. Regardless of various technologies used by applications,
Mule ESB enables easy integration of applications, enabling them to
exchange data.
• Mule ESB has the following two editions −
• Community Edition
• Enterprise Edition
• An advantage of Mule ESB is that we can easily upgrade from Mule
ESB community to Mule ESB enterprise because both the editions are
built on a common code base.
5. MULE ESB FEATURES
• It has simple drag-and-drop graphical design.
• Mule ESB is capable of visual data mapping and transformation.
• User can get the facility of 100s of pre-built certified connectors.
• Centralized monitoring and administration.
• It provides robust enterprise security enforcement capabilities.
• It provides the facility of API management.
• There is secure Data Gateway for cloud/on-premise connectivity.
6. MULE ESB FEATURES
• It provides the service registry where all the services exposed
into the ESB are published and registered.
• Users can have control through a web-based management
console.
• Rapid debugging can be performed using service flow analyzer.
8. MULE ESB ARCHITECTURE
• ESB architecture enables us to integrate different applications
where each application can communicate through it. Following
are some guidelines on when to use ESB −
• Integrating two or more applications
• Integration of more applications in future
• Using multiple protocols
• Message routing
• Composition and consumption
10. MULE ESB SOME IMPORTANT
COMPONENTS
• Components are message processors which execute business
logic on messages.
• They enable you to perform specific actions without writing any
Mule-specific code.
• You can drop a component – a POJO, Spring bean, Java bean, or script
– into a flow to perform almost any customized task within your Mule
application.
• For example, you can use a component to verify that items on an
invoice are in stock in a warehouse, or to update a database with a
customer’s order history.
11. MULE ESB SOME IMPORTANT
COMPONENTS
• Scripting Components:
• Mule includes several scripting components that you can use in flows to
execute custom business logic.
• These components enable you to drop a chunk of custom-written logic
into your flow to act upon messages.
12. MULE ESB SOME IMPORTANT
COMPONENTS
• Web Service Components:
• Also included are two components to facilitate exposing, consuming,
and proxying Web services.
• The CXF component leverages the CXF framework Mule uses to support
SOAP Web services; the REST component works with Jersey to support
RESTful Web services; both are bound to HTTP.
13. MULE ESB SOME IMPORTANT
COMPONENTS
• HTTP Static Resource Handler:
• Further, Mule provides an HTTP static resource handler to facilitate
working with calls over HTTP.
• Use the HTTP Static Resource Handler to easily serve up static content
when called.
14. MULE ESB SOME IMPORTANT
COMPONENTS
• Other processors Grouped Under Components:
• Use a Logger component to log activities in the flow as they occur.
• Use an Expression component to evaluate a particular expression upon a
message in a flow.
• Use an Invoke component to invoke the method of an object specified
with a Mule expression.
• Use an Echo component to return the payload of a message as a call
response.
15. MULE ESB SOME IMPORTANT
COMPONENTS
• Other processors Grouped Under Components:
• Use a Flow Reference component to access another flow from within a
flow.
• Use a Batch Execute component to kick off processing of a batch job.
16. MULE ESB PRO’S AND CON’S
• Pros:
• Connector Development Kit
• Light-weight. Scaling down - quick point-to-point integrations. To the
Cloud - CloudHub.
• Anypoint Platform has a Wide range of enterprise connectors are key to
its integration success.
• Ease of use, easy to learn, quality and range of out of the box
connectors, overall completeness of the solution.
17. MULE ESB PRO’S AND CON’S
• Cons:
• Processes monitoring, task schedule
• -Fewer features in connectors but not source stopper
• Not as robust in handling large data volumes, Informatics is better in
that respect.
• Sometimes error messages are cryptic and need basic knowledge of Java
Spring to sort them out.
18. THANKS
If you feel that it is helpful and worthy to share with others then please like and share the same.