Recommended approach for managing Dev, Test & PROD environments

Help Orchestrator
,
1

Hello: From UiPath learning materials, learnt that tenant creation specific to each business department is ideal. One part I did not understand is that is it recommended to create specific tenant for Dev, Test & PROD environments? if this is not the way, may I know how do you create these environments and tag them to various IT/Business departments?

Thanks
Madhukar

2

Hi Madhukar,

It is recommended to have two separate Orchestrator installations for distinguishing between Development and Production environments. This is to restrict developer permissions during deployment steps and to establish an approval mechanism by not allowing direct deployment of code to Production. For business departments, it is suggested to create separate folders (instead of tenants). This is because, when granting permissions to a department user, instead of providing editing rights for all existing processes/queues, only the permissions for processes/queues etc. within their own folder are defined.

Hope this helps,

All the best,
Kardelen

3

Thanks @kardelencihangir for the quick response. Separate orchestrator instance for each environment…do you mean this is applicable for both on-premises and cloud hosting? Can you help sharing instructions for both models or point me to UiPath documentation to learn more?

Thanks
Madhukar

1 Like
4

Hi Madhukar,

These documents could provide guidance:

How to Organize Modern Folders in UiPath Orchestrator | Community Blog

Orchestrator - Automation Best Practices (uipath.com)

Orchestrator - Organization Modeling in Orchestrator (uipath.com)

Orchestrator - Managing Tenants (uipath.com)

Best Practice/Setup Dev,Test,Prod Orchestrator Small Scale - Help / Orchestrator - UiPath Community Forum

Development, Testing and Production environment preparation - Help / Orchestrator - UiPath Community Forum

Best Regards,
Kardelen

2 Likes
5

@Madhukar_Dongari

check it for reference

6

Thanks @kardelencihangir, @Krishna_Raj.
‘Automation Best Practices’ says this:
Orchestrator offers a multi-tenancy option. By using more than one tenant, users can split a single instance of Orchestrator into multiple deployment environments, each with its own Robots, processes, logs, and so on. All tenants share the same Orchestrator database.

The above paragraph basically implies that One Orchestrator instance can be used by multiple tenants where in each tenant represents a specific env i.e. DEV or TEST or PROD.

I may be wrong but I did not find any documentation or none of your references talk about multiple instances of orchestrator for environment setup.

Am I missing some thing?

Also, I may suggest that UiPath team should do a Learning video or provide documentation very specific to this topic!!

Thanks
Madhukar

1 Like