Skip to main content

Hi All,

Sorry for the late response and recreating the  topic. The solution provide did to work as the heading info is no been added to the file. Not sure if this is because of the way I created the flows.   The file are received/collected from the FTP server and place into the folder on my server. Please would some assist with a possible solution.
 
Thank you

 

If I understand you correctly, you have an SFTP or FTP connector that acts in a client capacity (not the SFTPServer or FTPServer connector) to download files from an SFTP/FTP server on a scheduled basis. It is possible to configure a single connector to download files from one of multiple paths on the destination server - either because the Download Remote Path contains a list of multiple paths to retrieve from in a comma separated list:

 

or because the Advanced->Recurse Remote Subdirectories heading is configured:

 

 

Which allows the entire subtree of the Remote Path to be explored for files. Messages that are downloaded this way will be accompanied with one or two additional headers on the message:

 


The Subfolder header is present on any file downloaded using the Recurse remote subdirectories option, and includes the subfolder that the file was downloaded from relative to the Remote Path specified. The subfolder header can be used to preserve relative path information in files that interact with file systems or network protocols that use folder structures (File, SFTP, FTP):

https://cdn.cdata.com/help/AZJ/mft/SFTP.html#subfolder-headers

 

The RemotePath header will include the full server path that the file was downloaded from relative to the server, and is returned in either case (when multiple download paths are specified, this is the only way to confirm what path the files were picked up from
.

Either or both of these header can also be queried from the Branch connector to use to flow files that are picked up from different folders into separate processing pathways.


Please note that RemotePath was only added in later releases of CData Arc, so if you do not see this header, you may be on a release before this metadata header was added.


If this is still unclear, please open this as a query in our support queue by opening a request to [email protected]. If you have a flow that you have been working on, you can include it as an attachment with your submission.