+

FTP Send Endpoint Settings

FTP send endpoint settings configure where to send B2B messages transmitted over FTP. There are two types of FTP send endpoints:

  • Send to Partners

    • Target endpoint in an outbound message flow through which transformed B2B messages are sent to partners, either directly or through third-party connections

    • Acknowledgement endpoint in an inbound message flow

    A host, partner, or third-party connection can own FTP Send to Partners endpoints.

  • Target at Host

    Target endpoint in an inbound message flow through which transformed B2B messages are sent to the backend applications

    Only a host can own FTP Target at Host endpoints.

Create FTP send endpoints by configuring these settings on the <host> or Partner pages. You can also create these endpoints when you configure an outbound message flow:

Name Description Required

Owner

Host, partner, or third-party connection that owns the endpoint.

x

Protocol

Protocol that the endpoint supports.

x

Endpoint Name

Automatically generated name used to identify the endpoint, which you can modify manually.

x

Description

User-supplied value that describes the purpose of the endpoint.

Host

FTP server host, such as ftp.mulesoft.com, localhost, or 192.168.0.1. The host must be accessible from your Mule environment.

x

Port

Port number of the FTP.

x

Username

Username for the FTP server.

x

Password

Password for the FTP server.

x

Target Path

Path on your FTP server to EDI files that were generated from outbound message flows. This is also the path on your FTP server for storing transformed JSON and XML files generated from inbound message flows.

x

File name pattern

Filename pattern required by your partner or backend application.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub