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

1. Dale Lane Hursley Park, IBM UK Why do I need an Enterprise Service Bus and which one? July 2007

2. 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. 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

4. ESB inter-connects requestor and provider ESB provides Service Virtualization Intelligent processing of service request / responses, events, messages Service Provider Service Requestor What is an Enterprise Service Bus? Core Principles of the ESB Architectural Pattern ESB

5. What is an Enterprise Service Bus? A flexible connectivity infrastructure for integrating applications and services. An ESB performs the following between requestor and service • MATCHES & ROUTEScommunications between services • CONVERTSbetween different transport protocols • TRANSFORMSbetween different data formats • IDENTIFIES & DISTRIBUTESbusiness events

6. 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

7. What can an Enterprise Service Bus do? An ESB enables simple application integration across different platforms programming models messaging standards

8. 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

9. Why can an ESB help your connectivity needs? • 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

10. 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 Why can an ESB help your connectivity needs?

11. Loose coupling requires greater investment More design work More implementation work Benefits of an ESB: Loose coupling

12. 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 Benefits of an ESB: Loose coupling

13. Benefits of an ESB: Loose coupling Delivery Assurance Semantic Interface Location Language Data Format Interaction State Provider Consumer Business Data Model Service Version Security Protocol Service Provider Identity Platform Time

14. What is an Enterprise Service Bus? Business Innovation & Optimization Services Provide for better decision-making with real-time business information Interaction Services Process Services Information Services IT ServiceManagement DevelopmentServices Manages diverse data and content in a unified manner Enables collaboration between people, processes & information Orchestrate and automate business processes Enable inter-connectivity between services ESB Integrated environment for design and creation of solution assets Manage and secure services, applications & resources Partner Services Business App Services Access Services Apps & Info Assets Connect with trading partners Build on a robust, scaleable, and secure services environment Facilitate interactions with existing information and application assets Infrastructure Services Optimizes throughput, availability and performance SOA Reference Architecture – Model of the Logical Architecture

15. What is an Enterprise Service Bus? An ESB-centric view of the logical model ESB Application Services Security Interaction Process Information Management Services Development Services Partner Business App Access Management Registry • Outside of the ESB: • Business logic (“Application Services”)‏ • Tightly coupled to the ESB: • Service Registry • Tooling required for ESB • Development • Administration • Configuration (via Service Registry)‏ • Loosely coupled to the ESB: • Security and Management

16. What is an Enterprise Service Bus? “Uncluttered” Well Defined Self-Contained Application / Service Logic The ESB decouples connectivity logic from application and process logic – making SOA possible Flexible “Uncluttered” Business Process Logic Process Logic Intelligent Connectivity Logic Connectivity Logic The Enterprise Service Bus Application/Service Logic

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

18. Flexible connectivity infrastructure for integrating applications and services What is an Enterprise Service Bus?

19. Agenda 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

20. ESB offerings from IBM WebSphere WebSphere delivers the most complete ESB solution WebSphereMessage Broker Built for universal connectivity and transformation in heterogeneous IT environments WebSphere ESBBuilt on WebSphere Application Server for an integrated SOA platform WebSphere DataPowerIntegration Appliance Purpose-built hardware ESB for simplified deployment and hardened security

21. ESB offerings from IBM WebSphere WebSphere delivers the most complete ESB solution • Leading web services standards • First class interoperability between ESB products • Mission-critical qualities of service • Mediations to enable common patterns • Transformation of common data formats • Connectivity via common protocols

22. WebSphere ESB for z/OS Built 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 • Delivers leadership in SOA standards for service composition, and leverages the embedded messaging and web services engines from WebSphere • Integrates everything with WebSphere Adapters for enterprise applications, the breadth of the WebSphere ecosystem, and support for standard protocols • Optimized for standard XML and web services formats, with basic support for other common formats • Provides business visibility with embedded event engine for Business Activity Monitoring solutions

23. Advantages of WebSphere ESB for z/OS • High Availability • Workload Management • Scalability and isolation • Accounting, performance and capacity planning

24. WebSphere Message Broker for z/OS Built for universal connectivity and transformation in heterogeneous IT environments • 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. • Exploits the unparalleled reach and reliability of the WebSphere MQ enterprise messaging backbone • Integrates everything through standard protocols, WebSphere Adapters for enterprise applications, and specialized connectivity options • Enables transformation between a wide range of data formats, including XML, legacy, and industry standards, and custom formats • Optimized for high-volume processing and rapid time to value for complex mediation requirements with a robust set of pre-built mediation function

25. High Availability z/OS-specific Connectivity Workload Management Reporting and Chargeback Option to extend transformation options Advantages of WebSphere Message Broker for z/OS

