Skip to Content

FTP connector for Jitterbit Integration Studio

Summary

The FTP connector provides an interface for entering user-provided input such as a host and port to create an FTP connection. That connection provides the foundation to configure associated FTP connector activities that interact with the connection. Together, a specific FTP connection and its activities are referred to as a FTP endpoint.

Connector overview

This connector is used to first configure an FTP connection, establishing access to an FTP server, and then used to configure one or more FTP activities associated with that connection as a source or target within an operation or script:

  • Read: Reads data from an FTP endpoint and is intended to be used as a source in an operation or called in a script.
  • Write: Writes data to an FTP endpoint and is intended to be used as a target in an operation or called in a script.

Note

This connector is a native Integration Studio connector, which may be referred to by Jitterbit when communicating changes made to connectors. The release schedule for native Integration Studio connectors is based on the cadence of Harmony portal web applications.

Accessing the connector

The FTP connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

FTP activities

Connecting to SFTP with ssh keys

SSH client keys are used to authenticate Harmony with external resources such as SFTP servers.

For detailed information on using SSH client keys specifically for SFTP connections, and how to convert keys to an appropriate format for Jitterbit private agents, see Connecting to SFTP with ssh keys.

Troubleshooting

If you experience issues with the FTP connector, these troubleshooting steps are recommended:

  1. Ensure the FTP connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can check the agent logs for more information.

  5. For additional troubleshooting considerations, see Operation troubleshooting.

Additional resources

The following Jitterbit microlearning tutorials are available through our Jitterbit basics video series, created by Jitterbit University: