Connector Guides › Connectors Guide › Connecting to Endpoints › LDA Connector Migration to DYN JNDI › How the LDAMigrate Script Migrates the LDA Connector › DYN Object Creation

DYN Object Creation

After the migration process calculates metadata for the new endpoint type, the script prompts you for the connection details to a target CA IdentityMinder Provisioning Server. The migration process makes the following changes to the Provisioning Server that you specified:

• Creates a DYN JNDI endpoint type named LDAP DYN and populates the endpoint with the calculated metadata. The LDA namespace remains unchanged.
• Searches under the LDA namespace and clones any directories discovered into equivalent DYN endpoints under the LDAP DYN endpoint type. This process maps LDA attributes on directories to their DYN equivalents. The migration script prompts you for the password for each directory, because the migration process cannot discover the passwords. The migration does not affect the LDA directories.
• Searches and clones all LDA account templates (policies) by mapping their LDA attributes to their DYN equivalents, and puts them in the following container:

  eTDYNPolicyContainerName=DYN Policies, eTNamespaceName=LDAP DYN,…
  

  Note: The migration process does not affect the LDA account templates.

• Searches for all role and account template inclusions which name LDA account templates. The script changes all references to point to the equivalent DYN account templates, optionally deleting the existing LDA references. This deletion is the only change that the script makes to the LDA data that existed before the migration.
• Creates a list of the existing LDA inclusions in the LDAMigrate.log file.
• Performs the policy and directory inclusions migration.

  For example, the script creates a clone of an entry in the first container in the second container listed, as shown in the following example:

  eTSubordinateClass=eTLDADirectory,eTSuperiorClass=eTLDAPolicy,eTInclusionContainerName=Inclusions,eTNamespaceName=CommonObjects,dc=… 
  

  eTSubordinateClass=eTDYNDirectory,eTSuperiorClass=eTDYNPolicy,eTInclusionContainerName=Inclusions,eTNamespaceName=CommonObjects,dc=…