...

• The following command line arguments can be used with a File Transfer job:
  • -settings is the path to a YADE *.xml or *.ini configuration file that holds fragments and profiles for transfer of files.
    • YADE configurations can be managed from the Configuration -> File Transfer View and can be exported to *.xml files.
    • As the YADE configuration file has to be located with an Agent we recommend manually deploying or transferring this file to the Agent.
  • -profile is the name of the profile to be applied from the the YADE configuration file.
  • -java-options are options for the Java Virtual Machine. Frequently such options are used to specify the maximum heap size. By default YADE will use 32 MB, however, if 1000s of files are transferred with a single call to the YADE Client, e.g. when using a file specification to transfer any files from a directory, then it will be necessary required to increase the default heap size.
  • -log-level enables to specify Log4j2 log level indicators such as info, debug, trace that will provide more detailed information, e.g. for example in case that files permanently could not cannot be transferred. Find more details from JS7 - Log Levels and Debug Options.
• The above job script does not indicate a specific selection of files for transfer. This gives you two options:
  1. Hardto hard-wire the file selection directly with the YADE configuration file (yade.xml).
  2. Specify to specify the file selection from an order variable that is mapped to an environment variable with the job script. Use this environment variable with the YADE configuration.
     • Example:
       
       • Add an environment variable such as e.g. YADE_FILE_SPEC to your mapping of environment variables.
         • The value can be a hard-wired regular expression:
           
           
           
           
         • The value can be mapped from an order variable or node argument:
           
           
           
       • The YADE configuration can makes use of the ${YADE_FILE_SPEC} environment variable that will be substituted at run-time, e.g. with:
         
         
         
         
       • Note that this mechanism can be used for any environment variable names variables that are available for a job and with the YADE configuration.

File Transfer View

The File Transfer View view allows monitoring of current transfers and detailed checking checks of past and present transfers:

...

In this situation consider to use the JS7 - Resource Locks to implement an exclusive lock or a shared lock that will limit parallel access to a resource. Any file transfer jobs that cannot immediately acquire a Resource Lock will wait until the lock is freed.

Further Resources

• YADE
• JS7 - File Transfer History