To take advantage of the latest 4.0.2 features, you need to upgrade to Designer 4.0.2 AU. In addition, you need to install the User Application Base Version 2.2.0.20120516011608 package on your User Application driver.
The steps you need to perform are different depending on whether you are working with a package-enabled driver created in version 4.0 or 4.0.1, or an older non-package enabled driver. In either case, the update process automatically preserves any customizations made to the driver.
NOTE:If the User Application Base package 2.2.0.20120516011608 does not show up in the Import Package dialog, you have to manually import using the Browse button and get it from the following location: <designer root>/packages/eclipse/plugins/NOVLUABASE_2.2.0.20120426113439.jar.
Role and Resource Service drivers are not migrated. If you have an existing Role and Resource Service driver, you must create a new one for version 4.0.2.
Before you migrate the driver, you need to perform some setup steps to prepare the Designer project for migration:
Launch Designer 4.0.2.
If you have an existing Designer project that contains the User Application you want to migrate, make a backup copy of the project:
Right-click the name of the project in Project view, then select .
In the dialog box, type a new (or accept the default name), then click .
Update the schema for your existing project by selecting the Identity Vault in the Modeler view and choosing .
After you have updated the schema, you should verify that the version number for Identity Manager is correct in your project. To verify the version number:
Select the Identity Vault in the Modeler view and choose .
Select in the left navigation menu.
Select a server and click .
The field should show .
If you do not have an existing Designer project to migrate, create a new project by using .
The 4.0.2 User Application Driver requires the package.
When you begin working with an Identity Manager project, the user interface automatically prompts you to import new packages into the project. If you choose not to import the new User Application Base Version 2.2.0.20120516011608 package at that time, you need to install the package later, as described below.
To import the new User Application package:
Import the package by right-clicking and selecting .
Select the package.
Click .
To upgrade the new User Application package:
Right-click the 4.0 User Application Driver and click .
Click .
A check mark is displayed in the column for the User Application Driver base package.
Click for the package that indicates there is an upgrade available.
From the drop-down list, click .
Select the version that you want to upgrade to. Then, click .
All versions that are available to upgrade to are listed.
Click .
Fill in the fields with appropriate information to upgrade the package. Then click .
Read the summary of the installation. Then click .
Review the upgraded package. Then click to close the Package Management page.
The driver migration is not complete until you deploy the entire driver to the Identity Vault.
Open the project in Designer and run the Project Checker on the migrated objects.
See the section on 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 , or in the Modeler view, right-click the driver and choose .
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.
To migrate a 3.6.1 or 3.7 User Application Driver to 4.0.2:
Make a backup copy of the Designer project, if you have not done so already.
Import the User Application 3.6.1 or 3.7 driver into Designer.
Migrate the driver to 4.0.
Use one of the following methods to run 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 .
If the dialog box displays, 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.
If you are prompted for a driver version to migrate to, select , then click .
Designer warns you that schema changes are required in the Identity Vault. Select to continue the migration (if you have already updated the Identity Vault schema in a separate process), or select to cancel the migration (if you have not already updated the Identity Vault schema).
NOTE:The Identity Vault schema is updated when you run the RBPM Installation.
Check for project errors and remove the errors, if any are present.
Install the 4.0.2 User Application package () on the driver:
Import the package by right-clicking and selecting .
Select the package.
Click .
In the Developer View, right-click on the User Application Driver and click .
Go to the tab in the page.
Click on the symbol in the top right corner.
Select the and click on the button.
Complete the user application driver configuration.
Check for project errors and remove the errors, if any are present.
Deploy the 4.0.2 packaged driver.