Job Triggering

Kick Off Jobs Based on Events, Files, and Other Jobs

JAMS provides for event-driven job scheduling to allow jobs and processes to be triggered by events such as file transfers, system startups, runaway processes, or user written events.

File Triggers

JAMS event-based scheduling has built-in triggers which enable users to execute processes on any operating system based upon files being created, modified or deleted.

File Trigger

Event Triggers

Multiple triggers can be set on jobs so that jobs are triggered based on events, a specific date and time, or even from previous jobs that have failed or succeeded. With full support for Windows Workflow Foundation, users can create workflows that depict the dependencies that exist between various processes that are being managed through JAMS.

Status Trigger

Status Triggers

JAMS can check exit status and determine the appropriate job to trigger based on conditional flows. JAMS event-based job scheduling allows for jobs to have expected run times so that they can be monitored. Alerts can even be triggered to the appropriate person to notify him/her that a job is waiting for that person to release a file.

Alerts can be triggered when an expected event does not occur within a specified time window. With JAMS you can, as an example, alert a vendor or supplier that the system is waiting for their action or a file.

Variable Trigger

Variable Triggers

JAMS event-based job scheduling can also interrogate data by using JAMS Variables and allow specific data to be used as an alternative approach to an event based job trigger. JAMS Variables can be used between jobs so that data is passed throughout the workload.

Now, we’re leveraging file triggers. As soon as something happens in the database, it writes a file to the server. JAMS sees the file and it kicks off another job in real-time.

Rishi Maharaj, Senior Systems Administrator

Read the Case Study