© 2007 IBM Corporation IBM Software Group July 2007 Why do I need an Enterprise Service Bus and...

© 2007 IBM Corporation

IBM Software Group

July 2007

Why do I need an Enterprise Service Bus and which one?

Dale LaneHursley Park, IBM UK

2

IBM Software Group

Why do I need an Enterprise Service Bus and which one? © 2007 IBM Corporation

What is an Enterprise Service Bus?

Why can an ESB help your connectivity needs?

What are IBM's ESB solutions?

How can you further extend the ESB's capabilities?

How can you choose between IBM's ESB offerings?

Case Studies

Agenda

3

IBM Software Group







Case Studies

Agenda

4

IBM Software Group


ESB inter-connects requestor and provider

ESB provides Service Virtualization

Intelligent processing of service request / responses, events, messages

Service Requestor

Service ProviderESB


Core Principles of the ESB Architectural Pattern

6

IBM Software Group



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

A flexible connectivity infrastructure for integrating applications and services.

7

IBM Software Group


What can an Enterprise Service Bus do?

An ESB enables integration between loosely-coupled applications and services within and across:

–Services oriented architectures – where distributed applications

are composed of granular re-usable services with well-defined,

published and standards-compliant interfaces

–Message driven architectures - where applications send

messages through the ESB to receiving apps

–Event driven architectures - where applications generate and

consume messages anonymously

8

IBM Software Group


What can an Enterprise Service Bus do?

An ESB enables simple application integration across

–different platforms

–programming models

–messaging standards

9

IBM Software Group







Case Studies

Agenda

10

IBM Software Group


Reduce the number, size and complexity of interfaces

Reduces cost and risk involved as business changes and new opportunities arise

Promotes reuse – Data and business logic more usable and applications easier to service-enable

Dynamic real-time, event-driven SOA – replacing unresponsive, batch-updating IT systems


11

IBM Software Group


Leverage the benefits:

–Reliable and secure data movement

–anywhere in the enterprise

–Application Programmers focused on logic

–simplified programming tasks

–Dedicated environment

–Common tooling, management and operational support


12

IBM Software Group


Loose coupling requires greater investment

–More design work–More implementation work

Benefits of an ESB: Loose coupling

13

IBM Software Group


Tighter coupling tends to cost more over time

–Synchronizing multiple organisations on change

–Adapting, redeploying updated components without affecting others

–Making changes is hard and expensive, or impossible

–Different parts of the solution are difficult to manage separately

–Hard to move, hard to scale, hard to distribute, hard to replace

–More coupling implies more expensive testing


14

IBM Software Group


ProviderConsumer

LocationLanguage

DataFormat

DeliveryAssurance Semantic

Interface

PlatformProtocol

Time

Security

ServiceVersion

ServiceProviderIdentity

InteractionState

Business Data Model


15

IBM Software Group



Business Innovation & Optimization Services

Provide for better decision-making with real-time business information

Dev

elo

pm

ent

Ser

vice

s

Integrated environment for design

and creation of solution

assets

Interaction Services

Enables collaboration between people,

processes & information

Process Services

Orchestrate and automate business

processes

Information Services

Manages diverse data and content in a

unified manner

ESB Enable inter-connectivity between services

Partner Services

Connect with trading partners

Business App Services

Build on a robust, scaleable, and secure services environment

Ap

ps

&

Info

As

setsAccess Services

Facilitate interactions with existing information and application assets

IT S

ervi

ceM

anag

emen

t

Manage and secure services,

applications &

resources

Infrastructure ServicesOptimizes throughput,

availability and performance

SOA Reference Architecture – Model of the Logical Architecture

16

IBM Software Group


What is an Enterprise Service Bus?An ESB-centric view of the logical model

ESB

Man

ag

emen

t S

ervi

ces

Se

cu

rity

Ma

na

ge

me

nt

Application Services

InformationProcessInteraction

AccessBusiness AppPartner

Registry

Dev

elo

pm

ent

Ser

vice

s

Outside of the ESB:

Business logic (“Application Services”)

Loosely coupled to the ESB:

Security and Management

Tightly coupled to the ESB:

Service Registry

Tooling required for ESB

Development Administration Configuration (via Service Registry)

17

IBM Software Group


What is an Enterprise Service Bus?The ESB decouples connectivity logic from application and

process logic – making SOA possible

Flexible“Uncluttered”Business Process Logic

