ENTERPRISE SERVICE BUS

Goals
 Introduction to Enterprise Service Bus (ESB)
 What is an ESB ?  Evolution of ESB Features Of ESB  Role of ESB in Services Oriented Architecture

(SOA)  Key Advantages & Disadvantages Of ESB

Step to Understanding ESB Concept

    

Review Key SOA terms and Concept Enterprise Service Bus Description Definition And Scope of ESB How ESB Software Works Key Characteristic and Benefits
SOA Without ESB  SOA With ESB  ESB Value Proposition  Role of ESB


WHAT IS ESB ?
y Enterprise Service Bus is the Methodology to provide the Integration to the different Services. Here Services means any component which is providing some functionality to the Clients. ESB provides the Base for all those Services to interact with each other. y An enterprise service bus (ESB) is a pattern of middleware that unifies and connects services, applications and resources within a business. Put another way, it is the framework within which the capabilities of a business' applications are made available for reuse by other applications throughout the organization and beyond.

Definitions And Scope Of ESB

y In computing, an enterprise service bus (ESB) consists of a software

architecture construct which provides fundamental services for complex architectures via an event-driven and standards -based messaging-engine (the bus). Developers typically implement an ESB using technologies found in a category of middleware infrastructure products, usually based on recognized standards.

y An ESB generally provides an abstraction layer on top of an

implementation of an enterprise messaging system , which allows integration architects to exploit the value of messaging without writing code. Unlike the more classical enterprise application integration (EAI) approach of a monolithic stack in a hub and spoke architecture, an enterprise service bus builds on base functions broken up into their constituent parts, with distributed deployment where needed, working in harmony as necessary.

Service Oriented Architecture (SOA)

Definition Of Some Key Terms
.A
Service?
.Service Orientation?
A Way of Integrating Your Business As Linked Services And The Outcomes That They Bring. A Repeatable Customer Task For Exp Check Customer Credit ; Open a New Account;

.Service Oriented Architecture (SOA) ?

An IT Architectural Style That Supports Service Orientation.

.A Composition Application ?
A Set Of Related And Integrated Service That Support A Business Process Built On An SOA.

Basic SOA

What is an Enterprise Service Bus?

An Enterprise Service Bus(ESB) is an Flexible Connectivity Infrastructure for Integrating Application And Services.
An ESB Powers Your SOA By Reducing the Number, Size And Complexity of Interface.
An ESB Performs Following Between Requestor And Service

 Routing
Service.

Messages Between

Converting Transport
Protocols Between Request And Service

 Transforming Message
Formats Between Requestor And Service

 Handling Business Events

From Disparate Source.

Leverage the SOA Reference Architecture

Business Services
Supports enterprise business process and goals through businesses functional service

Interaction Services Development Services

Integrated environment for design and creation of solution assets Enables collaboration between people, processes & information

Process Services
Orchestrate and automate business processes

Information
Manages diverse data and content in a unified manner

Management Services
Manage and secure services, applications & resources

Enterprise Service Bus

Partner Services
Connect with trading partners

Business App Services

Build on a robust, scaleable, and secure services environment

Access Services
Facilitate interactions with existing information and application assets

Infrastructure Services
Optimizes throughput, availability and utilization

Apps & Info Assets

Supporting Products
WebSphere Data Power

Business Services
Supports enterprise business process and goals through businesses functional service

WebSphere ESB

WebSphere Message Broker

Interaction Services Development Services

Integrated environment for design and creation of solution assets Enables collaboration between people, processes & information

Process Services
Orchestrate and automate business processes

Information Services
WebSphere
Manages diverse data and content in a unified manner

Management Extender Services

Transformation

Enterprise Service Bus

Apps & Info Assets

Manage and Registry & secure Repository services, applications & resources

WebSphere Service

Partner Services
Connect with trading partners

Business App Services

Build on a robust, scaleable, and secure services environment

Access Services
Facilitate interactions with existing information and application assets

Infrastructure Services
Optimizes throughput, availability and utilization

EVOLUTION OF ESB
y Enterprise Service Bus concept started off life in the mid 90 s it was as an extension of a messaging pipe - that is, message based communications. y ESB concepts emerged majorly in 1996-97 y Standards activity in the integration marketplace increased and took root, and users wanted to find ways to lower the entry price for integration - having to buy a hub was very expensive, particularly when connections were few in the early stages of integration development. There were also fairly groundless concerns about availability with the hub and spoke model due to the perceived single point of failure. As a result, the ESB emerged

FEATURES OF ESB
y Invocation - support for synchronous and asynchronous transport protocols, y y y y y y y

service mapping (locating and binding). Routing - addressability, static/deterministic routing, content-based routing, rules-based routing, policy-based routing. Mediation - adapters, protocol transformation, service mapping. Messaging - message-processing, message transformation and message enhancement. Process choreography - implementation of complex business processes Service orchestration - coordination of multiple implementation services exposed as a single, aggregate service. Complex event processing - event-interpretation, correlation, patternmatching. Management - monitoring, audit, logging, metering, admin console.

In addition, an ESB is expected to exhibit the following characteristics:

y general use of XML as the standard communication language y support for web-services standards y validation against schemas for sending and receiving messages y the ability to apply business rules uniformly y enriching messages from other sources y the splitting and combining of multiple messages and the handling of exceptions y the provision of a unified abstraction across multiple layers y queuing, holding messages if applications temporarily become unavailable

ROLE OF ESB IN SOA

y SOA is a service oriented Architecture, means we are developing

the business logic as a service to finish small task. y SOA is a way of architecting your IT programs around a serviceoriented concept y The absolute key to this is that an SOA service relates to a BUSINESS piece of functionality as opposed to some programming activity y Therefore, it is clear to see that SOA requires some sort of communications capability, and while this does not have to be an ESB, the ESB fits the role very well particularly with its affinity to standards such as web services.

