Fileset/FTP Local Outbound pane

This tables shows outbound parameters:

Parameter Description
Directory Specify the local directory path (OBDIR). This specifies the directory for local file delivery.
File Name Template Fileset Local stores the file name for IB files, but after routing to an outbound Fileset FTP, it uses the inbound file name by default. With this option, you can define the template for outbound file names.

For example, if the template is SYS.TIMESTAMP, the outbound file name is similar to 20160411.

In another example, an outbound file name of site_testsite_p_5120.dat has a template of site_%CIS.SITE%_p_%MSG.PRIORITY%.dat.

If this field is left blank, then it reverts to the old behavior.

If this directory is specified, then File and File Name Template cannot both be empty.

For the templates, see Fileset FTP/Local outbound file name templates.

File Specify the default outbound file name (OBFILE).
Temporary File Specify the path and name of the temporary file to use when transferring data. If this text box is empty, then no temporary file is used. When the transfer is successfully completed, the temporary file is renamed to the value of the FTPTEMPFILE key. If this key is empty, then the file is uploaded as the actual file name.
Style Click the arrow to select from the list how messages are stored within the files (OBSTYLE). This value is particularly important when numerous messages are written to a file.
  • If single, then the driver reads the contents of the file into a single message.
  • hl7 and nl specify other schemes for delimiting messages within the file.

    For nl style, the delimiter is <NL> between messages. As each message ends with <CR>, between messages would look similar to <CR><NL>.

    For example:
    MSH|……<CR><NL>MSH|……
    <CR><NL>MSH|……<CR><NL>

    File read/writes in nl mode do not support the Unicode UTF-16 encoding. The nl mode cannot be performed without knowing the encoding beforehand, which is not known.

    For hl7, the delimiter is <CR>MSH and the last character at end-of-file must be NL. The NL at the end-of-file indicates that it is the end of the message. Basically, each message ends with <CR>. With the hl7 style there must be <CR>MSH in-between each message. The MSH is technically not a delimiter because it belongs to the next message. It serves only as the indicator for the beginning of the next message during parsing. In this sense, there are no delimiters between HL7 messages, as the engine seeks the <CR>MSH to find the beginning of the next message.

    For example:

    MSH|……<CR>MSH|……<CR>MSH|……<CR><NL>
  • len10 specifies a 10-byte record length, also called a length-encoded message.
  • eof specifies that the message has an end-of-file character, usually supplied by the computer’s operating system.
Append data Select this to append data to the file (OBAPPEND), if it exists. Otherwise, the file is overwritten each time the thread starts up.
Override all of these outbound control values with a message’s
DRIVERCTL
metadata string.
CRNL Convert This creates any files on a Windows server as Windows-type files and not as UNIX-type files. CRNL is for Windows and NL is for UNIX. This option is first performed on each message (record) in a file. After this, the message delimited Style is performed.

CRNL to NL converts Windows-based files to UNIX-based files. NL to CRNL converts UNIX-based files to Windows-based files.