The RTI TCP Transport enables communication between RTI Data Distribution Service applications using TCP. The communication can be either over a LAN or over a WAN.
RTI TCP Transport enables participant discovery and data exchange using the TCP protocol either on a LAN, or over the public WAN. RTI TCP Transport enables RTI Data Distribution Service to address the challenges of using TCP as a low-level communication mechanism between peers and limits the number of exposed ports to one. When using the default UDP transport, an RTI Data Distribution Service application uses multiple UDP ports for communication, which may make it unsuitable for deployment across firewalled networks.
There are two ways in which this transport can be configured:
Refer to Configure TCP Transport with Property QoS Policy for the predefined property strings.
With this first approach, RTI Data Distribution Service will dynamically load the TCP transport library at run time and then implicitly create and register the transport plugin.
Refer to NDDS_Transport_TCPv4_new for information on how to create a new TCP transport instance.
Refer to NDDS_Transport_Support_register_transport for documentation on how to register the transport instance with RTI Data Distribution Service.
To use this second approach, you need access to the TCP Transport Plugin API at compile time. Your application will have to include the following header file:
#include "ndds/transport_tcp/transport_tcp_tcpv4.h"
(The above path assumes that RTI TCP Transport is installed in the same directory as RTI Data Distribution Service.)
Regardless of which way is used to configure the TCP transport, you will need to specify TCP as the transport in the initial peers. See TCP Transport Initial Peers for details.