IBM Aspera HST Admin Manual page 182

Post Processing Fields
Optionally, specify post-processing to do after a drop or file is successfully transferred.
{
...
"post_processing":{
"source":{
"type":"TRANSFER_NONE",
"archive_dir":"/watchfolder_sessions/{$UUID}_{$DATETIME}"
}
},
...
}
Field Description
type The type of post-transfer processing. Files can be archived, deleted,
or retained after transfer of a drop. When files are archived or
deleted, source sub-directories are also deleted from the source,
unless the sub-directories were empty to start. File structure is
preserved in the archive.
•
•
•
•
archive_dir The destination of archived files, if the archive type is
TRANSFER_ARCHIVE. The path can be determined using the
following variables:
•
•
•
•
•
•
•
•
•
•
•
•
TRANSFER_NONE: Files stay in the source directory.
TRANSFER_ARCHIVE: Files in the source directory are moved
to a final archive after successful transfer. This option is not
supported for sources in object storage.
TRANSFER_DELETE: Files in the source directory are deleted
after successful transfer once the session completes.
FILE_TRANSFER_DELETE: Files in the source directory are
deleted after each successfully transfers, rather than waiting for
the session to complete.
{$TIMESTAMP} (Drop creation time in seconds since epoch)
{$DAY_OF_MONTH} (Time format for drop's creation time)
{$MONTH}
{$YEAR}
{$HOUR}
{$MINUTE}
{$SECOND}
{$DATETIME} (alias for {$YEAR}{$MONTH}
{$DAY_OF_MONTH}-{$HOUR}{$MINUTE}{$SECOND})
{$UUID}
{$NAME}
{$STATE}
{$FILE::STATE} (such as SUCCEEDED, FAILED)
| Watch Folders and the Aspera Watch Service | 182
Default
TRANSFER_NONE
N/A