Deployment configuration organization.

sivaramiyer

Greetings,

Currently, the TS publishing platform that i manage has 50+ different templates and content is deployed to the database using DD. The DD deployment configuration mapping (dcr xml - xpath - database table/field/relationships) for all the templates live in a single xml file (15000+ lines!).

Personally, I believe it would be way easier and modular to organize the datadeploy configuration under several smaller files based on template-category/type.
say:

video/dd-stand-alone.xml
video/dd-playlist.xml
video/dd-hub-page.xml

indices/dd-topic-landing.xml
indices/dd-show-landing.xml
...
..
.

and so on.

What is the recommended / suggested way of managing such large DD configuration files. Can you share the approach that is taken by your organization, if you follow a different way of organizing configuration.

Also, thinking along the lines of performance improvement, I think, breaking this massive chunk of configuration xml may improve performance (i have nothing to prove it will, I'm saying - it may), has anyone tried / noticed any improvement by doing so before?

Thanks,
Siv

OD 6.2.0 / TS 6.7.1 SP1

ISCBorisB

Greetings, Currently, the TS publishing platform that i manage has 50+ different templates and content is deployed to the database using DD. The DD deployment configuration mapping (dcr xml - xpath - database table/field/relationships) for all the templates live in a single xml file (15000+ lines!). Personally, I believe it would be way easier and modular to organize the datadeploy configuration under several smaller files based on template-category/type. say: video/dd-stand-alone.xml video/dd-playlist.xml video/dd-hub-page.xml indices/dd-topic-landing.xml indices/dd-show-landing.xml ... .. . and so on. What is the recommended / suggested way of managing such large DD configuration files. Can you share the approach that is taken by your organization, if you follow a different way of organizing configuration. Also, thinking along the lines of performance improvement, I think, breaking this massive chunk of configuration xml may improve performance (i have nothing to prove it will, I'm saying - it may), has anyone tried / noticed any improvement by doing so before? Thanks, Siv OD 6.2.0 / TS 6.7.1 SP1

Have you tried XML Entities, External Entities in particular?

We use XML Entities to make modular TS XML Configurations like templating.cfg, available templates
and the like. Note that I never tried Entities for DD Configuration so do not know if it'll work.
It's standard XML though, worth a try IMO.