A special file format is generated here that represents a completely serialized Integration Engine message. This file format can be processed by the inbound file adapter in the mode XMBSTREAM2FILE. This format can be used to temporarily save complete Integration Engine messages, including all Integration Engine-specific parameters that then no longer need to be specified in the inbound file adapter.

<port_no> specifies the HTTP server port that receives the messages from the Integration Engine.

For example, if you have specified XMB.httpPort=1234 and XMB.httpService=/file/Receiver, a URL must be specified as the end point address of the file adapter in the Integration Engine, as follows:

http://<fileadapterhost>:1234/file/Receiver

http://<fileadapterhost>:1234/file/Receiver?action=execute&pipelineid=Receiver

Specify whether a target directory (targetDir) should be created (1) or not (0), if one does not already exist. The default value is 1 (create directory).

Specify the target directory where incoming documents are to be saved. The system creates this directory automatically if you do not make any specifications for file.createDir.

Specify whether the system saves all inbound documents under the file name that you specified in file.targetFilename. The following values are permitted:

In mode overwrite, the file is overwritten so that the system always only saves the last received document.

In append mode the file is updated by appending the incoming documents.

In mode addTimestamp the system generates a new file for each document. The file name comprises the name specified under file.targetFilename, in each case extended by a time stamp in the format yyyyMMdd-HHmmss-SSS. This corresponds to the time that the document was processed, from the year (yyyy) to the millisecond (SSS), which is inserted before the file name extension.

This mode guarantees that no data is overwritten. In this way, files that originate from the same adapter configuration can simply be sorted according to the date that they entered processing

In mode addCounter the system generates a new file for each document. The file name comprises the name specified in file.targetFilename, extended by one counter that is added before the file name extension (for example, default002.file). The counter is constructed from the subsequent specifications.

The mode addCounter guarantees that no data is overwritten. If necessary, the system finds the next free counter from which it can construct a new file name.

In mode addCounter the exact format of the file name can be controlled using the following parameters; each parameter has a default setting.

Specify one or more characters that you want to add before the numerator in the file name. The default value is an empty character sequence (that is, no SeparatorString).

Specify the first counter to be used. It must be a valid integer number, though leading zeros are permitted. The length of the FormatString is used for all counters (including existing leading zeros) until overflow forces the format to be enlarged.

The default value is 000.

Enter a number that specifies the increment of the counter that successive counters are to be increased by. The default value is 1.

Only add the counter after the file name specified under file.targetFilename was used unaltered.

The default value is afterFirst.

If you do not set a parameter, the system generates the file names <default.file>, <default000.file>, <default001.file>, <default002.file> from the specified default values for incoming documents.

Specify the number of days that the management information for received messages with the service attribute Exactly Once (In Order) should be kept. This information is required to avoid messages being duplicated, if when handling an error the Integration Engine sends the same message to an adapter more than once. The default value is 60 days.

In the FTP client mode, the value addCounter is not permitted for the parameter file.writeMode.

The host name or IP address of the FTP server. If this specification is available, it is assumed that you are accessing an FTP server. The specifications file.targetDir and file.targetFileName refer to the FTP server.

A valid user name for the FTP server. It is not obligatory that you specify a user name. The default user is anonymous with the password anonymous.

Use this specification to define whether a new connection needs to be established each time a file is transferred to the FTP server (value perFileTransfer), or whether a permanent connection should be used (value permanently). In this case, the connection is re-established automatically if it closed on the server side (for example, due to a timeout). The default value is permanently.

0 – No header line

1 – Header line with column names from the XML document

2 – as for 1, followed by a blank line

3 – Header line is saved as xml.headerLine in the configuration and is copied

4 – as for 3, followed by a blank line

Specify the header line that is generated in the text file if xml.addHeaderLine has the value 3 or 4. This specification is mandatory.

If you do not make any specifications for xml.fieldSeparator, the specification xml.fieldFixedLengths is mandatory.

Specify how you want the system to respond when column widths in the actual document exceed those defined in xml.fieldFixedLengths. The following values are permitted:

Error means that processing of the document is terminated.

Cut means that a value is shortened to the maximum permitted length.

Ignore means that the system copies the value completely, regardless of it being too long. Subsequent columns are moved correspondingly.

The default value is Error.

If you do not specify xml.fieldFixedLengths, this specification is obsolete.

If you specify a character string here, it is added as a separator to all columns except the last. You can also specify this string in addition to xml.fieldFixedLengths.

If you made no specification for xml.fieldFixedLengths, this is the only specification to identify the individual columns in a row.

If you made a specification for xml.fieldFixedLengths, the length of the separator is not taken into account.

You must specify at least either xml.fieldFixedLengths or xml.fieldSeparator.

If you have only specified xml.fieldSeparator, the structures of the XML document can have differing numbers of elements that are added to each other separately in the text file by the value from xml.fieldSeparator . If you specify xml.fieldFixedLenghts this is not possible since the number of columns is defined when the column widths are given.

If you enter a character string here, the system adds it to the last column as a closing character. You can also make this specification in addition to xml.fieldFixedLengths. To include a line break following the closing character, you must explicitly define it by attaching ´nl´ (including the quotation marks) to the string.

If you specify a character string here, the system places it before the first column. You can also make this specification in addition to xml.fieldFixedLengths.

In all strings for separators (xml.fieldSeparator, xml.beginSeparator and xml.endSeparator), you can specify non-printable ASCII characters. These characters can be each be inserted individually in the string in the form ´0xHH´ (including the quotation mark), where HH represents the character coded as a hexadecimal value. A line break can be entered using the character ´nl´ (including the quotation marks); nl stands for new line here.

If the separators do not contain any line breaks, the text document is generated as a single line text. To restrict the width of the text, use this parameter. <noOfColumns> represents the maximum number of columns in this case. This parameter also functions together with the specification of a line break for xml.endSeparator.

This value requires xml.addHeaderLine=0 to be specified.