- This topic has 6 replies, 1 voice, and was last updated 7 years, 8 months ago by
.
-
Posts
-
-
Hi,
I have been requested to get email requests on failed send port submissions. This appears to be quite simple:
-
Set Enable routing for failed messages on the web service send port
-
Create a new SMTP send port with the following filter: ‘errorreport.errortype = failedmessage’
This will then mean that the SMTP send port will subscribe to any failed message routing for the web service sendport.I have since been requested to modify this so that an email will only be sent after 3 retries of the same message.I was wondering how I can do this and can only see the following options:-
Create a new orchestration which will subscribe to the failed messages in the web service send port and keep a count using some kind of promoted array of message ids that have failed before. This however seems messy and besides which would require a production code change which may be hard at present.
-
Create a service which will periodically query the BizTalk database direct using some kind of grouping query based on the message id? I am also hesitant about this as I do not want to really interfere in any way with the production locks etc.
-
The only other option I can see would be to have a database send port that would subscribe to the failed messages of the web service send port, which instead of sending an email would write a row to a database with the error/message id details. A windows service would then periodically scan this table with some sort of grouping function on the message id and determine if the same message had failed say three times in a row, and in turn send an email then.
Maybe there is something inherent in BizTalk that I am missing which will accomplish this?Thanks -
-
Hi!
Did you check the settings on the “Transport Advanced Options”-tab of the port? There you might see a block called “Transport Options”. Therein are the options for port-retrying. The port will not terminate to “suspended”-state before it has executed the given number of tries with the given interval. After this, the port will suspend and the failed message routing-process will kick in. In your case, as far as I can see, failed message routing may not even be nessecary (spelling on that one, anyone?). You might be able to utilize the “Backup Transport”.
Go through the port settings and fiddle around with that for a while and you might take a step in the right direction.
Regards, Niklas Häggström – Connecta AB, Sweden
-
Hi thanks for the response: Yeh will go with this need to as this is the ‘BIZTALK’ default method for this.
However our solution is architected in such a way that we rely on retries being generated from an originating database call (i.e. which send the original biztalk request via the recive port), so was looking at how you could interogate the biztalk sql database to do some more sophisticated queries, like only send an email if there have been 100 failed messages on that send port in the last 10 minutes?
Of which this could prob be donw via an orchestration, but was looking for a non code change i.e server admin or sql query.
Thanks
Simon
-
Rather than creating a system management application within Biztalk, you might like to look at using MOM, CA Unicenter or Tivoli, etc
These software products are specifically designed for detecting errors and applying rules to handle them. -
-
Simon,
I may have missed the gist of this thread, but one ‘Heath Robinson’ approach would be to use the backup transport option on the send port to send the message to a file location.
Poll that file location and when you receive 100 files, send an e-mail alert.
Not the world’s best, but it keeps it within BizTalk, however I would definately recommend MOM as the professional approach.
Rgds, Nick.
-
-
-
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.