====== SFTP Server send channel ======

The SFTP Server send channel allows you to interact with a message basket using the SFTP protocol.
The server send channel allows you to retrieve messages from the message basket (outgoing).

==== Properties ====

^Name  ^Meaning|
|//Name//|Name of the communication channel.|
|//Channeltype//|Re-list the type. (For verification)|
|//communication direction//|Preferably incoming.|
|//Messagebox //|Messagebox for incoming messages //(incoming)///, must be selected in the corresponding lookup table.|
|//Preset Sender//|Here you can assign a fixed sender, which is intended for this channel..|
|//Preset Recipient//|Here you can assign a fixed receiver, which is intended for this channel.|
|//Validation of the sender//|checks the sender address of the Interchanges for certain EDI subscribers, if they do not contain the specified subscriber, the message is entered with an error message in the inbound message basket and a corresponding report is generated (only if Required). The test method is selected by means of a combo box (None, Optional, Required, Fixed partner).|
|//Validation of the receipient//|checks the recipient address of the Interchanges for certain EDI subscribers, if they do not contain the specified subscriber, the message is placed in the message basket with an error message and a corresponding report is generated (only if required). The test method is selected by means of a combo box (None, Optional, Required, Fixed partner).|
|//Public//|By checking the check mark, the communication channel can be used for all subnodes. However, if a communication channel with the same name is created in the subnode, the communication channel of the subnode is used.|
|//Repetitions in case of errors//|If an error occurs, the number of consecutive reception attempts is determined by entering a value in the corresponding field.|
|//Automatic Unzipping//|Documents or attachments are automatically unzipped using the procedure selected in the combo box.|
|//Username//|User name of the standard user e. g. //root//.|
|//Password//|Password of the default user|

==== Properties (enhanced) ====


^Name  ^Bedeutung  |
|//certificate//|Path to the private certificate / key to authenticate the server.|
|//Subject of the certificate//|Subject of the private certificate|
|//Password of the certificate//|Password of the private certificate|
|//Timeout//|Specify a time in seconds until a timeout occurs|
|//client certificate//|Path to the public certificate|
|//Fingerprint of the client certificate//|Fingerprint of the client certificate|
|//Timeout//|Timeout, -1 is no timeout|
|//Use sub node addresses//|Use also trading partner logins from sub nodes|
|//Output Trace//|Increases the trace level during message processing by the communication channel to //Debug//. \\ In this way, a more detailed error or process log can be created.|
|//Logfile//|The relative or absolute file name for the log. A log file is created for each sftp session. Placeholders from FilenameMask can be used by the Containerizer as long as they do not access message content (such as ${MessageBox}, ${MessageDirection},...). Other possible placeholders are ${RemoteIP}, ${ChannelLoginName} and ${ChannelName}. For example:.\Log\sftp\${ShortDateStamp}\${RemoteIPAddress}\${TimeStamp}_${RemoteIPAddress}_${RemoteIPPort}-${ChannelName}_Login-${ChannelLoginName}.log\\ \\ It is possible to format the parameters, but without blanks, e. g.:\\ \\  .\Log\sftp\${ShortDateStamp}\${TimeStamp}${ChannelName:-$0}${RemoteIPAddress:-IP($0)}${RemoteIPPort:_Port($0)}${ChannelLoginName:_Login-$0}.log|