Administrator

cron Job Task Handler

A cron job execution task regularly retrieves jobs from database tables, based on the job handler name and cron job schedule. The cron job task must have a cron job schedule and job handler name, which are configured in the preferences node.

Tasks are used for multiple purposes, such as housekeeping or monitoring. The task ensures that each job does not run in parallel multiple times, cancels jobs that are unresponsive, and synchronizes job execution across JVMs through a database semaphore.

Job executions are managed centrally in the MOB_JOBS table, but you can manage jobs in the Operations Dashboard portal. Jobs can also execute only on a single server.

Preferences node: /businesslayer/com/sybase365/mobiliser/money/jobs/task/cronjob/handler/CronjobTaskHandler

You can set these configuration options:
Key Default Description
task.cronpatter 0 0/1***? Defines the cron job schedule in cron expression format. The default expression triggers a job every minute.
task.jobHandlerNames MOBILISER Defines the job handler names that correspond to the values in MOB_JOBS.STR_ HANDLER_NAME database table.

When you create new handler names, use commas to separate each name, for example, MOBILISER1,MOBILISER2,MOBILISER3.

New handler names create new records in the MOB_BULLY table. Verify that there is one MOB_BULLY table entry configured for each task.jobHandlerName. For example, the default handler name MOBILISER should have an entry with the STR_SERVICE="MOBILISER". If not, insert a new one, using these values:
  • STR_SERVICE = MOBILISER
  • BOL_IS_ACTIVE=Y
  • INT_LEASE_TERM=300

Configure the name of the system property as the value for the task.jobHandlerNames key, for example ${JOB_HANDLER_NAME}. This value is replaced by the system property with the same name. You can set the system property individually for each server by adding a -D parameter to the <SMP_HOME>\Server\props.ini file.

For example, -DJOB_HANDLER_NAMES=MOBILISER,MOBILISER2.