196 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
7.6 Message flows
In this scenario, we use two message flows, the VerifyCredit message flow and
the OpenAccount message flow, for the ESB function. The enterprise information
systems are also emulated using message flows.
7.6.1 Message set
Both message flows use a message set (Figure 7-28) that contains message
definitions to transform and parse the MRM message structure during the flow.
Figure 7-28 Message set SAM730rr_Bank
The messages are parsed using two physical formats:
? TDS
The TDS format is used to parse and wire messages that are sent to the
enterprise information systems in the VerifyCredit message flow.
? XML
The XML format is used to transform messages for the enterprise information
systems and to parse the SOAP envelope in the OpenAccount message flow.
198 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
The physical format for the t_data type, defined by TDS_SAM730, is used for
proprietary string messages used with Legacy 1. You can see this format by
selecting the t_data type in the message definition file and viewing its properties.
Figure 7-30 shows the TDS_SAM730 physical format.
Figure 7-30 TDS_SAM730 physical format
200 Using IBM WebSphere Message Broker as an ESB with WebSphere Process Server
Two types are defined: t_client and t_nameDomain. Each type defined in this
definition has a different TDS structure and organization. The message is parsed
according to the specification in the message definition and TDS structure
defined by the CSV_SAM730 format (Figure 7-32).
Figure 7-32 CSV_SAM730 physical format
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.