Development, Testing and Production environment preparation

Hello All,
Need your support as we recently have UIPath product and i am asking about best practice to create Development, Testing and Production environment according to below criteria we have 2 studio users and 1 basic orchestrator and one unattended robot on the other hand also we have 1 test robot and 1 test orechestrator.

Hello @mahmoud.zaky!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

Hello!

I am not sure exactly what it is you’d like to know. I’ve attached below a few links to Best Practices that might help.

Automation

Security
https://docs.uipath.com/orchestrator/docs/security-best-practices

Performance
https://docs.uipath.com/installation-and-upgrade/docs/performance-best-practices#ui-configuration-changes-for-improved-performance

Also here is the link to our Orchestrator Installation documentation. There is a lot of information but this should proved fairly detailed steps to install and set your Orchestrator environments.

Now for some high level advice. A common practice is to set up 3 environment.
This allows for 1 Production environment where your actual data and systems will be interacted with.
You should also set up a UAT environment, that closely mirrors the Prod environment but does not actually interact with production data or systems.
Then your third environment is your Dev environment where the first processes will be built and tested.

The general flow is to build in dev. This is the Orchestrator environment where the Developers will be connected to. They will build and test here and when their automations are ‘ready’ they will get published to Orch. When these are ready to go through User Acceptance Testing they go to the UAT environment through a manual package transfer, or a CI/CD pipeline like Jenkins or Azure DevOps.

In UAT the same process can be tested in an environment that effectively mimics prod. One they work here it should be ready to go to production.

This is the general flow but there are ways to do this. Many people combine UAT and Dev into one non prod Environment and use two separate tenants for this. This means you’d only need two separate servers for Orchestrator. 1 for Prod, and 1 for both UAT and Dev.

It’s even possible but not best practice to have all three on one Orch by using three different tenants.

I hope this helps.

2 Likes

thanks for your reply :slight_smile:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.