General

Use this tab to define the CRE license distribution and a threshold RoboServer version.

Both License and Threshold version options are disabled if KCU licensing is used.

License Distribution

Select the CRE license distribution mode.

Option	Description
Static	In this mode, CREs are distributed evenly between online RoboServers in the cluster. A CRE is an integral unit, and you cannot split one CRE among multiple RoboServers. For example, if you have six CREs but five RoboServers in a cluster, each RoboServer gets one CRE; therefore, one CRE remains unused. The number of CREs in a cluster must be equal to or bigger than that of RoboServers. If you assign fewer CREs to a cluster than the number of RoboServers present in the cluster, the cluster is disabled. To adjust the number of CREs, in the Action column for the cluster, from the context menu for a cluster, click Assign CRE. This action opens the Assign license units pane where you can adjust the number of license units and see how many units are available in total and how many remain.
Dynamic	In this mode, RoboServers receive the licenses from the cluster per request. A RoboServer can get as many licenses as it requests if they are available. In this mode, RoboServers communicate only with the Management Console and block other requests, such as API calls. If you encounter any problems establishing the connection between a RoboServer and a Management Console, switch server logging to DEBUG level and check the logs. See Logging for details. Dynamic license distribution mode is supported by Kofax RPA version 10.2 and later. Version 10.7 and later support this mode immediately after installation. To use dynamic license distribution, in versions 10.2 to 10.6, install the latest fix pack for the corresponding version. See Enable Dynamic License Distribution Mode in the Kofax RPA Upgrade Guide. In the Dynamic license distribution mode, if you want to reestablish the connection between a RoboServer and a Management Console after the Management Console is restarted, restart the RoboServer.

Option

Description

Static

In this mode, CREs are distributed evenly between online RoboServers in the cluster. A CRE is an integral unit, and you cannot split one CRE among multiple RoboServers. For example, if you have six CREs but five RoboServers in a cluster, each RoboServer gets one CRE; therefore, one CRE remains unused.

The number of CREs in a cluster must be equal to or bigger than that of RoboServers. If you assign fewer CREs to a cluster than the number of RoboServers present in the cluster, the cluster is disabled.

To adjust the number of CREs, in the Action column for the cluster, from the context menu for a cluster, click Assign CRE. This action opens the Assign license units pane where you can adjust the number of license units and see how many units are available in total and how many remain.

Dynamic

In this mode, RoboServers receive the licenses from the cluster per request. A RoboServer can get as many licenses as it requests if they are available. In this mode, RoboServers communicate only with the Management Console and block other requests, such as API calls. If you encounter any problems establishing the connection between a RoboServer and a Management Console, switch server logging to DEBUG level and check the logs. See Logging for details.

Dynamic license distribution mode is supported by Kofax RPA version 10.2 and later. Version 10.7 and later support this mode immediately after installation. To use dynamic license distribution, in versions 10.2 to 10.6, install the latest fix pack for the corresponding version. See Enable Dynamic License Distribution Mode in the Kofax RPA Upgrade Guide.

In the Dynamic license distribution mode, if you want to reestablish the connection between a RoboServer and a Management Console after the Management Console is restarted, restart the RoboServer.

Threshold RoboServer version

Defines the Kofax RPA version number, after which legacy robots should not be upgraded beyond. Helps perform a smooth upgrade of robots and block robots from running on a RoboServer they have not been tested on.

Robots with the product version below the threshold value are forwarded to the nearest newer version of a RoboServer. All the robots above the threshold value are distributed between RoboServers in accordance with strict version matching. That is, a robot with a product version higher than the threshold value can only be run on the RoboServer of the same product version.

For example, if a threshold value is set to 10.2.0.0, distribution of several random robots between several random RoboServers uploaded to the cluster looks similar to the following pattern:

	10.2.0.0 RoboServer	10.3.0.0 RoboServer	10.5.0.0 RoboServer	10.7.0.0 RoboServer
9.7.0.0 robot	Matching	-	-	-
10.1.0.0 robot	Matching	-	-	-
10.3.0.0 robot	-	Strict version matching	-	-
10.4.0.0 robot	-	-	-	-
10.7.0.4 robot	-	-	-	-

All robots with product versions below the threshold value are successfully matched with a RoboServer of the equal or higher version.

The 10.3.0.0 robot has a strict version matching as its product version is above the threshold value and it has a RoboServer of the same version in the cluster.

The 10.4.0.0 robot has no matching and cannot be run as its product version is above the threshold value and no RoboServer of the same version in the cluster is available.

The 10.7.0.4 robot has no matching and cannot be run as its product version is above the threshold value and no RoboServer of the same version in the cluster is available.

By default, threshold value is set to the current Management Console version.

If you upgrade to a newer version of Kofax RPA using a backup, the RoboServer threshold version is not updated automatically. To ensure the robots can run, navigate to Cluster settings > General > Threshold version and manually specify the RoboServer threshold version.

If you want to run older robots that use KCU licensing in a newer RoboServer (for example, you want to add a 10.3.2.2 RoboServer to a Management Console 11.2 environment), create a new cluster and place the older RoboServer node into that cluster. See Create New Cluster in RoboServers.