od-dd sync with uds

Hi,

I'm trying to make a od-dd-sync with data (not extened attributes) in uds database. I've managed to get it up and running asuming that I deploy metadata using the two dnr steps mentioned in the docu (one for the dcr's one for the xml dump file). The docu also say's that if you want to deploy data in a uds you don't need to dump everything first (loaduds full /dumpdir ) I think I've got this as well BUT in the loaddb.cfg file which I think is still used to load the data into the database there is a hardcoded link to the xml dumpl file. And that's where the trouble starts. My understanding is that there is no more dump file and datadeploy reads the deployed dcr's so I don't need that link anymore?? Or do I need to provide a variable name for the virtuall dump file??? I've tried a few thinks but it always fells over....

So any idea's are highly appreciated.

Marcus

Edited by marcussteiner on 04/30/03 12:14 PM (server time).

Find more posts tagged with

Comments

Migrateduser

Marcus,
There are 2 ways to setup OD-DD.
If using wide-table, then both a dump procedure and a db-import procedure is used, thus the tsxml.cfg and loaddb.cfg.

If using UDS, then only loaddb.cfg is required. You are correct in that DD reads the deployed DCR's to import into the database.

When configured the OD deployment to use UDS, the ddsync command is slightly different. If you havent caught it yet, there's an extra argument.

non-UDS: "ddsync ... load full"
UDS: "ddsync ... loaduds <target-top>"
where target-top is abs path of target destination dir.

marcussteiner

Dood,

thanks for your reply. I've managed to setup OD-DD in the wide table way using tsmxl.cfg and loaddb.cfg. This brings me to the question why we're doing that anyway. I'm not sure if I understand the philosophy behind it. I've never tried it, but wouldn't we also be able to take the oddd_full.xml opendeploy config file and trigger one 'normal' ts-to-xml datadeploy script using dnr on the sender. Then opendeploy it over to the reviever and then import it into the database using another 'normal' xml-to-db datadeploy script using dnr in the oddd_full file.

Instead we're using the tsxml.cfg and loaddb.cfg way which is a.) a bit messy to setup and b.) -even worst- limits us to exactly one tsxml.cfg and one loaddb.cfg file so we're not
able to setup several OD-DD sync scenarios. As mentioned I've never tried it and the question might be silly but can you explain that to me??

Anyway, comming back to the UDS setup. I've noticed the second argument in the script.
Taking the following scenario target/after/success in my oddd_full.xml:
ddsync.ipl c:\iw iwod_rcv_xml_dump loaduds full c:\iw\iwod_rcv_dcr

I suppose iwod_rcv_xml_dump is where ddsync.ipl will pick the filelist from? And iwod_rcv_dcr is where the dcr's is deploy to? My current problem is that either the filelist is empty after the deployment OR there is data in the filelist but it points to the wrong directory. In my source definition of oddd_full.xml I've got the following:

<sourceTeamsite>
area=Y:\default\main\ruv\WORKAREA\wa1
targetRules area="c:\iw\iwod_rcv_drc"
</sourceTeamsite>

<sourceFilesystem>
area=c:\iw\iwod_src_xml_dump
targetRules area="c:\iw\iwod_rcv_xml_dump"
</sourceFilesystem>

This is where I'm stuck at the moment. After having a look at ddsyn.ipl nothing will be written to the FILELIST if there's not "templatedata/$dtype/data" in the filename but
when specifying it the area (Y:\default\main\ruv\WORKAREA\wa1\templatedata\general\main\data) the filelist points to the wrong directory.

Any ideas? Any help is appreciated?

Regards
Marcus

Migrateduser

i know this is sorta off topic, but you guys seem to really know what you are talking about Smiley Happy

we have spent weeks trying to configure OD-DD sync correctly, but with no luck.

we are on a win2k environment, using UDS and DAS. we are trying to deploy from a Teamsite server to another non-Teamsite server that only has the Opendeploy receiver installed (oracle databases all around). we were told we didnt need DataDeploy installed on the receiver box since its not a teamsite server. is that correct?

do we need DD installed on the Target box like the documentation says?

since we are using UDS, does the IWXML.pm module have to be installed on both the base and receiver servers?

which of the 5 folders does IWXML.pm need copied into? all of them?

when i ran the iwperl -v on my Teamsite server here is what i got

\iw-home\interwoven\teamsite\iw-perl\lib/MSWin32-x86

\iw-home\interwoven\teamsite\iw-perl\lib

\iw-home\interwoven\teamsite\iw-perl\site\5.00503\lib

\iw-home\interwoven\teamsite\iw-perl\site\lib/MSWin32-x86

\iw-home\interwoven\teamsite\iw-perl\site\lib

thanks in advance, i would REALLY appreciate any help!

marcussteiner

Hi,
I've finally managed to set up it and running but still not sure if I understand everything the way I should:-)))
Anyway,
first you only need to copy the IWXML.pm module in one of the directories that comes out of iwperl -V. Copy it on both servers -won't do any harm- and see what happens when deleting it on one of them:-))

Second, od-dd sync and DAS does not work !! You'll have to set it up and running using manual (Firewall). Have you managed to write DD ts-to-xml and xml-to-db scripts??
Try this first and when done try to invoke them using an OD script with TWO dnr scripts and UDS (I find that easier).

Third, you need DataDeploy installed on the reciever (in order to make the xml-to-db/loaddb.cfg step). Not sure if it needs to be on the same box but on the same domain (again Port 1521 for Oracle).

This is my current understanding maybe there's better way#s to do it....

One thing I still don't understand is the difference between dd three tier and od-dd sync. So maybe someone could try to help me out here..

Let me know when you need help
Marcus

Edited by marcussteiner on 05/19/03 01:03 AM (server time).

Migrateduser

Hi Marcus,
The OD-DD wide-table approach does use the approach you describe, ie. dnr to DD out transient files that are OD'd over and then DD'd into the DB. That ddsync script really is a wrapper script around DD that does the dump and import tasks given the proper params. This wide-table approach is admittedly awkward and cumbersome as you have discovered. Its the precursor to UDS. IMHO, I think the wide-table approach should be deprecated. UDS should be the way to go.

In UDS, no transient files are used. The DD is not needed on the source side. It is used only on the target side to do the import into the DB. The list of DCR files to import is derived from OD itself. The DNR invocation of ddsync obtains a list of deployed files from OD and filters thru them for the DCRs and then feeds this filtered filelist into DD for import.

So as to your configuration, try specifying sourceFilesystem in both places rather than mixing with sourceTeamsite.
In ddsync.ipl, did you customize the list of DCR types to allow? Theres a customize section near the top of ddsync.ipl. Did you specify "general/main" as one of the dtypes? Since you are getting an empty filelist, then the path pattern for DCR files is not matching and thus no filelist.

Maybe you can post your OD deployment config and your ddsync.ipl for look-see?

Migrateduser

we got OD-DD sync working yesterday using UDS and .dump files without having DataDeploy installed on the receiver machine...we arent using filelists at all. we did a really customized job with some help from tech support (there is no documentation for this method)

marcussteiner

Wow,
can you tell me how you got the dump files loaded into the database then? Do you use the iwsync.ipl script for that?
And can you tell us more about that anyway?

Migrateduser

We got the files loaded in the db - by in tsxml.cfg changing the tag

teamsite-extended-attributes

to

teamsite-templating-records then in the loadb.cfg I changed the code to look like this:

<deployment name="ourcategory_ourdatatype">
<source>



<xml-formatted-data file = "e:\iwov_dumpdir\dumpdir\ourcategory_ourdatatype.dump" />

</source>

A real hack but it works

Migrateduser

If I gather correctly, what you have imlemented is using DD to update the database directly without the need to go thru another hop to an OD receiver? Cool.
The OD-DD solution is a reference solution and was really intended for those that need to deploy thru a firewall and want OD's encryption abilities.

Migrateduser

>>One thing I still don't understand is the difference between dd three tier and od-dd sync. So maybe someone could try to help me out here..

DD 3-tier is used if you have a DB server outside the firewall, in which case you would run the DD server on the server which has access to DB server :
iwdd.ipl cfg=<ddhome>/conf/ddserver.cfg

From the client machine you would invoke a deployment by specifying the host/port for the DD server in the config file
iwdd.ipl cfg=mydeployment.cfg $host=myhost $port=myport deployment=mydeployment

StreamInDoc2.docx

Migrateduser

Just to elaborate a bit...

2-tier DD deploys directly into a database.

3-tier DD deploys to another DD, which writes to the database. This is typically used when you don't want the database server to accept connections from outside the firewall.

OD-DD sync is similar to 3-tier DD, except that OD transfers the content between systems. This is typically used when files are to be sync'd with the database content, and/or when encrypted data transfer is needed.

Todd Scallan
Group Product Manager
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

StreamInDoc2.docx

marcussteiner

well :-))

