Implementing a retry pattern in an orchestration
A challenging situation with a BizTalk orchestration can be when communication with the external system fails and we have no idea what to do next. You can, for instance, in a Send port, configure a number of tries before an error message is generated by BizTalk. In case there is no properly planned action, the message and orchestration both are suspended in the BizTalk Administration Console and cannot be resumed in a fashionable manner. Once the communication is restored, resuming messages may work, but messages sent from an external system will not connect with the corresponding orchestration. Resuming the orchestration could fail if it is waiting for a specific message type. What you could do ...
Get BizTalk Server 2010 Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
