BRE rule not firing when called from ESB Toolkit Itinerary

Question

Running a BizTalk 2013r2 solution, I have the following itinerary:

All is good up to the selected "Auth Endpoint Detail"

This is calling the BRE, passing the following message:

<ns0:MasterCardRequest xmlns:ns0="http://www.EsbToolkit.TargetWebService/Authorization/MasterCardRequest">
  <ns0:AuthAmount>300</ns0:AuthAmount>
  <ns0:CardNumber>1111-1111-1111-1111</ns0:CardNumber>
  <ns0:OrderNumber>130</ns0:OrderNumber>
</ns0:MasterCardRequest>

This should cause the following "MasterCard" rule to fire - which would then send endpoint values in the context of the message:

Problem is - it's not firing! It does fire when I manually "Test Policy" from within the BRE Composer. However, when I run a message through BizTalk and check DebugView, I see the following:

I have doubled checked that the correct version of the policy is Deployed. I'd be very grateful for any ideas as to which the rule is not firing.

How many endpoints are you resolving? Do you really need to use ESBT? Roles look like an option here as well. — Johns-305, Sep 30 '16 at 16:17
Yes, need to use the toolkit for this solution as part of a PoC — Rob Bowman, Sep 30 '16 at 18:27
Haha, I take it you're not a fan? I must say, I can find it difficult to justify the additional complexity. — Rob Bowman, Sep 30 '16 at 19:07
Winner, winner. I've never seen ESBT make anything easier, just harder to develop, debug and support. Dynamic routing is pretty easy to do with just the BRE. — Johns-305, Sep 30 '16 at 19:58

score 1 · Accepted Answer · edited Oct 04 '16 at 20:45

1

You may check if document type property defined in the BRE ruleset matches to DocType shown in the debugview. The BRE resolver mechanics are not well documented, perhaps this will help: which is the meaning of recognize message format property?

Also when doctype is meant to be generic, avoiding namespace name in rules is recommended.

edited Oct 04 '16 at 20:45

Dijkgraaf

9,324
15
34
48

answered Sep 30 '16 at 18:00

dmitrio

26
3

Thanks dmitrio, the problem was my rule stated "Exists in Microsoft.Practices.Esb.ResolveProviderMessage" - the "ESB" letters must be all upper case – Rob Bowman Oct 03 '16 at 08:54

BRE rule not firing when called from ESB Toolkit Itinerary

1 Answers1