Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Overview
Contains multiple Smart Services for interacting with a remote file server via SFTP, FTP, or SCP. Using these services, an Appian application can be configured to send and receive files, folders, and metadata in a process. Features support for zlib compression.
Key Features & Functionality
Smart Services included:
Functions:
how to Appian SFTP Plug-in has ability to connect to the sftp server using the ssh keys for authentication?
How to reference ssh key in third party credentials
Has this problem been solved?
We are getting errors as follows after upgrading to 4.1.1 version
Error copying the Appian document to the remote server. See application server log for more details. Error Message: /fftssvt1/Linoma_Software/GoAnywhere_Services/userdata/webdocs/filepath/env/filname.csv (Not a directory).
Error copying the Appian document to the remote server. See application server log for more details. Error Message: Permission denied.
We are using private key configuration to connect to the FFTS server. Please advise what change is required to resume the process.
Does send file over SFTP support sending a zipped folder as the file?
Hi All, SFTP file server can be accessed through an SSH key pair ?
Can you please provide us the details.
Thanks,
Gaurav
Which version of the commons-lang is it ? Is it 3-3.18.0 ?
Hi Mike, I am not sure if anything can be changed in the configurations at Appian's end to resolve this. We discovered that upgrading the host servers resolved it. In our case it was SFG servers.