Hi friends, this is Manish Pandey. Welcome back. Today we are going to learn about UiPath Orchestrator complete tutorial. Let's see what is our agenda.
So we learned how to monitor robots, jobs and queues. How to create and manage machines. What is a standard machine and machine template. How to find machine name of your system. How to find the UiPath robot if not in the tray.
What is VDI and non-persistent VDI. How to create and manage robots. What is a standard robot and floating robot? What is attendant, non-attendant, non-production and development robots?
How to find domain username? How to create and manage environments? How to deploy process?
How to publish project to the orchestrator? How to upload a package to orchestrator? How to find the published project? package location, how to manage the package version, how to start a job and how to stop or kill the jobs.
So these are the agenda. We are going to learn these things. So let's start how to monitor robots jobs and queues.
so first that is monitoring so once we'll login into the orchestrator here we'll get list of menus here like monitoring robots machines process all these things so first here are getting monitoring. Orchestrator provides the monitoring features which gives you a real-time metrics to help you keep an eye on the health and the state of your robots, queues or jobs. There are three options to choose from the monitoring page first robots second queues and third jobs like the robots from the monitoring you are getting the the runtime overview the robot status so we are getting the you can see that the dashboard type we are able to monitor the our robots the health and the state of the robots like here we are getting one unresponsive one unused it means they are one robot that is unused and one there is one robot which is unresponsive. From here we can get the robot details like how many robots we have created in the orchestrator.
Now here it's showing the robot overview. It shows that we have only one standard robot that is unresponsive. Once we click on here we'll get the details of standard robots that is the start, job start time, error fields. If there is an error showing for the robots it will show here.
Currently there is no error. error found this is the overview of robots so from here we can select like the for the queues if you have any queues that will show here we can select the jobs so currently showing we have three jobs first right to notepad second project to orchestrator and third is demo process we can click here and we can see the overview of the each process so here we are getting all these details now we can go back from here we can select the next one the three jobs which was stopped it shows the interval of one day you can select one hour one day from here now what is machines you can see here the next one is machines because we need to create the machines here without creating machine we cannot create robot let me first delete the existing machines here and delete the machine finally cannot be deleted because it it has the robots attached to it it means you cannot delete the machines if it has any robots attached to the machines so first we'll go to the delete the robots here select the robot and delete that And then we can delete the machine here select this and Remove this from here Now I'm going to remove the process also currently we have the three process installed here. I'm going to remove all these things now I'm going to remove the environments So first we need to create a machine here.
So machine is nothing but your computer or laptop. It is used to add machines to the orchestrator to connect with the robots. So if you want to connect the robots with the machine on the orchestrator then first we need to create a machine we cannot directly create a robot because while creating a robots we require to select the existing machine that's why we cannot create robots at a first time So let's first create the machines here.
If we go to click on machine page here. Here we are getting the add button. Once we click on here we are getting two types of machines. First machine template and second standard machine.
Let me show you here. So there are two type of machines can be created. First standard machine and second machine templates. It should be used when the name of the machine on which you want to define robots remains the same each time you connect to it the standard scenario.
You define the machine once and then can connect to any number of robots in the robots page. The name of the standard machine must be same as your computer name. So let me show you here. Once we'll click here, we are getting machine template and the standard machine.
Create a standard machine. So here the name should be the same as your computer name so the question is how to find the machine name so first in the uipath robot tray on the orchestra setting window we can find the machine name like this you can go to the robot and you can click on orchestra setting and you can find the machine name here we are not getting uipath robot tray how to find the uipath robot if not in train so you can open this location c drive users and the username app data local ui path so for that we'll open the folder c drive users slash responde slash app data slash local slash ui path so we can open the this location and then here we are getting uipath agents so uipath agent is called our uipath robot so we can click here so once we click here it will open the ui path robot here. Now you can see this is the UiPath robot. Now we can see the name of the machine from there. Click here and then click on the settings and then click orchestra setting.
Here we are getting the machine names. We can copy this and we can enter here and then click on provision. so once we'll click here the machine will be created now you can see here if we click on view we will be getting the machine keys and the machine name and from here you can view logs of the machine from here currently we don't have you can download the logs here you can see the associated robots here you can filter out once we click on machine we are getting the options to filter like standard machine or template machine.
Let's suppose we have lots of machines available in the machine page then we can click here and we can select the machines that we need to filter. So we have selected the standard so it will show only a standard machine. The second we can right click on this PC and click on properties from the pop up. This is same as open control panel. Click on system and security.
and the click on system. So we can get the name of the system, machine name from here. And the third, we can open the command prompt and type host name and then press enter.
So we'll get the machine name from here. Let me show you. You can type the command prompt and you just have to write here host name. So we are getting this.
Here is the machine name. Now the another one, we can go to the the folder here click on this PC and right click and click on properties so we'll be getting the computer name that is called pandey so here this is the system name that is machine name so by this way we can find the machine name machine template so how can we create machine template and what is the machine template it should be used when the name of the machine on which you want to define robots changes every time as in the case of non-persistent virtual desktop infrastructures that is VDI it allows floating robots to run on any machine linked with the generated access key so machine template only work for active users attended floating robots and development floating robots so here once we'll click on add we are getting the machine template here click here now machine template can be the any name so let me type the machine template name only and click on provision so now we have the two machines has been created here first a standard machine and second template machine now we will be asking What is VDI and Non Persistent VDI? So, Virtual Desktop Infrastructure or VDI refers to the process of running a user desktop inside a virtual machine.
It enables fully personalized desktop for each user. For example, Citrix. Now what is non persistent VDI?
Non persistent VDI does not save any of the short code files, settings and other changes that user may make. In the other words, you can say it creates a kind of generic desktop that always reverse to the same original setup after user logs out. Once the session is over, those things are gone is also called shared or many to one.
Once we have created the machine, we need to create a robot here. So we will learn what is robot and how to create the robots. So a robot is an execution host that runs process built in UiPath Studio.
So from the robot page you can add robots to the orchestrator, connect with the created machines. Robots are the users working on a machines. Two hosting types of robots can be created.
First standard robots and second floating robots. So, what is a standard robots? It works on a standard machine only which is defined when creating it. We can create the standard robots here. So, once you choose the options to create a standard robot, you have to mention the machine name.
Like here we are getting, let me show you a standard machine how to create that. So once we click on add button, here we are getting to create a standard robot and here we are getting floating robot. So we will click on standard robot.
So now we need to select the existing machine name. So we have already created the machine that is pandey. So here you have seen we have created two machines. for the standard and second machine templates.
So here we have taken the standard robots. So it shows the standard robots allow it to work on single standard machine only. So we can select only standard machine only here.
the robot name. So, you can provide any name like if you are going to run for the testing robot and now you need to enter the domain name. So, how to find the domain name?
it can be found under open command prompt and type who am i and press enter so we can open the command prompt and we need to type who am i so we'll be getting the name that is pandey is less manis pandey so this is our domain username we can copy from here and we can type to the this page and now we need to provide the password if you have the password in our system then we need to enter the password or if you don't have any password to login to into our system then no need to provide so currently I have the password so I'm going to put the password here Now here we have the four types of robots that is development attended unattended robots. So I am going to take development and then create. Here we can put the description like this is for development. Purpose and we can create here if you want to create one more than we can select here and We can check and we can create one more Robots now we'll create here So by this way we can create the robots now here.
We are getting the status is Disconnected the type is development the username is pandas less money's one day and the machine name is Pandian and the robot name is testing Robots Now there are four types of robots first is attended robots So what is attended robots it works on the same workstation as human user and is usually triggered by the user through Their actions you cannot start process from the orchestrator on this type of robots and they cannot run under locked screen It can be started only from the robot tray. Attended robots should only run under human supervision. Now what is unattended robots? It runs unattended in virtual environments and can automate any number of processes.
This robot is responsible for remote execution, monitoring, scheduling and providing support. for your work queues. It can be run under a locked screen.
Now the third is non production robot. It retains all the features of the unattended robots but it should be used only for development and testing purpose. Now the last is development robots. It has the features of an unattended robots but it should only be used to connect your studio to orchestrator for development purpose. Currently it is disconnected.
We can connect. We have to open the UiPath robot and we need to go to the machine that we have created. So we are going to run the standard robot. So we'll click on the standard machine click on view and here we are are getting the machine key so copy that and open the orchestra settings and here from the orchestrator URL we need to paste or we already have the platform that UiPath.com in our orchestrator URL so we can select this or you can copy the name from the here and we can paste here and this is our previous used machine key so we can paste here and now we can connect here so once we'll connect here our robots will here as a available currently it is disconnected because we have not connected here so we are connecting here so once we'll connect here we'll get the status as a connected licensed so after some time just refresh this and we are getting the status is available and here we are getting the green color floating robots so it works on any machine a standard or template defined in orchestrator as the machine name is not relevant when creating it.
Only attended and development robots can be floating. These types of robots only work with Active Directory users and are useful if the machine you want to add the machine name. the add a robot to has a different name each time it is spawned.
Such as for non persistent VDIs same goes for hot seat environment where different people are working in shifts or on the same computer. In the floating scenario, you only need to define one machine template and floating robots one for each user. The template persist across your entire video is such that each of the users can connect to their robots using one key, the machine template key. Essentially, it is a floating licensing. which is often used when you have a large pool of users but they are not all working at the same time.
So instead you can choose a floating license in order to minimize the number that you need to support the number of users. we require the floating license if you are going to use the floating robots then we need floating license same as the unattended license so I'm going to show you how to create the floating robots so once I click here and I'm going to type you're floating and here we can paste the same name that is our computer name that is cmd who am i this is our the domain name we can paste here and the password we can provide here our system password and now you have seen here we have only attended and development robots because we can only create a attended or development robot for the floating robots so I'm going to select the development and we can write the description if we have this is floating robot now create this so now we have created the floating robots currently it is showing disconnected if you want to connect this then what will happen let me first disconnect disconnect this and go to the machines here and click on the machine templates click on edit copy the machine key cancel and select the orchestrator url and paste the machine key of the machine template. Now connect here. So once we connect So it will show here in the status that is unlicensed Because we don't have the license of the floating robots. So that's why we will not able to Work on the floating robots here.
Let me show you here now. We will go to the robots page It's showing this is disconnected because we don't have the license of the Floating robot so we'll disconnect here first so once we have created the robots we need to create the environments here so I'm going to tell you one more things from from robots page you can filter out we have the lots of things we can search the robots name from here directly so we are searching here floating so it will show only floating robots From here we can select the machine name. So based on machine name we can find the robots.
So let's suppose I'm going to find the machine template. So it will show only one. So currently it is not showing because the machine name is not assigned with the floating robots.
Here we can find the based on the username. We have the hosting type, environments, status. available, busy, disconnected, undisponsive and environment is a grouping of robots that is used to deploy process. From environment page you can create and manage environments.
If you have multiple robots on the same machine it is recommended. that you group them in the same environment otherwise some errors might occur when deploying different version of the same process you cannot delete environments if they have at least one robot attached to them or if they have a process or scheduled associated so by this way we can create the environment and we can manage their environments here it means we can associate the robots to the end environments so environments is something like if you are working on any company like you are working for the TCS we pro IBM so you can give the name of the environments here same name like click here and you can right here IBM project so it will show like you are working for the IBM project IBM company so you can create the environment of IBM project and you can Assign all these robots to this environment all these robots for the IBM project so if you need to attach or Configure only one robot to the IBM then you can just select only one and then click update So now we have the created environments. We have created the robots and machines Now we discuss about the process. So a process represents the association between a package and an environment.
Each time a package is linked to an environment it becomes available for all the robot machines that belong to that environment. From process page you can deploy an uploaded package to robot environments, manage previously created associations and keep all your process up to date. This helps you distribute packages on the robot.
robot machines and execute process faster from the job page. So here we are getting two menu one for the process and second package. So I'm going to add process here.
So we are getting the package name. So if we have the existing package we can select from here and we can select the version name. So here I'm going to select the project to orchestrator and select the latest version.
or if you want to select the old then you can select this and then here you need to select the environment it means we have the one robot attached to the this environment now we can create here so now this is showing that this is available so we have created one process here if you want to create more than one then you can also create your click on add you can select the next one you can select the version and then create here so by this way we can create multiple process here how to deploy process so select a package from the package name select the package version and select the environment to deploy the process you can select like this so if package is not available while deploying the process then open ui path studio and publish the project it will automatically add it to the process if you are going to deploy the process and you are not getting any package name here then how can you select the package from here So, for that you have to go to the UiPath Studio. We have the project here that is project testing and we can click on the publish. So it will directly upload it to the orchestrator. So we will click on publish.
And here it is showing the robot. defaults custom and then we can click on publish so once we click on publish it so the project published successfully the project name is this the version is 1.0.1 and the location is this now let's see here if we click create here i'm going to check so currently we are not getting here so if you are not getting the package name here let me first refresh this and click on add and let's see we are getting here or not so we are not getting here because at the time of publishing the project it was showing the location of the package but if you want to directly deploy the process or publish the process to the orchestrator then first we need to connect to the UiPath robot so for that we need the machine name will copy the machine name from here and then we'll open the orchestrator the robot orchestration select the the URL and then connect to this okay so now we have connected here the status showing connected now close this let's see the robot's status now this is connected and now if we click on publish page so here we are getting the orchestrator here publish to orchestrator previously it was showing the robots now orchestrator and then publish again so this time the version will be changed 1.02 and now this has been published there is no location showing here so now if we go to the the process page and click here we will be getting our the new process here that is project project testing and we can select this select the version and select the environments if you have multiple we will be getting here multiple list of the environments we can select this and we can create this and if it is still not there then we can click on the packages and we can upload the package from here browse click on the browse and we can search for the location C Drive and then program data then UI path and then packages so this is the location of the packages so we will open this location and then we will be getting all this published packages so this one is our package we can select that and we can click open and then click upload it so by this way we can upload the package from here manually if you don't have we're not getting here so now we have added the process how to publish project to the orchestrator. Robots should be connected during the publishing the project to orchestrator otherwise you may get an error or it will not be uploaded to orchestrator.
So as you have seen practically you have to click on the publish and then select the orchestrator then click on publish so once we'll click on publish we will be getting the version name and the successful message. Now how to upload a package to the orchestrator if you are not getting package in the orchestrator then go to the package packages page and upload a package to the orchestrator by this way that I already told you practically. Now what is the package location? So packages can be found from the below location that is c drive slash program data slash ui path slash packages.
So, you will be getting all these packages from here. The version management. From here, let's suppose here I have created a project and now if I am going to make some changes here and I am writing here project published. So if I am doing any changes in the project and we required to update the process then we can again click on publish and Click on publish so this time the latest version it was 1.0. 1 3 will be uploaded to the Orchestrator and now from here We will be getting the latest version of the project testing so here we are getting that updates are available we can download this you can click here go to the view process so now we are getting here the version that is 1.0.1.3 that is a minute ago we have published this we have not used this so we can and download this we can update this so are you sure you want to update the project testing ibm project to the version 1.0.3 so yes so once we'll update update this so this the latest version will be used next time and now we can click on close so here we are getting the rollback and latest option let's suppose if you want to roll back this one if you need only this one then we can roll back here so what will happen the last use process will be again that will be rolled back right So now our current process is 1.0.2 version.
Now again if you want to use the latest one then we can click the latest. So next time our current process will be 1.0.3. Here we are getting the current and this time we will be using the current one. Now close this.
We have updated that current version. So when a published studio project is edited and then republished, a new version of the package becomes available. So robots still execute the previous version unless the package is updated manually.
To update it, perform the steps below so we have the two options either we can update from the version management or we can update from the UI path robots directly let me show you from here so we are getting the the updates here we can click on the project testing and we can install the project here now we have the installed and we can install this one also or we can leave it if you want to use the current one then we can leave it and we can use the with the current or if you want to use the latest then you can update this and we can use that start a new job to initiate the execution of the package to end the execution of the process either the stop or the kill button can be used. So the stop command is executed when the automation project reaches the should stop activity in the studio and the kill command ends the process at the moment regardless of the activity that is being executed. So we have the two command that is stop and kill.
So here I am going to use the jobs. Once we click on the start select the let's suppose I am going to select the project testing. There is only one robot showing here we can select this. and we can start this once we click on start our process will be started UI path robot will start executing the process so let's click on start the command has been sent so let's see what is happening so now we have seen the process has been executed it is showing hello ui path and if you want to let's suppose i'm going to select the next one that is project to orchestrator then select the robots click click on start the command has been sent so here we are getting the running state if you want to stop then we can select this we can stop from there or we can kill from there so currently the process has been started it is showing please enter the current running company name let's suppose i am putting here vipro hi vipro welcome to the ui path orchestrator so currently it's showing running because i have not clicked on the message box So, once we click on this will show as a successful. Let me refresh this.
It is showing successful and let me tell you how to stop or kill the process. Select the write to notepad. Select the robots. Click start.
And now refresh this. so we have already done the process this has completed let me run the next one that is project to orchestrator select the robot and start the robots the command has been sent now refresh this and here we are getting the running now you can select this or we can kill from there or we can stop the jobs so once we will stop the jobs our job will be stopped let me refresh this this is stopping now let me if i will type anything here it is working and we can select that and we can kill from here now i have killed here ok so once we click kill the process we can kill the job this will terminate the process now we're getting the stopped so as i told you the kill commands ends the process at that moment regardless of the activity that is being executed it's like we have already executed our process and the input dialog box was showing so we'll we use the kill command so that's why it has killed ends the process now thank you so much friends thank you for watching this video i hope you like my video if you have any question please write in the video comment sections please press the like button thank you so much