Configure a Job Action that Transfers Files

Use this procedure to configure automated file transfer between servers. The source server can be the scanned server or a server that received files from a previous action. The destination can be a different server or a different directory on the same server.

To configure a Job action that transfers files

Create a Job and specify the scan server and directory.
On the New Job (or Edit Job) page, under Actions, from the Add action... list, select Transfer file.

This opens the Transfer File dialog box.
(Optional) Select Move if you want to delete files from the source location after the transfer.
(Optional) Select Preserve file attributes if you want the modification date and time on the destination server to match the source. When this option is not selected, the destination file’s timestamp shows the date and time of the transfer.
Configure the source server:
- For From, select the source server from the list of available servers. If this is the initial transfer, select the scanned server.
- Enter an expression to describe the files to transfer. For most transfers, use $SCANNED_PATH$/$RELATIVE_FILE_NAME$ (the default) for the initial transfer. This will transfer all updated files on the scanned server that meet your filter criteria. If the scan is recursive, this option will also include all subdirectories in that directory. For subsequent transfers, replace $SCANNED_PATH$ with the correct actual path for the files on the server you are transferring from.
Configure the destination server:
- For To, select the destination server.
  
  NOTE:If File Server groups have been configured by a Reflection Gateway administrator, the list of servers available to you is determined by your membership in one or more File Server groups.
- Enter an expression to identify the location and naming pattern you want to use for files on the destination server. The expression you enter for destination files can use a combination of text and tokens. For details, see Entering Expressions for Destination Files below.
Click OK to close the Transfer File dialog box.
Click Save.
Click Run Now to test the transfer. (If this is a repeat test, first update the files in the source location.)

Entering Expressions for Destination Files

The expression you enter for destination files in the Transfer File dialog box can use a combination of text and tokens. Refer to the examples below to understand how Reflection Gateway interprets these expressions. Note the following:

UserID in these descriptions is the user whose UserID is configured for authentication to the destination SFTP server. (See New/Edit SFTP Server.) Any destination location you specify must be accessible to this user.
If the destination server is a Reflection for Secure IT Server for Windows, specify destination paths using the virtual directory names that have been made accessible to UserID, not the actual physical directories on the server. (Virtual directory access is configured using the console’s SFTP Directories pane.)
If the destination server is a Reflection for Secure IT Server for UNIX (or other UNIX server), specify actual physical paths; UNIX servers do not use virtual directories.
Use forward slashes (/) for specifying paths on both Windows and UNIX servers.

Destination Expression	Output on Destination Server
$RELATIVE_FILE_NAME$ (the default)	Files are created in UserID’s SFTP login directory. The token is replaced by the relative path and filename of each file on the scanned server. If the scan is recursive, subdirectories that don’t yet exist are created in the login directory. If the scan is not recursive, files in subdirectories are not transferred, and this token is equivalent to $FILENAME$.
$FILENAME$	Files are created in UserID’s SFTP login directory. The token is replaced by the filename of each file on the scanned server. If the scan is recursive, files are not transferred to subdirectories. All files–including those in subdirectories on the scanned server– are transferred to the SFTP login directory.
upload/$RELATIVE_FILE_NAME$	Files are created in a subdirectory called upload in UserID’s SFTP login directory. If this directory does not exist, it is created. If the scan is recursive, subdirectories are created in the upload directory.
/upload/$RELATIVE_FILE_NAME$	Files are created in a directory called upload in the root directory. UserID must have write access to this directory. In most cases, the upload directory must already exist: If the server is a Reflection for Secure IT Server for Windows, it is not possible for any user to create a new directory in the root directory. UserID must have access to a virtual directory called upload that is mapped to an existing physical directory. If the server is a UNIX server, creating a new directory at the root level is only possible if UserID has root privileges (not recommended).
$JOB_ID$-$FILENAME$	Files are created in UserID’s SFTP login directory. Filenames use the Job ID followed by a hyphen and the filename of the file on the scanned server. NOTE:Don’t prepend text or tokens if you use $RELATIVE_FILE_NAME$ with a recursive transfer. Doing this will change both filenames and directory names.