When creating a connection pool with the Administration Console, you are defining the aspects of a connection to a specific database.
To create a connection pool, you must first install and integrate a driver supporting the JDBC API (JDBC driver). See To Integrate a JDBC Driver.
The following information is required to create the JDBC connection pool. Gather this information before proceeding:
Database vendor name
Resource type, such as javax.sql.DataSource (local transactions only), java.sql.ConnectionPoolDataSource (local transactions, possible performance improvements), and javax.sql.XADataSource (global transactions)
Data source class name
Required properties, such as the database name (URL), user name, and password
The Common Tasks page opens.
The New JDBC Connection Pool (Step 1 of 2) page opens.
Note - You can also access the New JDBC Connection Pool page by expanding the Resources node and the JDBC node, and selecting the Connection Pools node. Then from the Connection Pools page, click New to create a new connection pool.
This is a required field.
Choices include javax.sql.XADataSource (global transactions), java.sql.ConnectionPoolDataSource (local transactions, possible performance improvements), and javax.sql.DataSource (local transactions only).
The New JDBC Connection Pool (Step 2 of 2) page opens.
This field is usually filled in automatically with the class name associated with the resource type and database vendor you chose.
This value also determines the number of connections placed in the pool when the pool is first created or when application server starts. The default value is 8.
The default value is 32.
When the pool scales up and scales down toward the maximum and minimum pool size respectively, it is resized in batches. This value determines the number of connections in the batch. Making this value too large delays connection creation and recycling; making it too small will be less efficient. The default value is 2.
After this time expires, the connection is removed from the pool. The default value is 30.
The default value is 60,000.
Connection validation allows the server to reconnect in case of failure.
The application server can validate database connections in three ways: auto-commit, metadata, and table.
The application server validates a connection by calling the con.getAutoCommit and con.getMetaData methods.
Note - Many JDBC drivers cache the results of these calls. As a result, using these calls might not always provide reliable validations. Check with the driver vendor to determine whether these calls are cached or not.
The application queries the specified database table. The table must exist and be accessible, but no rows are required. Do not use an existing table that has a large number of rows, or a table that is already frequently accessed.
The table name must contain only alphanumeric, underscore, dash, or dot characters.
If this checkbox is deselected, individual connections are re-established only when they are used.
Examples of non-component callers include Servlet Filters.
If not specified, the connections operate with default isolation levels provided by the JDBC driver.
If the Guaranteed checkbox is selected, then all connections taken from the pool have the same isolation level. For example, if the isolation level for the connection is changed programmatically (with con.setTransactionIsolation) when last used, this mechanism changes the status back to the specified isolation level.
Examples of required properties include database name (URL), user name, and password. For information on available properties, see Properties Specific to JDBC Connection Pools.