It's all about the answers!

Ask a question

Is possible to update RequisitePro URL association after RQM data is migrated?

Kegham Anbarjian (231711) | asked Jan 20 '14, 7:07 p.m.
edited Jan 21 '14, 9:08 a.m. by Max Bridges (24126)


I have RQM 2.0.1 running on RQMServerA. It is integrated with RequsitePro via the ReqWeb service which is set up on the same server RQMServerA. The URL for accessing ReqPro documents from within RQM is http://RQMServerA:11080. I am migrating RQM 2.0.1 data to RQM 3.0.1 which is set up on a different server, RQMServerB (RTC, JTS and CCM 3.0.1 are also installed on RQMServerB along with RQM). I will be taking RQMServerA offline, hence I have also set up the ReqWeb service on RQMServerB. After I migrated the data to RQM v3.0.1, the URL for all of the existing artifacts is still pointing to http://RQMServerA:11080, but I need to change this to http://RQMServerB:11080, since I am also planning to move the ReqWeb service to RQMServerB. I need to update the ReqPro URL for all of my existing artifacts in the migrated DB, so that the URL points to http://RQMServerB:11080. has anyone encountered this scenario? If yes, how can I update the reference/association for all of the existing items in the RQM schema? The DB schema is set up in Oracle 10g. I took a quick look at the tables in the RQM schema, but given their large volume, I am not sure which table(s)  contain the reference to the RequisitePro URL.

If it's a simple matter of identifying the relevant tables in the schema and running a SQL update query, I was wondering if someone can point me in the right direction, as it would be a big help.



One answer

permanent link
Paul Slauenwhite (8.4k12) | answered Jan 21 '14, 6:30 a.m.
Unfortunately, this requires a server rename since the ReqPro URL is referenced in RQM test artifacts.  However, server rename is only supported in CLM 4.0+ (see

Kegham Anbarjian commented Jan 21 '14, 4:14 p.m.

Hi Paul,

Thank you for the reply and for the info. The good news is, I am planning to upgrade to CLM 4.0.3. I’d like to make a small precision though: I am not planning to rename the CLM server or the ReqPro server, so I am not sure how I can benefit from the server rename feature. I need to rename the embedded URL in RQM, specifically when a user clicks on the requirements document link of a test artifact from within RQM. Since I did an upgrade from RQM 2.0.1 to RQM 3.0.1 (and planning to upgrade to CLM/RQM 4.0.3), the existing link points to the ReqWeb service on RQMServerA. Since RQMServerA is going to be decommissioned, I need to update this embedded link and point it to the ReqWeb service on RQMServerB. I am hoping that there is a simple process to change this reference for all of my existing test case artifacts.


Kevin <o:p> </o:p>

Paul Slauenwhite commented Jan 22 '14, 10:07 a.m.

Hi Kegham,

The only way to change these embedded ReqPro URLs in RQM is through server rename.  You would not be renaming the public URL of the CLM server but rather the public URL of the ReqPro server. For example (see


Kegham Anbarjian commented Feb 03 '14, 5:54 p.m.

Hi Paul,

Thank you again for your input on this question, and my apologies for the belated reply. I was hoping for the chance to run my upgrade to CLM v 4.0.x. Given the current pace of the migration initiative, it might be a week or two before I will be able to give the server rename a try. I will keep you posted on how it goes.


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.