“Uncluttered”Well DefinedSelf-ContainedApplication / Service Logic

IntelligentConnectivityLogic

Connectivity LogicThe Enterprise Service Bus

Application/Service Logic

Process Logic

18

IBM Software Group


What is an Enterprise Service Bus?The ESB is not one thing – it is a distributed architecture

The Enterprise Service Bus

……. …….

…….

ESB ESB

ESBESB

ESB

19

IBM Software Group


Flexible connectivity infrastructure for integrating applications and services


20

IBM Software Group


Agenda






Case Studies

21

IBM Software Group


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

22

IBM Software Group


ESB offerings from IBM WebSphereWebSphere delivers the most complete ESB solution

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

23

IBM Software Group


WebSphere ESB for z/OSBuilt on WebSphere Application Server for an integrated SOA platform

Integrates seamlessly with WebSphere platform

Delivers business-critical qualities of service

Easily extended to WebSphere Process Server

Integrated solution for service mediation and hosting

• Provides business visibility with embedded event engine for Business Activity Monitoring solutions

• Optimized for standard XML and web services formats, with basic support for other common formats

• Integrates everything with WebSphere Adapters for enterprise applications, the breadth of the WebSphere ecosystem, and support for standard protocols

• Delivers leadership in SOA standards for service composition, and leverages the embedded messaging and web services engines from WebSphere

24

IBM Software Group


Advantages of WebSphere ESB for z/OS

High Availability

Workload Management

Scalability and isolation

Accounting, performance and capacity planning

25

IBM Software Group


WebSphere Message Broker for z/OSBuilt for universal connectivity and transformation in heterogeneous IT environments

• Optimized for high-volume processing and rapid time to value for complex mediation requirements with a robust set of pre-built mediation function

• Enables transformation between a wide range of data formats, including XML, legacy, and industry standards, and custom formats

• Integrates everything through standard protocols, WebSphere Adapters for enterprise applications, and specialized connectivity options

• Exploits the unparalleled reach and reliability of the WebSphere MQ enterprise messaging backbone

• Connect FROM anything TO anything: the broadest range of transport, protocol, data format and transformation capabilities

• Flexible and function rich ESB: address a wide range of requirements encompassing both existing & new, applications and services.

• Tightly integrated and optimized for the z/OS platform, including specific features for MQ, DB2, CICS, IMS and RRS subsystems.

• Advanced features such as Complex Event Processing and file based integration including VSAM.

26

IBM Software Group


High Availability

z/OS-specific Connectivity

Workload Management

Reporting and Chargeback

Option to extend transformation options

Advantages of WebSphere Message Broker for z/OS

27

IBM Software Group


WebSphere DataPower Integration Appliance XI50Purpose-built hardware ESB for simplified deployment & hardened security

Redefines the boundaries of middleware with specialized hardware

Many functions integrated into a single device

Simplified deployment and ongoing management

• Captures and emits events to facilitate web services management and enable business visibility in Business Activity Monitoring solutions

• Enables transformation between a wide range of data formats, including XML, legacy, and industry standards, and custom formats

• Optimized to bridge between leading standard protocols at wirespeed, including web services, messaging, files, and database access

• Secures services on the network with sophisticated web services access control, policy enforcement, message filtering, and field-level encryption

29

IBM Software Group


Scenario : for WebSphere ESBComposite 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

30

IBM Software Group


Scenario : for WebSphere Message BrokerHeterogeneous 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

31

IBM Software Group


Scenario : for WebSphere DataPower Integration ApplianceProtocol bridging

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

ODBC

3rd-partyJMS

MQ

HTTP/ HTTPS

FTP/ FTP over SSLJMS

DB2Oracle

SybaseODBC

WAS JMS

WMQ

Data Power XI50

3rd Party App Server

32

IBM Software Group







Case Studies

Agenda

33

IBM Software Group


ESB offerings from IBM WebSphereAn ESB without limits to enable complete SOA and BPM solutions

Universal Transformation

WebSphere Transformation Extender

Service Monitoring

Tivoli CAM for SOA

Publish Find Enrich GovernManage

Service Registry

WebSphere Services Registry and Repository

WebSphere MQ messaging backbone

MQI Java JMS XMS for .NET C# XMS for C/C++

Enterprise Messaging Backbone

WebSphere MQWebSphere Data Power XML

Security Gateway XS40

SOA Security Appliance

WebSphere Process Server

