JDA Allocation Administration - Auto-Server: Target Number of Processes showing 19 Auto-Allocation Server/jobs only although Target Number of Jobs/Core is set to a higher figure.

In case 19 concurrent auto-allocation instances are not utilizing the available physical CPU/cores (but it is desired to do so), the following options can be explored.
 

• Split the Hardware over several virtual machines and run Auto-Allocation Server on each virtual machine. (many on the physical machine)

• Run multiple instances of Auto-Allocation (without using Auto-Allocation Server).

• Run one Auto-Allocation Server on the physical machine and additional, individual Auto-Allocation instances (not managed by the Auto-Allocation Server). I.e. run both; Auto-Allocation Server (Chapter 15) & Auto-Allocation (Chapter 27) on the same physical machine in order to utilize all available CPU resources.

Customer specific testing will be needed to establish the needed count of auto-allocation instances needed and will be a function of e.g.:
# cpu's, # jobs, nature of jobs (Worklist Lines, Worklist shapes, Allocation Method, Data Collect criteria) 
 

working as designed.

• No error displayed.

 

• In the sample below

 

• JDA Allocation Administrator Guide (Admin.pdf) for future version 2018.1.0.0 will reflect this limit.
• To promote / advance change of the current cap of 19 jobs/machine, please log a dedicated Enhancement Request.
• This behavior is not stated in the JDA Allocation Administration Guide. (Admin.pdf) version <= 2016