Implementácia SOA pomocou ESB

© 2008 IBM Corporation13.3.2008

SOA and ESB

Implementácia SOA pomocou ESB

Michal Maliarik, IBM SLK

ESB WebSphere

Implementing an SOA using ESB WebSphere © 2008 IBM Corporation

Agenda

Komponentový prístup vs SOA Čo je to ESB SW Produkty pre implementáciu ESB

– Aké sú hlavne funkcie a výhody

Možnosti integrácie.

ESB WebSphere


Tvorba aplikácie

ESB WebSphere


Porovnanie funkčne a servisne orientovanej aplikácie

Funkčne orientovaná Postavené pre výkon Jeden dlhý vývojový cyklus Aplikačné silá Pevne viazané (tightly coupled) Štruktúrované aplikácie využívajúce

komponenty a objekty Známa implementácia

Procesne – servisne orientovaná Postavené pre zmeny Inkrementálny vývojový cyklus Orchestrované spolupracujúce riešenia Volne viazané (loosely coupled) Štruktúrované aplikácie využívajúce

služby Implementačná abstrakcia

ESB WebSphere


The Enterprise Service BusAn Enterprise Service Bus (ESB) is a flexible connectivity

infrastructure for integrating applications and services.

Shape = Transport protocol

Color = Data format

An ESB performs the following between requestor and service

CONVERTS between different transport protocols

MATCHES & ROUTES communications between services

TRANSFORMS between different data formats

IDENTIFIES & DISTRIBUTES business events

ESB WebSphere


Enterprise Service Bus

ESB WebSphere


ESB offerings from IBM WebSphereWebSphere delivers the most complete ESB solution

WebSphere ESBBuilt on WebSphere

Application Server for an integrated SOA platform

WebSphereMessage Broker

Built for universal connectivity and transformation in heterogeneous

IT environments

WebSphere DataPowerIntegration AppliancePurpose-built hardware ESB for simplified deployment and

hardened security

ESB WebSphere


ESB offerings from IBM WebSphere Each delivers a common set of ESB capabilities

Mediations to enable common patterns

Transformation of common data formats

Connectivity via common protocols

Leading web services standards

First class interoperability between ESB products

Mission-critical qualities of service

ESB WebSphere


WebSphere MQ

Reliable messaging for applications and Web services

Integrates virtually any commercial IT system

Proven qualities of service and availability for mission-critical applications

Supports industry standard interfaces

Connects Web Services with non-Web Services

Ubiquitous transport to extend and underpin your ESB

Reliable messaging backbone for SOA

HP-UX Windows zLinux Solaris AIX OS/400 NSS OVMSzOS Linux

Enterprise Service Bus

Enterprise Messaging Backbone:WebSphere MQ

ESB WebSphere


Highlights of WebSphere Message Broker 6.1 Consumability and Productivity

– Reduced time to get started

– Simplify debug, test, deploy tasks

Enhanced SOA Support– WS-Addressing and WS-Security built-in

– DataPower as WS-Security option

– WSRR Integration

Extended Connectivity– Gigabyte file support, including FTP

– SAP, Siebel,PeoplSoft nodes

– SMTP and JDBC Database nodes

Administration and Security– Enterprise security with LDAP and TFIM

– MB Explorer and real-time performance

– Numerous manageability improvements

Performance and Platform Coverage– More 64 bit platforms; JDBC XA; Java 5

– Ultra High Performance XML parser

– Compacted memory footprint

ESB WebSphere


WebSphere Message Broker Scenario – Heterogeneous service mediation

.NET Client

WebSphere (WAS/Portal)

SOAP/JMS

XML/MQ Client

XML/MQ

SOAP/HTTP

Text/MQ Client

Text/MQ

Some ClientXML/HTTP

SOAP/JMS

COBOL Copybook/MQ

SOAP/HTTP

XML/HTTP

.NET provider

3rd-party App Server provider

CICS

Legacy/custom provider

WebSphere Service Registry and Repository

SAPIDOC/ALE

WebSphere Message Broker

ESB WebSphere


First-class support for message and transport protocol bridging Protocol mediation with simple configuration

HTTP MQ WebSphere JMS FTP Tibco EMS

Request-response and sync-async matching Able to configure to preserve fully guaranteed, once-and-only-once delivery

WebSphere Data Power Integration Appliance XI50Scenario – Protocol bridging

ODBC

3rd-partyJMS

MQ

HTTP/ HTTPS

FTP/ FTP over SSLJMS

DB2Oracle

SybaseODBC

WAS JMS

WMQ

Data Power XI50

3rd Party App Server

ESB WebSphere


WebSphere ESBScenario – Composite application service hosting and mediation

WebSphereAdapter

