Stopping concurrent deployments

Hazzie

Hi,

I have been asked to research if we can stop concurrent deployments to the same web servers. They want 1 deployment at a time with a 2nd one queuing up behind the 1st to wait its turn.

Now i have seen that there is a CLT called iwodserverstatus.bat that reports back the amount of active deployments at that time. Going on to the server i can run it, however i seem to be having difficulty calling it from within a perl script.

#!e:/iw-home/iw-perl/bin/iwperl.exe
use TeamSite::Config;
$iwhome = TeamSite::Config::iwgethome(); chomp $iwhome;
my $cmd = "$iwhome\\OpenDeployNG\\bin\\iwodserverstatus.bat";
print "$cmd\n";
@rv = `$cmd`;
$x = 1;
print "starting val of x is $x\n";
foreach $val (@rv)
{
 print "Line $x : $val\n";
 $x += 1;
}

i get the following output

E:\iw-home\OpenDeployNG\bin\iwodserverstatus.bat
The system cannot find the path specified.
starting val of x is 1

Can i call a bat file in this way? Is there an easier way to find out if a deployment is currently being processed at that time.

My idea was to find out if there was an active deployment then get the 2nd task to loop round 3 times with a 60 second gap in between each check to see if it can deploy then go back to the final approver to say there may be a problem with OpenDeploy.


Cheers,

Hazzie
TS 5.5.2 on NT.

Migrateduser

If you are using OD 5.6, the event reporting database will indicate the status of deployments: IN-PROGRESS, COMPLETED, FAILED. So perhaps an alternate approach could be do do an SQL query to pick up the deployment status.

Fyi, there's a feature request for managing deployment concurrency on the target so that target area conflicts are handled gracefully (FR #21765). We hope to implement this in the next release. We are also working on a ContentServices API, so this would provide another means of obtaining deployment status programmatically. Stay tuned...

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com