Hello,

I created a send port using Biztalk View of VS 2005. I used it in an
orchestration. Built and deployed the solution.

When I try to configure this application in Biztalk Admin, it asks me to
configure a new Send Port instead of using the existing send port. There is
no option to select an existing port during configuration of app in Biztalk
Admin.

I must be doing something wrong, but don't know what.

Developer

[ Post a follow-up to this message ]

Hi,
I bet you have used "Specify Later" (default) when creating new ports. If
you would have used "Specify Now" and filleed in all port data, nto only
your ports will be created when the app was deployed, but they will be also
bound to appropriate orchestration ports.

-- Michael


--------------------[vbcol=seagreen] 
is[vbcol=seagreen] 
Biztalk[vbcol=seagreen] 

[ Post a follow-up to this message ]

On Wed, 4 Oct 2006 12:04:10 -0700, "Developer"
<developer@developland.com> wrote:

>I created a send port using Biztalk View of VS 2005. I used it in an
>orchestration. Built and deployed the solution.
>
>When I try to configure this application in Biztalk Admin, it asks me to
>configure a new Send Port instead of using the existing send port. There is
>no option to select an existing port during configuration of app in Biztalk
>Admin.
>
>I must be doing something wrong, but don't know what.
Probably, the receiv eport you created in BizTalk Explorer in VS.NET
2005 isn't in the same "application" as the orchestration?

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@eliasen.dk

[ Post a follow-up to this message ]

It depends on the type of Logical send port you have created in your
orchestration,

Say you manually created a "Dynamic one way Sendport" assume 'DynOrderPort'
in Biztalk Admin Console and your Orchestration Logical Port binding is not
been set to "Dynamic".

Your 'DynOrderPort' will not be listed while configuring your Sendport in
Biztalk Admin console.

HTH,
Selvan.

"Developer" wrote:

> Hello,
>
> I created a send port using Biztalk View of VS 2005. I used it in an
> orchestration. Built and deployed the solution.
>
> When I try to configure this application in Biztalk Admin, it asks me to
> configure a new Send Port instead of using the existing send port. There i
s
> no option to select an existing port during configuration of app in Biztal
k
> Admin.
>
> I must be doing something wrong, but don't know what.
>
> Developer
>
>
>

[ Post a follow-up to this message ]

Jan,

When I use Biztalk Explorer view to create a Send port, there is no way to
specify application.

While using Siebel adapter one needs ports at design time (to browse and
select Siebel objects), and at run time (to actually send/receive data). I
was hoping to use the same port for both. There seems to be no way to do
that.

Developer

"Jan Eliasen" <eliasen@nospam.nospam> wrote in message
 news:va8di2992eoa09e7plc18f8tvdf1bk1qr8@
4ax.com...
> On Wed, 4 Oct 2006 12:04:10 -0700, "Developer"
> <developer@developland.com> wrote:
> 
> Probably, the receiv eport you created in BizTalk Explorer in VS.NET
> 2005 isn't in the same "application" as the orchestration?
>
> --
> eliasen, representing himself and not the company he works for.
>
> Private blog: http://blog.eliasen.dk
>
> Private email: jan@eliasen.dk

[ Post a follow-up to this message ]

On Mon, 9 Oct 2006 11:10:25 -0700, "Developer"
<developer@developland.com> wrote:

>When I use Biztalk Explorer view to create a Send port, there is no way to
>specify application.
True. This is why one should never use BizTalk Explorer for that sort
of thing :-) Always use the BizTalk server Administration Console for
this.

>While using Siebel adapter one needs ports at design time (to browse and
>select Siebel objects), and at run time (to actually send/receive data). I
>was hoping to use the same port for both. There seems to be no way to do
>that.
I am not getting what you mean. You create a physical send port in
order to browse Siebel objects. And then later you can't bind your
orchestration to that same port. Is that what you are experiencing?
You should definately be able to do that. But, as anothe rperson has
written in this thread, the physical port you create must match the
logical port in the orchestration, ie. both must be dynamic or both
must be send only or send-response and so on.

--
eliasen, representing himself and not the company he works for.

Private blog: http://blog.eliasen.dk

Private email: jan@eliasen.dk

[ Post a follow-up to this message ]