Before beginning, make sure you have reviewed the differences between an in-place upgrade and a migration. See Section 12.0, In-place Upgrade Versus Migration.
Use the following checklist to verify that all of the steps are completed in the correct order for a successful migration of the Identity Manager system. Follow these steps for each Identity Manager server in your environment.
Create a backup of the current configuration of your Identity Manager solution. This is done by creating exports of your drivers or creating a Designer project of your Identity Manager solution. For more information, see Section 13.1, Creating a Backup of the Current Configuration.
Install the desired operating system. For a list of supported platforms, see Section 6.0, System Requirements.
Install eDirectory 8.8.5 on the server. For more information, see the eDirectory Installation Guide.
Install Identity Manager 3.6.1. Use the Section 4.0, Basic Identity Manager System Checklist to verify that all steps are completed.
If any of the drivers in the driver set are Remote Loader drivers, upgrade the Remote Loader server for each driver. For more information, see Section 13.6, Upgrading the Remote Loader.
(Conditional) If the old server is your User Application server, perform the following additional steps:
The User Application driver must be migrated in Designer. For more information, see the Roles Based Provisioning Module Migration Guide.
Create a new Roles Service driver. The Roles Service driver is not migrated. If you have an existing Role Service driver for version 3.6.1, you must create a new driver for version 3.6.1. For more information, see the Roles Based Provisioning Module Migration Guide.
Deploy the migrated User Application driver into the Identity Vault. For more information, see the Roles Based Provisioning Module Migration Guide.
Install the User Application on this new server. For more information, see the Roles Based Provisioning Module Installation Guide.
Add the new server to the driver set. For more information, see Section 14.1, Adding the New Server to the Driver Set.
Change the server-specific information for each driver. For more information, see Section 14.2, Changing Server-Specific Information.
(Conditional) Run configupdate.sh or configupdate.bat to change server-specific information from the old server to the new server for the User Application configuration. For more information, see “User Application Configuration Reference” in the Roles Based Provisioning Module Installation Guide.
(Optional) Overlay the new driver configuration files over the existing drivers to get new policies. This is required only if there is new functionality included in the policies for a driver that you want to add to your existing driver. For more information, see Section 13.7, Overlaying the New Driver Configuration File over the Existing Driver.
(Optional) Restore custom policies and rules to the drivers. When you overlay the new driver configuration files, the policies are overwritten, so restoring policies is required only if you did an overlay of the new driver configuration file. For more information, see Section 13.8, Restoring Custom Policies and Rules to the Driver.
Remove the old server from the driver set. For more information, see Section 14.3, Removing the Old Server from the Driver Set.
If you are using Novell Sentinel, you must update to Novell Sentinel 6.1. For more information about upgrading Sentinel, see the Sentinel Installation Guide.
Activate the Metadirectory engine and any upgraded driver. For more information, see Section 8.0, Activating Novell Identity Manager Products.