Use this page to set advanced data source properties in the application server. These properties activate and configure services that the application server applies to data sources to customize connections within an application server. These properties do not affect connections within the database.
Specifies the number of statements that can be cached per connection. The application server caches a statement after you close that statement.
If the statement cache is not large enough, useful entries are discarded to make room for new entries. To determine the highest value for your cache size to avoid any cache discards, add the number of uniquely prepared statements and callable statements (as determined by the SQL string, concurrency, and the scroll type) for each application that uses this data source on a particular server. This value is the maximum number of possible statements that can be cached on a given connection over the life of the server. Setting the cache size to this value means you never have cache discards. In general, configure a larger cache for applications with a greater number of statements.
If there is a particular statement that you do not want the application server to cache, configure the statement's poolability hint to false. The application server does not cache a statement if the poolability hint is set to false. The application specifies the statement poolability hints at run time.
In test applications, tuning the statement cache improves throughput from 10% to 20%. However, because of potential resource limitations, this might not always be possible.
Data type | Integer |
Default | Default values depend on the database. Typically, this value is 10. For Informix® versions 7.3, 9.2, 9.3, and 9.4, without the respective latest fixes, the default value must be 0. A default value of 0 means that there is no cache statement. |
When you check this option, the application server detects the existence of access by multiple threads.
Indicates that the exact match on connections retrieved out of the application server's connection pool (the connection pool search criteria does not include a user name and password) cannot exist. Instead, the connection re-authentication is done in the doConnectionSetupPerTransaction() of the DataStoreHelper class. The application server does not provide a connection re-authentication implementation at run time. Therefore, when you check this box, you must extend the DataStoreHelper class to provide implementation of the doConnectionSetupPerTransaction() method where the re-authentication occurs. If you do not complete this process, the application server might return unusable connections. For more information, refer to the API documentation for the com.ibm.websphere.rsadapter.DataStoreHelper#doConnectionSetupPerTransaction method.
When you check this option, the application server allows Java™ messaging service (JMS) to get optimized connections from this data source. This property prevents Java database connectivity (JDBC) applications from sharing connections with container-managed persistence (CMP) applications.
Specifies whether the container tracks cached handles, which are connection handles that an application component holds active across transaction and method boundaries. You can use this property to debug connection problems, but tracking handles can cause large performance overhead during run time.
AdminConfig.modify(myDataSourceVariable, '[[manageCachedHandles "true"]]')
Specifies whether the container issues an entry to the activity log when an application obtains a connection without a transaction context. These are exceptions to the Java Platform, Enterprise Edition (Java EE) programming model connection requirements.
Specifies that the application server does not enlist the connections from this data source in global or local transactions. Applications must explicitly call setAutoCommit(false) on the connection if they want to start a local transaction on the connection, and they must commit or rollback the transaction that they started.
Specifies that the application server uses the error mapping facility that is defined in the data store helper to identify errors. The application server does not replace exceptions that are thrown by the JDBC driver with exceptions that are defined in the error map of the data store helper.
Specifies that the application server uses the error mapping facility that is defined in the data store helper to identify errors, and the application server will replace the exceptions that are thrown by the JDBC driver with exceptions that are defined in the error map of the data store helper.
Specifies whether the connection manager tests newly created connections to the database.
Specifies the number of times you want to retry making the initial connection to a database after the first pretest operation fails.
If you select Validate new connections, this option specifies the length of time, in seconds, that the application server waits before retrying to make a connection if the initial attempt fails.
Specifies whether the connection manager tests the validity of pooled connections before returning them to applications.
If you select Pretest existing pooled connections, this option specifies the length of time, in seconds, to allot to the JDBC driver for validating a connection.
Specifies that the application server will use the JDBC driver to validate the connections. The JDBC provider must support JDBC 4.0 or greater to use this option.
Specifies an SQL statement that the application server sends to the database to test the connection. Use a query that is likely to have low impact on performance.
Specifies that the application server will use the get/use/close/connection pattern. This allows connection pooling for the application server to share connections that are in the same transaction. This optimization pattern allows one connection to be shared during a transaction even when connections use different connection properties.
The heterogeneous pooling feature allows you to extend the data source definition so that you can specify different custom properties or allow applications to override non-core properties for the data source.
Specifies the amount of time, in seconds, between retries for automatic client reroute.
Specifies the maximum number of connection retries that are attempted by the automatic client reroute function if the primary connection to the server fails. The property is only used when Retry interval for client reroute is set.
host1,host2
5000,50001
Specifies the JNDI name that is used to bind the DB2 client reroute server list into the JNDI name space. The DB2 database server will use this name to look up the alternate server name list when the alternate server information is not already in memory. This option is not supported for type 2 data sources.
Used with test connection only. When set to true, the Client reroute server list JNDI name will be unbound from the JNDI name space after a test connection is issued.