2. Upgrading RTI Connext
2.1. Upgrading to a Major Release
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:
The Migration Guide contains information about changes in your new release that may break previous functionality.
2.2. Upgrading to a Patch Release
For instructions on upgrading to a four-digit Connext patch release, see the instructions, including the release notes supplement, that come with the patch. See also Special Backup of RTI Libraries, below.
2.2.1. Special Backup of RTI Libraries
The following information applies only if you are installing a patch release (a release with four digits, such as 7.3.0.1) into an existing installation directory. It does not apply if you are installing a patch release into a new directory. See the instructions that come with your patch release to know whether it’s okay to install into an existing directory or you should install into a new one. You should almost never install a three-digit release into an existing installation directory.
2.2.1.1. Overwriting Libraries
When installing a new RTI package that overwrites a given library in the
<NDDSHOME>/lib/<architecture> directory, the installer will copy the
library from the <NDDSHOME>/lib/<architecture> directory to the
<NDDSHOME>/lib/<architecture>/<current_installed_version> directory.
This copy will serve as a backup.
For example, if you install patch version 7.3.0.1 to the RTI Core Libraries for x64Win64VS2017, your overwritten core 7.3.0 libraries will be copied into the following directory before the 7.3.0.1 libraries are installed: <NDDSHOME>/lib/x64Win64VS2017/7.3.0.
If you install another patch later, before the 7.3.0.1 libraries are overwritten, then the 7.3.0.1 libraries will be copied into <NDDSHOME>/lib/x64Win64VS2017/7.3.0.1.
2.2.1.2. Installing Add-on Products when Using RTI Tools
RTI Tools commonly rely on the backup directory, so it is important to make sure its contents are correct, especially when you are using add-on products, such as Security Plugins. To ensure the backup contents are correct, do the following:
Before installing a new patch (e.g., 7.3.0.1) that contains an
add-on product, such as Security Plugins, always install the base
<version>, such as 7.3.0 (for example,
rti_security_plugins-<version>-host-<crypto library>-<architecture>.rtipkg), of
the add-on product, if you haven’t already, before installing the
patch release version (for example,
rti_security_plugins-<version>.1-host-<crypto library>-<architecture>.rtipkg).
Installing the base version first ensures that when RTI Tools (such as RTI Admin Console and RTI System Designer) are not part of the patch release (they usually are not), they keep using the base libraries they are built with instead of the patched libraries. You will receive an error otherwise.
(The RTI tool will look for the base libraries in the backup directory, such as <NDDSHOME>/resource/app/lib/ x64Win64VS2017/7.3.0. But that backup directory either will not exist or will not contain all of the necessary base libraries if you didn’t install the base version packages first. The tool will then look for the library in the patched directory. But if the patched library uses a function that is not implemented in the core library in the backup directory, an error occurs.)