- Getting Started
- Requirements
- Best Practices
- Installation
- Updating
- Identity Server
- Troubleshooting startup errors
The Windows Installer
UiPathOrchestrator.msi
installer enables you to install Orchestrator on one or multiple nodes, depending on your needs. The following sections provide
you with the details on how to perform a successful installation in both single- and multi-node environments.
- Orchestrator
- Identity Server
- Webhooks
- Resource Catalog Service
In single-node installations, the session is kept in the memory, as you do not need to share it.
Multi-node Orchestrator deployments use the RESP (REdis Serialization Protocol) for communication, and thus can be configured using any solution implementing this protocol.
High availability deployments with multi-node Orchestrator are supported by UiPath only if the UiPath High Availability Add-on is used.
CERTIFICATE_SUBJECT
and IS_CERTIFICATE_SUBJECT
parameters are mandatory. Orchestrator-Identity Server integration does not work if different certifications are used for
Identity. Its value in the parameters file used must be a common one across all nodes. This can be accomplished by using:
- A wildcard certificate (
subject=*.domain.local
); or - A Subject Alternative Name (SAN) certificate containing the DNS name of the public load balancer and optionally the DNS names of all the nodes, either when creating the certificates or by editing the value in the parameters file before proceeding with the secondary node installation(s).
Certificates can be entered by subject or thumbprint.
Where the above methods assume installation and configuration of the primary and secondary nodes during the initial deployment, it is also possible to generate a parameters file from any existing node to be used in the installation of any additional node(s).
Generate-ParametersFile.ps1
script, found in the Tools
subfolder of the Orchestrator installation directory:
The metadata (definition) of all packages - activities, workflows, libraries - is kept in the SQL database for faster search and filtering.
In addition to this, it is possible to keep the actual files and execution media in the FileSystem or a blob storage of your choosing - Azure, Amazon S3, or Minio. This feature allows for a more performant file synchronization, especially in complex multi-node Orchestrator environments.
Take into consideration that, regardless of the storage you use to keep your packages, the maximum file size per upload is 28.6MB - a limitation given by IIS. To see how to change this for Amazon, Minio, FileSystem, and Azure, please visit this page.