Configuration of RTI DDS and RTI DDS Services.
Configuration of an execution of RTI Database Integration Service
General options, common to all data bases
Set it to true to enable real-time lazy database replication.
Setting this attribute to true will automatically configure the QoS values of publications
and subscriptions to provide conflict resolution and table initialization. The
attribute will also enable propagation of NULL values.
Default: false
Set it to true to enable typecode generation from table schemas.
When RTI Database Integration Service is used for table replication, setting this tag to true
(default) allows automatic table creation in the replicas.
Default: false if enable_table_replication is false. Otherwise, true
Use this attribute to increase the maximum number of objects per thread of
RTI Data Distribution Service.
Default: DDS default (1024)
Use this tag to configure Database Integration Service to use
waitsets to read samples from the subscriptions DataReaders.
Remote access configuration.
Configuration settings for Distributed Logger.
Options on how DDS types are mapped to data base tables,
common to all databases
This attribute sets the character that is used as a separator in the hierarchical
names generated when mapping IDL fields into SQL table columns. The attribute
is also used to configure the separator character for the columns in the meta
tables.
This attribute sets the open bracket character that is used in the index component
of the arrays and sequences members names.
This attribute sets the close bracket character that is used in the index component
of the arrays and sequences members names.
Configuration of a connection to a MySQL data base
Configuration of a connection to an Oracle data base. (Deprecated).
Kept for backward compatibility.
Configuration of a connection to a Timesten data base. (Deprecated).
Kept for backward compatibility.
Configuration of a connection to a SQL Server data base
Configuration of a connection to a PostgreSQL data base
Set of pre-defined entries to the table RTIDDS_SUBSCRIPTIONS
Default settings for an RTIDDS_SUBSCRIPTIONS
Pre-defined entry to the table RTIDDS_SUBSCRIPTIONS
Set of pre-defined entries to the table RTIDDS_PUBLICATIONS
Pre-defined entry to the table RTIDDS_PUBLICATIONS
Metadata fields associated with user data samples
Format of stored timestamps
SQL BIGINT
SQL TIMESTAMP
Metadata fields associated with user data samples
Metadata fields associated with user data samples
Metadata field to include or exclude
ALL
SOURCE_TIMESTAMMP
RECEPTION_TIMESTAMP
Data serialization schema
Legacy flat serialization
JSON serialization
JSONB serialization
Sets the domain ID associated with the participant.
This attribute controls the prefix length of the IDL member identifiers that will
be used to truncate column names when a table is automatically created.
This attribute controls the suffix length of the IDL member identifiers that will be
used to truncate column names when a table is automatically created.
This attribute is mandatory and there is no default value.
You must specify a valid DSN that is found
in a ODBCINI file or the Windows registry.
The RTI Database Integration Service Daemon will make a connection to this DSN.
User name for the data base connection
Password for the data base connection
Specifies the milliseconds interval
at which the RTI Database Integration Service Daemon publishes database changes. The
value must be greater than or equal to 0. With a value of 0 the daemon publishes
database changes as soon as they are available. A shorter time interval reduces
latency.
If enabled the RTI Database Integration Service Daemon’s log
messages will be stored in a table named RTIRTC_LOG in the database specified
by the DSN.
Enable storing log messages in the database
The value limits the size of the table, RTIRTC_LOG, in
the database that the daemon uses for logging messages. The default is 1000
rows, and a value of -1 implies no limit. When the table is filled, new log messages
will replace the oldest messages, effectively using the table as a circular
buffer.
This attribute is optional and it provides an estimation of the maximum duration of a
database transaction. If a table change is not committed in the interval specified by this
attribute, it will not be published to DDS.
The value limits the size of CLOB and NCLOB columns
for tables that do not have an associated TypeCode in
the RTIRTC_TBL_INFO meta table.
If a user table has an associated TypeCode, the maximum size of the CLOB and
NCLOB columns is determined on a per-column basis using the TypeCode information.
The value limits the size of BLOB columns for tables
that do not have an associated TypeCode in the
RTIRTC_TBL_INFO meta table.
If a user table has an associated TypeCode, the maximum size of the BLOB columns
is determined on a per-column basis using the TypeCode information.
The value is the default size used to store JSON samples in
a database. JSON strings longer than this value will be
allocated dynamically.
This attribute is optional and is only used if the Oracle TimesTen DSN specifies a diskless
connection. For diskless connections, the minimum size of the Oracle TimesTen XLA
staging buffer must be at least as big as the largest single SQL transaction executed
through the database connection. The size of a transaction is related to the aggregated
size of data values that have changed as a result of the transaction.
This column along with table_name specify the user table
into which data received by a DDSDataReader will be stored.
This column along with table_owner specify the user table
into which data received by a DDSDataReader will be stored.
The DDS domain ID that will be used to subscribe to DDS topics
whose values will be stored in the table
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 is used to designate one of the columns of the user table for use as the timestamp
when data changes are published with the DDSDataWriter
Determines the number of values of each instance received by
the DDS DataReader that can be stored in the table
Controls how many data samples are processed at a time.
Instead of executing SQL UPDATE or INSERT every time data is received,
the daemon only stores the data after it receives a certain
number of samples
is an upper limit on the amount of delay that will be
incurred before received data is stored in the database. The period can be set to 0 only if
process_batch is set to 1. This means that the daemon will store each data sample as it
is received so there is no need for periodic processing of the received samples
the user can chose whether or not the SQL
UPDATE/INSERT statements are committed when each data sample is stored or after
all of the data being processed have been stored
Commit the storage of a batch of data as a single transaction.
This will result in higher performance at
the risk of losing more data than necessary when the transaction is rolled-back
because an error with the database
This value will direct the daemon to commit the storage of each data sample as a
separate transaction.
Although the daemon will use more resources, if an error
occurs when a transaction is committed, only that data sample is lost.
Control the size of a cache, used to store keys that exist in the table, that
the daemon maintains for each DDS DataReader
Control the size of a cache, used to store keys that exist in the table, that
the daemon maintains for each DDS DataReader
If true, when a DDS DataWriter disposes an instance stored into
the database, the corresponding rows are deleted.
This column specifies the name of the QoS Profile that RTI Database Integration Service will use to
create the subscription. Syntax: QosLibraryName::QosProfileName
Whether or not duplicates should be filtered by
the daemon. If duplicates are not filtered, the subscription data
table may end up containing duplicates rows
Whether or not the samples associated with a DataWriter identified
by a virtual GUID must be stored in the database in order.
Whether or not the state of a RTI Database Integration Service subscription
must be persisted into the database.
The field only applies when filter_duplicates is set to true
Whether or not the daemon should overwrite the row corresponding to this
subscription/publication if it already exists in the database
Whether or not the daemon should delete the
previously existing rows in the subscription/publication table
This attribute is optional and sets the time between transaction
log acknowledgements in seconds. Greater values of this
setting reduce the frequency of transaction log file purging. Default
value is 30 seconds.