Deactivation in a multi-tiered deployment

Hi!!

We have 3 servers, for the sake of convenience, lets designate them as A, B and C.

We are currently running 2 deployment scripts. Both of them are scheduled. One of them needs to deploy files to a single server and follows the 1-tiered approach. The other script is a 2-tiered deployment.

The second script deploys files from A to B and a deployment script in turn deploys files from B to C. Apart from this a couple of scripts are also invoked via the deploy and run option.

We need to de-activate the first deployment script (which resides on machine A) till the "complete" deployment is over, that is till all the scripts finish executing on machine C as well.

In a 1-tiered deployment scenario, we could use the following option:
<deployNRun>
<dnrDeployment location="source" when="before" state="success">
<script cmd="Deactivate_Hourly.bat" where="D:\Apps\OpenDeploy\Scripts"/>
</dnrDeployment>

<dnrDeployment location="source" when="after" state="success">
<script cmd="Activate_Hourly.bat" where="D:\Apps\OpenDeploy\Scripts"/>
</dnrDeployment>

</deployNRun>

How do achieve the same in the mutli-layered approach??

Thanks v.much!!

Find more posts tagged with

Comments

Migrateduser

OD 5.6 provides a couple of new features that may help with this scenario. First, you can specify a multi-tier transactional deployment that scopes the deployment job to multiple tiers. Second, you can take advantage of the new "job level" DNR trigger points to specify a pre-deployment DNR to deactivate the scheduled deployment on system A and a post-deployment DNR to reactivate the scheduled deployment.

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

nk_sc

Thank you for your response!!

Currently we are using OD 5.0.1. We've tried making do with the present version and have come up with a work-around. I'm posting this to validate our approach .. is this an acceptable solution??

Previously we had an OD Receiver component on machine C. We have now installed the Base component on machine C. We have a deployment script on C now that performs a deployment back to machine A. This deployment does NOT transfer any content, its sole aim is to invoke a script on machine A that activates the prior scheduled deployment.

Is this kind of a cyclic deployment encouraged in such a scenario??
Any comments will be appreciated... Thanks!!

Migrateduser

There's no reason you can't deploy from one Base Server to another, and then run a job the other way. But IMO using OD 5.6 would be a better approach. Smiley Wink

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

nk_sc

Thanks very much for your response!!