Multi-threading XML PostBack project.
Needs to be [VB.NET] if at all possible, if not then C#.
Platform is Windows 2003 Server and may be going to 2008 with testing on XP but should work on Vista.
An existing? main frame application will be generating 1,000 to 5,000 small files every night.
Each file is composed of transactions lines for a separate external company.
I already some of the [VB.NET] code to process the data for the. More will be needed.
These 1000-5000 files must be processed each night at around 2-4AM local time.
Multiple threading will be required so that all the transactions can be processed in small amount of time.
? **Programs Needed:**
1.? ? ? ? ? Controller Program **(Cntr):** (starts threads or sends XML request, etc.) **Prefer VB.NET otherwise C#.**
2.? ? ? ? ? PostBack Program ? **(PB) - VB.NET:** To Process? 1 transaction file.
? Multi-threading / PostBack project.
**Controller Program (Cntr): VB.NET (Prefered) or C#**
1.? ? ? ? ? The controlling program? must be a **system service** application that will start automatically at a certain time (if not already running).
2.? ? ? ? ? Cntr will monitor a folder for files (optionally ? with a certain file pattern) and when the files are detected will ‘launch’ a thread / Task passing parameters (i.e. filename) via posting to an external server.
3.? ? ? ? ? Cntrl will post a simple XML request to the external server with a parameter (i.e. filename less extension) ensuring that it arrived successfully.
4.? ? ? ? ? Status windows with the option to change parameters would be needed. (i.e. number of threads, post URL, XML template). ? There would also be parameters for the PostBack programs.? Not sure where or how this should be handled yet.
5.? ? ? ? ? Logging to 1 file for all programs..
**PostBack Program (PB) (there will be 1-n threads running): VB.NET**
1.? ? ? ? ? PB will be URL posted from the external server with the parameter (i.e. filename) sent above.
2.? ? ? ? ? Complete the ‘handshaking with the external server using their ssl requirements. A **Java interface** would probably be the simpliest. This should be only a few lines of code but an interface is needed.
3.? ? ? ? ? The file will be read and transaction processing will occur **(we already have the processing component)** and will merge the code ourselves.
4.? ? ? ? ? Status window and parameters.? Not sure where or how this should be handled yet.
5.? ? ? ? ? Logging to 1 file.
I assume the parameters could be saved in an ini (config settings) file.? I am NOT a believer in using the Registry for everything.
Program doc on functions used and why plus operational doc required. Doc is to be explicit on what EXTERNAL requirements it has and how to? set.
Installation doc is a must.