6. Import/Deploy: What's New

(Home)     Previous     Next


1. Deploying Jobs

After deploying a job, Designer issues a command to the eDirectory server to determine if the job is correctly configured. Results from the command are displayed in the Deployment Result dialog box. The following image shows an example of an incorrectly configured job. In this case, the Driver object is disabled.




The job definitions for drivers and driver sets are imported into Designer when you import from an Identity Manager 3.5 server. These definitions then appear in the New Job dialog box.


2. A History Button on the Import Dialog Box

The Import dialog box now has an Import History button, which is to the right of the Browse button. Selecting this button shows a list of previously imported objects. The list is filtered to show only objects that can be imported into the current context. For example, policies are displayed if you are importing drivers into a driver set.




3. Deploying DN References Within DirXML Script Policies

Certain statements or verbs within DirXML Script can contain references to other DirXML Script or Mapping Table objects. This version of Designer has been improved to handle these references during an import or deploy operation. For example, the "include" statement causes the rules from the policy referenced by the name attribute to be included at runtime into the including policy as if they were part of the including policy at the point of inclusion. The import and deploy code detects these references and includes the referenced object in the operation.

For example, if policy P1 has an include statement that references policy P2 when P1 is deployed, P2 is also deployed. Likewise, if P1 is imported into Designer, P2 is imported. References are also detected for the "token-map" verb, which references a Mapping Table object. Mapping Tables were introduced in Identity Manager version 3.5.

4. Importing Multiple E-mail Templates

Previous versions of Designer allowed only a single e-mail template to be imported at a time. This version of Designer has been improved to support importing multiple e-mail templates in a single operation.




Other Enhancements and Bug Fixes
  1. Fixed a Directory Abstraction Layer Editor error on import of a User Application driver from an Identity Vault. Click here for details.
  2. eDir2eDir import now works correctly when multiple trees and servers are on the same machine. Click here for details.
  3. Engine control values are now created for deployed drivers. Click here for details.
  4. Resolved the error on importing a driver from an Identity Vault. Click here for details.
  5. Resolved the unhandled exception when you import from an Identity Vault by using browse permissions (not admin). Click here for details.
  6. Driver set GCVs are now exported with a driver. Click here for details.
  7. Designer now compares the Designer server version with the live server version during the deploy. Click here for details.
  8. Import now completes without any errors when a period is in the object name. Click here for details.
  9. Named passwords are now imported for jobs. Click here for details.
  10. Designer now reconciles and compares named passwords on a job. Click here for details.
  11. Designer now allows named passwords on a job and then deploys them. Click here for details.
  12. When deploying a job, Designer now issues a NotifyJobUpdate command to the engine. Click here for details.
  13. An import with improper credentials on a notification template now captures an error in import results. Click here for details.
  14. The Deploy filter no longer creates an empty XMLScript policy. Click here for details.
  15. Importing iManager-exported configuration files now fixes DN references in the policy data. Click here for details.
  16. The Identity Vault name now displays in deployment results. Click here for details.
  17. Exporting to a configuration file no longer fails if a policy in the channel contains a relative reference to the mapping table in a library. Click here for details.
  18. Importing from the Project view no longer brings in a duplicate library during an eDir-to-eDir import. Click here for details.
  19. Relative DN references are now imported correctly. Click here for details.
  20. A policy not in a policy set now brings in the referenced policy. Click here for details.
  21. The Deploy summary now shows the mapping table as an item to be deployed. Click here for details.
  22. A linked policy is now imported properly when that policy is contained in a library. Click here for details.
  23. Password policies are no longer orphaned in 3.0.1 example configurations. Click here for details.
  24. The Deploy summary now shows objects referenced in channel containers. Click here for details.
  25. A library deploy context is now in qualified-dot notation after an import. Click here for details.


(Home)     Previous     Next