Service Orchestrationand BPM

WebSphere Adapters

Service Enablement

34

IBM Software Group


WebSphere Services Registry and RepositoryRuntime selection and invocation interactions

(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

WebSphere Service Registry and Repository

(3) Retrieve requestor information

(4) Retrieves candidate providers information

Message

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

MessageService

Dynamic selectionDynamic selection

WSRR support• WESB 6.0.2 mediation primitive

• Port Type match• WMB SupportPac

• Port Type match• General metadata retrieval

• DataPower• Port Type match

35

IBM Software Group


WebSphere Adapters

Standards Based – Strategic Direction– JCA1.5 architecture plus support for SCA,CEI

and some BIDI language support

– Bundled with WebSphere Integration Developer (WID) development studio

– Configured with wizards based on Enterprise Metadata Discovery specification

– Deploy with WebSphere Process Server & WebSphere ESB

Version 6.0.2 includes WBI Adapter Framework and equivalent WBI adapter– Deploy with WebSphere Message Broker

For creating Custom JCA Adapters, download free WebSphere Adapter toolkit– Create JCA adapters for WAS

Business Applications• Oracle eBusiness Suite• JD Edwards• EnterpriseOne• PeopleSoft• Siebel• SAP *

Technical• JDBC *

• Flat Files *

• Email *

• FTP *

36

IBM Software Group


Deployment Options

WebSphere Transformation Extender

• WebSphere ESB• WebSphere Message

Broker• WebSphere Application

Server• WebSphere Process

Server• Stand-alone

• System z• Windows • UNIX• Linux

Industry Packs• HIPAA• HL7 • NCPDP• SWIFTNet FIN• SWIFTNET Funds• TRADERCOMS

• X12• Odette • EANCOM• EDIFACT• SEPA

Map

Transform

Validate

Code-free Design & Deployment High Throughput Execution of Complex Transformations In-Process Data Validation Solution Accelerator Packs One Engine, Multiple Deployment Options including System z

37

IBM Software Group


1. Describe the data

Developing a solution with WebSphere TX Multiple Deployment Options

Batch / JCL

CICS

IMS

COBOL program, EJB, Java program, etc.

Event-driven (with Launcher edition (USS)

WebSphere Message Broker + WTX4MB (USS)

Design Studio

Map

3. Deploy the transformation and run

2. Transform the data

XML Schema

Z/OS

COBOL Copybook

000520****************************************************************000530 01 TP-API-CB.000540 03 TP-AGAPI-CB.000550 000560 05 TP-AGAPI-REQUEST PIC X(40).000570 88 TP-AGAPI-INITIALIZE-REQUEST000580 VALUE 'INITIALIZE-MAPPING'.000590 88 TP-AGAPI-PERFORM-MAPPING000600 VALUE 'PERFORM-MAPPING'.000610 88 TP-AGAPI-FINISH-MAPPING000620 VALUE 'FINISH-MAPPING'.

000640 05 TP-AGAPI-VERSION PIC X(04).000650 88 TP-AGAPI-VERSION-VALID VALUES ARE '0100'000660 '0200'.000670 88 TP-AGAPI-VERSION-0100 VALUE '0100'.000680 88 TP-AGAPI-VERSION-0200 VALUE '0200'.

Windows

Importer

Importer

WTX Adapters

38

IBM Software Group


WebSphere Transformation Extender Pack for SEPA

For IBM Clients needing to develop their Single Euro Payments Area solution with

IBM WebSphere Transformation Extender

SEPA Credit Transfer

SEPA Direct Debit

SEPA UNIFI Message and Content Validation

EPC Implementation Rules Validation

SEPA to SWIFT MT 103

Sample SEPA-Domestic converters

39

IBM Software Group







Case Studies

Agenda

40

IBM Software Group


Criteria for ESB selection

Communication Protocols & Interaction Patterns

–Critical (e.g., MQ, SOAP/HTTP, pub/sub)

–Accommodated

–“Associated” standards (e.g., WS-Security, headers)

–APIs (e.g., JMS)

–Adapters (e.g. SAP)

41

IBM Software Group



Message Models & Meta-models

–Critical (e.g., XSD, specific XML schema)

–Accommodated

–“Associated standards” (e.g., SOAP headers, attachments)

–“Optimizing capabilities” (e.g., Weak-typing, validation)

–Adapters (e.g. SAP IDOC)

42

IBM Software Group



Mediation Flows and Mediation Patterns

–Mediation Flows and Mediation Patterns

–Conversion

–Transformation engine(s)

–Routing

–Security and Management integration

–Logging and auditing integration

–Registry integration

–Breadth of pre-built mediation primitives

–Custom mediation capability and Programming model

–Weakly-typed processing

43

IBM Software Group



Qualities of service

–Heterogeneous transaction coordination

–Reliable/assured delivery

–Performance

–Message size

–Throughput

–Scalability

–Reliability

–Availability

44

IBM Software Group



Non-functional

–Affinity to SOA environment (e.g., WebSphere Process Server)

–Affinity to IT environment (e.g. J2EE application server)

–Development tooling capabilities and affinity to current tools

–Configuration and administration tooling capabilities

–Existing and required skill set (e.g., J2EE skills)

–Product maturity and comfort level with leading edge products

–Price and total cost of ownership

45

IBM Software Group



Ease of integration

–with Monitoring and Management infrastructure

–with Security infrastructure

46

IBM Software Group


Deciding... to use WebSphere ESB

You use WebSphere Application Server – Your team has skills with WAS Administration and Java coding

You are now or planning on developing business process using WebSphere Process Server– WebSphere ESB and WPS have common tooling, programming model, and runtime

You are integrating with ISV business applications hosted on WAS or 3rd party solutions which extend and support WAS

You are focused on standards based interactions using XML, SOAP, and WS*

You want to mediate between Web services and existing systems using JMS and WebSphere JCA Adapters

Reliability and extensive transactional support are key requirements

You want to minimize your server investment by co-hosting WebSphere services and ESB in one application server

You want integration with other IBM WebSphere and Tivoli products

47

IBM Software Group


Deciding... to use WebSphere Message Broker

You are currently using WebSphere MQ or WebSphere Message Broker– Migrate to V6; implement ESB Patterns

– Leverage existing WMB skills

You have extensive heterogeneous infrastructures, including both standard and non-standards-based applications, protocols, and data formats– You have extensive MQ skills and infrastructure

– You are using Industry formats such as SWIFT, EDI, HL7

– You are integrating core z assets (e.g. connecting to CICS COBOL applications)

You are implementing a wide range of messaging and integration patterns– Examples include event processing, message splitting, aggregation

You need extensive pre-built mediation support

To achieve very high-performance with horizontal and vertical scaling

You have complex transformation needs

Reliability and extensive transactional support are key requirements


48

IBM Software Group


Deciding... to use WebSphere DataPower XI50

Ease of use is a pre-dominant consideration–Simple experience of drop-in installation and admin-based configuration with

no or minimal development required

You are transforming between XML-and-XML or XML-and-any other format

Your interaction patterns are relatively simple

Your mediation requirements are met by the existing DP mediations and minimal extensibility is needed

You are using XML-based or WS-Security extensively

You require use of advanced Web services standards

You need to minimize message latency when adding an ESB layer

You are doing extensive XML processing combined with high performance reqs

Your ESB must be in production very quickly


50

IBM Software Group


Deciding... to use WebSphere DataPower XS40

You are using an ESB gateway pattern – All XML interaction with 3rd parties should go through XS40 for XML threat

protection

51

IBM Software Group


Integrating ESBs

Options for integrating WMB and WESB/WPS together

– WMB’s JMS nodes (e.g. JMSInput and JMSOutput nodes) to WPS/WESB JMS binding

– WMB’s MQ nodes (e.g. MQInput and MQOutput)

– WMB’s MQ nodes with WAS v6 using WMQ

– WMB’s HTTP and SOAP nodes to WPS/WESB via SOAP/HTTP

52

IBM Software Group


Integrating ESBs

Options for integrating DataPower with WMB

– WMB’s HTTP node to DP using SOAP or XML over HTTP(s)

– DP XI50 use MQ to WMB MQ nodes

53

IBM Software Group


Integrating ESBs

Options for integrating DataPower with WESB/WPS

– SOAP over HTTP

– XML over HTTP into the HTTP Adapter of WESB/WPS

– With DP XI50 using SIBus MQLink but requires a hop through an MQ server

54

IBM Software Group







Case Studies

Agenda

55

IBM Software Group


Connectivity between web service requester & an EIS system

Web Servicesrequester

EIS Backend

SAP Adapter

ESB

Tooling Domain of interest -Intranet

WSRR

56

IBM Software Group



Customer environment– This customer is leading adopter of technology. Comfortable with sophisticated solutions

– WebSphere Application Server customer

Business Requirements– The customer wants to provide web service access to functionality in an Enterprise Information System

such as SAP R/3, PeopleSoft, or Oracle Financials

– Intranet environment doesn’t require complex security considerations

– The integration is based on message exchange/data replication scenarios - there is no business process or data synchronization between clients and EIS systems

– Support moderate volume of requests

Technical Requirements– The targeted integration is one-to-one, i.e., one ESB virtual service maps to one EIS application,

although multiple EISs can be exposed as web services at the same time

– Data transformation should use XSLT; development tooling important

– Log the messages as they flow through the hub – asynchronously to a file

Architecture Decisions– J2EE environment preferred

– Use available adapter product to simplify development

57

IBM Software Group



Infrastructure Pattern > ESB– Service virtualization

– Domain isolation unimportant

ESB Product selection > WebSphere ESB– Transport Protocols

– JCA adapter supported– SOAP/HTTP– Synchronous Request/response sufficient

– Message models

– XML metamodel desired– Content model supported

– Mediation flows

– XLST transformation and supporting tooling

– QoS and Non-functional requirements

– J2EE foundation (WebSphere Application Server)– XSLT transformation skills available– Adequate throughput and/or response time– Leading edge adopter

58

IBM Software Group


Connectivity between heterogeneous requesters & providers (Multi-protocol Exchange)

ESB

.NET Client

WebSphere (WAS/Portal)

Tooling

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

WebSphere provider

CICS

Some provider

Domain of interest -Intranet

WSRR

59

IBM Software Group



Customer environment– Customer is a leading adopter of technology. Comfortable with sophisticated solutions

Business Requirements– Any provider must be accessible via multiple heterogeneous requesters

– Support moderate volume of requests

– Intranet environment does not require complex security considerations

– Global transactions across multiple heterogeneous transaction managers

Technical Requirements– ESB must support

– Communication protocol conversion, but not adapters– Flexible data model conversion, with acceptable performance and adequate tooling

– Enterprise class persistent messaging backbone

Architecture Decisions– Canonical data model(s) used in ESB

– Consumers and providers must adapt to the service definition supported by the ESB

60

IBM Software Group



Infrastructure Pattern > ESB– Significant service virtualization

ESB Product selection > Message Broker– Transport Protocols

– Multiple protocols– Synchronous and asynchronous Request/response– MQ provides enterprise class persistent messaging backbone

– Message models

– Multiple built-in message metamodels– Content models supported

– Mediation patterns

– Significant protocol conversion capability– Significant transformation capability with supporting tooling– Supports advanced correlation of asynchronous request/response– Extensive runtime configuration options

– QoS and Non-functional requirements

– Global transactions across multiple heterogeneous transaction managers– Mature product which supports throughput and/or response time– Sophisticated transformation skills available

61

IBM Software Group


SOA Security and Integration

WebSphere DataPower Integration Appliance XI50

WebSphere MQ System z

External Application Server XI50

MQSystem z

62

IBM Software Group


SOA Security and Integration Challenge

– Difficult to modify home-grown custom software application

– Adopt SOA to enable an online Web service to greatly increase revenues, while reducing costs & increasing the security of the service

Solution– Deployed WebSphere DataPower Integration Appliance

– XI50 for SOA security and to transform & route messages

– Acts as a gateway by forwarding messages to System z mainframe to be checked against database

– Integrates ACORD XML services with existing WebSphere MQ

– Integrates SchemaTron validate to generate XSLT to load the generated XSLT onto the XI50 for runtime execution & filtering

Benefits– More than 10 times faster than internally developed custom software

– Fraud-protection processes are faster, more secure & less error prone

– Web service allows MIB to offer more services to customers while reducing overhead cost

63

IBM Software Group


Define your ESB architecture and terminology

–ESB components and related components–Specifically look at adapters, universal transformation and registry

Evaluate ESB products using your prioritized requirements

Develop and deliver ESB function incrementally

Summary – implementing an ESB

64

IBM Software Group







Case Studies

Agenda

© 2007 IBM Corporation IBM Software Group July 2007 Why do I need an Enterprise Service Bus and...

Documents

Transcript of © 2007 IBM Corporation IBM Software Group July 2007 Why do I need an Enterprise Service Bus and...