ESB Toolkit 2.2: Error in using the dynamic itinerary resolver (BRI)
4/30/2013 7:11:46 PM
User(s) can reproduce this bug
ESB Toolkit 2.2 with BizTalk Server 2013
Windows Server 2012
Dynamic itinerary selection using the ESB pipeline 'ItinerarySelectReceiveXML' and the Business Rules Engine does not work (i.e. using the ESB Resolver BRI). It is not possible to dynamically apply an itinerary on a receive port. Only static literary selection appears to work.
Further confirmation of the issue logged in this MSDN forum thread:
BizTalk 2010 Beta
Business Rules Engine
Create a FILE receive location using the pipeline 'ItinerarySelectReceiveXML' with the following pipeline settings applied:
Within the Business Rules Engine, create a rule with the name ‘DemoSelection’, and a rule that states If 1=1 then return itinerary DemoItinerary.
When dropping any file into the given FILE receive location the exception is thrown (logged in the Windows Event Log)
to post a comment.
Please enter a comment.
on 12/18/2013 at 2:47 AM
I am facing the same issue, No work around, even hot fixed described is working. I got this error on WCF Sql call on receive port with ItinerarySelectReceive Pipleline.
There was a failure executing the receive pipeline: "Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceiveXml, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=184.108.40.206, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "ESB Dispatcher" Receive Port: "test.ESB.test.Receive" URI: "mssql://xyz_STAGE?InboundId=getProductUpdates" Reason: Exception has been thrown by the target of an invocation.
on 8/8/2013 at 10:17 AM
We did as per the workarounds suggested but still the error remains same. Any more suggestions?
on 6/6/2013 at 1:38 AM
The whole advantage of the ESB Toolkit is to use Dynamic resolution, in my experience, using the BRI resolver is the #1 reason to use the ESB Toolkit.
Custom coding to extend the toolkit seems quite logical, custom actions to make it work as it does not out of the box does not, i don't know how to explain this to my customer.
to post a workaround.
Please enter a workaround.
on 5/12/2013 at 11:53 AM
The “Microsoft.Practices.ESB.Resolver.Unity.ResolveProvider” object in the ESB Toolkit 2.2 uses Microsoft Enterprise Library 5.0 and Unity 2.0 and Unity 2.0 uses a new streamlined configuration schema for configuring Unity. Therefore, the esb.config file from the ESB Toolkit must be modified.
The following adjustments should be made:
•Remove the <typeConfig> element
•Change the <typeAlias> element to <alias>
•Change the <type> element to <register>.
•Remove the <containers> elements and <types> elements.
For more information see:
© 2014 Microsoft