|
Home > Archive > BizTalk Server Orchestration > October 2004 > How to handle non-correlated messages?
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 |
How to handle non-correlated messages?
|
|
|
| Hi everyone,
If I have a message1 (activate) receive shape which initialises a
correlation set, followed by a message2 receive shape which follows that
correlation set, is there a neat way to handle any message2's which are not
correlated to a message1? ie. for them to be picked up by the same
correlation (perhaps a new instance), but for processing to begin from the
point of the message2 receive. Both message1 and message2 are files. This
problem's driving me crazy, so any answers would be more than welcome!
Many thanks!
| |
| Stephen W. Thomas 2004-10-25, 5:48 pm |
| You might want to look at a convoy. This will allow multiple Message 2’s to
be processed by one Orchestration. I have some samples on my blog.
Although, listening to what you want to do doesn’t really sound like this
would work for you. It sounds like you want a “catch all” to catch messages
with no subscription. I do not know a good want to do that off hand other
then to have a convoy what will do routing for you.
Hope this helps.
Stephen W. Thomas
http://www.geekswithblogs.net/sthomas
"GAT" wrote:
> Hi everyone,
>
> If I have a message1 (activate) receive shape which initialises a
> correlation set, followed by a message2 receive shape which follows that
> correlation set, is there a neat way to handle any message2's which are not
> correlated to a message1? ie. for them to be picked up by the same
> correlation (perhaps a new instance), but for processing to begin from the
> point of the message2 receive. Both message1 and message2 are files. This
> problem's driving me crazy, so any answers would be more than welcome!
>
> Many thanks!
>
>
| |
|
| Thanks for your response Stephen.
Yes, I need to handle messages with no subscription. A Message2 might be
received for which there is no Message1, but my orchestration still needs to
process it (albeit in a slightly different way). 99% of the time, there will
be a message1 and a message2, and a correlation between the two. They're
received into the same location as the (file-based) subscripted messages.
I've searched long and hard for a solution to this, and no-one seems to have
an answer. What really puzzles me is that surely this requirement is not so
outrageous that Microsoft didn't think of a way of coping with it? I'm sure
there must be an answer from somewhere. This solution is needed to support
critical business operations, and we can't ignore messages just because they
have no subscription.
Calling all Biztalk geniuses... please - can anyone shed some light on this???
|
|
|
|
|