- This topic has 2 replies, 1 voice, and was last updated 9 years, 7 months ago by
.
-
Posts
-
-
Hi everyone,
I suppose this is an open ended question, any advice is welcome.
Question: In an asycn messaging scenario (over transports such as FTP, SMTP and HTTP), what should I do (or can biztalk do) to help me ensure guaranteed delivery or reciept of messages?
I know there are protocols in the wild that help with this (for example ebXML), however, surely biztalk comes with something to “help” with this. Namely, when to retry a message, how to handle duplicates etc (i.e.everything a guaranteed delivery protocal should have).
If no, what protocols do you employ to do this?
I’m having real difficulty finding information on this, so experiance from the veterans would be welcome!
Thanks!
TM
-
One of the reliability feature provided by BizTalk adapters is configurable Retry. BizTalk allows you to configure the parameters like Number of Retry, Retry interval.
BizTalk detects, if there is any failure while sending data using adapters like FTP, HTTP, SMTP…. and then attempts to send data again as per the Retry parameters configured.
If data transfer fails even after all Retry attempts then it will log an error in Event log, after which manual intervention required to detect the problem
-
Also check out Delivery Notification: http://kentweare.blogspot.com/2007/11/biztalk-delivery-notification.html
Becareful with SMTP though. The behaviour that I have experienced is that BizTalk can pass the message off to the mail server(in my case Exchange) but if the mail server cannot not deliver it, BizTalk will not be made aware since it is really just a hand off to the email server. To mitigate some of the risks, have the reply address in your send port configuration an account that is monitored, this way if the mail bounces back at least you will know about it.
Kent
-
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.