Data Transformation Engine Map Designer Reference Guide

Chapter 16 - Map Audit Mapping from the Audit Log
Map Designer Reference Guide
250
The audit log file is created as specified on the next map execution. After you run
a map, the audit log file can be viewed on the Audit Log tab in the Organizer or
from a text file (map_name.log) in the map directory.
Mapping from the Audit Log
Mapping information from the audit log can provide useful performance statistics
and information about the content of your data. For mapping purposes, the
audit_2.mtt type tree provided in the examples directory defines the audit log
data objects.
The format of the audit log is XML-based to enable use with other applications.
The audit log is defined as a series of MercatorMapAudit elements. Each
MercatorMapAudit element represents the log data for one map instance. You
can get audit data for many map instances when the AuditLocation map setting
for FileName > Action = Append.
The compositional view of the MercatorMapAudit element in the input card
shown below displays the sequence of the information in the audit log.
If the
B
urstAudit > Data
map setting is
ON
,
DataLog i
n
formation appears for each burst.
If the
B
urstAudit > Execution
map
setting is ON, ExecutionLog elements
appear for each burst.
If selected,
M
apSettings
information
follows the ExecutionSummary.
DataSettings appear last.
If the
S
ummaryAudit > Execution
map
setting= ON, ExecutionSummary
information follows the
Burst(s)
ExecutionSummary in the Audit_2.mtt Type Tree
The audit log is created for a specific map. During map execution, after all bursts
complete, the status of the map is summarized in the ExecutionSummary. The