Once you create your custom base package, you should configure the initial settings you want to use for the driver. When you install a driver, the driver’s initial settings create a set of objects that the driver needs to be able to start.
The initial settings for your driver are specified as ds-object code. The code installs driver shim parameters, driver start options, named passwords, GCVs, and filters.
By default, when you create a package, the initial settings XML for the package is empty, as displayed in the package Properties window. Unless you are extremely proficient with XML and know are familiar with the Identity Manager schema, we recommend you populate your initial settings from an existing template.
You can use a working driver as a template, if you want your package to use specific settings in that driver. For example, if you want to create a custom eDirectory package, you can use an eDirectory driver as your development driver and populate your initial settings from the development driver.
If you only want to include a minimum of initial settings in your package and configure those settings manually, you can also add an empty Generic App driver.
You can only add certain driver properties as ds-attribute objects in the Initial Settings, as listed in the table below.
|
ds-attribute Object |
Description |
|---|---|
|
name |
Specifies the name of the driver. |
|
application-schema |
Specifies the schema of the application to which the driver connects. Each application has its own schema, but Identity Manager does not necessarily use all classes or attributes from a particular application schema. |
|
configuration-manifest |
Contains the Driver Health Configuration settings for the driver, which allow you to monitor the state of the driver and configure the driver to perform actions automatically depending on the driver’s health state. For more information about the Driver Health Configuration, see Driver Health Configuration. |
|
driver-filter-xml |
Specifies how the driver should filter incoming data. We recommend you do not use this ds-attribute to configure the base driver filter, but instead create filter extension objects. For more information about creating filter extension objects, see Adding Filter Extensions |
|
java-module |
Specifies the driver shim XML configuration the driver uses. For example, com.novell.nds.dirxml.driver.nds.DriverShimImpl or com.novell.idm.driver.ComposerDriverShim. |
|
log-events |
Specifies the types of events you want the driver to log in the audit log. For example, you can configure the driver to log errors, warning, or specific events like object modifications. By default, the driver uses the settings from the driver set, as specified in the Log Level tab in the driver set Properties window. For more information about configuring log levels, see Driver Set Log Levels. |
|
shim-config-info |
Specifies the Driver Parameters settings displayed in the Properties window for the driver. |
|
global-config-values |
Specifies any GCVs configured on the driver. For more information about GCVs, see Driver Global Configuration Values. |
|
global-engine-values |
Specifies the engine control values used by all drivers, including the subscriber channel retry interval and maximum eDirectory replication wait time. For more information about engine control values, see Engine Control Values. |
|
driver-start-option |
Specifies the default startup option for the driver. For more information about driver startup options, see Startup Option. |
|
named-password |
Specifies any named passwords configured on the driver. For more information about named passwords, see Driver Named Passwords. |
Complete the following steps to add initial settings to your base package.
In the Outline view, right-click the base package, then select Properties.
Click Initial Settings.
Click Populate From Template.
WARNING:When you populate your initial settings from a template, Designer overwrites any XML currently in the Initial Settings window. If you have any previously-customized XML, ensure that you save the existing XML before clicking Populate From Template.
In the Model Browser window, select the driver you want to use as a template, then click OK.
NOTE:You can use any driver currently available in your workspace to populate your Initial Settings window.
Modify the package initial settings as necessary for your environment.
When finished, click OK.