Skip to main content

UiPath : Orchestrator Basics

UiPath : Orchestrator Basics

By Dinesh Baskaran

1. What is Orchestrator?
2. What is Tenant in Orchestrator?
3. What is Jobs in Orchestrator?
4. What is Robots in Orchestrator?
5. What is Environment in Orchestrator?
6. What is Machines in Orchestrator?
7. What is Processes & Packages in Orchestrator?
8. What is Schedules in Orchestrator?
9. What is Assets in Orchestrator ?
10. What is Queues in Orchestrator ?


1. What is Orchestrator?

It is the managing body with whole control to the System. One Admin can manage everything through Orchestrator. Also we can add roles to control and monitor the system. In UiPath, generally orchestrator handles the Robots, Environment, Processes, Schedules, Assets and Queues.

UiPath Orchestrator is a User Interaction web page that need to be hosted in a webserver(IIS). One should have access to the tenants, then login and manage all the setup. UiPath Admin is the highest role can play with all over setup.

2. What is Tenant in Orchestrator?

 Tenant is the classification of hosting environment. Generally its a divided policy and communicated should be void between the tenants.

Each Tenants should have seperate Machines, Environment, Processes, Packages, Schedules, Assets and Queues. Its only way to connect a Machine with one Orchestrator Tenant at a time.

3. What is Jobs in Orchestrator?

Jobs in Orchestrator are runnable items in UiPath. Here you can trigger a new job or can control the job. 

Can stop or kill the job. Also can see the logs of job in orchestrator. 


4. What is Robots in Orchestrator?

Robots are the Individual machines which are configured and connect with orchestrator. Whenever orchestrator trigger goes to robot it can start the execution. 

Also robot setup need credentials of that machines. So robot can login to the machine and run the jobs as per schedule. 

5. What is Environment in Orchestrator?

Environment are classification of machine where we can track like higher or lower environment. 

So process need to coupled with environment in orchestrator

6. What is Machines in Orchestrator?

Machines are normal device names which we can add through network


7. What is Processes & Packages in Orchestrator?

Processes are the runnable bots which are developed by human. 

Here all coupled with a  environment. 

Package are version management system


8. What is Schedules in Orchestrator?

Schedules are timely trigger plan which need to be created by human. 
Normally schedule having the process, machines, time details to trigger automatically by orchestrator


9. What is Assets in Orchestrator ?

Assets are constant value which are dynamically taken from bot. 

So it will be useful when we need to change constant values without any code change


10. What is Queues in Orchestrator ?

Queues are items which should flown to jobs in a sequential order. 

Main motto of queues to avoid duplicate process when we run from multiple machines

YouTube Video about UiPath Orchestrator:


<iframe width="560" height="315" src="https://youtu.be/i2_KWt3UNyQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>




Comments

Popular posts from this blog

Azure - Web App Bot - Introduction

Hello everybody! Happy to give intro about Azure Web App Bot!!  Recently had some good time to learn and use this in real time requirements. I am sharing the things here to jump start with Azure Web App Bot.  Prerequisite: 1. Azure Subscription Before you got into Web app bot creation, I will give inputs about other terms which will be useful to gain more sounds.  Azure App Service:             This is used as hosting endpoint where you can access from world. All incoming connection will begin from app service. That endpoint it tied with Web app bot for bot service. App service always having different tech flavours for hosting. So while creating app service itself we can use the flavour of code which we used for development.  Web App Bot:               This is a service used as middleware for bot. Simply we can call as connecting medium. After bot development we need to access your bot through emulator in our local. But for other endpoint users we need to connect with channels that are