Enterprise service bus part 1

Enterprise Service Bus
Evgeny Epifantsev
december 2009
updated 2012
Exigen Services confidential Exigen Services confidential

Trainer contacts
• Evgeny Epifantsev
• Developer
• eepifantsev@exigenservices.com
Exigen Services confidential
2

Goals
• Provide an overview on:
• What is Enterprise Service Bus?
• How to implement it?
3

Agenda
• Introduction
• EAI evolution: P2P->MOM Hub->ESB
• ESB purpose and functions overview
• QoS and Policy Enforcement
• Components: Mediator VFTER (validate, filter, transform, enrich, route),
Choreographer
• Example of above topics
• Open source ESB
4

Part 1: Overview and ESB Concepts

Definition
6
ESB is idea of using common integration infrastructure across all
enterprise application and systems.
An Enterprise Service Bus (ESB) is a new architecture that exploits
Web services, messaging middleware, intelligent routing,
and transformation. ESBs act as a lightweight,
ubiquitous integration backbone through which software services
and application components flow."

What is ESB?
7
What is ESB?
Is a Pattern?
Is a Product?
Is an Architectural Component?
Is a Hardware Component?

Evolution
8
Point-to-Point
- Tight coupling
- Complexity ~N2
- No visibility
- Hard to secure
Service Bus (ESB)
+ Scalable
+ Service-oriented
+ Flexible
- Harder administration
+ Standards-based
+ Cost less than EAI
bus
Enterprise Application
Integration
Hub:
- Scalability
+ Easy administration
Bus:
- Standards and
proprietary
- High cost

ESB Architecture context
9
Java/EJB Http
Service location transparency Java/EJB Http
Sharing service across the enterprise
Separate of Business Services from Service implementation

ESB as a Pattern of SOA
10
WSDL
Business service
definition PlaceTrade
PlaceTrade
saveOrTradeOrder()
Java
implementation service
For saveOrTradeOrder()

ESB capabilities
11
Routing
Message
transformation
Message
enhancement
Security
Transaction
management Service
transformation
orchestration
Mapping
service
Message
processing
Protocol
Process
choreography

ESB basic functions
ROUTING messages between services
• Addressability, static/deterministic routing
• Content-based routing
• Policy-based routing
• Complex Rule-based routing
MESSAGING
• Message transformation
• Message processing
• Message enhancement
CONVERTATION
•Adapters and protocol conversion
•Transport protocols (synchronous and
asynchronous)

BUS: Protocol Conversion
Requests
Responses
13
ESB
Requests
Responses
Requests
Responses
Requests
Responses
Service
Requester
Service
Provider
Phone Phone w witihth w waapp - - W WXXMMLL/H/HTTTTPP
.N.NEETT - - S SOOAAPP/H/HTTTTPP
CC++++ - -X XMMLL/J/JMMSS
SSAAPP - - B BAAPPI I
WWeebbSSpphheerere 5 5.1.1 - -S SOOAAPP/J/JMMSS
SSAAPP - -B BAAPPI I
EExxteternrnaal lp paartrntneer r - -S SOOAAPP/H/HTTTTPPSS
UUsseer ra apppplilcicaatitoionn - -R RMMI I
DDaatatabbaassee – – S SQQLL
AApppplilcicaatitoionn - -X XMMLL/J/JMMSS

Service mapping
14
The ability to translate a business service into the corresponding
service implementation and provide binding and location information
 Could be implemented through XML, a database, or embedded
within the Mediator ESB component
 Usually contains the following core information
• Implementation service name
• Service protocol and binding information
• Protocol-specific info (i.e. timeouts)
• Service-specific routing information

Process choreography
Each of business node can be an
independent business service
15
The ability to manage complex business process that require the
coordination of multiple business services to fulfill a single business
service request
 Usually BPEL based
PlaceFixedIncomeTrade
CreateOrder SelectBid PlaceTrade ExecuteTrade

Service orchestration
16
The ability to manage the coordination of multiple implementation
services
 Can be BPEL based but is usually implemented through inter-service
communication or aggregate services
 Difference between Service orchestration and Process
Choreography is based on type of service • Process choreography - Business b seeinrvgic ceosordinated
• Service orchestration - implementation service

Transaction management
17
The ability to provide a single unit of work for a business service
request by providing a framework for the coordination of multiple
disparate services
 ESB should provide a compensatory transactional framework for a
service request
• WS - Coordination
• WS - AT
• WS –Business Activity

Security
18
The ability to protect enterprise services from authorized access
 Services visible to the entire enterprise through ESB
 The 4 “A’s” of Security
•Authentication
• Authorization
• Auditing
• Administration
 ESB should provide authentication, authorization and auditing
 ESB should access a security manager for authentication and
authorization rather than have the direct responsibility

Quality of Service and Policy enforcement
requestor provider
19
• Security WS-Security, SAML
• Reliable delivery for each connection
• Transaction management
WS-AT, WS-Coordination,
WS-Business Activity
• Traffic management
• Policy (WS-Policy) RR11
PP11
PP22
Tx_not
supported
Tx_not
supported
TxT_xr_erqeuqiureirded
CComompepnesnastaiotinon
TxT_xr_erqeuqiureirded
CComompepnesnastaiotinon
1
2
3
response
No
answer

