Database connection management
Connection management results in fewer connections being made to the database, which may improve performance. The IBM Transformation Extender engine reuses existing connections whenever possible. With global transaction management for those adapters able to take advantage of this functionality, connections have an even bigger role in maintaining data integrity. For more information about global transaction management, see the Global Transaction Management documentation.
There are two situations in which connection sharing occurs:
- between cards and maps within a map
- between multiple maps running serially within the Launcher
When connection sharing occurs between cards and maps within a map, the connection is described as active as long as there are one or more cards or rules that access a database and that have yet to be committed or rolled back. (For example, an active transaction exists.) When there are no such cards or rules, the connection is inactive, yet still alive.
When using a DBLOOKUP, DBQUERY, GET or PUT function, the setting defaults to Map when the map setting is set to Integral. The setting will change to Burst when the map setting is set to Burst; the setting is always Rollback.