After creating a base package, you need to create the feature packages that users install with the base package. Feature packages contain the bulk of the actual content for a driver, including policies, GCVs, filters, and prompts.
Creating the content for a package is different than creating the package. This section explains how to create the package, then Adding Content to Packages explains how to add the content to the package.
If you need several feature packages that cover a similar area of functionality, you can organize those packages using package groups. For example, when you install the LDAP driver using the LDAP Base package (NOVLLDAPBASE), the optional features listed do not display the name of each specific package by default but instead group features into the package groups Default Configuration, Entitlements, Password Synchronization, Data Collection, and Account Tracking. Users can then choose to install those optional features as a whole, rather than selecting a particular package.
NOTE:
We recommend you create and configure mandatory feature packages sparingly. If a feature or resource is required for all installations of the driver, you should include the feature in the base package, instead.
All packages must belong to a category and a group within that category. You cannot create a package outside of a package group.
Feature packages should belong to the same package group and category as the base package to which they belong.
When you create multiple feature packages, we recommend using package groups to organize packages by feature. This can make the structure of the different features more clear to the end user.
Right-click the package group where you want to create a new package and select New Package.
Specify a name, version number, and description for the package in the appropriate fields.
Specify a short name for the package in the appropriate field. Identity Manager and Designer display the specified short name when you open the package in a user interface. This name must be unique in the Identity Vault.
NOTE:The standard short name for a package is 12 characters long, separated into three sections of four characters: [Vendor][Target system][What package does].
For example, if you have an Active Directory feature package created by NetIQ, the package short name could be NTIQADIRBASE.
Click the Type drop-down menu and select Driver.
Verify the package category and group are correct.
Click Next.
In the IDM Compatibility section, select the minimum and maximum versions of Identity Manager that this package is compatible with. The selected versions should correspond to the versions selected for the base package.
In the Application Compatibility section, select the minimum and maximum versions of the managed application that this package is compatible with. The selected versions should correspond to the versions selected for the base package.
Select one or more driver types in the Available Driver Types list with which you want the package to be compatible and use the right-arrow icon to move them to the Supported Driver Types list
NOTE:The package must support at least one driver type. Ensure you select the type of application you used when creating your development driver.
Click Next.
Specify or modify the vendor information you want to include in the package, then click Next. You must specify the vendor name for the package.
Review the Summary page and click Finish.