Mulesoft ppt

Preview:

Citation preview

MULE ESB

Presented by

B. Abhimnyu

AGENDA

1.Enterprise service Bus

2.Mule ESB

3.Components

4.Scenarios

Enterprise Service Bus(ESB)

Enterprise Service Bus (ESB) is an application that gives

access to other applications and services. Its main task is to

be the messaging and integration backbone of an enterprise.

An ESB is a distributed middleware system to integrate

different applications. All these applications communicate

through the ESB. It consists of a set of service containers

that integrate various types of applications. The containers

are interconnected with a reliable messaging bus.

MULE ESB

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

efficiently exchange data.

WHY MULE ESB? 1.The Integration is possible with cloud

based applications also like

Facebook

Twitter

2.Reduces complexity compared to

WESB

3.Advanced Functionalities and

Features

The three main components of Mule Studio are as follows

Package Explorer:Package Explorer contains the entire

Structure of the project

Palette:Palette is a source for accessing

endpoints,components,transformers,cloud connectors

Canvas:It is a graphical editor to create your flows.

PACKAGE EXPLORER

PALETTE

CANVAS

About Package Explorer

Src/main/app: stores your flow

Src/main/java:stores custom java class

Src/main/resources: creates graphical flow

and we can also add required resources

Src/test/java:contains the test related java files

Src/test/resources:contains the flow related test

files

Mapping:stores the mapping related files

Palette Components

Connectors send and receive data, and are responsible for

connecting to external resources and delivering messages.

connectors can be Inbound or Outbound. An Inbound

Endpoint receives messages via its associated transport. Each

transport implements its own Inbound Endpoint element. An

Outbound Endpoint sends messages via its associated transport.

Each transport implements its own Outbound Endpoint element

Transformers

Transformers convert message payloads to formats expected by

their destinations.

It performs different conversions depending on requirements.

Filters

Filters: Filters decide which Mule messages should be

processed. Filters specify the conditions that must be met for a

message to be routed to a service or continue progressing

through a flow. There are several standard filters that come with

Mule ESB, which you can use, or you can create your own filters

Scenario-1

Pick a Order XML file from ftp server and

place the file into JMS Queue in string

format and take the file from the same

queue and place into

local folder(JSON format).

Scenario-2

Send a request (Order Request) to web

service through http endpoint and

place the response(Order Info) in local

folder in the form of csv file and do

transformation using data mapper.

Scenario-3

Using Quartz scheduler invoke mule flow

every 30 sec (Invoke web service and

place the response in local file).

Scenario-4

Can you send an email if got an

exception in mule flow.

THANK YOU

ANY QUERIES?