Page History

...

<?xml version="1.0" encoding="ISO-8859-1"?>
<job<process_chain>
class    <file_order_sourcemax_processes="10" remote_scheduler="http://dmzhost:4445">
    <remote_schedulers />
</process_class>

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

• The <file_order_source> A process class is configured as explained for a JobScheduler Master. In addition the attribute remote_scheduler 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 Universal Agent is operated for.
• 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"?>
<process_class  max_processes="10" remote_scheduler="http://dmzhost:4445">
    <remote_schedulers />
</process_class>

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

  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

...