On April 27, 2024, our Sign-in and Create Account options will be unavailable from 9am-12pm ET. During this maintenance window, developer account access and free trial registration will be unavailable.
data deploying to xml file
Hi all:
I'm tyring to use data deploy to export extended attributes of various documents in several work areas to a xml files.
Reading through all of the documentation, there doesn't seem to be too much written about how this is done.
Could some one please point me in the right direction on how such a configuration file should be written?
Can data deployalso be used to deploy data records to xml file? And if so, is it any different from how extended attrbutes are handled?
Thanks a lot.
Nancy
I'm tyring to use data deploy to export extended attributes of various documents in several work areas to a xml files.
Reading through all of the documentation, there doesn't seem to be too much written about how this is done.
Could some one please point me in the right direction on how such a configuration file should be written?
Can data deployalso be used to deploy data records to xml file? And if so, is it any different from how extended attrbutes are handled?
Thanks a lot.
Nancy
Tagged:
Comments
-
Hi Nancy,
Deploying to XML files is pretty much similar to deploying to the database with a few configuration tweaks in the .dd file
This is an example of a configuration file to output both the extentend attributes of whole vpath and the DCR values of a certain DCR type. Ive used lots of options in the configuration to allow things such as the destination file to be set from the command line.
<!-- usage iwdd.ipl cfg=mip_xml_docs.dd deployment=multi -->
<!-- options= [full | differential ] -->
<!-- docs_edition={edition to deploy} -->
<!-- prev_docs_edition={prev edition published | dummy if options=full}-->
<!-- vpath=minor vpath to branch edition ie, /default/main/www/docs/utsupport/EDITION/-->
<data-deploy-configuration>
<client>
<deployment name="mip_xml_docs">
<source>
<teamsite-extended-attributes
options="narrow,$options"
area="$vpath/$docs_edition"
base-area="$vpath/$prev_docs_edition">
<path name="./" visit-directory="deep" />
</teamsite-extended-attributes>
</source>
<destinations>
<xml-formatted-data file="$docs_dest" />
</destinations>
</deployment>
<deployment name="mip_xml_funds">
<source>
<!-- Pull data tuples from TeamSite EA's -->
<teamsite-templating-records
options="wide,$options"
area="$vpath/$docs_edition"
base-area="$vpath/$prev_docs_edition">
<path name="/templatedata/prodperf/prodperf/data" visit-directory="shallow" />
</teamsite-templating-records>
</source>
<destinations>
<xml-formatted-data file="$funds_dest" />
</destinations>
</deployment>
<deployment name="multi" options="transactional" >
<exec-deployment use="mip_xml_docs" />
<exec-deployment use="mip_xml_funds" />
</deployment>
</client>
</data-deploy-configuration>
Hopefully this will give you a head start. If you have any more specific problems with DataDeploying to XML, post them as we have done quite a lot.
stu
Stuart Eccles
Technical Architect
Quidnunc
http://www.quidnunc.com
Categories
- All Categories
- Cloud Editions
- 1 Thrust Services
- cat as link
- 1 Core SaaS Application development
- 10 Developer Announcements
- 15 General Questions
- 33.4K TeamSite
- 141 Application Governance & Archiving
- 15.2K Designing Analytics Reports
- 1K DevShare Downloads
- Core SaaS Applications
- nested parent
- 4.3K Developing Analytics Applications
- 8.8K Documentum Developer Forum
- Media Management developer
- 159 Transactional Content Processing (TCP)
- 1.7K Web Experience Management
- 55 Tempo Social
- 1 XM Fax