Best Practices OpenDeploy

vhi_interwoven

Hi,

I am trying to write some deployments to publish content for a new branching structure that has been created on my TeamSite system. There are about 10 new branches and some of these have sub branches too.

The way we use deployments normally is that we describe a deployment in the XML descriptor file, then we write an IPL to publish an edition on the relevant branch and invoke iwdeploy against that deployment. This IPL is invioked by an end user through the use of a 'Custom Menu Item' on the GUI.

The content is a mixture of JSPs, HTML, ASPs and images etc. The content needs to be deployed to 4 different servers, test web server (IIS), test app server (WebLogic), live web server (IIS) and live app server (WebLogic). As the content is mixed on the branches, in the deployments we point at all the content under a branch and use regular expressions to push only JSPs to the app servers and vice versa.

So for the new branches I am looking at writing a new deployment, per branch, per server. These will see me writing about 40 config files. (e.g. Branch1_Live_App_Server_Deployment, Branch1_Live_Web_Server_Deployment, Branch1_Test_App_Server_Deployment, Branch1_Test_Web_Server_Deployment..)

For the IPLs I will write one IPL per branch, which invokes first the app server deployment, then the web server deployment.

But is there a way to do it without writing so much code (much of which is very similar anyway)?
Can I pass in parameters or do some dynamic stuff in the deployment files?

If anyone has any ideas, I would be very grateful..(even some useful URLs would help)

Thanks,

James

Migrateduser

Which version of OpenDeploy are you using?

OpenDeploy supports parameter substitution, which could potentially save you from having so many deployment config files. Take a look at "Parameter Substitution" starting on p. 198 of the OD 5.6 Admin Guide.

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