automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Saving the connection strings
- Step 2: Creating your organizations in 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: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Cluster administration
- Product-specific configuration
- Troubleshooting
Step 1: Saving the connection strings

Automation Suite on OpenShift installation guide
Last updated May 16, 2025
Step 1: Saving the connection strings
Save the following information for further usage:
- The connection string for the Orchestrator database in the standalone deployment;
-
The connection string for the Insights database in the standalone deployment;
- The connection string for the
AutomationSuite_Platform
database in the Automation Suite deployment. You can retrieve the connection string from the
file, under theinput.json
platform
parameter.