Packages are the new content management feature in Identity Manager 4.0.1. All new driver content is delivered through packages instead of through driver configuration files.
Packages are managed, maintained, and created through Designer. iManager is package aware, but any changes to driver content through iManager are not maintained in Designer. For more information about managing packages, see Managing Packages
in the Designer 4.0.1 for Identity Manager 4.0.1 Administration Guide.
There are three different ways to upgrade your drivers to packages:
The simplest and cleanest way to upgrade drivers to packages is to delete your existing driver and create a new driver with packages. Add all the functionality you want in the new driver. The steps are different for each driver. For instructions, see the individual driver guides on the Identity Manager Drivers documentation Web site.
If you need to keep the associations created by the driver, you shouldn’t delete and re-create the driver. This option allows you to keep the associations, but still create the driver content with packages.
To replace the existing content with content from packages:
Create a backup of the driver and all of the customized content in the driver.
For instructions, see Section 4.8.2, Creating an Export of the Drivers.
In Designer, delete all objects stored inside of the driver. Delete the policies, filters, entitlements, and all other items stored inside of the driver.
Import the driver packages into the package catalog.
For instructions, see Importing Packages into the Package Catalog
in the Designer 4.0.1 for Identity Manager 4.0.1 Administration Guide.
Install the packages to the driver.
For instructions, see each driver guide at the Identity Manager Drivers documentation Web site.
Add the base, mandatory, and optional packages to the driver to get the desired functionality. These steps are specific for each driver.
For instructions, see each driver guide at the Identity Manager Drivers documentation Web site.
Restore any custom policies and rules to the driver. For instructions, see Section 4.16, Restoring Custom Policies and Rules to the Driver.
The driver now functions as before, but with content from packages instead of from a driver configuration file.
You can keep the driver as it currently is and add new functionality to the driver through packages, as long as the functionality in packages does not overlap the current functionality of the driver.
When you install a package, it can overwrite existing policies, which might cause the driver to not work, hence creating a backup is necessary. If any policy is overwritten you can import the backup driver config file and recreate the overwritten policy.
Before you begin, make sure that any customized policies have different policy names than the default policies. When a driver configuration is overlaid with a new driver file, the existing policies are overwritten. If your custom policies do not have a unique name, you lose those custom policies
To add new content to the driver with packages:
Create a backup of the driver and all of the customized content in the driver.
For instructions, see Section 4.8.2, Creating an Export of the Drivers.
Import the driver packages into the package catalog.
For instructions, see Importing Packages into the Package Catalog
in the Designer 4.0.1 for Identity Manager 4.0.1 Administration Guide.
Install the packages on the driver.
For instructions, see each driver guide at the Identity Manager Drivers documentation Web site.
Add the desired packages to the driver. These steps are specific for each driver.
For instructions, see the Identity Manager Drivers documentation Web site.
The driver contains the new functionality added by the packages.