The drivers implement the following JDBC features:
JNDI for Naming Databases
Connection Pooling
Java Transaction API (JTA)
Note: JTA is only supported by the DB2, Informix, Oracle, OpenEdge, SQL Server, and Sybase drivers.
You can use DataDirect Spy to track JDBC calls made by a running application with any of these features. The com.ddtek.jdbcx.datasource.DriverDataSource class, where Driver is the driver name, supports setting a semi-colon-separated list of DataDirect Spy attributes (see DataDirect Spy Attributes).
Refer to the DataDirect Connect Series for JDBC User’s Guide for more information about configuring data sources.
Example on Windows:
The following example creates a JDBC data source for the DB2 driver, which enables DataDirect Spy.
Note: If coding a path on Windows to the log file in a Java string, the backslash character (\) must be preceded by the Java escape character, a backslash. For example: log=(file)C:\\temp\\spy.log;logIS=yes;logTName=yes.
Using this example, DataDirect Spy would load the DB2 driver and log all JDBC activity to the spy.log file located in the C:\temp directory (log=(file)C:\\temp\\spy.log). In addition to regular JDBC activity, the spy.log file also logs activity on InputStream and Reader objects (logIS=yes). It also includes the name of the current thread (logTName=yes).
Example on UNIX:
The following example creates a JDBC data source for the Oracle driver, which enables DataDirect Spy.
Using this example, DataDirect Spy would load the Oracle driver and log all JDBC activity to the spy.log file located in the /tmp directory (log=(file)/tmp/spy.log). The spy.log file includes the name of the current thread (logTName=yes).