Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Deploying to multiple databases
msarker
Hello,
Please help answer the following query.
Our Data deployment scenario:
1. 2 target databases
2. 2 different dd_cofig.xml file
3. File list based deployment -- meaning two file lists for those two dd_config.xml
We started to work with "dbloader" to do the above work since we are deploying to the other types of servers (web,app) also. We are open to use "DNR" soution too.
Observation: It looks like that we need to create at least 4 deployment definitions (2 db and 2 filelist) in order to deploy.
Question: Is it possible to handle the above scenario with one/two deployment definition with transactional capability ?
Your time and suggestion would be appreciated.
Our System:
TS 6.5
Solaris 5.8
opendeploy 6.0.2
Find more posts tagged with
Comments
Migrateduser
The ability to update multiple databases using dbLoader sounds like feature request #57108. I'll attach your use case.
If you want to have a single definition do all the work, you should be able to structure it with multiple source-target pairings to get the files to the target, and then use a DNR to do the database update.
Todd Scallan
Sr. Dir. Product Mgt.
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
msarker
Todd
Thanks much for the information. I would probably go with the DNR solution.
Regards,
msarker