The dialog supports multiple selections which allows you to unselect a
group of drivers. To do this select the drivers you wish to exclude
from the import and then toggle their import state by pressing the space bar.
While importing a Driver Set the import dialog now allows you to select
which drivers should or should not be imported. By default all of a Driver Sets
drivers will be selected for import, to exclude a driver from being imported with
the Driver Set un-check the box next to the drivers name.
The dialog supports multiple selections which allows you to unselect a
group of drivers. To do this select the drivers you wish to exclude
from the import and then toggle their import state by pressing the space bar.
This version of Designer handles eDir-eDir driver imports in a different manner.
Prior to this version the detection and handling of eDirectory driver imports was
performed after one side of the eDir-eDir connection was imported. With this version
the user can select the other side of the eDir-eDir connection while in the import
dialog. This change was made so that all imported objects could be displayed on a
single summary page.
The following steps will allow a user to import an eDir-eDir driver and have them
connected as such in the Enterprise Modeler.
Select "Browse..." in the import dialog to add one side of the eDir-eDir connection
to the import list. The following is an example of a driver import. Similar steps would be
performed if the driver was being imported with a Driver Set.
In the import dialog select the eDirectory driver. Notice that eDirectory drivers
are easily identified in the import list by the eDir-eDir icon used by the Enterprise modeler.
The information label at the bottom of the dialog shows which eDir driver, if any,
the selected driver will be connected to after the import. Also note the "eDir2eDir"
button is now enabled on the right side of the import dialog.
Selecting the "eDir2eDir" button will display either a credentials dialog or a eDirectory
browser. The credentials dialog allows you to provide the user name and password for the
other side of the eDir-eDir connection. If Designer detects that the other Identity Vault
already exists in Designer or if this eDirectory driver is already associated with another
eDirectory driver the credentials page will not be displayed.
After providing the credentials to authenticate to the other eDirectory tree a browser
will allow you to select the corresponding eDirectory driver.
After selecting the corresponding driver and the "OK" button you will be returned to the
import dialog. Notice the information label at the bottom of the import dialog now shows
the full name of the eDirectory driver you just selected. If you wish to change the
associated eDirectory driver simply repeat the process again.
Prior versions of Designer displayed a separate summary dialog prior to each deployment.
This version now displays a single summary prior to imports and deployments.
The summary dialog has also been changed to display both the current eDirectory
and Designer values for all objects being imported or deployed. By default only
different values are displayed, to display all values unselect the
"Show only differences" check box.
Objects that exist in either Designer or eDirectory but not both are identified by a warning
overlay image. This helps you identify new objects being imported or deployed or those
that are may be overwritten. After viewing the import or deployment summary you can
continue the operation or select "Cancel" to quit.
This summary dialog is also used for comparing objects in eDirectory and Designer. To compare an object
simply select the object or objects in the Outline view or Enterprise Modeler, right click with the mouse
and select Live Operations->Compare.
A new result dialog is displayed after performing an import or deploy to
inform the user of any warnings or errors that occurred. A single dialog is displayed
for all imported or deployed objects. Any errors or warnings generated for
a specific object are listed as children under the object. Objects that generated
errors are identified by a "red" icon, warnings with a "yellow" icon. Objects that
did not generate warnings or errors are identified by a "green" icon.
For example the following image shows the results of two drivers that were deployed. The
driver named "Delimited Texta" deployed successfully while driver "Delimited Text"
deployed with warnings.
To view the errors and warnings associated with the imported or deployed
object simply expand the object node by selecting the plus sign. Selecting a
specific error or warning in the list will display its details.
The following shows an example of an Incompatible Identity Manager Version warning.
The details of the warning indicate that the driver has a Log Event selected in it's
properties that is not supported by the version of Identity Manager running on the
server we are deploying to.
The import and deploy preferences pages have been combined and reorganized. The various
import and deploy preferences are now located on a tab within a single preference page.
There is also a tab to contol which import and deploy user prompts are turned on.
This version of Designer has improved handling of cross driver policy references.
A cross driver policy reference is a policy that is referenced by a driver that does not
contain the policy. For example if Policy1 was contained under Driver1 but Driver2 referenced
Policy 1 in its Input Transformation then Driver2 would have a cross driver policy reference to
the policy.
If a cross driver policy reference is encountered during an import or deploy
opertion a dialog will allow you to choose whether or not to process the referenced policies.
This dialog may be turned off by checking the "Dont show this dialog again" check box.
All cross driver policy references are imported and deployed by default. This functionality
may be turned off however on the the Import and Deploy tabs located on the Designer for IDM
Import/Deploy preference page.
When importing an object with a cross driver policy reference
additional objects may be created in Designer. For example during an import if the referenced
policy was contained in a Driver that did not already exist Designer, then the referenced policy
and its Driver would be created. Likewise deploying an object with a cross driver policy reference
may create additional container objects in eDirectory.
 |
Other Enhancements & Bug Fixes |
|