2.4.7. Discovery Data Export/Import

DDS discovery data can be exported from the Admin Console to an XML file. This data file can then be imported into the Admin Console and displayed. This can be useful if you want to review the data later, or perhaps share it with a colleague or RTI support.

Discovery data includes information shown in the following views:

  • DDS Logical View

  • Physical View

  • Processes

  • DDS QoS

  • DDS Data Type

  • Log (Distributed Logger) panel in the Process View

Data imported from discovery files is then used to populate the Health and Match Analyses views.

2.4.7.1. Obfuscation

There are cases when discovery information contains information that should not be shared with third parties. For these cases, the export feature offers the ability to obfuscate (render unintelligible) information in these files. Below are the available options for obfuscating data, along with the discovery data to which they apply.

  • Names

    • All Topic names are obfuscated.

    • The EntityNameQosPolicy for DomainParticipants, Publishers, DataWriters, Subscribers, and DataReaders.

    • The PartitionQosPolicy for Publishers and Subscribers.

  • Properties

    • The PropertyQosPolicy name/value pairs are obfuscated. Some RTI-specific property names are not obfuscated, however. This is because Admin Console needs them to reconstruct data for the views.

    • Affects DomainParticipants, DataWriters, and DataReaders.

  • Types

    • Type information is not be stored and the type name is obfuscated.

  • Locators

    • The port and address of each locator are obfuscated.

    • This affects DomainParticipants, DataWriters, and DataReaders.

  • GUIDs (Globally Unique IDentifiers)

    • It may be possible to reverse engineer Internet Protocol (IP) address from these identifiers.

    • Affects DomainParticipants, Publishers, DataWriters, Subscribers, and DataReaders.

2.4.7.2. Limitations

This feature is considered to be a prototype release because of the following:

  • Data type information is stored in serialized (binary) form instead of native XML.

  • Obfuscating data type information simply removes it instead of obfuscating the embedded names.

  • Supplemental data from RTI services is not stored. Information originating from these services are responsible for populating information displayed in the UI views such as state, routes, and many other fields.