Managing and configuring QoS policies

RTI Connext is a data-centric software framework for distributing and managing real-time data. It allows applications and devices to work together as one, integrated system. The databus simplifies application and integration logic with a powerful data-centric paradigm: instead of exchanging messages, software components communicate via shared data objects.

Where the databus differs from other technologies is that you can define not only the schema but also the behavior of your data. Quality of Service (QoS) policies enable you to configure how communication occurs (such as rate and reliability), to limit resources, to detect system incompatibilities and setup error handling routines. But without deliberate planning, it can be easy to create inefficient or confusing policies that result in unexpected behavior. Our experience working with customers has shown that careful attention to QoS configuration and organization can simplify and accelerate your development efforts.

What's Involved

First, you and your team will consume the “Quality of Service in Connext” course on RTI Academy. Next, an expert will work with your team to understand your data model, system topology, and overall requirements to create and implement a plan for efficient organization of your QoS configuration. The path forward may include some combination of built-in profiles, snippets, custom profiles, and inheritance to simplify your QoS management.

Note: this effort does not provide any time to evaluate the fitness of your QoS policies for a given flow; the focus is on managing the use of QoS policy configuration.


The following criteria must be met before you can schedule this service:

  • You must have previous Connext experience and/or training. You must be familiar with the fundamental DDS concepts such as DDS entities, publish/subscribe APIs, Quality of Service configuration, discovery, transports, and configuration files.
  • You must consume the RTI Academy course prior to the live mentorship session.
  • You must be prepared to discuss your data model.

Expected Duration

This service typically is delivered in 1-3 hours.

Remote or Onsite

This activity can be delivered remote or onsite if bundled with other activities.

***Please note that RTI has restrictions for onsite services. If you are interested in onsite services, contact your Customer Success Manager to determine if your onsite request can be satisfied.***