General
Use this view to define CRE license distribution and threshold RoboServer version.
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. Note 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, click Assign CRE. |
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. |
Threshold RoboServer version
Defines the Kofax RPA version number, after which legacy robots should not be upgraded beyond. Helps to perform a fluid upgrade of robots and to block robots from running on a RoboServer they have not been tested on.
Robots with 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 product version higher than threshold value should only be run on the RoboServer of the same product version.
For example, if a threshold value is set to 10.2, distribution of several random robots between several random RoboServers uploaded to the cluster looks like the following:
10.2.0 RoboServer | 10.3.0 RoboServer | 10.5.0 RoboServer | |
9.7.0 Robot | Matching | - | - |
10.1.0 Robot | Matching | - | - |
10.3.0 Robot | - | Strict version matching | - |
10.4.0 Robot | - | - | - |
All the robots, which product versions are below the threshold value, are successfully matched with a RoboServer of the equal or higher version.
The 10.3.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 robot has no matching and cannot be run, as its product version is above the threshold value and there is no RoboServer of the same version in the cluster.
By default, threshold value is set to the current Management Console version. See Create a Cluster in the RoboServers topic for more information about RoboServer version matching.