Grouping servers in Transactional deployments

Bowker

OS W2K
OD 5.5

We have 6 different environments that are loosely dependent upon each other.
Public Production - 4 servers
Public Pre-Prod - 2 servers
Public Testing - 1 server
Private Production - 4 servers
Private Pre-Prod - 2 servers
Private Testing - 1 server

If a deployment fails to ANY machine in ANY environment all 14 servers roll back.

I would like it such that the 6 different environments don't depend upon each other, just the machines within each group. Is it possible (without setting up 6 different .xml configurations and running 6 different deployments) to do that in one config file and one deployment?

Migrateduser

One deployment config file: yes (by specifying multiple definitions).

One deployment: no. You would have to run the same deployment config multiple times, using variable substituion for the particular definition. (Or you could have 6 different deployment configs.)

The problem is the deployment element's "transactional" attribute is effectively global. So all defintions that are run via execDeploymentTask within the deployment element are lumped together into a single transaction.

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