

Connector Guides › Connectors Guide › Connecting to Endpoints › LDA Connector Migration to DYN JNDI › How the LDAMigrate Script Migrates the LDA Connector
How the LDAMigrate Script Migrates the LDA Connector
During the migration, the LDAMigrate script does the following:
- Rolls the LDA extension mapping files from the mappings/ directory into an equivalent metadata document against the DYN schema (including visual grouping metadata). The LDAMigrate script then uses this document to create a DYN JNDI namespace named LDAP DYN.
- Copies all LDA directories and LDA account templates to the new DYN JNDI namespace.
- Updates all provisioning roles referencing LDA account templates to reference the equivalent DYN JNDI account templates.
- Creates a DYN JNDI namespace named LDAP DYN which replaces the superseded LDA namespace.
- Creates equivalents to any existing LDA directories under LDAP DYN.
- Creates equivalents of all existing LDA account templates under LDAP DYN.
Note: Before running the migration script, you must be able to contact the LDA endpoint because the LDAMigrate script must validate the password. To ensure that the migration runs smoothly:
- Wait until the endpoint becomes available before running the LDAMigrate script (preferred method), or
- Skip the unavailable endpoint by entering 'B' for its password when prompted by LDAMigrate.
Copyright © 2013 CA.
All rights reserved.
 
|
|