When creating a connection pool with the Administration Console, you are defining the aspects of a connection to a specific database.
Before You Begin
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), javax.sql.XADataSource (global transactions), and java.sql.Driver
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), javax.sql.DataSource (local transactions only), and java.sql.Driver.
The New JDBC Connection Pool (Step 2 of 2) page opens.
If you selected one of the datasource resource types, this field is usually filled in automatically with the class name associated with the resource type and database vendor you chose. If you selected the java.sql.Driver resource type, this field is disabled.
If you selected the java.sql.Driver resource type, this field is usually filled in automatically with the class name associated with the driver and database vendor you chose. If you selected one of the datasource resource types, this field is disabled.
This option is disabled by default.
This value also determines the number of connections placed in the pool when the pool is first created or when the GlassFish 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 300.
The default value is 60,000.
This option is disabled by default.
If not specified, the connections operate with default isolation levels provided by the JDBC driver. By default, this option is not specified.
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. This option is enabled by default.
This setting is only applicable if a transaction isolation level has been specified.
Examples of required properties include database name (URL), user name, and password. The table normally contains properties used by the database vendor. For information on some of the available properties, see Properties Specific to JDBC Connection Pools.
If you do not specify a value for a property, it is removed from the table when you finish creating the connection pool. If you do not want to set a value for a property now, but you want the property to remain in the table so that the value can be set later, type a set of empty parentheses in the Value field:
()
See Also
<para><olink targetptr="task-jdbcresourcetargets">To Edit JDBC Resource Targets </olink></para>