Configuration of RTI Connext and RTI Connext services.
Defines types that can be used by
RTI Routing Service
Specifies a QoS library and profiles. The
contents of this tag are specified in the same
manner as for an RTI Connext
QoS profile file
This element allows configuring the DDS Router Service
A routing service may belong to a
group of several routing services
identified by a common
group_name. This common name
can be used to implement a specific
policy when the communication happens
between routing services of the
same group. For example, in the
built-in DDS adapter, a participant
will ignore other participants in the
same group, as a way to avoid circular
communication.
Specifies a library of transformation plugins.
Entry point to load apluggable transformation
Specifies a library of adapter plugins.
Declares an adapter plugin.
Declares a java adapter plugin.
Shared library containing the implementation
of the adapter plugin.
Name of the function used to create the
adapter plugin, implemented in the shared library.
Name of the class that implements the adapter plugin.
For example:
com.rti.routingservice.adapter.jms.JMSAdapter
Set of name-value pairs passed to the plugin implementation
Configures the Java JVM used to load and run Java adapters
such as the JMS Adapter
The class path used to load java adapters.
Default: The value of the environment
variable CLASSPATH
Options for the JVM
(as they're passed to the java executable).
Default: no options.
Defines a mapping between two data domains.
Configures one of the DDS participants.
(Only applicable to DDS domains)
Sets the participant QoS. The contents
of this tag are specified in the same manner as an
RTI Connext QoS profile file.
Use the attribute base_name to inherit from an
existing profile. Default: DDS defaults.
Configures one of the connections.
(Applicable to non-DDS domains)
Reference to the an adapter plugin
in the form LibraryName::PluginName
Sets the domain ID associated with the participant.
Makes a type defined in the file
available to this connection
The name routes will use to refer to this type
The full name (e.g. module1::module2::type) of
the type defined in the file
Configures different aspects of the internal memory management for
the data routed within this connection
The properties of a thread pool of execution. The settings
apply to all the threads within the pool.
(See Platform Notes for platform specific details)
]]>
]]>
]]>
]]>
Sets the mask, priority and stack size of the
thread associated with this session.
Sets the mask. Default: MASK_DEFAULT
Sets the thread priority.
Default: O.S. default
Sets the thread stack size.
Default: O.S. default
Defines an N-thread context for route processing.
A route can be processed by one thread at a time.
Sets the DDS publisher QoS. Only applicable
to DDS domains. Default: DDS defaults
Sets the DDS subscriber QoS. Only applicable
to DDS domains. Default: DDS defaults
Conditions and WaitSets provide another way for RTI Connext 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.
Defines a explicit mapping between an input topic
on one domain and an output topic on the other domain.
Defines a explicit mapping between an input data stream
on one connection and an output data stream
on the other connection
Defines the route's input topic.
Only applicable to DDS inputs.
The topic name used by this route's DataReader
The type of the samples read in this route.
This type can be discovered or registered in the participant.
Sets the DDS Data Reader QoS.
Default: DDS defaults
Defines the route's output topic.
Only applicable to DDS inputs.
The topic name used by this route's DataWriter
The type of the samples written in this route.
This type can be discovered or registered in the connection.
Sets the DDS Data Writer QoS.
Default: DDS defaults
Applicable to non-DDS inputs.
Defines the route’s input stream.
The stream name used to identify the data read
in this route.
The type of the samples read in this route.
This type can be discovered or registered in the connection.
This element is used to configure the output of a route.
The stream name used to identify the data written
in this route.
The type of the samples read in this route.
This type can be discovered or registered in the connection.
Defines a SQL content filter topic for the DDS Data Rader,
making possible to subscribe only to a subset of the
data.
The content filter expression.
For example: x > 100
Specifies a value for a content-filter
expression using parameters.
Enables the propagation of filter information that is an aggregation
of the user DataReaders' filters.
Maximum number of events that must occur to propagate
the filter information. All the events are handled at once.
Default: one.
Range: [1, DDS_LENGTH_UNLIMITED]
Maximum amount of time the propagation of the filter information
is delayed since the first occurrence of an event.
All the indication events that occur within this interval
will be handle at once.
Default: infinite
Range: [1ns, DDS_DURATION_INFINITE]
Sets a data transformation to be applied for every
data sample.
Reference to the an transformation plugin
in the form LibraryName::PluginName
Defines a set of potential routes, with the same input and output
type, and the same input and output stream name. A route can eventually be instantiated
when a new stream is discovered with a type name and a stream name that match
the filters in the auto route. When this happens, a route is created (but not necessarily
started) with the configuration defined in the auto route tag.
Defines a set of potential routes, with the same input and output
type, and the same input and output stream name. A route can eventually be instantiated
when a new stream is discovered with a type name and a stream name that match
the filters in the auto route. When this happens, a route is created (but not necessarily
started) with the configuration defined in the auto route tag.
This element is used to configure which data types and topics
are discovered in the output
Controls when the route input (StreamReader)
or output (StreamWriter) is created
Default: IMMEDIATE.
The route StreamReader/StreamWriter is created as
soon as possible; that is, as soon as the types are available.
Note that if the type is defined in the configuration
file, the creation will occur when the routing service
starts.
If the type is not defined in the configuration file, it has
to be discovered
The route StreamReader is not created until the associated
connection discovers a data Producer on the same
stream
For example, for a DDS domain, RTI Routing Service will
not create the route DataReader until a DataWriter for
the same topic is discovered on the same domain.
The routing service StreamWriter is not created until the
associated connection discovers a data Consumer on the
same stream.
For example, for a DDS domain, RTI Routing Service will
not create the route DataWriter until a DataReader for
the same topic is discover on the same domain
The routing service StreamReader/StreamWriter is not
created until its counterpart in the route is created.
Both conditions must be true
At least one of the conditions must be true
The participant used to read data in this route
participant_1 - the first participant of this domain route
participant_2 - the second participant of this domain route
The connection used to read data in this route
connection_1 - the first connection of this domain route
connection_2 - the second connection of this domain route
The name identifying the stream used
in
Defines if the input connection will use types discovered
in the output connection and vice versa for
the creation of StreamWriters and StreamReaders in
the route. Default: false
Writes the data sample as if they came from its original
writer. Setting this option to true allows having
redundant routing services and prevents the applications
from receiving duplicate samples.
Default: false
When this tag is true, the data samples read from the
input stream are written into the output stream with
the same timestamp that was associated with them
when they were made available in the input
domain.
This option may not be applicable in some adapter
implementations in which the concept of timestamp
is unsupported.
Default: false
Indicates whether or not disposed samples
(NOT_ALIVE_DISPOSE) must be propagated by the
topic route.
This action maybe be overwritten by the execution
of a transformation.
Default: true
Indicates whether or not
NOT_ALIVE_NO_WRITERS samples must be propagated
by the topic route by using the
unregister_instance() operation
This action maybe be overwritten by the execution
of a transformation.
Default: true
Indicates how the TopicRoute handles the TopicQueries received
from the user DataReaders on the subscription side.
Default: PROPAGATION.
The TopicRoute's DataWriter is automatically configured
with TRANSIENT_LOCAL durability and accepts matching
TopicQueries and dispatch them from its own sample cache.
The TopicQueries are propagated from the user DataReaders
to the user DataWriters, which will be the final
endpoints dispatching the propagated TopicQueries.
Remote access configuration.
Configuration settings for Distributed Logger.
Configuration of the publication of entity status and statistics
Override monitoring general configuration for this specific entity
Specify the settings for the stream query proxy mode.
When enabled, supported routes will forward stream queries
from the user output stream readers to the user input stream
writers.
The samples produced as result of the propagated stream queries
will be forwarded back to the original user output stream
readers that issued the stream queries.
Specify the frequency the status of this entity is published.
Set it to infinite to disable it.
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.
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
This type is deprecated use byte instead
This type is deprecated use int32 instead
This type is deprecated use float32 instead
This type is deprecated use float64 instead
This type is deprecated use char8 instead
This type is deprecated use wchar instead
This type is deprecated use char16 instead
This type is deprecated use int16 instead
This type is deprecated use uint16 instead
This type is deprecated use uint32 instead
This type is deprecated use int64 instead
This type is deprecated use uint64 instead
This type is deprecated use float128 instead
<xs:boolean>
<xs:string>
<xs:integer>
<xs:nonNegativeInteger>
<xs:positiveInteger>
<xs:string>
Uses a byte-oriented encoding wich successive bytes separates by comma and each byte represented
either using a decimal or hexadecimal notation. White space is allowed between bytes.
For example:
34, 44, 56,0x44,127,0xf3,
44,233,122, 122, 44, 222
<xs:string>
Name that uniquely identifies this element.
<xs:string>
A QoS Profile can inherit its values from other QoS Profiles described in the XML file
using this attribute.
<xs:string>
It can only be 255 characters in length.
<xs:string>
It can only be 255 characters in length.
<xs:string>
The name of the Property.
<xs:string>
RTI Connext will select a QoS based on the evaluation of this filter expression on the topic name.
<BY_RECEPTION_TIMESTAMP_DESTINATIONORDER_QOS|BY_SOURCE_TIMESTAMP_DESTINATIONORDER_QOS>
<INSTANCE_SCOPE_DESTINATIONORDER_QOS|TOPIC_SCOPE_DESTINATIONORDER_QOS>
<AUTOMATIC_TRANSPORT_MULTICAST_QOS|UNICAST_ONLY_TRANSPORT_MULTICAST_QOS>
<VOLATILE_DURABILITY_QOS|TRANSIENT_LOCAL_DURABILITY_QOS|TRANSIENT_DURABILITY_QOS|PERSISTENT_DURABILITY_QOS>
<KEEP_LAST_HISTORY_QOS|KEEP_ALL_HISTORY_QOS>
<AUTOMATIC_LIVELINESS_QOS|MANUAL_BY_PARTICIPANT_LIVELINESS_QOS|MANUAL_BY_TOPIC_LIVELINESS_QOS>
<INSTANCE_PRESENTATION_QOS|TOPIC_PRESENTATION_QOS|GROUP_PRESENTATION_QOS>
<INSTANCE_PRESENTATION_QOS|TOPIC_PRESENTATION_QOS|GROUP_PRESENTATION_QOS|HIGHEST_OFFERED_PRESENTATION_QOS>
<DDS_NO_SERVICE_QOS|DDS_PERSISTENCE_SERVICE_QOS|DDS_QUEUING_SERVICE_QOS|DDS_ROUTING_SERVICE_QOS|RECORDING_SERVICE_QOS|REPLAY_SERVICE_QOS|DATABASE_INTEGRATION_SERVICE_QOS>
<BEST_EFFORT_RELIABILITY_QOS|RELIABLE_RELIABILITY_QOS>
<PROTOCOL_ACKNOWLEDGMENT_MODE|APPLICATION_AUTO_ACKNOWLEDGMENT_MODE|APPLICATION_EXPLICIT_ACKNOWLEDGMENT_MODE>
<SHARED_OWNERSHIP_QOS|EXCLUSIVE_OWNERSHIP_QOS>
<NO_REPLACEMENT_IGNORED_ENTITY_REPLACEMENT|NOT_ALIVE_FIRST_IGNORED_ENTITY_REPLACEMENT>
<UNREGISTERED_INSTANCE_REPLACEMENT|ALIVE_INSTANCE_REPLACEMENT|DISPOSED_INSTANCE_REPLACEMENT|ALIVE_THEN_DISPOSED_INSTANCE_REPLACEMENT|DISPOSED_THEN_ALIVE_INSTANCE_REPLACEMENT|ALIVE_OR_DISPOSED_INSTANCE_REPLACEMENT>
<RTPS_AUTO_ID|xs:string>
A valid IP address
<SYNCHRONOUS_PUBLISH_MODE_QOS|ASYNCHRONOUS_PUBLISH_MODE_QOS>
<NONE_REFILTER_QOS|ALL_REFILTER_QOS|ON_DEMAND_REFILTER_QOS>
<LIVELINESS_BASED_REMOTE_PARTICIPANT_PURGE|NO_REMOTE_PARTICIPANT_PURGE>
<UDPv4|UDPv6|SHMEM|MASK_DEFAULT|MASK_NONE|MASK_ALL> [|<UDPv4|UDPv6|SHMEM>| ... ]
<RTPS_AUTO_ID_FROM_IP|RTPS_AUTO_ID_FROM_MAC|RTPS_AUTO_ID_FROM_UUID>
<MASK_DEFAULT|MASK_NONE|MASK_ALL|BUILTIN_UNICAST|BUILTIN_MULTICAST|USER_UNICAST|USER_MULTICAST> [|<BUILTIN_UNICAST|BUILTIN_MULTICAST|USER_UNICAST|USER_MULTICAST>| ... ]
<MASK_DEFAULT|FLOATING_POINT|STDIO|REALTIME_PRIORITY|PRIORITY_ENFORCE> [|<FLOATING_POINT|STDIO|REALTIME_PRIORITY|PRIORITY_ENFORCE>| ... ]
(See Platform Notes for platform specific details)
<SDP|EDS|SPDP|SEDP|MASK_NONE|MASK_ALL|MASK_DEFAULT> [|<SDP|EDS|SPDP|SEDP>| ... ]
<ZERO_CDR_PADDING|NOT_SET_CDR_PADDING|AUTO_CDR_PADDING>
<LENGTH_UNLIMITED|xs:nonNegativeInteger>
<DURATION_INFINITE_SEC|DURATION_ZERO_SEC|xs:nonNegativeInteger>
<DURATION_INFINITE_NSEC|DURATION_ZERO_NSEC|xs:nonNegativeInteger>
<DURATION_INFINITE_SEC|DURATION_ZERO_SEC|DURATION_AUTO_SEC|xs:nonNegativeInteger>
<DURATION_INFINITE_NSEC|DURATION_ZERO_NSEC|DURATION_AUTO_NSEC|xs:nonNegativeInteger>
<LENGTH_UNLIMITED|xs:positiveInteger>
<LENGTH_AUTO|xs:positiveInteger>
<AUTO_MAX_TOTAL_INSTANCES|xs:positiveInteger>
<THREAD_PRIORITY_DEFAULT|THREAD_PRIORITY_BELOW_NORMAL|THREAD_PRIORITY_LOW|THREAD_PRIORITY_NORMAL|THREAD_PRIORITY_ABOVE_NORMAL|THREAD_PRIORITY_HIGH|xs:positiveInteger>
(See Platform Notes for platform specific details)
<THREAD_STACK_SIZE_DEFAULT|xs:positiveInteger>
(See Platform Notes for platform specific details)
<GUID_AUTO|xs:string>
<DEFAULT_FLOW_CONTROLLER_NAME|FIXED_RATE_FLOW_CONTROLLER_NAME|ON_DEMAND_FLOW_CONTROLLER_NAME|xs:string>
<ENCAPSULATION_ID_CDR_LE|ENCAPSULATION_ID_CDR_BE|ENCAPSULATION_ID_CDR_NATIVE|xs:unsignedShort>
<METP_ENCAPSULATION_ID_SHMEM_LE|METP_ENCAPSULATION_ID_SHMEM_BE|METP_ENCAPSULATION_ID_SHMEM|xs:unsignedShort>
<METP_ENCAPSULATION_ID_IB_RDMA_READ_LE|METP_ENCAPSULATION_ID_IB_RDMA_READ_BE|METP_ENCAPSULATION_ID_IB_RDMA_READ|xs:unsignedShort>
TODO
<SILENT|ERROR|WARNING|LOCAL|REMOTE|ALL>
<PLATFORM|COMMUNICATION|DATABASE|ENTITIES|API|ALL>
<DEFAULT|TIMESTAMPED|VERBOSE|VERBOSE_TIMESTAMPED|DEBUG|MINIMAL|MAXIMAL>
Time specified in seconds and nanoseconds
Time specified in seconds and nanoseconds
Declares a sequence of elements, which correspond to different xs:string.
Sequence number specified in high and low, or as a 64-bit decimal value
Resource allocation settings.
A sequence of elements with valid IP addresses.
RTPS well-known port mapping configuration.
RTI Connext uses the RTPS wire protocol.
The discovery protocols defined by RTPS rely on well-known ports to initiate discovery.
These well-known ports define the multicast and unicast ports on which a Participant will listen for discovery
metatraffic from other Participants.
The discovery metatraffic contains all the information required to establish the presence of remote DDS entities in the network.
The well-known ports are defined by RTPS in terms of port mapping expressions with several tunable parameters,
which allow the user to customize what network ports are used by the middleware.
In order for all Participants in a system to correctly
discover each other, it is important that they all use the
same port mapping expressions.
QoS related to reliable reader protocol defined in RTPS.
It is used to configure a reliable reader according to the
RTPS protocol.
QoS related to the reliable writer protocol defined in RTPS.
It is used to configure a reliable writer according to RTPS protocol.
The reliability protocol settings are applied to batches instead of individual data samples when batching is enabled.
The virtual GUID (Global Unique Identifier).
The virtual GUID is used to uniquely identify different incarnations of the same DataReader.
The association between a DataReader and its persisted state is done using the virtual GUID.
A sequence of elements of non-negative integers
<THREAD_SETTINGS_CPU_NO_ROTATION|THREAD_SETTINGS_CPU_RR_ROTATION>
(See Platform Notes for platform specific details)
The properties of a thread of execution.
(See Platform Notes for platform specific details)
Type representing a list of unicast locators.
A unicast locator specifies a transport class, a unicast address, and a unicast port number on which messages can be received by an entity.
Type representing a function defined into an external library.
Type representing a list of addresses associeted with a topic expression.
Declares a sequence of elements, which correspond to different TransportUnicastSettings_t
entities.
Declares a sequence of elements, which correspond to different TransportMulticast_t
entities.
Type representing a list of multicast locators.
A multicast locator specifies a transport class, a multicast address, and a multicast port number on which messages can be received by an entity.
Declares a sequence of elements, which correspond to different TransportMulticastSettings_t
entities.
Type used to configure the properties of a channel.
Declares a sequence of elements, which correspond to different ChannelSettings_t
entities.
Properties are name/value pairs objects.
Declares a sequence of elements, which correspond to different Property_t
entities.
Declares a sequence of encapsulations.
Type representing a list of transport encapsulations associated to a set of transports.
Declares a sequence of elements, which correspond to different TransportEncapsulationSettings_t
entities.
Endpoint groups are identified by a role_name and a quorum_count.
Declares a sequence of elements, which correspond to different EndpointGroup_t
entities.
On a DataWriter, this QoS policy states the maximum period in
which the application
expects to call write() on the DataWriter, thus publishing a new sample. The application
may call write() faster than the rate set by this QoS policy.
On a DataReader, this QoS policy states the maximum period in
which the application
expects to receive new values for the Topic. The application may receive data faster than
the rate set by this QoS policy.
This policy controls how each subscriber resolves the final value of a data instance that
is written by multiple DataWriters.
The Durability QoS policy controls whether or not, and how,
published samples are
stored by the DataWriter application for DataReaders that are found after the samples
were initially written.
This QoS policy is only used if the DURABILITY QoS policy is
PERSISTENT or TRANSIENT
and you are using RTI Persistence Service, an optional product which may be
purchased separately.
The Entity Factory QoS policy is a mechanism whereby a user can indicate whether entities
should be automatically enabled upon creation by their factory or whether
enabling should be deferred to a later time of the user's own choosing.
This QoS policy provides an area where your application can
store additional information
related to the Publisher and Subscriber. This information is passed between applications
during discovery using built-in topics.
This QoS policy configures the number of samples that RTI
Data Distribution Service will
store locally for DataWriters and DataReaders.
This QoS policy is used to suggest the maximum acceptable delay that is acceptable
between when data is written and when data is received.
The purpose of this QoS is to avoid delivering stale data to the application. Each data
sample written by a DataWriter has an associated expiration time, beyond which the
data should not be delivered to any application. Once the sample expires, the data will
be removed from the DataReader caches, as well as from the transient and persistent
information caches.
The LIVELINESS QoS policy specifies how RTI Data Distribution
Service determines
whether a DataWriter is "alive". A DataWriter's liveliness is used in combination with
the OWNERSHIP QoS policy to maintain ownership of an instance
(note that the DEADLINE QoS policy
is also used to change ownership when a DataWriter is still alive)
The OWNERSHIP QoS policy specifies whether a DataReader will
see changes to an
instance of a Topic from multiple DataWriters. For non-keyed Topics, there is only one
instance of the Topic.
The OWNERSHIP_STRENGTH QoS policy is used to rank DataWriters
of the same
instance of a Topic, so that RTI Connext can decide which DataWriter will
have ownership of the instance when the OWNERSHIP QoS policy
(Section 6.5.13) is set
to EXCLUSIVE.
The PARTITION QoS provides another way to control which DataWriters will match
and thus communicate with which DataReaders. It can be used to prevent DataWriters
and DataReaders that would have otherwise matched with the same Topic and compatible
QoS policies from talking to each other. Much in the same way
that only applications
within the same DDS domain will communicate with each other, only DataWriters and
DataReaders that belong to the same partition can talk to each other.
Since data samples are sent independently over networks that may deliver packets out
of order, the PRESENTATION QoS policy allows you to control
how a Subscriber sorts
and orders the received samples in the DataReader's queue.
Since data samples are sent independently over networks that may deliver packets out
of order, the PRESENTATION QoS policy allows you to control
how a Subscriber sorts
and orders the received samples in the DataReader's queue.
This policy controls the behavior of the DataReader with regards to the lifecycle of the
data instances it manages, that is, the data instances that have been received and for
which the DataReader maintains some internal resources.
This RELIABILITY QoS policy determines whether or not data
published by a
DataWriter will be reliably delivered by RTI Connext to matching
DataReaders.
This SERVICE QoS policy Service QoS policy is used to indicate
what kind of service is associated with the DDS entity.
This QoS policy determines the DataWriter's publishing mode,
either asynchronous or synchronous.
The publishing mode controls whether data is written synchronously in the context of
the user thread when calling write(), or asynchronously in the context of a separate
thread internal to RTI Connext.
The RESOURCE_LIMITS QoS policy controls the memory resources
that RTI Data Distribution
Service allocates and uses for DataWriter or DataReader. One of the most important
fields is max_samples, which sets the size and causes memory to be allocated for the
send or receive queues.
This TIME_BASED_FILTER QoS policy allows you to specify that
data should not be delivered more than once per-specified
period for each data instance, regardless of how fast
DataWriters are publishing new samples of the data instance.
This QoS policy provides an area where your application can
store additional information
related to the Topic. This information is passed between applications during discovery
using built-in topics.
How this information is used will be up to user code. RTI Connext does
not do anything with the information stored as TOPIC_DATA except to pass it to other
applications.
The TRANSPORT_PRIORITY QoS policy allows the user application
to take advantage
of transports that are capable of sending messages with different priorities.
This QoS policy provides an area where your application can
store additional information
related to a DomainParticipant, DataWriter, or DataReader. This information is passed
between applications during discovery using built-in-topics. How this information is used
will be up to user code.
RTI Connext does not do anything with the information stored as
USER_DATA except to pass it to other applications.
This QoS policy determines if the DataWriter will dispose an instance when it is unregistered.
When a DataWriter unregisters an instance, it means that this particular DataWriter has
no more information/data on this instance. When an instance is disposed, it means that
the instance is "dead"-there will no more information/data from any DataWriter on
this instance.
<<RTI Extension>>
<<RTI Extension>>
Resource limits that apply only to DataReader instances.
<<RTI Extension>>
Resource limits that apply only to DataWriter instances.
<<RTI Extension>>
This QoS policy is used to partition the data published by a
DataWriter across multiple
channels . A channel is defined by a filter expression and a sequence of multicast locators.
<<RTI Extension>>
The PROPERTY QoS policy can be used to associate a set of
properties in the form of
(name,value) pairs with a DataReader, DataWriter, or DomainParticipant. This is similar to
the USER_DATA QoS policy, except this policy uses
(name, value) pairs, and you can
select whether or not a particular pair should be propagated
(included in the built-in topic).
<<RTI Extension>>
The purpose of this QoS is to allow the user to attach naming information to created
Entity objects.
It can only be 255 characters in length.
<<RTI Extension>>
Protocol that applies only to DataReader instances.
<<RTI Extension>>
<<RTI Extension>>
Protocol that applies only to DataWriter instances.
<<RTI Extension>>
This QoS policy can be used to decrease the amount of
communication overhead associated
with the transmission and (in the case of reliable communication) acknowledgment
of small samples in order to increase throughput.
<<RTI Extension>>
The DISCOVERY QoS configures how DomainParticipants discover each other on the
network.
<<RTI Extension>>
The DISCOVERY_CONFIG QoS policy is used to tune the discovery
process. It controls
how often to send discovery packets, how to determine when participants are alive or
dead, and resources used by the discovery mechanism.
<<RTI Extension>>
The DOMAIN_PARTICIPANT_RESOURCE_LIMITS QoS policy configures
the
resources used by a DomainParticipant. Many of these resources are used by the internal
RTI Connext database to store information about locally and remotely
created DDS Entities. Some of the parameters configure the data structures used to
search through the database efficiently. Finally, there are parameters that limit the sizes
of variable-length data fields.
<<RTI Extension>>
The WIRE_PROTOCOL QoS policy configures some Real-Time
Publish Subscribe
(RTPS) protocol-related properties for the DomainParticipant. The open RTPS protocol is
used by RTI Connext to format and interpret messages between Domain-
Participants.
<<RTI Extension>>
The EVENT QoS policy configures the internal RTI Data
Distribution Service Event thread.
The purpose of the Event thread is described in Event Thread.
<<RTI Extension>>
The RECEIVER_POOL QoS policy configures the internal RTI Data
Distribution Service
thread used to process the data received from a transport.
<<RTI Extension>>
Built-in topic reader's resource limits.
Defines the resources that can be used for a built-in-topic data reader.
A built-in topic data reader subscribes reliably to built-in topics containing
declarations of new entities or updates to existing entities in the domain.
Keys are used to differentiate among entities of the same type.
RTI Connext assigns a unique key to each entity in a domain.
<<RTI Extension>>
This QoS policy is used to enable or disable asynchronous
publishing and asynchronous
batch flushing for the Publisher.
If enabled, the Publisher will spawn two threads, one for asynchronous publishing and
one for asynchronous batch flushing.
<<RTI Extension>>
The DATABASE QoS policy configures the internal "database"
(thread and data structures)
used by RTI Connext to hold information about locally created
DDS entities and remote entities that are discovered through the discovery process.
<<RTI Extension>>
This QoS policy controls the creation and use of Exclusive
Areas. An exclusive area (EA)
is a mutex with built-in deadlock protection when multiple EAs are in use. It is used to
provide mutual exclusion among different threads of execution. Multiple EAs allow
greater concurrency by the internal and user threads when executing RTI Data Distribution
Service code.
<<RTI Extension>>
The TRANSPORT_BUILTIN QoS policy specifies which built-in
transports can be used
by the DomainParticipant. RTI Connext provides two built-in transports,
UDPv4 and shared memory. UDPv4 uses the IPv4 UDP protocol to send and receive
messages. The shared memory transport uses system shared memory for inter-process
communications.
<<RTI Extension>>
The TRANSPORT_SELECTION QoS policy allows you to select the
transports that have
been installed with the DomainParticipant to be used by the DataWriter or DataReader.
<<RTI Extension>>
The TRANSPORT_UNICAST QoS policy allows you to specify
unicast network
addresses to be used by DomainParticipant, DataWriters and DataReaders for receiving
messages. DomainParticipants receive messages to support the discovery process.
DataWriters may receive ACK/NACK messages to support the reliable protocol.
<<RTI Extension>>
The MULTICAST_MAPPING QoS policy allows you to specify
a list of multicast addresses
to be used by DataReaders for receiving
messages. The address is choosed using the topicname.
<<RTI Extension>>
This QoS policy allows you to specify network multicast
addresses to be used by
DataWriters when sending data samples to this DataReader.
<DISALLOW_TYPE_COERCION|ALLOW_TYPE_COERCION>
The DataWriter and the DataReader must support the same data type
in order for them to communicate.
The DataWriter and the DataReader need not support the same data type
in order for them to communicate as long as the reader’s type is assignable from the writer’s type
The Type Consistency Enforcement QoS Policy defines the rules for determining whether the type used
to publish a given data stream is consistent with that used to subscribe to it.
<<RTI Extension>>
This QoS policy allows you to associate encapsulation formats
to transport destinations.
<<RTI Extension>>
The Logging QoS policy configures the NDDS Config Logger.
<<RTI Extension>>
QoS policies related to DomainParticipants.
QoS policies related to DomainParticipantFactory.
QoS policies related to Publishers.
QoS policies related to Subscribers.
QoS policies related to Topics.
QoS policies related to DataReaders.
QoS policies related to DataWriters.
This profile groups the QoS policies related to DomainParticipants.
This profile groups the QoS policies related to DomainParticipantFactory.
This profile groups the QoS policies related to Topics.
This profile groups the QoS policies related to Publishers.
This profile groups the QoS policies related to Subscribers.
This profile groups the QoS policies related to DataWriters.
This profile groups the QoS policies related to DataReaders.
This profile groups the QoS policies related to DomainParticipants.
This profile groups the QoS policies related to DomainParticipantFactory.
This profile groups the QoS policies related to Topics.
This profile groups the QoS policies related to Publishers.
This profile groups the QoS policies related to Subscribers.
This profile groups the QoS policies related to DataWriters.
This profile groups the QoS policies related to DataReaders.
A QoS profile groups a set of related QoS.
The Qos Library provides a way to group a set of related QoS under a namespace.
The Qos inside a library are further organized into Qos Profiles.
Enumeration type for the specification of Distributed Logger's filter level.
Silent filter level
Fatal filter level
Severe filter level
Error filter level
Warning filter level
Notice filter level
Info filter level
Debug filter level
Trace filter level
Main type for the definition of Distributed Logger configuration.
The filter level to apply to the log messages.
Whether the remote administration of Distributed
Logger is active (true) or not (false).
Whether Distributed Logger should echo log messages to the standard output (true) or not (false).
Whether Distributed Logger should log infrastructure messages.
Thread settings for Distributed Logger.
Size of the Distributed Logger queue for incoming log messages to be written.