Specifying files and folders

Specify files so that they can be identified by the local machine. The name can be a file or a folder. Mapped drives cannot be used. The file names are the absolute path to the machine for both local and remote.

These rules apply if the source or destination location is a file or a folder:
  • If the source is a folder, then all sub-folders and files inside the folder are transferred.
  • If a source folder does not exist, it will not be created and an error message will be sent.
  • To create a new destination folder, add a backslash at the end of the file path.

    For example, C:\TestingDirectories\FTP\DestinationFolder\.

    By adding a backslash, a new folder called DestinationFolder will be created in the FTP folder.

  • If a source is a file and the destination file name is different than the source file, the source file name will be changed to the destination name during the transfer.
  • Front or back slashes can be used in file paths.
  • Both absolute and relative paths are supported.
  • UNC names are not supported.
These rules apply if wildcards are used:
  • If a source is a folder or the file name contains a wildcard, the destination cannot be a file.
  • Wildcards are specified using the asterisk character.
  • If a wild card is used in the source file name, all files and folders matching the name are transferred. The destination cannot be a file.
  • If the source contains a wildcard (or is a folder), the destination must exist. If it does not exist, an error message is displayed. The destination cannot be a file.
These are some examples of supported file paths or names:
  • file://home/UserName/UserDir/File.txt file://home/UserName/UserDir/File.txt
  • file:///C:/Documents and Settings/File.txt
  • file://///HostName/ShareLocation/ShareFile.txt
  • /home/UserName/UserDir/File.txt
These file paths or names are not supported:
  • <MappedDrive>:\program files\UserDir\File.txt
  • <MappedDrive>:/program files/UserDir/File.txt
  • <server>/c$/program files/UserDir/File.txt
Note: 
  • FTP Node completes successfully if rules are applied but no files are transferred when using a wildcard.
  • If no files exist using wildcard pattern matching, therefore there are no files to transfer, all files have been transferred successfully. This is applicable only if the source and destination both remote, for local to remote and remote to local, it would fail with an error.
  • Designate a folder with a trailing slash. For example:
    • /ThisIsAFile
    • /ThisIsAFolder/
  • A file name matching a folder name or vice versa cannot exist within the same folder.