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


In today's technological landscape, addressing security concerns and implementing robust policies in distributed applications is crucial. 

136 reads — 0 comments
Over the past decade, containerization has captured the attention of the engineering community across all verticals due to the compelling benefits it offers to software development, security, and operations (DevSecOps) teams. Containerization enhances and accelerates DevSecOps by promoting software consistency, test automation, fault reproducibility and early detection of security vulnerabilities, ultimately leading to more robust and secure service deployments.
300 reads — 0 comments
Most RTI environments rely on specific environmental variables to be set, the most popular being NDDSHOME. Environmental variables are used for building DDS applications and for picking up QoS Files. This article discusses basic environmental variables used for building and linking.
448 reads — 0 comments
The Connext DDS Platform provides several tools and mechanisms to help troubleshoot distributed DDS applications. This solution links the most commonly used.
258 reads — 0 comments
This solution lists some of the common reasons applications may use too much memory.
243 reads — 0 comments
This article links documents that explain how to tune discovery to minimize the impact one the system, especially for large-scale systems, as well as additional resources to understand how DDS discovery works and its impact on the overall system.
340 reads — 0 comments
Common reasons why an application may be running with a QOS different from what is intended. The observed result could be that the application runs with the wrong QOS values which could result in behavioral changes and/or other issues (e.g. request-offered incompatibility).
326 reads — 0 comments