When you upgrade Identity Manager engine or separately update a SAML method, iMonitor displays both present and not present status flags for SAML methods. You can ignore the not present status flag because eDirectory correctly uses the updated method. When the engine is upgraded, the upgrade process restarts eDirectory that internally takes care of using the updated SAML method. If you separately update a SAML method, manually restart the eDirectory server to use the updated SAML method.
After you upgrade the Remote Loader and the Roles Based Services, you can upgrade the Identity Manager Engine. The upgrade process updates the driver shim files that are stored in the file system on the host computer.
If your driver is using MapDB, ensure that your upgraded driver works correctly with the upgraded Engine. For more information, see Working with MapDB 3.0.5.
Ensure that there are no events in the cache file before you begin upgrading Identity Manager Engine.
Verify that the drivers are stopped. For more information, see Stopping, Starting, or Restarting a Driver in Designer in the NetIQ Identity Manager Driver Administration Guide.
Launch the installation program for Identity Manager engine from IDMversion_Win:\products\idm\Windows\setup\idm_install.exe.
Select the language that you want to use for the installation.
Read and accept the license agreement.
To update the Identity Manager engine and driver shim files, select the following options:
Identity Manager Server
iManager Plug-ins for Identity Manager
Drivers
Specify a user and the user password with administrative rights to eDirectory in LDAP format.
Review the summary, then click Install.
Read the installation summary, then click Done.
The Engine upgrade process leaves some of the existing MapDB cache files (dx*) in the Identity Vault’s DIB directory. You must manually remove these files for a driver using MapDB after upgrading the driver. For more information, see Working with MapDB 3.0.5.
Identity Manager 4.7 adds support for MapDB 3.0.5. In addition to Identity Manager Engine, MapDB is used by the following Identity Manager drivers:
Data Collection Services
JDBC
LDAP
Managed System Gateway
Office 365 and Azure Active Directory
Salesforce
If you are using any of these drivers, you must review the following sections before upgrading the driver:
Review the following considerations before upgrading an Identity Manager driver that uses MapDB:
Drivers shipped with Identity Manager 4.7 are compatible with Identity Manager 4.7 Engine or Remote Loader. You must follow the driver upgrade steps from the specific driver implementation guide.
Drivers shipped before Identity Manager 4.7 are not compatible with Identity Manager 4.7 Engine or Remote Loader.
Drivers shipped with Identity Manager 4.7 are not backward compatible with Identity Manager 4.6.x Engine or Remote Loader.
Drivers shipped with Identity Manager 4.7 are not backward compatible with Identity Manager 4.5.x Engine or Remote Loader.
The Identity Manager Engine upgrade process leaves some of the existing MapDB cache files (dx*) in the Identity Vault’s DIB directory (C:\Novell\NDS\DIBFiles). You must manually remove these files for your driver after upgrading the driver. This action ensures that your driver works correctly with Identity Manager 4.7 engine.
The following table lists the MapDB cache files that must be removed:
|
Identity Manager Driver |
MapDB State Cache File To Remove |
|---|---|
|
Data Collection Services |
DCSDriver_<driver instance guid>-* <driver instance guid>-* |
|
JDBC |
jdbc_<driver instance guid>_* |
|
LDAP |
ldap_<driver instance guid>* |
|
Managed System Gateway |
MSGW-<driver-instance-guid>.* |
|
Office 365 and Azure Active Directory |
<Azure driver name>_obj.db.* |
|
Salesforce |
<Salesforce driver name>.* <Salesforce driver name> |
where * represents the name of the MapDB state cache file. In case of a Salesforce driver, the MapDB state cache files are also represented by the driver name. Below are some examples of these files.
DCSDriver_<driver instance guid>-0.t, <driver instance guid>-1.p
jdbc_<driver instance guid>_0.t, jdbc_<driver instance guid>_1
ldap_<driver instance guid>b, ldap_<driver instance guid>b.p
MSGW-<driver instance guid>.p, MSGW-<driver instance guid>.t
<Azure driver name>_obj.db.t, <Azure driver name>_obj.db.p
<Salesforce driver name>.p, <Salesforce driver name>.t, Salesforce driver1