It's all about the answers!

Ask a question

Link between RQM and DOORS requirements are not reflecting after saving


Amit Garg (312051) | asked Oct 18 '13, 9:59 a.m.

We are using RQM 4.0.2 / DOORS 9.4.0.0/DWA1.5.0.0 and linking requirements from within RQM test plan or test case. No changes has been made to the configuration. Earlier linking was working but now when we link a requirement to a test case or test plan, save the changes and refresh the page, the link is not there in RQM. Looking into the "History" says the user has modified something but what is it, is not registered.

We are able to replicate the same behavior with RQM 4.0.3/ DOORS 9.4.0.0/DWA1.5.0.0.

The difference about our setup is that we are using a masking technique for the URLs. So if the RQM url is https://rqmserver:9443/qm, it has been provided a masked name as https://prodRQM/rqm

Same configuration is with DWA too. so the URL for DWA is https://prodDOORS/dwa instead of https://doorsserver:8443/dwa

However, to run the dbadmin command -dwaPort parameter has to be provided with some value as it can't take the null value. So we have used 443 port.

If we browse any of the above masked links with port 443 included in it, it redirects to the url (without port) and continues working.

Same configuration is with RQM 4.0.3 setup too. Kindly advice what we are missing as this is affecting our prod environment.

One answer



permanent link
Lei Shi (2271) | answered Oct 21 '13, 10:21 p.m.
I guess the problem is due to the  URL for DWA is https://prodDOORS/dwa, but the dwa port is used 443.

could you please give me a detail url of DWA object? You can check whether the dwa url is used the https://prodDOORS:443/dwa/xxx/xxx or https://prodDOORS/dwa/xxx/xxx 

If it's https://prodDOORS:443/dwa/xxx/xxx, you need to add doors as friend in the rqm as the https://prodDOORS:443/dwa/public/rootservice.

Also, I have a question about your masking technique for the URLs, do you mean you use the load balance technique like h5 and so on?



Comments
Amit Garg commented Nov 23 '13, 7:22 a.m.

Hello Lei Shi

The problem was with Firefox browser. Once we used IE, the problem didn't occur

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.