Hi Vinoth,
From experience, I would recommend that you use the following design (always try to use messaging service more than orchestration service when applicable)
1- create a receive port (i.e RP1 ) with a receive location to receive your source files
2- Create a send port that is subscribed to RP1 , and have a flat file assembler pipeline configured on it
3- configure the send port to append the out files to a temp path (i.e. C:\temp\OutputTemp.csv ), the file name should be static so that the aggregation can work
4- create another receive port (RP2) with a receive location to receive the aggregated file from your temp path
5- configure the receive location of RP2 to be scheduled at the time you consider end of day (i.e. 6pm), this means that the files will keep aggregating until 6pm
6- you can create an orchestration that is bound to RP2 which will add the head and the footer to the received file, or you can even create a web page (asp.net) that will do this for you by clicking a button (in case you want it to be a manual process at
the end of the day)
this approach is loosely couple which means you will have more control in following up issues (you can archive what you receive , you can change the end of day time anytime you want, avoid singleton issues and zombie messages in the message box , a faster
approach ...)