The July 2025 release of Data Ingestion and Replication includes the following changed behavior.
Improved option names for the JDBC driver type in the Db2 for i and Oracle connections
Improvements have been made to he JDBC driver option names in the JDBC Driver field in the Db2 for i Database Ingestion connection and in the Driver Type field in the Oracle Database Ingestion connection to make them clearer and more consistent in format and with the provider's naming. In the Db2 for i Database Ingestion connection, the option names are now Progress DataDirect Db2 JDBC and IBM JTOpen JDBC. In the Oracle Database Ingestion connection, the option names are now Progress DataDirect Oracle JDBC and Native Oracle JDBC. Existing connections that use the older option names will continue to work.
Restriction on dots in streaming ingestion and replication task names
If you edit an existing task that contains a dot (.) in its name, and retain the dot in the name, you cannot save the task. Task names can now include only alphanumeric characters, commas, plus signs, minus signs, spaces, and underscores. Existing tasks with dots in their names will continue to work unless you edit the task names.
Restart checkpoint information stored in the Kafka header
Application ingestion and replication and database ingestion and replication jobs that have a Kafka target now store the restart checkpoint information in the Kafka header. Previously, the checkpoint information was only persisted in the checkpoint file in the Secure Agent.
Newly deployed jobs send the checkpoint information into the Kafka header for each message. The checkpoint information is retrieved from the Kafka header when the job is restarted.
Because of this enhancement, newly deployed jobs that have a Kafka target are not restricted from running on other Secure Agents due to having a Kafka target.