An upgrade is when you install the new version of Identity Manager on the existing server. To install Identity Manager, you must upgrade the current versions of the operating system and eDirectory to the supported versions for Identity Manager 4.0.1. For a list of the supported platforms, see System Requirements
in the Identity Manager 4.0.1 Framework Installation Guide.
The are several advantages to performing an upgrade:
No new hardware
No migration of data
There are also disadvantages to performing an upgrade:
Downtime when eDirectory is updated and is restarted
There are certain scenarios when an upgrade is not feasible, or when multiple upgrades must be performed. Because Identity Manager 3.5.x and later are the only supported migration paths, these are the only versions that are described in the following scenarios.
The only supported situation for an upgrade is to have Identity Manager 3.5.x or Identity Manager 3.6.x on a supported operating system. However, there are some scenarios where an upgrade is not feasible. The following are some examples:
Unsupported OS: If the current version of the operating system is not supported by Identity Manager 4.0.1, the only supported upgrade path is to perform a migration to a new server.
Identity Manager 3.0.x: If the current version of Identity Manager is 3.0.x, you cannot perform a direct upgrade. The two options are:
Perform an upgrade to Identity Manager 3.5.x, upgrade to eDirectory 8.8.6, then perform an upgrade to Identity Manager 4.0.1.
Perform a migration to a new server.
Roles Based Provisioning Module: If you have the Roles Based Provisioning Module installed, you cannot perform an upgrade. You must perform a migration. For more information see the Identity Manager 4.0.1: RBPM and Reporting Migration Guide.
IMPORTANT:If Identity Manager 3.6.x is installed into an existing RBPM 3.7 system, the 3.6.1 Roles driver (which was launched automatically and silently by the Identity Manager 3.6.x installer) causes the nrfLocalizedNames and nrfLocalizedDescrs attributes setting to change from case‐ignore string to case‐exact string and overwrites the objects which results in a non‐functional RBPM 3.7 system. When the environment becomes non-functional, the only way to correct it is to utilize a back-up of the driver that was created before the current launching of the Identity Manager 3.6.x installer. For more information on restoring Invalidated User Application Drivers, see Restoring Invalidated User Application Drivers
If you are performing an upgrade, proceed to Section 4.0, Performing an Upgrade.