If your cloverleaf box is pulling (FTP/get) or pushing (FTP/put) files then the cloverleaf box is the client and the fileset-ftp protocol on cloverleaf can be used for performing that action because the cloverleaf application is the FTP client and the foreign system is the FTP server.
A FTP server does not even have to be running on your cloverleaf box if it is always acting as a client like describe in the previous sentence.
When the foreign system wants to push (FTP/put) the files to a cloverleaf box then you need to have the desired FTP server with user Id logins setup on the cloverleaf box.
In this case the foreign system does not have to have a FTP server running with user Id logins and is sometimes the reason foreign system owners perfer this.
You don’t want to use the hci user ID for their FTP/put and need to create a user ID just for their FTP/put.
In our case we have a FTP file system that has a setroot security that will not allow any of the FTP/put or FTP/get by a foreign system to navigate out of the user ID home directories.
We also have our FTP server configured with an access list that only will accept logins for a given userID / IP combination, so if anyone has the user Id and password they can’t obtain acces execpt from an authorized server.
This can also help prevent not only security breaches but from accidentally sending test data to a prodcution envirnment.
Each FTP interface where the foreign system is the client (FTP/push or FTP/get by the foreign system) to a cloverleaf box should have its own unique user ID if you want my advice.
So once you have the FTP server up and running on your cloverleaf box and their user login is working and they are able to put their files onto the cloverleaf box then use the fileset/local protocol in cloverleaf to scan the directory and pickup and process the files.
Depending on how often they write files and cloverleaf picks them up the case where cloverleaf tries to pickup a file before the foreign system finishes writing to the file can occur.
I handle this by having the foreign system append _hide to the filename and when done writing the file remove the _hide and configure cloverleaf to ignore any *_hide files which could be done via the dir_parse proc.
Russ Ross
RussRoss318@gmail.com
.
