Upgrade Overview

There are two upgrade procedures available for upgrading MediationZone; https://infozone.atlassian.net/wiki/spaces/MD94/pages/860356739/Upgrade+Overview#Standard-Upgrade-Procedure and https://infozone.atlassian.net/wiki/spaces/MD94/pages/860356739/Upgrade+Overview#Simplified-Upgrade-Procedure. During a standard upgrade procedure, the currently running system is updated, while in a simplified upgrade, a new system is installed in parallel and the old system is shut down. A simplified upgrade is typically made when skipping major version(s).

Before upgrading to version 9, you need to make https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266, regardless of which type of upgrade is performed, where the configuration is verified since there are changed and removed features.

Necessary preparation step when upgrading to version 9 from version 8.3

Standard Upgrade Procedure

The Standard Upgrade Procedure should be used when persisting runtime data (stored in the file system or database) is critical. This method requires upgrading sequentially through each major version, always upgrading to the latest minor version within each major release to maintain system integrity.

For example, if upgrading from version 8.3.3, the typical upgrade path would be:

8.3.3.x → 9.0.x.x → 9.1.x.x → 9.2.x.x → 9.3.x.x → 9.4.x.x

However, in this release we are allowing an exception from this rule, allowing an upgrade from 8.3.3 directly to 9.4:

8.3.3.x → 9.4.x.x

Rollbacks can be performed using cold backups of the database and file system, ensuring a complete restoration if needed.

See the table below for the upgrade instructions.

Note!

MediationZone 9.4 can only rollback to 9.3 and cannot roll back to 8.3. Therefore, it is essential to create a full backup of configurations, the database, and runtime data before upgrading, as outlined in the Standard Upgrade Procedure.

Standard Upgrade Paths - high level procedure overview

Note!
When upgrading through intermediate versions, starting up each version is not needed. You can proceed directly to the next version and restart the system once you have reached the target version.

Target Start	9.0	9.1	9.2	9.3	9.4

Target Start	9.0	9.1	9.2	9.3	9.4
8.1	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.1 → 8.2 8.2 → 8.3 8.3 → 9.0	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.1 → 8.2 8.2 → 8.3 8.3 → 9.1	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.1 → 8.2 8.2 → 8.3 8.3 → 9.1 9.1 → 9.2	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.1 → 8.2 8.2 → 8.3 8.3 → 9.1 9.1 → 9.2 9.2 → 9.3	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.1 → 8.2 8.2 → 8.3 8.3 → 9.4
8.2	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.2 → 8.3 8.3 → 9.0	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.2 → 8.3 8.3 → 9.1	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.2 → 8.3 8.3 → 9.1 9.1 → 9.2	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.2 → 8.3 8.3 → 9.1 9.1 → 9.2 9.2 → 9.3	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.2 → 8.3 8.3 → 9.4
8.3	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.3 → 9.0	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.3 → 9.1	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.3 → 9.1 9.1 → 9.2	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.3 → 9.1 9.1 → 9.2 9.2 → 9.3	https://infozone.atlassian.net/wiki/spaces/MD94/pages/545194266 8.3 → 9.4
9.0	-	9.0 → 9.1	9.0 → 9.1 9.1 → 9.2	9.0 → 9.1 9.1 → 9.2 9.2 → 9.3	9.0 → 9.1 9.1 → 9.2 9.2 → 9.3 9.3 → 9.4
9.1	-	-	9.1 → 9.2	9.1 → 9.2 9.2 → 9.3	9.1 → 9.2 9.2 → 9.3 9.3 → 9.4
9.2	-	-	-	9.2 → 9.3	9.2 → 9.3 9.3 → 9.4
9.3	-	-	-	-	9.3 → 9.4

Simplified Upgrade Procedure

In a Simplified Upgrade Procedure, a parallel instance of the new version is deployed. The configurations are shut down in the old system and started on the new system. With this approach, the processing downtime is minimised. While configurations can be transferred, runtime data cannot. Unlike the Standard Upgrade Procedure, the Simplified method enables direct upgrades between major versions without requiring intermediate steps.

See the table below for the upgrade instructions.

Simplified Upgrade Paths - high level procedure overview

Target Start	9.0	9.1	9.2	9.3	9.4

Target Start	9.0	9.1	9.2	9.3	9.4
8.1	Simplified Upgrade From 8
8.2
8.3
9.0	-	Simplified Upgrade From 9 Note that typically, a standard upgrade is done from this version, and not a simplified.
9.1	-	-	Simplified Upgrade From 9 Note that typically, a standard upgrade is done from this version, and not a simplified.
9.2	-	-	-	Simplified Upgrade From 9 Note that typically, a standard upgrade is done from this version, and not a simplified.
9.3	-	-	-	-	Simplified Upgrade From 9 Note that typically, a standard upgrade is done from this version, and not a simplified.

Manual Adjustments Required for Upgrades from 8.x to 9.x

Due to differences between the MZ 8 and MZ 9, upgrading may require manual adjustments to the configuration and CI/CD scripts. For example, in MediationZone 8.3, keystore-related fields in an agent configuration could be set in the Workflow Table. However, in MediationZone 9.4, these settings have been moved to the Security Profile configuration, and the Workflow Table no longer supports direct configuration of these fields.

For a detailed list of changes, see https://infozone.atlassian.net/wiki/spaces/PC/pages/7373380 .

Note!

There may be changes to certain agents and functions in the new version. Before upgrading, you should take note of any changes or updates that may have happened to your components, as you may have to modify your configuration before it can work with the newer version. See https://infozone.atlassian.net/wiki/spaces/BUG for detailed information about changes in each release.
The upgrade script does not restrict upgrades from invalid versions. Refer to the table below for the allowed upgrade paths.