Home Page › Forums › BizTalk 2004 – BizTalk 2010 › BRE: Major League Frustration! Someone PLEASE Shine a LIGHT on ME!:-)
- This topic has 3 replies, 1 voice, and was last updated 9 years, 10 months ago by
community-content.
-
AuthorPosts
-
-
November 16, 2007 at 1:24 PM #18449
Hello Techies–
I’ve tried every trick I know to fully qualify the type name for the xml vocabulary elements in the rule composer–for whatever reason, when I try to call the rule from an orchestration, i can select the policy, but cannot configure it with the paramter assignments.
In the rule composer I have the schema fully qualified. I’ve made sure the arguments in the rule are actually pointing to the correct version of the vocabulary. I’ve published the policies without deploying. I’ve deployed them. I’ve created new versions of the same thing changing the order to see if that mattered. Still the same results. I am missing some kind of binding–but I simply can’t find it. Is there an error message somewhere that is getting written out that might help me determine the issue? (read: I’ve even checked the event logger)
If any of you have been down this road before, please advise.
-
November 18, 2007 at 11:35 PM #18453
Hi Other Techy,
it’s really important to get the root name of the xml type correct. You set this in the properties of the schema. Did you set this, and are you using it?
John D.
-
November 19, 2007 at 9:49 AM #18459
John D.
Thanks so much for responding. I will check this now. The short answer is “I don’t know.” I tried so many different things–that this may have been one of the things I did–and perhaps even un-did in my quest for success!:-)
-
November 21, 2007 at 11:31 AM #18477
Hello All (With Special Thanks to John D.) —
For the problem I posted about the absent parameters under the policy when configuring the Call Rules shape in an orchestration, John D’s comment about the importance of fully qualifying the XML elements when either defining a vocabulary OR directly going from the schema with a drag/drop to the rule instruction window can’t be emphasized enough. I basically had a version of the XSD which was NOT included in my BTS project which I used when I developed the vocabulary. Although that XSD was fully qualified–it was NOT fully qualified for the correct project. Here’s I solved my woes: I deleted the schema. I imported the xml–converting it to an XSD. I included the new XSD as part of the project. I went to the Rule Composer–creating a new Policy and Rule, this time when including the schema fact, I included the XSD under the BTS project. I saved, published and deployed the policy/rule. I went back to the BTS project and configured the Call Rule shape–using the new policy. Viola! There were my parameters!
Now, there was hint I wasn’t fully qualifying things all along correctly–had I paid more attention to the EXACT name that was following my drag/drops from the schema to the rule instruction window–but in my frustration with it, I just didn’t notice. The vocabulary definition would have been harder to pickup–so if anyone out there has a similar problem, try debugging your quailfier by creating a new policy/rule and browsing on the XSD. Drag/drop DIRECTLY from the elements to the rule you are trying to create. The parameter will either bring over what you are expecting–or like me, you will discover that the qualifier is incorrect.
-
-
-
-
AuthorPosts
- The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.