16.4 System Properties

Connext uses the DomainParticipant’s PropertyQosPolicy to maintain a set of properties that provide system information, such as the hostname.

Unless the default the DDS_DomainParticipantQos structure (see 16.3.7 Setting DomainParticipant QosPolicies) is overwritten, the system properties are automatically set in the DDS_DomainParticipantQos structure that is obtained by calling the DomainParticipantFactory’s get_default_participant_qos() operation or by using the constant DDS_PARTICIPANT_QOS_DEFAULT.

System properties are also automatically set in the DDS_DomainParticipantQos structure loaded from an XML QoS profile unless you disable property inheritance using the attribute inherit in the XML tag <property>.

By default, the system properties are propagated to other DomainParticipants in the system and can be accessed through the property field in the Table 28.1 Participant Built-in Topic’s Data Type (DDS_ParticipantBuiltinTopicData).

You can disable propagation of individual properties by setting the property’s propagate flag to FALSE or by removing the property using the PropertyQosPolicyHelper operation, remove_property() (see Table 47.35 PropertyQoSPolicyHelper Operations).

The number of system properties that are initialized for a DomainParticipant is platform specific: only process_id and os_arch are supported on all platforms.

These properties will only be created if Connext can obtain the information for them; see Table 16.8 System Properties.

System properties are affected by the DomainParticipantResourceLimitsQosPolicy’s participant_property_list_max_length and participant_property_string_max_length.

Table 16.8 System Properties

Property Name



Time when the executable was created.1


Name and full path of the executable.2


Time when the execution started.3




Architecture for which the library was compiled (for example, x64Darwin10gcc4.2.1).


Process ID


Username that is running the process.5