Skip to main content

Upgrading to This Release

This section contains specific instructions applicable to upgrading to this major release. These instructions supplement Upgrading from an Earlier Version in the Installation Guide.

If you are upgrading to this release from a version prior to the last major release, you should also refer to the upgrade instructions for the last major releaseOpens in a new tab, as well as any other major release which your upgrade skips over.

TLS Changes

InterSystems IRIS for Health 2020.2 through 2020.4 contained the new OpenSSLOpens in a new tab 1.1.1 security libraries with TLS 1.3, it was removed from 2021.1, but this release restores support of these libraries. These libraries are supported but are not included in the product distribution.

C Runtime Requirements on AIX

Health Connect on AIX is compiled using the IBM XL C/C++ for AIX 16.1.0 compiler. If the system on which you are installing InterSystems IRIS for Health does not have the corresponding version of the runtime already installed, you must install it.

Upgrading Containers

Because a containerized application is isolated from the host environment, it does not write persistent data; whatever it writes inside the container is lost when the container is removed and replaced by a new container. Therefore, an important aspect of containerized application deployment is arranging for data to be stored outside of the container and made available to other and future containers.

The durable %SYS features enables persistent storage of instance-specific data — such as user definitions, audit records, and the log, journal, and WIJ files — when InterSystems IRIS for Health is run in a container, allowing a single instance to run sequentially in multiple containers over time. For example, if you run an InterSystems IRIS for Health container using durable %SYS, you can upgrade the instance by stopping the original container and running a new one that uses the instance-specific data created by the old one. For information about upgrading, see Upgrading InterSystems IRIS for Health Containers; for detailed information on durable %SYS, see Durable %SYS for Persistent Instance Data.

Important:

In this release, the distribution container has a nonroot default user. This improves the security of your container. If you are using a durable %SYS from a 2019.2 release or earlier instance, you need to change some file ownerships in the host’s durable directory before running InterSystems IRIS for Health 2022.1. Please contact your InterSystems sales engineer or the InterSystems Worldwide Response CenterOpens in a new tab for instructions on changing the file ownerships. If you do not make these changes, the container will encounter an error starting InterSystems IRIS for Health.

FeedbackOpens in a new tab