2.2 Upgrading from iManager 2.0.x

The first time you use iManager 2.5 to log in to an eDirectory tree that contains an iManager 2.0.2 RBS Collection, it is possible that not all of the roles and tasks will be displayed. This is working as expected because some of the iManager 2.0.2 plug-ins require updates so that iManager 2.5 can fully utilize them. Go to the RBS Configuration page which lists which RBS modules are out of date. We recommend that you update your RBS modules to the latest version so that you can see and use all of the installed modules on both iManager 2.0.2 and iManager 2.5.

Be aware in this situation of possibly having multiple roles with the same name. Some plug-in developers, when they updated their plug-ins for iManager 2.5, changed task IDs or module names but retained the same display names, thus causing the roles to appear to be duplicated when, in fact, one instance is from one version and the other is from a newer version.

NOTE:Because different installations of iManager 2.0.x or 2.5 might have a different number of plug-ins locally installed, you might see discrepancies in the module report for any given collection from the Role Based Services > RBS Configuration page. In order for the numbers to match between iManager installations, make sure that the same subset of plug-ins is installed on each iManager instance in the tree.

To check whether you have outdated RBS objects:

  1. Select the Configure view, then click Role Based Services > RBS Configuration task.

    The table on the 2.x Collections tabbed page displays any out of date modules.

  2. To update them, select the number in the Out-Of-Date column for the Collection you want to update.

    The list of outdated modules is displayed.

  3. Select the module you want to update and then click Update at the top of the table.

Upgrades from iManager 2.0.x to 2.5 are supported by the install program. When you run the iManager 2.5 installation program on a server that is running iManager 2.0.x, the existing 2.0.x directory structure is backed up to the TOMCAT_HOME directory. This assures the preservation of any custom content created in iManager 2.0.x. The Novell Plug-in Modules (NPMs) located in the backed-up 2.0.x directory are then compared to the NPMs included with iManager 2.5. NPMs that either don’t exist or are newer than those in the 2.5 packages directory are copied to the iManager 2.5 TOMCAT_HOME\webapps\nps\packages directory and installed.