Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 2 - Integration Maps Map Behavior During Execution

Intelligent Business Integration Reference Guide

Map Behavior During Execution

The execution characteristics of a map are determined by the execution

parameters that are configured at design time. However, these map execution

characteristics or map settings can also be overridden at run time.

The behavior of a single map invocation is as follows:

1 The adapters configured for their respective input cards retrieve some of the

input data.

The input data is validated against the respective input cards’ type tree

definition. This ensures that only valid data is passed to the output building

process. It is for this reason that any piece of any of the input data can be

used to build any of the output data. All of the input data is validated and

stored in the map’s workspace before any output data is built. Because the

entire workspace is available to the map when it comes time to build the

output, any portion of the input data can be used, counted, or manipulated to

generate any part of the output data.

2 After the input data has been validated, output objects can be used as inputs

for a subsequent output.

It is possible to create temporary outputs to signify map logic in certain

situations. The Sink adapter can be employed to ensure that the data is not

retained.

By default, the rollback behavior is applied at the entire map thread level.

Therefore, nothing will be committed to output or deleted from input until all

inputs have been successfully validated and all outputs have been written

successfully. A variety of commit and rollback options are available within the

configuration settings of each input and output card. By manipulating these

settings, it is possible to change the map’s default commit and rollback behavior

significantly.