diff --git a/docs/tutorials/connectors/FTP/SFTP/FTP_connector.md b/docs/tutorials/connectors/FTP/SFTP/FTP_connector.md index f9d4e2bfed931bdf4417226136fed9b3cc1cbe10..29ab79b7877537b4cd62c422d1d8b9cb44440606 100644 --- a/docs/tutorials/connectors/FTP/SFTP/FTP_connector.md +++ b/docs/tutorials/connectors/FTP/SFTP/FTP_connector.md @@ -1,19 +1,37 @@ # FTP/SFTP Connector + This connector can be used for an FTP connection as well as an SFTP connection. The difference between the two is port numbers: 21 for FTP and 22 for SFTP. This is determined by the FTP server you're connecting to. # Requirements + * A FTP or SFTP server's settings * Hostname * User credentials * Port number - * Directory path for delivery, if not to the root directory + * Directory path on the FTP/SFTP server for delivery, if not to the root directory * A local directory on the Secure Agent you are creating the mapping on. If your team does not have a folder dedicated for your work, you can reach out to the [Integration Team](mailto:integration-platform@doit.wisc.edu) to request one, however using the /tmp directory works fine for this Connector as the file isn't retained on the Secure Agent after successful completion. - # Connector +1) In Administrator > Connections, select "New Connection in the upper right corner of your browser. +2) Make sure to fill out these settings: + - Name: Please follow our [naming guidelines](/docs/best-practices/naming.md). + - Type: FTP/SFTP + - Runtime Environment: The Secure Agent you typically use. + - User Name: The user created for you on the FTP/SFTP server. + - Password: The above user's password. + - Host: The FTP/SFTP server hostname + - Port: This will toggle to either 21 or 22, depending on if you select "This is a secure FTP connection". The FTP/SFTP server administrator should give this information to you with the hostname and credentials. + - Local Directory: This is either /tmp or the folder path provided to you by the Integration Team after you've requested a team folder from them. + - Remote Directory: If delivering to the root of the file structure on the FTP/SFTP server, you will need to input "/" in this field. If you are delivering to a specific directory on the server, you will need to lead with the "/" (for example: /UAT/data). + - Code Page: The most commonly used format is UTF-8, so we recommend this unless the FTP/SFTP administrators or platform consuming this data requires something else. + + + # Mapping + + # References * [IICS KB on the FTP/SFTP Connector](https://docs.informatica.com/integration-cloud/data-integration/current-version/data-integration-connections/ftp-sftp-connections.html) \ No newline at end of file diff --git a/docs/tutorials/connectors/FTP/SFTP/SSH_key_file_processor.md b/docs/tutorials/connectors/FTP/SFTP/SSH_key_file_processor.md index a148a348dba4dfa65353b008830e564618fab2cc..d90fe403f52f6893077fb428c77aef3b3a428cbd 100644 --- a/docs/tutorials/connectors/FTP/SFTP/SSH_key_file_processor.md +++ b/docs/tutorials/connectors/FTP/SFTP/SSH_key_file_processor.md @@ -1,5 +1,7 @@ # SSH Keypair authentication SFTP mapping using File Processor Connector +This style of file syncing for an SFTP source or target is used if SSH keypair authentication is required. This can be with or without a passphrase on the keypair. Either the Integration Team can create the SSH keypair for you on the Secure Agent, or you can provide private key to the Integration Team to place on the Secure Agent. + # Requirements # Connector diff --git a/images/sftp_settings.png b/images/sftp_settings.png new file mode 100644 index 0000000000000000000000000000000000000000..dede3c74d4c5552e715538e72fe234682a11dd81 Binary files /dev/null and b/images/sftp_settings.png differ