We need to implement the best error handling technique to log errors when posting the xml files to a Web Service. we need valuable suggestions for the following scenerios.
Here is what we were thinking if the web Service becomes unavailable for some reason (to log errors):
“Post the failed XML documents to a DataBase. Write another flow service which is scheduled to run say every half an hour
(poll for the failed docs) and if there are messages, try to post again to a webservice. This time if that’s a success, delete the document from DB; else keep trying the same.”
But we are worried on how to handle the above case in the following situations:
"If the first failure generates a trouble ticket, and then you retry, and then again fail, will all of these failures keep generating trouble tickets?
Could there ever be a situation where you legitimately don’t want one of those records to reprocess?
If so, will there be a facility to not retry that one? Such as, a database column to disable, etc.
Will there be a need for some way to reprocess these ‘on demand’ and not on the schedule (what if you have thousands of errors and want to search and see which ones need to be reprocessed)?
If on demand will be necessary, will you need a GUI to do it, and what will this GUI be like, and is there more work involved for creating it?
Will there be a need for some way to view the content of these messages that failed and selectively run or reprocess them (what if you have thousands of errors and only want to reprocess a few hundred)"
Could anyone please suggest the best implementation for the above scenerio.
All responses are greatly appreciated.