Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
integrating templating and datadeploy
dcc
I'm following the instructions in the TS developers guide for integrating Templating, DataDeploy, and Workflow. They seem deceptively simple. It's not working, not even any datadeploy log files are being spit out. When I run the deployment cfg file through the ddgui it works fine so I know that works and i've followed the naming convention dcrtype_dd.cfg. I'm not sure what else to do. Two questions 1) Are there other log files other than the ones at dd-home/log that i can look at to find clues and 2) are there other steps i should be doing other than what is in the templating documentation to get this running? i looked at the datadeploy docs but did not find anything relevant. Any help is GREATLY appreciated!
Find more posts tagged with
Comments
Migrateduser
well... first things first. It sounds as though you are attempting to run a stand alone deployment and not use DAS. is this correct (if you are attempting to use DAS, what are the iwsyncdb commands that you have attempted or are you trying to do this all through the DD gui)?
Next you mention creating a dcrtype_dd.cfg yet you did not attach any example of the configuration. If you could give step by step examples of what you are attempting to do and examples of the configuration files you are using you might get more help from others on DevNet.
dcc
I'm not attempting to use DAS, but the documentation makes no mention if that is required or not.
Do you know what the answer to my questions are? 1) Are there other log files other than the ones at dd-home/log that i can look at to find clues and 2) are there other steps i should be doing other than what is in the templating documentation to get this running?
For a step by step example of what I have done, you can refer to the documentation I mentioned in my original post, because I have followed it. I have appended the dcrtype_dd.cfg file for your reference also.
Migrateduser
questions 1) Are there other log files other than the ones at dd-home/log that i can look at to find clues
If you are running DAS the logfiles go to dd-home/log on solaris or whatever log directory you specify during install in case of NT.
In case of standalone deployments specify the logfile option in iwdd.ipl command line:
iwdd.ipl cfg=mycfg.cfg deployment=mydep logfile=myfile.log
and 2) are there other steps i should be doing other than what is in the templating documentation to get this running? i looked at the datadeploy docs but did not find anything relevant. Any help is GREATLY appreciated!
If you are using DAS you have to follow these steps before deploying
1. generate the dbschema file using iwsyncdb.ipl -dbschemagen for the appropriate datatype
2. generate dd_cfg file by running iwsyncdb.ipl -ddgen ...
3. Generate database tables running iwsyncdb.ipl -initial ....
now you should be set to deploy dcr's to DB via DAS
If you have already performed the above steps check if DAS is running.
avdhut
I have tried with the inserts and updates...integrated with workflow...
Things really works....
For starting you can try invoking the datadeploy using command line....you can try something like following....
/webapps/iw-home/iw-perl/bin/iwperl /webapps/iw-home/datadeploy/bin/iwdd.ipl cfg=/<full_path>/engine_dd.cfg deployment=submitlist mysubmitlist=/var/tmp/aaaNsaqrZ mybasearea=/default/main/...../WORKAREA/Content_wa myDBUrl=db.server.com
ort
ID myDBUser=user myDBPassword=pass
someone will be able to help if you could attach your _dd file
there are other things like versions of teamsite and datadeploy which may cause the problems...make sure you have proper versions installed
Migrateduser
YOu need to evaluate why you want to use DAS or deployments in standalone mode. In DAS deployments, the table names and the schema for the root table would need to be in a particular format. The root table must have a "path" and "state" column and all other tables must also have a "path" column.
In standalone deployment, you have full control with what you want to do. You can deploy to a schema that's pre-defined or defined by DataDeploy for a given DCT.
