Scheduling work queue writers and batch processes

The scheduler-config.xml file contains entries in the following format:

<ProcessSchedule process="process_code" env="environment">
  <CronSchedule schedule_attributes/> 
</ProcessSchedule>

The process attribute sets the process to run. The env attribute is an optional attribute that specifies the environment in which the schedule definition for the process applies. The schedule_attributes value is a valid schedule specification.

If needed, you can list multiple ProcessSchedule entries for the same process. The process then runs according to each specified schedule. If you schedule a process to run while the same process is already running, then PolicyCenter skips the overlapping process. If the scheduler-config.xml file does not list a process, the process does not run.

Generally, schedule the amount of time between process runs in hours as opposed to minutes. This is because some batch processes require a lot of server resources. Schedule such processes to wake infrequently or at times that the server is less busy, such as late at night or very early in the morning.

You may want to schedule some PolicyCenter processes to run periodically throughout the business day. For example, the default configuration of PolicyCenter schedules the ActivityEsc work queue to run every 30 minutes. Exclude running such processes periodically during your nightly processing window. Instead, wait until the end of the processing window to run them. For example, schedule the ActivityEsc process to run every 30 minutes except during your nightly processing window. Alternatively, run such processes at prescribed places in your chain of nightly processes.

The PolicyCenter scheduler uses the PolicyCenter server time for reference.