API:-Application programing integrator

ESB:-enterprise service bus

EDI:-electronic data interchange

JSON:-java scripted object notation

XML:-extensible mark-up language

SOAP:- simple object access protocol

REST:-representative state transfer

WSDL:-web services description language

URI:-universal resource language

SDLC:-software developer life cycle

IDE:-integrated development environment

RAML:-restful API modelling language

NFD:-non-functional requirement

FRD:-function required document

RCA: rout cause analysis

POC:-proof of concept

MOM:-message oriented middleware

SLA:-service level agreement

TPS:-transfer per second

SAAS:-software as a service

PAAS:-platform as a service

IAAS:-integration as a service

SEDA:-stage event drive architecture

UI:-user interface

CRM:-customer relationship management

SOA:-service oriented architecture

JVM:-java virtual machine

TCP:-transfer connect protocol

HTTP:-hypertext transfer protocol

HTTPS:-hypertext transfer protocol security

FTP:-file transfer protocol

Encryption:-digital password

WHAT IS ESB?

Mule ESB is a integrated technology which have different type of application, mule is an open source
integrated frame work consist of different connectors which can easily integrated to our application

Mule is a light weight integrated framework mule esb includes powerful components included

*rest /soap /jms / sales force / cloudhub / raml / http /java / mango DB

Mule soft Any-point studio is a user friendly IDE which can easily drag connectors from the mule
palette

Mule ESB has 2editions

*community edition:-it’s a free edition

*enterprise edition:-it’s a commercial edition

Types of ESB

*Apache camel /*dellbomi / *j boss fuse / *open esb / *spring integration / *oracle esb /*IBM
message broker
MULE GOALS AND FUTUERS:-

Message transformation

Message enhancement

Message processing

Security

Service mapping

Service orchestration

Protocol transformation

Routing

Mule fallows SEDA structure

Seda is a event listenerclick--submit

Seda fallow the thread pool

*receiving thread pool

*process thread pool

*dispatcher thread pool

Mule ESB archstructure

APPICATION LAYER

INTIGRATION LAYER

TRANSPORT LAYER

MULE MESSAGE STRUCTURE

INBOND PROPERTIES OUT BOND PROPERTIES

Payload variables

Exceptional payload attachments

Inbound properties:-inbound properties are immutable we can’t change the business data

Outbound properties:-outbound properties are mutable we can the change the business data
Variables:- variable is used to store the values

*record variable

*session variable

*flow variable

Flow variable:-flow variable is used to storage the value .to store and access the data

Variable connector persist only for the current flow cannot cross the transport barrier

Session variable:-if want to store any value. And need to access those values with in the other flow .
We use session variable

Record variable:-used for Bach processing

Mule expression language (MEL)

to access are evaluate the date in the payload properties, and variables in mule message

=> mule Context related attributes:

Syntax: #[context Object.context Filed]

Ex: #[message.inboundproperties.’http.query.param’.name]
#[server.dateTime]
#[app.registry.beanName] – used to retrieve bean property name

=> Actual business payload attributes – JSON, XML & Java

XML:
Syntax: #[xpath3 //accountSummary/accounts/account/bankName]

JSON:
Syntax: #[json: /accountSummary/accounts/account/bankName]

Java:
Synatax:
#[payload.accountSummary.accounts.account.bankName]

What is difference between the soap and rest?

Soap has a official stranded because it’s Rest has no stranded protocal at all
a protocol because it a fallows SEDA orchestration

Soap support only http and xml Rest use multiple languages like
http,json,xml,csv..ets

Soap use xml to create payload. Data in Rest API deploy multiple stranded . so it
large size takes low data size

Soap use wsdl base service Rest use ul method

What is web service:-

Service available in the web

It enables the communication between applications over the web

Provide a stranded protocol /format for communication

Platform integration communication

Web service are client and server application that communication over the world wide web
(www),web service provide a stranded mean of integration between software application running on
a various of platform and framework

MOM:-

Message oriented middleware

Mom follows the pub & sub method, it process the request in the form of message Q’s

They are 2 methods

Queue:-

Topic:-

*Active mQ
 *rabit mQ

*ibm mQ

*Anypoint mQ

*kafka MQ

Queue:-In requester published in queue can be submitted by single consumer & subscriber

When message published to queue it not necessary for consumer & subscriber in online

TOPIC:-requester published in topic .can be subscriber by more consumers& subscribers

When message published to queue is necessary for consumer & subscriber in online

HTTP

HTTP:-http is a one of the network barrier

In http listener we expose our services to the external system using /host:port:url;

In http requester we consume our services from external source

HTTPS:-It is a service layer .it communicate via TLS

Tls creations are 2 types

True store:-contain certificate

Key store:-contain public & private keys

HTTP METHODS:-GET, PUT, POST, PATCH, DELETE

200:-successful

201:-create

400:-validation error

401:-unauthorised

404:-not found

405:-method not allowed

500:-internet service error

503:-service unavailable

504:-time out error

443:-https

TRANSFORMATION COMPONENT:-
Transformer is a nothing but it connect one type of object to any type of object

Types can be:-XML / JSON/JAVA/ CSV…etc

Inbuilt transformers

Customer transformers

Data wave transformers