Copy/Move (Push) File to Host Action

You can configure EFT to copy or move (also known as "offload") files to a specific location using a particular protocol whenever certain Events occur, such as when a report is created. You must provide EFT with connection information (protocol and login details) and file information (source path and destination path).

The Copy/Move Action can be applied to all File System Events; the User Events "User Quota Exceeded," "User Logged In," and "User Logged Out"; and the Server Events "Timer" and "Log Rotated."

Refer to Connection Profiles for details of setting up a Connection Profile before defining the Action.

To configure EFT to copy/move files

  1. Follow the procedure in Creating Event Rules, or select the Rule to which you want to add the Action. For example, create a Scheduler (Timer) Event.

  2. In the right pane, in the Actions list, double-click Copy/Move (push) file to host.

  3. In the Rule Builder, click Copy to toggle between Copy and Move to choose the Action you want for this Rule.

  4. In the Rule Builder, click one of the undefined parameters (e.g., '/%SOURCE.FILE_NAME%').

    The Offload Action Wizard appears.

  5. In the Connection Profile box, specify a connection profile for this Event. If none is specified, you will need to configure the Connection details as described below.

  6. On the Offload method box, specify a protocol type for the connection: Local (Local File or LAN), FTP (standard File Transfer Protocol), FTP SSL/TLS (AUTH TLS), FTP with SSL (Explicit encryption), FTP with SSL (Implicit encryption), SFTP using SSH2 (Secure Shell), HTTP (HyperText Transfer Protocol), HTTPS (Secure HTTP access), Accelerated Secure Transfer.

  7. (Optional) If you selected Local (Local Files or LAN), under Optional credentials override, provide the Windows account username and Password for connecting to remote shares (not local folders).

    Think of Local Transfer as an operation (offload or download) with a remote server.

    Think of "Optional credentials override") as "credentials to access remote server."

    For download action, it is "credentials for source folder."

    For copy/move (offload ), it is "credentials for destination folder."

     

    "Credentials to access local folder" ("source" for offload and "dest" for download) is Event Rule execution context (EFT account, or Folder Monitor account for FM rules, or Connected Client account for client-originated rules on an AD site):

    • Offload: local (EFT) => remote ("override credentials")

    • Download: local (EFT) <= remote ("override credentials")

    TEST1: Offloads file from "local" Share A (access as EFT account, i.e., X) to "remote" folder B (access as Y) => Fails, as X has no permissions on A.

    TEST2: Downloads file from "remote" Share A (access as Y) to "local" folder B (access as EFT account, i.e., X) => Succeeds, as Y has permissions on A and X has permissions on B.

  8. If you chose anything but Local do the following; if you chose Local, skip to the Source File Path page step.

    1. In the Host address box, type the IP address.

    2. The Port number for the selected protocol changes automatically based on the offload method. Provide a different port number, if necessary.

    3. Provide the Username and Password needed to establish the connection.

  9. Select the Use connected client's login credentials to authenticate check box if you want to use the local system account to authenticate. The availability of this check box is controlled on the Site's Security tab by the Persist username and password credentials for use in Event Rule context variables check box.

  10. If you chose SFTP, provide the client SFTP certificate information.

  11. If you chose a protocol that uses SSL (FTPS or HTTPS), provide the client and remote server's SSL certificate information.

  12. If you are connecting to a remote host through a SOCKS server, click SOCKS and provide the SOCKS connection information.

  13. If you are connecting to a remote host through a proxy, click Proxy. Provide the proxy connection information.

  14. To specify transfer options and time stamps, in the Offload wizard, click Advanced. Specify the advanced transfer options.

  15. (optional) To define commands to occur before and after this operation, click Pre/Post.

  16. In the Pre/post commands dialog box, you can specify one of the following operations to occur before and after the Copy/Move Action.

  17. Click Next. The Source File Path page appears.

  18. In the Source path box, provide the path to the file(s) that you want to offload. (No validation is performed.) For example, type:

    C:\Staging\*.dat or \\mydomain\common\jsmith\file.txt

    You can leave Source path blank or use %FS.PATH% to offload the files associated with the Event that triggered the Action. In a Timer Event, there is no context variable available for the path, so you must specify a filename.

  19. Select the Delete source file after it has been offloaded check box if you want to delete the file after it is copied/moved. (If the file is marked read-only, it will not be deleted.)

  20. Select the If the source file is missing treat as success check box if you want the Action to be considered successful even if the source file is missing.

  21. Click Next. The Destination File Path page appears.

  22. In the Destination path box, specify the location in which to save the offloaded file. (No validation is performed when you type a path; the Folder icon is only available for local transfers.)

    If you type a path to a folder that does not exist, the Event Rule will fail. Be sure you have the path defined correctly, e.g., make sure to use the proper slash. In general, forward slashes / are used in remote paths, and backward slashes \ are used in local Windows paths. Do not use both.

  23. Click Finish then click Apply to save the changes on EFT and/or add other Actions and Conditions to the Rule.

    If you are copying or moving the file to another location, and the file upload is a regularly occurring Event with a file of the same name, in the Offload Action wizard, add the variables %EVENT.DATESTAMP% and/or %EVENT.TIMESTAMP% to the path so that the date (YYYYMMDD) and/or time (HHMMSS) are added to the filename when it is moved/copied. Do not use %EVENT.TIME%, because the colon (e.g., 28 Aug 07 10:01:56) makes it unsuitable for file naming.

    For example, in the Offload Action wizard, in the Destination path box, provide the path and variables. For example, type:

    C:\Documents and Settings\Administrator\My Documents\upload\%EVENT.DATESTAMP%_%EVENT.TIMESTAMP%_%FS.FILE_NAME%

    With this path and variables, when a file is uploaded to the monitored folder, the file is moved to \My Documents\upload and the date and time are prepended to the filename. For example, 20080422_101212_mydailyprogress.doc.

Related Topics