WebSphere Enterprise Service Bus (ESB): Developing Complex Scenarios Simply

Size: px

Start display at page:

Download "WebSphere Enterprise Service Bus (ESB): Developing Complex Scenarios Simply"

Ariel Charles
6 years ago
Views:

1 IBM Software Group WebSphere Enterprise Service Bus (ESB): Developing Complex Scenarios Simply Andrew Borley Software Engineer 23 November 2010 WebSphere Support Technical Exchange

2 Agenda Brief WebSphere Enterprise Service Bus (ESB) product recap Sample WebSphere ESB scenario Explanation of the scenario implemented as a WebSphere ESB mediation flow. Demonstrating the use of: Promoted Properties Aggregation Dynamic Endpoints Advanced XML Stylesheet Transformation (XSLT) functions WebSphere Support Technical Exchange 2 of 33

3 WebSphere ESB Product Recap WebSphere ESB is part of the IBM Service Oriented Architecture (SOA)/Business Process Management (BPM) stack WebSphere WebSphere Process Server WebSphere ESB Process Choreography, Business Logic Message Transformation, Enrichment, Routing Integration Developer (tooling) WebSphere Application Server J2EE Application Hosting, Supporting Services WebSphere Support Technical Exchange 3 of 33

4 Product Recap Modules & Component Types WebSphere ESB only supports Mediation Modules with these components: Mediation Flows Java TM WebSphere Process Server also supports (Integration) Modules, with these additional components: BPEL (Process) Human Task Rule Group (Business Rules) etc WebSphere Support Technical Exchange 4 of 33

5 Sample WebSphere ESB Scenario WebSphere Support Technical Exchange 5 of 33

6 Stock Purchase Scenario A Wholesaler provides a Stock Purchasing service for customers and uses WebSphere ESB to: Check the incoming message for validity & missing information. Make multiple calls to a separate Stock Control application to reserve each item being purchased. Depending on the order priority (same-day, 48hr or weekly delivery), call out to one of a variety of Dispatch services to send the order. Finally, call an Invoicing service to manage the invoice. WebSphere Support Technical Exchange 6 of 33

7 Stock Purchase Scenario Stock Control Stock Purchase Mediation Client Check Details Acknowledge Order Reserve Stock Send to Dispatch Invoice Same Day Dispatch 48hr Dispatch Weekly Dispatch Invoicing WebSphere Support Technical Exchange 7 of 33

8 Scenario Message Flow Stock Client 1. Submit purchase order E1. Order details incorrect Purchase Mediation Stock Control Dispatch Invoicing E2. Order item not in stock 2. Reserve each order item 3. Dispatch order 4. Order invoicing 5. Return order acknowledgement WebSphere Support Technical Exchange 8 of 33

9 Scenario implemented as a WebSphere ESB Mediation WebSphere Support Technical Exchange 9 of 33

10 The Entire Flow Implemented as a single mediation flow using Subflows to encapsulate each functional block Using Subflows allows each block to be worked on separately and/or in parallel Could break up into multiple mediation flows or request/ response flows WebSphere Support Technical Exchange 10 of 33

11 The Entire Flow Convert the message and call the invoicing service Return order acknowledgement Check message details and add any missing data Call out to the Stock Reservation service once for each item in the order Choose and call out to a specific Dispatch service to dispatch the order Handle failures and fault conditions WebSphere Support Technical Exchange 11 of 33

12 CheckMessage Subflow Use promoted properties to switch on validation and tracing for development/debugging purposes If enabled, validate the incoming Service Message Object (SMO) If enabled, trace out the SMO Use a Message Filter to check the Customer Address field is set in the message If the Address data is missing, use a Database Lookup primitive to retrieve the Address and set it in the SMO If the Customer cannot be found in the Database, break out of the subflow to return a fault message WebSphere Support Technical Exchange 12 of 33

13 CheckMessage Subflow Message Validator and Trace primitive Promoted Properties The Promoted Properties will now be available as properties on the CheckMessageSubflow primitive itself. They need to be promoted again from the subflow primitive to be configurable in the WebSphere ESB Integrated Solutions Console WebSphere Support Technical Exchange 13 of 33

14 CheckMessage Subflow Promoted Properties in the WebSphere ESB Integrated Solutions Console WebSphere Support Technical Exchange 14 of 33

