adTempus 4 now available

adTempus

Job Scheduling and System Automation

Feature Comparison

The following table highlights differences between the Arcana Scheduler and adTempus.

Feature Arcana Scheduler adTempus
Job History and Status

Administration tool shows the status of only the most recent instance (execution) of the job to be started.

Job errors and warnings are reported in the system Event Log and can be viewed and filtered using the Event Viewer.

A limited amount of information (start and stop times) can be written to the Event Log for each instance of the job.

Administration tool shows the status of all instances of the job.

Complete history of the job (including start/end times, statistics, and statuses for each instance) is retained and can be viewed from the administration tool.

Error and warning messages are stored within adTempus and can be viewed from the administration tool.

History information is stored in a relational database, allowing access by third-party reporting tools.

Tasks Supported 

Can execute any program, batch file, script, document file, etc., in the same fashion as the Windows Run command. Services can be controlled using batch files that issue the appropriate commands.

Each job executes a single task.

Can execute any program, batch file, script, document file, etc., in the same fashion as the Windows Run command.

Also has native support for starting, stopping, and monitoring services; restarting the computer; executing scripts that can return exit codes; and terminating external processes.

Each job may have multiple steps, each of which executes a single task.

Job Dependencies  Each job may depend on either a file or group of files (presence or absence) or the state of an external process.

Each job (or step within a job) may depend on any number of files or processes.

Jobs or steps may also be made dependent on the status of another job or on the result of a user-provided script (which can be used to develop custom dependencies).

Connecting Jobs  Each job may execute one other job based on whether it completes successfully, completes with errors, does not run, or is terminated due to time limitations. Each job or step may execute any number of other jobs, based on many different trigger conditions.
Notification of Job Status  Each job may send an e-mail message to designated recipients based on its status (sending notification, however, precludes the execution of a "successor job" as described in the previous item).

Each job or step may send e-mail messages based on many different trigger conditions. Notification can be in addition to other actions (such as restarting the job).

The administration tool provides a "Failed Job" query that refreshes continuously to notify users of failed jobs.

Restart and Recovery  Jobs may be configured to execute automatically on service startup if their last scheduled execution time was missed.

Jobs may be configured to execute automatically on service startup if their last scheduled execution time was missed.

Additionally, jobs can be automatically restarted if the adTempus service was shut down while they were running (e.g., due to a system crash).

Holidays  Jobs can be configured to recognize a user-defined set of holidays, and to not run on those days. One set of holidays is used for all jobs. Any number of holiday sets can be defined; each job may be configured to use the appropriate set of holidays. If a job's execution falls on a holiday, it can be configured to skip execution, or run on the next, previous, or nearest day, business day, or non-holiday.
Scheduling  Each job may have any number of execution schedules. Each schedule specifies the months, days, days of the week, hours, and minutes at which the job will run. Each job may have any number of execution schedules. Times may be defined as intervals or specific times (every 3 minutes; every 1 hour; 12:03 AM and 3:05 PM). Dates may be defined as intervals (every 2 days), specific dates (November 20), specific kinds of dates (every Tuesday; Last day of month) or using complex rules (Third Tuesday of month; nearest business day to last day of month). Dates based on Easter are supported.
Security  Users may be granted access to all jobs, or only to those jobs that use their user account. A user either has full permission for a job or no permission for a job. Permissions may be set for each individual job; the access for each user may be customize to allow or prohibit viewing, modifying, adding, deleting or executing jobs.
System Monitoring  Not available The System Monitoring edition of adTempus allows you to monitor computers, files, processes, WMI events, and Event Log events, and trigger jobs based on these objects.
Reporting and Job Documentation  The Job Browser tool can produce a text-only list of a job's scheduled run times and properties. Built-in and custom reports can be used to list job properties, job accounting, etc. The Job Flow Diagram feature automatically produces graphical representations of jobs and job chains.
Distributed Scheduling  Jobs on one computer can trigger jobs on another computer by running a command-line job execution tool.

Includes built-in support for linking jobs on different computers.

Distributed Scheduling feature also allows centrally-managed jobs to be executed on "agent" computers in Slave, Mirror, or Load Balancing configurations.