For an upgrade to Identity Manager 3.5.1 to be successful, the following steps need to be completed.
Before an upgrade occurs, backing up the current drivers and their configuration information is the most important step. To back up the drivers, you need to export them.
In ConsoleOne®, right-click the Driver Set object, then select .
Select the driver you want to create an export for, then click .
Specify a filename. Leave the default extension of .xml, then click .
Click .
In iManager, you can export a driver or the entire driver set. If you export the driver set, there is a single configuration file created. If you export each driver, there is a configuration file created for each driver.
In iManager, select .
Browse to and select the driver or driver set you want to export, then click .
Leave the prompting fields blank to create an exact copy of the driver, then click .
If you select the Driver Set object, you receive a prompting page for each driver. Leave the fields blank for each driver to create an exact copy.
Click .
Click in the File Download window.
Browse to and specify a file location and name for the export, then click .
IMPORTANT:The file needs to have an .xml extension when it is saved.
After you have an export of the driver, test the export in a lab environment. Import the driver export and test the driver to make sure all of the parameters are correct and all of the functionality is there.
From Designer, right-click the Driver or Driver Set object in the Modeler view and click .
In the Export Driver Configuration window, browse to and specify a file location and name for the export, then click .
In order to upgrade to Identity Manager 3.5.1, the servers running the Identity Manager services need to meet the minimum requirements. See Table 1-3 for the list of minimum requirements for each platform.
If the supporting components need to be upgraded, do the upgrades in the following order:
Upgrade the OS to a supported version. For example, upgrade from NetWare® 6.0 to NetWare 6.5.
Upgrade eDirectory™ to eDirectory 8.7.3.6 with the latest Support Pack, or upgrade to eDirectory 8.8 with the latest Support Pack.
You must have Security Services 2.0.5 with NMAS™ 3.2.0 for SSL support.
Upgrade iManager to iManager 2.6 or 2.7 with the latest Support Pack (includes upgrading to Apache 2.0.52 or later and Tomcat 4.1.18 or later).
For Identity Manager User Application and Provisioning, see Section 5.2, Prerequisites to Installation.
Upgrade Identity Manager.
Activate the Metadirectory engine and any upgraded driver.
After the supporting components have been upgraded, the DirXML or Identity Manager engine is upgraded.
Make sure you have a valid export of the drivers before upgrading. See Section 3.3.1, Exporting Drivers.
Stop the drivers.
In iManager, select .
Browse to and select the Driver Set object, then click .
Click in the upper right corner of the driver icon, then select .
Set the drivers to manual start.
In iManager, select .
Browse to and select the Driver Set object, then click .
In the upper right corner of the driver icon, click .
On the Driver Configuration page, under, select .
Install Identity Manager 3.5.1.
The steps to upgrade to Identity Manager 3.5.1 are the same as the ones for installing Identity Manager 3.5. See Section 4.0, Installing Identity Manager for the instructions on how to install Identity Manager.
Identity Manager 3.5.1 copies over previous versions of Identity Manager, updating the binaries. Both iManager and Designer update the drivers to the new functionality.
In iManager, click the drivers to begin the Driver Upgrade Wizard.
Designer automatically begins the Driver Upgrade Wizard when it detects older drivers.
Set the driver startup options.
In iManager, select .
Browse to and select the Driver Set object, then click .
In the upper right corner of the driver icon, click .
On the Driver Configuration page, under , select or select your preferred method of starting the driver.
Look at the driver parameters and policies to make sure everything is set how you want it to be.
Start the driver.
In iManager, select .
Browse to and select the Driver Set object, then click .
Click the upper right corner of the driver icon, then select .
If you are running the Remote Loader, you need to also upgrade the Remote Loader files.
Create a backup of the Remote Loader configuration files. The default location of the files is as follows:
Windows C:\Novell\RemoteLoader\remoteloadername-config.txt
Linux: Create your own configuration file in the path of rdxml.
Stop the Remote Loader service or daemon.
Run the installation programs for the Remote Loader.
This updates the files and binaries to the current version. See Installing the Remote Loader
in the Novell Identity Manager 3.5.1 Administration Guide.
Upgrading from Identity Manager 3.0.1 to Identity Manager 3.5.1 in either a UNIX or Linux environment creates two uninstall locations and doesn’t completely remove packages. For example, if you start with a UNIX platform, such as SLES 9, and install Identity Manager 3.0.1, the Identity Manager uninstaller is in the /root/dirXML directory. Typing rpm -qa | grep -i dxml shows when the dxml packages were installed.
If you now upgrade this deployment to Identity Manager 3.5.1, it creates a new uninstall location at the /root/idm directory because of the naming change. Typing rpm -qa shows when the updated packages were installed.
Because of the directory change, if the administrator uninstalls Identity Manager 3.5.1, the uninstaller won’t remove all of the packages, even though it states that all items were successfully removed. To remove the rest of the packages, use the DirXML uninstaller.
If you are migrating to the latest version of the Identity Manager User Application, please refer to the Identity Manager User Application: Migration Guide for directions.