Again, thx for everybodies replay.
The current app we have is a windows service that does just that. Waits for the file to come in, decypts/untars/calls a sproc and moves the file. As I mentioned above, we implemented Biztalk about a month ago and picked 3 "different styles" of projects that we currently had running in production to rewrite in Biztalk just so we could get our hands around the new product. Our other projects we completed (more data integration between systems) are working great. This one has just felt like we've been forcing Biztalk the entire way.
This process does have a bit of business logic in it, in the sense that it performs certain actions in our DB based on the file name of the .tifs. Other than that, it's a file mover.
We considered using a "pointer" system as describied in the Apress Pro Biztalk 2006 book, where the actual files are not moved through the message box, but rather the file locations and biztalk is used for process flow logic only.
What we ended up doing is pulling all files recieved in our port and forcing them in a single file line before entering our orchestration through our custom pipeline components. In other words, the 1st file must be completely through the rcvd pipeline/orchestration before the 2nd one is allowed to enter. This seems to work fine and we've successfully pushed 4+gig of .pgp files through our process succesfully. However, it's a bit of a "quirky" way to do it.
Again, thx to your responses. I would still appreciate any more feedback, if someone feels like giving their 2 cents.