Hi all,
we're currently in the process of upgrading to OD 6.x and I was wondering if anybody has already done an upgrade using the new synchronization mode for OD-DD. The old way we've done it was to trigger DD through a dnr script in OD which was then triggerning ddsync.ipl to run DD. The command for our installation was as followed:
<dnrDeployment location="source"
when="after"
state="success">
<script cmd="g:\iw-home\iw-perl\bin\iwperl.exe
g:\iw-home\datadeploy\bin\ddsync.ipl
cfg=g:\iw-home\datadeploy\conf\CR.cfg
deployment=multi
-k state=$state^
-k ddarea=$ddarea^
-k BranchOfficeFileList=$branchofficefilelist^
-k ComponentFileList=$componentfilelist^
-k GlossaryFileList=$glossaryfilelist^
-k TrademarkFileList=$trademarkfilelist^
-k ContentFileList=$contentfilelist^
-k FilesFileList=$filesfilelist^
-k ImagesFileList=$imagesfilelist^
-Xwfid $wfid^
"
async="no" />
</dnrDeployment>
I've checked the documentation and found out that triggering DD module is done in the source definition of the OD config file. Beside many other problems we've got I've got no clue of how to pass over my -k parameters to my DD config file to replace the variables in it.
<sourceFilesystem area="$area^" filelist="$OD_filelist^">
<pathSpecification>
<path name="."/>
<dbLoader useDatabaseRef="live_db" databaseXmlFile="g:\iw-home\opendeploy\od6base\opendeployng\conf\database.xml">
<xmlData schemaMapFile="G:\iw-home\OpenDeploy\OD6base\OpenDeployNG\conf\6CR.cfg" xmlType="custom"/>
</dbLoader>
</pathSpecification>
</sourceFilesystem>
</source>
Can someone confirm that this call to DD is right in the first place and give me also a hint of how to resolve my variables problem in the DD config file.
Kind regards
Hollis
