- Overview
- Requirements
- Installation
- Prerequisite checks
- Downloading the installation packages
- uipathctl cluster
- uipathctl cluster maintenance
- uipathctl cluster maintenance disable
- uipathctl cluster maintenance enable
- uipathctl cluster maintenance is-enabled
- uipathctl cluster migration
- uipathctl cluster migration export
- uipathctl cluster migration import
- uipathctl cluster migration run
- uipathctl cluster upgrade
- uipathctl config
- uipathctl config add-host-admin
- uipathctl config additional-ca-certificates
- uipathctl config additional-ca-certificates get
- uipathctl config additional-ca-certificates update
- uipathctl config alerts
- uipathctl config alerts add-email
- uipathctl config alerts remove-email
- uipathctl config alerts update-email
- uipathctl config argocd
- uipathctl config argocd ca-certificates
- uipathctl config argocd ca-certificates get
- uipathctl config argocd ca-certificates update
- uipathctl config argocd generate-dex-config
- uipathctl config argocd generate-rbac
- uipathctl config argocd registry
- uipathctl config argocd registry get
- uipathctl config argocd registry update
- uipathctl config enable-basic-auth
- uipathctl config orchestrator
- uipathctl config orchestrator get-config
- uipathctl config orchestrator update-config
- uipathctl config saml-certificates get
- uipathctl config saml-certificates rotate
- uipathctl config saml-certificates update
- uipathctl config tls-certificates
- uipathctl config tls-certificates get
- uipathctl config tls-certificates update
- uipathctl config token-signing-certificates
- uipathctl config token-signing-certificates get
- uipathctl config token-signing-certificates rotate
- uipathctl config token-signing-certificates update
- uipathctl health
- uipathctl health bundle
- uipathctl health check
- uipathctl health diagnose
- uipathctl health test
- uipathctl manifest
- uipathctl manifest apply
- uipathctl manifest diff
- uipathctl manifest get
- uipathctl manifest get-revision
- uipathctl manifest list-applications
- uipathctl manifest list-revisions
- uipathctl manifest render
- uipathctl prereq
- uipathctl prereq create
- uipathctl prereq run
- uipathctl resource
- uipathctl resource report
- uipathctl snapshot
- uipathctl snapshot backup
- uipathctl snapshot backup create
- uipathctl snapshot backup disable
- uipathctl snapshot backup enable
- uipathctl snapshot delete
- uipathctl snapshot list
- uipathctl snapshot restore
- uipathctl snapshot restore create
- uipathctl snapshot restore delete
- uipathctl snapshot restore history
- uipathctl snapshot restore logs
- uipathctl version
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Step 4: Merging organizations in Automation Suite
\
before special characters.
To merge organizations in Automation Suite, run the following command:
./UiPath.OrganizationMigrationApp merge -i '<identity database connection of Automation Suite>' -o '<restored orchestrator DB in Automation Suite connection string>' -s '<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>' -d '<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>'
./UiPath.OrganizationMigrationApp merge -i '<identity database connection of Automation Suite>' -o '<restored orchestrator DB in Automation Suite connection string>' -s '<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>' -d '<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>'
-
Make sure to add
TrustServerCertificate=True
for both the source and destination SQL connections in the input. -
If you have multiple organization pairs to merge, make sure the organization ID sequence for the standalone product and the organization ID sequence for Automation Suite match.
To merge organizations in Automation Suite, run the following command:
./UiPath.OrganizationMigrationApp merge -i "<identity database connection of Automation Suite>" -o "<restored orchestrator DB in Automation Suite connection string>" -s "<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>" -d "<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>"
./UiPath.OrganizationMigrationApp merge -i "<identity database connection of Automation Suite>" -o "<restored orchestrator DB in Automation Suite connection string>" -s "<list of organization IDs of the standalone product separated by comma, e.g. orgID1,orgID2>" -d "<list of organization IDs of Automation Suite separated by comma, e.g. orgID1,orgID2>"
TrustServerCertificate=True
for both source and destination SQL connection strings in the input.
When running the UiPath.OrganizationMigrationApp tool, you must provide the following details:
-
The list of organization IDs for the standalone product
-
The list of organization IDs for Automation Suite
Make sure to use the same organization IDs as the ones identified in Step 1: Moving the Identity organization data from standalone to Automation Suite.
Condition |
Does the source user has an email address? |
Does the target user has an email address? |
Is the source user email the same as the one of the target user? |
Is the source username the same as the target username? |
Result |
1 |
|
|
|
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. |
2 |
|
|
|
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. After the merge, two users have the same username, and they must use the email address to login. |
3 |
|
|
|
or |
The source user is merged with the target user; the target user has access to standalone Orchestrator. |
4 |
|
|
N/A |
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. |
5 |
|
|
N/A |
|
The source user is merged with the target user; the target user has access to standalone Orchestrator. |
6 |
|
|
N/A |
|
The source user is moved to the target organization; the target organization user has access to standalone Orchestrator. |
7 |
|
|
N/A |
|
You must manually configure the email address for the target user or remove the target user. If you configure the email address, the source user is merged with the target user, and the target user has access to standalone Orchestrator. If you remove the target user, the source user is moved to the target organization, and the target organization user has access to standalone Orchestrator. |
8 |
|
|
N/A |
|
The source user is moved to the target organization, and the target organization user has access to standalone Orchestrator. |
9 |
|
|
N/A |
|
You must configure the email address to be empty for the target user or remove the target user. If you configure the email address as empty, the source user is merged with the target user, and the target user has access to standalone Orchestrator. If you remove the target user, the source user is moved to the target organization, and the target organization user has access to standalone Orchestrator. |
If the source and target robot usernames are the same, the source robot user is appended the user ID and is move to the target organization.
Source robot username |
Target robot username |
Moved source robot username |
sameRobot |
sameRobot |
|
If the source and target robot group names are the same, the source robot user is appended a string and is moved to the target organization.
Source group name |
Target group name |
Moved source group username |
sameGroup |
sameGroup |
|
If the organization merge failed, check the logs. Depending on whether the Identity or the Orchestrator migration failed, take the following steps:
If the Identity migration failed, you can just fix the error and execute the organization merge command again. This would rollback all the changes since we have set a transaction for operations for Identity.
If the Orchestrator migration failed, the Orchestrator database would roll back, but the Identity database would not rollback. As a result, you must restore the backup of the Identity database and replace the connection string to use the new database. After fixing the error, run organization merge command again.
If the Orchestrator migration failed, take the following steps:
-
Restore the backup of the Identity database.
-
Right-click the database directory and select Import Data-tier Application.
-
Select the backup database file.
-
Input the backup database name.
-
Wait for the process to complete.
-
-
Replace the identity connection string.
`"platform": { "sql_connection_str": "<dotnet connection string>", (added line) "enabled": true, },`
`"platform": { "sql_connection_str": "<dotnet connection string>", (added line) "enabled": true, },` -
Fix the error and use the new platform connection string to run the merge command again.