Watch Folder Service Configuration - IBM Aspera HST Admin Manual

High-speed transfer server
Table of Contents

Advertisement

Daemons have the same name as the user for which they are running. For example, if you used the root user to run
your services, you should see the root daemon listed.
For example, using the root daemon and a valid JSON file, watchfolderconf.json, the output of the
aswatchfolderadmin command should look like the following:
# /opt/aspera/bin/aswatchfolderadmin create-folder root -f
watchfolder_conf.json
Successfully created instance b394d0ee-1cda-4f0d-b785-efdc6496c585.
If aswatchfolderadmin returns err=28672, confirm that the user's docroot allows access to the source
directory. If you need to make changes to your docroot, see
Watch Folder Service
If aswatchfolderadmin returns err=2, a Watch Service is not running for the user. See the previous section
for instructions on starting a Watch Service.
6. Verify that the Watch Folder is running.
To retrieve a list of running Watch Folders, run the following command:
# /opt/aspera/bin/aswatchfolderadmin query-folders daemon_name
For example:
# /opt/aspera/bin/aswatchfolderadmin query-folders root
single watchfolder:
7. Test your Watch Folder.
If the source directory contains files, the Watch Folder collects them into a drop after the Watch service scan
interval passes and transfers them to the target.
Note: No files are transferred until the first scan interval passes. If the Watch service scan interval is set to the
default, files transfer after 30 minutes.
Once Watch Folders are created, manage them by using the aswatchfolderadmin utility. For information, see
Managing Watch Folders with aswatchfolderadmin

Watch Folder Service Configuration

The configuration for asperawatchfolderd is in the <server> section of aspera.conf. It includes drop and file
management and enabling the use of raw options (ascp options that are not yet directly included in Watch Folders).
<server>
<rund>...</rund>
<watch>
<log_level>log</log_level>
<log_directory>AS_NULL</log_directory>
<db_spec>redis:host:31415:domain</db_spec>
<watchd>...</watchd>
<watchfolderd>
<remote_tmpdir_conf>hide</remote_tmpdir_conf>
<purge_drops_max_age>1d</purge_drops_max_age>
<purge_drops_max_files>9223372036854775807</
purge_drops_max_files>
<raw_options>disable</raw_options>
</watchfolderd>
[aswatchfolderadmin create-folder]
on page 210.
[aswatchfolderadmin query-folders] Found a
b394d0ee-1cda-4f0d-b785-efdc6496c585
on page 193.
| Watch Folders and the Aspera Watch Service | 174
Updating the Docroot or Restriction of a Running

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents