====== FTP server receive channel ======

The FTP server receiving channel enables the connection to services that communicate via FTP protocol. eBiss acts as a server.
The receive channel allows you to place messages in the specified message basket (incoming).

{{:images:sign_warning.png?nolink|}}**Note:** FTP Server Receive channel is part of one of the licensed [[en:ueberblick:ebiss_module:start]].

==== 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.|

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

^Name  ^Meaning|
|//Data port//|FTP data port (preferably 20).|
|//Username//|Login of the FTP directory.|
|//Password//|Password of the FTP directory.|
|//SSL behavior//|How to encrypt the connection using SSL. Mode (None, Offer (=Automatic), Explicit, Implicit). In implicit mode, communication is immediately started via an encrypted channel, via another port. More often, the explicit mode is used. The connection is established via the non-encrypted standard ftp port and after the connection is established, but before authentication, it is switched to the encrypted mode.|
|//PFX file of the SSL certificate//|The client's private certificate (for client side authentication)|
|//Password file of the SSL certificate//|That to the above mentioned. Certificate associated password.|
|//Timeout//|Specification in seconds, with the value' 0' a timeout of 5 minutes is assumed by default.|
|//Use path-based addressing//|Determine the sender/receiver depending on the specified path.|
|//Set recipient address//|Assigns the path used to the receiver (' yes') or the sender (' no'). The assignment is used for subsequent partner identification if a path-based addressing is required (see above). is desired.|
|//Output Trace//| |