15 ReserveStock Subflow Use the aggregation pattern to call out to a service multiple times for a single input message Fan Out fires it's output terminal once for each Item in the Order Make the call out to the Stock Reservation service Fan In only fires it's output terminal when all Items in the Order have been processed Use an XSLT to copy the single Item into the message body for the call out to the Stock Reservation service Append the results of the call out to the Service Message Object (SMO) shared context If the Stock Reservation Service returns an outofstock or itemnotfound message, break out of the subflow to return these fault messages WebSphere Support Technical Exchange 15 of 33

16 ReserveStock Subflow Fan Out and Fan In primitive properties WebSphere Support Technical Exchange 16 of 33

17 ReserveStock Subflow XSL Transformation WebSphere Support Technical Exchange 17 of 33

18 ReserveStock Subflow Message Element Setter primitive properties WebSphere Support Technical Exchange 18 of 33

19 Dispatch Subflow Use the Endpoint Lookup primitive and WebSphere Service Registry and Repository (WSRR) to dynamically select and call out to one of a variety of Dispatch services An Endpoint Lookup primitive sends a query to WSRR with details about the message and the priority specified in the message by the customer. WSRR returns an appropriate service endpoint which is set in the SMO. Make the call out to the selected Dispatch service based on the service endpoint information set in the SMO WebSphere Support Technical Exchange 19 of 33

20 Dispatch Subflow Endpoint Lookup primitive properties WebSphere Support Technical Exchange 20 of 33

21 Dispatch Subflow Dispatch Services defined in WSRR Console Multiple services are defined in WSRR, each with their own endpoint. Each service has a User-defined property and value added in WSRR, defining a DispatchPriority for this service. This value is matched against the value in the SMO to choose the correct service WebSphere Support Technical Exchange 21 of 33

22 Dispatch Subflow Service Invoke primitive properties WebSphere Support Technical Exchange 22 of 33

23 Invoice Subflow Use the XSL Transformation primitive to convert the message to the format required to call out to a generic Invoicing service An XSL Transform primitive converts the body of the SMO to the format required by the Invoicing service Make the call out to the generic Invoicing service with the converted message WebSphere Support Technical Exchange 23 of 33

24 Invoice Subflow XSL Transformation WebSphere Support Technical Exchange 24 of 33

25 Invoice Subflow XSL Transformation WebSphere Support Technical Exchange 25 of 33

26 Invoice Subflow XSL Transformation WebSphere Support Technical Exchange 26 of 33

27 Invoice Subflow XSL Transformation WebSphere Support Technical Exchange 27 of 33

28 GeneralFailure Subflow Subflow terminals can be set to 'Any message type' meaning they accept any message and thus can be reused multiple times at any point in any flow. Primitives must have their own terminals set to 'Any message type' Trace the SMO out (this primitive may also have it's 'enabled' property promoted) Fail the flow, printing out an exception and rolling back the transaction WebSphere Support Technical Exchange 28 of 33

29 The Entire Flow Convert the message and call the invoicing service Return order acknowledgement Check message details and add any missing data Call out to the Stock Reservation service once for each item in the order Choose and call out to a specific Dispatch service to dispatch the order Handle failures and fault conditions WebSphere Support Technical Exchange 29 of 33

30 Summary Brief WebSphere ESB product recap Sample WebSphere ESB scenario The scenario implemented as a WebSphere ESB mediation flow. Demonstrating the use of: Promoted Properties Aggregation Fan In and Fan Out primitives Dynamic Endpoints Endpoint Lookup primitive Advanced XSLT functions WebSphere Support Technical Exchange 30 of 33

31 Additional WebSphere Product Resources Learn about upcoming WebSphere Support Technical Exchange webcasts, and access previously recorded presentations at: Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Join the Global WebSphere Community: Access key product show-me demos and tutorials by visiting IBM Education Assistant: View a webcast replay with step-by-step instructions for using the Service Request (SR) tool for submitting problems electronically: Sign up to receive weekly technical My Notifications s: WebSphere Support Technical Exchange 31 of 33

32 We Want to Hear From You! Tell us about what you want to learn Suggestions for future topics Improvements and comments about our webcasts We want to hear everything you have to say! Please send your suggestions and comments to: WebSphere Support Technical Exchange 32 of 33

33 Questions and Answers WebSphere Support Technical Exchange 33 of 33

Advanced Integration Services In IBM Business Process Manager

IBM Software Group Advanced Integration Services In IBM Business Process Manager Pratima Ahuja (pratima@us.ibm.com) Software Engineer 09/11/2012 WebSphere Support Technical Exchange Agenda What is an AIS