Use this dialog to define the file-to-file transfer parameters for this connector and file-to-file dispatcher.
Req
Msg Descriptor
The name of the message descriptor to use for sending file transfer request
messages. If not specified, kfxMsg00000001 is used.
Receiver
Notify Results
The business service to which the receiving connector should send the file
transfer results message. This results message is identical to the results
message the sending file transfer connector sends to the eBP application
that originated the request. This message is similar in format to the
original request message, and it is sent for both successful and unsuccessful
file transfers.
Max Data
Msg Size (required)
The largest message the connector can send in Kbytes
(minimum value is 500; maximum value allowed is 2,097,151).
Load Balancing
Providing you have CandleNet eBP Administrator application management installed,
checking this specifies that file transfer requests using this connector
should take advantage of system load balancing—that is, send the request
to a business service configured for load-balancing.
Note: This option is required if the file-to-file dispatcher you are creating sends any requests to load-balanced connectors. The file transfer can fail if this box is not checked, and this dispatcher attempts to send a request to a load-balanced connector. The CandleNet eBP File Transfer User's Guide describes how to configure a load-balanced connector.
Overwrite
Files
If checked, specifies that existing output files can be overwritten with
new output files of the same name.
Transactional
If checked, specifies that the XML request occur under transactional control.
Persistent
Messages
If checked, specifies that this connector use persistent messages on all
send requests.
Expiry
The number of hours and/or minutes the connector should wait for the file
transfer to complete before cancelling the request.
Enable Path (checkbox)
If checked, enables the following checkboxes and text fields. Note that
checking Enable Path requires that you complete Send Path,
Receive Path,
or both.
Send
Path
The default path the sending connector uses to locate files to transfer.
Otherwise, the path specified in the Source.Path
XML element is used, and if that is not specified, the connector looks
for the source files in its current working directory.
Receive
Path
The default target directory for transferred files. Otherwise the path
specified in the Destination.Path
element is used, and if that is not specified, the receiving connector
stores the transferred files in its current working directory.
Accept
XML Paths
If checked, allows fully-qualified paths in the XML request Source.Path
and Destination.Path
elements when Send
Path and Receive Path
are also defined. For information on the XML Source and Destination elements,
refer to the CandleNet
eBP File Transfer User's Guide.
If unchecked, the XML request will fail if either or both of the following are true:
Send Path is set, this connector is a sender, and Source.Path specifies a fully-qualified path.
Receive Path is set, this connector is a receiver, and Destination.Path specifies a fully-qualified path.
Relative
Paths
Allows the file transfer XML to use relative path names when specifying
source and destination file locations. Checking this box also enables
the Create Relative Paths checkbox.
For example, Destination.Path specifies ..\newpath, and Receive Path below is set to c:\filetrans\receive, eBP File Transfer stores the transferred files in a directory it creates called c:\filetrans\newpath.
Create Relative
Paths
Specifies that eBP File Transfer create directories when the destination
file path uses a relative path, and the resulting path specification does
not exist. (This applies to receiving connectors only.)
Note: The connector will reject any XML request that uses relative paths unless Relative Paths is checked.