BizTalk Server Orchestration - Problem to use more than 1 operation in a port

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > August 2005 > Problem to use more than 1 operation in a port





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 Problem to use more than 1 operation in a port
Fredrik

2005-08-25, 7:48 am

Hi,

I'm building a solution in BT2004 that is exposed as a webservice. When I am
adding more than 1 operation to the port (exposed as webservice) the
correlation does not work. BizTalk complains about more than one subscription
for the incoming message.

It works fine if I am using two ports instead of one port with two operations.

Tips how to deal with this would be very appreciated. I am surprised I
cannot find more info regarding this on the web, for me it should likely be a
common issue for everyone exposing the orchestration as web service.

Thanks,
Fredrik
Jon Flanders[MVP]

2005-08-25, 6:02 pm

Fredrik - I have also run into the problem. Although it is possible to
define one porty type with multiple operations - biztalk does get a little
confused.

What I ended up doing was to create one orchestration per operation. Then
to create the webservice endpoint I ran the wizard code programmactically -
http://www.masteringbiztalk.com/blo...2cda32c922.aspx
so I could create one ASMX with multiple operations.

HTH

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Fredrik" <Fredrik@discussions.microsoft.com> wrote in message
news:09D7A9C4-877C-4FD6-A417-B24E3C6DAF9F@microsoft.com...
> Hi,
>
> I'm building a solution in BT2004 that is exposed as a webservice. When I
> am
> adding more than 1 operation to the port (exposed as webservice) the
> correlation does not work. BizTalk complains about more than one
> subscription
> for the incoming message.
>
> It works fine if I am using two ports instead of one port with two
> operations.
>
> Tips how to deal with this would be very appreciated. I am surprised I
> cannot find more info regarding this on the web, for me it should likely
> be a
> common issue for everyone exposing the orchestration as web service.
>
> Thanks,
> Fredrik



Fredrik

2005-08-26, 5:55 pm

Jon, thans for your reply!

Yes, I am using same message type for all operations and now I realise that
the issue is because of this.

Do you know if it is possible to create a receive shape filter, filtering on
port operation name or id?


Thanks,
Fredrik



"Jon Flanders[MVP]" wrote:

> Fredrik - I have also run into the problem. Although it is possible to
> define one porty type with multiple operations - biztalk does get a little
> confused.
>
> What I ended up doing was to create one orchestration per operation. Then
> to create the webservice endpoint I ran the wizard code programmactically -
> http://www.masteringbiztalk.com/blo...2cda32c922.aspx
> so I could create one ASMX with multiple operations.
>
> HTH
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "Fredrik" <Fredrik@discussions.microsoft.com> wrote in message
> news:09D7A9C4-877C-4FD6-A417-B24E3C6DAF9F@microsoft.com...
>
>
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com