MapSettings > MapAudit
You can use the MapAudit settings to create and store map audit logs. The audit logs contain information about data audit, execution audit, map settings, and data settings.
MapAudit settings are compiled (as overrides) into the .msl file, which is run by the Launcher.
To enable the audit log
The audit log is created in a file in the map directory or to a location that you specify using the AuditLocation settings.
When you choose Custom for Directory under the AuditLocation setting, enter a file path in Value. The value you enter in FileName determines the audit log file name.
There are three options from which to choose for the audit log filename (): Default, Unique, and Custom. The following table displays the filename outcome of each option.
- Value
- Description
- Default
- The file is automatically assigned an audit log file name (based on the compiled map name) with a .log file name extension.
- Unique
- Generates a unique audit log name in the following format:
Mer_mapname_processkey_mapcounter_hostname.log
Run_mapname_processkey_mapcounter_hostname.log
The prefix "Mer" is used with top-level maps while "Run" is used for run maps.
- mapname
- The executable map name.
- processkey
- Unique value for each process.
- mapcounter
- Unique value for each map instance (within the same process)
- hostname
- The host name of the computer where Transformation Extender is running.
- Custom
- A custom filename. Enter the name in the FileName Value field. Note: Wildcards can be used as long as an input trigger resolves them.