One of the core features of DDS is “discovery”-- the mechanism by which a DDS application can learn about other DDS applications and their endpoints. In the majority of DDS applications, the discovery process is fully dynamic, meaning that no a priori knowledge about remote applications is required by the local application.
In some DDS systems however, particularly those that require very high determinism such as safety critical applications, it is advantageous to use “static” endpoint discovery. In this static approach, each DDS application programmatically asserts which remote DomainParticipants it is expecting to discover at runtime, and what DataReaders and DataWriters (endpoints) those remote DomainParticipants contain. These assertions enforce what can be discovered, not necessarily what will be discovered; this is due to the fact that a DomainParticipant the local application is expecting may never actually be present in the system.
RTI Connext DDS Micro and RTI Connext DDS Cert include the Dynamic Participant Static Endpoint (DPSE) discovery plugin that can be used to achieve static discovery. This plugin is part of every Micro and Cert installation. RTI Connext Professional can support static discovery through the use of the optional Limited Bandwidth Endpoint Discovery (LBED) Plugins.
RTI’s Admin Console tool uses the RTI Connext Professional libraries and therefore must make use of the LBED plugins.
For the purpose of this document, it is assumed that RTI Connext Professional 6.1.0 is installed on the development host and that the Admin Console version matches this installation.
Lastly, it is assumed that readers of this document are familiar with all aspects of configuring the environment and building applications for both Pro and Micro.
First, log into the customer support portal at https://support.rti.com then select the LBED version that is appropriate for your development host.
Open the RTI Launcher, and move to the Configuration tab. Click on the “Install RTI Packages” button, navigate to your downloaded file, and install.
Now that the LBED plugins are installed, you must configure Admin Console to use them; this is done in the tool’s quality of service (QoS) settings.
The QoS file in this example-- RTI_ADMIN_CONSOLE_EXAMPLE_PROFILE.xml-- is essentially a clone of the default one used by Admin Console with the exceptions that it:
- Renames the QoS library to MyLibrary
- Adds a QoS profile named MyLibrary::MicroVisualization
- Contains information about where Admin Console should find the LBED plugin, and where to find the static discovery information
After starting Admin Console, open the preferences dialog from "View-->Preferences" in the menu bar. Use the "Add Files" button near the bottom of the window to specify the RTI_ADMIN_CONSOLE_EXAMPLE_PROFILE.xml file. Then manually join Domain 100, selecting MyLibrary::MicroAdministration from the drop-down list of QoS profiles.
At this point, Admin Console should visualize the publisher_1 application when it is run.