11.0 Importing into Designer

The Import feature allows you to import the following items into defined projects:

Depending on a project’s complexity, importing can save you time in building and rebuilding drivers, channels, packages, and policies. For instance, after a driver, channel, package, or policy is built, you can import it into new projects and modify it to run in the new environment instead of starting from scratch on each new driver, channel, package, or policy.

You import projects, drivers, channels, schemas, and policies from an existing OpenText eDirectory tree running the OpenText Identity Manager system (Identity Vault), or from an exported project located in the file system. You import packages from the file system or the auto update feature in Designer. In Designer, use the Deploy feature to save drivers, channels, and policies into a OpenText Identity Manager server in an Identity Vault. Use the Export feature to save project, drivers, channels, and policies to a local, removable, or network directory.

What you are able to import depends where you are at within a project. To import an OpenText eDirectory object, you must have sufficient rights to access the OpenText eDirectory tree that is associated with the Identity Vault you are designing. Each of the following sections explains how to import each component of your OpenText Identity Manager solution.

During import, Designer does not import anything that is encrypted. This includes named passwords, e-mail notifications, existing certificates, and the Secure Login administrator password.