Data Transformation Engine Resource Adapter Reference Guide

Chapter 8 - Messaging-specific Adapter Information Adapter Transactions

Resource Adapters Reference Guide

Adapter Transactions

Map definitions provide settings to control the scope of messaging adapter

transactions. It is important to understand how connections to messaging systems

are controlled and how this relates to transactional scope.

Transactional Control

Scope is a setting that can be specified for a source or target in a map to

determine transaction commitment. The Scope setting can be one of the

following:

♦ Map

♦ Burst

♦ Card

Connection Management

Connection management results in fewer connections being made to the

messaging system which may improve performance. Existing connections are

reused whenever possible. Two situations exist where connection sharing occurs:

♦ between cards and maps within a map

♦ between multiple maps running serially within the Event Server

In the situation in which connection sharing occurs between cards and maps

within a map, the connection is described as "active" as long as at least one card

or rule is accessing a database and has yet to be committed or rolled back (that

is, there is an active transaction). When all cards or rules complete the database

access, connection is "inactive", but still open.

Messages as a Data Source

The two data source processing modes are: integral mode and burst mode.

For each input card in the map, the mode is set to either Burst or Integral in the

Map Designer Input Card dialog box using the SourceRule > FetchAs setting.

Within a map, some input cards may be in burst mode while others are in integral

mode, indicating that these cards are executed only once.