\n
It is My File BizTalk Orchestration.(Please let me know if anything need to change).
\n\nAlso, if you provide any example of it will helpful as i am beginner in BizTalk.
Reputation: 145
Starting with this version, BizTalk can route fault messages, and that's pretty good. Let's say I'm receiving a badly-formatted positional txt file and a receive pipeline can't let the message get into the orchestration. I can see that between the 'Suspended Services Instances' I have my suspended service gone in error with its code and its pretty explicit description.
I would love to get all this data into a file (txt) and route it into a dedicate folder, without using custom pipeline components or other libraries, just BizTalk out of the box functionalities.
Is it all possible (to save exception in log file)?
It is My File BizTalk Orchestration.(Please let me know if anything need to change).
Also, if you provide any example of it will helpful as i am beginner in BizTalk.
Upvotes: 2
Views: 160
Reputation: 11527
Short answer: You need some custom components or the ESB Toolkit.
If you switched on routing for failed message on the Receive Port, you can create a send port which has the Filter ErrorReport.FailureCode Exists
and all failed messages will go to this port. You can add additional filters to limit it to certain ports or other context properties.
The below example shows what it looks like. It also has an additional filter as this is the ESB Exception Management Framework Send Port, which is part of the ESB Toolkit. However just adding that filter will just send the original message, without all the error information. The Microsoft sample ESB Exception Management Framework includes a ESB Fault Processor Pipeline component to get the original message and error report, and to insert them into a DB.
Upvotes: 1