...
The JobScheduler can be controlled by commands (e.g. starting a jobs) from external applications (or scripts).
More information of all available commands can be found here: Jetty/xml_commands.xml Command List].
The syntx of the command is similar to the xml syntax which is used to implement JobScheduler objects. The API contains commands, like "start_job, add_order, show_state, ...". Everytime when a command is sent to the JobScheduler engine, the engine will reply an answer. This answer is pure XML as well. JOC, for Example, is using this external API very intensive.
An external application, which is able and has the authorisation to send such commands to the JSEngine can use http(s) or tcp/ip to establish the communication. That means, that even a script language like javascript can be used to communicate. For Java users we have a wrapper class paket which was created using JAXB and the xsd schema for the commands and answers.
protocols
The commands can be transferred to the JobScheduler via the following protocols:
...
| Code Block |
|---|
jobscheduler.sh command "<span style="color:red;"><show_state/></span>" | sed -e 's;[^>]*$;;' | xmllint --format - |
see also
- [Technical description of JobScheduler/scheduler.pdf], Chapter 5.2 ff
- [The xml for the external API/xml.xml]
- [SOSJobSchedulerModel/SOSJobSchedulerModel/html/index.html]
- [SOSJobSchedulerModel, junit testsSOSJobSchedulerModel.junit/html/index.html]