Specific map and type tree settings

Important map and type tree settings that are used in the examples are of particular importance for running with the MT and MX Generic Envelope service.

Burst
The burst concept deals with the scope of the data that is processed in one run of the map. Generic Envelope service example maps are set to execute in burst mode.
Audit settings
Audit settings enable an map to generate data audit information that can be used by the Generic service in business process reports.
Restart
The use of a restart flag allows a IBM Transformation Extender map to continue to attempt to process remaining transactions after an invalid transaction is found in the input file.
Custom MT type tree
On the Generic Envelope service MT example, the Generic Envelope service expects that the resulting file of the transformation map contains only SWIFT MT block 4 content, without any header or trailer information.

Parent topic: Design considerations for the MT and MX Generic Envelope and Deenvelope examples