Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« POV: FDMEE vs Cloud Data Management | Main | ODI 12C Miscellaneous concepts: »

Job Scheduler

A job scheduler is a system which enables the execution of jobs from the back-end. Job scheduling is also referred to as batch scheduling, or workload automation. The job-schedulers offers a GUI based platform for definition and monitoring of background processes running on a distributed sets of servers, applications, operating systems and networks. The scheduler works on simple logic. It simply picks up the jobs which are to be run on a day at particular time and processes them based on various constraints. It also offers the dependency kind-of model, in a way that the jobs can follow each other. Thus, day-to day activities of Hyperion, SAP, PeopleSoft, or mainframes admins can be easily automated based on the underlying business needs and timelines.

One of the popular job schedulers is Maestro, which offers all the wonderful features of graphical user interface. Few of the features of maestro are mentioned below: -


  • Central control: It offers central control for the processes configured from various platforms and applications. It saves from the hassle of dealing with the different platforms and applications present at different servers. It consolidates job scheduling across various systems like Linux, Unix, Windows, Mainframes etc. at one place.


  • Simple Interface: It offers a simple interface, which enables to easily track and manage jobs, schedules, tasks, job status, and job history helping in speedy diagnosis of the underlying issues. It offers views, which show jobs that are active, running, inactive, held, or that require assistance.


  • System Recovery: This feature makes sure that after a job fails, they are addressed automatically by putting dependent jobs on hold, run a recovery job (if defined), stop processing further jobs, re-run the original jobs, or continue to the next job, alert the operator via email.

  • Calendars and Schedules:  Maestro offers scheduling and calendar feature to manage batch job execution. Each schedule has a date, runs on that particular date/week/ calendar and contains a list of jobs which are defined to be executed on that particular date. Maestro carried forward the uncompleted schedules from the previous day. A calendar if an array of dates. Any number of calendars can be created to meet scheduling needs. For e.g.: a calendar name "month-end" can contain the list of the dates of "financial close", "Holiday" can have list of financial holidays when the jobs should not execute.

  • Queuing system: Maestro carries out a deterministic approach to identify the priority of the jobs. It considers parameters like elapsed execution time, estimated execution time, Job dependency, count of simultaneous jobs runs allowed for a user, file dependency, occurrence of prescribed events, resource availability, etc.

  • Security: The system is secure enough to check IP validation to prevent access by external systems.

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles