There are several types of Novell eDirectory data that you can migrate. You can model all types in one session or more (because the modeling information is saved); however, you can only migrate one type at a time. The type you have selected in the
field is migrated when you click the button.The options displayed in the
field are filters that determine what is displayed on the tab. When you select a migration task, the fields (and their data) change appropriately in the tab’s two panels ( and ). For example, when you select , only the paths, fields, and data applicable to applications are displayed in both panels. For the panel, you see what is in your eDirectory tree. For the panel, you see what currently exists in the ZENworks database, and is viewable in ZENworks Control Center.The numbering for the
options represents the suggested migration sequence because of possible dependencies, such as associations that require their applications and associated objects to already exist in order to re-create those associations in Configuration Management. Therefore, you would migrate the applications first, then later migrate the associations. However, you can migrate eDirectory data in any order, including any subsets of a type. This can be useful for an incremental migration, such as migrating your various departments’ applications at different times.You can also delete any item from the
panel, which deletes it from the ZENworks database so it is no longer viewable in ZENworks Control Center.