When using biztalk webservices publishing wizard, I only see one
receiving port on the "orchestrations and ports" screen - even though
the orchestration has 2 receiving ports.

If I publish it as web service, only the active receiving port is
published, the other receiving port is ignored.

Anyone run into this before or point me to the right steps for
publishing an orchestration with multiple receiving ports?

thanks in advance.

[ Post a follow-up to this message ]

Hi Michael,

> When using biztalk webservices publishing wizard, I only see one
> receiving port on the "orchestrations and ports" screen - even though
> the orchestration has 2 receiving ports.
>
> If I publish it as web service, only the active receiving port is
> published, the other receiving port is ignored.
>
> Anyone run into this before or point me to the right steps for
> publishing an orchestration with multiple receiving ports?

What exactly is it that you wish to accomplish? A single webservice with an
operation for each receive port in the orchestration? This might very well
be possible, by using the webpublishing wizard twice, and then hand-merging
the code for generated webservices.

That said, this might suggest that the design is not the best. In this case,
instead of multiple receive ports, I might go with a single receive port
with multiple operations, which would give the expected result (think of
ports in orchestrations as services as defined by WSDL, rather that
something that maps to a receive or send port, and it all makes a little bit
more sense).


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Are both Port Types public?

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

Hi Michael,

> When using biztalk webservices publishing wizard, I only see one
> receiving port on the "orchestrations and ports" screen - even though
> the orchestration has 2 receiving ports.
>
> If I publish it as web service, only the active receiving port is
> published, the other receiving port is ignored.
>
> Anyone run into this before or point me to the right steps for
> publishing an orchestration with multiple receiving ports?

What exactly is it that you wish to accomplish? A single webservice with an
operation for each receive port in the orchestration? This might very well
be possible, by using the webpublishing wizard twice, and then hand-merging
the code for generated webservices.

That said, this might suggest that the design is not the best. In this case,
instead of multiple receive ports, I might go with a single receive port
with multiple operations, which would give the expected result (think of
ports in orchestrations as services as defined by WSDL, rather that
something that maps to a receive or send port, and it all makes a little bit
more sense).

[ Post a follow-up to this message ]

If you want two webmethods from two different orchestrations or different
ports you can do this by running the wizard code in a custom way.  This
sample
http://staff.develop.com/jfland/Per...a
32c922
does exactly that (it creates one asmx with N webmethods  instead of one
asmx per Port)

--
Jon Flanders [DevelopMentor]
http://staff.develop.com/jfland/
http://www.develop.com/courses/biztalk
"Tomas Restrepo (MVP)" <tomasr@mvps.org> wrote in message
news:%23F9CaEKMFHA.3356@TK2MSFTNGP12.phx.gbl...
> Hi Michael,
> 
>
> What exactly is it that you wish to accomplish? A single webservice with
> an
> operation for each receive port in the orchestration? This might very well
> be possible, by using the webpublishing wizard twice, and then
> hand-merging
> the code for generated webservices.
>
> That said, this might suggest that the design is not the best. In this
> case,
> instead of multiple receive ports, I might go with a single receive port
> with multiple operations, which would give the expected result (think of
> ports in orchestrations as services as defined by WSDL, rather that
> something that maps to a receive or send port, and it all makes a little
> bit
> more sense).
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/
>
>
>

[ Post a follow-up to this message ]

You hit the nail on its head Richard, I redid a sample with both ports
set as public and the wizards picked up both ports. It's good to have
an answer from someone who knows what he is talking about.

Thanks

Richard Blewett [DevelopMentor] wrote:
> Are both Port Types public?
>
>  Regards
>
>  Richard Blewett - DevelopMentor
>  http://www.dotnetconsult.co.uk/weblog
>  http://www.dotnetconsult.co.uk
>
>    Hi Michael,
> 
though[vbcol=seagreen] 
>
>  What exactly is it that you wish to accomplish? A single webservice
with an
>  operation for each receive port in the orchestration? This might
very well
>  be possible, by using the webpublishing wizard twice, and then
hand-merging
>  the code for generated webservices.
>
>  That said, this might suggest that the design is not the best. In
this case,
>  instead of multiple receive ports, I might go with a single receive
port
>  with multiple operations, which would give the expected result
(think of
>  ports in orchestrations as services as defined by WSDL, rather that
>  something that maps to a receive or send port, and it all makes a
little bit
>  more sense).

[ Post a follow-up to this message ]