nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

DD Workflow integration

Brewy

Hi, I have just completed creating a .cfg file for all of our TS templates and now want to integrate dd with our workflows. I have run stand alone deployments of individual DCR types but am a bit confused on where to go next.

Do I only have to use 1 configuration file ie all_tables.cfg containing the whole schema definition and call iwdd.ipl with that? If so how do I pass the filepath as a parameter to iwdd? Obviously I don't want to trigger a deployment of the whole /templatedata for one file.

I have attached my .cfg file. As you can see it contains a config section and I would like to be able to pass in the $sourceArea and $sourcePath vars. I don't know how I can do this however:
<data-deploy-elements filepath="/apps/TeamSite/datadeploy/conf/database.xml" />
<client>
<deployment name="full">
<source>
<xml-source options="wide" area="$sourceArea" area-type="ts-filesystem" xml-type="interwoven">
<path name="$sourcePath" visit-directory="deep"/>
</xml-source>
</source>
<destinations>
<database use ="mysql" clear-table ="$myclearflag" delete-tracker="yes">

Find more posts tagged with

Comments

Migrateduser

You can only have 1 source tag in your file. So you could create separate config files for each templating type. another option is to use "filelist" and point to a file containing a list of all the files you want to deploy.

I take it that you don't want to use DAS but rather want to deploy all your data in standalone mode?

Mariam

i_like_smile

You can pass parameters to iwdd.ipl like this:
iwdd.ipl cfg=<path/to/cfg/file> deployment=<dep_name> sourceArea=<path/to/source/Area> sourcePath=<path/to/source/Path>

However, one thing is not clear is about your destination. Are all of your TS templates use the same Database schema? If so, above should work. If not, I think you need to create separate DD config file for different destinations.

marcussteiner

Do do your call more dynamically you can call it like that:
<script cmd="g:\iw-home\iw-perl\bin\iwperl.exe
g:\iw-home\datadeploy\bin\iwdd.ipl
cfg=g:\iw-home\datadeploy\conf\prototype.cfg
deployment=prototype
-k ddarea=$ddarea^
-k filelist=$filelist^"
async="no" />

In the dd cfg file your source could be like that:

<source>
<teamsite-extended-attributes
options = "wide,full"
area = "$ddarea^">
<path filelist="$filelist^" />
</teamsite-extended-attributes>
</source>

This will do your dd on a filelist basis. Double check for insert update and deltes. Hope this helps

hollis