ebXML Host: ebXML Tab

Save the content of the HTTP header and raw (unprocessed) message sent to the remote host. The files are stored in the ebXML\sent+received directory under the root path. These files can be useful in diagnosing problems, but should be disabled if disk space needs to be conserved. Click Resend to send a duplicate of a previously stored raw message to the trading partner.

Allows the incoming file to be given the name specified in its associated field. Use this option to override the file name specified by the sender. This feature is useful in situations where the received file name must be something other than its original file name, and is common for IBM i / iSeries (AS/400) platforms where the file name must be specified with a .mbr extension. This field can also include any of the supported macros allowing for the incoming file to be named, for example, with a date-time stamp. Subdirectory path identifiers (for example, ‘/’ or ‘\’) can also be used in conjunction with macros to allow filtering of the incoming file to a specific subdirectory under the inbox based on the value of the macro variable. See Using macro variables (Destination File context) for a discussion of all applicable macros.

Note: If a subdirectory path is specified and it does not already exist, it will automatically be created as needed unless the subdirectory path is under an inbox on the AS/400 Native File System. In that case, the physical file denoting the subdirectory path (in the form: DIRECTORY.FILE) must be created under the specified inbox before files can be written to it.

Allows you to sort incoming messages based on content-type to a subdirectory under the Inbox specified on the General tab. Specify each of the Content-Types you want to direct to specific subdirectories by entering a name in the Directory field. You can specify directories for Content-Types of: EDIFACT, X12, XML, Binary, Plain Text, EDI Consent and Other (a default for messages with all other Content-Types you might receive). You can specify the same subdirectory for multiple Content-Types. You can also leave Directory entries blank, which causes any received messages of that Content-Type to be stored in the Inbox specified on the General tab.

For IBM i / iSeries (AS/400) usage, see AS/400 Setup and installation or AS/400 PC network access setup for information on configuring the Content-Type Inbox settings to access the Native File System (NFS).

Note: If you use this feature, incoming messages are placed in the specified folder based on the content type specified in the HTTP header of the message. The VersaLex application does not check the actual content of the message to determine its content type.