DB2 Connect Version 10.5 for Linux, UNIX, and Windows
Connection management
Connection pooling
Establishing and severing connections to the
database server can be a very resource intensive process that adversely
affects both database server and DB2 Connect™ server performance. To reduce this processing usage, DB2 Connect server products
use connection pooling to maintain open connections to the database
in a readily accessible pool.
Connection concentrator
The connection concentrator reduces the resources
required on DB2® for z/OS® database
servers to support large numbers of workstation and web users. This
function can dramatically increase the scalability of your DB2 for z/OS and DB2 Connect solution while
also providing for fail-safe operation and transaction level load
balancing in DB2 for z/OS data
sharing environments.
Connection pooling and connection concentrator
While connection pooling and connection concentrator seem
to have similarities, they differ in their implementation and address
different issues. Connection pooling helps reduce the processing usage
of database connections and handle connection volume. Connection concentrator
helps increase the scalability of your DB2 for z/OS and DB2 Connect solution by optimizing
the use of your host database servers.
Connection concentrator required with WebSphere MQ Transaction Manager and DB2 for z/OS
When running applications in an IBM® WebSphere® MQ
(formerly known as IBM MQSeries®) environment, WebSphere MQ can act as an
XA-compliant transaction manager, coordinating any distributed, two-phase
commit transactions. When WebSphere MQ
is acting as a transaction manager in this way, and the data sources
are from the DB2 family of products,
there are several configuration requirements.