BizTalk Server Orchestration - 2 receive ports back to back

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > April 2005 > 2 receive ports back to back





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 2 receive ports back to back
Anthony Morgan

2005-04-16, 5:48 pm

Hi All;

I have an orachstration with 2 receive ports. The first recieve port will
have activation set to true, and tied to a file receive port.

The second recieve port will be assigned to a SQL server adapter receive
port that is tied to a stored procedure with no prameters. It's just pulling
statistics fom the database.

I am trying to set this up so that when the file arrives the orecstration
will activate, and receive from the stored procedure. I'll then use the
result from the 2 message to contrauct a 3rd.

My problem is, I can't get biztalk to compile with 2 receive ports. I get
the message: "you must specify at least one already-initialized correlation
set for a non-activation receive that is on a non-selfcorrelating port"

I have the activate set to true on the first receive, and false on the second.
I tried to set up a convory, but I get the message: "in a sequential convoy
receive the ports must be identical"

I'm not sure what to do here. Can I even have 2 receive ports in an
orchastration without using correlation?

Thanks




Jon Flanders[MVP]

2005-04-16, 8:46 pm

To answer one question - You are correct - in order to have two receive
ports in an orchestration you must use correlation.

To answer the other question - you don't want two receive ports. You want a
SQL send port instead of the SQL receive port. You can call a stored proc
with no parameters from a send, and get back a response to process inside of
your orchestration.

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

"Anthony Morgan" <AnthonyMorgan@discussions.microsoft.com> wrote in message
news:D2AAE9A5-6C19-44C2-9068-96466BB6063B@microsoft.com...
> Hi All;
>
> I have an orachstration with 2 receive ports. The first recieve port will
> have activation set to true, and tied to a file receive port.
>
> The second recieve port will be assigned to a SQL server adapter receive
> port that is tied to a stored procedure with no prameters. It's just
> pulling
> statistics fom the database.
>
> I am trying to set this up so that when the file arrives the orecstration
> will activate, and receive from the stored procedure. I'll then use the
> result from the 2 message to contrauct a 3rd.
>
> My problem is, I can't get biztalk to compile with 2 receive ports. I get
> the message: "you must specify at least one already-initialized
> correlation
> set for a non-activation receive that is on a non-selfcorrelating port"
>
> I have the activate set to true on the first receive, and false on the
> second.
> I tried to set up a convory, but I get the message: "in a sequential
> convoy
> receive the ports must be identical"
>
> I'm not sure what to do here. Can I even have 2 receive ports in an
> orchastration without using correlation?
>
> Thanks
>
>
>
>



Anthony Morgan

2005-04-20, 5:49 pm

Ok,

If I understand this correctly, my port is going to be a send response
port. I created a new schema for the stored procedure with a
responce and request node. I have ties the send to the request
message, and the response to the response message.

Now I'm getting the stupidest error. the request message has not been
created. I have not idea how to create a message that isn't really a
data containing item. I've done it with a dummy Map, but is there a
better way? or is there another way to set up the send port witha
different type of message?

Thanks

On Sat, 16 Apr 2005 17:48:53 -0700, "Jon Flanders[MVP]"
<jon.flanders@gmail.com> wrote:

>To answer one question - You are correct - in order to have two receive
>ports in an orchestration you must use correlation.
>
>To answer the other question - you don't want two receive ports. You want a
>SQL send port instead of the SQL receive port. You can call a stored proc
>with no parameters from a send, and get back a response to process inside of
>your orchestration.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com