Jobs enable you to have custom Tcl scripts executed once or repeatedly. Jobs are available in both the Content Manager and the Template Engine. With the latter, however, jobs can only be configured via the Tcl interface.
There are system jobs and user jobs. System jobs are predefined routines for the purpose of, for example, transferring update records to the Template Engine in the context of the incremental live server export. They can neither be deleted nor modified. User jobs, on the other hand, can be created, modified, and deleted as desired. Both job categories share the same name space, i. e. two jobs cannot have the same name even if they belong to different categories.
The jobs in a category are placed in the execution queue at execution time unless they have already been added to it. This prevents a more frequently executed job from being placed in the queue several times if this job or another one is currently running.
All jobs in a category are processed sequentially since they share the same execution queue. This has the advantage that several jobs can be triggered at the same time and will nevertheless be processed consecutively (initiation and execution are asynchronous). As a result, performance losses caused by simultaneous execution of many time-intensive Tcl scripts can be avoided.
The execution of jobs is logged. The maximum number of log entries the
system creates per job is determined by the value of the
jobMaxLogLength system configuration entry.
How jobs can be defined in the HTML user interface is described in section The Jobs Section.