|
Home > Archive > BizTalk Server Orchestration > March 2005 > Biztalk query
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]
|
|
| Abhishek 2005-03-03, 5:53 pm |
| Hi
I am creating an orchestration and exposing it as webservice but I am
facing some problem, can you help me with this ?
1) I created two Schema - BizPartnerInfo, MoreBizPartnerInfo.xsd and
promoted its properties BizPartnerID through the same property schema
and created an correlation set for the same.
2) I created an request - response port AddBizPartnerPort.
3) Now through a recivee shape (Receive1) I recd an instance of
BizPartnerInfo.xsd through the AddBizPartnerPort.
4) Did some operation and sent an response through a send shape
(Send1) the AddBizPartnerPort and initialized the correlation set.
5) After doing all this, in the same orchestration I received an
instance of MoreBizPartnerInfo.xsd through AddMoreInfoPort and
setting the following correlation set.
6) Set the transaction of orchestration as long running.
6) I exposed the web service, created ports and started orchestration.
7) The first port request-response works fine but when I try to invoke
the webservice function for the second port from biztalk does not
recognizes the promoted property and thus the message is not
associated with the orchestration.
(Could not find a matching subscription for the message. )
8) I tried to track the messages through the HAT and found that the
promoted properties work fine for the first port's request and
response but the promoted properties do not appear for the second
schema. I thoroughly checked the second schema seem and property
promotion looks fine.
Can any body please tell, what may be wrong ?
Thanks
Abhishek
abhisheksaraswat@gmail.com
| |
| Matt Milner 2005-03-03, 8:46 pm |
| Are you using the xmlreceive pipeline on your web service receive location?
If so, you might want to check on that property promotion. Try receving the
same message from a file receive and see if the properties get promoted.
Also, try saving your message out to disk and checking it for structure and
to make sure your promoted property is in it. (Right click in hat and save
message).
Matt
"Abhishek" <abhisheksaraswat@gmail.com> wrote in message
news:cfc59162.0503030615.494710f3@posting.google.com...
> Hi
>
> I am creating an orchestration and exposing it as webservice but I am
> facing some problem, can you help me with this ?
>
> 1) I created two Schema - BizPartnerInfo, MoreBizPartnerInfo.xsd and
> promoted its properties BizPartnerID through the same property schema
> and created an correlation set for the same.
>
> 2) I created an request - response port AddBizPartnerPort.
>
> 3) Now through a recivee shape (Receive1) I recd an instance of
> BizPartnerInfo.xsd through the AddBizPartnerPort.
>
> 4) Did some operation and sent an response through a send shape
> (Send1) the AddBizPartnerPort and initialized the correlation set.
>
> 5) After doing all this, in the same orchestration I received an
> instance of MoreBizPartnerInfo.xsd through AddMoreInfoPort and
> setting the following correlation set.
>
> 6) Set the transaction of orchestration as long running.
>
> 6) I exposed the web service, created ports and started orchestration.
>
> 7) The first port request-response works fine but when I try to invoke
> the webservice function for the second port from biztalk does not
> recognizes the promoted property and thus the message is not
> associated with the orchestration.
>
> (Could not find a matching subscription for the message. )
>
> 8) I tried to track the messages through the HAT and found that the
> promoted properties work fine for the first port's request and
> response but the promoted properties do not appear for the second
> schema. I thoroughly checked the second schema seem and property
> promotion looks fine.
>
> Can any body please tell, what may be wrong ?
>
> Thanks
> Abhishek
> abhisheksaraswat@gmail.com
| |
| Ben Cuttriss 2005-03-07, 5:49 pm |
| It's also useful to check in the PropertySchema.xsd to make sure only one
element was created / promoted. Elements are case sensitive so I often see
things like...
- <xs:element name="SessionId" type="xs:string">
- <xs:annotation>
- <xs:appinfo>
<b:fieldInfo propertyGuid="044b416a-752c-4ff9-ab6a-1a6f3e6cc348" />
</xs:appinfo>
</xs:annotation>
</xs:element>
- <xs:element name="SessionID" type="xs:int">
- <xs:annotation>
- <xs:appinfo>
<b:fieldInfo propertyGuid="cb7945c2-cde9-42c7-9e87-43d74e543620" />
</xs:appinfo>
</xs:annotation>
</xs:element>
It all looks OK - except there are two fields!! Note they are called
SessionID and SessionId. There should only be one. If a correlation was
setup on SessionID, it would lose one expecting SessionId. Make sure you
clean up the PropertySchema as well after you've fixed the naming in the
original schemas and re-promoting.
This is basically another way to check what Matt is already recommending.
Regards
Ben Cuttriss
"Matt Milner" wrote:
> Are you using the xmlreceive pipeline on your web service receive location?
> If so, you might want to check on that property promotion. Try receving the
> same message from a file receive and see if the properties get promoted.
> Also, try saving your message out to disk and checking it for structure and
> to make sure your promoted property is in it. (Right click in hat and save
> message).
>
> Matt
>
>
> "Abhishek" <abhisheksaraswat@gmail.com> wrote in message
> news:cfc59162.0503030615.494710f3@posting.google.com...
>
>
>
| |
| Abhishek 2005-03-10, 7:47 am |
| I tried receiving it through the file receive(xml receive pipeline)
and it worked fine. But I need to make it work through the Webservice
(xml receive pipeline) which is not working for me.
"Matt Milner" <matt.milner@m3technologypartners dot com> wrote in message news:<ODWw7BGIFHA.1860@TK2MSFTNGP15.phx.gbl>...
> Are you using the xmlreceive pipeline on your web service receive location?
> If so, you might want to check on that property promotion. Try receving the
> same message from a file receive and see if the properties get promoted.
> Also, try saving your message out to disk and checking it for structure and
> to make sure your promoted property is in it. (Right click in hat and save
> message).
>
> Matt
| |
| Abhishek 2005-03-10, 7:47 am |
| Hi Ben,
Thanks for the suggestion, I tried doing it with the File receive
location and the same messages and message type worked fine. So I dont
think that there is any problem with the property promotion.
I guess the issue is with the webservice port. The biztalk server does
not reads the field as a promoted property.
One more thing, Can you tell me how do I save the incoming message /
suspended message to a file.
Thanks
Abhishek (abhisheksaraswat@gmail.com)
----------------------------------------------------
Ben Cuttriss <BenCuttriss@discussions.microsoft.com> wrote in message news:<7CC7DEB2-A796-44BD-988C-A8CF64FC2912@microsoft.com>...[vbcol=seagreen]
> It's also useful to check in the PropertySchema.xsd to make sure only one
> element was created / promoted. Elements are case sensitive so I often see
> things like...
>
> - <xs:element name="SessionId" type="xs:string">
> - <xs:annotation>
> - <xs:appinfo>
> <b:fieldInfo propertyGuid="044b416a-752c-4ff9-ab6a-1a6f3e6cc348" />
> </xs:appinfo>
> </xs:annotation>
> </xs:element>
> - <xs:element name="SessionID" type="xs:int">
> - <xs:annotation>
> - <xs:appinfo>
> <b:fieldInfo propertyGuid="cb7945c2-cde9-42c7-9e87-43d74e543620" />
> </xs:appinfo>
> </xs:annotation>
> </xs:element>
>
> It all looks OK - except there are two fields!! Note they are called
> SessionID and SessionId. There should only be one. If a correlation was
> setup on SessionID, it would lose one expecting SessionId. Make sure you
> clean up the PropertySchema as well after you've fixed the naming in the
> original schemas and re-promoting.
>
> This is basically another way to check what Matt is already recommending.
> Regards
> Ben Cuttriss
>
> "Matt Milner" wrote:
>
[vbcol=seagreen]
| |
| Ben Cuttriss 2005-03-10, 8:48 pm |
| Abishek,
If you are using the XML receive pipeline on the 2nd "following correlation"
receive port, and it works fine if this is file, then I suggest you re-export
the web service again (maybe a different version is present) - recreate the
receive ports, set the pipeline to Xml Receive Pipeline and restart your
process, it should work.
Does it work if the second receive is a file receive? If it does, I can't
suggest anything else apart from above.
Let me know
Ben
"Abhishek" wrote:
> Hi Ben,
>
> Thanks for the suggestion, I tried doing it with the File receive
> location and the same messages and message type worked fine. So I dont
> think that there is any problem with the property promotion.
>
> I guess the issue is with the webservice port. The biztalk server does
> not reads the field as a promoted property.
>
>
> One more thing, Can you tell me how do I save the incoming message /
> suspended message to a file.
>
> Thanks
> Abhishek (abhisheksaraswat@gmail.com)
>
> ----------------------------------------------------
>
> Ben Cuttriss <BenCuttriss@discussions.microsoft.com> wrote in message news:<7CC7DEB2-A796-44BD-988C-A8CF64FC2912@microsoft.com>...
>
>
|
|
|
|
|