ICS ANNOUNCES KRONOS ENTERPRISE SCHEDULER 3.00
Paramus, NJ - Novemeber 21, 2001 - Indus Consultancy
Services (ICS) today announced the 3rd-generation release of Kronos
Enterprise Scheduler, a full-featured job scheduling system written
for the Enterprise Java (J2EE) environment. This major new release
adds new types of jobs, enhanced dependency support, new types of
dependencies, greatly enhanced Java tasks, and support for the
Microsoft SQL Server database.
Previous releases of Kronos Enterprise Scheduler required every job
to have a regular schedule for execution. With the introduction of
Release 3.00, jobs can be one of three types: Scheduled Jobs are the
traditional jobs which Kronos Enterprise Scheduler has supported all
along. Every scheduled job will have a schedule defined which will
determine when the job will execute. Manual Jobs will execute only
when explicitly instructed to do so, rather than executing at
regularly scheduled times. This is useful when a job needs to
execute at irregular intervals. For example, a job may need to run
only when conditions are met within an external system; the external
system can use the Kronos Enterprise Scheduler APIs to execute the
job strictly on an as-needed basis. Finally, there are Dependency-On
ly Jobs. Again, these jobs have no regularly scheduled execution,
but will run whenever all of their dependecies have been satisfied.
A scheduled time can also be provided in the definition of the job,
to control the time of day that the job should execute once the
dependencies are met.
Dependencies themselves have been greatly improved in this latest release.
A new concept of a Dependency Timewindow has been introduced, which allows
you to specify a timeframe within which a job’s dependencies need to have
been met. For example, Job A might depend upon the sucessful execution of
3 other jobs. By defining a Dependency Timewindow of "last 24 hours" for
Job A, this would indictate that Job A would only run if the 3 jobs it
depended on had run sucessfully within the past 24 hours. Kronos
Enterprise Scheduler now supports File Dependencies as well, allowing you
to define a job as executing only if a particular file exists, does not
exist, or has changed within a given timeframe. This is particularly
useful for data transfer jobs which need to execute anytime a new version
of a file arrives.
Support for parameter passing to Java-based tasks has also been improved.
The introduction of User Variables means that parameter values are no
longer necessarily fixed once the task is created. Instead, each parameter
on a method is associated with a User Variable, and each User Variable
has a default value which is the value normally used. If the job is
executed via the Kronos Enterprise Scheduler API, however, the caller of
the API can specify overridding values for the variables. Additionally,
in previous releases, only methods with primitive datatypes (or the object-
equivalent of the primitive type) were supported. With Release 3.00, all
methods with either primitive or serializable parameter types are supported.
If the task is defined through the Kronos Enterprise Scheduler User
Interface, complex objects will have default values of null; however, if
defined via the API, the caller of the API can provide the object which
should be used as the default parameter value, and this will be serialized
to the database for later use. Again, these values can all be overridden
should the job be executed via the API.
So whether you are looking for an end-user tool to manage scheduling
of system or application jobs throughout your enterprise, or whether
you are looking for a powerful API to bring scheduling functionality
to your own applications, Kronos Enterprise Scheduler continues to
add innovative features that keep it ahead of the competition.
visit product page at www.indcon.com.
Request a FREE 30-day evaluation and see for yourself why
Kronos Enterprise Scheduler remains the most comprehensive solution
on the market today.