`

XML/JMS

Service Mediations

Business Services

Web Applications

WebSphere ESBWebSphere ESB

Customer Service

Reps

ERP System

Customer MasterDB2

Credit Application

Warehouse Application

Application DataOracle DB

Suppliers

Customers

SOAP/HTTPS

JDBC

FTP

JDBC

ESB WebSphere



(6) Message is transformed and routed to the selected endpoint.

(6) Message is transformed and routed to the selected endpoint.

Message

(1) A Message is received

ESBMediation

(2) Invokes a selection mediation.

Publish Find Enrich GovernManage


(3) Retrieve requestor information

(4) Retrieves accurate and up-to date candidate providers information and metadata

Message

(5) Executes matching algorithm to identify the provider service for requestor service

Message

Service

ESB WebSphere


Scenario - Metadata-driven Runtime

Publish Find Enrich GovernManage


Message

1) During service invocation a message is received by the ESB

1) During service invocation a message is received by the ESB

Me

ssa

ge

2) The ESB routes the message to an intermediate logging mediation or agent

2) The ESB routes the message to an intermediate logging mediation or agent

Service Management Repositories

3) Retrieve monitoring policy for the message from the WSRR

3) Retrieve monitoring policy for the message from the WSRR

Mediation

4) Mediation records the operational data about the running service

4) Mediation records the operational data about the running service

Service

Message

Me

ssag

e

Performance and health alerts are generated based on operational data and recorded in the WSRR

Performance and health alerts are generated based on operational data and recorded in the WSRR

5) The ESB then continues with the invocation of the service.

Operatio

nal data

Performance data

Policies

ESB WebSphere


Analytici potvrdzujú budúcnosť viacnásobných ESB

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

ESB WebSphere


Multiple ESB Configurations Working Together

HQ Data Center

Branch Office Branch Office Branch Office

Specialized Appliance

Extranet

ESB WebSphere


ESB WebSphere


Enterprise Secure Zone

Demilitarized Zone

Example of Federated ESB (I)

DataPowerXI50

(DynamicallyRoute and logWeb services)

PartnerWebSphere

Web services

SOAP/HTTP

Web Application

WSRR

SOAP

DataPower

XS40

Web services for CICS

TFIM

WMB V6

(distributeevents)

PublishersSubscribers

SOAP/HTTP

MQ

MQMQ

ESB WebSphere


Headquarters

Retail Store

Example of Federated ESB (II)

Full-featured ESB with richer

mediation & connectivityPoint of

Sale Terminal

Mainframe DBMS

SOAP/HTTP TP

Monitor

POS/Store Applications

MQ

MQLightweightcommercial Java-based

ESBJ2EE Server

Enterprise Applications

MQ

JMSPoint of

Sale Terminal

Retail Store

Point of Sale

Terminal

POS/Store Applications

MQ

Lightweight commercial Java-based

ESB

Point of Sale

Terminal

MQ

SOAP/HTTP MQ

ESB WebSphere


ESB WebSphere


Federation – Models (work in progress)

In a federated bus environment, service interactions via N buses– Can be modeled as N recursive mediated interactions: Mediated interaction == consumer -> mediation -> provider– Can be modeled as N+1 recursive direct interactions: Direct interaction == consumer -> provider

The consumer - mediation direct interaction – Can run local to the consumer, or run remote from the consumer

The mediation in a mediated interaction can offer two forms of provider address resolution– Static, using 'fixed' addresses (development or deploy time) or dynamic, using a service registry

The observations allow us to describe a simplified model of bus federation– Federation interactions treated as recursive direct interactions– Mediation instances, or virtual services, may offer dynamic target resolution via a service registry

A federated SOA can contain both local and hub-based mediations in a more or less arbitrary logical topology with physical behavior controlled by the service registry

Interaction

ESB 2ServiceProvider

ESB 1Service

Consumer

ConsumerInstance

ProviderInstance

MediationInstance 1

Mediated interaction

MediationInstance 2

Mediated interaction

Federated interaction

Direct interaction

ESB WebSphere


WESB and WMB

ESB WebSphere


ESB deployments benefit from complementary technologies

Management technologies will become increasingly important to ESB deployments over the next few years, especially in large enterprise with

massive SOA deployments and federation across multiple domains

Complement Problem domain Relation to ESB

SOA Governance Service registry, metadata repository, policy management, and service lifecycle management

ESB can lookup service locations and policies from the registry.

Services management Service monitoring, alerting, and problem determination of composite applications

Can manage service interactions through the ESB

Identity and access management

Securing access to web services through identity and role management; security policy administration, decision, and enforcement; trust and identity mapping

ESB can serve as the decision point and enforcement point for secure access to services

WebSphere Service Registry and RepositoryTivoli Composite Application Manager for SOA (ITCAM for SOA)Tivoli Federated Identity Manager (TFIM)

ESB WebSphere


Tivoli Federated Identity Management Provides identity and access control services that enable architects and developers to migrate

identity processing out from applications into reusable services– Provides standards-based, end-to-end identity translation and access control from point of contact (e.g. XML firewall) –to– mainframe (e.g.

CICS)– Includes Tivoli Access Manager

TFIM makes an Enterprise Service Bus “identity aware”– WebSphere Enterprise Service Bus– WebSphere Message Broker– WebSphere DataPower Integration Appliance XI50– ….Other ESBs (via open standards)

Service A Service BIdentity =

rayIdentity =

[email protected]

Security Token Service(powered by Tivoli Federated Identity Manager)

Exchange this representation of this user from Service A for one that Service B will understand

New representation of user identity for Service B

Federated ESB

TivoliAccess Manager

Authorized ?

Yes / No

ESB WebSphere


ESB offerings from IBM WebSphere

WebSphere ESB: built on WebSphere Application Server for an integrated SOA platform

WebSphere Message Broker: built for universal connectivity and transformation in heterogeneous IT environments

WebSphere DataPower Integration Appliance XI50: purpose-built hardware ESB for simplified deployment and hardened security

ESB WebSphere


Reducing IT Complexity is Easier with an ESB

The role of the ESB is to decouple connectivity logic from application and process logic, thus making the benefits of SOA possible

IBM has the broadest ESB portfolio, plus products to extend your ESB

The IBM strategy is to provide a family of ESBs that are optimized to uniquely meet customer needs

ESB WebSphere


For more information…

WebSphere offerings for Application Integration http://www.ibm.com/software/info1/websphere/index.jsp?tab=solutions/appintegration

ESB without limits from WebSpherewww.ibm.com/software/integration/esb

For more IBM ESB success stories, visit:www.ibm.com/software/success

Documents

Implementácia SOA pomocou ESB