- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Step 9: Migrating standalone Test Manager
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).
If you want to run the Test Manager migration script from a machine different then 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:
-
If your standalone Test Manager uses file storage in standalone installation, retrieve the
Storage.Locationkey from theappsettings.production.jsonfile from the standalone Test Manager installation directory.For example, usually the default value of the
Storage.Locationkey isC:\ProgramData\UiPath TestManager\Storage. -
Move the contents of the
Storagedirectory 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>:~/storagescp -r Storage/ <username>@<machine_ip or hostname>:~/storage -
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./testmanager_migrator.sh -s <storage_folder_location> -yThe script uses the
-s <storage_folder_location>parameter to specify the root folder of tenant data for migration. -
To move the attachments to a InCluster Ceph object store, run the Test Manager migration script with the following command:
./testmanager_migrator.sh -s <storage_folder_location> -is -y./testmanager_migrator.sh -s <storage_folder_location> -is -yThe 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.
-
2. Update storage location in database
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:
-
Confirm that all attachments have been successfully migrated to the external storage.
-
In the standalone Test Manager installation directory, search the Test Manager provisioning tool.
You can find this tool packaged with each build as
testmanager.exein 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. -
Execute the following command using the provisioning tool.
testmanager.exe database updateStorageLocation -cs <connection string> -b <destination bucket name>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.