Configure Post Transfer Actions in Gateway Administrator

Post Transfer Actions run on the Transfer Site file server.

Post Transfer Actions are assigned to Transfer Sites using the Add Actions option. An Action will run only if it has been added to the Transfer Site.

Although you can assign multiple Actions to a Transfer Site, the order of actions in the Transfer Site definition does not control the order of execution for these actions. To ensure that a series of actions takes place in a predictable sequence, it is possible to include the actions in a single script, then create an Action that runs that script. However, using Jobs is the preferred approach where multiple actions are required to occur in a specific sequence.

Outputs from one Action cannot be used as inputs to another Action.

Failed execution of an Action does not prevent other Actions from executing. Use Jobs when you want to ensure that one action is successful before the next action in a sequence is initiated.

Actions are executed only after successful transfers. They do not run after unsuccessful or canceled transfers.

Post Transfer Actions run immediately after file is transferred. Job actions do not run until after the configured scan interval.

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 10 Actions can execute simultaneously. Additional actions are added to a queue and executed as other actions are completed. You can modify this default in the Gateway Administrator properties file using the configservice.event.threads setting.

If the Reflection Gateway Administrator service or computer shuts down for any reason, unprocessed actions are processed when the service resumes.