Configuration of RTI DDS and RTI DDS Services.
Configuration of an execution of RTI Persistence Service
Remote administration configuration.
Configuration settings for Distributed Logger.
Configuration of the persistent storage to store the topic data
Database connection used to persist the topic data
Persist data in the filesystem
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: PS
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
For each participant
tag, RTI Persistence Service creates two
DDS DomainParticipants on the same domain ID:
one to subscribe to changes and one to publish changes.
QoS for the domain participants. Default: DDS defaults.
Configures different aspects of the internal memory management for
the data persisted within this persistence group
Durable subscriptions for a given topic.
A persistence group describes a set of topics whose data that
must be persisted by the persistence service.
A list of POSIX expressions separated by commas that describe
the set of topics associated with the persistence group.
The filter can be specified as an attribute of persistence_group
as well. Default: *
A list of POSIX expressions separated by commas that describe
the set of topics denied in the persistence group.
This "black" list is applied after 'filter'.
Default: empty
Content filter topic expression. A persistence group can subscribe
to a specific set of data based on the value of this expression.
Default: no expression.
Controls whether or not the
persistence service propagates dispose messages from DataWriters
to DataReaders. Default: true
Controls whether or not the
persistence service propagates unregister messages from
DataWriters to DataReaders. Default: false
Controls whether or not the
persistence service propagates the source timestamp
of the received samples. Default: false
Indicates if the persistence
service should create one Publisher per persistence group or one
Publisher per PRSTDataWriter inside the persistence group.
Default: true
Indicates if the persistence
service should create one Subscriber per persistence group or
one Subscriber per PRSTDataReader in the persistence group.
Default: true
Indicates if the HISTORY
and RESOURCE_LIMITS QoS policy of the PRSTDataWriters
and PRSTDataReaders should be configured based on the
DURABILITY SERVICE value of the discovered DataWriters.
Default: false
Indicates if the persistence
group must use a separate ODBC database connection to store
the topic data received by each PRSTDataReader.
Default: true
This property controls how often (expressed as a number of
samples) the PRSTDataReader state is stored in the database.
The PRSTDataReaders are the DDS DataReaders created by the
persistence service.
This property is only applicable when the persistence service
operates in persistent mode (the database_connection tag is present)
Default: 1
Determines how much state
will be kept in memory by the PRSTDataWriters in order to
avoid accessing the database.
The property is only applicable when the persistence service
operates in persistent mode (the database_connection tag is present).
Default: For KEEP_LAST or ResourceLimitsQosPolicy.
max_samples != DDS_UNLIMITED_LENGTH, the default is true.
Otherwise, the default is false
This property controls how often (expressed as a number of
milliseconds) transactions are comitted for a PRSTDataWriter.
Default: 0
This property controls how often (expressed as a number of
samples) transactions are comitted for a PRSTDataWriter.
Default: 1
This property controls how often (expressed as a number of
milliseconds) samples are marked as acked in the database by
the PRSTDataWriter.
Default: 0
Defines how many samples will be pre-fetched by a PRSTDataWriter to satisfy late joiner requests.
Default: 20000
This property is used to enable support for durable subscriptions in the PRSTDataWriters.
When durable subscriptions are not required setting this property to false will
increase performance.
Default: true
Indicates if the persistence service will use waitsets or listeners
to read data from the PRSTDataReaders.
Default: false
QoS for the Publishers
QoS for the Subscribers
QoS for the DataWriters
QoS for the DataReaders
DSN used to connect to the database using ODBC. You should
create this DSN through the ODBC settings on Windows systems,
or in your .odbc.ini file on UNIX/Linux systems.
Username for the data base connection.
Default: no user name
Password for the data base connection.
Default: no password
indicates if the topic data
associated with a previous execution of the persistence service
must be restored or not. If the topic data is not restored, it will be
deleted from the database. Default: true
Specifies the ODBC driver to load. By default, RTI Connext
will try to use the standard ODBC driver manager
library (UnixOdbc on UNIX/Linux systems, the Windows
ODBC driver manager on Windows systems).
Domain ID associated with the Participant. Default: 0
The topic name that will be subscribed to and whose
received values will be stored in the associated table
The type name of the topic that will be subscribed to
This column specifies the name of the QoS Profile that RTI Real-Time Connect will use to
create the subscription. Syntax: QosLibraryName::QosProfileName
Indicates if redundant persistence
service instances should synchronize their states with
one another.
Default: NO synchronization
When set to true, data messages lost on the way to one service
instance can be repaired by another without impacting the original
publisher of that message.
Default: false
When set to true, durable subscriptions and their state will be
synchronized across the different instances of persistence service.
Default: false
This property controls how often (expressed as a number of
milliseconds) the state of a durable subscription is synchronized
with other persistence services.
Default: 5000
Indicates if persistence service must purge samples after they
are acknowledged.
When persistence service runs with this flag set to true, samples
are removed from the PRSTDataWriters' queues as soon as they are
acknowledged by all of the live DataReaders and all of the durable
subscriptions.
When persistence service runs with this flag set to false, the
local durability of the PRSTDataWriters is configured to be
TRANSIENT_LOCAL. Acknowledged samples are kept in the
PRSTDataWriters' queues until new resources are needed.
Default: false
This tag can be used to enable and configure a sample log for
the PRSTDataWriters in a persistence group.
A sample log is a buffer of samples on disk that,
when used in combination with delegated reliability,
allows decoupling the original DataWriters from slow DataReaders.
Default: NO sample logging
Indicates whether or not sample logging is enabled.
Default: 0
Determines how many samples should be read and processed at once by the sample
log write thread.
Default: 100
Specifies the maximum size of a sample log file in Mbytes. When a log file becomes full,
persistence service creates a new log file.
Default: 60 MB
The period (in milliseconds) at which persistence service removes sample
log files whose full content have been written into the
PRSTDataWriter by the sample log write thread.
Default: 10000 millisec
This tag indicates how often (in milliseconds) the read bookmark is persisted into disk.
Default: 1000 millisec
Describes a durable subscription.
Sets the domain ID associated with the participant.