BizTalk BRE - Easier Troubleshooting












0















I've been using the BRE with BizTalk 2016 (FP3 CU5) lots lately. When it works then it's great but I've found troubleshooting problems with policy execution to be very difficult and wanted to check if anyone has found a better way.



I'm using an orchestration CallRules shape to execute the policy. I've also created unit tests that call the policy with a DebugTrackingIntercerceptor. In the case of a successful policy execution, where rules fire, the debug info that's output looks something like:



FACT ACTIVITY 19/11/2018 07:59:12
Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
Operation: Assert
Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.GetServiceRequestDetailsResponse:/*[local-name()='GetServiceRequestDetailsResponse']/*[local-name()='GetServiceRequestDetailsResult']/*[local-name()='Customer']/*[local-name()='ContactTransports']/*[local-name()='ContactTransport'][*[local-name()="Name" and .="Email"]]
Object Instance Identifier: 9589157

AGENDA UPDATE 19/11/2018 07:59:12
Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
Operation: Add
Rule Name: BartecUpdate
Conflict Resolution Criteria: 0

RULE FIRED 19/11/2018 07:59:12
Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
Rule Name: BartecUpdate
Conflict Resolution Criteria: 0

FACT ACTIVITY 19/11/2018 07:59:12
Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
Operation: Retract
Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.CreateActivity
Object Instance Identifier: 49478415


Some of the rules within the policy check the value of certain elements of XML document facts. If, the asserted fact happens to have one of these elements missing (such as from the first rule in the activity debug info shown above), then there is no obvious indication of a problem from the tracking info. The only way to identify something's not right is if you notice that the rule did not fire. From here it's a matter of meticulously checking for the presence of elements used in each rule.



Is there a better way to identify why a rule did not fire?










share|improve this question





























    0















    I've been using the BRE with BizTalk 2016 (FP3 CU5) lots lately. When it works then it's great but I've found troubleshooting problems with policy execution to be very difficult and wanted to check if anyone has found a better way.



    I'm using an orchestration CallRules shape to execute the policy. I've also created unit tests that call the policy with a DebugTrackingIntercerceptor. In the case of a successful policy execution, where rules fire, the debug info that's output looks something like:



    FACT ACTIVITY 19/11/2018 07:59:12
    Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
    Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
    Operation: Assert
    Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.GetServiceRequestDetailsResponse:/*[local-name()='GetServiceRequestDetailsResponse']/*[local-name()='GetServiceRequestDetailsResult']/*[local-name()='Customer']/*[local-name()='ContactTransports']/*[local-name()='ContactTransport'][*[local-name()="Name" and .="Email"]]
    Object Instance Identifier: 9589157

    AGENDA UPDATE 19/11/2018 07:59:12
    Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
    Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
    Operation: Add
    Rule Name: BartecUpdate
    Conflict Resolution Criteria: 0

    RULE FIRED 19/11/2018 07:59:12
    Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
    Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
    Rule Name: BartecUpdate
    Conflict Resolution Criteria: 0

    FACT ACTIVITY 19/11/2018 07:59:12
    Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
    Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
    Operation: Retract
    Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.CreateActivity
    Object Instance Identifier: 49478415


    Some of the rules within the policy check the value of certain elements of XML document facts. If, the asserted fact happens to have one of these elements missing (such as from the first rule in the activity debug info shown above), then there is no obvious indication of a problem from the tracking info. The only way to identify something's not right is if you notice that the rule did not fire. From here it's a matter of meticulously checking for the presence of elements used in each rule.



    Is there a better way to identify why a rule did not fire?










    share|improve this question



























      0












      0








      0








      I've been using the BRE with BizTalk 2016 (FP3 CU5) lots lately. When it works then it's great but I've found troubleshooting problems with policy execution to be very difficult and wanted to check if anyone has found a better way.



      I'm using an orchestration CallRules shape to execute the policy. I've also created unit tests that call the policy with a DebugTrackingIntercerceptor. In the case of a successful policy execution, where rules fire, the debug info that's output looks something like:



      FACT ACTIVITY 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Operation: Assert
      Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.GetServiceRequestDetailsResponse:/*[local-name()='GetServiceRequestDetailsResponse']/*[local-name()='GetServiceRequestDetailsResult']/*[local-name()='Customer']/*[local-name()='ContactTransports']/*[local-name()='ContactTransport'][*[local-name()="Name" and .="Email"]]
      Object Instance Identifier: 9589157

      AGENDA UPDATE 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Operation: Add
      Rule Name: BartecUpdate
      Conflict Resolution Criteria: 0

      RULE FIRED 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Rule Name: BartecUpdate
      Conflict Resolution Criteria: 0

      FACT ACTIVITY 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Operation: Retract
      Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.CreateActivity
      Object Instance Identifier: 49478415


      Some of the rules within the policy check the value of certain elements of XML document facts. If, the asserted fact happens to have one of these elements missing (such as from the first rule in the activity debug info shown above), then there is no obvious indication of a problem from the tracking info. The only way to identify something's not right is if you notice that the rule did not fire. From here it's a matter of meticulously checking for the presence of elements used in each rule.



      Is there a better way to identify why a rule did not fire?










      share|improve this question
















      I've been using the BRE with BizTalk 2016 (FP3 CU5) lots lately. When it works then it's great but I've found troubleshooting problems with policy execution to be very difficult and wanted to check if anyone has found a better way.



      I'm using an orchestration CallRules shape to execute the policy. I've also created unit tests that call the policy with a DebugTrackingIntercerceptor. In the case of a successful policy execution, where rules fire, the debug info that's output looks something like:



      FACT ACTIVITY 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Operation: Assert
      Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.GetServiceRequestDetailsResponse:/*[local-name()='GetServiceRequestDetailsResponse']/*[local-name()='GetServiceRequestDetailsResult']/*[local-name()='Customer']/*[local-name()='ContactTransports']/*[local-name()='ContactTransport'][*[local-name()="Name" and .="Email"]]
      Object Instance Identifier: 9589157

      AGENDA UPDATE 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Operation: Add
      Rule Name: BartecUpdate
      Conflict Resolution Criteria: 0

      RULE FIRED 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Rule Name: BartecUpdate
      Conflict Resolution Criteria: 0

      FACT ACTIVITY 19/11/2018 07:59:12
      Rule Engine Instance Identifier: 7bbad914-92a1-4783-b81a-f0a4d993fa9a
      Ruleset Name: LCC.Corporate.NotificationService.BartecMissedBins
      Operation: Retract
      Object Type: TypedXmlDocument:Lcc.Integration.Corporate.CatsCrm.Schemas.CatsCrm_lcc_catscrm.CreateActivity
      Object Instance Identifier: 49478415


      Some of the rules within the policy check the value of certain elements of XML document facts. If, the asserted fact happens to have one of these elements missing (such as from the first rule in the activity debug info shown above), then there is no obvious indication of a problem from the tracking info. The only way to identify something's not right is if you notice that the rule did not fire. From here it's a matter of meticulously checking for the presence of elements used in each rule.



      Is there a better way to identify why a rule did not fire?







      biztalk business-rules biztalk-2016






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 23 '18 at 2:41









      Dijkgraaf

      7,39582744




      7,39582744










      asked Nov 19 '18 at 8:28









      Rob BowmanRob Bowman

      2,6191457110




      2,6191457110
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370842%2fbiztalk-bre-easier-troubleshooting%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53370842%2fbiztalk-bre-easier-troubleshooting%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          這個網誌中的熱門文章

          Xamarin.form Move up view when keyboard appear

          Post-Redirect-Get with Spring WebFlux and Thymeleaf

          Anylogic : not able to use stopDelay()