Managing interoperability between Connext and other DDS implementations
Connext communicates over the wire using the formal Real-time Publish-Subscribe (RTPS) protocol, an international standard managed by the Object Management Group (OMG). RTPS has been developed from the ground up with performance, interoperability and extensibility in mind. Its purpose and scope are to ensure that applications based on different implementations of DDS can interoperate. Furthermore, the RTPS protocol has built-in extensibility mechanisms that enable new revisions to introduce new message types, extend the existing messages, or extend the Quality of Service settings in the product—without breaking interoperability.
However, speaking the same language doesn’t mean different DDS implementations will have a conversation. Implementation differences, varying levels of support for common features or QoS policies in the specification, additional specifications (such as DDS X-Types or Security), or extended capability beyond the DDS specification can contribute to the challenges when trying to integrate multiple DDS implementations. If you’re struggling with making Connext work with other DDS implementations, rely on the RTI Professional Services team to guide you through the steps and identify risks that may result.
An expert will work with your team to understand your goals for interoperability and create a plan for integrating other DDS implementations. If necessary, this plan may include the development of prototypes or demonstrators to get your team started on the right path.
Note: The RTI Professional Services team are DDS experts, but are not experts about non-RTI implementations of DDS. Some investigation may be necessary to determine if/how Connext can interoperate with your chosen other implementations.
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 be prepared to discuss your data model.
- You must have knowledge about the other DDS implementation with which Connext will integrate.
This service typically is delivered in 4-24 hours.
Remote or Onsite
This activity can be delivered remote or onsite if bundled with other activities.