Jobs

DMZTransfer manages transfer through jobs that are defined as:
A transfer of files from one organisation to another that is scheduled to occur at a defined frequency. Jobs are defined and owned by the uploader, who can modify the job via the browser interface.

The agreement between uploader and downloader is that the uploader will upload all their files and complete the upload before the date and time of the job instance

Example: A weekly job was created with an Initial Date/Time of 1/1/2000 10:00:00 and the job specifies files will be kept for 1 day, then every day from then on, the uploader must upload all their files before 10:00:00 that day.

The downloader can try and download the files anytime during the day (if the uploader has uploaded them early) but they are only guaranteed to be available after 10am each day. Since the job has been defined to keep the file for one day, the downloader can download these files any many times as they like until 10am the next day. Note: to download a file that has already been downloaded, do not use pending (as the files will not be pending the second time).

• Job Name
  The name that each occurrence of this job will have. This name must be unique for your organisation. Spaces are allowed, when you use the script client from the command line, you will need to put double quotes around the job name. e.g. startDMZ -cupload -j"my daily upload job"
  
  
• Initial Date/Time
  The time of the first iteration of this job. No uploads can occur for dates before this value. This has extra meaning for different job frequencies as follows:
  • Adhoc
    The initial Date/Time is the earliest time that that iterations of this transfer can occur.
  • Daily
    The transfer is expected each day from this date and expected each day by this time.
  • Weekly, Monthly, Yearly
    The date part of initial Date/Time is when the first upload could occur.
    This date may not be one of those required by the schedule
    (i.e. for job that has a schedule of each Tuesday, if the job is created on Monday, then Monday will still be the initial date. The next iteration, however, will be on the next tuesday, and tuesday from then on
    The time part is used for each repetition, either weekly, monthly or yearly
    
    
• Job description
  Textual description for the job, useful for adding more information for the users of this job
  
  
• Deliver to
  The name of the downloading organisation. Contact your administrator if an organisation you need to contact is not available.
  
  
• Frequency
  Textual description of the currently selected frequency.
  
  
• Change frequency to:
  The following frequency types are available:
  • Adhoc
    Transfers can occur at any time. This type of job has no frequency constraints and uploads can occur whenever they are required. This type of job is often used to send small numbers of corrections or abnormal files via the browser. It differs from the other types jobs by not grouping multiple files that are sent. Instead, a separate instance of the job is created at the start of transferring each file.
    e.g. Uploading 5 files to an adhoc job with the script client would result in 5 pending transfers for the downloader.
    See the script client section of the documentation for how it manages to download all the pending adhoc transfers.
  • Daily
    Transfers occur each day from the Inital Date/time. The time value is also used as the time for each repetition.
  • Monthly
    Transfers occur either at a certain calendar day (e.g. 5th of each month) or a certain business day (3rd last business day of the month). Business days are interpreted as not New Zealand national holidays
  • Yearly
    Transfers occur each year at the same day
    
    
• Associate files
  This is the ability to constrain the number and type of files that can be uploaded.
  • Associate files with this job
    This allows the user to control how many files must be uploaded before the job is complete. This is not editable for Adhoc jobs
  • Associate files "Select Files"
    This allows the user to control the exact number and names of the files that must be uploaded before the job can be complete. This is not available for Adhoc jobs
  • Manual
    This allows the user to decide for each time they upload, how many files they want to upload. This in effect has puts no constraints on the number of names of files to upload. This is not available for Adhoc jobs. Marking a job complete is a manual process in the Browser by clicking the button and it is automatically done within the script client after each call to the script client.
    
    
• Monitor Job
  This check box indicates that DMZTransfer will check that uploads are completed in time and that download are completed within the keep-for period. This should almost always be selected.
  
  
• Deliver files within(download specific parameter)
  Specifies the number of hours after the download becomes available that the downloader should have retrieved the files. If the download is still pending after this time, then an email alert is sent to the "download email alert to" job field.
  
  
• Retain files for
  This is the period of time for each iteration, that uploaded files will be available for download. After this time, the files will be deleted.
  
  
• Upload/Download email Alert to
  An email address to send alerts for uploads and that have been missed. To send to multiple recipients, setup a mailing alias group within your organisation.
  
  
• Destination directory
  This is currently unused
  
  
• Minimum file size
  Minimum size (in bytes) for each uploaded file
  
  
• Overwrite files
  For script client only. Allow files that have the same name and are being downloaded into the same directory to overwrite those files. This requires Overwrite files after to be specified.
  
  
• Response Required
  Activates messages - available within the browser interface - so that uploaders and downloaders can be notified of each upload and download via the messages tab on the website
  
  
• Upload Response to
  DMZTransfer user account to send messages regarding uploads. These will appear in the messages tab on the browser.
  
  
• Download Response to
  DMZTransfer user account to send messages to regarding downloads. These will appear in the messages tab on the browser.
  
  
• Maximum file size
  Maximum size (in bytes) for each uploaded file
  
  
• Overwrite files after
  For script client only. Number of days after files are available for download to disallow overwriting of any existing files on the local machine. This is only effective if Overwrite files is also checked
  
  
• Information fields only
  Extra packing-slip information that can allow uploaders and downloaders to communicate about the methods to process the files once they are downloaded. These are setup on this job screen and are made available as part of the packing slip to the downloader to process as they see fit.