DOORS 9.3.0.4 / RQM 3.0.1 - integration not working
Hi -
I am able to get RQMI running. I then run the export from my DOORS module. The problem is that I never see the requirements show up in RQM. I saw the following snippet of an error in my RQM Tomcat console window: "RQM Server refused to accept this connection. The returned Test Plan will not contain requirements from the RM server." Am I missing something that the documentation hasn't explained? Do I need to have the requirements module set up for RQM? In other words, do I need to configure RRC as a container for RQM's requirements? I played around with it but didn't get it working. I recall that the RQM 2.0.1 / DOORS 9.2 integration created RQM requirements. I imagine the same is for the new integration (3.0.1 / 9.3.0.4). Help!! |
4 answers
Hi - I'm not sure if we have the same exact issue, but I ran into something similar with DOORS 9.3.0.4 and RQM 3.0.1. The RQMI Server seemed to be running correctly and after exporting a view from DOORS I received a successful "Export status: Exported" message when checking the status in DOORS. If I then ran the traceability report in DOORS I wouldn't see the associated test plan in the "Test Plans and Test Cases" column (all were blank). The exported requirements also wouldn't show up in the "Requirements" section of the RQM test plan I exported the requirements to. The solution to my issue seems to be a simple one. Not being even a novice DOORS user, when I had created my sample requirements, the objects I created only had text in the "Heading" property field. It appears that the DOORS-RQM integration only exports requirements to RQM that have data in the "Object text" property field. After adding the object text to my requirements, my exports were successful and I could see the associated test plans/test cases in DOORS and requirements in RQM. If you don't have the "object text" properties filled out for the requirements you want to export, give that a shot. Hope that helps! |
Hi - Hey Dan, Also forgot to mention that the DOORS 9.3.0.4 and RQM 3.0.1 integration does not require that RRC is setup as a container for the requirements. Understand what you were thinking there though, as I had the same thoughts before I got through my issue. |
Hi Dan,
Did you ever get this resolved? I am getting the same error that you mention below with DOORS 9.3.0.6 and RQM 3.0.1. Thanks, Murad Hi - |
Hi,
Your problem may due to a known limitation of DOORS RQMI. You can see the information from RQMI help - After a successful export, a new requirement is created in the RQM database for each object in the DOORS view that contains text in the object text field. Hi Dan, Hi - |
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.