Configure Post Transfer Actions in Reflection for Secure IT

If you have configured Reflection for Secure IT Server for Windows (version 8.2 or later) as your Transfer Site file server, you can set up Post Transfer Actions directly on this server. Unlike Post Transfer Actions created in Gateway Administrator, Post Transfer Actions created this way are not associated with individual Transfer Sites; by default they act on all uploaded files. A typical use for this kind of Action is running a virus scanner.

Post Transfer Actions configured on the Reflection for Secure IT server run under the same account as the Reflection for Secure IT service (the Local System account). This account has administrative privileges on the local system.
By default, Post Transfer Actions act on all files uploaded to this server. A filter option is available that enables you to limit the action to all files that match the filter specification.
You can configure multiple Post Transfer Actions, but the order of actions in the Post Transfer Actions pane does not control the order of execution for these actions. To ensure that a series of actions takes place in a predictable sequence, include the actions in one batch file.
Outputs from one Post Transfer Action cannot be used as inputs to another Action.
Failed execution of a Post Transfer Action does not prevent other Post Transfer Actions from executing.
Post Transfer Actions are executed only after successful transfers. They do not run after unsuccessful (or canceled) transfers.
Post Transfer Actions are not supported for downloads or other file transfer events (such as renaming or deleting a file on the server).
By default, up to 50 actions can execute simultaneously. You can modify this default on the Post Transfer Actions pane.

Logging for Reflection for Secure IT Post Transfer Actions

Error messages and Post Transfer Action output can be viewed in either the Windows Event Viewer or the server's debug (text) log file. Windows Event logging is enabled by default, but the default logging level does not include the Post Transfer Action output; you need to increase the logging level to "Information" to see this content. Debug logging is not enabled by default. When working with Post Transfer Actions, enabling debug logging to a text file is recommended.

To configure Post Transfer Action logging to a text file on a Reflection for Secure IT Server for Windows

From the Reflection for Secure IT Server Configuration tab, click Debug Logging.
Click Enable debug logging to log file. By default, this log is set to Information, which is is sufficient to include Post Transfer Action output and error messages.

You can click Custom to fine-tune the level of output that is sent to this log. Three settings control Post Transfer Action output: LOG_I_PTA_ERROR, LOG_I_PTA_RESULT, and LOG_T_PTA.
Save your settings (File > Save Settings).

To view the text log file

From the Reflection for Secure IT Server console View menu, select View Latest Debug Log File.