4.3. What’s New in 7.1.0

4.3.1. Improved startup by reducing discovery traffic

Admin Console will now only create local endpoints (DataWriters and DataReaders) for specific features if and when it discovers corresponding opposite endpoints in the DDS domain. For example, when Admin Console starts, it will not create local endpoints for Distributed Logger unless and until it finds corresponding endpoints for Distributed Logger running in that domain.

Previously, Admin Console created local endpoints for features such as Distributed Logger before knowing if they were needed. These extra endpoints caused unnecessary Discovery traffic in some cases. Now Admin Console will start with zero DataWriters and DataReaders, thus creating as little Discovery traffic as possible, while still supporting all of the existing features.

4.3.2. Ability to publish samples

Now you can use Admin Console to publish data samples. To do so, you will select a Topic that you want to publish samples of, and its QoS. To create the Publisher and DataWriter for sending the sample, Admin Console needs the Topic’s type-code definition; if Admin Console hasn’t already discovered it, you will be prompted to provide this information.

Once Admin Console has created the Publisher and DataWriter for your selected Topic, you can fill in the sample’s content using Python code within Admin Console. This sample can be cached and/or sent to available DataReaders.

4.3.3. Distributed Logger ‘message’ topic now visible from custom implementations

Previous versions of Admin Console checked that the Distributed Logger ‘message’ topic (rti/distlog) was being published from the Connext Core Library version 5.1 or newer, otherwise the messages would not be shown. This was originally done to prevent incompatibilities that could have happened with custom implementations prior to 5.1. However, it also meant that customers who wanted to publish this topic from a Connext Micro version did not see their messages in Admin Console. This restriction has been removed.

4.3.4. Security information and match analysis updates

Security attributes are now visible in Admin Console. This information is now exposed through the builtin topics, so it can now be visualized in Admin Console. In addition, Admin Console will now perform a security match analysis with this same information.

For details on how the security attributes are matched, see Match Analyses View.

4.3.5. Support for Dynamic Certificate Expiration and Pre-Shared Key Protection

Admin Console will now show a dialog when a certificate in use is about to expire. Three new fields were added to the security preferences page to allow editing key_revision_max_history_depth, rtps_protection_preshared_key, and certificate_expiration_advance_notice_duration properties.

For more information on these new properties, see Properties for Configuring Authentication, in the RTI Security Plugins User’s Manual.

4.3.6. New Platforms

This release adds support for Red Hat® Enterprise Linux 9 systems on x64 CPUs. See RTI Connext What’s New in 7.1.0.

4.3.7. Use of JEP Third-Party Software

Admin Console now uses JEP 4.1.0.

4.3.8. Third-Party Software Upgrades

The following third-party software used by Admin Console has been upgraded:

Table 4.1 Third-Party Software Changes

Third-Party Software

Previous Version

Current Version

XStream

1.4.19

1.4.20

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.