Page History

...

<?xml version="1.0" encoding="ISO-8859-1"?>
<job  title="API Job for JobScheduler Advanced Data Exchange" order="yes" stop_on_error="no" name="jade">
    <description >
        <include  file="jobs/jadeJob.xml"/>
    </description>
    <params >
        <param  name="operation" value="move"/>
        <param  name="source_host" value="dmzhost"/>
        <param  name="source_protocol" value="sftp"/>
        <param  name="source_ssh_auth_method" value="password"/>
        <param  name="source_user" value="foo"/>
        <param  name="source_password" value="bar"/>
        <param  name="target_dir" value="c:\temp"/>
        <param  name="target_protocol" value="local"/>
        <param  name="file_path" value="%scheduler_file_path%"/>
    </params>
    <script  language="java" java_class="sos.scheduler.jade.JadeJob"/>
    <run_time />
</job>

...

• 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 JADE 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 JADE YADE job could be run on JobScheduler Universal Agent to send the file to the JobScheduler Master host.
• If the transfer is successfull, a file_order_sink is not required, as the JADE YADE Job is configured with the move command which removes the input file from the agent host after transfer.