automation-suite
2023.4
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Step 5: Updating the migrated product connection strings
OUT OF SUPPORT
Automation Suite on EKS/AKS Installation Guide
Last updated Nov 21, 2024
Step 5: Updating the migrated product connection strings
To download
uipathctl
, see Downloading the installation
packages.
To generate the input.json
configuration file, take one of the following steps:
- Option A: Generate the latest
input.json
file:uipathctl manifest get-revision | Out-File -Encoding ascii input.json
uipathctl manifest get-revision | Out-File -Encoding ascii input.json - Option B: List all the past
input.json
files and determine which one you want to choose:uipathctl manifest list-revisions
uipathctl manifest list-revisions
- Move the
versions.json
file to the same directory asinput.json
. You can getversions.json
from the Automation Suite installation folder. - Provide the new connection strings for the installed products.
-
To provide the restored connection string to the Orchestrator service, add or update
sql_connection_str
underorchestrator
in theinput.json
file:"orchestrator": { "sql_connection_str": "<restored orchesrator connection string>", (added line) "enabled": true }
"orchestrator": { "sql_connection_str": "<restored orchesrator connection string>", (added line) "enabled": true } -
If Test Automation tables are placed inside the standalone Orchestrator database, you can also add the same connection string for Test Automation feature inside the
input.json
file:"orchestrator": { "testautomation": { "enabled": true, "sql_connection_str": "<restored orchestrator connection string>" }, "sql_connection_str": "<restored orchestrator connection string>", (added line) "enabled": true }
"orchestrator": { "testautomation": { "enabled": true, "sql_connection_str": "<restored orchestrator connection string>" }, "sql_connection_str": "<restored orchestrator connection string>", (added line) "enabled": true } - To provide the restored connection string to the Insights service, add or update
sql_connection_str
underinsights
in theinput.json
file."insights": { "sql_connection_str": "<restored connection string>", (added line) "enabled": true }
"insights": { "sql_connection_str": "<restored connection string>", (added line) "enabled": true }
-
- Update the
input.json
file by running the installer.- To migrate Orchestrator only, run the following command:
uipathctl manifest apply input.json --only orchestrator --versions versions.json
uipathctl manifest apply input.json --only orchestrator --versions versions.json - To migrate Insights only, run the following command:
uipathctl manifest apply input.json --only insights --versions versions.json
uipathctl manifest apply input.json --only insights --versions versions.json
Note:If you run the command on Windows, replaceuipathctl
with.\uipathctl.exe
in the command. - To migrate Orchestrator only, run the following command:
- Remap the organization IDs in the Insights tables.
For more details, see Remapping the organization IDs.