...
| Excerpt |
|---|
The JobScheduler comes with a number of powerful interfaces that are targeted at the following scenarios: - implementing jobs and monitor scripts monitors that would e.g. check execution results and decide on specific actions. Such scripts implementations 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
| Excerpt Include |
|---|
| API Interface |
|---|
| API Interface |
|---|
| nopanel | true |
|---|
|
Read more ....
The XML
...
Interface
| Excerpt Include |
|---|
| XML Interface |
|---|
| XML Interface |
|---|
| nopanel | true |
|---|
|
Read more ....
The JobScheduler REST Web Service Interface
| Excerpt Include |
|---|
| JobScheduler - REST Web Service |
|---|
| JobScheduler - REST Web Service |
|---|
| nopanel | true |
|---|
|
Read more ....
The JOC Cockpit REST Web Service Interface
| Excerpt Include |
|---|
| JOC Cockpit - REST Web Service |
|---|
| JOC Cockpit - REST Web Service |
|---|
| nopanel | true |
|---|
|
Read more ....