...
- The JobScheduler Universal Agent can be used to watch incoming files and to trigger a job chain start for each file.
- The mechanisms for starting job chains apply as stated in the section about File Watching
- Subsequent jobs can be executed on the JobScheduler Master or on any Agent involved.
- Any number of jobs can be executed in sequence or in parallel for incoming files.
- Incoming files can be removed or moved to a different location
- by any of the jobs involved or
- at the end of processing by a file order sink that is specified with the job chain.
- Should an incoming file be treated by jobs, e.g. parsed or otherwise accessed, then the file has to be transferred to the host on which the respective job is executed.
- Use the YADE JITL Jobs to transfer files between locations with a number of protocols such as FTP, FTPS, SFTP, HTTP, WebDAV etc.
- YADE can be executed on any host and can be configured for YADE Server-to-Server File Transfer.
- Use Cases
Configuration
- File watching is configured by the JobScheduler Master. No configuration is required on the JobScheduler Agent.
- The JobScheduler Master holds the configuration of a job chain with a file order source that is assigned to the Agent.
...
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
<?xml version="1.0" encoding="ISO-8859-1"?>
<job_chain file_watching_process_class="agent_in_dmz" process_class="agent_in_dmz">
<file_order_source directory="/srv/files/2/in"/>
<job_chain_node state="start" job="job1" next_state="continue" error_state="error"/>
<job_chain_node state="continue" job="job2" next_state="success" error_state="error"/>
<file_order_sink state="success" move_to="/tmp/jobscheduler/file/success" remove="no"/>
<file_order_sink state="error" move_to="/tmp/jobscheduler/file/error" remove="no"/>
</job_chain> |
...