4.3. What’s New in 7.0.0

4.3.1. Updated Security Settings

The security preferences for Admin Console have been updated to rename Shared Secret Algorithm` to Key Establishment Algorithm. The entries for this setting have been expanded to include auto and a new alternative EC Diffie-Hellman. The previous entries have been renamed to better align with industry-standard terminology.

4.3.2. Support for Partitions at the DomainParticipant level

Previously, Partitions could only be set for Publishers and Subscribers; they control which DataWriters and DataReaders within those entities match each other and can communicate. Now you can also set Partitions at the DomainParticipant level. Then, in order for DomainParticipants with Partitions to communicate with each other, they need the same domain ID, domain tag, and at least one matching Partition.

This includes the following enhancements to Admin Console:

  • You can use the updated Preferences panel to select Partitions for DomainParticipants.

  • The match analysis mechanism has been updated, so you can differentiate the entities that a specific entity cannot communicate with due to the DomainParticipant’s partitions visibility. This can be seen in the Admin Console graphs; the nodes will have a different style when DomainParticipant Partitions are not matching. Additionally, health status will indicate that DomainParticipant Partitions are mismatching.

  • You can filter the Admin Console graph views based on these Partitions. This allows you to focus on the communication related to the specific partitions.

  • When subscribing to a topic, you can specify a Partition for the DomainParticipant associated with the Subscriber.

  • Exported discovery data includes information about these Partitions, so this information can be seen in offline mode when importing discovery data into Admin Console.

For more information on DomainParticipant-level Partitions, see the Connext Core Libraries What’s New document, and the PARTITION QosPolicy in the Connext Core Libraries User’s Manual.

4.3.3. Larger DomainParticipant liveliness assertion period

Admin Console now uses a much larger default (10 seconds compared with 1 second) DomainParticipant liveliness assertion period in order to help scalability while in use with large systems. It does this by reducing the network traffic created by Admin Console itself.