For an upgrade to Identity Manager 3.0.1 to be successful, the following steps need to be completed.
Before an upgrade occurs, getting a backup of the current drivers and their configuration information is the most important step. To get a backup of the drivers, you need to export the drivers.
In ConsoleOne, right-click on 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.
In order to upgrade to Identity Manager 3.0.1, the servers running the Identity Manager services need to meet the minimum requirements. See Section 4.2, Identity Manager Components and System Requirements 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.73 with the latest patch, or upgrade to eDirectory 8.8.1.
Upgrade iManager to iManager 2.6 SP2 (includes upgrading Apache 2.0.52 or later and Tomcat 4.1.18 or later).
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.
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 and select .
On the Driver Configuration page, under Startup Options, select .
Install Identity Manager 3.0.1. The steps to upgrade to Identity Manager 3.0.1 are the same as when you install Identity Manager 3.0. See Section 4.0, Installing Identity Manager for the instructions on how to install Identity Manager.
Set the drivers 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 and select .
On the Driver Configuration page, under Startup Options, select or you preferred method of start up for 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 in the upper-right corner of the driver icon, then select .
If you are running the Remote Loader, you need to upgrade the remote loader files as well.
Create a backup of the Remote Loader configuration files. The default location of the files:
Windows C:\Novell\RemoteLoader\remoteloadername-config.txt
Linux - You 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
Remote Loaders
in the Novell
Identity Manager 3.0.1 Administration Guide.