Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 3 - Methods of Execution Event-Driven Execution Model
Intelligent Business Integration Reference Guide
46
Audit and Transaction Logging Example
The totally flexible architecture of Mercator products allows the design and
development of sophisticated transaction and audit logging using standard
functionality. This is supported by the complete range of resource adapters and
the many tools available in the complete line of Mercator products.
Maps are transactional processes and each map can be configured to have its own
error detection and recovery procedures, as well as auditing capability. The
resulting audit logs themselves can be mapped, as input data, to dedicated
execution logging, error logging, and exception handling routines.
Typically, audit and transaction logging processing is achieved by designing re-
usable map systems to process audit logs resulting from map execution. The
following is an example of this type of functionality:
♦ The map component, Read Audit is configured to automatically be triggered
by the arrival of audit log files generated by the main map execution activity.
♦ Outputs 1 and 2 (TransmissionLog and ExecutionHistory) are intermediate
output formats inside the map, and are not sent to an external destination.
Their output is re-used in outputs 3 and 4 (ErrorLog and
ExecutionHistoryDB).