Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Help

Basic FTP Transport

The Basic FTP Transport Provider allows you to receive messages in the form of files from a specified FTP directory, and similarly send messages as outgoing files, with minimal configuration.

The Receive Transport Provider requires you to configure the FTP URL, FTP Username, FTP Password and the wildcard filter (specifying the files to retrieve from the server).  You can also set whether the transfer is ASCII or binary.  The Username can be left empty for anonymous access.

Context properties ReceivePath, FileName, and ReceiveLocationType are all set on incoming Messages.

The Send Transport Provider is similar but requires you to configure the output file name (which can include tokens from the Message Context surrounded by % characters, e.g. 
%MessageID%), plus whether to write to a temporary file and then rename on completion (to prevent other processes from picking up a partially written file), and whether to append to or replace any existing file.

If you require more control over the connection settings, or you wish to use a secure or HTTP protocol for the transfer, please use the Advanced FTP Transport Provider.