After you have created a package, you must add Identity Manager content to the package for the package to have value.
You can add different types of content to a package, including policies, ECMAScript objects, package prompt resources, and entitlements. For a full list of all types of content you can add to a package, see Table 6-1.
IMPORTANT:You can only add content to a package you create. You cannot add content to a package you have imported unless you also have the Designer project in which the package was developed.
For more detailed information on adding GCVs, prompts, policies, and filter extensions to a feature package, see the following sections:
To add content to a feature package, you must first install the package on the driver, add the content item to the driver, then add the configured content item to the package. You can then view the content item under the feature package in the Package Catalog. When users install the package, whatever language Designer is using is the language in which the package itself is installed.
Complete the following steps to install the package on the driver:
Verify you have a development driver installed. If not, follow the steps in Creating a Development Driver to install a development driver.
Verify that you have created a feature package. Otherwise, follow Creating Feature Packages to create a new feature package.
In the Modeler, right-click the development driver, then click Driver > Properties.
In the Properties window, click Packages to install the feature package on the driver.
Click the plus icon to display the packages you can install on the driver.
The package list is initially filtered by driver types. To see all available driver packages, deselect Show only applicable package versions.
Select the feature package you want to install and click OK.
Click OK.
Specify configuration information for any prompts displayed in the Installation Wizard, then click Next.
Click Finish to install the package.
As with Identity Vault and driver set packages, you can also add GCVs to a feature package. For information on adding GCVs to a package, see Adding GCV Resource Objects.
To add package prompts to a feature package, complete the following steps:
Verify that you have created a feature package. Otherwise, follow Creating Feature Packages to create a new base package.
Right-click the feature package in the package catalog and select Generate Prompt Resource.
Select the type of package prompt you want to configure:
Initial Settings: This option creates all of the default attributes required to create a driver object.
Upgrade Settings: This option creates a Resource object that contains style sheets that maintain the package settings so that they are not overwritten when the new package is installed. Select this option if the package you are creating is an upgrade to an existing package.
NOTE:You can only create one of each type of prompt for a particular package.
In the package catalog, expand the package version and Resources directory.
Right-click the new package prompt and select Properties.
Verify the type of package prompt.
Specify the order in which you want the Driver Configuration Wizard to display the current package prompt. The Wizard displays prompts in ascending order starting from 0.
Verify the target displayed is correct for the package prompt. If you want to add the prompt to a different package, click Add, browse to the package, and click OK.
Click the Prompts tab. The Properties window displays what the current package prompt looks like in the Driver Configuration Wizard.
To add policies to a feature package, complete the following steps:
Verify that you have created a feature package. Otherwise, follow Creating Feature Packages to create a new base package.
In the Outline view, right-click the driver name and select New > DirXML Script.
Specify a name for the new policy and click OK.
In the Outline view, right-click the new policy and select Add to Package.
Select the feature package where you want to add the policy and click OK.
NOTE:Only packages that are created in Designer are displayed in the list. Any packages that are imported into Designer are not displayed in the list.
Double-click the policy and use the Policy Builder to add rules as necessary. For information about building policies in the Policy Builder, see Managing Policies with the Policy Builder
in NetIQ Identity Manager - Using Designer to Create Policies.
Close the policy and click Yes to save the resource.
Repeat Step 5 through Step 7 for each policy you want to add.
When you create a custom feature package, you should configure Identity Manager to allow data flowing through your environment to go through your new driver’s workflow. For your driver and associated packages to process data, you must create a filter.
Filters act as gates to stop data going into or out of your driver. Filters allow you to specify criteria against which the driver matches any incoming our outgoing data and then executes a specified action. You can filter data on both the Publisher or Subscriber channels of your driver, or simply set up a filter that notifies you when an object is modified.
You should understand the types of data you want the driver with that package installed to process. You can then configure the specific subset of data you want to be processed or synchronized by the driver.
For example, you may want the driver to sync data regarding user objects. You can create a filter extension within your feature package that allows any data related to user objects through the workflow, while blocking any other type of data. If the Identity Vault sends an event about a group object to your driver, the filter sees that the event is not about a change to a user object and does not send the event through the driver workflow.
To create a filter, you must create a filter extension resource in your feature package and then deploy that package to a driver. For more information about filter extensions, see Controlling the Flow of Objects with the Filter
in NetIQ Identity Manager - Using Designer to Create Policies.
Complete the following steps to create a filter.
Verify that you have created a feature package. Otherwise, follow Creating Feature Packages to create a new base package.
In the Outline view, right-click the driver name and select New > Resource.
Specify a name for the new filter resource.
Click the Content type drop-down menu and select application/vnd.novell.dirxml.filter-ext+xml.
NOTE:Filter extensions can only be created and modified when the Identity Vault is running in package development mode. You cannot perform these operations with development mode disabled.
Click OK.
In the Filter Editor, add and configure filters as necessary. For information about configuring filters in the Filter Editor, see Controlling the Flow of Objects with the Filter
in NetIQ Identity Manager - Using Designer to Create Policies.
Close the filter and click Yes to save the resource.
In the Outline view, right-click the new filter and select Add to Package.
Select the feature package where you want to add the filter extension and click OK.
NOTE:Only packages that are created in Designer are displayed in the list. Any packages that are imported into Designer are not displayed in the list.
Repeat Step 2 through Step 9 for each filter you want to add.
You must add content to a User Application driver through a non-base package, as described in the following steps:
Create an Identity Vault in the package development mode.
Install the User Application driver with the latest User Application package.
Create a new User Application non-base package and install it on the User Application driver.
Configure custom objects such as roles, resources, PRDs, or categories and then add them to the non-base package.
Release the non-base package after you have completed configuring the custom objects.
You must install the non-base package only on a driver that already includes a User Application base package. After you have completed the preceding steps, the customizations that you made to the custom objects are preserved on further upgrades or downgrades of the non-base package.
You must modify the existing content of a User Application driver through a non-base package, as described in the following steps:
Create an Identity Vault in the package development mode.
Install the User Application driver with the latest User Application package.
Create a new User Application non-base package and install it on the User Application driver.
Modify the existing Data Abstraction Layer objects and then add them to the non-base package.
IMPORTANT:Ensure that you add the entire object group to the non-base package because Designer does not allow you to add individual system objects. For example, to modify an Entity object, add the entire Entity group to the non-base package.
Release the non-base package after you have completed configuring the custom objects.
You must install the non-base package only on a driver that already includes a User Application base package. After you have completed the preceding steps, the customizations that you made to the custom objects are preserved on further upgrades or downgrades of the non-base package.