InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.14: Administering database connections (overview) >
6.6.14.0: Properties of JDBC drivers: WebSphere Application Server >
6.6.14.0.1: Properties of data sources
- Connection timeout
- Specifies the maximum time in seconds that requests for a connection wait if the maximum
number of connections is reached and all connections are in use.
This value must be a positive integer.
- Database Name
- Specifies the name of the database used to store entity bean data.
For example, enter WAS. This would make your data source point to
jdbc:db2:WAS.
- Driver
- Specifies the name of the JDBC driver that this data source is
using.
- Idle timeout
- Specifies the maximum time in seconds that an idle (unallocated) connection can remain
in the pool before being removed to free resources.
This value must be a positive integer.
- JNDI Name, JNDI Binding Path
- The JNDI name for the resource, including any naming subcontexts.
This name is used as the linkage between the platform's binding information
for resources defined in the a client applications deployment descriptor and
actual resources bound into JNDI by the platform.
- Maximum connection pool size
- Specifies the maximum number of connections that can be in the pool. If the maximum
number of connections is reached and all connections are in use, additional requests for a
connection wait up to the number of seconds specified in the Connection timeout
property.
This value must be a positive integer.
- Minimum connection pool size
- Specifies the minimum number of connections in the pool.
This value must be a positive integer.
- Name
- Specifies a name by which to administer the data source.
It is recommended that you enter
a name that is suggestive of the database you will use to store entity bean data,
such as WASDataSource, where WAS is the database name. The JNDI lookup for such
a data source would be jdbc/WASDataSource.
- Orphan timeout
- Specifies the maximum time in seconds that an inactive (but allocated) connection can
remain in the pool before being removed.
This value must be a positive integer.
The administrative server and console can
exhibit odd behavior in response to database URLs that are not valid. When you
use a database URL, ensure you have typed it correctly.
|
|