Déploiement multinœud

If your deployment has grown and you need to increase capacity, expanding your Orchestrator to a multi-node installation is the next logical step. It offers both better performance and failure resistance as multiple Orchestrator nodes are available - when one fails, the other(s) can pick up the load. Horizontal scalability is also available, as it is possible to add additional nodes as your Robot needs grow further. This deployment model should not, however, be confused with High Availability, as the lone HAA node remains as a potential single point of failure.

Remarque :

Remember to take into consideration the Orchestrator hardware requirements corresponding to the scale of your deployment.

Please note that this model is more resource intensive than a single node installation, requiring additional components such as the High Availability add-on for Orchestrator (or other tested solution) and a network load balancer.

Le diagramme ci-dessous décrit un déploiement multinœud simple d'au moins deux nœuds Orchestrator synchronisés à l'aide d'un seul nœud HAA :

Important :

Les déploiements d'Orchestrator multi-nœuds ne sont pris en charge par UiPath que si le module complémentaire UiPath High Availability est utilisé.

Ces déploiements utilisent le protocole RESP (REdis Serialization Protocol) pour la communication et peuvent donc être configurés à l'aide de n'importe quelle solution mettant en œuvre ce protocole. Les solutions potentielles testées (mais non prises en charge) par UiPath sont :

• MSOpenTech Redis sous Windows v3.0.504
• Redis Server v3.2.8 et v5.0.4
• Redis Enterprise v5.4.0-19