IBM WebSphere Enterprise Service Bus Proof of Technology

Transcription

1 IBM WebSphere Enterprise Service Bus Proof of Technology An IBM DeveloperWorks Workshop

2 Featured Products IBM WebSphere Enterprise Service Bus (ESB) v7.0 WebSphere Integration Developer v7.0 WebSphere Service Registry and Repository v7.0 WebSphere MQ v7.0

3 Objectives After this session you should be able to: Describe the role of an ESB in a Service Oriented Architecture (SOA) Understand where it can be used in your organization Use the WebSphere Integration Developer to develop a mediation Use the Test Environment to test your mediation Build out interactions with WebSphere Process Server, WebSphere Services Registry and Repository, and WebSphere MQ

4 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) WebSphere MQ Service Invocation (0:45) Service Gateway (1:00) WSRR Integration (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

5 Agenda for Day One P00 Introductions (0:20) P01 SOA and ESB (0:40) P02 WebSphere Enterprise Service Bus Introduction (0:45) Break (0:15) L01 Basic Mediation Lab (0:45) Lunch (1:00) P03 Service Message Objects (SMOs) & Primitives (0:30) L02 Service Component Architecture (SCA) and WebSphere Process Server Integration (1:00) Break (0:15) L03 WebSphere MQ Service Invocation (0:45) L04 Service Gateway Lab (0:60) P00 Review Today, Discuss Tomorrow

6 Agenda for Day Two P00 Review L05 WebSphere Service Registry and Repository Integration (0:45) Break (0:15) L06 Sub Flow Lab (0:30) P05 Adapters (0:30) L07 Adapter (0:30) Lunch (1:00) L08 Advanced Mapping Lab (1:00) P06 Service Invoke and Custom Primitives (0:30) L09 Custom Mediation Component (0:30) P00 Evaluations & Next Steps (0:15)

7 P01 SOA and ESB Introduction Service Oriented Architecture and the Enterprise Service Bus An IBM DeveloperWorks Workshop

8 Objectives Explain the concepts of a Service Oriented Architecture (SOA) Describe the role of the Enterprise Service Bus (ESB) within SOA What is an ESB? Why is an ESB important to me?

9 Service Component Architecture - IBM SOA Programming Model Separation of Concerns Java Java What How WSDL Port Type Interface WSDL Port Type Reference Mediations Java BPEL State Machine Business Rules Human Task Implementation Types Selector Interface Maps

10 SCA enables SOA flexibility SOA is the architectural style that supports loosely coupled services to enable business flexibility in an interoperable, technology-agnostic manner. SOA consists of a composite set of business-aligned services that support a flexible and dynamically re-configurable end-to-end business processes realization using interface-based service descriptions. WSDL A business contract to X be implemented by.

11 The Vertical Silo Problem Cashier Accountant Point of Sale Comptroller Accounting Sales Tax Calculation Sales Tax Calculation Analyst Application functionality is tightly bound to a static notion of a process Little flexibility to take into account new roles or processes Financial Reporting Sales Tax Calculation Applications Infrastructure This creates redundant code and functions. Inflexible, expensive and hard to maintain. Management is focused on the health of the server, network and middleware Applications are black boxes.

12 The New World: Composable Services Cashier Point of Sale X Accountant Comptroller Accounting X Sales Tax Calculation Applications Financial Reporting X Sales Tax Calculation Sales Tax Calculation Analyst Sales Tax Calculation X This forces us to re-examine what we call applications and what we call infrastructure! Infrastructure Services Externalizing common functions as services, in a standards-based fashion, allows for code re-use, saving on development and maintenance. However, this creates an important dependency; if the service is not working, the applications cannot function X

13 The New World: Composable Services + ESB Cashier Point of Sale Accountant Comptroller Accounting Sales Tax Calculation Sales Tax Calculation Analyst Financial Reporting Sales Tax Calculation Applications Services ESB Sales Tax Calculation Infrastructure Hosting the service on an ESB destination, we have policy enforcement, mediations and a centralized management point. This ESB destination can be monitored by IBM Tivoli products.applications are no longer black boxes.

14 Choreograph components into business processes Customer Division(s) Shared Services Supplier Outsourced

15 Add a Flexible Integration Layer - ESB Customer Division(s) Enterprise Service Bus Shared Services Supplier Outsourced Mediations WebSph ere DataPo wer WebSphere Service Registry & Repository Tiv oli SOA Management Adapters Web Services Gateway

16 SOA Reference Architecture Enable SOA Model of the Logical Architecture Integrated environment for design and creation of solution assets Interaction Services Process Services Information Services Enables collaboration between people, processes & information Orchestrate and automate business processes Manages diverse data and content in a unified manner ESB Enable inter-connectivity between services Partner Services Business App Services Access Services 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 IT Service Management Provide for better decision-making with real-time business information Apps & Info Assets Development Services Business Innovation & Optimization Services Manage and secure services, applications & resources

17 What Problems Do We Need To Solve? How to move information around A B C X A messaging component Y Z

18 Why is this a Challenge? Computers are really dumb. You have to tell them everything. How do you? Move data across different systems, platforms, and devices when the hardware (HW), software (SW) configurations and programming models are different? Overcome network failures? Deliver information when the target application is not online or is busy? Ensure transmission integrity and recovery? Handle lost or/duplicate data? Ensure a secure connection? Ensure multi-step transactions either happen completely or not at all? Apply qualities of service based on different requirements? e.g., assured delivery, fast delivery? Manage a session (request/response)? Efficiently distribute events? Scale to handle volumes? Deal with data in unlike formats? Determine which data to send where? Audit who send what, where and when? You either: 1. Program it all into your applications 2. Build your own middleware 3. Buy middleware to do it for you Computers are really dumb. They do exactly what you tell them to.

19 What is an Enterprise Service Bus (ESB)? A flexible connectivity infrastructure for integrating applications as services which reduces the number, size, and complexity of interfaces. An ESB: VIRTUALIZES the location and identity of participants CONVERTS between different transport protocols used by the participants TRANSFORMS message formats between participants APPLIES appropriate qualities of service for the given interaction DISTRIBUTES business event information to/from disparate sources. Shape = Protocol Color = Data type

20 The ESB allows you to focus on your core business The integration logic stays in the bus NEW Check Traveler Service Travel Reservation Process Check Credit Service Book Flight Service Add new services faster Enterprise Service Bus Hotel Availability Service NEW Flight Availability Service Flight Availability Service Book Hotel Service OLD Flight Availability Service Book Car Service Change services with minimal impact to existing services

21

22 P02 WebSphere Enterprise Service Bus Introduction An IBM DeveloperWorks Workshop

23 Presentation Objectives Introduce IBM WebSphere Enterprise Service Bus (ESB) Explain SOA Infrastructure Challenges Explain the WebSphere ESB Architecture Explain other IBM ESB Offerings

24 SOA Reference Architecture Business Innovation & Optimization Services Facilitates better decision-making with real-time business info Development Services Provides an Integrated environment for designing and creating solution assets Interaction Services Process Services Information Services Enables people, processes & info to collaborate Orchestrates & automates business processes Provides unified mgmt of diverse data and content Enterprise Service Bus Facilitates communication between resources Partner Services Business App Services Access Services Connects with trading partners Supports robust, scaleable, & secure svcs Facilitates interactions with existing info & app assets Infrastructure Services Optimizes throughput, availability and performance IT Service Management Manages and secures services, apps, & resources

25 ESB Core Principle Service Virtualization Service Requestor ESB ESB inter-connects requestor and provider Interactions are decoupled A level of indirection is introduced Indirection is a key SOA principle separation of concerns ESB provides Service virtualization of Location and identity Interaction pattern and protocol Interface ESB also enables service oriented solution aspects Security Management Enforcement Service Provider

26 ESB an Architectural Pattern We describe the enterprise service bus first and foremost as an architectural pattern. In fact, it is possible to construct service buses from a variety of different underlying integration technologies. The architecture pattern remains valid and is a guiding principle to enable the integration and federation of multiple service bus instantiations. Rob High, IBM SOA Foundation Chief Architect, in SOA Foundation Architecture Whitepaper

27 Enterprise Service Bus Reference Architecture Enterprise Service Bus Gateway Mediation Primitives XSLT Maps BO Maps DB Lookup Service Invoke Logging/Tracing Message Filter FanIn / Fan Out SLA Check Custom Mediations Message Validator Message Model / Formatting Communication ACORD EDIFACT RosettaNet HL7 Copybook SOAP/HTTP FTP String/MQ XML/JMS XML/HTTP SOAP/JMS QoS Agents, service requestors, Infrastructure (security, monitoring) Routing Interaction Patterns (pub/sub, sync/async, ) Message Flows

28 Standards-based Enterprise Service Bus BPEL Engine JMS Message Interacting System (internal or external) SOAP Message SCA Service UDDI WSDL Service Bus Web Service WSDL Interface Component MQ Message SCA Service WSDL Interface Component Web Service WSDL Interface Component SCA Service WSDL Interface Component Web Service WSDL Interface Component

29 WebSphere ESB Delivering an Enterprise Service Bus to power your SOA Provides Web Services connectivity, JMS messaging and service oriented integration Improve flexibility through the adoption of service oriented interfaces Minimize disruption by using an ESB to handle integration logic Allow the flow of business events and add needed intelligence to that flow Ease of use Integrated, interactive and visual development experience requires minimal programming skills Simple to develop, build, test, deploy and manage Improve time to value Cost effective solution for services integration Support for hundreds of ISV solutions Save time and development costs by utilizing pre-built mediation function Dynamically re-configure to meet changing business needs Seamless integration with the WebSphere platform Leverages WebSphere qualities of service: clustering, fail-over, systems management, security Easily extends to leverage WebSphere Process Server as needs dictate Integrates with IBM Tivoli security and systems management offerings

30 WebSphere ESB Key Features & Benefits Feature Function Benefit Built on WebSphere Application Server Inherits WebSphere Application Server Quality of Service (QoS) including high availability, security, transaction integrity and centralized administration Superior and proven reliability and management JMS, HTTP, IIOP Rich Web Services (Internet Inter-Orb connectivity options Protocol ) and adapter connectivity Abstracts connection complexity associated with Web Services Native SCA support for WebSphere MQ Transactional integration with Seamless integration WebSphere MQ across the WebSphere MQ networks Programming : Prebuilt management and mediation environments Intelligent message routing, logging, and XSL Transformations (XSLT) transformation services, along with service endpoints Abstracts integration logic outside the application, reducing coding, improving clarity and promoting reuse

31 WebSphere ESB Key Features & Benefits Feature Function Supports message, service and event oriented architectures Web Services, XML, HTTP, A central, logical JMS, WebSphere MQ and messaging infrastructure Common Event Infrastructure for the organization (CEI) enable many kinds of bus destinations Supports multiple messaging styles Synchronous, Asynchronous, More flexibility and drives Event-Oriented and Publish/ use of messaging Subscribe patterns Easy access to your packaged and legacy applications Support for Java EE Existing IT investment Connector Architecture (JCA) can easily participate in and WBI Adapters with SOA discovery tools Eclipse-based tooling with WebSphere Integration Developer for artifact development Widely adopted tooling environment with WebSphere Integration Developer also used with WebSphere Process Server Benefit Increases return on programming skills and better integration with WebSphere Process Server

32 WebSphere ESB Key Features & Benefits Feature Function Benefit Service Component Programming model Single programming model for message queues, event topics and services Reduces complexity and increases flexibility of application code Policy enforcement point Security, encryption, and other policy enforcement Centralized point for policy enforcement Integrated Universal Description, Discovery, and Integration (UDDI) Service Registry or WebSphere Service Registry and Repository Locate and store service artifacts using WebSphere Application Server UDDI or WebSphere Service Registry and Repository More secure Web Services with greater reuse, decorate data with ontology (WebSphere Service Registry and Repository) Dynamically call WebSphere Service Registry and Repository or UDDI for service endpoint lookup

33 WebSphere ESB and WebSphere Integration Developer Delivering an Enterprise Service Bus that s easy to use WebSphere Integration Developer provides an integrated, interactive and visual development environment for rapid development of integration logic Requires minimal knowledge of Java or Java EE Simple to develop, build, test, deploy and manage services components Comprehensive documentation with easy to understand samples Provides a simplified development experience for standards-based artifacts First-class support for intelligent message routing, enrichment, and transformation

34 WebSphere Application Server, WebSphere ESB, and WebSphere Process Server WebSphere Process Server Choreography And Solution Viewpoint WebSphere ESB Mediation WebSphere Application Server Network Deployment WebSphere Application Server Clustering App Server

35 WebSphere ESB and WebSphere Application Server WebSphere ESB: Mediation layer builds on WebSphere Application Server foundation to provide intelligent connectivity Pre-built mediation functions and easy to use tools enable rapid construction and implementation of a Enterprise Service Bus Leverage visual tooling to exploit supplied pre-built mediation functions WebSphere Application Server: Transport layer foundation provides infrastructure via JMS 1.1, HTTP, IIOP

36 WebSphere ESB and WebSphere Process Server WebSphere Process Server: Process layer builds on WebSphere ESB and WebSphere Application Server foundation to deliver robust business process management Built on a common foundation, so that WebSphere ESB customers can easily migrate upward and leverage: Support for all styles of integration, including human tasks, roles based task assignments, and multilevel escalation. Business rules, business state machines, and selectors to dynamically choose interface based on business scenarios Change business processes on the fly with relatively minimal skills WebSphere ESB: Mediation layer builds on WebSphere Application Server foundation to provide intelligent connectivity WebSphere Application Server: Transport layer foundation provides infrastructure via JMS 1.1, HTTP, IIOP Use WebSphere Process Server when you need to automate business processes that span people, workflows, applications, systems, platforms, and architectures.

37 WebSphere Integration Family WebSphere Process Server Choreography Service Components Human Tasks Business Processes Business State Machines Business Rules and Selectors WebSphere ESB Supporting Services Interface Maps Business Object Maps Mediations Mediation SOA Core Service Component Architecture (SCA) Clustering Relationships Business Objects Common Event Infrastructure WebSphere Application Server Network Deployment AppServer Foundation

38 IBM leads with the most complete product family Business Process WebSphere Process Server For customers who want a higher level solution to design, automate and manage composite applications and operational business processes. Built on WebSphere ESB. WebSphere ESB WebSphere Message Broker A new product that delivers an Enterprise Service Bus. Provides Web Services connectivity and data transformation. Built on WebSphere Application Server. ESB WebSphere Application Server A world-class Java EE foundation providing industry-leading levels of availability, scalability, and performance. Increased capabilities / automation A new version of our proven product that delivers an advanced Enterprise Service Bus. Provides universal connectivity and data transformation. Built on WebSphere MQ. WebSphere MQ Provides reliable integration messaging to connect applications and Web services across more than 80 supported platform configurations.

39 What is IBM offering for an ESB 1 WebSphere ESB V7 delivers an Enterprise Service Bus built on top of and leveraging WebSphere Application Server. Facilitates SOA for Web services. Uniquely able to connect to WebSphere MQ networks. 2 WebSphere Message Broker V7 built on top of and leveraging WebSphere MQ. Delivers a universal Enterprise Service Bus facilitating SOA for existing (non-web Services) applications.

40 WebSphere DataPower Software An SOA Appliance Creating customer value through extreme SOA performance and security Skills & Support Simplifies SOA with specialized devices Accelerates SOA with faster XML throughput Helps protect SOA XML implementations WebSphere DataPower redefines the boundaries of middleware extending the SOA Foundation with specialized, consumable, dedicated SOA appliances that combine superior performance and hardened security for SOA implementations

41 WebSphere ESB, WebSphere Message Broker and WebSphere DataPower WebSphere ESB HTTP WebSphere Message Broker HTTP JMS WebSphere MQ Web Services XML WebSphere Adapters Plus the following: JMS WebSphere MQ Web Services XML WebSphere Adapters Web Services (WS) connectivity and data transformation TIBCO Rendezvous Weblogic JMS Biztalk TIBCO EMS JMS MQe Multicast Tuxedo FTP EDI-FACT SonicMQ JMS COBOL HIPAA HL7 Real-time IP Copybook ACORD AL3 Word/Excel/PDF SWIFT FIX ebxml EDI-X.12 MQTT Custom Formats Universal connectivity and data transformation High Throughput Connectivity, data transformation & security WebSphere DataPower HTTP WebSphere MQ Web Services WS-* SLM Security Crypto DataGlue FTP ODBC XML XSLT

42 One Integrated Platform WebSphere ESB V7 is part of the IBM SOA platform The ONLY offering in the industry combining all you need for SOA in ONE integrated platform. WebSphere Process Server v7 WebSphere ESB v7 Service Mediation WebSphere Application Server v7 Service Hosting Java EE/SOA standards Java EE, JMS, HTTP, SOAP, UDDI, XML, WSDL, BPEL, SCA Service-based Process Management

43 The SOA Platform WebSphere Message Broker Plugs into the IBM SOA platform providing high-speed data movement and universal mediation One Integrated Platform enabling non-soa applications to participate as services. WebSphere Process Server v7.0 WebSphere Message Broker V7.0 WebSphere ESB v7.0 WebSphere Application Server v7.0 Java EE/SOA standards Java EE, JMS, HTTP, SOAP, UDDI, XML, WSDL, BPEL, SCA Non-Java OSs Non-WS/Java EE (COBOL, RPG, C++, transports Perl, etc.) (MQI, SCADA, FTP, TIBCO RV, MSMQ) Non-WS/Java EE technologies (Tuxedo, IBM IMS, IBM CICS, etc.) Non-XML formats (EDI, SWIFT, HIPAA, ACORD, Custom formats, etc.)

44 Applying DataPower to the SOA/ESB Design Pattern Partner Zone Demilitarized Zone InterEnterprise Zone WebSphere DataPower XML Security Gateway XS40 Domain Firewall Protocol Firewall Network Infrastructure XML Firewall and Web Services Gateway Enterprise Secure Zone ESB Enterprise Service Bus Message Broker

45 Summary The ESB is a basic requirement of a Service Oriented Architecture An ESB provides mediations which facilitate the connection of services IBM offers a world-class ESB Portfolio WebSphere ESB, WebSphere Message Broker, WebSphere DataPower WebSphere ESB is: A standards-based ESB An integral part of the WebSphere family Executes the mediations of an ESB Is built on the foundations of WebSphere Application Server and WebSphere Integration Developer

46

47

48 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) WebSphere MQ Service Invocation (0:45) Service Gateway (1:00) WSRR Integration (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

49 L01 Basic Mediation Lab Parts 1 thru 4 An IBM DeveloperWorks Workshop

50 L01 Basic Mediation Lab (Parts 1 thru 4) What is this exercise about The objective of this lab is to provide you with an understanding of the IBM WebSphere ESB product and its capabilities. Lab Requirements List of system and software required for the student to complete the lab: WebSphere Integration Developer V7.0 installed WebSphere Enterprise Service Bus V7.0 test environment installed What you should be able to do Create a mediation module using the WebSphere Integration Developer Tooling. Have a fair understanding of the out of box mediation module primitives.

51

52 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) WebSphere MQ Service Invocation (0:45) Service Gateway (1:00) WSRR Integration (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

53 P03 Modules, Service Components, and Primitives An IBM DeveloperWorks Workshop

54 Mediation Module Purpose Protocol switching SOAP, JMS, WebSphere MQ, SCA, HTTP, Adapters Content transformation Aggregation, Logging, Events, Policy Enforcement,

55 Functional Components Mediation Module Exports Imports Components Mediation Flow

56 Modules Contain One or More Components Modules contain wired Service Components Service Components use Business Objects for data Solutions are a collections of Modules Module B Web Client Export Module A Component Component Component Wires Interfaces Import References Business Object Services Export

57 Service Component: Overview This is what I need Java WSDL Port Type Interface Java WSDL Port Type Reference This is how we implement Mediations Java BPEL State Machine Business Rules Human Task Implementation Types Selector Interface Maps

58 The Challenge to Programmer Productivity for SOA Composition S Comervic Arc ponee hite nt c e tur JDBC result set Data JavaBeans Bu JAXB objectsin Obj ess JMS message ect s JCA data EJB transfer bean JAX-RPC POJO EMF data XML DOM etc., etc., etc EJB stateless session bean composition WSJavaBean composition BPEL UML activity diagrams BPEL flows FDML flows WSFL flows XLANG flows etc., etc., etc Invocation JAX-RPC (static and DII) JDBC EJB stateless icesession v t bean r n e JCASe on JMSomp C s WSIF etc., etc., etc

59 Mediation Flow Development Specify source interface Specify target interface Specify mapping between source and target operations

60 Operations need to be transformed Parameters between operation need to be transformed We need to specify how to transform inputs to outputs

61 61 Mediation Flow access to context and protocol information Pre-defined Mediation Functions: Validation and Transformation, Service Registry and Database lookup Split and Aggregation Logging and Events

62 Mediation Flow Primitives.

63 Service Message Object Mediation primitives process messages as SMOs The SMO is an extension of the Business Object (BO) structure It contains: context, message headers, fault details, an array of properties and payload information ServiceMessageObject headers SMOHeader SOAPHeader JMSHeader context correlation transient body shared

64 Service Message Object Accessible During Mapping Provides common representation of content exchanged between services Structured content includes body content (Business Object) and headers Headers include transport-specific data (e.g. JMS headers and properties, SOAP headers, WebSphere MQ headers) Logical structure accessible using XPath and Service Data Object (SDO) application programming interfaces (APIs) SMO is implemented as a specialization of Business Object

65 Service Message Object API Accessible by API (com.ibm.websphere.sibx.smo.*) ServiceMessageObject smo = (ServiceMessageObject)a_type; DataObject context = smo.getcontext() DataObject transient = context.gettransientcontext(); ServiceMessageObject context headers SMOHeader SOAPHeader JMSHeader correlation transient body shared

66 Service Message Object - Context Correlation: Set on request flow and persisted across call out on response flow Transient: Set on individual flows and not persisted Shared: Set on request flow and persisted in request flow

67 Summary Mediations are designed to transform and route data content Primitives are the tools that make that possible There are many provided primitives as well as the ability to design you own custom primitives The SMO API is the programming model for all WebSphere ESB mediations

68

69 L01 Basic Mediation Lab Parts 5 thru 7 An IBM DeveloperWorks Workshop

70 L01 Basic Mediation Lab (Parts 5 thru 7) What is this exercise about The objective of this lab is to provide you with an understanding of the IBM WebSphere ESB product and its capabilities. Lab Requirements List of system and software required for the student to complete the lab: WebSphere Integration Developer V7.0 installed WebSphere Enterprise Service Bus V7.0 test environment installed What you should be able to do Create a mediation module using the WebSphere Integration Developer Tooling. Have a fair understanding of the out of box mediation module primitives.

71 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) WebSphere MQ Service Invocation (0:45) Service Gateway (1:00) WSRR Integration (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

72 P05 Adapters An IBM DeveloperWorks Workshop

73 Objectives Define Adapters Explain importance of Adapters in SOA Enterprise Meta Data Discovery Explain IBM Adapter technologies List reference materials Summarize

74 The Access Challenge Sometimes things just don t fit We may not have a Service interface to all the parts we need

75 Two Faces of an Adapter Adapters acts as a mediator to the asset One face looks like a Service One face looks like a native user End result is SCA artifacts WSDL, XSD, SCA EIS-Specific

76 WebSphere Adapter Capabilities Service oriented approach to enterprise information system (EIS) integration Coarse grained and optimized for exchanges of larger sets of data Embody key principles of loose coupling Encapsulate EIS Business functions and events in the form of Business Objects Common Framework An abstraction from wire protocols, application APIs, or data transformation between domains Consistent configuration, deployment, and administration? Files DB

77 Enterprise Metadata Discovery (EMD) Define a common API that adapters can use to expose their services and business objects to tools for the generation of J2CA based applications. Implementation of the API is a simple extension to the capabilities of the Java EE Connector Architecture (J2CA) resource adapter Tool that drives the discovery of services available on the EIS consistently for all adapters. Single tooling environment that supports development for multiple EIS systems, using multiple Adapters.

78 WebSphere Integration Developer EMD Tooling Enterprise Discovery Import Test & Deploy Configure Wire

79 Artifacts Generated by the EMD Wizard CICS Server CICS Region- DEMO Program ISFREQFL EMD Wizard Import Business Object Interface COBOL source code

80 Two Classes of Adapters WebSphere Adapters Based on JCA standard IBM s Strategic Direction for adapters WebSphere Business Integration Adapters Based on JMS technology Heritage adapter set

81 WebSphere Adapters (JCA) WebSphere Enterprise Service Bus ESB Mediation R.R I WebSphere Adapter EIS

82 WebSphere Adapters (JCA) JCA 1.5 Qualities of Service Transaction Management Assured Event Delivery Connection Management Provides scalability + SCA Security Management End-to-End Java EE Security JCA 1.5 Interface Specifications + SDO Common Client Interface (CCI) Common API for interacting with Resource Adapter Service Provider Interface (SPI) System level contracts between Java EE App server and EIS to provide services (QoS) + EMD + CEI + WebSphere Extensions

83 WebSphere Business Integration Adapters WebSphere Enterprise Service Bus ESB Mediation R.R WebSphere BI Adapter EIS

84 What is a WBI Adapter? The Adapter can be logically divided into three sections The front end, or Application Specific Component, works with the application or the technology. The Adapter can both extract or place data into an application The back end, called the Framework, places data into message queues and receives data from message queues that have been placed by the integration product. Object Discovery Agents (ODA) introspect into EIS to create Business Objects. Application Specific Component Siebel Framework WebSphere Process Server Siebel APIs JMS SiebelAdapter.jar WebSphere Message Broker WebSphere ESB

85 Events and Business Objects Inbound event EIS sends data to the Process Server Outbound event EIS receives data from the Process Server Outbound Inbound Data is represented as Business Objects Event is a Business Object sent to an EIS or received from an EIS

86 WebSphere Adapters - Outbound Customer Updated Module SCA R.R Component I EIS Import Resource Adapter EIS Binding Mediation BPEL POJO etc JCA Container EIS

87 WebSphere Adapters- Inbound Customer Updated Event Triggered Module Resource Resource Adapter Adapter EIS Export Export EIS Binding JCA Container EIS SCA I Component Mediation BPEL POJO etc

88 WebSphere Business Integration (WBI) Adapters in SCA Module Export I SCA Component Mediation BPEL POJO etc JMS IInn bboo uunn dd JMS Bindings R.R WBI Adapter I Import JMS ndd oouun b b t t O Ouu EIS

89 WebSphere Business Integration Adapters Web Services standards Enterprise Applications SAP Oracle E-Business Suite Siebel PeopleSoft Enterprise JD Edwards OneWorld Ariba Buyer IBM Lotus Domino MS Exchange i2 Messaging / Clients JMS WebSphere MQ XMS.NET C++ Java MQe Multicast Real-time IP MQTT Data Sources Technologies JDBC ODBC EJB Files FTP HTTP CORBA COM TCP LDAP Host Systems Data Formats XML COBOL Copybook EDI X.12 EDIFACT SWIFT FIX ACORD HIPAA HL7 NCPDP C header IBM DB2 Oracle IBM Informix MS SQL Server Sybase JDBC ODBC VSAM IMS/DB Teradata CICS IMS/TM COBOL RPG Tuxedo TN3270 TN5250 Batch Sequential files plus hundreds of adapters from IBM business partners

90 WebSphere JCA 1.5 Adapters WebSphere Adapter for CICS External Call Interface (ECI) 1.0 WebSphere Adapter for CICS ECI 1.5 WebSphere Adapter for IMS 1.0 WebSphere Adapter for IMS 1.5 WebSphere Adapter for v7.0 WebSphere Adapter for Flat Files v7.0 WebSphere Adapter for IBM i v7.0 WebSphere Adapter for FTP WebSphere Adapter for JDBC v7.0 WebSphere Adapter for JD Edwards v7.0 WebSphere Adapter for Lotus Domino v7.0 WebSphere Adapter for PeopleSoft v7.0 WebSphere Adapter for SAP v7.0 WebSphere Adapter for Siebel v7.0

91 Adapters All WebSphere JCA Adapters are included in WebSphere Integration Developer for superior out-of-the-box experience All WebSphere Adapters in WebSphere Integration Developer are for development use IN WebSphere Integration Developer Flat File, FTP, JDBC, , IBM i, Lotus Domino, SAP, Siebel, PeopleSoft, JD Edwards, Oracle E-Business Suite The Technology WebSphere Adapters are also entitled for production use Flat File, FTP, JDBC, , IBM i, Lotus Domino The Application Adapters are licensed separately Other features CICS ECI and IMS J2C Connectors CTG no longer bundled in WebSphere Integration Developer! WebSphere Service Registry and Repository Discovery Agent WebSphere Business Integration Adapter Artifact Importer

92 Summary Adapters provide access to existing assets and EISs Two classes of adapter: WebSphere Adapters based on JCA WebSphere Business Integration Adapters based on JMS Seamlessly integrated into the SOA world

93

94 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) WebSphere MQ Service Invocation (0:45) Service Gateway (1:00) WSRR Integration (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

95

96 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) WebSphere MQ Service Invocation (0:45) Service Gateway (1:00) WSRR Integration (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

97 P06 Service Invoke and Custom Primitives An IBM DeveloperWorks Workshop

98 Service Invoke Overview of function Service invoke primitive Invokes a service from within a request or response flow Conceptually similar to the combination of: Callout node Callout response node Callout fault node Associated with: A reference on the module assembly A specific operation on the reference Operation can be request/response or one way Possible to be asynchronous to the mediation flow Asynchronous with callback style of service invocation Resumption of mediation flow upon callback

99 Service Invocation Primitive Invokes a target service from a request or response flow Service must be defined via Reference Three response terminals - Time-out, OK, Error Assembly Diagram Mediation Flow New context area in the SMO contains invocation request/response body content

100 Service Invoke Terminals One input terminal Message type = request message for the operation 0 to n output terminals One output terminal for the response Message type = response message for the operation Does not exist for one way operations One output terminal for timeouts Message type = request message for the operation Only used for asynchronous timeouts Does not exist for one way operations One output terminal for each modeled fault for the operation Message type = fault message for the operation and fault One fail terminal (for unmodeled faults) Message type = request message for the operation

101 Service Invoke Properties Reference name - the name of the service reference which will be used to call the operation. Operation name - the name of the operation called, made available through the reference. Use dynamic endpoint if set in the message header allows endpoints in the SMO TargetAddress header, if present, to override the endpoint. Async timeout specifies the time to wait for a response when performing an asynchronous deferred response invocation. If a time out occurs, the Timeout terminal is fired and it is treated as an unmodeled fault with respect to retry. If set to 0, an immediate response is expected. If set to -1, an infinite wait for response will occur.

102 Service Invoke Retry Properties Retry on dictates the type of fault which if received will trigger a retry. The options available are: Never - operation call is never retried Any fault - operation call is retried on any type of fault Modeled fault - operation call is retried on modeled faults only Unmodeled fault - operation call is retried on unmodeled faults only Retry count sets the number of times a call should be retried. (> 0) Retry delay is the number of seconds to wait between retry attempts. Try alternate endpoints determines if alternate endpoints available in the SMO should be used on retries.

103 Service Invoke Invocation styles Invocation of service uses SCA invocation styles Synchronous Synchronous call made to the service (SCA invoke ) Mediation thread blocked until service returns Asynchronous with deferred response Asynchronous call made to the service (SCA invokeasync ) Mediation thread blocked until response received (SCA invokeresponse ) Async timeout property specifies maximum wait time Asynchronous with callback Asynchronous call made to the service (SCA invokeasyncwithcallback ) Mediation thread continues Anything additional wired on input side of service invoke primitive continues Terminates once all additional processing is completed Callback with response starts new mediation thread Anything wired on output side of service invoke primitive runs on this thread

104 Service Invoke Multiple invokes A flow can have multiple service invoke instances in sequence A series of service invocations Parallelism possible using asynchronous with callback May only have limited practical application A flow can have multiple service invoke instances in parallel

105 Custom Mediation Primitive A custom mediation is the same as any other mediation, only more so. You create the mediation module in the same way Custom Mediation primitive allows you to implement your own mediation logic in Java code. The Custom Mediation primitive combines the flexibility of a user-defined mediation primitive, with the simplicity of a pre-defined mediation primitive. SMO content can be accessed using predefined functions: For example: Object value = smo.get("/headers/properties[1]/value"); Object value = smo.get("/headers/properties.0/value"); String color = smo.getstring("/headers/properties[name=color]");

106 Custom Mediation Primitive By default a custom mediation primitive has one input terminal (in), one output terminal (out), and one fail terminal (fail). You can add more input and output terminals. The input terminals (one or more) are wired to accept a message; the output and fail terminals are wired to propagate the message. Development is done using the Java editor or the visual editor Flow: The input message is passed as the input parameter to the Java code. If the operation returns successfully, the response from the Java code is propagated to an output terminal. If the operation returns unsuccessfully, the fail terminal propagates the original message, together with any exception.

107 Summary WebSphere Enterprise Service Bus comes with a set of basic primitives to build mediation flows without coding Service Invoke primitive allows you to call external services. Custom Mediations allow you to escape out and execute custom code from mediation flow

108

109 Agenda SOA and WebSphere ESB Introduction (1:00) Basic Mediation Lab (0:45) Break (0:15) Service Message Objects (SMOs) & Primitives (0:30) Adapters (0:30) Lunch (0:30) Service Invoke and Custom Primitives (0:30) Choice of Labs (Break in afternoon for 15 Minutes) SCA and WebSphere Process Server Integration (1:00) Service Gateway (1:00) WSRR Integration (0:45) WebSphere MQ Service Invocation (0:45) Sub Flow (0:30) Adapter (0:30) Advanced Mapping (1:00) Custom Mediation (0:30) WrapUp

110 L02 Service Gateway An IBM DeveloperWorks Workshop

111 L02 WebSphere Process Server Integration What is this exercise about? The objective of this lab is to provide you with an understanding of the IBM WebSphere Enterprise Service Bus (ESB) product and its capabilities. Lab Requirements List of system and software required for the student to complete the lab: WebSphere Integration Developer V or higher installed WebSphere Enterprise Service Bus V or higher test environment installed What you should be able to do? Create a mediation module with service gateway mediation using the WebSphere Integration Developer Tooling. Understand the concept of the service gateway and its usage.

112 L03 WebSphere Service Registry and Repository Integration An IBM DeveloperWorks Workshop

113 L03 WebSphere Service Registry and Repository Integration What this exercise is about The objective of this exercise is to provide you with an understanding of the IBM WebSphere ESB product and its capabilities. Specifically, you will create a WebSphere ESB mediation flow that queries WebSphere Service Registry and Repository for service artifacts at runtime. This capability enables a primary ESB use case dynamic routing of business service request to preferred service provider based on policy. Lab Requirements List of system and software required for the student to complete the lab. WebSphere Integration Developer V7.0 installed WebSphere Enterprise Service Bus V7.0 test environment installed WebSphere Service Registry and Repository V7.0 environment installed What you should be able to do Have a fair understanding of how WebSphere Service Registry and Repository interacts with WebSphere ESB. Understand how dynamic routing of business services works.

114 L04 WebSphere MQ and Service Invocation An IBM DeveloperWorks Workshop

115 L04 WebSphere MQ and Service Invocation What this exercise is about Accessing WebSphere MQ queues Calling an external service from within the mediation flow FanOut and FanIn with aggregation Lab Requirements WebSphere ESB WebSphere MQ What you should be able to do Describe the way connections are made to existing WebSphere MQ environments Describe the patter of FanOut and FanIn Explain the usefulness of calling an external service from within a flow Describe how to use the Shared Context to facilitate aggregation of data from disparate services.

116 L05 Adapter An IBM DeveloperWorks Workshop

117 L05 WebSphere Adapters What this exercise is about The objective of this exercise is to provide you with an understanding of the IBM WebSphere ESB product and its capabilities. This exercise details WebSphere Adapter for Flat Files. WebSphere Adapter for Flat Files allows WebSphere ESB or WebSphere Process Server to interact with the file system for inbound or outbound transactions. A file will be placed in a directory, which will generate an event for WebSphere ESB to process. This is an example of an inbound event into WebSphere ESB/WebSphere Process Server from an adapter. A mediation on the ESB will listen for the event and process it. Lab Requirements List of system and software required for the student to complete the lab. WebSphere Integration Developer V7.0 installed WebSphere Enterprise Service Bus V7.0 test environment installed WebSphere Adapter for Flat Files V7.0 What you should be able to do Understand how adapters work in general. Understand how to import them into WebSphere Integration Developer Understand how adapter fit into the SCA environment.

118 L06 Custom Mediation Component An IBM DeveloperWorks Workshop

119 L06 Customer Mediation Components What this exercise is about The objective of this lab is to provide you with an understanding of the IBM WebSphere ESB product and its capabilities. This lab details the custom mediation primitive. Lab Requirements List of system and software required for the student to complete the lab. WebSphere Integration Developer V7.0 installed WebSphere Enterprise Service Bus V7.0 test environment installed What you should be able to do Explain the need for the custom mediation components and how they are architected in SCA.

120 Review, Evaluations & Next Steps An IBM DeveloperWorks Workshop

121 WebSphere ESB Presentations Labs P01 SOA and ESB (0:40) L01 Basic Mediation Lab P 1-4 (0:45) P02 WebSphere ESB Introduction (0:45) L01 Basic Mediation Lab P 5-7 (1:15) P03 SMOs & Primitives (0:30) L02 Service Gateway (0:45) P04 Adapters (0:30) L03 WebSphere Service Registry and Repository Integration (1:00) P05 Service Invoke and Custom Primitives (0:30) L04 WebSphere MQ and Service Invocation (1:30) L05 Adapter (0:30) L06 Custom Mediation Component (0:30)

122 Next Steps Think about your environment, Do you have an ESB today? Is you company planning to move to a SOA? How will you provide messaging services to your SOA based applications? How will you handle process flow, human and automated, short and long running? How will you design, managing and implement all those services? Other WebSphere Proof of Technologies BPM / SOA High level overview of the entire WebSphere BPM suite Modeler In depth view of the WebSphere Business Modeler Monitor In depth view of the WebSphere Business Monitor WebSphere Process Server In depth with the WebSphere Process Server WebSphere Service Registry and Repository In depth view of the WebSphere Service Registry and Repository Fabric In depth view of WebSphere Web Services Fabric Adv. ESB I depth view of the WebSphere Message Broker

123 Reference Materials IBM SG Getting Started with WebSphere ESB v6.0 SG Production Topologies for WebSphere Process Server and WebSphere ESB V6 SG Patterns: SOA Design Using WebSphere Message Broker and WebSphere ESB SG Connecting Enterprise Applications to WebSphere ESB WebSphere ibm.com

124 We appreciate your feedback in order to improve this educational event. Please fill out the survey form.