10.3 Importing a Driver Configuration File
You can import an Identity Manager driver configuration file into the selected driver set for a project by using the Import from Configuration File option, 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.
These configuration files are in XML format, which you can save to a local, removable, or network directory through the Export to Configuration File option. After you select the driver configuration file to import, you are prompted to provide driver-specific information for setting up the driver and building policies. The exported .xml files are compatible with those used by the iManager driver configuration file plug-ins for Identity Manager 2.7. This allows you to export configuration files from Designer and import those files through iManager or through Designer’s Import feature.
You can also use the option as a backup method. For example, if you are working on a group of policies in an Active Directory driver, you can use the to back up your work, adding dates to the exported filenames so you can select a particular driver configuration that you want to use as the basis for your Active Directory driver. If something goes wrong, you can re-import the base driver. You can also use this export/import feature to export and import just the policies you are working on.
Of course, a better method for backing up your projects is through the version control feature. See Section 18.0, Version Control.
You can import a configuration from a file in three ways:
10.3.1 Importing an Identity Manager Project from the File System
The 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 .project file and accompanying file structure for the project to completely import. For information about importing a project, see Section 10.1.2, Importing a Project from the File System.
10.3.2 Importing a Driver Configuration from a File in the Modeler View
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 DriverSet 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:
-
for Windows:
C:\Program Files\Novell\Designer\eclipse\plugins\com.novell.idm_3.0.0.x\defs\driver_configs\current\drivername
-
For Linux:
/home/username/designer/eclipse/plugins/com.novell.idm_3.0.0.x/defs/driver_configs/current/drivername
(The “x” after the idm_3.0.0 number refers to Designer build numbers). 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.
-
-
Click .
-
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.
NOTE: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. If you want to change an option that you did not initially choose, it is not possible, 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.
-
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 select and to fill out what you need. You may also need to fill out GCVs at the driver set level.
Since 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.
-
You might have imported a single driver or a collection of drivers (a driver set). If you are importing a driver set, repeat Steps 4 and 5 for each driver in the driver set. When you are finished with each imported driver, click at the Import Configuration Results window.
10.3.3 Importing from a File through the Outline View
You can use the Outline View to import driver sets, drivers, channels, and policy configuration files from the file system. The following example demonstrates how to import a driver, but the procedure also works for the other files.
-
Double-click the icon under a project name in the Project view. This brings up the project model in the Modeler view.
-
Click the tab.
-
Right-click the Driver Set object and select .
-
In the Import a Driver Configuration File window, type the name of the configuration file, or browse to and select the .xml file.
When a driver is exported, Designer uses the name of the driver set or driver object, to which you can add dates. In this example, it is an Active Directory driver that was exported June 26th and is now being imported.
-
Click , then click to import the configuration file.
To import a policy into a driver set:
-
In the Outline view, click the icon, then click .
-
In the Import a Driver Configuration File window, browse to or specify the XML configuration file name.
-
Click , then click to import the selected policy.
Each policy is saved to its own .xml file. By default, Designer uses the name of the policy or rule selected.
-
In the Perform Prompt Validation window, you are asked if you want to fill in required driver information. If you answer , you see the Import Information Requested dialog box as described in Step 5 and you must provide values to all of the required fields. If you answer , you still see the Import Information Requested dialog box, but it isn’t necessary to fill in the required information.
-
Complete the import by filling out the Import Information forms for the driver configuration file as necessary. Policies are saved with a skeleton driver configuration structure, which designates where the policy resides. In this case, the driver already existed and the imported policy was initially written for that driver.
-
Click .
When the policy or rule is imported, you see the Import Configuration Results window, which indicates if there were any problems with the import procedure.
Errors during the import procedure are displayed with a red icon, and you see an Error description that is related to the operation results. If you have multiple errors, selecting an error displays the error’s description in the field. See Error Messages and Solutions for further information.
-
Click to finish the import process and close the Import Configuration Results window.