When creating custom packages, you first need to create a new base package. The base package acts as a master list that tells Designer how to assemble all the custom sub-packages you create.
Base packages should not contain content such as policies or resource objects. We recommend only including package prompts and initial settings information in your base package.
WARNING:Designer does not automatically check if a package functions properly or is complete. If you attempt to deploy a package that is incomplete or does not work correctly, you can inadvertently modify your package targets.
Complete the following steps to create a custom base package.
(Optional) If you want to create a new package category, navigate to the Outline view in Designer and complete the following steps:
Right-click the package catalog, and then select New Category.
Specify the name of the category, then click OK.
For example, if you want to create a base package for a database application driver, you could specify Database as the category name.
(Optional) If you want to create a new package group within a category, complete the following steps:
Right-click the package category where you want to create a group and select New Group.
Specify the name of the package group, then click OK.
For example, if you want to create a base package for a database application driver, you could specify the name of the specific database application as the group name.
Right-click the package group where you want to create a new package and select New Package.
NOTE:All packages must belong to a category and a group within that category. You cannot create a package outside of a package group.
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 a base Active Directory package created by NetIQ, the package short name could be NTIQADIRBASE.
Click the Type drop-down menu and select Driver.
Select Base Package.
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. For example, if you create a new package in an Identity Manager 4.7 environment that uses a feature only available in 4.5, you can use the minimum version to prevent users with Identity Manager 4.0.1 or earlier to install the package.
In the Application Compatibility section, select the minimum and maximum versions of the managed application that this package is compatible with.
NOTE:Identity Manager does not currently enforce restrictions on the minimum and maximum application versions specified. Identity Manager can only provide a recommendation to user who try to install the 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, or select <All> if you want the package to support all possible driver types.
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.
(Optional) If you want to require a particular non-feature package, like a common driver set package, be installed along with your base package, complete the following steps:
In the Outline window, expand the Package Catalog and navigate to the version of the base package you created in the preceding steps.
Right-click the base package and select Properties.
In the Properties window, click Dependencies.
Click the plus icon to and select the package you want to add as a dependency. For more information about common Identity Vault and driver set packages, see Creating Identity Vault and Driver Set Packages.
Click OK.
Drag and drop a development driver from the palette. Follow the steps in Creating a Development Driver in case you wish to install a development driver.
In the Modeler, right-click the development driver, then click Driver > Properties.
In the Properties window, click Packages to install the base package on the driver.
NOTE:Ensure that the package created in Step 7 is listed.
The package list is initially filtered by driver types. To see all available driver packages, deselect Show only applicable package versions.
Click OK.