Page History

...

<?xml version="1.0" encoding="ISO-8859-1"?>
<job_chain file_watching_process_class="agent_in_dmz">
    <file_order_source  directory="/srv/files/1/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>

Explanations

• A process class is configured in a separate file, e.g. agent_in_dmz.process_class.xml, as stated with the above sample. The process class specifies the protocol, host and port that the Agent is operated for.
• The job chain references the above process class with the file_watching_process_class attribute that causes the subsequent configuration for file order sources and file order sinks to be applied to the respective JobScheduler Agent.
• The <file_order_source> is configured as explained for a JobScheduler Master.
• Subsequent jobs are executed on the JobScheduler Master
• The <file_order_sink> specifies incoming files to be moved to different directories on the JobScheduler Agent host depending on the execution result of the job chain.

...

The following configuration applies to a job chain that specifies file watching and job execution on the Agent: 

<?xml version="1.0" encoding="ISO-8859-1"?>
<job_chain 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>

...

• A process class is configured in a separate file, e.g. agent_in_dmz.process_class.xml, as stated with the above sample. The process class specifies the protocol, host and port that the Agent is operated for.
• The job chain references the above process class that causes the subsequent configuration for file order sources, file order sinks and jobs to be applied to the respective JobScheduler Agent.
• The <file_order_source> is configured as explained for a JobScheduler Master and applies to the JobScheduler Agent.
• Subsequent jobs are executed on the JobScheduler Agent.
• The <file_order_sink> specifies incoming files to be moved to different directories on the JobScheduler Agent host depending on the execution result of the job chain.
• For more detailed explanations see see:

  • Jira
    server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1301

  • Jira
    server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1300

  • Jira
    server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JS-1422

File watching with file transfer for job execution on the JobScheduler Master

...

• A process class is configured in a separate file, e.g. agent_in_dmz.process_class.xml, as stated with the above sample. The process class specifies the protocol, host and port that the Agent is operated for.
• The job chain references the above process class with the file_watching_process_class attribute that causes the subsequent configuration for file order sources to be applied to the respective JobScheduler Agent.
• The <file_order_source> is configured as explained for a JobScheduler Master and applies to the JobScheduler Agent.
• The YADE file transfer Job is executed on the JobScheduler Master
  • It receives the triggered file, specified in the file_path parameter with %scheduler_file_path%, from the Agent host.
    • At runtime %scheduler_file_path% is substituted with the actual path of the triggered file.
  • Alternatively, a YADE job could be run on JobScheduler Universal Agent to send the file to the JobScheduler Master host.
• If the transfer is successfullsuccessful, a file_order_sink is not required, as the YADE Job is configured with the move command which removes the input file from the agent host after transfer.

Change Management References