RIP not working while using transformation service in messaging extender

Question

We are receiving a flat file and using a custom flat file disassembler, we are transforming the message using transformation service using a BRE resolver in a messaging extender as the first component in itinerary. If one of the records in input message fail to transform the complete message errors out. If we change the extender to orchestration extender, it works correctly as in only the record failing to map is errored out. As we are using disassembler and the transformer service comes into picture only after disassembling, shouldn't it fail only the errored record even if we are using messaging extender? 

Looking forward to your responses,

Regards,

Dipti

---

Dipti Porwal

Answer 1

I believe your issue is related to this: http://biztalkmessages.vansplunteren.net/2009/03/26/recoverable-interchange-processing-enhancements-in-biztalk-2009/

hth

---

MCT, MCSD.NET, MVP

Answer 2

Thanks for your answer Dwight. We have already tried implementing setting the SuspendonMappingfailure property as described in this blog but it doesnt work with the itinerary. Setting up this property works for a Non-esb scenario but looks like ESB dispatcher component is not aware of this property at all. Moreover, I can see the suspended message is not xml and not disassembled whereas we are applying the disassembling before esbdispatcher(we have added esbdispatcher component to resolve party stage so the message should have got disassembled before that in the disassembler stage) Why is esbdispatcher receiving the original input message rather than the disassembled message? Please share your thoughts on the same. Is there any other property in esbdispatcher that we can make use of?

---

Dipti Porwal

Answer 3

I have not received any reply on this and haven't found a solution as well. Those who understand ESB toolkit well, please throw in your suggestions/views.

Thanks!

Dipti

---

Dipti Porwal

Answer 4

Can you post the stages you have in your custom pipeline component?

It should just be a case of setting the "Recoverable Interchange Processing" property to true in your Flat File Disassembler pipeline component.

---

Colin Meade (MCTS BizTalk Server)