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 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. |
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.
|
|
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
metadata
string. |
|
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. |