Page History

...

An application prompts JobScheduler to start a JobScheduler 1 job or a JS7 workflow.

JobScheduler 1: Creates a text message in the XML format for the queue "JobChains". The content of the message can be e.g.:
```
<add_order job_chain='REL_PATH/JOBCHAIN_NAME' at='now'></add_order>
```

JS7: Creates a text message in the JSON format for the queue "Workflows". The content of the message can be e.g.:

{"controllerId":"testsuite","orders":[{"workflowPath":"/JS7Demo/01_HelloWorld/jdHelloWorld","scheduledFor":"now"}],"auditLog":{}}

JobScheduler 1.x: Reads a message from the queue „JobChains" and sends the XML snippet via TCP/UDP to a JobScheduler instance.
JS7: Reads a message from the queue „Workflows" and sends the JSON body via HTTP(S) to a JS7 JOC Cockpit instance.

A Java job runs in a
- JobScheduler 1: job chain and implements the Producer to send information to the Message Service after completion of a number of job nodes in a job chain.
- JS7: workflow and implements the Producer to send information to the Message Service after completion of a number of job nodes in a workflow.
A Java job runs in a
- JobScheduler 1: job chain and implements the Consumer, i.e. connects to the Message Service to check for new messages that include possible job start requests.
- JS7: workflow and implements the Consumer, i.e. connects to the Message Service to check for new messages that include possible add order requests.
The Producer as well as the Consumer run run in any job chain/workflow.

Producer: Jobs
- JobScheduler 1: Job sends some information to a message queue to signal completion of a job chain.
- JS7: Job sends some information to a message queue to signal completion of a workflow.

Consumer:
- JobScheduler 1: Reads JobScheduler XML API command from a message and hands over the XML command to JobScheduler for execution.
- JS7: Reads JobScheduler JSON command from a message and hands over the JSON body to a JS7 JOC API call for execution.

Use with File Transfer jobs

...