The humble job definition is one of the core elements of JAMS Job Scheduler. If you’ve ever tried to apply your business logic – e.g. “Run this job once on the first day of the month.” – to jobs in two different scheduling tools, you know the value of consistency.
Watch our Definitions video to learn how to define batch processes for the modern enterprise.
JAMS definitions enforce scheduling standards across the entire infrastructure, no matter how heterogeneous. Managing IT is complicated enough with multiple programming languages and a constantly changing array of business applications. Letting each one of these technologies dictate its own dictionary of scheduling and automation terms is a major source of inefficiency.
IT teams may disagree on the best method of tackling a specific project, but they can all agree that “Monday” is “Monday”. If a team decides that a particular batch job should run every Monday, there should be a unified way to enforce that rule. Just as the MVC method helps software respond quickly, the separation of scheduling logic and job source helps IT operations adapt. Did you want to change the execution of 20 batch processes from “Monday” to “Every Other Monday” to match with a new business rule? With JAMS, you could apply that new definition in one uniform way. If you rely on multiple schedulers, a simple change like that is dependent on the scheduling logic in each host system. The Cron guy starts down the every second week path, while the PeopleSoft team wants a start date so they can set Process Scheduler to recur every two weeks. Sound familiar?
Scheduled Date is just one of more than 150 properties you can apply to batch processes in JAMS. Watch the video for a quick walk-through or download JAMS to explore deeper.