The following table describes the functionality for managing resource connections and transactions. Select the functionality according to the purpose of the system. For details about the functionality, see the reference location.
Table 1-3 Correspondence between the functionality for managing the resource connections and transactions and the purpose of a system
Functionality name | Purpose of the system | Compliance with Java EE standards | Reference location | |||||
---|---|---|---|---|---|---|---|---|
Reliability | Performance | Operation and maintenance | Expansion | Others | Standard | Expanded | ||
Connection pooling | N | Y | N | N | N | Y | Y | 3.14.1 |
Functionality available with connection pooling | N | Y | N | N | N | N | Y | 3.14.2 |
Connection sharing and association | N | Y | N | N | N | Y | N | 3.14.3 |
Statement pooling | N | Y | N | N | N | N | Y | 3.14.4 |
Light transaction | N | Y | N | N | N | N | Y | 3.14.5 |
In-process transaction service | N | Y | N | N | N | Y | N | 3.14.6 |
DataSource object caching | N | Y | N | N | N | N | Y | 3.14.7 |
Optimizing container management sign-on in DB Connector | N | Y | N | N | N | N | Y | 3.14.8 |
Detecting connection errors | Y | N | N | N | N | Y#1 | Y#1 | 3.15.1 |
Waiting to acquire connections in the case of connection depletion | Y | N | N | N | N | N | Y | 3.15.2 |
Retrying to acquire connections | Y | N | N | N | N | N | Y | 3.15.3 |
Displaying the connection pool information | Y | N | N | N | N | N | Y | 3.15.4 |
Clearing the connection pool | Y | N | N | N | N | N | Y | 3.15.5 |
Automatically closing a connection | Y | N | N | N | N | Y | N | 3.15.6 |
Connection sweeper | Y | N | N | N | N | N | Y | 3.15.7 |
Transaction timeout and statement cancellation | Y | N | N | N | N | Y | N | 3.15.8 |
Transaction recovery | Y | N | N | N | N | Y | N | 3.15.9 |
Issuing of SQL statements for troubleshooting | N | N | Y | N | N | N | Y | 3.15.10 |
Automatic closing of objects | Y | N | N | N | N | Y | N | 3.15.11 |
Managing the resource adapter life cycle #2 | N | N | N | N | N | Y | N | 3.16.1 |
Managing the resource adapter work #2 | N | N | N | N | N | Y | N | 3.16.2 |
Message in-flow #2 | N | N | N | N | N | Y | N | 3.16.3 |
Transaction in-flow #3 | N | N | N | N | N | Y | N | 3.16.4 |
Looking up Administered objects #2 | N | N | N | N | N | Y | N | 3.16.5 |
Specifying multiple connection definitions #2 | N | N | N | N | N | Y | N | 3.16.6 |
Connection pool clustering functionality (temporary stop, restart, and status display of the connection pool) | Y | N | N | N | N | N | Y | 3.17 |
Resource connection test | N | N | Y | N | N | N | Y | 3.18 |
Functionality for operations in a firewall environment | N | N | Y | N | N | N | Y | 3.19 |
Note: The functionality for which Y is specified in both Standard and Expanded columns of the Compliance with Java EE standards column indicates that the Application Server-specific functionality has been expanded to the Java EE standard functionality. The functionality for which Y is specified only in the Expanded column indicates the Application Server-specific functionality.
#1: In the case of Connector 1.0, Expanded. In the case of Connector 1.5, Java EE standards.
#2: This functionality can be used only when you use a resource adapter compliant with the Connector 1.5 specifications.
#3: This functionality can be used only when you use the TP1 inbound adapter from the resource adapters compliant with the Connector 1.5 specifications.