|
Home > Archive > BizTalk Server Orchestration > November 2004 > Receive > Process > Send in same order as received?
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 |
Receive > Process > Send in same order as received?
|
|
| Martin Hellspong 2004-11-24, 5:52 pm |
| How do I make sure that messages are received, processed, and sent out in the
same order as they are received?
We have a website where customers can do several actions, A, B, C, D in any
order and combination (creating messages ActionA, ActionB etc.). Before doing
any actions, however, the customer must first register, creating a
CustomerRegistrationMessage.
When returning to the website later, the customer can do more actions,
without having to register.
The messages arrive in the correct order to BizTalk (the same MSMQT receive
location), for example:
CustomerRegistrationMessage
ActionB
ActionA
(and then a month later)
ActionC
Currently there are one different Orchestration per Action, and one for the
registration. BizTalk does some fairly simple processing of the messages, and
then sends them on to a backend system (again using MSMQ/T). However, we
suspect that they are not always sent in the same order, i.e. an Action
generated by a new customer might arrive at the backend system before the
CustomerRegistrationMessage, making the backend system fail since the Action
refers to a Customer that has not been registred yet.
Any ideas how to solve the ordering problem? Maybe correlation could help me
here, but I do not see how it should be applied to this problem.
How do I get the Action-handling orchestrations to wait for the processing
of a registration message, that might have already passed through a month
ago... and also, even if the registration message is currently being
processed in parallell, how can the Action-handling orchestrations wait for
the registration message to been processed and sent, before continuing.
| |
| Alistair 2B.net 2004-11-25, 5:49 pm |
| Hi Martin
Funny that, we have just achieved something similar by using a parallel
shape in our orchestration that will wait until all the conditions have
been, this might not help you as all this does is process everything once
the conditions have been made.
Hope this helps
Aly
"Martin Hellspong" <MartinHellspong@discussions.microsoft.com> wrote in
message news:EC1C5C7F-48A3-4776-9616-97F8ACE612D1@microsoft.com...
> How do I make sure that messages are received, processed, and sent out in
> the
> same order as they are received?
>
> We have a website where customers can do several actions, A, B, C, D in
> any
> order and combination (creating messages ActionA, ActionB etc.). Before
> doing
> any actions, however, the customer must first register, creating a
> CustomerRegistrationMessage.
>
> When returning to the website later, the customer can do more actions,
> without having to register.
>
> The messages arrive in the correct order to BizTalk (the same MSMQT
> receive
> location), for example:
>
> CustomerRegistrationMessage
> ActionB
> ActionA
> (and then a month later)
> ActionC
>
> Currently there are one different Orchestration per Action, and one for
> the
> registration. BizTalk does some fairly simple processing of the messages,
> and
> then sends them on to a backend system (again using MSMQ/T). However, we
> suspect that they are not always sent in the same order, i.e. an Action
> generated by a new customer might arrive at the backend system before the
> CustomerRegistrationMessage, making the backend system fail since the
> Action
> refers to a Customer that has not been registred yet.
>
> Any ideas how to solve the ordering problem? Maybe correlation could help
> me
> here, but I do not see how it should be applied to this problem.
>
> How do I get the Action-handling orchestrations to wait for the processing
> of a registration message, that might have already passed through a month
> ago... and also, even if the registration message is currently being
> processed in parallell, how can the Action-handling orchestrations wait
> for
> the registration message to been processed and sent, before continuing.
|
|
|
|
|