An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

Version 6.0.1

Enhancements

• The driver has been enhanced to comply with FIPS standards for data encryption. As part of this enhancement, the driver was tested with FIPS 140-3 enabled using a Red Hat OpenJDK 21 on a Red Hat Universal Base Image 9 instance. Refer to FIPS (Federal Information Processing Standard) for details.*
  Available: 1/31/2025 | 6.0.1.001709
• The driver has been enhanced to support SAP BW/4HANA and other SAP ODATA V2 services exposed through the SAP Gateway. Refer to Supported SQL statements and extensions for details.
  
• The driver has been enhanced to support CDS views that require parameters. Refer to CDS views for details.
  
• The driver has been enhanced to support HTTP Header authentication for use with the S/4HANA sandbox hosted at https://api.sap.com. Refer to HTTP header authentication (S/4HANA only).
  
• The driver has been enhanced to support a default value of 100000 and maximum value of 1000000 for the connection property WSFetchSize. Refer to WSFetchSize for details.
  
• The driver has been enhanced to set the maximum size of VARCHAR columns within the result set metadata using the MaxVarcharSize connection property. Refer to MaxVarcharSize for details.
  
• The driver has been enhanced to use proxy server settings defined in the JVM system properties by default. If no proxy settings are defined in the connection string or data source, the driver will attempt to use the values of the http.proxyHost and http.proxyPort JVM system properties to connect to the database.

Changed Behavior

• The connection property SpyAttributes has been updated to exclude the attribute load=classname, which was previously used to load the driver specified by the given class name. If a log file name does not include the .log extension, the driver automatically appends it.*
  Available: 10/30/2025 | 6.0.1.001858
• The driver has been updated to remove all sensitive values from the string returned by calling getURL(). You might be impacted if your applications or tests expect these values when calling the function.
• The installer program now requires you to install a JRE that is Java SE 11 or higher before running the installer. In earlier versions, the JRE used by the installer program was included in the product. However, to avoid potential security vulnerabilities, the installer program no longer includes a JRE. Instead, the installer program uses the JRE in your environment to allow for the most secure version of a JRE to be used.*
  Note: This change does not affect the JVM requirements for the driver. For the latest driver requirements, refer to the Product Compatibility Guide.
  Available: 7/3/2024
• The HostName connection property has been renamed ServerName. To support existing configurations, HostName will continue to be supported as an alias for ServerName. Refer to ServerName for details.
  

NOTES, KNOWN ISSUES, AND LIMITATIONS

• Using the driver with IBM SDK Java Edition 8: When using the driver with IBM SDK Java Edition 8, you may encounter one of the following errors:
  • "fatal alert:protocol_version"
  • "Error fetching OData2 service metadata, please check your OData2 end-point"
  To work around these errors, the driver requires IBM SDK Java 8.0 Service Refresh 3 Fix Pack 10 and higher with the JVM option -Dcom.ibm.jsse2.overrideDefaultTLS set to true. This overrides the default TLS setting and uses TLSv1.2 for a successful connection.
• Update and Delete support on services with E-Tag validation: The driver does not support update or delete operations on services that require E-Tag validation. If you execute update or delete operations on a service requiring E-Tag validation, the driver returns a 428 error.
• Services having different relative path not supported in ServiceList: The driver does not connect to services specified by the ServiceList property that have a different relative path than the standard, which is https://<hostname>/sap/opu/odata/sap.
• JDBC Methods: The following notes on JDBC methods apply generally to Progress DataDirect for JDBC drivers. Additional information on driver support for the JDBC API can be found in the "JDBC Support" section of the product user's guide.
  • The DataDirect 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.
  • 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 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.

Version 6.0.0

Features

• Supports SQL read-write access to SAP S/4HANA cloud data source
• Supports JDBC core functions
• Supports the core SQL-92 grammar
  
• Supports SAP S/4HANA data types through data type inference
• Supports Basic authentication
• Supports SSL data encryption
• Supports connection to custom business objects and views via custom services, 
  including custom fields added through SAP S/4HANA UI.
  
• Supports the handling of large result sets with paging and the FetchSize connection property 
• Includes Interactive SQL for JDBC (JDBCISQL). It 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.
  
• Includes the Progress DataDirect S/4HANA Configuration Manager for quick configuration and testing of your driver in a web browser. The tool allows you to: 
  • Generate and edit connection URLs
  • Test connect connection URLs
  • Execute SQL commands for testing
  • Access connection property descriptions and the full product documentation