18.4 Upgrading OpenText Identity Manager Engine

Ensure that you upgrade Identity Vault before upgrading the OpenText Identity Manager engine. The OpenText Identity Manager engine upgrade process updates the driver shim files that are stored in the file system on the host computer.

18.4.1 Verifying Linux RPMs Before Installing

Perform the following steps to verify the RPMs:

  1. Download the Identity_Manager_4.10.0_Linux.iso from the Software and License page.

  2. Mount the downloaded.iso.

  3. Navigate to the following location for public key:

    <ISO-MOUNT-location>/common/license/

    For example, cd /mnt/common/license/

  4. Run the following commands to import the keys:

    rpm --import MicroFocusGPGPackageSign.pub
    rpm --import OT-package-sign.pub

  5. (Optional) Run the following command to verify the signature:

    rpm --checksig -v <mount-location>/IDVault/setup/<RPM Name>

    For example,

    rpm --checksig -v /mnt/IDVault/setup/novell-NDSbase-*.x86_64.rpm

18.4.2 Upgrading the Identity Vault

  1. Download the Identity_Manager_4.10.0_Linux.iso as instructed in Where to Get OpenText Identity Manager in the OpenText™ Identity Manager CE 24.4 (v4.10) Overview and Planning Guide.

  2. Mount the downloaded.iso.

  3. From the root directory of the .iso file, navigate to the IDVault/setup directory.

  4. Run the following command:

    ./nds-install

  5. As iManager is getting deprecated, enter your response for the following warning prompt:

    This version of eDirectory installation will upgrade various packages required by eDirectory and iManager. The updated packages may impact iManager running on the same server. Do you want to continue installation/upgrade (y/n)

    1. (Optional) If yes, proceed to Step 6.

    2. (Optional) If no, the update will be terminated.

  6. Accept the license agreement and proceed with the installation.

  7. Specify adminDN. For example, cn=admin.ou=sa.o=system.

  8. Specify y when prompted for stopping OpenText eDirectory instances and upgrading NICI.

  9. Specify if you want to configure Enhanced Background Authentication.

NOTE:Run ndsconfig upgrade after nds-install, if DIB upgrade fails and the nds-install command prompts to do so. If OpenText eDirectory services are not starting after an upgrade, run the ndsconfig upgrade command. For more information, see the OpenText eDirectory Installation Guide.

18.4.3 Upgrading the OpenText Identity Manager Engine

Verify that the drivers are stopped. For more information, see Stopping the Drivers.

Perform the following steps to upgrade the OpenText Identity Manager Engine:

  1. Download the Identity_Manager_4.10.0_Linux.iso from the Software Downloads website.

  2. Mount the downloaded .iso.

  3. Run the following command:

    ./install.sh

  4. Read through the license agreement.

  5. Enter y to accept the license agreement.

  6. Specify whether you want upgrade the OpenText Identity Manager components. The available options are y and n.

  7. Select OpenText Identity Manager Engine.

  8. Specify the following details:

    Identity Vault Administrator: Specify the Identity Vault administrator name.

    Identity Vault Administrator Password: Specify the Identity Vault Administrator password.

The engine upgrade process retains 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.9.

Working with MapDB 3.0.9

OpenText Identity Manager supports MapDB 3.0.9. In addition to OpenText Identity Manager Engine, MapDB is used by the some drivers like Office365 and Azure Active Directory.

If you are using any of these drivers, you must review the following sections before upgrading the driver:

Understanding OpenText Identity Manager 4.10 Engine Support for Driver Versions

Review the following considerations before upgrading an OpenText Identity Manager driver that uses MapDB:

  • Drivers shipped with OpenText Identity Manager 4.10 are compatible with OpenText Identity Manager 4.10 Engine or Remote Loader. You must follow the driver upgrade steps from the specific driver implementation guide.

(Optional) Manually Removing the MapDB Cache Files

The OpenText Identity Manager Engine upgrade process leaves some of the existing MapDB cache files (dx*) in the Identity Vault’s DIB directory (/var/opt/novell/eDirectory/data/dib). You must manually remove these files for your driver after upgrading the driver. This action ensures that your driver works correctly with OpenText Identity Manager 4.10 engine.

The following table lists the MapDB cache files that must be removed:

OpenText 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 version of the MapDB state cache file. Any MapDB state cache files containing the above names, regardless of the versions, must be removed. 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>_0, 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

18.4.4 Upgrading the OpenText Identity Manager Engine as a Non-root User

Perform this action only if you have installed OpenText Identity Manager engine as a non-root user.

  1. Download the Identity_Manager_4.10.0_Linux.iso from the Software and License page.

  2. Mount the downloaded .iso.

  3. Run the following command:

    ./install.sh

  4. Select OpenText Identity Manager Engine and press Enter.

  5. Specify the non-root install location for OpenText Identity Manager engine. For example, /home/user/eDirectory/.

  6. Specify y to complete the upgrade.

18.4.5 Upgrading the Remote Loader

If you are running the Remote Loader, you need to upgrade the Remote Loader files.

  1. Create a backup of the Remote Loader configuration files.

  2. Verify that the drivers are stopped. For more information, see Stopping the Drivers.

  3. Stop the Remote Loader service or daemon for each driver.

    rdxml -config path_to_configfile -u

  4. Download the Identity_Manager_4.10.0_Linux.iso from the OpenText Downloads website.

  5. Mount the downloaded .iso.

  6. Run the following command:

    ./install.sh

  7. Read through the license agreement.

  8. Enter y to accept the license agreement.

  9. Specify whether you want upgrade the OpenText Identity Manager components. The available options are y and n.

  10. Select Remote Loader.

  11. After the installation finishes, verify that your configuration files contain your environment’s information.

  12. (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.

  13. Start the Remote Loader service or daemon for each driver.

    rdxml -config path_to_config_file

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 OpenText 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.9.

18.4.6 Upgrading the Java Remote Loader

  1. Create a backup of the Java Remote Loader configuration files.

  2. Verify that the drivers are stopped. For more information, see Stopping the Drivers.

  3. Stop the Remote Loader service or daemon for each driver.

    dirxml_jremote -config path_to_configfile -u

  4. Download the Identity_Manager_4.10.0_Linux.iso from the OpenText Downloads website.

  5. Mount the downloaded .iso.

  6. Navigate to the /IDM/packages/java_remoteloader directory.

  7. Copy and replace the dirxml_jremote_dev.tar.gz file in your existing Java Remote Loader installed directory.

  8. 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

  9. Extract the files that you have copied in step 7 and step 8.

    For example, tar -zxvf dirxml_jremote.tar.gz

  10. (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.

  11. Start the Remote Loader service or daemon for each driver.

    dirxml_jremote -config path_to_config_file