# Upgrading Avantra

As with all enterprise software, Avantra will require maintenance during its use in the form of patches, upgrades and other administrative tasks. We typically launch a new major version of Avantra once per year along with 3-6 minor functionality versions and a number of bug-fixing patches. This section will guide you through our versioning and compatibility process.

## Versioning

Avantra consists of several software components. Each of these components has a particular version number, and the whole Avantra suite has a major version number as well.

Major Version

The full major version number for Avantra always has the format `[major].0.0`. The major Avantra version described in this document is 23. We also use the term release as a synonym for a major version. We typically release one major version per year.

Minor Version

Every Avantra component has a minor version number in format `[major].[minor].[patch-level]`. The `[minor]` version denotes the functionality release (of which there are usually several throughout the year). For each minor release, the `[patch-level]` is reset to zero.

Patch Number

Each minor version can have zero or more bug-fix patches to rectify code issues or deliver patches to existing functionality as required.

The details of what is each version can be found in the Release Notes.

## Version Compatibility

As a general rule, all Avantra components sharing the same `[major].[minor]` version prefix are compatible to each other, regardless of the particular patch level. Also, as a general rule, components having a different `[major].[minor]` version prefix are not compatible!

In order to support smooth version upgrades Avantra Server components ensure a certain degree of compatibility to Avantra Agents with a lower `[major].[minor]` version number. This is described in a more formal way in the Release Notes. The rule here is that your Avantra Server should be at the highest version followed by the Avantra Agent version.

| You must not install an Avantra Agent with a higher `[major].[minor]` version number than the `[major].[minor]` version number of the Avantra Server components!

## Version Upgrades vs Applying Patches

Applying Patches

When we talk about applying patches we mean to replace a particular Avantra component with one that shares the same `[major].[minor]` version number except for the `patch-level`..

Version Upgrades

When we talk about version upgrades or (short) upgrades we mean to lift the whole Avantra installation from one `[major].[minor]` or `[major]` version to the next.

## SAP Transport Versions & Upgrades

All Avantra transports, both for monitoring and automation, have a version number in the form `[major].[minor].[patch-level].[build-number]`. The major, minor and patch-level will match the Avantra Server and Avantra Agent version numbers at the point of release and the `build-number` will be specific to the SAP Transport in question.

Not every Avantra release will include updates to the SAP Transports and, where possible, all transports are backward compatible which allows you to upgrade your Server and Agents independent of your SAP Transports. If the latest Avantra release comes with new transport requests it will be listed under the contributions in the download area.

Please make sure to read the release notes prior to upgrades to ensure you are aware of any compatibility notices.

## Java Runtime

Before completing an upgrade of any Avantra component (server or agent), we strongly recommend that you upgrade your Java runtime environment at the same time (ideally before the upgrade). Bringing your Java runtime up to the latest patch version of the current major release can improve security and also reduce support issues.

| If you are running an outdated Java runtime (greater than 6 months old) and you raise a support request with Avantra, you will be requested to bring your Java runtime up to the latest patch level to rule out compatibility issues.