Configure the File Transport Connector
The File transport connector makes it possible to send and receive files to
IFS Applications.
The File Reader scans an IN directory for messages in any format, executes them
and
sends an answer back to the RESPONSE directory.
The File Sender has the possibility to send files in different xml-formats or
plain text to an OUT directory.
Note: If the user does not have write permission to create this folder structure in Unix environments, it should be created manually at the first time. After that the full acess rights to the normal user should be granted.
Contents
- Setup the file sender parameters
Setup the configuration parameters for the FILE_SENDER1.
For explanation and help about the parameters, see the quick help which is
displayed as a tool tip for every parameter.

- Two parameters has been added to the file sender (Bug 110869):
WRITE_TO_DESTINATION: True/False - default False.
If set to True the file sender will write files directly to the folder specified
in OUT_DIRECTORY.
If set to False the file sender will write files to a
temporary folder and when finished writing move the files to the folder
specified in OUT_DIRECTORY.
CREATE_LOCK_FILE: True/False - default False (setting only valid if
WRITE_TO_DESTINATION = True).
If set to True the file sender will create a file with the same name but ending
with .LOCK before starting to write a file. When the file is written the LOCK
file is removed.
- Configure the CONNECT_SERVER1 to run the File Reader
Add FILE_READER1 instance name in the
CONNECT_SERVER1 configuration.
- Setup the file reader parameters
Setup the configuration parameters for
FILE_READER1 instance.
The POLL_TIME parameter is the time in milliseconds between each check for new
files.
The USE_GUID parameter adds a unique key to the response file to separate files
with the same name.
For explanation and help about the other parameters, see the quick help
which is displayed as a tool tip for every parameter.

The USING_TEMPORARY_DIRECTORY checkbox is useful on Unix systems when
the owner of the inbound files isn't the same as the
owner of the process running the Connect server.
If the file owner and the process owner aren't the same an error will occur
and the files in the In directory will not be processed. To avoid this
situation the files should first be copied to the temporary directory (temp)
created by Connect.
When the complete file is stored in the temporary directory the file can be
copied to the In directory, the owner of the file is not important when using
this option.
Note!
The copy functionality from the Temp directory to
the In directory has to be implemented, it's not a part of Connect.
- Restart the CONNECT_SERVER1
Shutdown the connect server and start it up again.
It's possible to create new instances of the File Reader Transport Connector
provided that they should scan distinct directories (Only one File Reader can
scan an in-directory).
Instructions for how to create a new connector instance.