DO we need different instances for orchestrator for different environments (Dev,Prod and UAT)

[Tanujasethi]

HI team,

Do we need difference instances of Orchestrator for different environments for eg. Dev, Production and UAT.

Because if we use same instance of Orchestrator then database will be same for all 3 environments and there is security risk involved.

[ovi (Viorela Preda)]

Hi Tanuja,

It is recommended to have one Orchestrator instance for Dev and Test environments and another Orchestrator instance for pre-production(UAT) and Production. If you use the same instance, you’re right, all the data will be in the same database(even if you have different tenants).

[ailas2030 (Avi)]

@ovi Do we need separate license for each instance of Orchestrator?

[ovi (Viorela Preda)]

Please contact the sales team for this: Contact Sales - RPA Business Process Strategy | UiPath

[andrzej.kniola (Andrzej Knioła)]

I’ll challenge this last post - it’s ok that the prices are not public. I get that.
But this is not consistent:

• Do I need separate robot licences for X setup? public info
• Do I need separate licences for Studio for X setup? public info
• Do I need separate licences for Orchestrator instances in a recommended deployment model? Contact sales (??)

There’s a ton of confusion in licensing already. Why add more “mystery” to it?

[ovi (Viorela Preda)]

@andrzej.kniola

Do I need separate licences for Orchestrator instances in a recommended deployment model? Contact sales (??)

Test Environment is not charged(this info i know for sure), but you may need a license for it anyways that should be given for free(I am not sure of this info that’s why i recommended to contact the people who know for sure).

@andrzej.kniola

There’s a ton of confusion in licensing already. Why add more “mystery” to it?

I agree, I just want that the answers I give to be correct. (don’t argue with me, please )

[ailas2030 (Avi)]

Thank you @ovi

[BejoyEdison (Bejoy Edison M)]

I get that it is better to have separate Orchestrator instance is for Dev and Prod.
But i have this doubt regarding deployment, if we had same orchestrator instance we could easily deploy to every environments from orchestrator but in case of 2 orchestrator instance do we need to manually copy the package to the system having UAT/Prod orchestrator instance . What is the recommended way for deploying a package from the Dev Env to Prod Environment

Many Thanks

[fhenry (Flournoy Henry)]

Did you ever get an answer to this? If we have 2 or more Orchestrators; what is the recommended way to deploy from one to the other, while maintaining the version number, etc.?

[Foehl (Felix Oehl)]

@BejoyEdison, @fhenry
There are a couple of other threads on this related topic. Try these:

Testing and Production environment deployment on Studio, Orchestrator, Robot

Hi, I would like to check below I have two environments, testing and production as below. Testing environment: UiStudio x 1, Orchestrator x 1, Unattended Robot x 1, attended robot x 1 Production environment: UiStudio x 1, Orchestrator x 1, Unattended Robot x 1, attended robot x 1 Now I have build a workflow/transcript in testing environment and done the testing. How could I export this workflow/transcript to production environment? Export the workflow/transcript from testing environment st…

Best way to deploy package from Dev to multiple Prod systems when Dev and Prod is connected to separate Orchestrator instance

The recommended way to setup Orchestrator is to have one Orchestrator instance for Dev/Test environments and another Orchestrator instance for (UAT)/Production So how do we upload/deploy a package to UAT/Prod Orchestrator instance from the Dev/Test Orchestrator instance, do we need to manually do it? What is the recommended way for deploying a package from the Dev Env to Prod Environment when we use 2 orchestrator instance as recommended. I am using 18.2 version