+

SFTP Send Endpoint Settings

SFTP send endpoint settings configure where to send B2B messages transmitted over SFTP. There are two types of SFTP 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 SFTP Send to Partners endpoints.

  • Target at Host

    Target endpoint in an inbound message flow through which transformed JSON and XML messages are sent to the backend applications.

    Only a host can own SFTP Target at Host endpoints.

Create SFTP 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

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

x

Port

Port number of the SFTP.

x

Username

Username for the SFTP server.

x

Password

Password for the SFTP server.

x

Target Path

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

x

Filename pattern

Filename pattern required by your partner or backend application.

Was this article helpful?

💙 Thanks for your feedback!

Edit on GitHub