Job scheduling in CM Core

In KCM Core, jobs are distributed over the available KCM Document Processors in the order they arrive. If a single KCM Core installation is used to serve both KCM ComposerUI Server and batch jobs, long-running batch jobs may cause a delay in the processing of the interactive KCM ComposerUI Server requests. To prevent this, KCM Core offers two options that cause KCM ComposerUI jobs to be run before other jobs. Add one or both of these to the dp.ini file in the Config folder of the ITPWork folder, and restart KCM Core.

[Configuration]
PrioritizeOnLine=Y		     ; Y or N, default value N
DedicatedOnLine=<number>	; Number of CCM Document Processors to
 					                   ; reserve, default value 0

When set to Y, PrioritizeOnLine causes KCM Core to schedule KCM ComposerUI jobs ahead of other jobs, if taking jobs from the queue. Note that this only has an effect if both KCM ComposerUI jobs and other jobs are queued. If all KCM Document Processors are processing jobs and a KCM ComposerUI job is submitted, it has to wait until a KCM Document Processor has finished processing its job.

With DedicatedOnLine you can reserve one or more KCM Document Processors for KCM ComposerUI jobs. These KCM Document Processors are not used for other, possibly long-running, jobs. This makes it much more likely that KCM Document Processor will be available quickly for processing of KCM ComposerUI Server job, if one is submitted.