BTS2004... I am attempting a very simple orchestration which incorporates a
policy defined using the Business Rules Composer(BRC). The orchestration is
essentially a ReceiveXML -> BusinessRule -- SendXML structure.  The policy
simply chechs an <Age> tag and if greater than 21, sets the <Legal> that to
"true".  When I use the BRC to test the policy with an XML file, the <Legal>
tag is updated as expected.  No matter what I try for the orchestration, the
input and output XML are always identical.  I also tried using the Tutorial
Module 2 to perform this type or demo. Even for the step-by-step, using BRC
works; using orchestration does not.  Any thoughts?

Richard.

[ Post a follow-up to this message ]

Based upon info from HAT, there is no Fact Activity for the policy when run
through the orchestration.  Originally, a vocabulary based upon the xml
schema was used to build the policy.  I've since modified the policy to go
directly against the XML Schema.  Neither is producing any Fact Activity as
monitored by HAT.  Can anyone shed some light on what may be happening here?
Also, assuming this is a XPath naming issue, why does this policy work
correctly when I use the Business Rule Composer Test utility?

Richard.

"RichardO" wrote:

> BTS2004... I am attempting a very simple orchestration which incorporates 
a
> policy defined using the Business Rules Composer(BRC). The orchestration i
s
> essentially a ReceiveXML -> BusinessRule -- SendXML structure.  The policy
> simply chechs an <Age> tag and if greater than 21, sets the <Legal> that t
o
> "true".  When I use the BRC to test the policy with an XML file, the <Lega
l>
> tag is updated as expected.  No matter what I try for the orchestration, t
he
> input and output XML are always identical.  I also tried using the Tutoria
l
> Module 2 to perform this type or demo. Even for the step-by-step, using BR
C
> works; using orchestration does not.  Any thoughts?
>
> Richard.

[ Post a follow-up to this message ]

Yet more information...

HAT shows me one of the rules that does not fire as shown below:

IF
xml.CardHardOrchestration.License./root.Age is greater than or equal to 21
THEN
xml.CardHardOrchestration.License./root.IsLegal(true)

Notice the ./ between License and root.  This appears to be an incorrect
xpath structure, but I cannot find a way to correct this for the
orchestration.  I've manipulated the xpath selector and xpath field for the
Age and IsLegal properties in BRC, but nothing seems to work.  Can someone
give me an indication of what these two properties should read?  Keep ion
mind, the policy does work when using BRC's Test Policy... tool.

Thanks.

Richard.
"RichardO" wrote:
[vbcol=seagreen]
> Based upon info from HAT, there is no Fact Activity for the policy when ru
n
> through the orchestration.  Originally, a vocabulary based upon the xml
> schema was used to build the policy.  I've since modified the policy to go
> directly against the XML Schema.  Neither is producing any Fact Activity a
s
> monitored by HAT.  Can anyone shed some light on what may be happening her
e?
> Also, assuming this is a XPath naming issue, why does this policy work
> correctly when I use the Business Rule Composer Test utility?
>
> Richard.
>
> "RichardO" wrote:
> 

[ Post a follow-up to this message ]

Are you invoking a function of an assembly?



"RichardO" <RichardO@discussions.microsoft.com> wrote in message
news:11BD2ED7-AD94-465F-BA19-B4875B9DD8A8@microsoft.com...
> Yet more information...
>
> HAT shows me one of the rules that does not fire as shown below:
>
> IF
> xml.CardHardOrchestration.License./root.Age is greater than or equal to 21
> THEN
> xml.CardHardOrchestration.License./root.IsLegal(true)
>
> Notice the ./ between License and root.  This appears to be an incorrect
> xpath structure, but I cannot find a way to correct this for the
> orchestration.  I've manipulated the xpath selector and xpath field for
the[vbcol=seagreen]
> Age and IsLegal properties in BRC, but nothing seems to work.  Can someone
> give me an indication of what these two properties should read?  Keep ion
> mind, the policy does work when using BRC's Test Policy... tool.
>
> Thanks.
>
> Richard.
> "RichardO" wrote:
> 
run[vbcol=seagreen] 
go[vbcol=seagreen] 
as[vbcol=seagreen] 
here?[vbcol=seagreen] 
incorporates a[vbcol=seagreen] 
orchestration is[vbcol=seagreen] 
policy[vbcol=seagreen] 
that to[vbcol=seagreen] 
<Legal>[vbcol=seagreen] 
orchestration, the[vbcol=seagreen] 
Tutorial[vbcol=seagreen] 
using BRC[vbcol=seagreen] 

[ Post a follow-up to this message ]

David,

I'm not sure what you're meaning.  When using the orchestration, I'm using
the call business rule component within a scope component to invoke the
business rule.  None of the variable within the business rule are resolving
properly.

Ironically, this business rule can be invoked from other tools like the
Business Rule Composer and also including an SDK application that does
nothing but invoke the rule.  Within th enext week or two, we'll be building
a new BizTalk server environment and I'll retry it then through
orchestration.  It may be something with this BTS installation.  At this
point though, we're just working around it by building the business rule cal
l
into a web service and invoking the service when needed.  It would definitel
y
be a lot nicer to be able to use the BTS component rather than custom code,
but I guess the world's not perfect.  However, if you think of anything that
may cause this or want to take a look at this rule and orchestration, please
let me know.

Thanks.

Richard.

"David" wrote:

> Are you invoking a function of an assembly?
>
>
>
> "RichardO" <RichardO@discussions.microsoft.com> wrote in message
> news:11BD2ED7-AD94-465F-BA19-B4875B9DD8A8@microsoft.com... 
> the 
> run 
> go 
> as 
> here? 
> incorporates a 
> orchestration is 
> policy 
> that to 
> <Legal> 
> orchestration, the 
> Tutorial 
> using BRC 
>
>
>

[ Post a follow-up to this message ]