5. QoS Provider

Each Vortex DDS block has a QoS that can be set using the Block Parameters.

The following section explains how the QoS is set for a DDS entity using the QoS Provider.

5.1. QoS Provider File

Quality of Service for DDS entities is set using XML files based on the XML schema file DDS_QoSProfile.xsd. These XML files contain one or more QoS profiles for DDS entities. An example with a default QoS profile for all entity types can be found at DDS_DefaultQoS.xml.

Note: Sample QoS Profile XML files can be found in the examples directories.

5.2. QoS Profile

A QoS profile consists of a name. The file contains QoS elements for one or more DDS entities. A skeleton file without any QoS values is displayed below to show the structure of the file.

<dds xmlns="http://www.omg.org/dds/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
            xsi:schemaLocation="file:DDS_QoSProfile.xsd">
    <qos_profile name="DDS QoS Profile Name">
        <datareader_qos></datareader_qos>
        <datawriter_qos></datawriter_qos>
        <domainparticipant_qos></domainparticipant_qos>
        <subscriber_qos></subscriber_qos>
        <publisher_qos></publisher_qos>
        <topic_qos></topic_qos>
    </qos_profile>
</dds>

Example: Specify Publisher Partition

The example below specifies the publisher’s partitions as A and B.

<publisher_qos>
    <partition>
        <name>
            <element>A</element>
            <element>B</element>
        </name>
    </partition>
</publisher_qos>

You can also set the partition from the QoS tab of Publisher and Subscriber blocks. Please see Publisher Block: Override Partition and Subscriber Block: Override Partition sections for more information.

5.4. Known Limitations

See QoS Provider Known Limitations for a list of limitations on QoS Provider support.