MQ FTE - Manage your file transfers the easy way!
ValerieLampkin 27000182R2 Visits (28746)
Don't know much about MQFTE? Here's a good starting place. WebSphere MQ FTE (File Transfer Edition) is a product that enables secure and reliable managed file transfers. It can be administered by either a GUI or the command line.
You have the option of monitoring a directory or MQ queue for new data and initiating a transfer based on criteria that can be configured to monitor for files by seconds, minutes or hours.
When a matching condition is found, the monitor can copy or move a file or it may run a FTE call (such as ANT script). Some options that may be employed by a directory monitor trigger are a file name pattern, size of file, that file hasn’t changed for certain number of polls, or at that a certain file does NOT exist. This last option is useful for a temporary file to be placed in a directory to prevent transfer until you are ready for the transfer to begin.
The trigger file isn’t necessarily the file that is to be transferred. You can set a monitor to check for the trigger file and then actually perform the transfer on a different file. Often, an exit or call is made afterwards to delete the trigger file after transfer occurs.
One thing to keep in mind is that if more than one file matches the trigger pattern, a new transfer will be started for every file found. This could cause a problem if you have a short poll interval and lots of files. High CPU may result as many transfers are initiated when the first one has not yet completed.
A common problem we have seen is when 1,000s of transfer are started instead of one big transfer. If there are 1,000 files matching the trigger pattern (for example *.log file), the FTE would start 1,000 transfers of 1 file each. You can use the batch size ( -bs) parameter to avoid this. For example: 1,000 files with a monitor batch size of 100 results in 10 transfers of 100 files.
Some parameters that can be used to help configure and modify your FTE agent are moni
Thanks to Matthew Whitehead, Hursley UK for his assistance with this blog entry.