Scenario C: Using a broker as auditor

This scenario demonstrates how to use a broker as an auditor and uses the Message Brokers Toolkit to create message flows and message sets, and to create and deploy broker archive (bar) files. It also involves creating a Configuration Manager and a broker, and inputting instance messages that can contain MQRFH2 headers.

The scenario uses database updates that have been defined using mappings. The broker receives a confirmation for a provisional booking, the message flow inserts a row into a database table representing the confirmation, updates a counter in another table representing the key of the confirmation, and deletes the provisional booking from a third table.

This scenario uses the DataDelete, DataInsert and DataUpdate nodes in the message flow, and requires the following mapping functions:
  • Mapping in DataInsert node
  • Combine input data into single insert
  • Mapping in DataUpdate node
  • Mapping in DataDelete node
  • Bar file to override datasource
The names and values used for message flows, message sets, elements and attributes, and the expressions and code samples are for illustrative purposes only.
Related reference
Message mappings