The driver upgrade process involves updating the driver files, upgrading the installed driver packages, and updating the Sun-One plug-in.
This section provides general instructions for updating a driver. For information about updating the driver to a specific version, search for that driver patch in the NetIQ Patch Finder Download Page and follow the instructions from the Readme file accompanying the driver patch release.
Download the latest available packages.
To configure Designer to automatically read the package updates when a new version of a package is available, click Windows > Preferences > NetIQ > Package Manager > Online Updates in Designer. For more information about managing packages, see the NetIQ Designer for Identity Manager Administration Guide.
Upgrade the installed packages.
Open the project containing the driver.
Right-click the driver for which you want to upgrade an installed package, then click Driver > Properties.
Click Packages.
If there is a newer version of a package, there is check mark displayed in the Upgrades column.
Click Select Operation for the package that indicates there is an upgrade available.
From the drop-down list, click Upgrade.
Select the version that you want to upgrade to, then click OK.
NOTE:Designer lists all versions available for upgrade.
Click Apply.
(Conditional) Fill in the fields with appropriate information to upgrade the package, then click Next.
Depending on which package you selected to upgrade, you must fill in the required information to upgrade the package.
Read the summary of the packages that will be installed, then click Finish.
Review the upgraded package, then click OK to close the Package Management page.
For detailed information, see the Upgrading Installed Packages in the NetIQ Designer for Identity Manager Administration Guide.
The driver patch updates the driver files. You can install the patch as a root or non-root user.
Before installing the patch, complete the following steps:
Take a back-up of the current driver configuration.
(Conditional) If the driver is running with the Identity Manager engine, stop the Identity Vault and the driver instance.
(Conditional) If the driver is running with a Remote Loader instance, stop the Remote Loader instance and the driver instance.
In a browser, navigate to the NetIQ Patch Finder Download Page.
Under Patches, click Search Patches.
Specify Identity Manager nn LDAP Driver nn in the search box.
Download and unzip the contents of the patch file to a temporary location on your server.
For example, IDM45_LDAP_410.zip.
In a root installation, the driver patch installs the driver files RPMs in the default locations on Linux. On Windows, you need to manually copy the files to the default locations.
Ensure that you have completed the prerequisites for installing the patch. For more information, see Prerequisites.
Update the driver files:
Linux: Log in to your server as root and run the following command in a command prompt:
rpm -Uvh <Driver Patch File Temporary Location>/linux/novell-DXMLldap.rpm
For example, rpm -Uvh <IDM45_LDAP_410.tar.gz>/linux/novell-DXMLldap.rpm
Windows: Navigate to the <Extracted Driver Patch File Temporary Location>\windows folder and copy the following files to <IdentityManager installation>\NDS\lib or <IdentityManager installation>\RemoteLoader\<architecture>\lib folder.
LDAPShim.jar
LDAPUtil.jar
(Conditional) Copy the mapdb.jar file to <IdentityManager installation>\NDS\lib or <IdentityManager installation>\RemoteLoader\<architecture>\lib folder.
This step is only required for driver version 4.0.2 if not performed in the previous driver patch updates.
(Conditional) Replace the existing cache (JDBM) with the new cache (mapDB).
This step is only required for driver version 4.0.2 if not performed in the previous driver updates.
You need to resynchronize the changes made on the connected system while the driver is stopped for upgrade. This is because a new Cache (DBfiles) is being regenerated and previous cache (JDBM) will not be referenced after upgrade. Therefore, changes during this period must be resynchronized.
(Conditional) If the driver is running locally, start the Identity Vault and the driver instance.
(Conditional) If the driver is running with a Remote Loader instance, start the Remote Loader and the driver instance.
When JDBM is replaced with mapDB, a new set of DB files are created by mapDB and the existing cache is no longer referenced in the upgraded driver. Therefore, you must set Synchronize subsequent changes flag instead of Synchronize Everything in the upgraded driver. When this flag is set, the driver takes relatively lesser time to synchronize the objects when you have a large number of objects in the connected system.
NOTE:To install the driver on Solaris, call NetIQ Support.
Verify that <non-root eDirectory location>/rpm directory exists and contains the _db.000 file.
The _db.000 file is created during a non-root installation of the Identity Manager engine. Absence of this file in the directory might indicate that Identity Manager is not properly installed and it might be necessary to re-install it to place the file in the directory.
To set the root directory to non-root eDirectory location, enter the following command in the command prompt:
ROOTDIR=<non-root eDirectory location>
This will set the environmental variables to the directory where eDirectory is installed as a non-root user.
To install the driver files, enter the following 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 <rpm-location>
For example, to install the LDAP 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-DXMLLDAP.rpm
NOTE:If your plug-in version matches the version shipped with the driver patch file version, skip this section.
Locate the correct plug-in binary file in the extracted driver patch directory.
The file is located in directories representing the supported platforms under the \sunpasswordplugin4002 directory. For example, if your Sun directory runs on Linux, look in the sunpasswordplugin4002\Linux directory. The name of the plug-in file is novl-idm-pswd.so on all platforms. On Windows, the file is named as novl-idm-pswd.dll.
Copy the binary plug-in file to the correct place in your Sun Java System Directory installation.
For example, the default installation location for Sun Java System Directory on Windows is C:\Program Files\Sun\MPS\lib directory. Copy the novl-idm-pswd.dll to the lib directory. On other platforms, the default installation location is often /var/Sun/mps. Locate the directory on your server and copy the plug-in file to the lib directory.
NOTE:On Solaris SPARC computers, the Sun Java System Directory installation includes both 32-bit and 64-bit versions of the library. The default 32-bit version of the library is located in /var/Sun/mps/lib and the 64-bit version is located in /var/Sun/mps/lib/64. Both 32-bit and a 64-bit versions of the plug-in are included in the driver patch file. You should copy both versions to their respective locations in your Solaris installation directory. At runtime, the Sun Java System Directory appropriately determines which version to load.
After making the changes, restart the Sun directory.