ROLE OF ESB IN SOA

y An ESB does not itself implement a service-oriented

architecture (SOA) but provides the features with which one may implement such. y ESBs attempt to isolate the coupling between the service called and the transport medium. Most ESB providers incorporate SOA principles and allow for independent message formats. y And ESB is not essential for a SOA, but it is very helpful

SOA Without ESB

Decouples Interface From Application

Rich Business Abstractive Describe the Application Interface

 Decouples the

 The Number And

 Business

Interface From The Business Application

Complexity Of The Interface Is Reduced

Application And Other Interface Become Reusable.

But Interfaces Tightly Coupled With Point To Point Connection

SOA With ESB

Decouple Interface From Point To Point Connections

 Decouples The Point

 Allows For Dynamic

 Enable More Flexible

 Enables You To Find

To Point Connection From The Interface.

Selection Substitution And Matching

Coupling And Decoupling Of The Applications.

Both The Application And The Interface For Reuse.

Result Great Business Responsiveness

BENEFITS OF ESB
y Today's fast-paced business world demands the ability to change and adapt rapidly. An enterprise service bus can enable you to integrate your business applications and processes quickly and easily, allowing you to respond to business challenges and opportunities as soon as they arise. y The ESB pattern can improve operational performance and reduce costs while simplifying the task of connecting dissimilar applications across a network of different operating systems.

BENEFITS OF ESB
y An enterprise service bus (ESB) enables a business to make use of a comprehensive, flexible and consistent approach to integration while also reducing the complexity of the applications being integrated. Due to the complex and varying nature of business needs, ESB is an evolutional progression that unifies message oriented, event driven and service oriented approaches for integrating applications and service. Implementing an ESB facilitates greater reuse of IT assets by separating application logics and integration tasks, so you can reduce the number, size, and complexity of integration interfaces. In doing so, you can add or change services with minimal interruption to existing IT environment; reduce cost and risk involved as business changes and new opportunities arise.

BENEFITS OF ESB
y The benefit of an ESB is that it eases the process of creating an SOA. y Within the boundaries of an ESB, support for multiple protocols and data transformation enables heterogeneous services to behave as if they were homogeneous y The support for reliable and secure messaging and queuing is also available through straight-forward configuration rather than coding y Add in the availability of logging and access control for governance and ESB can be a very useful tool indeed

BENEFITS OF ESB
y Faster and cheaper accommodation of existing systems. y Increased flexibility; easier to change as requirements change. y Standards-based y Scales from point-solutions to enterprise-wide deployment (distributed bus). y Predefined ready-for-use service types. y More configuration rather than integration coding. y No central rules-engine, no central broker. y Incremental patching with zero down-time; enterprise becomes "refactorable

All customer services communicate in the same way with the ESB: the ESB translates a message to the correct message type and sends the message to the correct producer service.

Potential IT Benefits:
y Create additional value from existing applications and information y Quickly add best-of-breed applications y Reduce the total cost of ownership through a standards based service-oriented architecture (SOA) y Quickly respond to changing value-chain requirements y Leverage existing assets in new ways y Simplify complex programming tasks y Reduce software development and maintenance cost y Improve system security, scalability, availability and robustness

Potential Business Benefits :

y Improve customer service and business agility y Lower operating costs y Access real time business information accurately and rapidly y Accelerate mergers and acquisitions y Lower inventory costs y Improve return on assets y Eliminate manual process errors y Improve and automate value-chain management

The key advantages of using an ESB are less about features and functions and more about how you use it.
y Standardization y Loose Coupling y Scalability and Reliability y Routing and mediation y Complex message exchange patterns

Key Benefits & Disadvantages Of ESB

Advantages OF ESB
   

Disadvantages OF ESB


Faster and cheaper accommodation of existing systems. Increased flexibility; easier to change as requirements change. Standards-based Scales from point-solutions to enterprise-wide deployment (distributed bus). More configuration rather than integration coding. Incremental Patching with zero downtime; enterprise becomes refactorable

Usually requires an Enterprise Message Model, resulting in additional management overhead. Requires ongoing management of message versions to ensure the intended benefit of loose coupling. Incorrect, insufficient, or incomplete management of message versions can result in tight coupling instead of the intended loose coupling. It normally requires more hardware than simple point-to-point messaging. Though ESB systems can require a significant effort to implement, they produce no commercial value without the subsequent development of SOA services for the ESB Middleware analysis skills needed to configure, manage, and operate an ESB.

 

 

ESB Value Proposition

Focus On Your Core Business Not Your IT

Industry analysts confirm multiple ESB future

ESB Adoption Trends - Gartner

80% of large companies will have ESBs or similar SOA infrastructure products from three or more vendors in 2009. (0.7 probability) half of all large companies will apply a systematic, federated approach to managing their disparate SOA domains and ESBs in 2009. (0.7 probability)
Roy Schulte, Gartner, Succeeding With Multiple SOA Service Domains and Disparate ESBs, May 2007

ESB Adoption Trends - Forrester

Some of Forrester's most advanced clients got on the ESB bandwagon years ago and today find that they have an embarrassment of riches, with multiple ESBs. This outcome is almost inevitable for larger enterprises; no single ESB today can satisfy all requirements equally well across the whole of a large enterprise.
Larry Fulton, Forrester, Shaping Your Middleware Strategy to Benefit from ESBs, May 2007

SOURCES
y EBIZQ.NET y WIKIPEDIA y IBM.COM y SOABLOKE.COM y JAVABEAT.COM

*******Thank You*******