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).

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.

2214 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:

3792 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.

26426 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.
2014 reads — 0 comments

Note: Applies to Connext DDS 5.3.0 and above.

RTI Admin Console is compatible with RTI Security Plugins. Configuring security in Admin Console will allow you to visualize your secure DDS system. To configure security in Admin Console, follow these steps:

3940 reads — 1 comment

This document describes how to check when the discovery process is completed. The tool that is going to be used is Wireshark. Before the analysis, these are some links that are of interest:

8786 reads — 2 comments
he Modern C++ API for RTI DDS uses shared pointer to implement “reference types,” which include all subclasses of dds::core::Entity, such as DomainParticipant or DataReader, and other classes, such as FlowController, QosProvider. For more information about how different types are implemented, here are the conventions we follow in the API.
4998 reads — 1 comment