Introduction
The JobScheduler comes with a number of powerful interfaces that are targeted at the following scenarios:
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.
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.
The JobScheduler REST Web Service Interface
The JobScheduler comes with a powerful REST Web Service interface for access by external applications. This interface is used for tasks such as adding orders, adding events and retrieving job and order status information.
The JOC Cockpit REST Web Service Interface
The JOC Cockpit comes with a REST Web Service interface for JSON. This interface is used for access to the job inventory and the job history as well as individual objects such as jobs, job chains and orders and provides current status information.