SFTP Sending - “Parameters” -> “Advanced”

In this section, the adapter-specific parameters and the adapter channel status are defined.

“Adapter-Specific Message Properties”

The adapter-specific properties are:

Set Adapter-Specific Message Properties: Enables the use of other related indicators. These indicators are used to insert in the message header the corresponding information that can not be known until the runtime.

File Name: Name of the read file. Technical name of the “FileName” property, namespace: “http://sap.com/xi/XI/System/File”.

Directory: Directory path containing the file. Technical name of the “Directory” property, namespace: “http://sap.com/xi/XI/System/File”.

File Type: Read file type (binary or text). Technical name of the “FileType” property, namespace: “http://sap.com/xi/XI/System/File”.

File Encoding (only if File Type is selected): Encoding of the read file. Technical name of the “FileEncoding” property, namespace: “http://sap.com/xi/XI/System/File”.

Source File Size: Data size in bytes of the read file. Technical name of the “SourceFileSize” property, namespace: “http://sap.com/xi/XI/System/File”.

Source File Timestamp: Timestamp of the moment of the file reading. Technical name of the “SourceFileTimestamp” property, namespace: “http://sap.com/xi/XI/System/File”.

Source SFTP Host: Name or IP of the source SFTP server. Technical name of the “SourceSFTPHost” property, namespace: “http://sap.com/xi/XI/System/File”.

“Adapter Status”

Status: Allows to disable the adapter completely, so it cannot be activated in the runtime workbench. Two possible values:

• Active

• Inactive

“File Splitting EOIO Proccessing of Large Binary Files”

The option to split files for an organized delivery or Chunk Mode, it is only available for a QoS of EOIO type.

Selecting a QoS of EOIO type, a new section called “File Splitting” will be shown in the Advanced tab.

Activating this option, a drop-down box will be shown to select the size of each part forming the message. For each file part processed, a new message is generated which will be included in the queue defined for the EOIO flow.

It is important to highlight that being message parts and not the complete message, the payload cannot be accessed to do any kind of conversion and the file will be processed as a binary type file.