26. WebSphere DataPower Integration Appliance XI50 Purpose-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 • Secures services on the network with sophisticated web services access control, policy enforcement, message filtering, and field-level encryption • Optimized to bridge between leading standard protocols at wirespeed, including web services, messaging, files, and database access • Enables transformation between a wide range of data formats, including XML, legacy, and industry standards, and custom formats • Captures and emits events to facilitate web services management and enable business visibility in Business Activity Monitoring solutions

27. Scenario : for WebSphere ESB Composite application service hosting and mediation Customer ServiceReps Warehouse Application Customers FTP WebSphere ESB XML/JMS Service Mediations Web Applications Credit Application Business Services JDBC Customer MasterDB2 JDBC SOAP/HTTPS WebSphereAdapter Application DataOracle DB Suppliers ERP System

28. Scenario : for WebSphere Message Broker Heterogeneous service mediation WebSphere Service Registry and Repository SOAP/JMS SOAP/JMS WebSphere (WAS/Portal)‏ 3rd-party App Server provider WebSphere Message Broker SOAP/HTTP SOAP/HTTP .NET provider .NET Client XML/HTTP XML/HTTP Legacy/custom provider Some Client COBOL Copybook/MQ XML/MQ XML/MQ Client CICS IDOC/ALE Text/MQ Text/MQ Client SAP

29. Scenario : for WebSphere DataPower Integration Appliance 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 WAS JMS DB2 Oracle Sybase ODBC JMS FTP/ FTP over SSL Data Power XI50 3rd-partyJMS MQ 3rd Party App Server WMQ HTTP/ HTTPS Protocol bridging

30. 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

31. ESB offerings from IBM WebSphere Publish Govern Manage Enrich Find An ESB without limits to enable complete SOA and BPM solutions Service Orchestrationand BPM Service Registry Service Monitoring WebSphere Process Server WebSphere Services Registry and Repository Tivoli CAM for SOA Universal Transformation Service Enablement WebSphere Adapters WebSphere Transformation Extender SOA Security Appliance Enterprise Messaging Backbone MQI Java JMS XMS for .NET C# XMS for C/C++ WebSphere Data Power XML Security Gateway XS40 WebSphere MQ messaging backbone WebSphere MQ

32. WebSphere Services Registry and Repository Service Runtime selection and invocation interactions Dynamic selection WebSphere Service Registry and Repository • WSRR support • WESB 6.0.2 mediation primitive • Port Type match • WMB SupportPac • Port Type match • General metadata retrieval • DataPower • Port Type match Publish Govern Manage Enrich Find (3) Retrieve requestor information (4) Retrieves candidate providers information ESB Mediation Message Message Message (2) Invokes a selection mediation. (5) Executes matching algorithm to identify the provider service for requestor service (1) A Message is received (6) Message is transformed and routed to the selected endpoint.

33. 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 *

34. WebSphere Transformation Extender 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 Transform Map Validate Deployment Options Industry Packs • WebSphere ESB • WebSphere Message Broker • WebSphere Application Server • WebSphere Process Server • Stand-alone • System z • Windows • UNIX • Linux • HIPAA • HL7 • NCPDP • SWIFTNet FIN • SWIFTNET Funds • TRADERCOMS • X12 • Odette • EANCOM • EDIFACT • SEPA

35. Developing a solution with WebSphere TX Z/OS Importer Map Importer Multiple Deployment Options • Batch / JCL • CICS • IMS • COBOL program, EJB, Java program, etc. • Event-driven (with Launcher edition (USS)‏ • WebSphere Message Broker + WTX4MB (USS)‏ • 2. Transform the data 1. Describe the data WTX Adapters • 3. Deploy the transformation and run COBOL Copybook XML Schema 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-REQUEST 000580 VALUE 'INITIALIZE-MAPPING'. 000590 88 TP-AGAPI-PERFORM-MAPPING 000600 VALUE 'PERFORM-MAPPING'. 000610 88 TP-AGAPI-FINISH-MAPPING 000620 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'. Design Studio Windows

36. 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

37. 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

38. 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)‏

39. Criteria for ESB selection 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)‏

40. Criteria for ESB selection 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

41. Criteria for ESB selection Qualities of service Heterogeneous transaction coordination Reliable/assured delivery Performance Message size Throughput Scalability Reliability Availability

42. Criteria for ESB selection 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

43. Criteria for ESB selection Ease of integration with Monitoring and Management infrastructure with Security infrastructure

44. 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

45. 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 You want integration with other IBM WebSphere and Tivoli products

46. 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 You want integration with other IBM WebSphere and Tivoli products

47. 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

48. 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

49. 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

50. 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