It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×10,908
×2,339
×1,381
×118

question asked: Sep 26 '13, 6:20 p.m.
question was seen: 4,634 times
last updated: Jun 25 '14, 6:35 p.m.

Related questions

FAQ - How this Forum works

What's the best way to migrate data from RQM 2.0.1 to RQM 4.0.3?

1
Kegham Anbarjian (23●1●6●11) | asked Sep 26 '13, 6:20 p.m.
retagged Sep 27 '13, 1:45 p.m. by Lisa Caten (342●9●13)
I have a question on the best way to upgrade RQM from v2.0.1 to v4.0.3. Here is a description of the environment:

I have RQM v2.0.1 running on Tomcat on Server A. It is connected to an Oracle DB instance RQM1, running on a dedicated DB server. I am using ReqWeb to pull RequisitePro artifacts into RQM 2.0.1.

I also have RTC, RRC, and RQM v4.0.3 running on WAS on Server B. It is connected to another Oracle DB instance RQM2, running on a different DB server. I want to export all the data in RQM 2.0.1 to RQM 4.0.3.

My questions:
1) What's the best way to export all artifacts and data to RQM 4.0.3?
2) Is there a utility that can export/import all RQM artifacts at once, and for all the projects?
3) Will the import of data into RQM 4.0.3 automatically update the links to ReqPro?



Thanks,
Kevin

Accepted answer

1
permanent link
Lisa Caten (342●9●13) | answered Sep 27 '13, 1:45 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
A good place to start is the Upgrading from version 2 (two-step process) guide.
Kegham Anbarjian selected this answer as the correct answer
Comments
Kegham Anbarjian commented Oct 04 '13, 12:17 p.m.

Thank you, Lisa. This is a good resource. I wish there was a simpler way to upgrade to version 4.x.

3 other answers

Most liked answers ↑|Newest answers|Oldest answers

2
permanent link
Vidya Malkarnekar (1.0k●1●5) | answered Sep 27 '13, 2:01 p.m.
JAZZ DEVELOPER
If you want to get data from  RQM 2.0.1 on server A into  existing 4.0.3 repository on server B, you will have to first upgrade 2.0.1 on server A to 4.0.3  ( with intermediate migration to 3.0.*).   Then you can copy the projects and artifacts from one 4.0.3  server to another using copy utility -- https://jazz.net/wiki/bin/view/Main/RQMCopyUtility. 
This has to be done on per project basis and there are some limitations on what gets copied.

Comments
Kegham Anbarjian commented Oct 04 '13, 12:06 p.m.

Vidya,

Thank you for your help. Do you know what the limitations are for copying project artifacts from one RQM 4.0.3 server to another?

My challenge for an in-place upgrade is that RQM 2.0.1 is running on a Windows 2003 Server that is set up as a 32-bit OS. I cannot upgrade to 3.0.1 and to 4.0.3 because the latter doesn't support 32-bit architecture, it only works on a 64-bit platform -- https://jazz.net/library/article/811 .  I also verified that I cannot upgrade Windows 2003 Server to Windows 2008, since my Windows 2003 server is set up as a 32-bit architecture.

If anyone knows of a way to make RQM v4.0.3 work on a 32-bit platform, it would be the answer to my woes.

0
permanent link
Kegham Anbarjian (23●1●6●11) | answered Jun 25 '14, 1:06 p.m.
edited Jun 25 '14, 5:12 p.m.

All,

Thank you all for the input and for the resources for my RQM 2.0.1 upgrade project. Given that it was a major upgrade affecting several layers (OS platform, WAS, RTC, database) and the performance limitations with the export/import repotool, it took some time to conduct a proof of concept and develop an upgrade strategy. 

I followed the 2-step process to perform the upgrade on a Windows 2008 Server. Given the large amount of data to export, it was taking a significant time to export from our Oracle 10g database. One thought I had was to develop a script for a schema-to-schema data migration/conversion, which would have significantly improved the performance and eliminated the I/O bottleneck for creating a tar file. Unfortunately, this was not possible given the resources and the amount of time it would take to develop such a solution. 

Per recommendation from the Rational team, the 10g export and subsequent data import into Oracle 11g was performed by setting up a staging environment and by temporarily installing RQM 2.0.1, RTC 3.0.1, WAS 7.x, and Oracle 10g and 11g databases on a local drive. This approach proved highly beneficial. We were able to improve the export/import performance and score a 50% gain. After migration to RTC 3.0.x, it was much easier to upgrade to RTC 4.0.6, then clone the 11g database from Staging to Production.

Thought of sharing this with the hope that it would benefit others who are going through a smilar RQM upgrade.

Comments
N Z commented Jun 25 '14, 6:35 p.m.

Kegham, congratulations on performing the upgrade, it is not an easy process. I see it took about 9 months since you originally posted. We had a similar experience in time and performed essentially the same steps you did. We also mounted some key file systems into RAM (instead of using disk. This was on Linux), this saved another 50%, but is an extremely risky proposition (not one I would recommend), however, it was the only way for us to get the upgrade done in 5 days! This meant we had 3 days of down time.


I see my comment below was voted down. I'm not sure why? Is it because it wasn't considered helpful? Or was my criticism of the Jazz Team inappropriate?
I think it is important for the Jazz Team to understand that any upgrade that is this complex and takes 6-9 months top complete demonstrates a fundamental flaw with the process/product, and a total disdain for their customers. Honestly, I fear for future upgrades, and hopefully, I won't be around for them! Please take note!

-1
permanent link
N Z (362●21●27) | answered Oct 29 '13, 12:26 a.m.
Unfortunately, the Jazz Team have not done their user base any favors with the upgrade process, it really isn't good enough, so lots of reading and planning, and run the upgrade in a test environment first.

Your answer

Register or to post 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.