In Designer 4.0 and later, packages replace driver configuration files; however, you can still import driver configuration files. Any new functionality for the drivers is contained in packages, not in the configuration files.
You can import an Identity Manager driver configuration file into the selected driver set for a project by using theoption, which imports an XML configuration file that can be a driver set, an individual driver, driver channels, or policies. If you import a driver configuration file that contains only a policy, Designer creates the framework for parent containment objects, such as a channel, a driver, or a driver set. Such parent containment objects do not contain attributes; they are only the framework of the channel, driver, or driver set from where the policy came.
You can import a configuration from a file in three ways:
The project file and accompanying file structure for the project to completely import. For information about importing a project, see Section 12.1.2, Importing a Project from the File System.option allows you to import an Identity Manager project that has been saved to the file system through the > option. The project must have a valid .
You can import a previously exported configuration file or one of the sample .xml driver configurations that are included with Designer.
To import a configuration file into a driver set:
Select an Identity Vault in the Modeler view.
Right-click a Driver Set object within the Identity Vault, then select.
In the Import a Driver Configuration File window, type the name of the configuration file, or browse to and select the .xml file.
If you use the Browse feature, by default Designer takes you to the following directories:
C:\Program Files\Novell\Designer\eclipse\plugins\com.novell.idm_<version><time stamp>\defs\driver_configs\current\drivername
You can use one of the .xml configuration files in a selected directory or you can browse to a directory containing an exported configuration file.
Complete the import by filling out the Import Information Requested prompts for the driver configuration file.
The template varies, depending on the driver configuration file selected and the state in which the file was saved. Saved files might only prompt for a driver name, but need other values in order to work in a network environment.
The pre-Identity Manager 3.6 Driver Configuration Wizard adds different policies to the driver, depending on which options you select when you initially import the driver. You cannot change an option that you did not initially choose, because the information is not included in the driver. You must delete the driver and create a new one through the Driver Configuration Wizard.
WARNING:Do not use the Driver Configuration Wizard on the .xml file that you are importing. The Wizard brings up the Import Information Request forms, but these forms are pulled from the default driver that come with Designer and will overwrite the driver you are importing. Use this method only if you need to start over.
The Identity Manager 3.6 Driver Configuration Wizard adds all policies when the driver is imported, and are not lost if you did not select an option in the Import Information Request forms. If this is a driver configuration file that came with Identity Manager 3.6, you can change the driver’s values through the Properties page.
If the driver needs other values and parameters in addition to what appears on the Import Information Requested template, close the template, right-click the driver line in the Modeler view and selectand to fill in what you need. You might also need to fill in GCVs at the driver set level.
Because each driver contains different values and parameters, consult the driver manual that matches the installed driver at the Identity Manager Drivers Web site. Then select the manual for the driver you are configuring.
Click, then click in the Import Configuration Results window.
When you are finished with each imported driver, clickat the Import Configuration Results window.