Journey Manager (JM) The transaction engine for the platform. | System Manager / DevOps | All versions This feature is related to all versions.
Journey Manager comes with the number of standard scheduled jobs that run regularly and perform routine operations, such as transaction processor schedule job that delivers transactions and purges data as per your environment data retention policies, generate receipts and temp file cleanup. A scheduled job invokes a schedule job service, which in turn calls other services that do the actual work. This increases flexibility by allowing you to swap out and reconfigure services. Unlike collaboration jobs, scheduled jobs are not necessarily related to one or more submissions. Instead of coming with a fixed set of hard-coded schedules, Manager allows you to manage existing scheduled jobs, modify their schedules, and control and monitor their execution.
Jobs have a schedule, which means they are automatically started by Manager at regular intervals.
All scheduled jobs use a schedule that runs them automatically at regular intervals. You can pause and resume a scheduled job or trigger it manually.
Manager uses the Quartz Job Scheduling Framework to manage scheduled jobs. If Manager is configured to use multiple server nodes, the job scheduler runs only on a one node. You must log on to the Journey Manager Home Dashboard of that node to make changes to the scheduled jobs. Also, the Quartz configuration must be set to
org.quartz.jobStore.isClustered = “true” to turn on clustering features.
There are two trigger types - simple and cron.
A simple trigger type defines how many times a scheduled job should be run and a time interval between each run. The interval can be set from 15 seconds up to 24 hours. This is sufficient for regular scheduled jobs but allows no control exactly when a scheduled job runs.
A cronCron is a time-based job scheduler in Unix-like computer operating systems. People who set up and maintain software environments use cron to schedule jobs (commands or shell scripts) to run periodically at fixed times, dates, or intervals. trigger type allows fine-grained control on when a scheduled job is executed. You must use cron expressions to specify both the interval between the runs and the time to execute the scheduled job. This is particularly useful for maintenance activities to perform overnight, outside the system peak usage times. This is particularly useful for maintenance jobs that need to run outside of peak times.
Next, learn about standard scheduled jobs.