Page History

...

• 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 successful, 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.

References

Change Management References

See also

• How to execute Jobs and Job Chains with Agents