Orchestrator is typically licensed through either a host license or an organization-level license, by a system administrator.
However, there are certain functions in Orchestrator that require that administrators or users of Orchestrator understand and work with other types of licenses, which allow the use of various features. These are called service licenses and, of these, of particular interest is the runtime.
This page covers strictly the licensing aspects of interest to Orchestrator administrators and users for using Orchestrator.
To learn more about the various types of licenses, see:
Several permissions are available to allow a user to perform the various license-related actions described on this page:
- License - Edit or License - Create - enables you to activate or update licenses
- License - View - enables the See More buttons on the License page, which allow you to see details about the licensed Robots in their corresponding page. The View Robots button is also available on these pages if you also have the Robots - View permission.
- License - Delete - enables you to remove licenses.
A licensing process most commonly starts with activating your Orchestrator license, as explained here. If you want to manage your licenses at host level, activate your Orchestrator license and allocate them as explained here.
Afterward, all you need to do to activate a Robot license is to connect the Robot to Orchestrator.
- You can activate its license directly from Orchestrator. This is the recommended method.
- You can activate it locally and then connect Studio to Orchestrator through its Robot. Remember to select the Stand-alone license checkbox when creating your Robot, to prevent Orchestrator from allocating Studio a license from its pool of licenses.
There are several ways to monitor license usage from Orchestrator:
- If you want to assess whether there's room for maximizing licensing efficiency, you have the possibility to monitor historical licensing data on the Tenant > Monitoring page, by selecting License from the Section list.
- In the License page, the total number of runtimes available on all online machines is displayed. Remember that a machine consumes the licenses as soon as the Robot Service starts.
To instantly release a license, disable the machine from the corresponding License page. Please note that you cannot use Studio or the Robot on a disabled machine.
How many runtimes to allocate
Although license management is typically performed from the administration interfaces, in Orchestrator you do work with a particular type of license: the runtime, which is a service license for robot use.
Runtimes are the licenses you need to run unattended automations. You allocate runtimes when you create a machine object in Orchestrator. There are two aspects to know when allocating runtimes:
- Number of runtimes: You can assign a custom number of runtimes to a machine object (standard machine, or machine template), which determine the number of processes that can run at the same time on a machine.
The number required runtimes is given by the number of jobs you want to allow to be executed at the same time on this machine; it is not impacted by the number of robots on the machine.
Let's say you have a machine template with 10 Production (Unattended) runtimes allocated to it. For each workstation that is connected using the machine key of that template, 10 Production (Unattended) runtimes are reserved from the available licenses at the tenant level, allowing for executing 10 jobs at the same time. From these reserved runtimes, a runtime is only in use during job execution. So if you connect 4 machines to Orchestrator using that template, you need and reserve 40 runtimes at the tenant level. With, for example, 25 jobs running, 25 out of the 40 reserved runtimes are in use, leaving 15 runtimes that are reserved, but unused.
- Types of runtimes: The types of runtimes that are assigned to a machine object determine the types of processes that can run on that machine.
Runtimes for classic folders
Because for classic folders you can have several Robot entities on the same machine, it is important to understand that more Robots does not mean more execution capacity. For that you need more runtimes.
例如，若为拥有 5 个机器人的计算机分配 3 个运行时，则一共只会占用 3 个许可证。如果执行 5 个作业或调度该计算机上的所有机器人，则会发生以下事件：
- 在前 3 个拥有许可证的机器人上执行 3 个作业；
- 剩余 2 个无许可证的权机器人将处于挂起状态；
- 前 3 个机器人释放许可证；
- the remaining 2 Robots are licensed and they execute the assigned jobs, leaving one license reserved, but not in use.
如果您在一台计算机上只有一个无人值守或非生产机器人，且已为该计算机分配 30 个运行时，则当其处于在线状态时，需使用 30 个许可证。
If a Windows 7 machine has 10 users (Robots), you can only execute one process at a time, and you have to leave the number of runtimes to its default value, 1. If you assign more than 1 runtime to a Windows workstation machine and try to execute multiple jobs at the same time, errors are thrown.
If the UiPath Robot service is running on a given machine, it is displayed as licensed. If there are no more licenses available, the machine is not licensed.
By default, you are notified 180, 90, 30, 14, 7, and 1 day before the license expiry date. You can configure these values using the
SystemJobs.LicenseExpirationAlert.DaysBefore app setting.
At host level, for single licenses distributed across multiple tenants, only the system administrator receives these email alerts. At tenant level, all the active users with License - View permission receive them. The emails are localized per user.
您可以单击“确定”以关闭通知，然后继续照常工作。在规定的宽限期结束后，您的 Orchestrator 将不再获得许可，并且无法再运行。