CEI

Common Event Infrastructure
Common Event Infrastructure (CEI) is IBM's implementation of API, and
infrastructure for the creation, transmission, persistence and distribution of a wide
range of business, system and network Common Base Event formatted events.
21
Based on Common Base Event
(IBM implementation of Web Services Distributed Management )
CEI Event Submission Interfaces (Event Source)
CEI Event Subscription Interfaces (Event Server)
CEI Event Query Interfaces (Event Server)

CEI Event types

Common Event Browser

ESB Components

ESB components
25
 ESB can broken down into the following components
• Mediator
• Service registry
• Choreographer
• Rules Engine
MMeeddiaiatotorr
Service
registry
Service
registry
CChhoorreeooggrraapphheerr RRuuleless e ennggininee

Mediator (Routing, Message transformation)
Service
Requester
Transform
XSLT
26
Mediator
Requests
Responses
Requests
Responses
Requests
Responses
Requests
Responses
Service
Provider Validation
XSD
Validation
XSD
Transform
XSLT
Enrich
XPath
Enrich
XPath
Route
UDDI
Route OOppeeraratete
UDDI
VETRO
export
import

Process choreographer
partnerLink
27
BPEL – Business Process Execution language
partnerLink
purchasing
partnerLink
invoicing
ppuurrcchhaasseeOOrrddeerrPPTT purchasing partnerLink
invoicing
CCoommppuutetePPrriciceePPTT
ininvvooiciceeCCaalllblbaacckkPPTT
<wsdl:portType
name="purchaseOrderPT">
<wsdl:operation …
</wsdl:operation>
</wsdl:portType>
<plnk:partnerLinkType
name="purchasingLT">
</plnk:partnerLinkType>
<plnk:partnerLinkType name="invoicingLT">
<plnk:role portType="pos:computePricePT" />
<plnk:role portType="pos:invoiceCallbackPT“ />
</plnk:partnerLinkType>

BPEL Process
<receive portType="lns:purchaseOrderPT" … />
<flow>
<invoke portType="lns:computePricePT“ … />
<receive portType="lns:invoiceCallbackPT" …/>
</flow>
<reply portType="lns:purchaseOrderPT” … />
28
<sequence>
<sequence>
<receive portType="lns:purchaseOrderPT" … />
<flow>
<invoke portType="lns:computePricePT“ … />
<receive portType="lns:invoiceCallbackPT" …/>
</flow>
<reply portType="lns:purchaseOrderPT” … />
<sequence>
<sequence>

Implementation Mediation Module
Mediation module
Requests
Responses
Mediation flow
Imports component Exports
29
Mediation flow
Requests
Responses
Requests
Responses
Requests
Responses
Service
Requester
Service
Provider
Exports Imports

Implementation mediation Flow
30
InInteterrfafacceess MMeeddiaiatitoionn p prrimimitiitviveess

Implementation in Business Works
31

Implementation steps
WebSphere ESB Messaging Resources
Import WSDL(SCA, Web
Service, HTML, JMS)
Connect WSDL ports with
mediator (import)
Generate exports with
binging (SCA, Web
Service, HTML, JMS)
32
Import WSDL(SCA, Web
Service, HTML, JMS)
CCrreeaatete m meeddiaiatotorr
Connect WSDL ports with
mediator (import)
Generate exports with
binging (SCA, Web
Service, HTML, JMS)
CCrreeaatete b buuss i ninsstatannccee
SSeetutupp S SDDOO r reeppoossitiotorryy
SSeetutupp r reessoouurrccee a addaappteterrss
Create client listeners for
Create client listeners for
every protocols
every protocols
CCrreeaatete i ninteterrcceepptotorrss
CCrreeaatete m meeddiaiatotorr ( (EEJJBB))

ESB platforms
WSO2 ESB Apache Synapse, WS Apache Axis2
Sun GlassFish ESB NetBeans IDE, BPEL orchestration, WS JAX-WS,
Mule ESB EE custom implementation model, WS CXF, No BAM,
IONA Fuse ESB Apache ServiceMix, JBI, OSGI, WS CXF, no BAM,
WebSphere ESB WebSphere MQ, JMS, BPEL, SCA
33
Business Rules, Transaction, BAM
no Business rules
Business rules
WS JAX-WS, BAM, Business Rules
Matrix BusinessWorks no transaction, no dusiness rules, BAM
Oracle ESB JMS, BPEL

Open source way
Business
34
ESB
Business
Rules
DDrroooolsls Rules
RRoouutitningg
eeipip
ccaammeell
jajavvaa
jBjBPPMM CChhoorreeooggrraapphhyy
Transform
ation
Transform
ation
xxssltlt
xxppaathth
ssimimpplele
IBIBMM EEvveenntsts
OOraracclele
JJMMSS
AAMMQQ

Thank You!
Questions?
35

Enterprise service bus part 1

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie Enterprise service bus part 1

Ähnlich wie Enterprise service bus part 1 (20)

Mehr von Return on Intelligence

Mehr von Return on Intelligence (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Enterprise service bus part 1

Hinweis der Redaktion