HOWTOs

This page contains a set of short informal recipes to help you solve common challenges you may face when using RTI Connext DDS. This recipes include topics such as configuring favorite IDE to work with our libraries, tuning the performance of your application, or configuring your firewall to let DDS traffic through.

You can contribute by commenting on existing HOWTOs or creating your own here (requires logging in).

This article discusses the various problems and possible solutions to a design pattern you may encounter when architecting your DDS-based application.

The example shown in this document is using the traditional C++ API.

In a Data-centric distributed application where your system data model is shared with the middleware, you may want to share only part of the information that each individual application is maintaining. 

36 reads — 0 comments

When you use RTI Connector, all the types, topics, domain, and entities must be defined in an XML file that gets loaded when the Connector object is created.

For example, the following snippet loads the required definitions from "config.xml" and then instantiates a new Connector object for the domain participant "MyParticipant" defined in the participant library "MyParticipantLib"

const rti = require('rticonnextdds-connector');
var connector = new rti.Connector("MyParticipantLib::MyParticipant", "config.xml");

 

545 reads — 0 comments

This document describes all the steps required to use a hardware Trusted Platform Module (TPM) version 2.0 to protect the identity of domain participants in a system built on top of RTI Connext DDS Secure.

The attached PDF gives step by step instructions on how to use the TPM 2.0 chip available in many business-class PCs. Note that older computers might have a chipset implementing the older specification of the TPM (1.2). Refer to the separate HOWTO document to work with TPM 1.2.

632 reads — 0 comments

The attached PDF describes all the steps required to use a hardware Trusted Platform Module (TPM) version 1.2 to protect the identity of domain participants in a system built on top of RTI Connext DDS Secure.

497 reads — 0 comments

ContentFilteredTopics allow a DataReader to receive only samples that pass a filter expression. The user application doesn’t know whether a sample has been filtered; nor does it know one detail that may affect performance: the filtering can be applied on either the DataWriter side or the DataReader side.

When the DataReader filters:

1169 reads — 1 comment

If you are a Windows user and have ever needed to capture traffic from the loopback interface, you will probably have struggled to do so. Wireshark won't let you do it.

4569 reads — 1 comment
 
We are excited that you are looking forward to working with Connext 6! 
Some users may have questions about the compatibility of pre-existing license files with the latest Connext release. Fortunately, this is fairly straight forward.
939 reads — 0 comments

Pages