How to run only once DNR scripts

Hi,

We are using two transactional deployNRun scripts (dnrDeployment tag) for database & inktomi. Deployment is done to farm of three load-balanced web servers. When the deployment runs, it is executing three times for each DNR scripts. We tried to use dnrDeploymentJob, but it doesn't rollback the file deployed when database script fails (i.e when dnr script returns error code -2). I checked in the OpenDeploy 5.6 SP1 release notes that dnrDeploymentJob doesn't support transactional dnr.

We are running Windows 2000 SP3, Teamsite 5.5.2 SP3 & OpenDeploy 5.6.

How to make the script to run only ONCE per entire deployment.

Thanks,
Jithendra
Pktech Sdn Bhd

Find more posts tagged with

Comments

Migrateduser

Perhaps you can structure your deployment to have two definitions. Then execute one def with DNR and the other without, all within one <deployment transactional="yes" > element.

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

Jith

I tried this way also, but still doesn't work.

First definition(single server) doesn't wait for the second definition(two servers) deployment to be completed and starts executing datadeploy and Inktomi DNR. If the deployment fails for the second definition, only file deployment of first definition will be rollbacked. Inktomi search index and database will be out of sync.

Screen Shot 2012-11-10 at 08.34.51.png

Screen Shot 2012-11-10 at 08.35.13.png

Migrateduser

It's not pretty, but perhaps you can have two legs write out something, like a special database entry, that the DNR for the third leg waits for before proceeding. That way you can block your Inktomi processing until the other two legs are done deploying.

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

carnix

Have you tried scripting the other deployments in the DNR script? Here's what I mean:

Create a dummy deployment that does more or less nothing, sends c:\x.txt to c:\x.txt or something, but runs a script either before or after deployment (it matters not). Then, inside of this script, you can specifically define each deployment as you would on a command line, run any other scripts between each deployment, etc. What's more, you can then write other scripts that will call this one, say in the File Menu in TeamSite when logged in as Master or something to avoid having to use the OpenDeploy console...
.c

Michael Langford, Webmaster - CARE USA
151 Ellis Street, Atlanta, GA, 30303
http://www.care.org/

Edited by carnix on 07/18/03 01:55 PM (server time).

Jith

Thanks Todd Scallan for your info.

I broke up the deployment into 3 legs. First two legs will have an extra dnr which will write into log file the status. The third leg will check the log file for status before it proceeds with Database & Inktomi deployment.

Whether any future release supports transactional dnrDeploymentJob?

Edited by Jith on 07/23/03 11:55 PM (server time).

Migrateduser

> Whether any future release supports transactional dnrDeploymentJob?

I've filed a feature request: #43224

If you send me your company name, I'll attach it as an interested party.

Thanks.

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