Connect JDBC 5.1.4
- Last Updated: May 8, 2026
- 30 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
DataDirect Connect(R) for JDBC
DataDirect Connect XE (Extended Edition) for JDBC
Release 5.1.4
February 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
CONTENTS
Post-GA Product Announcements
Requirements
Installation Directory
Data Source and Platform Support
Changes since Service Pack 4
Changes for Service Pack 4
Changes for Service Pack 3
Changes for Service Pack 2
Changes for Service Pack 1
Release 5.1.0 Features
Installation/Uninstallation
Available DataDirect Connect Series for JDBC Drivers
Notes, Known Problems, and Restrictions
Using the Documents
DataDirect Connect Series for JDBC Files
Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new
features after the General Availability (GA) of the product. For the latest
updates and enhancements, please refer to the release notes
(https://www.progress.com/datadirect-connectors/whats-new).
Requirements
A supported JVM must be defined on your system path.
The driver requires a Java Virtual Machine (JVM) that is Java SE 8 or higher,
including Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
Installation Directory
The default installation directory for DataDirect Connect for JDBC and
DataDirect Connect XE for JDBC is:
* Windows:
C:\Program Files\Progress\DataDirect\Connect_for_JDBC_51
* UNIX/Linux:
/opt/Progress/DataDirect/Connect_for_JDBC_51
Data Source and Platform Support
For the latest data source and platform support information, refer to the
Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
Changes since Service Pack 4
Signed Installer Packages
-------------------------
Starting June 20, 2022, installer packages signed with a digital signature
will be available for download from OEM FTP. For instructions on verifying
installer package signatures, refer to
https://community.progress.com/s/article/Signed-packages-for-DataDirect-OEMs.
Documentation
-------------
Any product package made available after August 7, 2020 will not include the
HTML help system or user's guide PDF. The Progress DataDirect Connect Series for
JDBC documentation set is available via product and data source tiles from the
Progress Information Hub:
https://docs.progress.com
While the product packages will not include these documentation items, the
installation Help directory will provide an HTML redirect for direct access
to the HTML help.
Timestamp Logging in Spy and JDBC Packet Logs
---------------------------------------------
The driver has been enhanced to include timestamp in the Spy and JDBC packet
logs by default. If required, you can disable the timestamp logging by
specifying the following at connection: For Spy logs, set
spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
set ddtdbg.ProtocolTraceShowTime=false.
Interactive SQL for JDBC
------------------------
Interactive SQL for JDBC (JDBCISQL) is now installed with the product.
JDBCISQL is a command-line interface that supports connecting your driver
to a data source, executing SQL statements and retrieving results in a
terminal. This tool provides a method to quickly test your drivers in an
environment that does not support GUIs.
Java SE 7 Support
-----------------
Java SE 7 has reached the end of its product life cycle and will no longer
receive generally available security updates. As a result, the drivers will no
longer support JVMs that are version Java SE 7 or earlier. Support for
distributed versions of Java SE 7 and earlier will also end, including
IBM SDK (Java Edition).
Kerberos krb5.conf File
-----------------------
The drivers for DB2, SQL Server, Oracle, Sybase and Hive support Kerberos
authentication. These drivers no longer set the java.security.krb5.conf system
property to force the use of the krb5.conf file installed with the driver jar
files in the /lib directory of the product installation directory. For the
latest instructions on configuring the drivers for Kerberos, see the "Notes,
Known Problems, and Restrictions" section below.
Statement Pooling
-----------------
Added the RegisterStatementPoolMonitorMBean connection property. Note that the
driver no longer registers the Statement Pool Monitor as a JMX MBean by default.
You must set RegisterStatementPoolMonitorMBean to true to register the Statement
Pool Monitor and manage statement pooling with standard JMX API calls.
Driver for Apache Hive
----------------------
* The BatchMechanism connection property has been added to the driver. When
BatchMechanism is set to multiRowInsert, the driver executes a single insert
for all the rows contained in a parameter array. MultiRowInsert is the default
setting and provides substantial performance gains when performing batch
inserts.
* The driver has been enhanced to support SSL for Apache Hive 0.13.0 and higher,
incorporating the addition of nine new connection properties.
* The driver's Kerberos functionality has been enhanced to support SASL-QOP
data integrity and confidentiality.
DB2 Driver
----------
* The driver has been enhanced to support the Generic Security Standard (GSS)
plug-in for authentication. The plug-in consists of a set of APIs that you can
implement to customize your authentication requirements and interoperate with
various security methods. You can configure a GSS plug-in using the refreshed
AuthenticationMethod property and the new GSSPluginName and GSSPluginObject
properties.
* The driver has been enhanced to support connecting to a proxy server through
an HTTP connection. HTTP proxy support is configurable with the new
ProxyHost, ProxyMode, ProxyPassword, ProxyPort, and ProxyUser connection
properties.
* The KeepAlive connection property has been added to the driver.
Enabling the KeepAlive property allows the client to keep idle TCP
connections active by periodically passing packets to the server.
* The driver has been enhanced to support Windows Defender Credential
Guard when using Kerberos Authentication.
* The version of Bouncy Castle that ships with the driver has been upgraded to
1.60, which fixes the following security vulnerabilities:
- CVE-2018-1000613
- CVE-2018-1000180
- CVE-2017-13098
This upgrade is available starting in build 5.1.4.000276 of the driver. For
more information on the vulnerabilities resolved by this upgrade, refer
to https://nvd.nist.gov/.
* For DB2 for z/OS, the AlternateID connection property has been modified to set
the name of the schema in the DB2 CURRENT SCHEMA special register instead of
the DB2 CURRENT SQLID special register. AlternateID now sets the name of the
schema in the CURRENT SCHEMA special register for DB2 for i, DB2 for
Linux/UNIX/Windows, and DB2 for z/OS.
* Added support for cursor type OUT parameters for DB2 for Linux, UNIX, Windows
stored procedures.
Greenplum Driver
----------------
* The driver has been enhanced to support a customized version of the Greenplum
COPY command. It provides an additional keyword, LOCALFILE, to allow you to
copy data from or to standard file-system files that are stored anywhere on
your network, not just on the database server. For details, refer to the
DATADIRECT CONNECT SERIES FOR JDBC USER'S GUIDE.
* The driver has been enhanced to leverage server-side prepared statements via
the PrepareThreshold connection property. PrepareThreshold determines the
number of PreparedStatement executions that must occur before the driver
begins using server-side prepared statements. The default value is 0. When set
to a value greater than 1, the driver starts using server-side prepared
statements upon reaching the configured threshold value.
* The driver has been enhanced to support the following data types:
Citext, JSON, and UUID.
* Added support for the Kerberos authentication protocol with the following
connection properties:
- AuthenticationMethod
- ServicePrincipalName
IBM Informix Driver
-------------------
* If you attempt to execute a DatabaseMetadata API with catalogName filter set
as '' (Empty String) against Informix 14.1, the API will return the full list
of objects instead of an empty result. All DatabaseMetadata APIs, such as
getTables() and getColumns(), which support catalogName as filter are
affected by this behavior.
Microsoft SQL Server Driver
---------------------------
The driver has been enhanced to support Azure Active Directory authentication
(Azure AD authentication). Azure AD authentication is an alternative to SQL
Server Authentication that allows administrators to centrally manage user
permissions to Azure SQL Database data stores. To enable Azure AD
authentication, the new ActiveDirectoryPassword value must be specified for the
AuthenticationMethod connection property
(AuthenticationMethod=ActiveDirectoryPassword). In addition, the appropriate
values must be specified for the HostNameInCertificate, User and Password
connection properties. Refer to "Azure Active Directory Authentication" and
"AuthenticationMethod" sections in the user's guide for more information.
MySQL Driver
------------
* The driver has been enhanced to support the sha256_password and
caching_sha2_password authentication plugins.
OpenEdge Driver
---------------
* The driver has been enhanced to support the void cancel() method for SELECT
statements with OpenEdge V12.4 and higher. If a SELECT statement is cancelled
during the first or a subsequent fetch operation, the driver returns a
"query aborted" exception. This method can be used by a thread to cancel a
statement that is being executed by another thread. One or more statements may
be cancelled if the method is called on a statement object that is executing
multiple statements simultaneously and the driver may not return expected
results.
Oracle Driver
-------------
* Support has been added for Oracle Database Vault.
* Support has been added for the Oracle Database Exadata Cloud Service.
* The Oracle driver has been enhanced to support Oracle Wallet SSL
authentication introduced in Oracle 11.1.0.6. The AuthenticationMethod
connection property should be set to either SSL or SSLUIDPassword to allow
SSL authentication when connecting with the driver.
- When AuthenticationMethod=SSL, the driver uses SSL certificate information
to authenticate the client with the server. The Keystore property must
specify the Oracle Wallet that has the SSL certificate information, and the
KeystorePassword property must specify the required password. The User and
Password properties should not be specified. Here is an example connection
URL.
jdbc:datadirect:oracle://server3:1521;SID=ASC;encryptionMethod=ssl;
authenticationMethod=SSL;keystore=.\wallets\keystore.p12;
keystorePassword=Passw0rd
- When AuthenticationMethod=SSLUIDPassword, the driver uses user ID/password
and SSL authentication to connect with the server. The User and Password
properties must be specified, the Keystore property must specify the Oracle
Wallet that has the SSL certificate information, and the KeystorePassword
property must specify the required password. Here is an example connection
URL.
jdbc:datadirect:oracle://server3:1521;SID=ASC;User=test;
Password=secret;encryptionMethod=ssl;authenticationMethod=SSL;
keystore=.\wallets\keystore.p12;keystorePassword=Passw0rd
Note: When Oracle Wallet SSO is used as the keystore or truststore, the
keystorePassword and truststorePassword properties are not required.
* The Oracle driver has been enhanced to support the following new data
integrity algorithms for Oracle 12c and higher:
- SHA256
- SHA384
- SHA512
To use these algorithms, specify their values with the DataIntegrity
connection property (for example, DataIntegrity=(SHA256,SHA384)) and enable
data integrity checks with the DataIntegrityLevel property. For more
information on using these properties, refer to the DATADIRECT CONNECT SERIES
FOR JDBC USER'S GUIDE.
* The LOBPrefetchSize connection property has been added to the driver and is
supported for Oracle database versions 12.1.0.1 and higher. This connection
property allows you to specify the size of prefetch data the driver returns
for BLOBs and CLOBs. With LOB prefetch enabled, the driver can return LOB
meta-data and the beginning of LOB data along with the LOB locater during a
fetch operation. This can have significant performance impact, especially for
small LOBs which can potentially be entirely prefetched, because the data is
available without having to go through the LOB protocol.
PostgreSQL Driver
-----------------
* The driver has been enhanced to support connecting to a proxy server through
an HTTP connection. HTTP proxy support is configurable with the new
ProxyHost, ProxyMode, ProxyPassword, ProxyPort, and ProxyUser connection
properties.
* The driver has been enhanced to support the SCRAM-SHA-256 authentication
method, which uses a hashing mechanism for encrypting passwords to establish
a secure connection with PostgreSQL (v10.0 and higher). This method requires
a Java Virtual Machine (JVM) that is Java SE 8 or higher.
* The driver has been enhanced to support a customized version of the PostgreSQL
COPY command. It provides an additional keyword, LOCALFILE, to allow you to
copy data from or to standard file-system files that are stored anywhere on
your network, not just on the database server. For details, refer to the
DATADIRECT CONNECT SERIES FOR JDBC USER'S GUIDE.
* The driver has been enhanced to support the PostgreSQL COPY command for batch
inserts. When BatchMechanism is set to copy, the driver leverages the
PostgreSQL COPY command for substantial performance gains.
* The driver has been enhanced to support retrieving the values of
auto-generated keys.
* The driver has been enhanced to support the following data types:
Citext, JSON, JSONB, and UUID.
* Added support for the Kerberos authentication protocol with the following
connection properties:
- AuthenticationMethod
- ServicePrincipalName
* The ExtendedColumnMetadata connection property has been added to the driver.
This property determines how the driver returns column metadata when
retrieving results with ResultSetMetaData methods.
Sybase Driver
-------------
* The driver has been enhanced to support Sybase Extended Password Encryption
and Sybase Extended Plus Encrypted Password, which use an asymmetrical key
type. This provides stronger password encryption for the secure transmission
of public key passwords over networks.
* The version of Bouncy Castle that ships with the driver has been upgraded to
1.60, which fixes the following security vulnerabilities:
- CVE-2018-1000613
- CVE-2018-1000180
- CVE-2017-13098
This upgrade is available starting in build 5.1.4.000120 of the driver. For
more information on the vulnerabilities resolved by this upgrade, refer
to https://nvd.nist.gov/.
Changes for Service Pack 4
DB2 Driver
----------
The connection properties RandomGenerator and SecureRandomAlgorithm have been
added to the driver.
* RandomGenerator allows you to specify the type of random number generator
(RNG) the database uses for secure seeding.
* SecureRandomAlgorithm can be used to specify the SecureRandom number
generation algorithm used for secure seeding with implementations of JDK 8
or higher when RandomGenerator is set to secureRandom.
Oracle Driver
-------------
* The SDUSize connection property has been added to the driver. This connection
property allows you to specify the size in bytes of the Session Data Unit
(SDU) that the driver requests when connecting to the server.
* The SupportBinaryXML connection property has been added to the driver. This
connection property enables the driver to support XMLType with binary storage
on servers running Oracle 12C and higher.
* The connection properties RandomGenerator and SecureRandomAlgorithm have been
added to the driver.
- RandomGenerator allows you to specify the type of random number generator
(RNG) the database uses for secure seeding.
- SecureRandomAlgorithm can be used to specify the SecureRandom number
generation algorithm used for secure seeding with implementations of JDK 8
or higher when RandomGenerator is set to secureRandom.
SQL Server
----------
Support for NTLMv2 has been added to the driver. You can use the
AuthenticationMethod connection property to specify that the driver use NTLMv2
authentication when establishing a connection.
Driver for Apache Hive
----------------------
* Support for row-level inserts has been added to the driver.
* The driver has been enhanced to support the Char, Decimal, Date, and Varchar
data types.
CryptoProtocolVersion Connection Property
-----------------------------------------
To avoid vulnerabilities associated with SSLv3 and SSLv2, including the POODLE
vulnerability, this connection property can be used with any of the following
drivers.
- DB2 driver - PostgreSQL driver
- Greenplum driver - Progress OpenEdge driver
- MySQL driver - Microsoft SQL Server driver
- Oracle driver - Sybase driver
Result Set Holdability
----------------------
Support for result set holdability has been added to the driver.
Changes for Service Pack 3
No features introduced.
Changes for Service Pack 2
Driver for Apache Hive
----------------------
Added support for the Kerberos authentication protocol with the following
connection properties:
* AuthenticationMethod
* ServicePrincipalName
Greenplum Driver
----------------
* Added SSL support for Greenplum 4.2, incorporating eight additional connection
properties
* Added SupportsCatalogs connection property, which enables driver support for
catalog calls
* Added four connection properties to handle VARCHAR, LONGVARCHAR, and NUMERIC
data types: MaxVarcharSize, MaxLongVarcharSize, MaxNumericPrecision, and
MaxNumericScale
Oracle Driver
-------------
Modified to support all Oracle 11gR2 Kerberos encryption algorithms
PostgreSQL Driver
-----------------
* Added SupportsCatalogs connection property, which enables driver support for
catalog calls
* Added four connection properties to handle VARCHAR, LONGVARCHAR, and NUMERIC
data types: MaxVarcharSize, MaxLongVarcharSize, MaxNumericPrecision, and
MaxNumericScale
Changes for Service Pack 1
New Drivers
-----------
* Driver for Apache Hive(TM)
- Supports Apache Hive 0.8.0 and higher
- Supports HiveServer1 and HiveServer2 protocols
- Supports Hive distributions:
- Amazon Elastic MapReduce (Amazon EMR)
- Apache Hadoop Hive
- Cloudera's Distribution Including Apache Hadoop (CDH)
- MapR Distribution for Apache Hadoop (MapR)
- Returns result set metadata for parameterized statements that have been
prepared but not yet executed
- Supports connection pooling
- Includes the LoginTimeout connection property which allows you to specify
the amount of time the driver waits for a connection to be established
before timing out the connection request
- Includes the TransactionMode connection property which allows you to
configure the driver to report that it supports transactions, even though
Hive does not support transactions. This provides a workaround for
applications which do not operate with a driver that reports transactions
are not supported.
- The driver provides support for the following standard SQL functionality:
- Create Table and Create View
- Insert
- Drop Table and Drop View
- Batches in HiveServer2 connections
* Greenplum Driver
- Supports Greenplum database versions 4.2, 4.1, 4.0, 3.3, 3.2
- Supports connection pooling
- Supports the DataDirect Bulk Load API
- Includes the TransactionErrorBehavior connection property which determines
how the driver handles errors that occur within a transaction
- Includes the LoginTimeout connection property which allows you to specify
the amount of time the driver waits for a connection to be established
before timing out the connection request
* PostgreSQL Driver
- Supports PostgreSQL database versions 9.2, 9.1, 9.0, 8.4, 8.3, 8.2
- Supports SSL protocol for sending encrypted data
- Supports connection pooling
- Supports the DataDirect Bulk Load API
- Includes the TransactionErrorBehavior connection property which determines
how the driver handles errors that occur within a transaction
- Includes the LoginTimeout connection property which allows you to specify
the amount of time the driver waits for a connection to be established
before timing out the connection request
DataDirect Spy
--------------
Enhanced to throw warning when EnableBulkLoad fails in Oracle, SQL Server,
Sybase, and Salesforce drivers.
Oracle Driver
-------------
Added support for Oracle Wallet
SQL Server Driver
-----------------
* Added ApplicationIntent connection property, which enables you to request
read-only routing and connect to read-only database replicas.
* Enhanced drivers so that transaction isolation level may only be changed
before the transaction is started.
Sybase Driver
-------------
Enhanced AuthenticationMethod connection property to allow for the driver to
send a user ID in clear text and an encrypted password to the server for
authentication.
Release 5.1.0 Features
Oracle Driver
-------------
Support for the Oracle Advanced Security (OAS) data encryption and data
integrity feature, including support for the following new connection
properties:
* DataIntegrityLevel sets the level of OAS data integrity used for data sent
between the driver and database server.
* DataIntegrityTypes specifies one or multiple algorithms to protect against
attacks that intercept and modify data being transmitted between the client
and server when OAS data integrity is enabled using the DataIntegrityLevel
property.
* EncryptionLevel determines whether data is encrypted and decrypted when
transmitted over the network between the driver and database server using
OAS encryption.
* EncryptionTypes specifies one or multiple algorithms to use if OAS
encryption is enabled using the EncryptionLevel property.
Salesforce Driver
-----------------
* The new KeywordConflictSuffix keyword=value pair for the ConfigOptions
property allows you to specify a string that the driver appends to any object
or field name that conflicts with a SQL engine keyword. For example, if you
specify KeywordConflictSuffix=TAB, the driver maps the Case object in
Salesforce to CASETAB.
* The new RefreshSchema connection property specifies whether the driver
automatically refreshes the remote object mapping and other information
contained in a remote schema the first time a user connects to an embedded
database.
Installation/Uninstallation
Installing
----------
A complete installation of both DataDirect Connect for JDBC and DataDirect
Connect XE for JDBC requires approximately 67 MB of hard disk space.
Java SE 8 or higher is required to use DataDirect Connect Series for JDBC.
Standard installations of Java SE on some platforms do not include the jar file
containing the extended encoding set that is required to support some of the
less common database code pages. To verify whether your Java SE version provides
extended code page support, make sure that the charsets.jar file is installed
in the \lib subdirectory of your Java SE installation directory. If you do not
have the charsets.jar file, install the international version of Java SE.
The installer accepts multiple product license keys. For details, refer to the
DATADIRECT CONNECT SERIES FOR JDBC INSTALLATION GUIDE.
Uninstalling on Windows
-----------------------
When you connect with the Salesforce driver, the driver creates multiple local
Salesforce files in the <install_dir>\testforjdbc subdirectory, where
<install_dir> is your product installation directory. If you connect using the
default Salesforce driver URL jdbc:datadirect:sforce://login.salesforce.com,
the names of these files are associated with your user name. For example, if
your user name is test01@xyz.com, the local Salesforce files that are created
would be:
<install_dir>\testforjdbc\ddsforce.log
<install_dir>\testforjdbc\test01.app.log
<install_dir>\testforjdbc\test01.config
<install_dir>\testforjdbc\test01.log
<install_dir>\testforjdbc\test01.properties
<install_dir>\testforjdbc\test01.SFORCE.map
<install_dir>\testforjdbc\test01.SFORCE.native
When you run the Windows uninstaller, these files are not removed. You can
explicitly delete them.
Available DataDirect Connect(R) Series for JDBC Drivers
See http://www.datadirect.com/products/jdbc/matrix/jdbcpublic.htm for a complete
list of supported databases/sources.
DataDirect Connect for JDBC Drivers
-----------------------------------
DB2 (db2.jar)
Informix (informix.jar)
MySQL (mysql.jar)
Oracle (oracle.jar)
PostgreSQL (postgresql.jar)
Progress OpenEdge (openedgewp.jar)
SQL Server (sqlserver.jar)
Sybase (sybase.jar)
DataDirect Connect XE for JDBC Drivers
--------------------------------------
Apache Hive (hive.jar)
Greenplum (greenplum.jar)
Salesforce (sforce.jar)
Notes, Known Problems, and Restrictions
The following are notes, known problems, or restrictions with Release 5.1.4 of
DataDirect Connect Series for JDBC.
GSS plug-in authentication implementation
-----------------------------------------
The following limitations apply to connection pooling through LDAP using GSS
authentication:
* GssPluginObject cannot be specified in the connection URL.
* GssPluginObject cannot be stored in LDAP for pooled connections.
Using Multiple Statements in a Prepared Statement Against PostgreSQL
----------------------------------------------------------------------
The PostgreSQL driver encounters the following issues when it attempts to use
multiple statements in a prepared statement:
* When attempting to call executeBatch(), the driver returns the following
error:
"com.ddtek.jdbc.base.BaseBatchUpdateException: [DataDirect][PostgreSQL JDBC
Driver][PostgreSQL]cannot insert multiple commands into a prepared statement."
* When a function call is a part of any of the statements used in the prepared
statement, the driver returns an error.
* When attempting to execute an Insert or an Update statement against a BYTEA
type column in PostgreSQL versions before 9.0, the driver returns the
following error:
"java.sql.SQLSyntaxErrorException: [DataDirect][PostgreSQL JDBC Driver]
[PostgreSQL]column "c_binary" is of type bytea but expression is of type bit.
You will need to rewrite or cast the expression."
* When attempting to execute setBoolean() against a BOOLEAN type column, the
driver returns the following error:
"java.sql.SQLSyntaxErrorException: [DataDirect][PostgreSQL JDBC Driver]
[PostgreSQL]column "c_boolean" is of type boolean but expression is of type
bit. You will need to rewrite or cast the expression."
Note: To work around this issue, you can use other set methods, such as
setObject() and setString().
DashDB Constraints for Tables
-----------------------------
By default, dashDB does not enforce constraints for tables. As a result, dashDB
will not enforce uniqueness on the new tables, and therefore, incorrect or
unexpected results can occur if table data violates the not-enforced
constraint. If you want to enforce uniqueness, specify the ENFORCED parameter
when creating or altering unique or referential constraints, such as primary
keys and foreign keys.
Configuring the Drivers to Use Kerberos
---------------------------------------
The drivers for DB2, SQL Server, Oracle, Sybase and Hive support Kerberos
authentication. These drivers no longer set the java.security.krb5.conf system
property to force the use of the krb5.conf file installed with the driver jar
files in the /lib directory of the product installation directory. Here are the
latest instructions on configuring the drivers for Kerberos.
To configure a driver for Kerberos:
1. Set the AuthenticationMethod property to kerberos.
2. Specify the JAAS login module in your JAAS login configuration file using
either of the following methods.
- Modify the JDBC_DRIVER_01 entry in the JDBCDriverLogin.conf file to include
the JAAS login module information needed for your environment. The
JDBCDriverLogin.conf file is installed in the /lib directory of the driver
installation directory.
- Specify a JAAS login configuration file directly in your application with
the java.security.auth.login.config system property. The specified login
configuration file must contain the JAAS login module information with the
entry JDBC_DRIVER_01.
NOTE: Whether you are using the JDBCDriverLogin.conf file or another file,
the login configuration file must contain the entry JDBC_DRIVER_01 with JAAS
login module information. The following examples show that the JAAS login
module information depends on your JRE.
* Oracle JRE Example
JDBC_DRIVER_01 {com.sun.security.auth.module.Krb5LoginModule
required useTicketCache=true;};
* IBM JRE Example
JDBC_DRIVER_01 {com.ibm.security.auth.module.Krb5LoginModule
required useDefaultCcache=true;};
3. Set the default realm name and the KDC name for that realm using either of
the following methods. (If using Windows Active Directory, the Kerberos realm
name is the Windows domain name and the KDC name is the Windows domain
controller name.)
- Modify the krb5.conf file to include the default realm name and the KDC
name for that realm. For example, if your Kerberos realm name is XYZ.COM
and your KDC name is kdc1, your krb5.conf file would include the following
entries.
[libdefaults]
default_realm = XYZ.COM
[realms]
XYZ.COM = {kdc = kdc1}
NOTE: During installation, a krb5.conf file is installed in the /lib
directory of the product installation directory. The installed krb5.conf
file contains generic syntax for setting the default realm name and the KDC
name for that realm. If you are not already using another krb5.conf file
for your Kerberos implementation, you can modify it to suit your
environment. However, you will either need to specify the location of this
file using the java.security.krb5.conf system property, or you will need to
add the file to a directory where it may be found by your JVM. See "Keberos
Requirements" in your Java documentation for details on the algorithm used
to locate the krb5.conf file.
- Specify the Java system properties, java.security.krb5.realm and
java.security.krb5.kdc, in your application. For example, if the default
realm name is XYZ.COM and the KDC name is kdc1, your application would
include the following settings.
System.setProperty("java.security.krb5.realm","XYZ.COM");
System.setProperty("java.security.krb5.kdc","kdc1")
NOTE: Even if you do not use the krb5.conf file to specify the realm and
KDC names, you may need to modify your krb5.conf file to suit your
environment. Refer to your database vendor documentation for detailed
information.
4. If using Kerberos authentication with a Security Manager on a Java Platform,
you must grant security permissions to the application and driver. See
"Permissions for Kerberos Authentication" in the User's Guide for examples.
Using the XMLType Data Type with the Oracle Driver
--------------------------------------------------
The default XML storage type was changed from CLOB to BINARY in Oracle 11.2.0.2.
For Oracle 11.2.0.1 and earlier database versions, the driver fully supports the
XML storage type with CLOB. For Oracle 12c and later, you can enable the driver
to support XML storage with BINARY by setting the SupportBinaryXML connection
property to true.
For database versions that fall between Oracle 11.2.0.1 and 12c, columns created
simply as "XMLType" are not supported by the driver. An attempt to obtain the
value of such a column through the driver results in the exception "This column
type is not currently supported by this driver." To avoid this exception, change
the XML storage type to CHARACTER (CLOB) or use the TO_CLOB Oracle function to
cast the column.
Using Kerberos Authentication with DB2 V10.5 for Linux, UNIX, and Windows
-------------------------------------------------------------------------
The DB2 driver cannot authenticate with Keberos due to the behavior of the
DB2 V10.5 for Linux, UNIX, and Windows server. The issue has been opened with
IBM: PMR 06453,756,000.
Stored Procedures and Updates/Deletes for Pivotal HAWQ 1.1
----------------------------------------------------------
The Greenplum driver does not support stored procedures and updates/deletes for
Pivotal HAWQ 1.1.
Oracle 12c Server Issues
------------------------
The following issues were discovered during certification with Oracle 12c.
* Kerberos cannot be configured successfully with Oracle 12c. This server issue
has been reported to Oracle. Oracle has acknowledged the defect:
Bug 17497520 - KERBEROS CONNECTIONS USING A 12C CLIENT AND THE OKINIT
REQUESTED TGT ARE FAILING.
* When using the DataIntegrity (checksums) Oracle Advanced Security feature with
Oracle 12c, the server may unexpectedly drop the connection with the driver.
This server issue has been reported to Oracle: SR 3-7971196511.
* The newPassword connection property is only supported when connecting to an
Oracle server earlier than Oracle 12c. If the newPassword connection property
is specified when attempting to connect to an Oracle 12c server, the driver
throws a "No Matching Authentication Protocol" exception.
Using Bulk Load with PosgreSQL and Greenplum
--------------------------------------------
If the driver throws the error "The specified connection object is not valid for
creation of a bulk load object" while you are attempting to use the DataDirect
Bulk Load API, ensure that postgresql.jar (or greenplum.jar) is listed before
any other DataDirect drivers on your classpath.
Using the SELECT...INTO Statement with the Salesforce Driver
------------------------------------------------------------
The SELECT...INTO statement is supported for local tables only. The source and
destination tables must both be local tables. Creating remote tables in
Salesforce or loading from remote Salesforce tables using SELECT INTO is not
supported. Additionally, the option to create the destination table as a
temporary table does not currently work.
Stored Procedures Not Supported for Database.com
------------------------------------------------
The Salesforce driver incorrectly reports that it supports stored procedures for
Database.com (for example, using DatabaseMetadata.supportsStoredProcedures()).
Stored procedures for Database.com are not supported.
Using Bulk Load with Oracle
---------------------------
For the best performance when using the bulk load protocol against Oracle, an
application can specify "enableBulkLoad=true" and perform its batches of
parameterized inserts within a manual transaction. Using the bulk load protocol
can impact the behavior of the driver. The application should do nothing else
within the transaction. If another operation is performed BEFORE the inserts,
the driver is unable to use the bulk load protocol and will choose a different
approach. If some other "execute" is performed AFTER the inserts, the driver
throws the following exception:
An execute operation is not allowed at this time, due to unfinished
bulk loads. Please perform a "commit" or "rollback".
Using Bulk Load with Microsoft SQL Server 2000 and Higher
---------------------------------------------------------
For optimal performance, minimal logging and table locking must be enabled.
Refer to the following Web sites for more information about enabling minimal
logging:
http://msdn.microsoft.com/en-us/library/ms190422.aspx
http://msdn.microsoft.com/en-us/library/ms190203.aspx
Table locking, a bulk load option, is enabled by default. Table locking prevents
other transactions from accessing the table you are loading to during the bulk
load. See the description of the BulkLoadOptions connection property in the
DATADIRECT CONNECT FOR JDBC USER'S GUIDE for information about enabling and
disabling bulk load options.
Starting the Performance Tuning Wizard
--------------------------------------
* When starting the Performance Tuning Wizard, security features set in your
browser can prevent the Performance Wizard from launching. A security warning
message is displayed. Often, the warning message provides instructions for
unblocking the Performance Wizard for the current session. To allow the
Performance Wizard to launch without encountering a security warning message,
the security settings in your browser can be modified. Check with your system
administrator before disabling any security features.
* The Performance Wizard does not automatically launch from the installer when
the installer is run on the Macintosh operating system. You can start the
Performance Wizard by executing the install_dir/wizards/index.html file.
Executing Scripts (for UNIX Users)
----------------------------------
If you receive an error message when executing any DataDirect Connect for JDBC
shell script, make sure that the file has EXECUTE permission. To do this, use
the chmod command. For example, to grant EXECUTE permission to the
testforjdbc.sh file, change to the directory containing testforjdbc.sh and
enter:
chmod +x testforjdbc.sh
Distributed Transactions Using JTA
----------------------------------
If you are using JTA for distributed transactions, you may encounter
problems when performing certain operations, as shown in the following
examples:
SQL SERVER 7
1. Problem: SQL Server 7 does not allow resource sharing because it cannot
release the connection to a transaction until it commits or rolls back.
xaResource.start(xid1, TMNOFLAGS)
...
xaResource.end(xid1, TMSUCCESS)
xaResource.start(xid2, TMNOFLAGS) ---> fail
2. Problem: Table2 insert rolls back. It should not roll back because it is
outside of the transaction scope.
xaResource.start(xid1, TMNOFLAGS)
stmt.executeUpdate("insert into table1 values (1)");
xaResource.end(xid1, TMSUCCESS)
stmt.executeUpdate("insert into table2 values (2)");
xaResource.prepare(xid1);
xaResource.rollback(xid1);
SQL SERVER 7 and SQL SERVER 2000
1. Problem: Recover should not return xid1 because it is not yet prepared.
xaResource.start(xid1, TMNOFLAGS)
xaResource.recover(TMSTARTRSCAN) ---> returns xid1 transaction
This problem has been resolved in DTC patch QFE28, fix number winse#47009,
"In-doubt transactions are not correct removed from the in-doubt transactions
list".
This Microsoft issue is documented at
http://support.microsoft.com/default.aspx?scid=kb;en-us;828748.
All Drivers
-----------
* The DataDirect Connect Series for JDBC drivers allow PreparedStatement.setXXX
methods and ResultSet.getXXX methods on Blob/Clob data types, in addition to
the functionality described in the JDBC specification. The supported
conversions typically are the same as those for LONGVARBINARY/LONGVARCHAR,
except where limited by database support.
* Calling CallableStatement.registerOutputParameter(parameterIndex, sqlType)
with sqlType Types.NUMERIC or Types.DECIMAL sets the scale of the output
parameter to zero (0). According to the JDBC specification, calling
CallableStatement.registerOutputParameter(parameterIndex, sqlType, scale) is
the recommended method for registering NUMERIC or DECIMAL output parameters.
* When attempting to create an updatable, scroll-sensitive result set for a
query that contains an expression as one of the columns, the driver cannot
satisfy the scroll-sensitive request. The driver downgrades the type of the
result returned to scroll-insensitive.
* The DataDirect Connect Series for JDBC drivers support retrieval of output
parameters from a stored procedure before all result sets and/or update counts
have been completely processed. When CallableStatement.getXXX is called,
result sets and update counts that have not yet been processed by the
application are discarded to make the output parameter data available.
Warnings are generated when results are discarded.
* The preferred method for executing a stored procedure that generates result
sets and update counts is using CallableStatement.execute(). If multiple
results are generated using executeUpdate, the first update count is returned.
Any result sets prior to the first update count are discarded. If multiple
results are generated using executeQuery, the first result set is returned.
Any update counts prior to the first result set are discarded. Warnings are
generated when result sets or update counts are discarded.
* The ResultSet methods getTimestamp(), getDate(), and getTime() return
references to mutable objects. If the object reference returned from any of
these methods is modified, re-fetching the column using the same method
returns the modified value. The value is only modified in memory; the database
value is not modified.
Driver for Apache Hive
----------------------
The following are notes, known problems, and restrictions with the driver.
These restrictions are based on using Apache Hive 0.9; other versions of
Apache Hive will have their own restrictions. You may find a more complete
listing of Apache Hive known issues and limitations for your version of
Apache Hive in the Apache Hive user documentation here:
https://cwiki.apache.org/confluence/display/Hive/Home
* OLTP Workloads
- Note that Apache Hive is not designed for OLTP workloads and does not offer
real-time queries or row-level updates. Apache Hive is instead designed for
batch type jobs over large data sets with high latency.
* Known Issues for Apache Hive
- No support for row-level updates or deletes
- No difference exists between "NULL" and null values
- For HiveServer1 connections, no support for user-level authentication
- For HiveServer1 connections, no support for canceling a running query
- For HiveServer1 connections, no support for multiple simultaneous
connections per port
* HiveQL
- Apache Hive uses HiveQL, which provides much of the functionality of SQL,
but has some limitation syntax differences. For more information, refer to
the Hive Language Manual at
https://cwiki.apache.org/confluence/display/Hive/LanguageManual.
- A single quote within a string literal must be escaped using a \ instead
of using a single quote.
- Numeric values specified in scientific notation are not supported in
Hive 0.8.0.
- Apache Hive supports UNION ALL statements only when embedded in a
subquery. For example:
SELECT * FROM (SELECT integercol FROM itable UNION ALL
SELECT integercol FROM gtable2) result_table
- Subqueries are supported, but they can only exist in the From clause.
- Join support is limited to equi-joins.
* Transactions
- Apache Hive does not support transactions, and by default, the Driver for
Apache Hive reports that transactions are not supported. However, some
applications will not operate with a driver that reports transactions are
not supported. The TransactionMode connection property allows you to
configure the driver to report that it supports transactions. In this mode,
the driver ignores requests to enter manual commit mode, start a
transaction, or commit a transaction and return success. Requests to
rollback a transaction return an error regardless of the transaction mode
specified.
DB2 Driver
----------
* Unlike previous versions of the DB2 driver, the 5.1.0 version of the driver
does not buffer the input stream if a parameter is a BLOB, CLOB, or DBCLOB
type.
* The ResultSetMetaData.getObject method returns a Long object instead of a
BigDecimal object when called on BIGINT columns. In versions previous to
DataDirect Connect Series for JDBC 3.5, the DataDirect Connect for JDBC DB2
driver returned a BigDecimal object.
* Scroll-sensitive result sets are not supported. Requests for scroll-sensitive
result sets are downgraded to scroll-insensitive result sets when possible.
When this happens, a warning is generated.
* The DB2 driver must be able to determine the data type of the column or stored
procedure argument to implicitly convert the parameter value. Not all DB2
database versions support getting parameter metadata for prepared statements.
Implicit conversions are not supported for database versions that do not
provide parameter metadata for prepared statements.
Oracle Driver
-------------
* For database versions prior to Oracle 12c, the newPassword connection property
is supported only when connecting to servers for which the
ALLOWED_LOGON_VERSION parameter is either not specified or is specified with a
value of 8. If the newPassword connection property is specified when
attempting to connect to an Oracle server for which the ALLOWED_LOGON_VERSION
parameter is specified with a value greater than 8, the driver throws a
"No Matching Authentication Protocol" exception. The newPassword connection
property is not supported for Oracle 12c.
* When connecting to Oracle instances running in restricted mode using a
tnsnames.ora file, you must connect using a service name instead of a SID.
* If using Select failover and a result set contains LOBs, the driver cannot
recover work in progress for the last Select statement for that result set.
You must explicitly restart the Select statement if a failover occurs. The
driver will successfully recover work in progress for any result sets that
do not contain LOBs.
* If you install the Oracle driver and want to take advantage of JDBC
distributed transactions through JTA, you must install Oracle8i R3 (8.1.7)
or higher.
* Because JDBC does not support a cursor data type, the Oracle driver returns
REF CURSOR output parameters to the application as result sets. For details
about using REF CURSOR output parameters with the driver, refer to the
DATADIRECT CONNECT SERIES FOR JDBC USER'S GUIDE.
* By default, values for TIMESTAMP WITH TIME ZONE columns cannot be retrieved
using the ResultSet.getTimestamp() method because the time zone information is
lost. The Oracle driver returns NULL when the getTimestamp() method is called
on a TIMESTAMP WITH TIME ZONE column and generates an exception. For details
about using the TIMESTAMP WITH TIME ZONE data type with the driver, refer to
the DATADIRECT CONNECT SERIES FOR JDBC USER'S GUIDE.
* The Oracle driver describes columns defined as FLOAT or FLOAT(n) as a
DOUBLE SQL type. Previous to DataDirect Connect Series for JDBC 3.5, the
driver described these columns as a FLOAT SQL type. Both the DOUBLE type and
the FLOAT type represent a double precision floating point number. This change
provides consistent functionality with the DataDirect Connect Series for ODBC
Oracle driver. The TYPE_NAME field that describes the type name on the Oracle
database server was changed from number to float to better describe how the
column was created.
SQL Server Driver
-----------------
* Microsoft SQL Server 7 and SQL Server 2000 Only: Although the SQL Server
driver fully supports the auto-generated keys feature as described in the
Microsoft SQL Server chapter of the DATADIRECT CONNECT FOR JDBC USER'S GUIDE,
some third-party products provide an implementation that, regardless of the
column name specified, cause the driver to return the value of the identity
column for the following methods:
Connection.prepareStatement(String sql, int[] columnIndexes)
Connection.prepareStatement(String sql, String[] columnNames)
Statement.execute(String sql, int[] columnIndexes)
Statement.execute(String sql, String[] columnNames)
Statement.executeUpdate(String sql, int[] columnIndexes)
Statement.executeUpdate(String sql, String[] columnNames)
To workaround this problem, set the WorkArounds connection property to 1. When
Workarounds=1, calling any of the auto-generated keys methods listed above
returns the value of the identity column regardless of the name or index of
the column specified to the method. If multiple names or indexes are
specified, the driver throws an exception indicating that multiple column
names or indexes cannot be specified if connected to Microsoft SQL Server 7 or
SQL Server 2000.
* In some cases, when using Kerberos authentication, Windows XP and
Windows Server 2003 clients appear to use NTLM instead of Kerberos to
authenticate the user with the domain controller. In these cases, user
credentials are not stored in the local ticket cache and cannot be obtained
by the SQL Server driver, causing the Windows Authentication login to fail.
This is caused by a known problem in the Sun 1.4.x JVM. As a workaround, the
"os.name" system property can be set to "Windows 2000" when running on a
Windows XP or Windows Server 2003 machine. For example:
Dos.name="Windows 2000"
* To ensure correct handling of character parameters, install
Microsoft SQL Server 7 Service Pack 2 or higher.
* Because of the way CHAR, VARCHAR, and LONGVARCHAR data types are handled
internally by the driver, parameters of these data types exceeding 4000
characters in length cannot be compared or sorted, except when using the
IS NULL or LIKE operators.
Documentation Errata in USER'S GUIDE
------------------------------------
* The "Data Types" and "Using Extended Data Types" topics incorrectly
indicate support for Oracle 12c extended capabilities for the VARCHAR2,
NVARCHAR2, and RAW data types. Extended capabilities for these data types are
not currently supported.
Documentation Errata in REFERENCE
---------------------------------
* The "Oracle Driver" topic under the "getTypeInfo()" section incorrectly
indicates support for Oracle 12c extended capabilities for the VARCHAR2,
NVARCHAR2, and RAW data types. Extended capabilities for these data types are
not currently supported.
Documentation
PROGRESS DATADIRECT CONNECT SERIES FOR JDBC DOCUMENTATION SET
-------------------------------------------------------------
The Progress DataDirect Connect Series for JDBC documentation set is available
via product and data source tiles from the Progress Information Hub:
https://docs.progress.com
You can access the online help system directly via the HTML redirect in the
installation Help directory.
DataDirect Connect Series for JDBC Files
When you extract the contents of the installation download package to your
installer directory, you will notice the following files that are required to
install DataDirect Connect Series for JDBC:
Windows: PROGRESS_DATADIRECT_CONNECT_JDBC_5.1.4_WIN.zip
Non-Windows: PROGRESS_DATADIRECT_CONNECT_JDBC_5_1_4.jar
When you install DataDirect Connect Series for JDBC, the installer creates the
following directories and files in the product installation directory (as
determined by the user), represented by INSTALL_DIR.
INSTALL_DIR:
------------
BrandingTool.jar Standalone branding tool (OEM installs only)
BuildAdapters.jar File used to create resource adapters
DDProcInfo.exe Windows executable to start the Processor Information
Utility
DDProcInfo UNIX/Linux script to start the Processor Information
Utility
fixes.txt File describing fixes
jdbcreadme.txt This file
LicenseTool.jar File required to extend an evaluation installation
NOTICES.txt Third-Party vendor license agreements
INSTALL_DIR/DB2/bind:
---------------------
iSeries/*.* Files for explicitly creating DB2 packages on
DB2 for i
LUW/*.* Files for explicitly creating DB2 packages on
Linux/UNIX/Windows
zOS/*.* Files for explicitly creating DB2 packages on z/OS
INSTALL_DIR/Examples/bulk:
--------------------------
Load From File/bulkLoadFileDemo.java
Java source example for bulk loading from a
CSV file
Load From File/load.txt Sample data for the example
Streaming/bulkLoadStreamingDemo.java
Java source example for bulk loading from a
result set
Threaded Streaming/bulkLoadThreadedStreamingDemo.java
Java source example for multi-threaded bulk
loading from a result set
Threaded Streaming/README.txt
Instructions on how to use the
thread.properties file
Threaded Streaming/thread.properties
Properties file for the example
INSTALL_DIR/Examples/connector:
-------------------------------
ConnectorSample.ear J2EE Application Enterprise Archive file
containing the ConnectorSample application
connectorsample.htm "Using DataDirect Connect for JDBC Resource
Adapters" document
graphics/*.* Images referenced by the "Using DataDirect
Connect for JDBC Resource Adapters" document
src/ConnectorSample.jsp Source for the JavaServer Page used to access
the ConnectorSample application
src/connectorsample/ConnectorSample.java
Java source file defining the remote
interface for the ConnectorSample EJB
src/connectorsample/ConnectorSampleBean.java
Java source file defining the home interface
for the ConnectorSample EJB
src/connectorsample/ConnectorSampleHome.java
Java source file containing the
implementation for the ConnectorSample EJB
INSTALL_DIR/Examples/JNDI:
--------------------------
JNDI_FILESYSTEM_Example.java
Example Java(TM) source file
JNDI_LDAP_Example.java Example Java source file
INSTALL_DIR/Examples/SforceSamples:
-----------------------------------
buildsamples.bat Batch file to build the Salesforce example
buildsamples.sh Shell script to build the Salesforce example
ddlogging.properties Logging properties file
runsalesforceconnectsample.bat
Batch file to run the Salesforce example
runsalesforceconnectsample.sh
Shell script to run the Salesforce example
bin/com/ddtek/jdbc/samples/SalesforceConnectSample.class
Java example class
bin/com/ddtek/jdbc/samples/SampleException.class
Java example class
src/com/ddtek/jdbc/samples/SalesforceConnectSample.java
Java source example
INSTALL_DIR/Help/:
------------------
ConnectforJDBCHelp.html HTML redirect to the Connect Series help system
INSTALL_DIR/jdbcisql/:
----------------------
jdbcisql.bat Batch file to start JDBC iSQL
jdbcisql.ini Configuration file for JDBC iSQL
jdbcisql.jar Java program to start JDBC iSQL
jdbcisql.sh Shell script to start JDBC iSQL
INSTALL_DIR/lib:
----------------
db2.jar DB2 Driver and DataSource classes
db2.rar DB2 resource archive file
greenplum.jar Greenplum Driver and DataSource classes
hive.jar Driver for Apache Hive and DataSource classes
informix.jar Informix Driver and DataSource classes
informix.rar Informix resource archive file
mysql.jar MySQL Driver and DataSource classes
mysql.rar MySQL resource archive file
openedgewp.jar Progress OpenEdge Driver and DataSource classes
oracle.jar Oracle Driver and DataSource classes
oracle.rar Oracle resource archive file
postgresql.jar PostgreSQL Driver and DataSource classes
sforce.jar Salesforce Driver and DataSource classes
sqlserver.jar SQL Server Driver and DataSource classes
sqlserver.rar SQL Server resource archive file
sybase.jar Sybase Driver and DataSource classes
sybase.rar Sybase resource archive file
db2packagemanager.jar DataDirect DB2 Package Manager jar file
DDJDBCAuthxx.dll Windows DLL that provides support for NTLM
authentication (32-bit), where xx is the Build
number of the DLL
DDJDBC64Authxx.dll Windows DLL that provides support for NTLM
authentication (Itanium 64-bit), where xx is the
Build number of the DLL
DDJDBCx64Authxx.dll Windows DLL that provides support for NTLM
authentication (AMD64 and Intel EM64T 64-bit), where
xx is the Build number of the DLL
DB2PackageManager.bat Batch file to start the DataDirect DB2 Package
Manager
DB2PackageManager.sh Shell script to start the DataDirect DB2 Package
Manager
JDBCDriver.policy Security policy file listing permissions that must be
granted to the driver to use Kerberos authentication
with a Security Manager
JDBCDriverLogin.conf Configuration file that instructs the driver to use
the Kerberos login module for authentication
krb5.conf Kerberos configuration file
INSTALL_DIR/lib/JCA/META-INF:
-----------------------------
db2.xml DB2 resource adapter deployment descriptor
informix.xml Informix resource adapter deployment descriptor
mysql.xml MySQL resource adapter deployment descriptor
oracle.xml Oracle resource adapter deployment descriptor
sqlserver.xml SQL Server resource adapter deployment descriptor
sybase.xml Sybase resource adapter deployment descriptor
MANIFEST.MF Manifest file
INSTALL_DIR/pool manager:
-------------------------
pool.jar All DataDirect Connection Pool Manager classes
INSTALL_DIR/SQLServer JTA/32-bit:
---------------------------------
instjdbc.sql File for installing JTA stored procedures
sqljdbc.dll File for use with JTA stored procedures
(32-bit version)
INSTALL_DIR/SQLServer JTA/64-bit:
---------------------------------
instjdbc.sql File for installing JTA stored procedures
sqljdbc.dll File for use with JTA stored procedures
(Itanium 64-bit version)
INSTALL_DIR/SQLServer JTA/x64-bit:
----------------------------------
instjdbc.sql File for installing JTA stored procedures
sqljdbc.dll File for use with JTA stored Procedures
(AMD64 and Intel EM64T 64-bit version)
INSTALL_DIR/testforjdbc:
------------------------
Config.txt Configuration file for DataDirect Test
ddlogging.properties Logging properties file
testforjdbc.bat Batch file to start DataDirect Test
testforjdbc.sh Shell script to start DataDirect Test
lib/testforjdbc.jar DataDirect Test classes
INSTALL_DIR/UninstallerData:
----------------------------
resource/*.* Resource files for the Windows
uninstaller
.com.zerog.registry.xml Support file for the uninstaller
InstallScript.iap_xml Support file for the uninstaller
installvariables.properties
Support file for the Windows uninstaller
Uninstall Progress DataDirect Connect (R) and Connect XE for JDBC 5.1 SP4.exe
Windows uninstaller
Uninstall Progress DataDirect Connect (R) and Connect XE for JDBC 5.1 SP4.lax
Support file for the Windows uninstaller
uninstaller.jar Java uninstaller
INSTALL_DIR/UninstallerData/Logs:
---------------------------------
Progress_DataDirect_Connect_(R)_for_JDBC_5.1_SP4_InstallLog.log
Log file created by the Windows installer
INSTALL_DIR/wizards:
--------------------
index.html HTML file to launch the Performance Tuning Wizard
applet
JDBCPerf.jar Jar file containing the classes for the Performance
Tuning Wizard applet
images/*.* Graphic files used by the Performance Tuning
Wizard applet
February 2026
=================
End of README