Overview

This patch is applicable for SAP User drivers running Identity Manager 4.6.x or Identity Manager 4.7.x. The driver version will be changed to 4.0.4.0 after the patch is applied.

System Requirements Upgrading the Driver

The driver upgrade process involves the following tasks:

Upgrading the Driver Packages
  1. Download the following packages:

  2. Open the project containing the driver.

  3. Right-click the driver for which you want to upgrade an installed package, then click Driver > Properties.

  4. Click Packages.
  5. A check mark indicates a newer version of a package in the Upgrades column.

  6. Click Select Operation for the package that indicates there is an upgrade available.

  7. From the drop-down list, click Upgrade.

  8. Select the version that you want to upgrade to, then click OK.
  9. NOTE: Designer lists all versions available for upgrade.

  10. Click Apply.

  11. (Conditional) Fill in the fields with appropriate information to upgrade the package, then click Next.
  12. Depending on which package you selected to upgrade, you must fill in the required information to upgrade the package.

  13. Read the summary of the packages that will be installed, then click Finish.

  14. Review the upgraded package, then click OK to close the Package Management page.

Upgrading the Driver

The driver upgrade process involves updating the driver files.


Updating the Driver Files
  1. Take a back-up of the current driver configuration.

  2. (Conditional) If the driver is running locally, stop the driver instance and the Identity Vault.

  3. (Conditional) If the driver is running with a Remote Loader instance, stop the driver and the Remote Loader instance.

  4. Download and unzip the contents of the IDM_SAPUM_4040.zip file to a temporary location on your computer.

  5. (Conditional) To update the driver files as a root user:

    1. On the server where you want to apply the driver patch, log in as root/administrator.

    2. Navigate to the <extracted IDM_SAPUM_4040.zip> directory and perform one of the following actions for your platform:

    3. Windows: Copy the sapumshim.jar file to your driver installation folder. For example, \NetIQ\IdentityManager\NDS\lib, if the driver is locally installed with the Identity Manager engine or \Novell\RemoteLoader\lib if the driver is installed with the Remote Loader.

  6. (Conditional) To update the driver files as a non-root user:

    1. Verify that <non-root edirectory="" location="">/rpm directory exists and contains _db.000 file.
    2. The _db.000 file is created during a non-root installation of the Identity Manager engine. Absence of this file might indicate that Identity Manager is not properly installed. Reinstall Identity Manager to correctly place the file in the directory.

    3. To set the root directory to the location of non-root Identity Vault, enter the following command in the command prompt:
    4. ROOTDIR=<non-root eDirectory location>

      This will set the environmental variables to the directory where Identity Vault is installed as a non-root user.

    5. To install the driver files, enter the following command:
    6. For example, to install the SAP User driver RPM, use this command:

      rpm --dbpath $ROOTDIR/rpm -Uvh --relocate=/usr=$ROOTDIR/opt/novell/eDirectory --relocate=/etc=$ROOTDIR/etc --relocate=/opt/novell/eDirectory=$ROOTDIR/opt/novell/eDirectory --relocate=/opt/novell/dirxml=$ROOTDIR/opt/novell/dirxml --relocate=/var=$ROOTDIR/var --badreloc --nodeps --replacefiles /home/user/novell-DXMLsapus.rpm

      where /opt/novell/eDirectory is the location where non-root eDirectory is installed and /home/user/ is the home directory of the non-root user.

  7. (Conditional) If the driver is running locally, start the Identity Vault and the driver instance.

  8. (Conditional) If the driver is running with a Remote Loader instance, start the Remote Loader instance and the driver instance.

Technical Support Information

Issues Fixed in This Release


Issues Fixed in Previous Releases

Issue Fixed in Driver 4.0.3.2


  • Issues Fixed in Driver 4.0.3.1
  • Issues Fixed in Driver 4.0.3 and Earlier Releases