2.2.2.5. RTI Infrastructure Services

2.2.2.5.1. Use <domain_participant_qos> tag instead of <participant_qos> tag to be compliant with DDS-XML specification

In Connext 7, the following Infrastructure Services products now allow use of the <domain_participant_qos> tag in place of the <participant_qos> tag: Routing Service, Recording Service, Persistence Service, and Cloud Discovery Service. This change was already made to XML-Based Application creation and QoS profiles in the Core Libraries in 6.1.0. (See Section 3.2.1.5.) Now the mentioned Infrastructure Services have also applied the change. This change was made to the schema file rti_service_common_definitions.xsd and its included files to make them compliant with the DDS-XML specification.

Although the <participant_qos> tag is still supported for backward compatibility, you should transition to the new tag, <domain_participant_qos>.

2.2.2.5.2. Removals in Cloud Discovery Service

2.2.2.5.2.1. <refresh_period> tag removed and replaced by new tags to configure announcement resends

The <refresh_period> tag from previous releases has been replaced by the new tags described below. The <refresh_period> is still present in the XSD, and Cloud Discovery Service logs a warning if that tag is parsed; however, the value of <refresh_period> no longer influences the operation of Cloud Discovery Service.

Using the following new mechanism in place of <refresh_period> allows for higher efficiency in bandwidth usage without sacrificing discovery speed:

<forwarder>
    <event>
        <new_or_update_participant_announcements>
        </new_or_update_participant_announcements>

        <min_new_or_update_participant_announcements_period>
        </min_new_or_update_participant_announcements_period>

        <max_new_or_update_participant_announcements_period>
        </max_new_or_update_participant_announcements_period>
    </event>
</forwarder>

This new mechanism enables the forwarder to resend an announcement a set number of times with a random interval between each resend. The random interval occurs within the range determined by <min_new_or_change_participant_announcements> and <max_new_or_change_participant_announcements>.

For further details on these new fields, see Forwarder, in the RTI Cloud Discovery Service documentation.

2.2.2.5.2.2. domain_id_info_seq field in DatabasePeriodic type used in monitoring removed

The @optional sequence<DomainIdInfo> domain_id_info_seq field in the DatabasePeriodic type used for Monitoring, in RTI Cloud Discovery Service, and defined in CdsMonitoring.idl, has been removed.

You will not be able to use your CdsMonitoring.idl file from your release 6.1.2 or earlier application to subscribe to monitoring data published by your Connext 7 application, and vice versa. If you have Cloud Discovery Service in both Connext 7 and a previous release, you will need to create different DataReaders for each monitoring Topic for each release.

2.2.2.5.3. Persistence Service

2.2.2.5.3.1. Durable writer history, durable reader state, and Persistence Service no longer support external databases

See Section 2.2.2.1.1 for details.

2.2.2.5.3.2. Incompatible persistent storage (database) format

In release 7, the schema of the persistent storage files and tables created by Persistence Service to store DDS samples and instances has changed. Therefore, you cannot use the files and/or tables generated with previous releases of Persistence Service with Connext 7. If you have this requirement, contact RTI Support at support@rti.com.

2.2.2.5.3.3. Default journal_mode and synchronization values have changed

In release 7, the default values for the following configuration parameters in Persistence Service have changed:

• <journal_mode>: changed from DELETE to WAL

• <synchronization>: changed from OFF to NORMAL

This change provides the best out-of-box performance without sacrificing database integrity in the event of a crash or power failure. RTI does not expect your performance to be affected negatively by this change.

See Configuring Persistent Storage, in the RTI Connext Core Libraries User’s Manual for more information on these parameters.

2.2.2.5.3.4. Web Integration Service no longer installed in separate package

As described in What’s New in 7.1.0, in the Web Integration Service Release Notes, Web Integration Service is now installed with Connext Professional; you will no longer find a separate installation package for it. There are no migration tasks associated with this change. Every file is located in the same path, your XML configurations will work, you’ll find scripts and examples in the same path.

Note that if you need to use Web Integration Service on a platform for which there is no host installer (e.g., ARM Linux), you will need to install the Connext Professional target .rtipkg package for that platform.