11.3. What’s New in 7.2.0
Monitoring Library 2.0 can be enabled in Recording Service so that all DDS entities created by this service will provide monitoring data to Observability Framework.
To enable Monitoring Library 2.0 in Recording Service, add the XML code snippet shown below to an XML QoS profile, then run Recording Service from the folder containing the profile. Add the snippet to any of the following XML files:
NDDS_QOS_PROFILES.xml
, located in the Connext installation directory at<NDDSHOME>/resource/xml/
USER_QOS_PROFILES.xml
, located in the Web Integration Service working directoryAny XML file included in the
NDDS_QOS_PROFILES
environment variable
<?xml version="1.0"?>
<dds>
<qos_library name="MonitoringEnabledLibrary">
<qos_profile name="MonitoringEnabledProfile" is_default_participant_factory_profile="true">
<participant_factory_qos>
<monitoring>
<enable>true</enable>
</monitoring>
</participant_factory_qos>
</qos_profile>
</qos_library>
</dds>
For more information, see How to Load XML-Specified QoS Settings in the Core Libraries User’s Manual.
11.3.1. Recordings converted to CSV can include the Source timestamp
Converter Service can now show the Source timestamp, in addition to the
Reception timestamp, when converting a recorded database into CSV. To do
so, set the new <include_source_timestamp>
tag to true; this tag is false
by default.
11.3.2. Support for dynamic certificate renewal
A running Recording or Replay Service instance can use the new
authentication.identity_certificate_file_poll_period.millisec
property in
RTI Security Plugins to renew its identity certificate without the need to
restart the service. The
authentication.identity_certificate_file_poll_period.millisec
property
must have a value greater than zero for the participant to periodically poll
its identity certificate file for changes.
For more information, see the sections on how to support RTI Security Plugins in Recorder and in Replay. Also see Advanced Authentication Concepts in the RTI Security Plugins User’s Manual.
11.3.3. Support for dynamic certificate revocation
A running Recording Service instance (Recorder or Replay) can use the
authentication.crl
and the new authentication.crl_file_poll_period.millisec
properties in RTI Security Plugins to specify certificate revocations
without the need to restart the service. The authentication.crl_file_poll_period.millisec
property must have a value greater than zero for the participant to
periodically poll the provided CRL file for changes.
For more information, see the sections on how to support RTI Security Plugins in Recorder and in Replay. Also see Advanced Authentication Concepts in the RTI Security Plugins User’s Manual.
11.3.4. Third-party software changes
The following third-party software used by Recording Service have been upgraded:
Third-Party Software |
Previous Version |
Current Version |
---|---|---|
libxml2 |
2.9.4 |
2.11.4 |
libxslt |
1.1.35 |
1.1.38 |
For information on third-party software used by Connext products, see the “3rdPartySoftware” documents in your installation: <NDDSHOME>/doc/manuals/connext_dds_professional/release_notes_3rdparty.