Step 8: Migrating standalone Test Manager

Migrate standalone Test Manager to Automation Suite on EKS/AKS, including moving attachments to the configured storage.

To successfully migrate standalone Test Manager to Automation Suite, you need to follow these steps:

1. Migrate Test Manager storage

When you installed Automation Suite, you also configured a desired storage option. You must move all Test Manager attachments to this destination storage used by your Automation Suite instance.

To move all Test Manager attachments, you should use the Test Manager migration script (testmanager_migrator.sh).

Note:

If you want to run the Test Manager migration script from a machine different than the one originally holding the attachments, move all attachments to that different machine first.

To move your Test Manager attachments to Automation Suite, follow these steps:

1. If your standalone Test Manager uses file storage in standalone installation, retrieve the Storage.Location key from the appsettings.production.json file from the standalone Test Manager installation directory.

   For example, usually the default value of the Storage.Location key is C:\ProgramData\UiPath TestManager\Storage.

2. Move the contents of the Storage directory to the machine where you intend to run the Test Manager migration script.

   You can use the following command to copy the storage content:

   scp -r Storage/ <username>@<machine_ip or hostname>:~/storage
   

3. Run the Test Manager migration script to move your Test Manager storage attachments either to an external object store or to an InCluster Ceph object store:

   • To move the attachments to an external object store, run the Test Manager migration script with the following command:

     ./testmanager_migrator.sh -s <storage_folder_location> -y
     

     The script uses the -s <storage_folder_location> parameter to specify the root folder of tenant data for migration.

   • To move the attachments to an InCluster Ceph object store, run the Test Manager migration script with the following command:

     ./testmanager_migrator.sh -s <storage_folder_location> -is -y
     

     The script uses the -s <storage_folder_location> parameter to specify the root folder of tenant data for migration.

     Note:

     We do not recommend moving your Test Manager attachments in the InCluster Ceph due to its dependency on the cluster's state, and the limited scalability.

Result: Your Test Manager attachments are available in the destination storage used by your Automation Suite instance.

2. Update storage location in database

Note:

This step applies only if you moved your Test Manager attachments to an external object store used by your Automation Suite instance.

Follow these steps to update the folder hierarchy and bucket information in the database after migrating attachments to external storage:

1. Confirm that all attachments have been successfully migrated to the external storage.

2. In the standalone Test Manager installation directory, search the Test Manager provisioning tool.

   You can find this tool packaged with each build as testmanager.exe in the default installation location, as follows: C:\Program Files (x86)\UiPath\TestManager\Tools\TestManagerProvisioner. Alternatively, you can find the executable in your custom installation folder. For more information on the Test Manager provisioning tool, visit Test Manager provisioning tool.

3. Execute the following command using the provisioning tool.

   testmanager.exe database updateStorageLocation -cs <connection string> -b <destination bucket name>
   

   Replace <connection string> and <destination bucket> with the appropriate values for your environment:

   • <connection string>: Enter the connection string for the target Automation Suite instance.
   • <destination bucket>: Specify the name of the destination storage bucket in the object store.

Result: The database folder hierarchy and bucket information are updated to point to the migrated attachment storage.