Creating FTP Source Activity

FTP Source activity enables you to define the name and path of the source file located at FTP server, which is to be later transferred to the target location. On execution of the process flow, FTP Source activity enable Adeptia Server to fetch this source file from the specified FTP location.

Prerequisites

If you are using SSL FTP Server then you need to validate it by importing certificates. For information on how to create Keystore and import certificates, refer to Creating Keystore.

Steps to create FTP Source Activity

1. Go to Develop > Services > Source > FTP. 

   Open

   

2. Click Create New.
   
   
   

   Open

   

   
   
   
   

3. Type the name and the description for FTP Source in the Name and Description text boxes respectively.

4. Type the host name/IP address and port of the FTP Server in the Host Name and Port text boxes respectively.

5. Type the username in the User ID text box.

6. Type the password, if required, in the Password text box. Then re-enter the password in the Confirm Password text box.

7. Type the path of source file in the Remote File Path text box. This file path specifies the location of the source directory where the file is located.

8. Type the name of the source file in the File Name text box. 

9. Select the transfer mode from the Transfer Mode drop-down list box. This option is used to specify the mode in which the source file is transferred to/from FTP server. The file can be transferred either in Binary or in ASCII format. 

10. Select the transfer type from the Transfer Type drop-down list box. The available options are:
    
    

    • Passive

    • Active

11. Select SFTP check box, if the FTP Server specified in the Host Name text box is an FTP Server over SSH. Select the key manager from the Key Manager drop-down list box.

12. Select FTPS check box, if the FTP Server specified in the Host Name text box is an FTP Server over TLS/SSL. Do the following:
     

    1. Select FTPS mode from the FTPS Mode drop-down list box. The available options are Explicit and Implicit.  Select FTPS mode with respect to FTP Server you are accessing.

    2. Protection Level: It is a single Telnet character code specifying the data channel protection level. This command indicates server what type of data channel protection the client and server will be using. The default protection level is None. The available options are:

       • None

       • Clear: This protection level indicates that the data channel will carry the raw data of the file transfer with no security applied

       • Private: This protection level indicates data will be confidentially protected

13. Select Validate Server check box, if you want Adeptia Suite to authenticate FTP server and subsequently validate the certificate sent by FTPS server against the certificate imported in Keystore. This certificate is required to authenticate the trusted FTP server. Do the following:

    1. Select a keystore activity from the Keystore Name drop-down list box.

14. Expand Advanced Properties.
    
    
    

    Open

    

    
    
    
    

15. Select Delete File on Success check box, if you want to delete the FTP source file after successful execution of the process flow. In case, the process flow is aborted due to any reason, the source file will not be deleted.

16. The Connector drop-down lists the APIs to connect to the FTP Server. The options changes as per your selection of the protocols that you want to use to establish FTP connection. 

17. Select Verbose check box, if you want to create a log file of your FTP activity. This check box is enabled only if you select Secure Inet Factory from the Connector drop-down list box.

18. Set the time limit (in seconds) in the Data Timeout text box to end the infinite loop with no output. At times, when Adeptia Suite is connected with FTP server, there could be connectivity issues. This could result in an infinite loop with no output. This issue can be resolved by setting a time limit if no data is transferred between Adeptia and FTP servers. By default, this is set to 60 seconds. This implies that if there is no data transfer for 60 seconds between both the servers, the connection is considered broken and an error message is displayed.
    
    
    

19. Click Save.