- Overview
- Requirements
- Recommended: Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 1: Configuring the OCI-compliant registry for offline installations
- Step 2: Configuring the external objectstore
- Step 3: Configuring High Availability Add-on
- Step 4: Configuring Microsoft SQL Server
- Step 5: Configuring the load balancer
- Step 6: Configuring the DNS
- Step 7: Configuring the disks
- Step 8: Configuring kernel and OS level settings
- Step 9: Configuring the node ports
- Step 10: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Step 13: Generating cluster_config.json
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive and Active/Active configurations
- High Availability Add-on configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- Monitoring configuration
- Optional: Configuring the proxy server
- Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster
- Optional: Passing custom resolv.conf
- Optional: Increasing fault tolerance
- install-uipath.sh parameters
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Step 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating objectstore from persistent volume to raw disks
- Migrating from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating to an external OCI-compliant registry
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive or Active/Active deployment
- Guidelines on backing up and restoring an Active/Passive or Active/Active deployment
- Redirecting traffic for the unsupported services to the primary cluster
- Monitoring and alerting
- Migration and upgrade
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Upgrading Automation Suite
- Downloading the installation packages and getting all the files on the first server node
- Retrieving the latest applied configuration from the cluster
- Updating the cluster configuration
- Configuring the OCI-compliant registry for offline installations
- Executing the upgrade
- Performing post-upgrade operations
- Product-specific configuration
- Using the Orchestrator Configurator Tool
- Configuring Orchestrator parameters
- Orchestrator appSettings
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to disable TX checksum offloading
- How to upgrade from Automation Suite 2022.10.10 and 2022.4.11 to 2023.10.2
- How to manually set the ArgoCD log level to Info
- How to expand AI Center storage
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- How to forward application logs to Splunk
- Unable to run an offline installation on RHEL 8.4 OS
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Support bundle log collection failure
- Test Automation SQL connection string is ignored
- Data loss when reinstalling or upgrading Insights following Automation Suite upgrade
- Single-node upgrade fails at the fabric stage
- Cluster unhealthy after automated upgrade from 2021.10
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Volume unable to mount and remains in attach/detach loop state
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Unhealthy Insights component causes the migration to fail
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Docker registry migration stuck in PVC deletion stage
- AI Center provisioning failure after upgrading to 2023.10 or later
- Upgrade fails in offline environments
- SQL validation fails during upgrade
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Longhorn REST API endpoint upgrade/reinstall error
- Upgrade fails due to overridden Insights PVC sizes
- Setting a timeout interval for the management portals
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Update the underlying directory connections
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Missing Ceph-rook metrics from monitoring dashboards
- Pods cannot communicate with FQDN in a proxy environment
- Failure to configure email alerts post upgrade
- Document Understanding not on the left rail of Automation Suite
- Failed status when creating a data labeling session
- Failed status when trying to deploy an ML skill
- Migration job fails in ArgoCD
- Handwriting recognition with intelligent form extractor not working
- Failed ML skill deployment due to token expiry
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- After Disaster Recovery Dapr is not working properly for Process Mining
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Automation Suite certificate is not trusted from the server where CData Sync is running
- Running the diagnostics tool
- Using the Automation Suite support bundle
- Exploring Logs
Automation Suite on Linux installation guide
Migrating standalone products to Automation Suite
For migrating your standalone product data to Automation Suite, you can follow one of the two processes available:
You must choose one process to use, you cannot use both.
This page describes the differences between the two options to help you choose which one to use.
Both processes are for moving your data from the standalone installation of Orchestrator to the Orchestrator service in Automation Suite, but there are some differences.
The full installation migration process essentially links your standalone Orchestrator database to Automation Suite, so all the data it includes is available in Automation Suite. You should use this method if, in addition to Orchestrator, you also want to migrate other products and services.
The full migration option ensures high-fidelity data transfer between the standalone product databases and the automatically created Automation Suite databases. If you do not want to use the default Automation Suite databases, you can opt for your own migrated databases provided that you update their connection strings.
The single tenant migration process, on the other hand, uses the Automation Cloud™ Migration Tool to strictly copy the entities present in your standalone Orchestrator. The tool retrieves them from standalone Orchestrator over API and then writes them in Automation Suite over API.
| Full installation migration |
Single tenant migration | |
|---|---|---|
|
Scope |
|
|
|
Outcome |
Orchestrator in Automation Suite contains exactly the same data and is configured in exactly the same way as your standalone Orchestrator. |
All your entities are copied over to Orchestrator, but Orchestrator in Automation Suite uses the default Automation Suite configuration. To get to the same setup you had in your standalone installation, you must perform a first-time configuration of Automation Suite, which you can do at any time - before or after migration. |
|
Prerequisites |
Requires that you upgrade standalone Orchestrator to a version that matches the targeted Automation Suite version. |
Supports direct migration from any supported standalone Orchestrator version 2019.4. |
|
Organization hierarchy |
You have two options:
|
You can migrate your tenants to the same organization, or to several organizations, as needed. |
Although typically you can only use one migration option or the other, this sample scenario describes a use case where you could use both.
If you intend to perform the full migration, the Automation Cloud Migration Tool can support the migration process by allowing you to more easily set up a test environment in Automation Suite with production data that you can use for end-to-end testing.
If you want to first test Automation Suite and would like to do so on your actual Orchestrator data, here is what the full process might look like:
- Deploy Automation Suite in a test or development environment.
-
Migrate partial data from standalone Orchestrator to Automation Suite using the Cloud Migration Tool. See Single tenant migration for instructions.
This allows you to perform a proof-of-concept or trial on a real dataset. At this point, you have your Orchestrator data, but you are using the default Automation Suite and Orchestrator configurations. You can, for example, readily test run a process, but you cannot readily log in with an SSO account.
- With the partial migration complete, validate critical scenarios and use cases and address any issues.
-
Upgrade the test environment for standalone Orchestrator to the desired version.
Follow the instructions in Updating using the Windows installer and make sure to put the environment in read-only mode.
- Perform a test migration to Automation Suite following the Full migration instructions.
- Redirect all test users and robots to the new Automation Suite test environment.
- Address any issues during and after the migration, validate the process end-to-end.
- Deploy Automation Suite in a production environment.
-
Upgrade you production environment for standalone Orchestrator to the desired version.
Follow the instructions in Updating using the Windows installer and make sure to put the environment in read-only mode.
-
Perform the full production migration to Automation Suite following the Full migration instructions.
Important: This overwrites the previously migrated data, which is lost. With this migration, all your custom configurations are applied, and your Orchestrator entities are also migrated. You should see the same information in Automation Suite as you do in your standalone Orchestrator. - Redirect all production users and robots to the new Automation Suite production environment.
If needed, you can discard tenants from standalone Orchestrator that you no longer need (for example, testing tenants). If you do not create an organization and tenant pair for a tenant from your standalone installation, it is not available in Automation Suite. The data for any discarded tenants is still migrated to the new database, but the tenants are not accessible from the user interface.