2-tier: no problem database next to the ts server.

od-dd-sync: dd installed on both the ts server and a reciever in the dmz. (is this really needed? or is it
enough just to have dd installed on the target server?)
anyway then first do the ts-to-xml (using tsxml.cfg) then deploy both content and the dump file
using od to the reciever (target). finally doing xml-to-ts (using loaddb.cfg). all this is done
in one opendeploy script using two dnr scripts and ddsync.ipl
this will make sure both content and database assets are sychronized.
is this process correct?

3-tier: well, I've done 'normal' ts-to-xml datadeployments as well as xml-to-ts datadeployments using
iwdd.ipl. But considering what you said before, how will ts-to-xml dump files get deployed from one dd to
another one? using opendeploy or will they communicate to each other?
In order to get a teamsite assets to a database in a 3-tier environment will I need one ts-to-xml datadeployment
and then one xml-to-db datadeployment? or will one script do the job?

this brings up the following questions:

If I'd like to install dd on the target (reciever box) with no ts installation to I need to install the iwxml.pm?
and where do I put it? iwperl -V won't work. Should I use "print @INC" ?
Is there anything else to consider when installing dd on a reciever box with no ts installation (in my example it's Unix box)

regards

PaulW

2 Tier:

With regard to the 2-tier deployment, I would say that you wouldn't need a DD receiver on the target server, as long as the TS box can open up a connection with the database. Or you could probably do a custom script sitting on the TS Server, that created the filelist based on the OpenDeploy files generated. Then pass that filelist to DataDeploy running on the receiver.

Wouldn't going from TS-XML-DB be considered 3 tier? or do you think that 3 tier would need to be over 3 separate servers?

Your process sounds correct, except wouldn't the 2nd step be xml-db?

3 Tier:

The dump file gets created in the pre-DNR script. Then deployed by OpenDeploy to the DD receiver. Then the post-DNR script moves that data from the dump file on the receiver to the database.

Answers:
you only need the iwxml.pm if you are performing a UDS deployment. Note that there is a iw-perl directory installed under the DataDeploy directory.

If anyone wants to correct me, go ahead.