Ensure that you upgrade Identity Vault before upgrading the Identity Manager engine. The Identity Manager engine upgrade process updates the driver shim files that are stored in the file system on the host computer.
Download the Identity_Manager_4.9.0_Windows.iso as instructed in Where to Get Identity Manager in the NetIQ Identity Manager Overview and Planning Guide.
Mount the downloaded.iso.
Navigate to the <iso mounted location>\IdentityManagerServer\products\eDirectory\x64 directory.
Run the eDirectory_929_Windows_x86_x64.exe file.
In the Basic tab, specify the following details:
If you select New Tree, specify the following details:
Tree Name: Specify a tree name for Identity Vault.
Server FDN: Specify a server FDN.
NOTE:Though Identity Vault allows you to set the NCP server object's FDN up to 256 characters, NetIQ recommends that you restrict the variable to a much lesser value because Identity Vault creates other objects of greater length based on the length of this object.
Tree Admin: Specify an administrator name for Identity Vault.
Admin Password: Specify the administrator password.
If you select Existing Tree, specify the following details:
IP Address: Specify the IP address of the of the existing tree for Identity Vault.
Port Number: Specify the port number for the existing tree. The default value is 524.
Server FDN: Specify a server FDN.
Tree Admin: Specify the existing administrator name for Identity Vault.
Admin Password: Specify the administrator password.
(Conditional) In the Advanced tab, specify the following details:
To use IPv6 addresses on the Identity Vault server, select Enable IPv6.
NOTE:NetIQ recommends that you enable this option. To enable IPv6 addressing after installation, you must run the setup program again.
To enable Enhanced Background Authentication (EBA), select Enable EBA.
Specify the HTTP clear text and secure ports. The default values are 8028 and 8030 respectively.
Specify the LDAP clear text and secure ports. The default values are 389 and 636 respectively.
In the Install Location field, specify the location where Identity Vault is installed.
In the DIB Location field, specify the location where the DIB files are located.
Click Upgrade and proceed with the upgrade process.
Verify that the drivers are stopped. For more information, see Stopping the Drivers.
Perform the following steps to upgrade the Identity Manager Engine:
Download the Identity_Manager_4.9.0_Windows.iso from the NetIQ Downloads website.
Mount the downloaded .iso.
Navigate to the <ISO installed location>\IdentityManagerServer folder and run the install.exe.
Select the language that you want to use for the installation and click OK.
In the Introduction page, click Next.
Read and accept the license agreement and then click Next.
The installed components and their versions are displayed.
Select Identity Manager Engine and click Next.
Specify the following details:
Identity Vault Administrator: Specify the Identity Vault administrator name.
Identity Vault Administrator Password: Specify the Identity Vault Administrator password.
Select the required edition of the Identity Manager that you want to install from the following:
Standard Edition
Advanced Edition
NOTE:Make sure to select the same edition as in the previous version.
Specify the configuration settings for Identity Manager Engine. For more information, see Configuration Worksheet for Identity Manager Engine.
In the pre-upgrade summary page, review the settings and click Upgrade.
The 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.9 are compatible with Identity Manager 4.9 Engine or Remote Loader. You must follow the driver upgrade steps from the specific driver implementation guide.
Drivers shipped before Identity Manager 4.9 are not compatible with Identity Manager 4.9 Engine or Remote Loader.
Drivers shipped with Identity Manager 4.9 are not backward compatible with Identity Manager 4.8.x Engine or Remote Loader.
Drivers shipped with Identity Manager 4.9 are not backward compatible with Identity Manager 4.7.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. 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.9 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
If you are running the Remote Loader, you need to upgrade the Remote Loader files.
NOTE:Before upgrading .NET Remote Loader, ensure that you have successfully installed all the Windows updates on your system.
Create a backup of the Remote Loader configuration files. The default location of the files is C:\...\RemoteLoader\remoteloadername-config.txt.
Verify that the drivers are stopped. For instructions, see Stopping, Starting, or Restarting a Driver in Designer in the NetIQ Identity Manager Driver Administration Guide.
Stop the Remote Loader service or daemon for each driver.
In the Remote Loader Console, select the Remote Loader instance, then click Stop.
Stop the cache process using Windows Task Manager.
Download the Identity_Manager_4.9.0_Windows.iso from the NetIQ Downloads website.
Mount the downloaded .iso.
Navigate to the <ISO installed location>\IdentityManagerServer folder and run the install.exe.
Select the language that you want to use for the installation and click OK.
In the Introduction page, click Next.
Read and accept the license agreement and then click Next.
The installed components and their versions are displayed.
Select Remote Loader Service and click Next.
In the pre-upgrade summary page, click Upgrade.
After the upgrade is complete, verify that your configuration files contain your environment’s information.
(Conditional) If there is a problem with the configuration file, copy the backup file that you created in step 1. Otherwise, continue with the next step.
Start the Remote Loader service or daemon for each driver.
IMPORTANT:If your driver uses MapDB, manually remove the existing MapDB state cache files for the driver after upgrading the driver. This is required because Identity Manager engine upgrade process does not remove all of these files from the Identity Vault’s DIB directory. For more information, see Working with MapDB 3.0.5.
Create a backup of the Remote Loader configuration files. The default location of the files is C:\...\RemoteLoader\remoteloadername-config.txt.
Verify that the drivers are stopped. For instructions, see Stopping, Starting, or Restarting a Driver in Designer in the NetIQ Identity Manager Driver Administration Guide.
Stop the Remote Loader service or daemon for each driver.
In the Remote Loader Console, select the Remote Loader instance, then click Stop.
Stop the lcache process using Windows Task Manager.
Download the Identity_Manager_4.9.0_Windows.iso from the NetIQ Downloads website.
Mount the downloaded .iso.
Navigate to the <ISO installed location>\IdentityManagerServer\products\IDM\java_remoteloader folder.
Copy and replace the dirxml_jremote_dev.tar.gz file in your existing Java Remote Loader installed directory.
Based on the file present in your existing setup, copy and replace one of the following files in your existing Java Remote Loader installed directory:
dirxml_jremote.tar.gz
dirxml_jremote_mvs.tar
Extract the files that you have copied in step 8 and step 9.
Use the 7-zip or supported software to unzip the .tar.gz file.
(Conditional) If there is a problem with the configuration file, copy the backup file that you created in step 1. Otherwise, continue with the next step.
NOTE:Use the version.txt file to ensure that you have the latest version of Java Remote Loader.
Start the Remote Loader service or daemon for each driver.
Verify that the drivers are stopped. For more information, see Stopping the Drivers.
Perform the following steps to upgrade the Identity Manager Engine:
Download the Identity_Manager_4.9.0_Windows.iso from the NetIQ Downloads website.
Mount the downloaded .iso.
Navigate to the <ISO installed location>\IdentityManagerServer folder and run the install.exe.
Select the language that you want to use for the installation and click OK.
In the Introduction page, click Next.
Read and accept the license agreement and then click Next.
The installed components and their versions are displayed.
Select Fanout Agent and click Next.
In the pre-upgrade summary page, review the settings and click Upgrade.
Start the Fanout Agent service.