How do i redeploy a biztalk projects with correlations w/o stopping
existing instances of running orchestrations?

Background: Our process has correlations with possible wait shapes
greater than 4 days. We got ~ 1000 new orchestration instances each
day, so there are always ~ 100 running wait instances around.

Now our customer wants e.g. a new send port for another billing (or
something which can't be handled by a simple assembly update), which
results in a redeployment (unenlist and stop all orchestrations,
undeploy the assemblies, redeploy them).

So how do i restart the 100 already running instances, which i needed
to kill in order to update? Are correlations really unupdateable (in
the meaning of adding a send or receive port)?

[ Post a follow-up to this message ]

Christian

In theory you should beable to leave the current ochestrations running and
redeploy your changes, It is my understanding and i'm probably wrong that if
you increase the version number of the next deployment the current running
ochestrations will use the old version and the new orchestrations will start
by using the new version.  My understanding is that you can rebuild your
orchestration and redeploy.

Cheers

Aly !

"Christian Birkl" <Christian.Birkl@gmail.com> wrote in message
news:9b71a2e8.0411280546.50c22a6b@posting.google.com...
> How do i redeploy a biztalk projects with correlations w/o stopping
> existing instances of running orchestrations?
>
> Background: Our process has correlations with possible wait shapes
> greater than 4 days. We got ~ 1000 new orchestration instances each
> day, so there are always ~ 100 running wait instances around.
>
> Now our customer wants e.g. a new send port for another billing (or
> something which can't be handled by a simple assembly update), which
> results in a redeployment (unenlist and stop all orchestrations,
> undeploy the assemblies, redeploy them).
>
> So how do i restart the 100 already running instances, which i needed
> to kill in order to update? Are correlations really unupdateable (in
> the meaning of adding a send or receive port)?

[ Post a follow-up to this message ]

You need to use assembly versioning - check out
ms-help://BTS_2004/Deploying/htm/ebiz_depl_assemblies_wqzo.htm  in the
documentation (title is "Deploying a New Assembly Version to Run Side by
Side with an Existing Assembly Version").

"Christian Birkl" <Christian.Birkl@gmail.com> wrote in message
news:9b71a2e8.0411280546.50c22a6b@posting.google.com...
> How do i redeploy a biztalk projects with correlations w/o stopping
> existing instances of running orchestrations?
>
> Background: Our process has correlations with possible wait shapes
> greater than 4 days. We got ~ 1000 new orchestration instances each
> day, so there are always ~ 100 running wait instances around.
>
> Now our customer wants e.g. a new send port for another billing (or
> something which can't be handled by a simple assembly update), which
> results in a redeployment (unenlist and stop all orchestrations,
> undeploy the assemblies, redeploy them).
>
> So how do i restart the 100 already running instances, which i needed
> to kill in order to update? Are correlations really unupdateable (in
> the meaning of adding a send or receive port)?

[ Post a follow-up to this message ]