This page covers debugging problems creating links from IBM Rational Quality Manager (RQM) and IBM Rational Team Concert (RTC) to IBM Rational DOORS. While there is some overlap, issues creating links from Rational DOORS to RQM and RTC will be covered separately. The link model used with Design Management and IBM Rational Requirements Composer (RRC) is different and hence that is also not covered here, though again there is overlap.
Initial assessment
What error is seen?
Is it failing for all users?
Has it ever worked?
Is it failing for all possible link types?
In which tool is it failing?
Symptoms
A link from RTC or RQM is not created. The effect is, when looking at a work item or a test case, the related Rational DOORS requirement is not seen and no hover over is possible.
A backlink from Rational DOORS to RTC or RQM is not created. In this case, the link is there in RTC or RQM and the users in those tools can see the related requirement. However the users in Rational DOORS have no knowledge the link exists. For example, they may not see the Rational DOORS requirement is linked to a RTC work item or RQM test case.
Impact
This may impact all users
Data gathering and subsequent analysis steps
Firebug can be useful if no error is seen in the web browser. It can show what requests it is sending to Rational DOORS Web Access and what responses are arriving back. Of particular note is usually the Net tab.
Extra logging in Rational DOORS Web Access will show what requests are arriving and responses are being sent. See How to increase the Rational DOORS Web Access logging levels and review the request.log and response.log.