Migrate RTC2 and RQM2 to same 3.0 Server
I am currently running RTC 2.0.0.2 IFix005 and RQM 2.0.1.1 on separate machines, and these are using a cross server connection. What I want to do is to install the RQM M11 (which includes RTC RC3) and migrate all project areas from the two V2 servers to the same V3 server.
I've tried this method: Export RTC data from V2 server: repotools -export toFile=rtcData.tar Import RTC data to V3: repotools-ccm -import fromFile=rtcData.tar repotools-ccm -migration_exportJTSData toFile=jtsData.tar repotools-jts -migration_importJTSData fromFile=jtsData.tar createMappingFile=rtc-mapping.txt createTables repotools-ccm -migration_importUserMapping fromMappingFile=rtc-mapping.txt Now this successfully imports the project areas from RTC. The same can be done for RQM. Export RQM data from V2 server: repotools -export toFile=rqmData.tar Import RQM data to V3: repotools-qm -import fromFile=rqmData.tar repotools-qm -migration_exportJTSData toFile=jtsData.tar repotools-jts -migration_importJTSData fromFile=jtsData.tar createMappingFile=rqm-mapping.txt createTables repotools-qm -migration_importUserMapping fromMappingFile=rqm-mapping.txt Now the RQM project areas are up and running perfectly fine on RQM 3 M11. BUT, the importing of RQM overwrites data in the JTS database, which breaks the RTC project areas. Similarily if I migrate RQM data first and then RTC data, the RTC project areas will work but not the RQM areas. So: what I have succeeded to do is to migrate RTC data OR RQM data from V2 to V3, but not both. I can (and have) install one installation of RQM M11, and one with RTC 3.0 (either RQM M11 package or regular RTC 3.0 with only CCM), migrate separately V2->V3 and do a crossserver connection between them just like in V2. But what I'm really interested in is to see how RTC 3 and RQM 3 work out together when running on the same JTS, and preferably not doing so by creating project areas from scratch since I cant migrate my existing ones. Have anyone successfully done this, and if so using what commands? |
7 answers
I don't think it is possible to do this because they both would have the
same context root. If you look at the install it only allows you to pick one to migrate not both (I believe for the reason above). You will have to choose one or the other. On 11/27/10 12:08 PM, gabri wrote: I am currently running RTC 2.0.0.2 IFix005 and RQM 2.0.1.1 on separate |
|
I did not use either migration choice in the installation manager, so ccm and qm are my context roots for V3. The commands above did let me migrate to different context roots, ie jazz->ccm, and jazz->qm. Only not both.
I suppose if I could copy a project area from one RTC3 server to another I could migrate separately to different Jazz 3.0 servers, and then copy RTC data from one to the other to get everything to the same Jazz Team Server. But I read in another thread that this functionality does not exist yet, so I'm limited to repotools importing of RTC project areas, which breaks the RQM areas. Maybe what I'm asking for is some migration functionality that does not exist yet but is planned (I know the real release of RQM is many months away). Can I read somewhere about which migration paths are planned for the future? |
What you are describing would require implementation of this plan item on a Jazz Foundation level: 93151: Support moving projects between Jazz repositories.
As per the above URL this has been deferred to post-3.0. Regards, Patrick |
|
I worked alittle more on this, and found out that I was actually quite close to the solution in my first post. All I had do to was to remove the word createTables in the second call to repotools-jts.
The commands to migrate RTC2 and RQM2 contents into the same JTS (RQM M11) is then (when you have rtcData.tar and rqmData.tar already): repotools-ccm -import fromFile=rtcData.tar repotools-ccm -migration_exportJTSData toFile=jtsData.tar repotools-jts -migration_importJTSData fromFile=jtsData.tar createMappingFile=rtc-mapping.txt createTables repotools-ccm -migration_importUserMapping fromMappingFile=rtc-mapping.txt repotools-qm -import fromFile=rqmData.tar repotools-qm -migration_exportJTSData toFile=jtsDataRqm.tar repotools-jts -migration_importJTSData fromFile=jtsDataRqm.tar createMappingFile=rqm-mapping.txt repotools-qm -migration_importUserMapping fromMappingFile=rqm-mapping.txt A side note: I did this using DB2 (Express) for all databases. The same did for some reason not work with derby databases, maybe there's a bug in repotools scripts when using databases, because the *.txt mapping files where not created. |
Gabriel,
I'm on a similar migration, and i'm have a few doubts. What did you configured in the new server? URI? DB? Thanks |
Gabriel, Yes, that's what I did at that time, by editing all teamserver.properties. And then running the Setup after migration was complete. Although right now I have been working with a similar migration from 2.0 to 3.0.1 on separate RTC and RQM target, and I got some problem with this approach so I'm not sure it is the best. The approach I use know is to run through a full Setup, registering applications initiate databases and everything. Then after that run the migration scripts. And after that, since migration destroys the application registering data in the databases, I remove CCM and QM as registered applications in JTS. Remove all related friends and oath consumers in JTs, CCM, QM, then run Setup a second time, to reregister all applications. Again, not sure if it's the best way, but I got the server running after migration this way, and it saves me from having to edit any teamserver.properties by hand at all. One more thing, the repotools command, -importUsers should be used as well, on a cvs-file created with -exportUsers in version 2, as the very last step with server started. Forgot to mention that one earlier. |
Hi there, I have my data in oracle and I want to migrate it to MySQL. Please do share the proper solution or procedure for it.
============ Server Moving & Migration |
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.