Start
-
-
The Job Scheduler can be configured using
XML- and .ini files
and recognises command line options.
Jobs, job chains and other objects can be dynamically configured
using Hot Folders.
Jobs, job chains, etc. can also be
centrally configured
by a Supervisor Job Scheduler
and replicated for other Job Scheduler instances.
Jobs, job chains etc. can be centrally configured
by a Supervisor Job Scheduler for remote Job Scheduler instances.
-
-
A GUI for configuration and documentation is provided with the Job Scheduler.
-
Database and History
-
The Job Scheduler can save its task and order queue information in a
database,
which is used to record a
history containing individual
log files.
-
Operation as a Service
-
The Job Scheduler can be installed as a service
on Windows systems and started as a
daemon on Unix.
-
-
Fail-safe operation with automatic failover.
Jobs
-
Explanation of a Job
-
A job consists of a configuration that determines the program
that should be executed, the run time attributes,
behaviour in event of an error and optional components,
e.g. for pre- and post-processing.
-
Application Programming Interface (API)
-
The classes and methods that a job has access to.
Available for
Java,
JavaScript,
VBScript and
Perl.
-
-
Locks allow the access of multiple jobs to resources to be regulated.
-
-
Jobs can be executed on remote Job Schedulers.
|
|
Order processing and File Monitoring
-
Orders and Job Chains
-
The Job Scheduler can process orders through job chains.
Job chains define the order in which jobs are to be executed and can be restarted if required.
-
-
Files added to a directory are can be used by the Job Scheduler to create and start orders.
These can then be processed by a job chain.
-
Directory Monitoring
-
The Job Scheduler can monitor directories and start jobs when files are added to these directories.
-
Distributed Orders
-
Orders can be processed by clusters of several Job Schedulers running on different servers.
Protocols and Forwarding of E-mails
-
-
The Job Scheduler maintains various protocols for jobs, tasks and orders as well as a common protocol,
the
scheduler.log.
-
-
The Job Scheduler can be configured to send task protocols and messages by E-mail.
Communication and Operation
-
-
The Job Scheduler has its own
HTTP server
and can be operated using a HTML interface.
- Telnet und TCP
-
XML commands can be transmitted using a telnet client or a TCP connection.
Command: telnet localhost 4444. See .
-
-
The Job Scheduler can process
commands in XML
as well as in
HTTP,
TCP and
UDP.
|