You create a receiver FTP adapter to save XML messages from the Integration Server/PCK in files on an FTP server.
To use FTPS (File Transfer Protocol using SSL/TLS), the following prerequisites must be met:
The CA certificate used to sign the server certificate must be added to the TrustedCAs keystore view.
More information: How to Use Key Storage
The use of FTPS follows the specification RFC 4217.
If you want to convert an XML document to a text file, select File Content Conversion and make the required entries for conversion under Content Conversion Parameters (see below).
This selection is not available in the PCK.
Define File Access Parameters
You can enter variables for the target directory. The variables can relate to elements in the XML schema of the payload or to attributes in the message header.
More information: Defining Variable Substitution for Target Directory/File Name
If the indicator is not set and the target directory does not exist, the adapter returns an error.
You can enter variables for the file name scheme.
More information: Defining Variable Substitution for Target Directory/File Name
Define FTP and FTPS Connection Parameters
Only change this setting if you have a specific reason. In passive mode, the client establishes a data connection to the port required by the server.
The FTP control connection is protected using TLS/SSL (Transport Layer Security (BC-SEC)/Secure Sockets Layer). File transfer is unencrypted.
All communication with the FTP server is encrypted using TLS/SSL.
If you have selected FTPS for Connection Security, enter the following details:
Retain the default setting. Only adjust the Command Order to match those expected by the FTP server if you encounter problems with the FTP connection. For information about the correct setting, see the documentation for the FTP server.
The corresponding key/certificate pair must be saved in a keystore view of the AS Java.
Otherwise, enter the User Name and Password that are valid for the FTP server, and confirm.
Define Processing Parameters
The file is created. The document received last is saved in each case.
If you want the created file to be overwritten, select Overwrite Existing File. If you do not set the indicator, processing is stopped until the created file is processed.
You can only set the indicator if you select Use Temporary File under Put File below.
The file is written when the inbound documents are appended.
A new file is created for each document. A time stamp with the format yyyyMMdd-HHmmss-SSS is added to the file name. The time stamp is added as the last part of the name before the extension.
This mode guarantees that no file is overwritten. In this way, files that originate from the same adapter configuration can be sorted.
A new file is created for each document. The message ID generated by the Integration Server/PCK is added to the file name. The ID has the format: xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx .
The message ID is added as the last part of the name before the extension. This mode guarantees that no file is overwritten.
A new file is created for each document. A counter, which is inserted before the file name extension, is added to the file name (for example, default002.file ).
Specify the following for Counter Definition:
Specify one or more characters that you want to add before the counter in the file name.
Specify the first counter to be used. It must be a valid integer number. Leading zeros are permitted.
Specify the counter increment.
Specify when the counter is to be added.
If you select After First File , the counter is added when the file name is first used unchanged.
If you select Immediately , the counter is added with the first inbound document.
This option is available only if you select the Transport Protocol as File System (NFS) .
This selection is not available for the File Construction Mode Append .
An empty file (length 0 bytes) is put in the target directory.
No file is put in the target directory.
Under File Encoding, specify a code page.
The default setting is to use the system code page that is specific to the configuration of the installed operating system. The content of the message is converted to the corresponding code page before the message is saved as a file.
You should use this conversion only for plain text and not for XML documents. If you want to change the encoding of an XML document, then select the File Type as Binary and apply XMLAnonymizerBean as an additional module in the Module tab page.
Permitted values for the code page are the existing charsets of the Java runtime. According to the SUN specification for the Java runtime, at least the following standard character sets must be supported:
Seven-bit ASCII, also known as ISO646-US, or Basic Latin block of the Unicode character set
ISO character set for Western European languages (Latin Alphabet No. 1), also known as ISO-LATIN-1
16-bit Unicode character format, big-endian byte order
16-bit Unicode character format, little-endian byte order
Check which other character sets are supported in the documentation for your Java runtime implementation.
Define Operating System Commands
More information: Defining Operating System Commands Before/After Processing
Define Content Conversion Parameters
Select the Content Conversion tab page.
More information: Converting XML in the Receiver File/FTP Adapter to Text Format
Define Variable Substitution for Target Directory/File Name Scheme
More information: Defining Variable Substitution for Target Directory/File Name
Define Adapter-Specific Message Attributes
A configured variable substitution (see above) is performed after the attributes from the message header are applied.
If the indicator is set and the header for adapter-specific message attributes or one of the set attributes is missing from the message, this leads, in asynchronous cases, to a delivery exception in the audit log of the message. In synchronous cases, the sender of the message is notified.
If you do not set the indicator, and message attributes are missing, the adapter accesses information from the adapter configuration.
To evaluate the following attributes in the PI message header, set the corresponding indicators:
You can only set this indicator if the target file is written using a temporary file.
The attribute namespace for the adapter is http://sap.com/xi/XI/System/File .
Define the Adapter Status
Define Additional Parameters in Advanced Mode
Specify the additional parameter names and parameter values in the table.
Additional parameters are published in SAP Note 801926 .