Planning the Upgrade

Before the Upgrade

Documentation Review

Before starting the upgrade, you should review the following documents:

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.

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:

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:

  1. Stop All Application Instances and Connections
  2. Backup Your Installation
  3. Install the New Application Version
  4. Configure the New Application
  5. Start one New Application Instance
  6. Upgrade the Repository
  7. Upgrade the Data Locations
  8. Restart All Application Instances

Out-of-Place Upgrade

The upgrade path is as follows:

  1. Stop All Application Instances and Connections
  2. Backup Your Installation
  3. Duplicate your Repository and Data Location
  4. Install the New Application Version
  5. Configure the New Application
  6. Start one New Application Instance
  7. Upgrade the Repository
  8. Upgrade the Data Locations
  9. Restart All Application Instances