Automation Suite
2023.10
false
Step 4: Merging organizations in Automation Suite - Automation Suite 2023.10
Banner background image
logo
Automation Suite on Linux Installation Guide
Last updated Feb 13, 2024

Step 4: Merging organizations in Automation Suite

For Linux

Note:
Make sure to follow the general escape instructions for the Shell tool of your choice. For instance, in Bash you must add \ before special characters.

To merge organizations in Automation Suite, run the following command:

./UiPath.OrganizationMigrationApp merge -i '<Identity DB connection string>' -o '<Orchestrator DB connection string>' -s '<List of source organizations to merge separated by comma, e.g. orgID1,orgID2>' -d '<List of destination organizations to merge separated by comma, e.g. orgID1,orgID2>' -t '<List of tenant IDs to link Orchestrator, e.g. tenantId1,tenantId2>'./UiPath.OrganizationMigrationApp merge -i '<Identity DB connection string>' -o '<Orchestrator DB connection string>' -s '<List of source organizations to merge separated by comma, e.g. orgID1,orgID2>' -d '<List of destination organizations to merge separated by comma, e.g. orgID1,orgID2>' -t '<List of tenant IDs to link Orchestrator, e.g. tenantId1,tenantId2>'
Note:
Make sure to add TrustServerCertificate=True for both source and destination SQL connections in the input.
Note:
If you have multiple organization pairs to merge, make sure the sequence for source and target orgId, orgId, and tenantId match.

For Windows

To merge organizations in Automation Suite, run the following command:

./UiPath.OrganizationMigrationApp merge -i "<Identity DB connection string>" -o "<Orchestrator DB connection string>" -s "<List of source organizations to merge separated by comma, e.g. orgID1,orgID2>" -d "<List of destination organizations to merge separated by comma, e.g. orgID1,orgID2>" -t "<List of tenant IDs to link Orchestrator, e.g. tenantId1,tenantId2>"./UiPath.OrganizationMigrationApp merge -i "<Identity DB connection string>" -o "<Orchestrator DB connection string>" -s "<List of source organizations to merge separated by comma, e.g. orgID1,orgID2>" -d "<List of destination organizations to merge separated by comma, e.g. orgID1,orgID2>" -t "<List of tenant IDs to link Orchestrator, e.g. tenantId1,tenantId2>"
Note: Make sure to add TrustServerCertificate=True for both source and destination SQL connections in the input.

Migration tool input

When running the UiPath.OrganizationMigrationApp tool, you must provide the following details:

  • Source organizations

  • Tenant IDs

  • Destination organizations

Source organizations

To get a list of source organizations, run the following command on the standalone database and use GlobalId with the related partition (organization) name on the restored database:
SELECT * FROM [identity].[Partitions]SELECT * FROM [identity].[Partitions]

Tenant IDs

To get a list of tenant IDs, run the following command on the AutomationSuite_Platform database on the SQL Sever. You can find the tenant ID in the Id column.
SELECT TOP 10 * FROM [oms].[Tenant] WHERE Name = '*'SELECT TOP 10 * FROM [oms].[Tenant] WHERE Name = '*'

Destination organizations

To get a list of destination organizations, run the following command on the AutomationSuite_Platform database on the SQL Sever. You can find the destination organizations in the OrganizationId column. Make sure to escape special characters in the passwords you provide accordingly.
SELECT * FROM [oms].[Tenant]SELECT * FROM [oms].[Tenant]
Let's assume you created the following two tenants: tenant haonantest1as inside an organization called haonantest1as; and tenant haonantest2as inside an organization called haonantest2as. You must record the two tenant IDs as shown in the following image:
docs image

Merge expectations

Users

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.

Robot users

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

sameRobot_47a26d4a-2180-4fdd-8e1e-2379300a1162

Groups

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

sameGroup_db39a5c6-f73c-4011-b40e-4ea620fe3d01

Settings

If source settings and target settings have the same name, the setting value of the target is used.

If organization merge failed

If the organization merge failed, check the logs. Depending on whether the Identity or the Orchestrator migration failed, take the following steps:

Failed Identity migration

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.

Failed Orchestrator migration

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:

  1. Restore the backup of the Identity database.

    1. Right-click the database directory and select Import Data-tier Application.
      docs image
    2. Select the backup database file.
      docs image
    3. Input the backup database name.
      docs image
    4. Wait for the process to complete.
      docs image
  2. 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, 
    },`
  3. Fix the error and use the new platform connection string to run the merge command again.

Support and Services icon
Get The Help You Need
UiPath Academy icon
Learning RPA - Automation Courses
UiPath Forum icon
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2024 UiPath. All rights reserved.