What are you looking for?

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

    Didn't find what you were looking for?

    Extend your Search in Community

    Got any questions?

    We're always happy to help with questions you might have. Contact Us

Manager Topics

Scheduled Jobs Overview

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |  v5.1 & Higher This feature is related to v5.1 and higher.

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 performs data retention purging. A scheduled job invokes a schedule job service, which in turn calls other services that do the actual work.

One of the standard scheduled jobs is the collaboration job controller scheduled job, which processes standard collaboration jobs that are in the ready to be processed state.

In some cases, a particular solution may require custom scheduled jobs, so Manager allows you to create new scheduled jobs and configure them.

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.

Trigger Types

There are two trigger types - simple and cron.

Simple

A simple trigger type defines a number of 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.

Cron

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.

Next, learn about standard scheduled jobs.

Feedback

Did this topic provide the information you need or leave you wanting to know more? Is there some way we can make this topic better? Let us know how we can improve this documentation.

Contact Us

Community

Our Community is a dynamic, user-driven source of information that provides a home for sharing Journey platform knowledge where you can ask questions and get answers quickly.

Explore Community

Support

Temenos is committed to supporting our customers with Journey platform solutions installed in the cloud or on premise. Learn more about our Customer Care Team, and its policies, procedures, and processes.

Learn More