Migration from CQ to RTC
Hi,
We are planning a move from CQ to RTC and had a few questions: 1) How can we handle CQ history? I was planning on writing a perl scrip tto serialize the CQ history into a string and simply add it as a not to each CQ entity. But if someone had a different better idea I am open to it! 2) What about attachments? Are those handled properly? 3) Are there any material improvements to how CQ importing is done that is planned for 3.0 that we should be waiting for? Thanks in advance! |
3 answers
are you planning to use CQ Connector? you can use this tool to migrate your CQ repository into RTC
Also, with CQ Bridge you can have access to your CQ repository using RTC Web Interface |
are you planning to use CQ Connector? you can use this tool to migrate your CQ repository into RTC Since we ultimately want to no longer have CQ around, I think we would either use the connector or some other similar mechanism... |
Geoffrey Clemm (30.1k●3●30●35)
| answered Aug 09 '10, 8:09 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Just as a terminological note, as of 3.0, any integration between two
repositories at the data level is called a "connector". There currently are three kinds of connectors: - synchronizers (two way data flow) - bridge (just links are created, and those links can be navigated/queried by the GUI) - importer (effectively, a one-way synchronizer, into RTC). So it sounds like you either want to use the importer (one shot transition), or synchronizer (bring the data over incrementally, allowing for use of both repositories for as long as you want/need to). For your specific questions, I'll defer to the folks who have more experience using the CQ importer and synchronizer. As I recall, history is not brought over by either, so your string approach is probably the best you can do. I think attachments can be brought over by the synchronizer ... don't know about the importer. Cheers, Geoff On 8/9/2010 2:37 PM, ScottChapman wrote: akhataeiwrote: |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.