0% found this document useful (0 votes)
4 views2 pages

Differences between single-node and multi-node

The document outlines the key differences between single-node and multi-node deployments of UiPath Orchestrator, particularly when transitioning to a disaster recovery setup with active-active configuration. Important considerations include configuring network time synchronization, setting specific values in the configuration file, and ensuring consistent credentials and connection strings across all nodes. Additionally, it emphasizes the need for centralized logging and uniform NuGet package keys across the Orchestrator nodes.

Uploaded by

suckinthedark
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views2 pages

Differences between single-node and multi-node

The document outlines the key differences between single-node and multi-node deployments of UiPath Orchestrator, particularly when transitioning to a disaster recovery setup with active-active configuration. Important considerations include configuring network time synchronization, setting specific values in the configuration file, and ensuring consistent credentials and connection strings across all nodes. Additionally, it emphasizes the need for centralized logging and uniform NuGet package keys across the Orchestrator nodes.

Uploaded by

suckinthedark
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Differences

between single-
node and multi-
node
What are the differences between both options?
When you start the fresh Orchestrator installation, you don't have to worry about what is different in
UiPath.Orchestrator.dll.config file between single-node and disaster recovery with active-active configuration.
The installer does everything for you. But, when you switch from a single-node deployment to a disaster
recovery with active-active deployment, besides adding a load balancer, you have to consider the following
changes. Configure the network time to synchronize all the HAA VMs with the same Network Time servers.

• Set quartz.jobStore.clustered value="true".You cannot reset these credentials, so do not lose them.

• NuGet packages can't be stored locally, in a subfolder of Orchestrator's main folder. Exception is when
Orchestrator is installed in Azure Cloud as PaaS and scaled out to multiple instances.HAA will work only for 30
days without a license.

• Set LoadBalancer.UseRedis value="true".

• A connection string that enables you to setup your Redis server, which contains the URL of the server, the
password, and the port used with Redis. All the HAA cluster nodes should be added in the connection string.
By default, the Orchestrator will communicate with the HAA cluster using port 10000.

<add key="LoadBalancer.Redis.ConnectionString"
value="10.10.20.184:10000,10.10.24.148:10000,10.10.22.114:10000,password=1234
5678" />

• EncryptionKey should be the same for all Orchestrator nodes.

• Store the logs generated by all the Orchestrator nodes in a common place, recommended is
serverElasticBuffer.

<logger name="*" minlevel="Info" writeTo="serverElasticBuffer" />

• Keys (ApiKey, Path, Repositoty Type, Storage Type, Storage Location) related to NuGet packages should be
the same for all Orchestrator nodes.

UIPATH ORCHESTRATOR INSTALLATION AND TROUBLESHOOTING 2

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy