.. include:: /../getting_started/vars.rst

RTI Infrastructure Services
***************************

.. _section-Product-Persistence-700:

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

In 7.0.0, 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 :numref:`section-General-XML-610`.) 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 <https://www.omg.org/spec/DDS-XML/1.0/PDF>`_.

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

.. ROUTING-814


Removals in Cloud Discovery Service
===================================

<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:

.. code-block:: xml

    <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 
:link_cds_forwarder_700:`Forwarder, in the RTI Cloud Discovery Service documentation <>`.

.. MG-113

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 :link_cds_monitoring_700:`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.1 or earlier application to subscribe to monitoring data published by 
your 7.0.0 application, and vice versa. If you have *Cloud Discovery Service* 
in both 7.0.0 and a previous release, you will need to create different 
*DataReaders* for each monitoring *Topic* for each release.

.. MG-114


Incompatible persistent storage (database) format
=================================================
In 7.0.0, 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.0.0.
If you have this requirement, contact RTI Support at support@rti.com.