Lightweight

Double-click install with no need to install any supporting enterprise platforms, web servers, messaging systems, databases, etc.

100% cross-platform/OS-neutral

Written in pure Java.  Tie together Windows, UNIX, and Mac machines into one coordinated batch system.
 

Fully distributed, real time event model

Actions of all 3 components (Server, Client, GUI) synchronized across your TCP/IP network via real time events and queuing.
 

Simple, intuitive GUI (see screen shots on main page)

• Visually define job schedules/dependencies.
• Extensive, layered filtering of job data to enable quick visual management/monitoring of jobs.
• View "tails" of your completed jobs' output logs (stderr/stdout) as well as OS-generated errors directly from the GUI (no need to log into remote client machines).
• View job run histories.
• Search full text of entire batch.
• Group jobs freely into logical, hierarchical units, without affecting dependencies and timing.
• Visually monitor the state of client ("agent") machines in real time.
   

Secured data

All network communications done over SSL (no job data ever passed in cleartext over the network). All job definitions stored in an encrypted database.
 

Holiday calendars

Freely define custom holiday calendars to prevent jobs from running on holidays. Each job can be associated with any calendar (or none).

Parameterized batch date

For commands that require a current date, use the parameterized system date in any format you choose. You can also use 1-day offsets (previous business day, previous calendar day).
 

Fully configurable notifications

Define alert emails on a batch-wide or per job basis.
 

XML export/import

Export/import  job definition data in order to archive/version/source code control.

Built-in jobs

Apart from pure command line jobs that you can define yourself, Job2Do comes with the following built-in jobs: non-secure FTP, file monitor, zip/unzip, job data export, email.
 

On demand jobs and "streams"

Set up sequences or "streams" of jobs that, while having complex dependencies, do not run on a specified day at a specified time. These jobs appear in the same view as your other jobs (or they can be filtered out), but can only be started manually. Upon manual start of the "lead" job, the entire stream will execute, obeying all dependencies. This feature is very useful for testing new streams or executing special "one-off" batches on an irregular basis.