3. What’s New in 7.5.0

This section describes what’s new in Connext 7.5.0 compared to release 7.3.0 LTS.

RTI® Connext® 7.5.0 is an early access release. See the Connext Releases page on the RTI website for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

3.1. Reduced bandwidth usage for Persistence Service synchronization

This release introduces an improved sample synchronization protocol for redundant Persistence Service instances, ensuring eventual consistency of DDS instances with minimal network usage.

To enable and configure the new protocol, use the <data_synchronization> tag under <persistence_service><synchronization>. For configuration details and guidance, see Synchronizing of Persistence Service Instances in the Connext Core Libraries User’s Manual.

The old synchronization protocol is deprecated. However, if needed you can still use it by setting the tag <synchronize_data> under <persistence_service><synchronization>.

3.2. Option to initialize DomainParticipantFactory when Persistence Service instance is created

This release introduces a new parameter, RTI_PersistenceServiceProperty::initialize_dp_factory, which allows enabling or disabling the initialization of the DomainParticipantFactory when creating a Persistence Service instance using the API RTI_PersistenceService_new.

• When set to DDS_BOOLEAN_TRUE (the default), the Persistence Service will initialize the DomainParticipantFactory from XML if a profile has is_default_participant_factory_profile set to TRUE. This is particularly useful for enabling the use of features such as Monitoring Library 2.0 in Persistence Service without requiring additional programmatic setup.

• If your application has already initialized the DomainParticipantFactory before creating the Persistence Service instance, you may want to set this parameter to FALSE to prevent overwriting any QoS settings previously configured.

See the RTI_PersistenceServiceProperty Struct Reference.

3.3. Deprecations and Removals

This section describes items that are deprecated or removed in 7.5.0, compared to 7.4.0.

Deprecated means that the item is still supported in this release, but will be removed in a future release. Removed means that the item is discontinued or no longer supported.

Any deprecations or removals noted in RTI’s documentation serve as notice under the Real-Time Innovations, Inc., Maintenance Policy #4220 and/or any other agreements by and between RTI and customer regarding maintenance and support of RTI’s software. RTI’s current standard terms and support and maintenance policies are available at https://www.rti.com/terms.

3.3.1. Persistence Service synchronization protocol using <synchronize_data> tag has been deprecated

As a result of the fix for Reduced bandwidth usage for Persistence Service synchronization, the sample synchronization protocol enabled by the <synchronize_data> tag has been deprecated and should not be used. The tag is still available for use by setting the tag <synchronize_data> under <persistence_service><synchronization>; however, using this protocol leads to high bandwidth usage. This is because each Persistence Service instance transmits received data samples to all other Persistence Service instances, regardless of whether those instances have already received the samples.