Configuration of RTI Connext and RTI Queuing Service
Defines types that can be used by RTI Queuing Service
Specifies a QoS library and profiles. The contents of this tag are specified in the same manner as for an [NDDS] QoS profile file
Configuration for RTI Queuing Service
Remote access configuration.
The settings for the DDS Domain Participant used in a QueuingService.
The DDS Domain ID used by the RTI Queuing Service instance
The QoS setting for the RTI Queuing Service Domain Participant
Configuration settings for Distributed Logger.
Use this tag to enable or disable the publication of
statistics calculated within fixed time windows
Enable the publication of statistics calculated in this
time window
Configuration of the publication of entity status and statistics
Specify the frequency the status of this entity is published.
Set it to infinite to disable it.
Configuration of the publication of entity status and statistics
Period in which the current averages are retreived
and used for the calculation of the statistics. A smaller
period will give more accurante historical statistics but
a higher use of resources.
Override monitoring general configuration for this specific entity
Storage kind for the service and storage settings for persistent queues
Set the different QoS settings for the service.
Sets the persistence settings for the service
If set to TRUE a persitent service will start from an existing database.
Filesystem storage settings for persistent queues
The directory where the files to persist the data will be placed.
Default: current working directory
A prefix for all the files created by RTI Persistence Service.
Default: QS
Determines the level of synchronization of the
data to store with the physical disk.
Default: OFF.
Every sample is written into physical disk as
RTI Persistence Service receives it
Samples are written into physical disk at
critical moments
No synchronization is enforced. Data will
be written to phyisical disk at the OS's
discretion
Sets the journal mode.
Default: DELETE.
The rollback journal is deleted at the conclusion
of each transaction.
This mode commits transactions by truncating the
rollback journal to zero-length instead of deleting it.
This mode prevents the rollback journal from being
deleted at the end of each transaction. Instead,
the header of the journal is overwritten with zeros.
This mode stores the rollback journal in volatile RAM.
This saves disk I/O but at the expense of database
safety and integrity.
The WAL journaling mode uses a write-ahead log instead
of a rollback journal to implement transactions.
The OFF journaling mode disables the rollback journal
completely.
If the application crashes in the middle of a transaction
when the OFF journaling mode is set, then the files containing
the samples will very likely go corrupt.
Sets the auto-vacuum status of the storage.
Default: FULL.
When auto-vacuum is disabled and data is deleted from the storage files,
the files remain the same size.
The storage files are compacted after every transaction.
<NOT SUPPORTED>
Trace file for debug information.
Default: None
The max size in kbytes for a persistence file (multiple files will be used if exceed)
Default: 1 GB (one million kbytes)
The configuration for the RTI Queuing Service SharedSubscriber
This element allows to configure a queue where the undelivered messages are sent
The topic name associated to a SharedReaderQueue
This element allows to define the session settings for a RTI Queuing Service instance.
THis tag allows to define the different settings for a session
Thread settings for a certain session
Dequeue period for a certain session
Slaves will search for the master if a timeout period elapsed since the last messages from the master was received.
Timeout for messages enqueued without quorum.
Conditions and WaitSets provide another way for [NDDS] to communicate status changes (including the arrival of data). While a Listener is used
to provide a callback for synchronous access, Conditions and WaitSets provide asynchronous data access. In other words, Listeners
are notification-based and Conditions are wait-based.
Shared Reader Queue configuration
The topic name associated to a SharedReaderQueue
The type name of the toppic associated to a SharedReaderQueue
A shortcut to create a reply queue. This tag defines the type of the reply queue.
A shortcut to create a reply queue. This tag defines the topic name of the reply queue.
Set the different QoS settings for a certain SharedReaderQueue.
Watermark settings. high_watermark, low_watermark represent percentages.
Resource allocation settings.
Sets the resource settings for a certain SharedReaderQueue.
The allocation settings for a certain SharedReaderQueue.
The watermark settings for a certain SharedReaderQueue.
The replacement policy when the queue is full of messages.
The replacement policy when the queue is full of messages.
The replacement policy kind when the queue is full of messages.
Set the retry policy for messages
The maximum time before a response can be considered timed out.
Set the distribution policy for a certain SharedReaderQueue.
The kind of distribution policy used to distribute samples amongst SharedReaderQueue subscribers
Mark the last undelivered sample of a queue for a Consumer
Settings for producer updates, fail over and load balancing.
Enabled should be 1, true or YES for synchronization to be set.
Settings for producer updates, fail over and load balancing.
Enabled should be 1, true or YES for synchronization to be set.
Settings queues replicated across multiple queuing service instances.
Ensure a quorum of queue instances agree on the message consumer before the message is sent.
The number of queue service instances running the same queue.
Sets the maximum time a message can remain in a SharedReaderQueue.
Sets the maximum time a message can remain in a SharedReaderQueue.
Sets the persistence settings for the SharedReaderQueue
in_memory_state should be 1, true or YES for synchronization to be set.
Set the reliability settings for a SharedReaderQueue