BizTalk Server Orchestration - Orchestration ReDeploy

This is Interesting: Free IT Magazines  
Home > Archive > BizTalk Server Orchestration > June 2004 > Orchestration ReDeploy





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 Orchestration ReDeploy
Neal Walters

2004-06-20, 11:09 pm

Is it dangerous not to bump up the version number each time you deploy?

I had added some suspend shapes to my orch, deployed, then undeployed (stopping all active orch's), rebuilt, redeployed etc... and still finding my orch suspended. When I go into Orch Debugger, under the "Tracked Events" on the left side, I see 4 steps w
ith no action name and no action type.

Thanks in advance,
Neal Walters
http://Biztalk-Training.com

Gilles [MSFT]

2004-06-20, 11:09 pm

Hello Neal,

>Is it dangerous not to bump up the version number each time you deploy?


I assume you are running BizTalk server 2004.

During developement, I personally never bump up the version of my orchestrations because I terminate all instances and un-deploy
my previous version, so there is only one version of the orchestration at a time.

>I had added some suspend shapes to my orch, deployed, then undeployed (stopping all active orch's), rebuilt, redeployed etc... and still finding my
>orch suspended. When I go into Orch Debugger, under the "Tracked Events" on the left side, I see 4 steps with no action name and no action type.


It looks like you have stale orchestrations. Use HAT (healt and activity tracking) to terminate the service for those orchestrations.
You should really be "cleaning up" all suspended instances before undeploying.

Thanks a lot.
-Gilles.

BenW

2004-06-20, 11:09 pm

I have just had a terriable time trying to sort out a problem, which was only resolved by bumping up the version number. There appears to be a problem undeploying and deleting, which relates assemblies and ports and which persists across reboots.

I added a schema that one of the ports used after the initial deployment. The error log kept on saying it could not load because it could not find it, if someone wants to try to locate where the problem is this is a pointer.

"Gilles [MSFT]" wrote:

> Hello Neal,
>
>
> I assume you are running BizTalk server 2004.
>
> During developement, I personally never bump up the version of my orchestrations because I terminate all instances and un-deploy
> my previous version, so there is only one version of the orchestration at a time.
>
>
> It looks like you have stale orchestrations. Use HAT (healt and activity tracking) to terminate the service for those orchestrations.
> You should really be "cleaning up" all suspended instances before undeploying.
>
> Thanks a lot.
> -Gilles.
>
>

Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com