The drivers implement the following JDBC features:
JNDI for Naming Databases
Connection Pooling
You can use DataDirect Spy to track JDBC calls made by a running application with either 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").
Note: The following examples are drawn from DB2 and Oracle use cases. However, they inform the implementation of DataDirect Spy for most Progress DataDirect drivers.
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.
DataDirect Spy loads 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.
DataDirect Spy loads the Oracle driver and logs 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).