Please enable JavaScript to view this site.

Altova FlowForce Server 2020 

The /system/ftp container includes functions used to perform FTP operations on a remote FTP server.

 

Paths in FTP functions

Some FTP functions have a Working Directory parameter. This parameter is common to many FlowForce functions. If you set the Working Directory, remember that all local paths supplied as parameters to FTP function must be relative, not absolute. For example, when uploading a file, you can enter C:\Upload as Working Directory and file.txt as Source file. The final source path will become C:\Upload\file.txt.

 

In addition, some FTP functions have a Directory on host parameter that plays the same role as Working Directory, on the remote FTP server. Therefore, if you set the Directory on host, all remote paths supplied as parameters to the FTP function must be relative, not absolute. For example, when uploading a file, you can enter uploads as Directory on host and file.csv as Target file. The final target path will become /uploads/file.csv.

 

This is also important if you configured jobs as File System Triggers or HTTP Triggers. Such jobs have a triggerfile parameter that supplies the path of the file that triggered the job. If you intend to use the triggerfile parameter in any FTP function, remember that its path is absolute.

 

To obtain the file name with extension from the triggerfile, use the following FlowForce expression:

 

 {filename-with-extension(triggerfile)}

 

For an example, see the FTP store function.

© 2019 Altova GmbH