WebSphere Integration Developer v Mediation Module

Transcription

1 WebSphere Integration Developer v Mediation Module Frank Toth Staff Software Engineer WebSphere Support Technical Exchange

2 Agenda Service Message Object Aggregation Asynchronous call Asynchronous call with deferred response Setting Message Header information Datahandler primitive Type Filter primitive 2 of 37

3 Mediation module Mediation modules are deployable projects that contain mediation flows. They can be deployed on the WebSphere Process Server or the WebSphere Enterprise Service Bus. Mediation primitives, within the flow, process messages as Service Message Objects (SMO). SMOs are enhanced Service Data Objects (SDOs), and the SMO model is a pattern for using SDO DataObjects to represent messages. 3 of 37

4 Service Message Object (SMO) An enhanced business object that includes the message payload and a header. The header contains information about the transport protocol used to invoke a service and mediation exception information. A service message object provides an interface to access and modify message payloads and headers. All SMOs have the same basic structure. The structure consists of a root data object called a ServiceMessageObject, which contains other data objects representing the header, body, attachments, and context data. 4 of 37

5 SMO structure Headers carry header information for different types of messages SMO JMS SOAP MQ HTTP EIS Context - lets mediation primitives pass data that is not part of the message payload, between themselves System defined FailInfo - used to hold runtime exception information PrimitiveContext used for dynamic routing and FanOut primitive DynamicProperty mediation policy information that is used to overwrite prompted properties User defined Transient pass values between mediation primitives, either in request or response flow Correlation pass values from request flow to response flow Shared for data aggregation, one per thread, request or response flow Exceptions for shared context loss: asynch with callback, or ServiceInvoke primitive outside of FanOut/ FanIn User context pass values between SCA components within module Data the actual message data type defined by reference to a Web Services Description Language (WSDL) Attachment Content id Content type Data 5 of 37

6 Aggregation For one customer, retrieve all orders, and for each order, retrieve all shipping information. Populate shared context with retrieved data. Shared context 6 of 37

7 Aggregation Assembly Diagram 7 of 37

8 Aggregation Mediation Flow Request Define Shared Context Create Order Input Retrieve All Orders 8 of 37

9 Aggregation Mediation Flow Response For each Order Create Shipping Input and move Shared context Use XPath Editor to select expression 9 of 37

10 Aggregation XPath editor 10 of 37

11 Aggregation Mediation Flow Response Retrieve all Shipping information Move Shipping information to Shared context, CurrentShipOrder 11 of 37

12 Aggregation XSL Transformation mapping 12 of 37

13 Aggregation Mediation Flow Response Aggregate CurrentShipOrder to all Shipping Orders in Shared context Use XPath Editor to select expression 13 of 37

14 Aggregate XPath editor 14 of 37

15 Aggregation Final result <p:serv icemessageobject xsi:ty pe="p:serv icemessageobject" xmlns:xsi=" xmlns:de=" Demo_lib" xmlns:or="wsdl. xmlns:or_1=" xmlns:p=" "> <context> <shared xsi:ty pe="de:sharedsipmentconf irmation"> <aggregartionshiporder> <order_number>1</order_number> <ship_items> <item_id>1</item_id> <order_quantity >12</order_quantity > <shipped_quantity >5</shipped_quantity > <order_date>december 21, 2009</order_date> <tracking_number>11</tracking_number> </ship_items> <ship_items> <item_id>1</item_id> <order_quantity >8</order_quantity > <shipped_quantity >3</shipped_quantity > <order_date>december 22, 2009</order_date> <tracking_number>22</tracking_number> </ship_items> <ship_items> <item_id>1</item_id> <order_quantity >15</order_quantity > <shipped_quantity >7</shipped_quantity > <order_date>december 23, 2009</order_date> <tracking_number>33</tracking_number> </ship_items> </aggregartionshiporder> <aggregartionshiporder> <order_number>2</order_number> <ship_items> <item_id>2</item_id> <order_quantity >12</order_quantity > <shipped_quantity >5</shipped_quantity > <order_date>december 21, 2009</order_date> <tracking_number>11</tracking_number> </ship_items> 15 of 37

16 Asynchronous call For all customers, create a JMSMapBody type JMS message and put the message on a JMS queue. Each MapEntry corresponds to an element of OneCustomer 16 of 37

17 Asynchronous call Import the predefined JMS message type schema definition into a Library project 17 of 37

18 Asynchronous call Assembly Diagram Select default data format 18 of 37

19 Asynchronous call Mediation Flow One W ay Define Shared Context For each Customer 19 of 37

20 Asynchronous call Mediation Flow One W ay Create JMSBody for each customer and save it in shared context Create JMSBody input from shared context Put a message on JMS queue 20 of 37

21 Asynchronous call Java custom code and XSL Transformation mapping 21 of 37

22 Asynchronous call Final result 22 of 37

23 Asynchronous call with deferred response Put an MQ message on the request queue and get the response message back from the response queue 23 of 37

24 Asynchronous call with deferred response MQ request response Set MQ Header Put a message on MQ queue and get a response back 24 of 37

25 Asynchronous call with deferred response MQHeaderSetter Use the Add button to invoke wizard 25 of 37

26 Setting Message Header information SOAPHeaderSetter Use the Add button to invoke wizard 26 of 37

27 Setting Message Header information Set SOAP Header information 27 of 37

28 Setting Message Header information Custom Java code 28 of 37

29 Datahandler primitive The Data Handler primitive is used to convert an element of a message from a physical format to a logical structure, or from a logical structure to a physical format 29 of 37

30 Datahandler primitive Converts XML input as string into XMLDataType BO 30 of 37

31 Datahandler primitive Make sure to select the right BO definition corresponding to input Schema definition Incorrect selection Correct selection 31 of 37

32 Type Filter primitive Use the Type Filter mediation primitive to selectively route messages 32 of 37

33 Type Filter primitive Filters A list of XPaths, types, and associated terminal names, that define the filtering performed by the mediation primitive Use XPath Editor to select pattern 33 of 37

34 Useful resources WebSphere Business Process Management Info Center v6r2mx/index.jsp XPath Tutorials 34 of 37

35 Additional WebSphere Product Resources Discover the latest trends in WebSphere Technology and implementation, participate in technically-focused briefings, webcasts and podcasts at: Learn about other upcoming webcasts, conferences and events: Join the Global WebSphere User Group 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: 35 of 37

36 Join WebSphere Support Technical Exchange on Facebook! Stay up-to-date on upcoming webcast sessions Suggest future topics Network with other product users And More Suggest program improvements Become a fan now! 36 of 37

37 Questions and Answers 37 of 37