DataDeploy | Controlling the order of DCR Deployment.

sivaramiyer

Hello,

Platform: TS671/OD 6.2.0/ Linux ESA

Consider the below scenario where a particular DCR is associated with
multiple DCRs within it.

For ex: homepage dcr has couple of modules attached to it.

home-page.dcr [has reference to module-1.dcr and module-2.dcr]
module-1.dcr
module-2.dcr

is it possible to control the behavior of the DataDeploy to specify the deployment order of the DCT types? Say DCRs of module type takes preference before homepage type. is it possible to define a strategy like this in DD?

Any help/reference much appreciated.
thanks
Sivaram

Migrateduser

Hello, Platform: TS671/OD 6.2.0/ Linux ESA Consider the below scenario where a particular DCR is associated with multiple DCRs within it. For ex: homepage dcr has couple of modules attached to it. home-page.dcr [has reference to module-1.dcr and module-2.dcr] module-1.dcr module-2.dcr is it possible to control the behavior of the DataDeploy to specify the deployment order of the DCT types? Say DCRs of module type takes preference before homepage type. is it possible to define a strategy like this in DD? Any help/reference much appreciated. thanks Sivaram

you can do two ways

1 - if you are using DbLoader in your OD config, you can define multiple pathspecs (and therefore DBloaders) which MUST have their own unique TargetRules Area element defined in order to work.. It "should" also have filters, to only send thru the specific. The DbLoader documentation is VERY poor, and although you cannot specify multiple DB loaders in SEPERATE definitions within the same config (it gives an error) , you CAN specify mulitple DBloaders within the SAME definition if you use the approach I show below.

here is an example of an OD config with this done:

[html]


















































[/html]

2 - if you are doing dataDeploy directly, you would setup filters and multiple deployments, and a master deployment that would execute the others (in my example its "multi"):


[html]















































































































[/html]