We have several custom scripts as well as commercial program. All will run on a windows server (2012R2). Being that the output results per minute are minimal, at least 3 of the 4 programs will need to be run simultaneously. I am going to be performing a stress test on the server to determine the actual number of processes it can handle safely.
My initial thought is to have the following:
-GUI interface that will execute the various processes. Sometime soon, I am going to put the server under a stress test to see if it can handle +/-5 simultaneous instances of each (3-4) programs. It is possible that we will have to upgrade the server which we will do if needed.
-A system of "failsafes" that will either stop the process(es) or alert the person that there is a problem. The problems can be:
-System overhead is high
-A proxy address is not working
-An account is failing to log in. The only think I can think of here is to utilize our custom OCR program to scan for pages that have certain text on it like "You Account is Temporarily Locked" or something similar. If it sees this, it will automatically stop the process and alert the person who is running this. Alternatively, we can run the OCR offline and do the same thing once the previous process is completed
On the GUI, (as per the results of the stress test), if for example we determine that the maximum number of simultaneous processes is 20 (5 each), then the system will not allow that to be exceeded.