|
Home > Archive > BizTalk Server Orchestration > April 2005 > Rule does not fire
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Rule does not fire
|
|
| Michael Krok 2005-04-14, 2:49 am |
| I think I did everything correctly but I must be missing something. I
created a bunch of vocabularies from an XML schema (constants, and XML
attributes get and set). Created a policy and one rule. The Rule checks
values from the fact location (input xml document). When I test the rule in
the Rule composer using the given input document the rule fires and all of
my attributes are updated with their new values as expected.
I deployed the policy and created a simple orchestration with a Receive,
Call Rules, and Send shapes, bound to messaging port and rec loc. The
policy is available in the orchestraiopn designer and I can build and deploy
the orchestration just fine. When I send in a file, the orchestraion
executes and the file is written out the other side. The output document
does not get updated. When I look in HAT, the rule is listed in the "not
fired" list.
Am I missing something?
Thanks in advance
mike
| |
| Matt Milner 2005-04-14, 8:46 pm |
| What else is listed in the rule tracking? What conditions were evaluated?
Can you see that any facts were unrecognized?
matt
"Michael Krok" <TheDuck@nospam.newsgroup.com> wrote in message
news:ehrU7TMQFHA.648@TK2MSFTNGP14.phx.gbl...
>I think I did everything correctly but I must be missing something. I
>created a bunch of vocabularies from an XML schema (constants, and XML
>attributes get and set). Created a policy and one rule. The Rule checks
>values from the fact location (input xml document). When I test the rule
>in the Rule composer using the given input document the rule fires and all
>of my attributes are updated with their new values as expected.
>
> I deployed the policy and created a simple orchestration with a Receive,
> Call Rules, and Send shapes, bound to messaging port and rec loc. The
> policy is available in the orchestraiopn designer and I can build and
> deploy the orchestration just fine. When I send in a file, the
> orchestraion executes and the file is written out the other side. The
> output document does not get updated. When I look in HAT, the rule is
> listed in the "not fired" list.
>
> Am I missing something?
>
> Thanks in advance
> mike
>
| |
| Michael Krok 2005-04-15, 2:48 am |
| Thanks for responding Matt
"Rule Tracking" - sorry for the ignorance but this is my first rule.
When I go into the message flow in HAT, and select "Policy Execution
Details" for that message the results are:
Fact Activity - none
Rules that Fired - none
Rules that did not Fire - My one and only rule was reported
Conditions Evaluated - none
Agenda Updates - none
Now when I execute the policy from the Rules Composer against a test file,
it works and I can see the trace evaluating all conditions and updating the
data as expected. Basicly playing nice. That is why I feel that I must be
missing something between the orchestration and policy. I don't know what
the difference is. I always used to apply business logic in the map, but
I'm trying to just do the right thing!
Waitng anxiously for your direction. :-)
Michael Krok
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:eCGpjvVQFHA.1476@TK2MSFTNGP09.phx.gbl...
> What else is listed in the rule tracking? What conditions were evaluated?
> Can you see that any facts were unrecognized?
>
> matt
>
>
> "Michael Krok" <TheDuck@nospam.newsgroup.com> wrote in message
> news:ehrU7TMQFHA.648@TK2MSFTNGP14.phx.gbl...
>
>
| |
| Matt Milner 2005-04-16, 2:47 am |
| did you successfully setup the parameters in the Call Rule shape to pass in
your xml document?
It looks as if you didn't have all of the necessary facts to do evaluations.
This usually means a fact is missing. In your case it seems like the XML
document is the only fact, is that correct? Are you using an .Net classes
or database facts in your rules?
if you could not select the message to pass in, this is usually caused by
not fully qualifying the schema name in the business rule composer when
creating vocabulary. The document type defaults to the typename of the
schema, but it needs to include the namespace name as well. So, when you
create a vocabulary item, you have something like MyNamespace.MyDocumentType
for the document type.
HTH,
Matt
"Michael Krok" <TheDuck@nospam.newsgroup.com> wrote in message
news:O1VLflWQFHA.3336@TK2MSFTNGP09.phx.gbl...
> Thanks for responding Matt
>
> "Rule Tracking" - sorry for the ignorance but this is my first rule.
>
> When I go into the message flow in HAT, and select "Policy Execution
> Details" for that message the results are:
> Fact Activity - none
> Rules that Fired - none
> Rules that did not Fire - My one and only rule was reported
> Conditions Evaluated - none
> Agenda Updates - none
>
> Now when I execute the policy from the Rules Composer against a test file,
> it works and I can see the trace evaluating all conditions and updating
> the data as expected. Basicly playing nice. That is why I feel that I
> must be missing something between the orchestration and policy. I don't
> know what the difference is. I always used to apply business logic in the
> map, but I'm trying to just do the right thing!
>
> Waitng anxiously for your direction. :-)
>
> Michael Krok
>
> "Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
> news:eCGpjvVQFHA.1476@TK2MSFTNGP09.phx.gbl...
>
>
| |
| Michael Krok 2005-04-16, 5:48 pm |
| Ok - without looking at it....
#1 - I know I did not set a parameter to pass in from the rules shape. I
don't remember seeing an option. I'll check that one out. If I can see one
available, then that should be step 1.
#2 - I am only using the XML document as a fact. I'm not using a .NET class
or DB in my rule.
As far as the fully qualified schema goes; am I to assume that from the
Rules Composer I need to select a deployed BizTalk assembly that includes
the schema I'm using? I created my vocabularies from the same "schema" on
the file system, not one out of an assembly albeit they are identical.
I'll check these things out and report back. Thanks alot.
Mike
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:eyllq8jQFHA.3076@tk2msftngp13.phx.gbl...
> did you successfully setup the parameters in the Call Rule shape to pass
> in your xml document?
> It looks as if you didn't have all of the necessary facts to do
> evaluations. This usually means a fact is missing. In your case it seems
> like the XML document is the only fact, is that correct? Are you using an
> .Net classes or database facts in your rules?
>
> if you could not select the message to pass in, this is usually caused by
> not fully qualifying the schema name in the business rule composer when
> creating vocabulary. The document type defaults to the typename of the
> schema, but it needs to include the namespace name as well. So, when you
> create a vocabulary item, you have something like
> MyNamespace.MyDocumentType for the document type.
>
> HTH,
> Matt
>
>
>
> "Michael Krok" <TheDuck@nospam.newsgroup.com> wrote in message
> news:O1VLflWQFHA.3336@TK2MSFTNGP09.phx.gbl...
>
>
| |
| Michael Krok 2005-04-16, 8:46 pm |
| Well it worked!! Thanks
I did not have the fully qualified name in the vocabularies and I did not
have the message set as a parameter to the policy. I actually should have
tried to set the parameter before I made the changes to my vocabulary and
rules to see if it would work but I didn't. So it was either one eor the
other.
The one thing I can't understand is why my test document now fails when I
test hte rule from Rules Composer. Before I made these changes the test
document was updated after I ran the test. Now it does not update until I
run it throught the orchestration. This must be a version 1.0 feature. Any
ideas would be appreciated but I think I'm on the right track now.
Thanks Again Matt
Michael Krok
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message
news:eyllq8jQFHA.3076@tk2msftngp13.phx.gbl...
> did you successfully setup the parameters in the Call Rule shape to pass
> in your xml document?
> It looks as if you didn't have all of the necessary facts to do
> evaluations. This usually means a fact is missing. In your case it seems
> like the XML document is the only fact, is that correct? Are you using an
> .Net classes or database facts in your rules?
>
> if you could not select the message to pass in, this is usually caused by
> not fully qualifying the schema name in the business rule composer when
> creating vocabulary. The document type defaults to the typename of the
> schema, but it needs to include the namespace name as well. So, when you
> create a vocabulary item, you have something like
> MyNamespace.MyDocumentType for the document type.
>
> HTH,
> Matt
>
>
>
> "Michael Krok" <TheDuck@nospam.newsgroup.com> wrote in message
> news:O1VLflWQFHA.3336@TK2MSFTNGP09.phx.gbl...
>
>
|
|
|
|
|