|
Home > Archive > BizTalk Server Orchestration > October 2004 > sequential convoy error
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 |
sequential convoy error
|
|
|
| Hi all,
simple question.
I am setting up a simple orchestration to correlate the reception of
the following 3 documents; Purchase Order, ASN and Invoice.
All of the messages are being dropped into a different directories,
in the above order.
Initally I had 3 different ports all watching a different directory
and linking these to a receive port. This received an error to the
effect that in a sequential convoy all receives must use the same port.
So I changed the recieve port to check just one directory and
included 3 operations to recieve each of the different types. The error
this time is 'in a sequential convoy receive the messagetypes must be
indential unless the port is marked for OrderedDelivery'. Obviously the
having the same types for my scenario is not useful and the only
concrete reference to the OrderedDelivery is in regard to MSMQ(I am
using the file watcher port).
Any ideas about what I am doing wrong or a better way to approach
this situation?
Regards
Mark Sargent
| |
|
| Sorted,
by selecting the binding to specify later, presented the option to
select the ordered delivery.
Mark wrote:
> Hi all,
> simple question.
> I am setting up a simple orchestration to correlate the reception of
> the following 3 documents; Purchase Order, ASN and Invoice.
> All of the messages are being dropped into a different directories, in
> the above order.
>
> Initally I had 3 different ports all watching a different directory
> and linking these to a receive port. This received an error to the
> effect that in a sequential convoy all receives must use the same port.
>
> So I changed the recieve port to check just one directory and included
> 3 operations to recieve each of the different types. The error this time
> is 'in a sequential convoy receive the messagetypes must be indential
> unless the port is marked for OrderedDelivery'. Obviously the having the
> same types for my scenario is not useful and the only concrete reference
> to the OrderedDelivery is in regard to MSMQ(I am using the file watcher
> port).
>
> Any ideas about what I am doing wrong or a better way to approach this
> situation?
>
> Regards
>
> Mark Sargent
|
|
|
|
|