You must migrate the version 3.5 User Application drivers that you want to use in Identity Manager 3.5.1. Migrating a User Application driver updates all directory abstraction layer definitions and provisioning request definitions to use the latest format. Several non-visible runtime configuration objects are also updated and additional properties are added.
The migration of a User Application driver ensures that the driver contains the necessary configuration for new features in Identity Manager 3.5.1, while maintaining existing configurations (for example, custom entities and provisioning request definitions).
The migration tool only migrates the User Application configuration of the User Application driver. It does not migrate the entire driver. Specifically, it doesn't migrate policies. These are handled by the general Designer and the deploy code. For information about migrating policies, see Upgrading Identity Manager Policies.
NOTE:You can set preferences for migrating User Application drivers (see
Setting Provisioning View Preferences
in the
Identity Manager 3.5.1 User Application: Design Guide).
Install Identity Manager Designer version 2.1.
See
Installing Designer
in the
Novell Designer 2.1 for Identity Manager 3.5.1 Guide.
Create a new provisioning project to store the local representations of the artifacts that are located on your Metadirectory server.
See
Setting Up a Provisioning Project
in the
Identity Manager 3.5.1 User Application: Design Guide.
Import the driver set that contains the User Application drivers that you want to migrate.
See
Importing Provisioning Objects
in the
Identity Manager 3.5.1 User Application: Design Guide.
Make a backup copy of the new provisioning project as follows:
Right-click the name of the project in Project view, then select .
In the Copy Project dialog box, type a new (or accept the default name), then click .
Use one of the following methods to select the Migrate command for the User Application that you want to migrate.
In the , right-click the name of the User Application and select .
In the view, right-click the name of the User Application and select .
In the view, right-click the name of the User Application and select .
This step migrates the local definition of the driver, found in the IDM Designer workspace. These changes are not made to the Metadirectory server until a later step when you deploy the changes.
Click the tab.
Click the plus (+) sign next to the name of the project to show the list of User Applications in the project.
Right-click the name of the User Application that you want to migrate and select .
The dialog box is displayed. This dialog box informs you that migrating the User Application will close all editors.
Select .
If you have unsaved work in an open editor, the dialog box displays.
If the dialog box is displayed, select to save changes in open editors.
A dialog box warns you that the migration requires changes to the Identity Vault schema. You can choose to continue or cancel the migration.
Select to continue the migration, or select to cancel the migration.
When the migration is completed, a dialog box displays listing information, warnings, and errors encountered during migration. For example, for all objects added during migration, informational text displays for those objects. You can perform several operations by using this dialog box:
The migration automatically saves a log file describing the content of the dialog box to the project-name/Provisioning/AppConfig folder for the associated User Application. The name of the file will be migrationLog date.log . It is also possible to save the migration log to a file anywhere on disk by clicking the floppy disk icon in the upper right corner of the dialog box.
To revert to the original User Application configuration (for example, if errors occurred during the migration) click the button.
You can undo the migration until you click in the dialog box.
To deploy the migrated configuration directly from the dialog box, select .
If you select this option, the migrated driver is validated before it is deployed. If you don’t select this option, you should run the Project Checker on the migrated driver.
See
Validating Provisioning Objects
in the
Identity Manager 3.5.1 User Application: Design Guide.
Select the desired options in the dialog box, then click .
Designer checks to see if the User Application driver exists in the Identity Vault. If it does not (for example, if you imported a project from a file, or imported a driver from a driver configuration file), Designer displays a dialog box that asks you if you want to deploy the entire driver.
If you want to deploy the entire driver at this time, click .
If you do not deploy directly from the migration dialog box, run the Project Checker on migrated objects.
See
Validating Provisioning Objects
in the
Identity Manager 3.5.1 User Application: Design Guide
.
If validation errors exist for the configuration, you are informed of the errors, which must be corrected before the driver can be deployed.
If you do not deploy directly from the migration dialog box, deploy the driver by right-clicking the name of the driver and selecting .
After the migration, the project is in a state in which only the entire migrated configuration can be deployed. You also cannot import any definitions into the migrated configuration. After the entire migrated configuration has been deployed, this restriction is lifted and you can deploy individual objects and import definitions.
Repeat Step 5 through Step 15 through for each User Application driver in the driver set.
NOTE:When you upgrade a driver to Identity Manager 3.5.1, ensure that all other drivers in the same driver set are also upgraded to Identity Manager 3.5.1. See Upgrading Drivers to the New Architecture.