Backlog of Messaging Replay Requirements
We plan to expose a receive location in BizTalk for systems to send us a message if they have failed to process a message.
What we would like is some kind of backlog in BizTalk360 to store these messages and assign \ alert administrators of the master system.
Whilst the ESB Exception Management Portal fields could be rigged to support this, a dedicated set of fields\functions would be better:
• Assigned to Team
• Data Type
• Record Identifier
• Error Message(s)
• (Addressed By Action) : Resubmit from source | Raised with Service Desk | No action required
• (Addressed By Notes) :
• (Addressed By Timestamp)
• (Addressed By Name)
Charlie Mott
shared this idea
-
Charlie Mott
commented
Also see comments in this feedback idea: http://feedback.biztalk360.com/forums/331695-biztalk360-operations/suggestions/14934354-delet-esb-fault-messages-that-users-do-not-want-to
-
Charlie Mott
commented
Just to clarify. I want to alert users to the fact they need to resubmit the message from the source system (after they have addressed the cause of the error). Generally, if data cleansing is needed, I would rather fix at source rather than fix-and-repair using BizTalk ESB Toolkit.