Use this page to set advanced properties for your data source. These properties activate and configure services that the application server applies to data sources to customize how connections are used within the application server. These properties do not affect how connections are used by the database.
Specifies the number of statements that can be cached per connection. WebSphere Application Server caches a statement after the user closes it.
You can also use the Tivoli Performance Viewer
to minimize cache discards. Use a standard workload that represents a typical
number of incoming client requests, use a fixed number of iterations, and
use a standard set of configuration settings. Note: The higher the
statement cache, the more system resources are delayed. Therefore, if you
set the number too high, you could lack resources because your system is not
able to open that many prepared statements.
In test applications, tuning the statement cache improved throughput by 10-20%. However, because of potential resource limitations, this might not always be possible.
Data type | Integer |
Default | Depends on the database. Most are 10. Informix versions 7.3, 9.2, 9.3, and 9.4, without the respective latest fixes, must be 0. A default of 0 means there is no cache statement. |
If checked, the application server detects the existence of access by multiple threads.
If checked, there cannot be an exact match on connections retrieved out of the WebSphere Application Server connection pool (that is, connection pool search criteria do not include user name and password). Instead, the reauthentication of connection is done in the doConnectionSetupPerTransaction() of the DataStoreHelper class. Note that WebSphere Application Server runtime does NOT provide connection reauthentication implementation. Therefore, when this box is checked you MUST extend the DataStoreHelper class to provide implementation of the doConnectionSetupPerTransaction() method where the reauthentication takes place. Failure to do that results in wrong connections being handed out to users. For more information, refer to the API documentation for com.ibm.websphere.rsadapter.DataStoreHelper#doConnectionSetupPerTransaction(...).
Connection reauthentication can help improve performance by reducing the overhead of opening and closing connections, particularly for applications that always request connections with different user names and passwords.
If checked, the application server allows JMS to get optimized connections from this data source. This property prevents JDBC applications from sharing connections with CMP applications.
If checked, the application server tries to connect to this data source before it attempts to send data to or receive data from this data source. If you select this property, you can specify how often, in seconds, the application server retries to make a connection if the initial attempt fails.
When PreTest existing pooled connections is checked, use this property to specify how long, in seconds, the application server waits before retrying to make a connection if the initial attempt fails.
Specifies the string of data that the application server sends to the database to test the connection. Because the pretest operation is designed to test only that a connection makes a round trip to and from the database server, use a simple, low-impact query. A good choice for a PreTest SQL string is a generic query that has minimal potential impact on performance of the application server.
Data type | Integer |