Running the Graphical Data Mapping Retail sample
The Graphical Data Mapping Retail sample contains a single message flow
with several message transformations that are implemented using graphical
data mapping. Messages are enriched with data from
a database, using parameters from the current message.
How to run the GraphicalDataMappingRetailSample message flow
This scenario uses a simplified sales data feed instead of the TLOG
industry standard, for which a separate product sample is available. In
this scenario, the message flow enriches messages by using
database lookups and message transformation, and creates multiple output
messages from a single input message.
- In the message broker project GraphicalDataMappingRetailSampleApplication, open
GraphicalDataMappingRetailSampleFlow.mbtest under Flow Tests. It contains an XML input
message containing store sales information.
- Click Send message to put the message in the Store Sales In MQInput node queue called GDMRETAILIN.
- The input message is transformed into an XML LoyaltySalesData
message and then put to the loyalty sales queue by the MQOutput node.
- The StockOrder Mapping node generates a CSV StockOrder
message for each StockOrder element in the StockOrderBatch
message, and the messages are then written as separate lines into an output file. The file is stored in the folder that was specified in the MQSI_FILENODES_ROOT_DIRECTORY environment variable during the database setup (as described in Setting up the database).
For example:
- On Windows: c:\MQSIFileOutput
- On Linux: /tmp/MQSIFileOutput
The name of each file is set to a unique value by the Batched Depot Stock Updates node.
Back to sample home