Transforming a Message using ESQL

IBM Integration Bus version 10 presents various techniques to change a message. This scenario is pays attention on message transformation by making use of ESQL.
This use case is based on a sales processing scenario. At the time of a sale, the customer’s name, the code for the product, a description of the product, its category, the unit price, and quantity purchased are documented. Each customer might procure numerous items. A record with all the customer orders is created. The example application transforms the incoming message and create an invoice statement for each customer included in the record.
The messages used for input and output are self-defining XML messages. Each message consists of three parts:
A header, which encloses a count of the number of repetitions of the repeating SaleList structure that follows.
The body, which includes the repetitions of the repeating SaleList structure.
The trailer, which contains the time the message was processed.
The transformation and production of the statement for each customer within a SaleList is achieved with a single message flow.
IBM IBUS Message transformation using ESQL
The message transformation  using ESQL performs the following processing:
Studies a WebSphere MQ message containing an XML payload.
Analyzes the input message and creates an invoice for each customer. This is attained with a single Compute node containing ESQL.
Creates a WebSphere MQ output message containing an XML payload.
IIB 7132011705573410451

Post a Comment


Home item

Blog Archive

Popular Posts

Random Posts

Flickr Photo