The document discusses enterprise service bus (ESB), which is a software architecture that provides fundamental services for more complex middleware architectures. An ESB simplifies integration and flexible reuse of business components using a service-oriented architecture. The key capabilities of an ESB include routing, message transformation, enhancement, protocol transformation, service mapping, message processing, process choreography, service orchestration, and transaction management. An ESB contains components like mediators, a service registry, a choreographer, and a rule engine that work together to provide these capabilities. The Java Business Integration specification aims to standardize integration middleware components to perform the functions of an ESB.

1. Enterprise Service Bus
BY
K.JAYA PRAKASH
M.G.I.T

2. Agenda
• Introduction
• The ESB Architecture
• The capabilities of an ESB
• ESB components
• JBI specification and impact on the ESB

3. Introduction
• What is ESB?
 It is pattern
It is architecture component
It is product

4. ESB definition
• An enterprise service bus (ESB) is a software
architecture for middleware that provides
fundamental services for more complex
architectures.
• Enterprise Service Bus (ESB) which simplifies
that integration and flexible reuse of business
components using standard service-oriented
architecture (SOA) providing a responsive,
low-cost, high-impact framework for the
technology.

5. Architecture of ESB
Normal architecture communications
Client
Services provider Services provider
CICS /main frames
Java/EJB

6. ESB architecture communications
Client
Enterprise service bus
Service provider Service provider
Ex:
Ex:
CICS /main frames
Java /EJB

7. Complete Architecture of ESB
Services
Services providers Services providers providers
Enterprise services Bus (ESB)
Services providers Services providers

8. The capabilities of ESB
ge Message
Messa tion
tran sforma enhancement Protocol
transmission
g
Routin
Service
Enterprise services mapping
ity bus (ESB)
Secur
Message
g
processin
n
Transactio
ent
managem s
Service Proces aphy
gr
orchestration choreo

9. Routing
• The ability to channel request to a particular
services provider based on deterministic or
variable routing criteria
– Type of routing
static or deterministic
content based routing
policy based routing

10. Message transformation
• The ability to convert the structure and format
of the incoming business services request to
the structure and format expected by service
provider
some examples
xml------COBOL
object----xml
xml-------object
CICS -----xml

11. Message enhancement
• The ability to add or modify the information
contained in the message as required by the
services provider
– Type of message enhancement
• Data format conversion
• Supplement data included in original data
• Rule based enhancement

12. Protocol transformation
• The ability to accept one type of protocol
from the consumer as input(i.e. SOAP/JMS)
and communication to services provider
through different protocols.
• Has both physical connection attributes as
well as logical connectivity.
• Example
• SOAP/JMS------IIOP
• XML/HTTP-----CICS/MQ
• SOAP/MQ-----RMI/IIOP

13. Service mapping
• The ability to translate a business service into
corresponding implement services location
information
1. Usually contain the following are information
1. Implementation services name
2. Services protocol and binding of information
3. Protocol specific into ( time out ,failure Information )
4. Services specific routing information

14. Message processing
• The ability to manage state and performance
request management by accepting input
request and ensuring delivery back to client
via message synchronization.
Client
Output request Error
notification
Input ESB
queues to
ESB

15. Process choreography
• The ability to manage complex business
process that requires the co-ordination of
multiple business services to fulfill a single
business services request
• Usually BPEL based

16. Services orchestration
• The ability to manage co-ordinate of multiple
implementation services.
• Usually BPEL based
Differences b/w services choreography and services
orchestration
 process choreography : business services
 services orchestration : implement services

17. Transaction management
• The ability to provide a single unit of work for
business services request to provide a frame
work for the co-ordination of multiple
resources across multiple disparate services.

18. Security
• The ability to protect enterprise services from
unauthorized access.
in SOA there are no more silos: services because
visible to the entries enterprise through ESB.
Four types security
 Authentication
 Authorization
 Auditing
 Administration

19. ESB components
• There is no single product that can efficient do
all of the capabilities required ESB .
• An ESB can be broken down into following
components
1. mediators
2. services registry
3. choreographer
4. rule engine

20. ESB basic components
mediators Services registry
Choreography Rule engine

21. Client application
ESB
mediator
choreography
Service
Registry
Service provider

22. • Mediators responsibility • Choreography
responsibility
• Routing
• Communication • Message processing
• Message transformation • process chorography
• Protocol • transaction message
• Message processing • Security
• security

23. • Services Registry • Rule engine
responsibility responsibility
• Service mapping • Routing
• Message transaction
• Message enhancement

24. JBI java business integration
• The goal JBI to create a standard based
architecture for integration middle ware
components to perform ESB
• The JBI specifics is not concerned about how
external consumer and services provide
interact ,but rather how internal consumer
and provider interact
• Java Business Integration JSR (JBI) extends
J2EE and J2SE with business integration.

25. • The JBI environment
JBI defines a container that can host
components. Two kinds of components can be
plugged into a JBI environment
• Service engines provide logic in the environment,
such as XSL (Extensible Style sheet Language)
transformation or BPEL (Business Process Execution
Language) orchestration.
• Binding components are sort of "connectors" to
external services or applications. They allow
communication with various protocols, such as
SOAP, Java Message Service.

26. • JBI Architecture

27. Thank you