Help Needed - OD and DD script for Deployment

I m deploying files and the related metadata(EA) from a single source to a single target.
I want to deploy these to multiple targets from a single source by filtering based on the path of the files (/generated and /assets).
I m using the deployment approach in which the EAs of the deployed files get deployed to the DB using the database.xml file present on the Target.

PFA the deployemnt script definition where I m deploying to a single target (i.e.WebServer). I want to deploy the assets to WebServer and Generated files to AppServer.
How can I apply filters in this definition, as the 'targetRules' element is present in the source.
Can there be multiple 'targetRules' in the same source?
Can anyone please provide some help.

Find more posts tagged with

Comments

Adam Stoller

I m deploying files and the related metadata(EA) from a single source to a single target.
I want to deploy these to multiple targets from a single source by filtering based on the path of the files (/generated and /assets).
I m using the deployment approach in which the EAs of the deployed files get deployed to the DB using the database.xml file present on the Target.

PFA the deployemnt script definition where I m deploying to a single target (i.e.WebServer). I want to deploy the assets to WebServer and Generated files to AppServer.
How can I apply filters in this definition, as the 'targetRules' element is present in the source.
Can there be multiple 'targetRules' in the same source?
Can anyone please provide some help.

If you're basing the distinction for your deployments on path - then you should be able to easily sift the list of files into distinct filelists before calling the deployment so that your deployment configuration file can reference different filelist parameters for different deployment definitions.

Husna

Is it not possible to apply filter on the targets by using a single Filelist?

Husna

I forgot to add one more point, I m getting an error in the script if I use more then one 'dbLoader' element in the deployemnt script...
It says 'dbLoader cannot be used in more than one definition'.

Adam Stoller

Is it not possible to apply filter on the targets by using a single Filelist?

If you have different target replicationFarm's you need different deployment definitions - you could use different filters in each definition to process a single filelist as you are indicating - but I don't believe you can do what you want / need within a single definition (even if you use multiple pathSpecification and/or multiple targetRules sections)

Adam Stoller

I forgot to add one more point, I m getting an error in the script if I use more then one 'dbLoader' element in the deployemnt script...
It says 'dbLoader cannot be used in more than one definition'.

If you have different definitions (one for webserver, one for appserver) then presumably you only need the dbLoader associated with one (the appserver) definition.

If you only have a single node for the appserver farm this will probably work (I've never used dbLoader, I've always used DNR scripts). If you have multiple nodes defined for the appserver farm then this will probably have the same problem that other implementations have had - in which you need to break up the farm and make sure that one of the "sub" farms has only a single node in it and associate the DNR (or dbLoader?) only with the definition that is associated with that farm. If you search the forums - this aspect has been talked about before.

Husna

You have mentioned that "If you have different definitions (one for Webserver, one for Appserver) then presumably you only need the dbLoader associated with one (the appserver) definition."

How will DD work for the WebServer(as ther is no dbLoader element present in that definition) as I need to do a DataDeploy for the content being deployed to Webserver as well as Appserver to a single Database present in the WebServer.
The Webserver and Appserver are two different machines.

Adam Stoller

You have mentioned that "If you have different definitions (one for Webserver, one for Appserver) then presumably you only need the dbLoader associated with one (the appserver) definition."

How will DD work for the WebServer(as ther is no dbLoader element present in that definition) as I need to do a DataDeploy for the content being deployed to Webserver as well as Appserver to a single Database present in the WebServer.
The Webserver and Appserver are two different machines.

So you're saying that for a set of N-files one subset-A files get sent to WebServer and another subset-B get sent to AppServer - right so far?
And that there is data associated with both subsets that need to be sent to a single database server - yes?

As long as the subsets (A and

are distinct, there should be no problem having a dbLoader or DNR script associated with both deployment definitions / execDeployTasks.

As long as there is only one node in each of the AppServer / WebServer farms - there should also be no problem with attempting to DD the same files multiple times per overall deployment.

As far I can recall - if you have two (or more) distinct farms targeted for deployments you need to have two (or more) deployment definition specifications and then two (or more) execDepoymentTasks - so trying to stuff it all into a single deployment definition specification is, I believe, a no-go.

Husna

Answer to your questions is as follows:
(So you're saying that for a set of N-files one subset-A files get sent to WebServer and another subset-B get sent to AppServer - right so far?) -RIGHT
(And that there is data associated with both subsets that need to be sent to a single database server - yes? ) -YES

I m fine with using two Definitions for this deployment but the problem I m facing is as follows:

" dbLoader cannot be used in more than one definition "...

vpatel

Answer to your questions is as follows:
(So you're saying that for a set of N-files one subset-A files get sent to WebServer and another subset-B get sent to AppServer - right so far?) -RIGHT
(And that there is data associated with both subsets that need to be sent to a single database server - yes? ) -YES

I m fine with using two Definitions for this deployment but the problem I m facing is as follows:

" dbLoader cannot be used in more than one definition "...

And you have multiple target side DD deployments that are synchronized with OD deployments?

Husna

Yes...

PFA the screenshot where I m getting an error by using 2 dbLoader elements in a single script in 2 different definitions.

vpatel

Yeah you are not allowed to have multiple dbLoaders. With that said, probabl your best bet may be to have 2 separate set of deployments -- one for OD and one for DD.

Adam Stoller

Yeah you are not allowed to have multiple dbLoaders. With that said, probabl your best bet may be to have 2 separate set of deployments -- one for OD and one for DD.

Or two definitions using a DNR script instead of dbLoader to invoke DataDeploy - but you will also need two DD definitions - using the same filters being used for the OD distinction of Web and App server, so as to avoid trying to do duplicate INSERTs in the DD portion.

Migrateduser

see my post here:

http://devnet.interwoven.com/forums_vb/showpost.php?p=137763&postcount=2

you can use multiple DBloaders and/or filters using the following approaches, both work.