RTI Routing Service
6.0.1
Contents
1. Introduction
1.1. How To Read This Manual
1.2. Paths Mentioned in Documentation
1.3. Files Mentioned in Documentation
2. Core Concepts
2.1. Resource Model
2.1.1. Directory
2.1.2. Service
2.1.2.1. Plugin Interaction
2.1.2.2.
Service
States
2.1.3. DomainRoute
2.1.3.1.
DataReader
States
2.1.4. Connection
2.1.4.1. Plugin Interaction
2.1.4.2.
Connection
States
2.1.4.3. Type Registration
2.1.5. Session
2.1.5.1. Plugin Interaction
2.1.5.2.
Session
States
2.1.6. Route
2.1.6.1. Plugin Interaction
2.1.6.2.
Route
States
2.1.7. AutoRoute
2.1.7.1.
AutoRoute
States
2.1.8. Input
2.1.8.1. Plugin Interaction
2.1.8.2.
Input
States
2.1.9. Output
2.1.9.1. Plugin Interaction
2.1.9.2.
Output
States
2.2. Builtin plugins
2.2.1. DDS Adapter
2.2.1.1. DDS AdapterPlugin
2.2.1.2. DDS Connection
2.2.1.3. DDS Session
2.2.1.4. DDS StreamReader
2.2.1.5. DDS StreamWriter
2.2.2. Forwarding Processor
3. Usage
3.1. Command-Line Executable
3.1.1. Starting Routing Service
3.1.2. Stopping Routing Service
3.1.3. Routing Service Command-Line Parameters
3.2. Routing Service Library
3.2.1. Example
4. Configuration
4.1. Configuring Routing Service
4.2. Terms to Know
4.3. How to Load the XML Configuration
4.4. XML Syntax and Validation
4.5. XML Tags for Configuring RTI Routing Service
4.5.1. Routing Service Tag
4.5.1.1. Example: Specifying a configuration in XML
4.5.2. Administration
4.5.3. Monitoring
4.5.3.1. Monitoring Configuration Inheritance
4.5.4. Domain Route
4.5.4.1. Example: Mapping between Two DDS Domains
4.5.4.2. Example: Mapping between a DDS Domain and raw Sockets
4.5.5. Session
4.5.6. Route
4.5.7. Input/Output
4.5.7.1. Creation Modes
4.5.7.2. Specifying Types
4.5.7.3. Data Transformation
4.5.8. Auto Route
4.5.9. Plugins
4.6. Enabling Distributed Logger
4.7. Support for Extensible Types
4.7.1. Example: Samples Published by Two Writers of Type A and B, Respectively
4.8. Support for RTI FlatData and Zero Copy Transfer Over Shared Memory
4.8.1. Example: Configuration to enable both FlatData and zero-copy transfer over shared memory
5. Remote Administration
5.1. Overview
5.1.1. Enabling Remote Administration
5.1.2. Available Service Resources
5.1.2.1. Example
5.1.3. Resource Object Representations
5.2. API Reference
5.2.1. Remote API Overview
5.2.2. Service
5.2.3. DomainRoute
5.2.4. Connection
5.2.5. Session
5.2.6. AutoRoute
5.2.7. Route
5.2.8. Input/Output
5.3. Example: Configuration Reference
6. Monitoring
6.1. Overview
6.1.1. Enabling Service Monitoring
6.1.2. Monitoring Types
6.2. Monitoring Metrics Reference
6.2.1. Service
6.2.2. DomainRoute
6.2.3. Session
6.2.4. AutoRoute
6.2.5. Route
6.2.6. Input/Output
7. Software Development Kit
8. Propagating Content Filters
8.1. Enabling Filter Propagation
8.2. Filter Propagation Behavior
8.3. Filter Propagation Events
8.4. Restrictions
9. Topic Query Support
9.1. Dispatch Mode
9.2. Propagation Mode
9.3. Restrictions
10. Traversing Wide Area Networks
10.1. TCP Configuration elements
10.1.1. TCP Transport Initial Peers
10.1.1.1. Example: Setting discovery peers for TCP wan/lan
10.1.2. TCP Transport Property
10.2. Support for External Hardware Load Balancers in TCP Transport Plugin
11. Tutorials
11.1. Starting Shapes Demo
11.2. Example: Routing All Data from One Domain to Another
11.3. Example: Changing Data to a Different Topic of Same Type
11.4. Example: Changing Some Values in Data
11.5. Example: Transforming the Data’s Type and Topic with an Assignment Transformation
11.6. Example: Transforming the Data with a Custom Transformation
11.7. Example: Using Remote Administration
11.8. Example: Monitoring
11.9. Example: Using the TCP Transport
11.10. Example: Using a File Adapter
11.11. Example: Using a Shapes Processor
12. Common Infrastructure
12.1. Application Resource Model
12.1.1. Example: Simple Resource Model of a Connext DDS Application
12.1.2. Resource Identifiers
12.1.2.1. Escaped Identifiers
12.1.2.2. Example: Resource Identifiers of a Generic Connext DDS Application
12.1.2.3. Example: Resource Identifiers Generated from XML Entity Model
12.2. Remote Administration Platform
12.2.1. Remote Interface
12.2.1.1. Standard Methods
12.2.1.2. Custom Methods
12.2.2. Communication
12.2.2.1. Reply Sequence
12.2.2.2. Example: Accessing from Connext DDS Application
12.2.3. Common Operations
12.2.3.1. Create Resource
12.2.3.2. Get Resource
12.2.3.3. Update Resource
12.2.3.4. Set Resource State
12.2.3.5. Delete Resource
12.3. Monitoring Distribution Platform
12.3.1. Distribution Topic Definition
12.3.1.1. Example: Monitoring of Generic Application
12.3.2. DDS Entities
12.3.3. Monitoring Metrics Publication
12.3.3.1. Configuration Distribution Topic
12.3.3.2. Event Distribution Topic
12.3.3.3. Periodic Distribution Topic
12.3.4. Monitoring Metrics Reference
12.3.4.1. Statistic Variable
12.3.4.2. Host Metrics
12.3.4.3. Process Metrics
12.3.4.4. Base Entity Resource Metrics
12.3.4.5. Network Performance Metrics
12.4. Plugin Management
12.4.1. Shared Library
12.4.1.1. Configuration
12.4.2. Service API
13. Release Notes
13.1. Supported Platforms
13.2. Compatibility
13.3. What’s New in 6.0.1
13.3.1. New platforms
13.3.2. Removed platforms
13.3.3. Earlier detection of invalid configurations
13.3.4. Added Support for Proxy of TopicQueries in Routes with Multiple Inputs and Outputs
13.4. What’s Fixed in 6.0.1
13.4.1. QoS Topic Filters were not supported
13.4.2. Executable did not log build ID for DDS libraries
13.4.3. Remote create operation failed with resource identifiers formatted as noted in User’s Manual
13.4.4. Unbounded generation of file handles if monitoring enabled on QNX platforms
13.4.5. Inconsistent state if remote operation performed on disabled DomainRoute
13.4.6. Changing Session period through Route’s API updated the period, but with a delay
13.4.7. Added operations in Processor API to access DataReader/Writer of a DDS input/output
13.4.8. Unexpected routes created after disabling and enabling AutoRoutes
13.4.9. Routing Service failed to detect configuration with duplicate names
13.4.10. Executable always ignored logging QoS
13.4.11. Out of memory error if Monitoring enabled on QNX platforms
13.4.12. Segmentation fault when reading from custom processor if underlying StreamReader didn’t return SampleInfo list
13.4.13. Failure to remotely create entity resulted in XML object inserted in loaded DOM
13.4.14. Undefined behavior if entity names contained characters “:” or “/”
13.4.15. XML variables outside of <routing_service> were not expanded
13.5. Previous releases
13.5.1. What’s New in 6.0.0
13.5.1.1. New platforms
13.5.1.2. Support for multiple connections in a domain route
13.5.1.3. Support for multiple inputs and outputs in routes or topic routes
13.5.1.4. Support for C++ Adapter, Transformation and Service APIs
13.5.1.5. New pluggable processor API
13.5.1.6. Redesigned remote administration architecture
13.5.1.7. Redesigned remote monitoring architecture
13.5.1.8. Support for advanced logging
13.5.1.9. Support for XML variables expansion from command-line and service API
13.5.1.10. Paused and disabled state is cleared after disabling an entity
13.5.1.11. Removed warning caused by multiple registrations of a type
13.5.2. What’s Fixed in 6.0.0
13.5.2.1. Remotely disabling TopicRoute/Route could fail while forwarding data
13.5.2.2. Routing Service in debug mode did not link with debug version of Distributed Logger
13.5.2.3. Route stream matching not applied correctly in presence of certain partitions
13.5.2.4. Crash on shutdown if types provided through both discovery and XML
13.5.2.5. Sample loan not returned to DDS input upon DDS_DataReader::get_key() failure
13.5.2.6. Enabling monitoring through ServiceProperty::enable_monitoring only worked if <monitoring> tag present
13.5.2.7. Logged message included inaccurate number of dropped samples
13.5.2.8. Deserialization errors may have occurred under some conditions
13.5.2.9. TopicRoutes with TopicQuery proxy mode enabled forwarded live data only to first output
13.5.2.10. Routing Service Java API did not work with some TypeCodes
14. Copyrights
RTI Routing Service
Docs
»
12. Common Infrastructure
View page source
12. Common Infrastructure
¶
12.1. Application Resource Model
12.1.1. Example: Simple Resource Model of a Connext DDS Application
12.1.2. Resource Identifiers
12.2. Remote Administration Platform
12.2.1. Remote Interface
12.2.2. Communication
12.2.3. Common Operations
12.3. Monitoring Distribution Platform
12.3.1. Distribution Topic Definition
12.3.2. DDS Entities
12.3.3. Monitoring Metrics Publication
12.3.4. Monitoring Metrics Reference
12.4. Plugin Management
12.4.1. Shared Library
12.4.2. Service API