The Policy Engine Settings page contains settings related to the policy service of product provisioning. In general, the settings on this page should not be altered unless you know what they do and have discussed it with an AirWatch representative. Altering them could adversely affect your environment.
Enter the minimum number of threads the system keeps alive to service work items from the in-memory queue.
If there are more work items than threads available, then only the number of work items as there are threads available will make contact at once.
As a thread completes the operation for the work item, it will move on to another device.
Enter the maximum number of threads the system spawns to service work items from the in-memory queue.
If there are more work items selected than threads available, then the policy engine will spin up additional threads until it meets this maximum amount. Only the number of devices as there are threads available will contact at once.
As a thread completes the operation for the work item, the system allows it to decay (provided there is no more work in the in-memory queue) down to the minimum threads level.
|Timer Interval||Enter the time between the policy engine searches for work in the queue.|
|Queue Batch Size||The Queue Batch Size is the interval the policy engine picks up work items from the database and claims into the in-memory queue. If set to zero, it attempts to claim everything so in a multiple policy engine scenario, it should be set to a non zero value, like 1000, to avoid starving a policy engine.|