Migrating Control Room data

You can migrate your V10.0.x Control Room data to the V11.0 Control Room

Before you begin

  • Back up the following repository and databases in the source Control Room V10.0.x environment:
    • Control Room V10.0.x shared repository
    • Control Room V10.0.x SQL database
  • Ensure you have access to the source Control Room V10.0.x repository path through a shared drive and you have the following information about your V10.0.x environment:
    • The credentials to connect to the Control Room V10.0.x SQL database
    • The master key to connect to the Control Room V10.0.x credential vault
      Tip: If your source Control Room uses the express mode to store the credential vault master key and you haven't a copy of the key available, you can recover the key from the CredentialVault.dat file in the source Control Room repository.
  • Ensure that Control Room V11.0 is installed in the target environment and the following settings are configured:
    • Control Room administrator
    • Credential vault
    • Version control (if applicable)
    Attention: The authentication type must be the same in both the V10.0.x and V11.0 environments otherwise you cannot migrate your data.
  • Take the following actions to ensure that Control Room V11.0 can connect to the source Control Room V10.0.x database during data migration:
    • If you plan to use Windows authentication, Control Room V11.0 uses the user that runs the Control Room V11.0 services to connect to the source database. Ensure that this user has access to the source database.
    • If you plan to use a secure connection, import the certificate for the SQL Server source database system into the Control Room V11.0 Java trust store by using the following command: 
      jre\bin\java -jar certmgr.jar -appDir "C:\rpa_installation_directory" -importTrustCert "certificate_path"

About this task

During data migration, you can migrate data for the following artifacts:
  • Task bots and MetaBots in the repository with version history if applicable
  • Users, roles, and permissions
  • Schedules
  • Credentials
Important: To avoid data conflicts, do not perform any of the following actions in your V10.0.x environment during data migration:
  • Create users, roles, or permissions.
  • Create and upload any metadata, for example, new bots.
  • Create schedules.
  • If you have version control enabled, check out bots.
  • Schedule or deploy on-demand bots.

Procedure

  1. Start the V11 control room and log in as the Control Room administrator.
  2. Migrate your data to the target environment.
    Go to ADMINISTRATION > Migration and click Migrate data or migrate data now.

    The migration wizard guides you through migrating your data from the Control Room V10.0.x database to the new V11.0 database. You can migrate data by roles, users, or bots.

    For more information, see Migration overview in the Automation Anywhere documentation.

    The Data tab shows you a summary of the roles, users, bots, schedules, and credentials that will be migrated.

  3. Verify that all the data can be migrated and click Migrate data.

Results

When the data migration finishes, a summary of the migration is displayed. The audit log also contains entries that show the progress of the migration for each artifact. Check both the migration summary and the audit log for errors.

V10.0.x roles and users are migrated to the equivalent roles and users in V11 with the following exceptions:
Roles
  • Roles with upload, download or delete permissions in the source Control Room are granted run/schedule permission in the target Control Room.
  • If a user-defined role exists in both the source and target Control Room, the role name gets a _1 suffix when it's migrated. For example, if a Bot_Manager role is available in both versions of the Control Room, a new Bot_Manager_1 role is created during migration.
Users
Users with the same name in both the source and target Control Room have _1 suffix added to the name after migration. For example, if the user Mike_Lee exists in both versions of the Control Room, a new user name, Mike_Lee_1, is created during migration. For Active Directory users, if a domain user already exists in the target Control Room, the user and their dependencies are skipped during migration.

From V11.0.0.1, access to the MetaBot Designer in Bot Creator is controlled by the AAE_MetaBot Designer system role. Users with a V10.0.x bot creator device license are automatically assigned this role during migration.

What to do next

You might need to adapt the settings of some of the migrated artifacts in the target environment. In addition, some artifacts cannot be migrated. To continue to use these artifacts, take the following actions in the V11.0 control room:
Devices (bot runners and bot creators)
After migration, the V10.0.x clients do not appear on the V11.0 Devices page. To see the devices on this page, upgrade the clients to V11.0 and then log them into the V11.0 control room.
Version Control Settings
Version control settings aren't migrated. If you used version control in your V10.0.x control room, enable version control manually in V11.0.
Schedules
All migrated schedules are disabled. Edit the schedules in the V11.0 control room to assign a bot runner and then activate the schedules.