Configuring Participants

An XML <persistence_service> tag will contain a set of <participants>. The persistence service will persist topics published in the domainIDs associated with these participants. For example:

<persistence_service name="Srv1">
    <participant name="Part1">
        <domain_id>71</domain_id>
        ...
    </participant>
    <participant name="Part2">
        <domain_id>72</domain_id>
        ...
    </participant>
</persistence_service>

Using the above example, the persistence service will create two pairs of DomainParticipants on DDS domains 71 and 72, respectively. In each pair, one DomainParticipant is used to receive data and the other to publish.

After the DomainParticipants are created, the persistence service will monitor the discovery traffic, looking for topics to persist.

Notice that in some cases there may be more than one pair of DomainParticipants per domain when there are multiple versions of a type for a given topic. (See Support for Extensible Types.)

The <domain_id> tag can be specified alternatively as an attribute of <participant>. For example:

<persistence_service name="Srv1">
    <participant name="Part1" domain_id="71">
        ...
    </participant>
</persistence_service>

describes the participant tags. Notice that <persistence_group> is required.

<durable_subscriptions>
  <element>
     <role_name>DurSub1</role_name>
     <topic_name>Example MyType</topic_name>
     <quorum>2</quorum>
  </element>
  <element>
     <role_name>DurSub2</role_name>
     <topic_name>Example MyType</topic_name>
  </element>
</durable_subscriptions>

© 2016 RTI