Normally file movement is composed of a multi-step sequence of transfers.  Aspera file transfers enable either file-by-file or session based submissions.  This can include automatic forwarding which can be initiated either externally or internally by either a push files to, or pull of files from. This forwarding is commonly done by a server in a DMZ which forwards the request to a server inside the network or to a server located inside another DMZ stage when using a multistage DMZ architecture. After that forward completes the data gets forwarded again to the final destination.  

Files can be automatically moved to different folders within the server.  This is useful for archival purposes, post processing, or for more complex multistage transfers.

Each step in the automation process has a self-contained state which can be seen in the manifest file.  The manifest file is useful for debugging, troubleshooting and tracking, a normal manifest file will usually contain:

  • User information
  • Cookie and Token data
  • Directory structures throughout the process

Since automated transfers are powered by FASP they are fast and secure.  They use secure authentication and content protection with encryption during transit with the ability to utilize encryption at rest (EAR).

Aspera Console has the capabilities to manage the Nodes.  This allows you to easily monitor and control the transfers and receive notifications throughout the process.

Automation tools are cross platform and available for Windows, Macintosh and Linux.

Video player

Video

×