Migrating from CQTM and RMT to Rational Quality Manager

Kim Soderhamn, IBM SWG – Rational Denmark
Last updated: December 09, 2009
Build basis: Rational Quality Manager 2.0.0.1 iFix1, ClearQuest 7.0.1.2

Introduction

This article contains the hints, and hands on info you need to migrate RMT(Rational Manual Tester) and CQTM(ClearQuest Test Manager) to RQM(Rational Quality Manager). A lot of the info, hints, and workarounds are not found in the standard guidelines so this article provides you with the info we have found in the process.

Strategy

If you have more than 1 registry you may want to create separate project areas for these to keep them apart.
Notice that test plan hierarchy (plans having plans) will not be created in RQM as no such thing exists here.

Prerequisites

Obviously its a good idea to test the migration in a test environment first, so make a mirror of your environment. Install the products. ReqPro and RMT can be moved by moving shared files and moving the ReqPro db. And CQ can be moved using the maintenance tool. Check the on-line help resources for the subjects.

Additionally, it is a good idea to have a database backup of the RQM Jazz DB incase you need to roll back for further testing (as you cannot delete records in RQM).

Both CQTM migration and RMT migration will require CQ and RMT both be installed respectively, along with special migration tools. Both tools are located in the RQM install folder (named Migration).

Also, there may be a number of firewall issues if you are using a newer version of Windows. You need to open traffic for port 9443 (tcp outbound jazz) as well as port 80 (http), and port 443 (https) and for whatever port your DB is using. You may also have to open your license server port.

You don’t need to have a bridge or connector to CQ up and running before migrating.

Requirements (ReqPro)

When you run the CQTM migration, you need specify the location of your ReqWeb ahead of time on each project Area(system.properties). The url must contain the server and the port like: http://thereqwebservername:11080
Additionally you must make sure that the reqweb url for each RA Project in CQTM points to this place and contains the port as well (http://thereqwebservername:11080/ReqWeb). Importantly, if you have moved CQ to a new server, this value must be updated along with the location of the ReqPro Projects on the RA_Projects records. You can find the records by making a query in CQ. On each project there are 3 values to update.
If ANY of your test cases don’t have the name field filled out (do a cq qry to check) they will fail to import.
In this case perform a manual import of the lot. You do this in RQM by selecting Requirements > Import Requirements
To be safe you should probably select all requirements of a specific project. Notice, there may still be a bug in the import wizard; if you’ve selected all requirements of a type and then return to this requirements type before finishing, you will no longer have all requirements of this type selected. If you have no reqweb in your drop-down, you forgot to create the ReqPro link on the project area. If the list of projects to select is empty, it is most likely because you have moved your ReqPro and you have not updated the file with the ReqPro installation location:

C:Program FilesIBMRationalSDLCprofilesprofile2installedAppsDefaultNodeReqWeb.earReqWeb.warWEB-INFclassesconfig.txt

See the instructions for editing the configuration file for an alternate installation directory.

Notice that you may have to refresh your view in RQM after importing (the small yellow arrows).
When performing a manual import of requirements you should remove the requirements from the mapping file of the CQTM export tool, as you do not want to migrate them twice. You will not find the mapping file (migration.cfg) in the install folder but instead in a folder like:

C:UsersAdministrator.RationalClearQuestrcp_configuration_71eclipsepluginscom.ibm.rational.clearquest.testmanagement.rqmexport_2.0.0.v20091119_1542data

The requirements section should be one of the first. CQ must be restarted preferably with the -clean argument (simply add ” -clean” to your cq shortcut).

When requirements are in place (all name fields have values or you’ve done a manual import) you should import from RMT before doing the CQTM migration.

There is more general help available on this topic here.

Test Scripts (RMT)

To run this migration: first run the install-tool.bat and then find the newly created rmt2rqm.bat inside the RMT install folder and run it.

Select File > Migrate.

In the server field you enter the server name with no protocol or port. I chose not to be the owner of all migrated assets:
Next, select to Convert Group Statements to Steps (I was told this was a good idea). Also, select the target project area and select if you will migrate project assets or not. If you have created projects inside RMT then you most likely want select Migrate Project Assets. If not then select Migrate Non-Project Assets. My RMT scripts are not in any projects which means I will have no projects to select.
On the following page you need to add the directories of your rmt scripts and logs for the specific project; this path should match the path you have in CQTM.

Click finish.
Now, something strange may happen where the tool tells you that some scripts already exist even though your jazz db is empty. I don’t know why this is, but I click Yes To All to overwrite all.
Check your scripts in RQM – notice you may need to refresh your view (the small yellow arrows).

here

Testcases, Testplans and Linking It All (CQTM)

If you have a version of the migration plug-in installed in CQ and all other prerequisites, you should be ready to migrate CQTM data.

Make a connection to the database you want, connect, and then go to File > Export > Export to RQM.

Notice the warning about the paths previously mentioned in this guide. No spelling or case difference is accepted.
On the next page enter the target RQM server. This time protocol should be used (https).
Finally select the target project area. Select all of the optional artifacts:

Click Finish.
Verify that the test plans, test cases, etc. are there, and that:
- Test plans are linked to test cases
- Test scripts are linked to test cases
- Requirements are linked to test cases
You will need to restart CQ after this procedure, before migrating again, or using it for other purposes.
Notice that in CQ you are not required to have requirements on the test plans before you add them to test cases like you normally do in RQM. However, with the migration tool, a parent test plan doesn’t get the requirements of the child test case.

Ther is more general help available here on migrating test assets from Rational ClearQuest Test Manager.

Troubleshooting:

If you don’t get your requirements linked, check the section on manual import of requirements in this article.
If you don’t get requirements or RMT scripts linked in your CQTM migration plug-in, it may have a bug and should be replaced. To remove the plug-in installed in CQ, simply rename the C:UsersAdministrator.Rational folder, then download a fresh version of the tool from jazz.net RQM extras (all downloads section of latest RQM).

Products used for this migration:

RMT 7.0.1.2 iFIX2

CQ 7.1.0.2

ReqPro 7.1.0.2

RQM 2.0.0.1 iFix1

migration tools 2.0.0.1

For more information

About the author

Kim Soderhamn has been employed by IBM for more than 12 years and is working as a Technical Services Consultant for IBM Software Group Rational in Denmark kims@dk.ibm.com.

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.

Feedback

Was this information helpful?

5 people rated this as helpful.