4.3. What’s New in 7.2.0
4.3.1. Graphical Data Publishing is no longer experimental
As of Connext 7.2.0, Graphical Data Publishing (GDP) is no longer experimental.
4.3.2. The Discovery file name displays in the title bar when working with offline data
When importing a Discovery file, Admin Console now shows the path of that file in the title bar to better indicate that offline data, not ‘live’ system data, is being displayed.
4.3.3. Improvements to Admin Console tree views
The following improvements are available in Admin Console tree views:
DomainParticipants are now available and selectable in the Physical View. On selecting a DomainParticipant the first time, the Process View for its parent process displays. If selected a second time, the QoS and other panels display data from that DomainParticipant.
The sort order in all tree views is now done first by entity name in a case-insensitive manner. When the entity is a process, the process name is sorted (case insensitive), and then the process ID (as a number, not a string) is used.
4.3.4. Admin Console now reports a mismatch for the instance state consistency QoS
Admin Console previously did not report a mismatch for the instance state consistency QoS. Admin Console now accounts for instance state consistency when calculating the health of a system and match analysis.
4.3.6. Support for mutable security properties
Admin Console now reuses, instead of destroying and recreating, all DomainParticipants when changing mutable security properties.
For more information about which security properties are mutable, see the RTI Connext Property Reference Guide.
4.3.7. Integration with instance state consistency enhancements
A new instance_state_consistency_kind option is now available in the
dialogs for Subscribing/Publishing.
If “Recover instance state” was selected while subscribing, Admin Console’s Instance Table will now attempt to recover and display samples that have transitioned back to the ALIVE state. Note that this recovery is not always possible because only a single sample is kept for each instance. For example, if a different DataWriter with a lower strength publishes samples after the liveliness loss, Admin Console’s cached sample will come from the lower-strength DataWriter; therefore, the sample will not show in the Instance Table. However, if the cached sample is from the same DataWriter that is transitioning the instance to ALIVE, then the sample will appear.
4.3.8. Publisher and Subscriber entity names now default to their entity kind
This update was available in release 7.1.0, but not documented at that time.
Previously, Publisher and Subscriber DDS entities “inherited” the names of the first child discovered. This logic helped provide insight into the QoS name policy, even though neither the Publisher nor Subscriber QoS names are distributed on the wire. Starting with Connext 7.2.0, that logic has been removed to avoid confusion caused by QoS settings not being reflected in Admin Console. Now, as soon as the actual QoS settings are distributed through discovery, that information is added in the Admin Console user interface.
4.3.9. Third-Party software changes
The following third-party software is now used by Admin Console:
Third-Party Software |
Version |
|---|---|
picocli |
4.7.3 |
jackson-core |
2.15.0 |
jackson-databind-jdk8 |
2.15.0 |
jackson-dataformat-xml |
2.15.0 |
The following third-party software used by Admin Console have been upgraded:
Third-Party Software |
Old Version |
New Version |
|---|---|---|
JavaFX |
11 |
17.0.7 |
AdoptOpenJDK |
11.0.13 |
17.0.6 |
AdoptOpenJRE |
11.0.13 |
17.0.6 |
Eclipse |
2020-06 |
2023-03 |
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.