Performing FTP Transfers

These examples show the Client File Name, the Server File Name, and the Virtual Alias parameters that are set in a transfer definition from TIBCO MFT Internet Server and how they are resolved during an FTP transaction.

Assume that there is a directory called c:\test1 (client file name) on the client’s side containing file1.txt and file2.txt. The client will perform an FTP Upload (put) and FTP Download (get) to and from the MFT FTP server on 192.168.222.222. There is a directory called c:\test2 on TIBCO MFT Internet Server (server file name) that contains file3.txt and file4.txt. The transfer will be done using a user ID of user1.

Two transfer definitions should be created for the user1 user to perform these FTP transactions: one for Upload and one for Download. As stated earlier, both files should point to the same c:\test2 directory on the server side where the files will be transferred to and from. Also, this directory must be assigned the same Virtual Alias parameter value in both the upload and the download file transfer definitions. For this example, the virtual alias will be /FtpFiles.

Procedure

  1. The user1 user performs an FTP login from the client side c:\test1 directory onto MFT FTP server on 192.168.222.222. The user1 user will see the following welcome message configured on the MFT server. 
    C:\test1>ftp 192.168.222.222
Connected to 192.168.222.222.
220-TIBCI MFT FTP Server (v. 7.2.1)
220 This is the MFT Server 7.2.1 on 192.168.222.222 Welcome!
User (192.168.222.222:(none)): user1
331 Password required for user1
Password: ************
230 Logon OK. Proceed.
  2. The user1 user is able to see the list of files available for the Upload and Download transactions according to file transfer definitions. 
    ftp> dir
drwx------    user11  user1              0 Oct 13 09:56 FtpFiles
d-wx------    user11  user1              0 Oct 13 09:56 F41310000001
dr-x------    user11  user1              0 Oct 13 09:56 F41310000002
    The FTPFiles directory is a Virtual Alias parameter value which corresponds to the c:\test2 server directory.
    Note: Files named F41380000001 and F41380000002 are examples of an error condition. They are shown here as an example of what the user may see when no Virtual Alias parameter is configured in the transfer definition. They are the actual file IDs which The user1 user will see if no Virtual Alias parameter was configured for upload (F41380000001) or download (F41380000002) file transfer definitions. The correct configuration FtpFiles is used for this example of the FTP transaction.
  3. The user1 user performs a listing of the /FtpFiles directory in order to see the files available for transfer. 
    ftp> cd FtpFiles
ftp> dir
150 Opening data connection for file list.
-rwx------    user11  user1          79005 Apr 15 14:25 file3.txt
-rwx------    user11  user1         702188 Apr 15 14:42 file4.txt
  4. The user1 user performs an Upload (put) of the file file1.txt from current directory c:\test1 on the client side to the /FtpFiles directory on the server side, and then checks that the file was uploaded by listing the /FtpFile directory again. 
    ftp> put file1.txt
200 PORT command successful.
150 Opening data connection for FtpFiles
226 Transfer successful. AuditID=A41310000001
ftp: 40705 bytes sent in 0.00Seconds 40705000.00Kbytes/sec.
ftp> dir
-rwx------ user11 user1 40705 Apr 13 09:57 file1.txt
-rwx------ user11 user1 79005 Apr 15 14:25 file3.txt
-rwx------ user11 user1 702188 Apr 15 14:42 file4.txt
  5. The user1 user performs Download (get) of the file3.txt down to the client side. 
    ftp> get file3.txt
150 Opening data connection for file file3.txt (79005)
226 Transfer successful. AuditID=A41310000002
ftp: 79005 bytes received in 0.88Seconds 90.29Kbytes/sec.