Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


The JADE have many features to simplify the day to day data transfer requirements. One of the JADE's feature is Atomic Transfer.


In some use cases files are automatically picked up either directory monitoring applications or FTP server daemons, on target server. In case of large file size data transfer take some seconds, but usually the directory watchers pickup the file as soon as initial bytes are written on the target server.


To avoid any partially transferred file being picked up by the directory watchers JADE has inbuilt feature called Atomic transfer. JADE has two parameters atomic_prefix and atomic_suffix to configure atomic transfer. As the name suggest, during file transfer JADE will create a temporary file on target server with atomic_prefix and atomic_suffix in the filename, thus make it virtually hidden for the directory watchers. As soon as file transfer completed without error, JADE rename the file to its original name. In the case of any error partially transferred files will be deleted from the target server.

JADE JITL job example

     title = "API Job for JobScheduler Advanced Data Exchange"
     order = "yes"  stop_on_error = "no" >

       <include file = "jobs/JADE-Job.xml" />
       <param name = "atomic_prefix" value = "~" />
       <param name = "atomic_suffix" value = "~" />
       <param name = "file_spec"     value = "^report.csv$" />
       <param name = "host"          value = "" />
       <param name = "local_dir"     value = "." />
       <param name = "operation"     value = "copy" />
       <param name = "passive_mode"  value = "false" />
       <param name = "password"      value = "top-secret" />       
       <param name = "remote_dir"    value = "." />       

     <script language   = "java"
             java_class = "sos.scheduler.jade.JadeJob" >

  • No labels
Write a comment…