Planning the Upgrade
Before the Upgrade
Documentation Review
Before starting the upgrade, you should review the following documents:
- The
"Semarchy Convergence for MDM Release Notes" provides the latest information about the Semarchy Convergence Release, including new features and bug fixes.
- The
"Semarchy Convergence for MDM Installation Guide" provides the procedures for installing and configuring Semarchy Convergence for MDM. In this guide, you should review the system requirements for this new release.
- Depending on your current version and the upgrade version, some actions may be required after the upgrade process. Review these
Post-Upgrade Actions before starting the upgrade process.
Understanding Major, Minor and Patch Versions
Version numbers in Convergence for MDM are expressed in the following format:
<major_version>.<minor_version>.<patch_version>
. For example, version 1.3.2.
The upgrade may be a major upgrade, a minor upgrade or a patch. The differences between the old version number and the new version number define the type of upgrade.
- A
Major Upgrade takes place as soon as the major version differs. Major versions include major feature changes, and typically require repository and data locations upgrade. For example, upgrading from
1.3.2 to
2.0.1 is a major version upgrade.
- A
Minor Upgrade takes place when first digit remains the same but the second differs. Minor versions include minor feature changes, and typically require repository and data locations upgrade. For example, upgrading from 2.
0.3 to 2.
1.0 is a minor version upgrade.
- A
Patch is applied when the patch version only differs. Patches do not require repository and data location upgrade. For example, upgrading from 2.0.
0 to 2.0.
3 is patching.
Although the process is the same for all types of upgrade, be aware that the repository and data location upgrade steps may be skipped for patches.
Unless specified otherwise, the upgrade path between two version of Convergence for MDM is direct. You do not need to install intermediate versions.
Select the Upgrade Path
The upgrade supports two paths:
-
In-Place Upgrade consists in installing the new version of Semarchy Convergence for MDM in place of the previous version and upgrading the existing repositories. With this method, you can revert the environment to its original state by restoring the backup of the application folders and database schemas.
-
Out-of-Place Upgrade consists in replicating the existing Convergence for MDM environment and upgrading the copy. The original environment remains unchanged.
You may choose one of the other path for your infrastructure. This choice depends on your IT infrastructure policies for upgrading.
Upgrade Path Overview
In-Place Upgrade
The upgrade path is as follows:
-
Stop All Application Instances and Connections
-
Backup Your Installation
-
Install the New Application Version
-
Configure the New Application
-
Start one New Application Instance
-
Upgrade the Repository
-
Upgrade the Data Locations
-
Restart All Application Instances
-
Post-Upgrade Actions
Out-of-Place Upgrade
The upgrade path is as follows:
-
Stop All Application Instances and Connections
-
Backup Your Installation
-
Duplicate your Repository and Data Location
-
Install the New Application Version
-
Configure the New Application
-
Start one New Application Instance
-
Upgrade the Repository
-
Upgrade the Data Locations
-
Restart All Application Instances
-
Post-Upgrade Actions