Our customer manufactures and delivers Clip Fasteners and Bonding Equipment to leading automobile plants as well as the industrial and construction sectors.
The customer has a system that generates and copies "commands" to files every five seconds. These files have to be:
§ Picked up and distributed to multiple recipients
§ Processed by the server before being sent
§ Processed by the client (i.e. loaded into an application) after being sent
This entire process should be completed in less than five seconds.
Especially important for the customer is the ability to automatically prioritize and order the files.
File prioritizing:
Files placed in high priority FEST “Hot” directories should be sent before those placed in lower priority FEST “Hot” directories. Additionally, if a high priority FEST “Hot” directory is performing retries (on one of the files), FEST should start transmitting files from lower priority FEST “Hot” directories.
File ordering:
The customer requires assurance that FEST will wait until it has completed processing one file (from the same directory) (including execution of the remote commands) before sending the next file. In other words, for each FEST “Hot” directory, the customer needs FEST to send the files one after another. However, if a transfer is aborted, FEST will cease sending files from that FEST “Hot” directory.
The needs of the client can be met using the existing FEST filters. The basic flow will be as follows:
1. The client’s system places the files into FEST “Hot” directories with a directory being designated for each recipient.
2. The files are immediately picked up by FEST, pre-processed and then sent to the recipients.
3. FEST will also reside on the client side. As soon as a file is dropped into the designated "in" directory, it will be picked up by FEST and processed.