Data Transformation Engine Intelligent Business Integration Reference Guide

Chapter 2 - Integration Maps Map Behavior During Execution
Intelligent Business Integration Reference Guide
32
There are a number of potential benefits in using Burst mode:
♦ A single map consumes a large quantity of input data, but only a small portion
of that data is needed to build an individual output. Burst mode can be used to
minimize the size of the workspace (an internal index of types present in the
data stream). In some cases, a smaller workspace can increase map
performance.
♦ Coordinating multiple inputs together. For example, the first unit of data for
Input Card 1 must be coordinated with the first unit of data for Input Card 2,
and so forth. If Burst mode is not enabled, one input must then act as a
“driver” and matching outputs must be searched for.
♦ Processing a single logical unit of work at a time. For example, one row from a
database table at a time or one message from a message queue at a time. This
would equate to the Burst mode being enabled with the FetchUnit parameter
set to 1.
TargetRule Settings
TargetRule settings in the output card specify what data is output, how the
output data is routed, and what to do when an error occurs.
The Target card setting specifies the adapter
target for the data produced by the map. The
Command card setting enables additional
adapter-specific parameters to be entered (such
as the queue manager name as when using the
WebSphere MQ adapter, queue name, and other
parameters used to control adapter behavior).
The
OnSuccess
and
OnFailure
card settings, which
work in conjunction with the Scope setting, specify
what the map does with the output data when a map,
burst or card succeeds or fails.
The Retry card setting specifies action to take if
adapter errors occur. For example, if
Retry >
Switch = On
and the source connection fails, the
adapter process is retried at the interval specified
with the
Interval
value up to as many times as
defined with the MaxAttempts setting.