Connector Guides › Connectors Guide › Connecting to Endpoints › Lotus Notes/Domino Connector › LND Installation › LND Migration

LND Migration

The LND migration is driven by a text menu-driven interface. When run for the first time, information to be used to connect to a Provisioning Server is requested (defaults are presented in square [] brackets) and password characters are displayed as stars (*) to prevent snooping. Once a successful connection to the Provisioning Server is achieved, all of the connection details (except password) are saved and can be recalled using a simple number displayed as a label the next time the migration interface is run.

When connecting to a Provisioning Server, the migration script queries for all of the existing LND endpoints that are registered within the Provisioning Server. You are then given an opportunity to review the settings for each endpoint (port number, use SSL, and so forth). Once a successful connection to the LND endpoint is achieved, the details entered for it are saved in the Provisioning Server and the data migration itself takes place.

From the bin folder of the Connector Server, find LNDMigrate.bat for Windows and LNDMigrate (without .sh) for UNIX environments to start the migration.

<jcs-home>\bin

Log files are generated in

<jcs-home>/resources/lnd/LNDMigrate.log

Following are the migration updates that take place:

• eTLNDAccount attributes
  • eTLNDInternetOnlyUser and eTLNDNoIDFileCreation attribute values are copied from the Provisioning Manager to account's matching LND Person document.
  • Values for the eTLNDLocalAdmin and eTLNDManager attributes are now Provisioning Server LDAP DNs and must be translated from the previous Notes internal name syntax.
  • A new field for the UserUniqueOU name is calculated and stored in the Person document for accounts that have a "Unique OU" value set. This improves performance when re-exploring as it saves the connector from having to look up every account's immediate parent to decide whether it is a real OU or a unique OU.
• eTLNDAccountTemplate attributes
  • Values for the eTAccountContainer, eTLNDGroupMembership, eTLNDLocalAdmin, and eTLNDManager attributes are now Provisioning Server LDAP DNs and must be translated from the previous Notes internal name syntax.

    Note: The values of eTLNDLocalAdmin and eTLNDManager contain special syntax to differentiate “Unique OU”. Refer to section How Managed Objects are Referred to in the Java LND Connector for details. If the account template does not have an LND endpoint assigned, the values of eTLNDLocalAdmin and eTLNDManager will not be converted to “Unique OU” syntax for unique OUs, instead all unique OUs will be treated as real OUs.

Important! After the migration tool has run successfully, you must re-run the exploration and correlation for those endpoints that have just been migrated in order to update the account DN syntax stored in the repository and fix all the broken links between the accounts and global users due to the changed account DN syntax.