Documentation deprecated: This documentation is no longer being updated as of 3.8.0. For up-to-date information, see the guide information in the IBM Developer Community and the endpoint reference in IBM API Explorer.
The Aspera Watch Folder service is designed to power next-generation, large-scale, automated file and directory transfers including ultra-large directories with 10 million items+ and "growing file" sources. Collections of files and folders can now be grouped into a single “drop” and transferred to remote nodes as a single logical unit. Operators can specify the cool-off period before initiating the transfer and any local or remote post-transfer processing steps to be executed once the entire set of files in the drop has been transferred, and enable the transfer of "growing" (in progress) files. A new RESTful API enables complete programmatic control for customized and automated transfer processing. The new Watch Folder service is available in the core server products for Windows and Linux as of version 3.6.1, macOS as of version 3.6.3, and AIX, Solaris, and Isilon as of version 3.7.3. Watch Folders can be managed through Console 3.0.
The Aspera Watch Service (asperawatchd) is used to monitor changes to file systems by taking snapshots and analyzing the difference between them. It is used by Aspera Watch Folders to automatically transfer new files that are added to a source folder to an Aspera node. The output from asperawatchd can be used as input for ascp sessions to transfer updated and new files to a remote machine, as well as by Aspera Sync. The Watchd API is available as of 3.8.0 and is primarily used to manage watchd services for pull Watch Folders when the Watch Service is run on a different node than the Watch Folder service.
Watch Folder API Documentation
To view the Watch Folder API documentation, select the version that you wish to view:
Watchd API Documentation
Note: The /watchd endpoint should be /watchds in the following documentation.