These release notes provide enhancements, changed behavior, and resolved issues for the Hybrid Data Pipeline Server. Server version information can be obtained from the Hybrid Data Pipeline Web UI by selecting About from the help dropdown.
Note: For the latest data source and platform support information, refer to the Product Compatibility Guide.
Hybrid Data Pipeline has been enhanced to include an SBOM file. The file uses an SPDX format with a _SPDX.json suffix, for example, PROGRESS_DATADIRECT_HDP_<component>_5.0.0.<build-number>_SPDX.json. The SBOM files are located at the same level as the installers. Henceforth, this file is available for Hybrid Data Pipeline releases.
SQL statements exceeding 2000 characters were not logged in SQLAudit due to column size limitations, creating a critical audit and security gap.
Intermittent service hangs on a single node required manual restarts, caused by SQLTransactionRollbackException during concurrent DELETE operations.
Incomplete data was retrieved from JDBC SAP S/4HANA driver where result set was limited (~250K rows) and varied based on WSFetchSize configuration.
Microsoft SQL Server JDBC connection using Active Directory Service Principal authentication failed due to issues with loading msal4j and third-party dependencies, impacting all drivers relying on external libraries for authentication.
See Hybrid Data Pipeline known issues for details.
Hybrid Data Pipeline has been enhanced to support correlated logging. Correlated logging enables you to track and relate activity across Hybrid Data Pipeline and client components by tagging each request with a unique correlation or trace ID. For details, refer to Correlated logging.
Hybrid Data Pipeline now supports Kerberos authentication for SQL Server connections. Hybrid Data Pipeline must be configured to use SQL Server Kerberos during deployment. For details, refer to Kerberos authentication for Microsoft SQL Server.
The Apache Tomcat server used to support the operation of the Hybrid Data Pipeline server has been upgraded from version 9.0.107 to version 11.0.10.
The Bouncy Castle Provider used to support FIPS 140-2 compliant cryptography has been upgraded from version 1.78 to version 2.0.0.
A JRE is no longer included in the product package. For installation of the Hybrid Data Pipeline server, a JVM must be installed on the host machine and defined on the system path. During installation, you may select this JVM or a different JVM for runtime operation of the server. For more information about product requirements, deployment, and configuration, refer to the Deployment Guide. For upgrade information, refer to Upgrading from Hybrid Data Pipeline 4.6 to 5.0 in the Deployment Guide.
Modifications of the JVM used with the Hybrid Data Pipeline server are no longer required.
Hybrid Data Pipeline has dropped support for OData Version 2. OData Version 2 data sources must be replaced with OData Version 4 data sources. For upgrade information, refer to Upgrading from Hybrid Data Pipeline 4.6 to 5.0 in the Deployment Guide. For information about OData connectivity, refer to Configuring OData connectivity in the User's Guide.
The SAP HANA data store is no longer supported and has been removed.
See Hybrid Data Pipeline known issues for details.