An XML <persistence_service> tag will contain a set of DomainParticipants. 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 DomainParticipants on DDS domains 71 and 72. After the DomainParticipants are created, the persistence service will monitor the discovery traffic looking for topics to persist.
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>
Table 7 describes the participant tags. Notice that <persistence_group> is required.
|
Tags within <participant> |
Description |
Number of Tags Allowed |
|
<domain_id> |
Domain ID associated with the Participant. The domain ID can be specified as an attribute of the participant tag. Default: 0 |
0 or 1 |
|
<durable_ |
Configures a set of Durable Subscriptions for a given topic. This is a sequence of <element> tags, each of which has a <role_name>, a <topic_name>, and a <quorum>. For example: <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>
Default: Empty list See Configuring Durable Subscriptions in Persistence Service for additional information |
0 or 1 |
|
<participant_ |
Participant QoS. Default: DDS defaults |
0 or 1 |
|
<persistence_ |
A persistence group describes a set of topics whose data that must be persisted by the persistence service. |
1 or more |
© 2015 RTI