2. Upgrading RTI Connext

2.1. Upgrading to a Major Release

You should install a major, three-digit release in a new, clean directory. Never mix and match release versions in the same installation directory.

For instructions on upgrading from one major (three-digit) Connext release to another, see the Migration Guide on the RTI Community Portal (https://community.rti.com/documentation), particularly these sections:

• Upgrade Steps

• Regenerating Code and Updating Your Projects

• The Migration Guide contains information about changes in your new release that may break previous functionality.

2.2. Upgrading to a Patch Release

Follow these instructions for upgrading to a four-digit Connext patch release. See also the release notes supplement that comes with the patch and RTI Connext Professional Patches: FAQ and Use Guidelines.

2.2.1. Patch Installation Instructions

You should install a four-digit patch in a new, clean directory. The basic steps are as follows:

1. Install the patch release host executable in a new directory.

2. Install the patch release target package.

3. Install add-ons: host first, then target.

Attention

If the package has “target” in its name, you must install its corresponding host first. Never install only a target package in any release. Follow these instructions so that you do not mix release versions in the same installation directory.

Using 7.7.0.1 as an example, install the packages as follows:

1. Install the Connext 7.7.0.1 host executable for your platform into a new installation folder (not on top of your current installation):

   rti_connext_dds-7.7.0.1-pro-host-<host_platform>.[run|exe]

2. Use RTI Launcher (or rtipkginstall) from the new installation to install the 7.7.0.1 target package; see Installing the Host and Target:

   rti_connext_dds-7.7.0.1-pro-target-<architecture>.rtipkg

3. (Optional) Install other add-ons that you might be using. For example:

   • rti_security_plugins-7.7.0.1-host-openssl-3.5-<host_platform>.rtipkg, followed by rti_security_plugins-7.7.0.1-target-openssl-3.5-<architecture>.rtipkg

   • rti_connext_dotnet_support-7.7.0.1.rtipkg

   • rti_cloud_discovery_service-7.7.0.1-host-<host_platform>.rtipkg, followed by rti_cloud_discovery_service-7.7.0.1-target-<architecture>.rtipkg

Note

The fourth digit of the patch version is not included in your new (rti_connext_dds-7.7.0) installation folder name. You can confirm that you have successfully installed the patch by checking rti_versions.xml in the rti_connext_dds-7.7.0 folder.

If your build pipeline requires you to install an .rtipkg file in step 1 instead of a .run or .exe file, contact support@rti.com for the .rtipkg file and instructions.

2.2.2. Public Header File Changes

Most four-digit patch releases contain public header file changes that are incompatible with previous releases. Therefore, you should install patches into a new directory (not on top of your current installation). You shouldn’t mix and match packages or products from other releases.

For example, if you are upgrading to 7.7.0.y and you are using Security Plugins with OpenSSL, do not continue using Security Plugins with OpenSSL from 7.7.0 or a previous 7.7.0.x release, but install the Security Plugins package from 7.7.0.y (for example, rti_security_plugins-7.7.0.y-host-openssl-3.5-<host_platform>.rtipkg).

This rule applies to all Connext products supported in 7.7.0, whether or not they are already included in your patch. (If they aren’t, you can request them.)