Large message handling

When creating ITX maps to handle very large files, consideration should be given to the fact that ITX may exceed its memory capability for processing the file, that the database unit of work size could be very large, and if parallel processing is required, these factors could be multiplied.

For file sizes of over 1000 messages, the use of the PUT WIRE function in ITX should be considered to handle the chunking of inbound messages.

For much larger files, consideration should be given to Fragmentation within FTM, or alternatively, configuring a dummy Source in the message collection passed to ITX, along with the file name in the extendedCfg of the Config – to enable the ITX map to read the file from the file system itself.

For an outbound map, consideration should be given to limiting the size of the OutMapper document sent to the ITX map by minimizing the number of fields returned by the outbound Object Selectors defined in the Finite State Machines.

Outbound Fragmentation should also be considered for very large outbound Physical Transmissions, with a de-fragmentor developed in a message flow and linked by the Post Mapper message flow hook in the Outbound ITX Integration flow.