Serialized orchestration instance during deployment new version of orchestration.

08-16-07, 09:01 AM

amit chaudhary

Hi All,

I have scenario where orchestration has a long running transaction
that some times takes 15 day to complete. I have developed the
orchestration and orchestration is working fine.

In future if I will modify the orchestration and redeploy again on
production, what will happened with the Orchestration instance that
are serialized. Will serialized orchestration instance work fine with
new version?

I am confused how serialized orchestration instance should be treated.

Can any one please help me?

Thanks in Advance

Regards
Amit chaudhary

08-16-07, 09:31 AM

Randal van Splunteren

Hello amit,

Have a look at the BPM Solution in the BizTalk 2006 documentation. In this
scenario a decoupled orchestration pattern is used to be able to do business
process versioning.
I think this might help you.

You can find the scenario in the Biztalk help: planning and architecture
\ Scenarios for Business Solutions \ Business Process Management Solution

or online:

http://msdn2.microsoft.com/en-us/library/aa559473.aspx

HTH,

Randal van Splunteren
Aviva Solutions
[..]

08-17-07, 01:58 AM

Richard Seroter

So let's say you indeed version the orchestration assembly and deploy it.
Now, you'd see two orchestrations in the application. You would unenlist the
"old" one, and enlist the new one. All new messages will process through the
new orchestration only.

For any currently running/dehydrated orchestrations, they will complete
their cycle with the OLD version. That's why you can't delete the old
orchestration while there are currently pending operations that use it.

Hope that helps.

08-17-07, 07:31 AM

amit chaudhary

Hi Richard,

As per my understanding, both old and new orchestration will run
together. I will unenlist physical receive port from old orchestration
and enlist the port to new orchestration. Now all new messages will be
processed by new orchestration only.

I am confused with send port. I suppose I have to enlist send port to
both orchestrations in my scenario because both old and new
orchestration should able to use same physical send port.

Can I share one send port with in two orchestrations? I have one more
query, Can I share physical receive port with in two orchestration.

Thanks for such a good assistance.

Regards
Amit

On Aug 17, 5:58 am, Richard Seroter
<RichardSero> wrote:
[..]

08-17-07, 07:39 AM

amit chaudhary

Hi Randal,

First of all thanks for such a good assistance.

I haven't read that example before but yesterday I read it. It seems
very complex to me.
I am not export on BizTalk server however I have experience on other
integration technologies like DTS. Now day I am learning BizTalk
server. I am able to develop simple scenario but I feel problem in
Complex business scenario.

I might take your help in future, I hope I will get same assistance
later too.

Regards
Amit Kumar

On Aug 16, 1:31 pm, Randal van Splunteren
<RandalvanSplunte> wrote:
[..]

08-17-07, 03:42 PM

Richard Seroter

You can keep the old orchestration exactly as is ... that is, bound to the
receive and send ports.

When you deploy the new orchestration, you can bind it to the same ports.
You simply unenlist the old orchestration so that it is no longer used by new
inbound messages, but still available for previously dehydrated instances to
finish up with.

08-17-07, 07:50 PM

Jan Eliasen

On Thu, 16 Aug 2007 17:58:59 -0700, Richard Seroter
<RichardSeroter> wrote:

>So let's say you indeed version the orchestration assembly and deploy it.
>Now, you'd see two orchestrations in the application. You would unenlist the
>"old" one, and enlist the new one. All new messages will process through the
>new orchestration only.
>
>For any currently running/dehydrated orchestrations, they will complete
>their cycle with the OLD version. That's why you can't delete the old
>orchestration while there are currently pending operations that use it.
Eh? To unenlist an orchestration, you need to stop it first. So the
old ones wont complete.

Similar Threads
Orchestration Deployment I have published orchestration as web service and currently I am binding web service port using BizTalk Explorer using VS.NET. But on production biztalk server I cannot...
Direct Binding from orchestration to a new instance of the same orchestration Hello, We have an orchestration (lets call it "RunOrch") which constructs a message, promotes some property by given parameters and sends it to the messagebox with direct...
changes don't appear in new instance of orchestration I have 2 projects: a messaging project and an orchestration project. The messaging project has all my schema defs and maps. All of the maps use custom xslt. And of course,...
Orchestration Deployment Hi , I have a component which is kind of wrapper over the deployment+Bind+Enlist+Start tasks into a single task. Now i have a need of performing all these tasks as an atomic...
Orchestration instance Hi, I have deployed and orchestration.I have a receiveport that receives files from a folder. Now if i put 10 files in that folder, also 10 instances of my orchestration...