10. XML profiles
eProsima Fast DDS allows for loading XML configuration files, each one containing one or more XML profiles. In addition to the API functions for loading user XML files, Fast DDS tries to locate and load several XML files upon initialization. Fast DDS offers the following options:
Load an XML file named DEFAULT_FASTDDS_PROFILES.xml located in the current execution path.
Load an XML file which location is defined using the environment variable
FASTDDS_DEFAULT_PROFILES_FILE
(see FASTDDS_DEFAULT_PROFILES_FILE).Load the configuration parameters directly from the classes’ definitions without looking for the DEFAULT_FASTDDS_PROFILES.xml in the working directory (see SKIP_DEFAULT_XML).
Load directly the XML as a string data buffer.
An XML profile is defined by a unique name that is used to reference the XML profile during the creation of an Entity, the Transport configuration, or the DynamicTypes definition.
Both options can be complemented, i.e. it is possible to load multiple XML files but these must not have XML profiles with the same name. This section explains how to configure DDS entities using XML profiles. This includes the description of all the configuration values available for each of the XML profiles, as well as how to create complete XML files.
- 10.1. Creating an XML profiles file
- 10.2. DomainParticipantFactory profiles
- 10.3. DomainParticipant profiles
- 10.4. DataWriter profiles
- 10.5. DataReader profiles
- 10.6. Topic profiles
- 10.7. Transport descriptors
- 10.8. Intra-process delivery profiles
- 10.9. Log profiles
- 10.10. Dynamic Types profiles
- 10.11. Common
- 10.12. Example