You must migrate the version 3.5 or 3.5.1 User Application drivers that you want to use in Identity Manager 3.6. 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, while maintaining existing configurations (for example, custom entities and provisioning request definitions).
WARNING:You must use Designer for Identity Manager to migrate User Application drivers. You cannot use iManager.
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 User Application: Design Guide).
Install Designer for Identity Manager version 2.1.1 with Roles Based Provisioning Tools.
(Optional.) Create a new provisioning project to store the local representations of the artifacts that are located on your Metadirectory server. To migrate an existing project, continue with Step 3.
For instructions on creating a provisioning project, see
Setting Up a Provisioning Project
in the
Identity Manager User Application: Design Guide.
To populate the new provisioning project, import the driver set that contains the User Application drivers that you want to migrate.
See
Importing Provisioning Objects
in the
Identity Manager User Application: Design Guide.
Make a backup copy of the new or existing provisioning project that contains the User Application driver to migrate.
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 driver and select .
In the view, right-click the name of the User Application driver and select .
In the view, right-click the name of the User Application driver and select .
This step in the process migrates the local definition of the driver found in the Designer workspace. These changes are not made to the Metadirectory server until a later step when you deploy the changes. You must use the Outline view to perform the deployment, and you must deploy the entire driver.
If the dialog box displays, select .
This dialog box informs you that migrating the User Application will close all editors.
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.
Make sure is NOT selected.
Open the project and run the Project Checker on the migrated objects.
See “Validating Provisioning Objects” in the Identity Manager User Application: Design Guide. If validation errors exist for the configuration, you are informed of the errors. These errors must be corrected before you can deploy the driver.
Navigate to the Outline view, right-click the driver, and select .
After the migration, the project is in a state in which only the entire migrated configuration can be deployed. You cannot import any definitions into the migrated configuration. After the entire migration configuration has been deployed, this restriction is lifted, and you can deploy individual objects and import definitions.
Repeat this process for each User Application driver in the driver set.
NOTE:When you upgrade a driver, ensure that all other drivers in the same driver set are also upgraded to the same version. See Upgrading Drivers to the New Architecture.