Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

The JobScheduler comes with a number of powerful interfaces that are targeted at the following scenarios:

  • implementing jobs and monitor scripts that would e.g. check execution results and decide on specific actions. Such scripts often make use of the API Interface to check and manipulate JobScheduler Objects.
  • developing individual programs and complex jobs, e.g. based on the Java API Interface, that would manipulate JobScheduler objects, e.g. create and submit orders from an individual application.

Differences between these interfaces are:

  • The API Interface is used in jobs and monitors and allows access to the JobScheduler objects.
  • The XML Interface can be used by external programs or by the command line. Quite often its area of operation includes adding orders, adding events and retrieving job and order status information.

The API interface

The JobScheduler comes with an extensive set of objects and methods for implementation with jobs and monitors. Such implementations often make use of the API Interface to check and manipulate JobScheduler Objects, e.g. to add orders, to modify the order and job status. Find detailed information about objects and methods with the Reference Documentation.

Read more ....

The XML interface

The JobScheduler comes with a powerful XML interface for operation from job scripts and monitor scripts, from the command line and from other applications. Quite often this interface is used for adding orders, adding events and retrieving job and order status information.

Read more ....

Pages


 
 

Navigation


  • No labels
Write a comment…