Notes on migrating users from 6.5 or an earlier version to 7.0 or later - 7.3

When you use the dbmigration tool to migrate users from 6.5 or an earlier version to 7.0 or later, pay attention to the following:

• You need to define the domain property in the file <$INSTALLDIR>/conf/mdm.conf. For example, tac.domain=@company.com. This allows the usernames from the source MDM server to be translated into emails.
• You need to provide the Talend Administration Center connection information in the file dbmigration.properties. For example:

  tac.baseUrl=http://localhost:8080//org.talend.administrator
  tac.authUser=security@company.com
  tac.authPass=admin

• If a user to be migrated from the source MDM server does not exist in Talend Administration Center, a new user will be created for the target MDM server.
  • If the user from the source MDM server owns the administration role, the new user created for the target MDM server will have the Master Data Management type. Otherwise, the newly created users will have the No Project Access type.
  • If the user from the source MDM server has more than one system role, the new user created for the target MDM server will use the role with the lowest privilege and a warning message will be displayed because an MDM user has one and only one system role from 7.0.
  • If the user from the source MDM server owns both the System_Admin and administration roles and does not own any other system roles, the new user created for the target MDM server will have the Super Admin user type.
  • If the user from the source MDM server owns the administration role but does not have the System_Admin role, the administration role will be ignored directly by the new user created for the target MDM server and the corresponding warning message is displayed.
  • If the user from the source MDM server is inactive, the new user will be inactive.
  • The new user will reuse the password of the user to be migrated.
• If a user to be migrated from the source MDM server already exists in Talend Administration Center, the Master Data Management Web Role of the existing user for the target MDM server will be updated accordingly.
  • If the user from the source MDM server has more than one system role, the existing user for the target MDM server will use the role with the lowest privilege and a warning message will be displayed because an MDM user has one and only one system role from 7.0.
  • If the user from the source MDM server has only one system role System_View, the migration of the user will fail and an error message will be displayed because this system role no longer exists from 7.0.
  • If the user from the source MDM server is inactive, any MDM privileges of the existing user will be removed for the target MDM server .