2.1. Supported Platforms

A platform refers to the combination of your target machine’s OS version, CPU, and toolchain (compiler or Visual Studio). Each platform has an RTI architecture name, which is a shorthand way to identify the platform. The “target” is the machine where you will deploy your completed application. (As opposed to a “host”, which is where you will be developing the application.)

For example, if you have a 64-bit Windows machine with Visual Studio® 2017, the architecture name is x64Win64VS2017. For a 64-bit Linux machine with gcc version 7.3.0, the architecture name is x64Linux4gcc7.3.0.

The first table lists the supported operating systems and their architecture names in this release.

Once you know your architecture name, use the following tables to see which products/features are supported. You will also need to know your architecture name when downloading/installing various Connext libraries.

These table have columns that show you the supported products/features for each architecture supported in this release. A ● means supported in this release, an empty cell means unsupported in this release.

Note: You may need to scroll down to the end of each table and then scroll to the right in order to see all the content.

Footnotes for the above tables: Section 2.1.9 Footnotes

Other platform-specific information is in the RTI Connext Core Libraries Platform Notes.

2.1.1. RTI Architecture Names

Table 2.1 RTI Architecture Names

Operating System

OS Version

CPU

Compiler/Toolchain

RTI Architecture [2]

Standard Target Libraries

Windows (Intel)

Windows 10 [6], 11;

Windows Server 2016, 2022

x64

VS2017, VS2019, VS2022

x64Win64VS2017

macOS

macOS 11, 12, 13, 14

ARM64

clang 12.0, 13.0, 14.0, 15.0

arm64Darwin20clang12.0

Linux (Intel)

Red Hat Enterprise Linux 8, 9;

Ubuntu 18.04 LTS, 20.04 LTS, 22.04 LTS, 24.04 LTS

x64

gcc 7.3.0

x64Linux4gcc7.3.0 [7]

Source Bundles

n/a

n/a

Docker Images

Linux (Intel)

Ubuntu 22.04 LTS

amd64

gcc 7.3.0

x64Linux4gcc7.3.0

2.1.2. APIs

This table shows which APIs are supported on each architecture.

Table 2.2 APIs

Operating System

RTI Architecture [2]

Java [20]

Python [16]

.NET (C#) [19]

C/C++

Modern C++ [5][10]

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

●

●

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

●

Source Bundles

n/a

n/a

●

●

●

●

●

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

2.1.3. Transports

This table shows the which transports are supported on each architecture.

Table 2.3 RTI Transports

Operating System

RTI Architecture [2]

UDP/IPv4

UDP/IPv6

Multicast

TCP/IPv4

Shared Memory (w/ zero copy) [14]

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

● [4]

●

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

●

Source Bundles

n/a

n/a

●

●

●

●

●

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

2.1.4. Infrastructure Services

This table shows which RTI Infrastructure Services are supported on each architecture.

Table 2.4 RTI Infrastructure Services

Operating System

RTI Architecture [2]

Persistence Service [3]

Routing Service

Recording & Replay Services

Web Integration Service

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

●

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

Source Bundles

n/a

n/a

●

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

2.1.5. Other Connext Professional Libraries

This table shows other libraries provided with Connext Professional and which platforms support them.

Table 2.5 Other RTI Connext Professional Libraries

Observability Framework

Other Libraries

OS

RTI Architecture [2]

Observability Collector Service

Monitoring Library 2.0

Request/Reply

Monitoring Library

Distributed Logger

LBED [18]

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

●

●

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

●

●

Source Bundles

n/a

n/a

●

●

●

●

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

● [21]

2.1.6. Core Library Features

This table shows features of the Core Libraries.

Table 2.6 Core Library Features

Operating System

RTI Architecture [2]

Monotonic Clock

CPU Core Affinity

Durable writer history & reader state

RTI DDS thread name

Backtrace [11]

Cmake Find Package

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

●

● [13]

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

● [12]

●

Source Bundles

n/a

n/a

●

●

●

●

●

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

2.1.7. Tools

This table shows which RTI Tools are supported on each architecture.

Table 2.7 RTI Tools

Operating System

RTI Architecture [2]

Shapes Demo

Launcher

Monitor

Admin Console

System Designer

rtiddsgen server 4.4.0

Utilities (rtiddsping, rtiddsspy)

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

●

●

●

● [9]

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

● [17]

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

● [8]

●

●

Source Bundles

n/a

n/a

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

2.1.8. Connext Security Extensions and Other Add-ons

This table shows add-on products and which architectures support them.

Table 2.8 Add-ons

Security Extensions

Other Add-ons

Operating System

RTI Architecture [2]

Security Plugins (for OpenSSL) [1]

Security Plugins (for wolfSSL) [15]

TLS Support [1]

Security Plugins SDK [1][15]

Cloud Discovery Service

Real-time WAN Transport

Standard Target Libraries

Windows (Intel)

x64Win64VS2017

●

●

●

●

●

macOS

arm64Darwin20clang12.0

●

●

●

●

●

Linux (Intel)

x64Linux4gcc7.3.0 [7]

●

●

●

●

●

●

Source Bundles

n/a

n/a

Docker Images

Linux (Intel)

x64Linux4gcc7.3.0

2.1.9. Footnotes

These are the footnotes used in the preceding tables.

Table 2.9 Footnotes for Supported Platforms Tables

1

Tested with OpenSSL 3.0.12 unless stated otherwise.

2

Supports DDS 1.4 and RTPS 2.5.

3

Tested with filesystem only in PERSISTENT mode.

4

No Traffic Class support.

5

Tested with C++11 unless stated otherwise.

6

Per Microsoft, this should be compatible with Windows 10 IoT Enterprise with a Windows native application.

7

This should also work on Wind River Linux 9.

8

Tested on x64 Linux, with Chrome version 112 and Firefox version 108.

9

Tested on x64 Windows 10 only, with Chrome version 112 and Firefox version 108.

10

Supporting Modern C++ means supporting the RPC feature unless otherwise stated.

11

If you want backtrace information: on all Linux architectures, compile with -fno-omit-frame-pointer and add linker flag -rdynamic. For Linux architectures on Arm CPUs, also compile with “-funwind-tables”. On all Windows architectures, you need the Dbghelp.dll and NtDll.dll libraries.

12

For architectures using gcc 6 or higher: to display backtrace information, you must link the executable with “-no-pie” to prevent PIE generation.

13

NOT supported in release mode.

14

Zero-copy transfer over shared memory is NOT supported for Java, Ada, .NET and Python programming languages. It is only supported for C, Traditional C++, and Modern C++ programming languages.

15

Tested with WolfSSL 5.5.1.

16

Tested with Python 3.6-3.11.

17

Tested on ARM64 macOS, with Chrome version 112, Firefox version 108 and Safari version 16.2.

18

Supports dynamic linking only.

19

Built with .NET 6, compatible with .NET 5+ (and newer). Also supported on .NET Core 2.1 (and above) and .NET Framework 4.8.3 (and above).

20

Built with AdoptOpenJDK 17.0.6, compatible with Java 8 and above.

21

You need a license file to run this container image. (https://hub.docker.com/r/rticom/collector-service/)