UiPath Orchestrator is a web application that enables you to orchestrate your UiPath Robots in executing repetitive business processes.
Orchestrator lets you manage the creation, monitoring, and deployment of resources in your environment, acting in the same as an integration point with third-party solutions and applications.
Capabilities of UiPath Orchestrator:
- Provisioning : creates and maintains the connection between Robots and web application
- Deployment : assures the correct delivery of the package versions to the assigned Robots for execution
- Configuration : maintains and delivers Robot environments and processes configuration
- Queues : ensures automatic workload distribution across Robots
- Monitoring : keeps track of Robot identification data and maintains user permissions
- Logging : stores and indexes the logs to an SQL database and Elasticsearch (depending on your architecture and configuration)
- Inter-connectivity : acts as the centralized point of communication for 3rd party solutions or applications
RPA UiPath Studio User Interface
The user interface of UiPath Orchestrator has divided into three parts, such as :
The Monitoring menu contains the following options, such as :
- Robots : The global and folder overview of your robots and activity.
- Jobs : Execution instances of processes assigned to robots.
- Queues : Overview of queues and transaction statuses and SLA predictions.
- Logs : Overview of all robot logs.
The Automation menu contains the following options, such as :
- Processes : Folder view of the distribution of package versions to Robot environments
- Triggers : Time or event triggers for job execution
- Queues and Transactions: Work queues used to distribute work items to robots with real-time monitoring of each queue item
- Assets : Shared variables or configurations that can be invoked in the design processes by developers and used in your processes
- Tasks : Human intervention assignments required for long-running process resumption
The Management menu contains the following options, such as :
Machines are nothing but your Computer/Laptop. It is used to add Machines to the orchestrator to connect with robots. There are two types of robots we can create:
- Standard Machines : Standard machines can be used when the name of the machine on which you wanted to define robots remains the same each time you connect to it. 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 the same as your system/Computer name.
- Machine Templates : The Machine Templates are used when the name of the machine on which you want to define robot changes every time as in the case of the Non-Persistent Virtual Desktop infrastructures(VDI). Is allows floating robots to run on any machine linked with the generated access key.
Machine Templates only works for active directory users, Attended Floating Robots and Development Floating Robots.
- Folders: Organizational management and resource allocation
- Users and Roles: Users and permissions management
Robots and Environments:
The robot is an execution host that runs the processes built in UiPath Studio. From the robots page, you can add robots to the orchestrator and connect with created machines.
Two types of Hosting Robots can be created :
The standard robot works only on the standard machine, which is defined when we are creating it. So Once you choose the option to create a standard robot, you have to mention the Machine Name, Robot Name, password, Robot type, and description.
The Floating Robots work on any machine defined in Orchestrator, as the machine name is not relevant when creating it. Only the attended and development robots can be floating.
These types of robots only work with Active Directory users and are useful if the machine you wanted to add a robot to has a different name each time it is spawned, such as for Non-Persistent VDI's.
In the floating scenario, you only need to define one machine templates and Floating Robots. The template persists across your entire VDI such that each of the users can connect to there 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 all not 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.
There are Four types of Robots we can create :
- Attended Robots: It works on the same work station as a human user and is usually triggered by the user through there actions. You cannot start processes from the orchestrator on this type of robot, and they cannot run under the locked screen. It can be started only from the robot Tray. Attended robots should only run under human supervision.
- Unattended Robots: Unattended robots can run in virtual environments and can automate any number of processes. This robot is responsible for remote execution. Monitoring, Providing, Scheduling support for work queues. The Unattended robots can be run under the locked screen.
- Non-Production Robots: It retains all the features of the Unattended robot. But it should be used only for development and testing purposes.
- Development Robots: It has the features of unattended robots, but it should only be used to connect your studio to orchestrator for development purposes.
- Packages and Libraries: Business process definition packages published by developers, and libraries of grouped packages upload for sharing and reuse
- Task Catalogs: Containers used to categorize your tasks based on various criteria
Basics of Automation in UiPath Studio