Importing Requirements into RQM
The instructions for importing requirements from ReqPro into RQM begin with the following:
Select the Source type. Enter the Host Name or IP address of the host. Enter the Port number of the host. Entering the above I see this message: Error : The requisite web server might be temporarily unavailable. Please check your hostname and port. What host name is the system looking for? That of the ReqPro project or the ReqWeb server? I've tried both unsuccessfully. What syntax is the system expecting to see for the host name and port? |
17 answers
The instructions for importing requirements from ReqPro into RQM begin with the following: RQM is looking for the ReqWeb Sever URL. So I typically use http://:11080. In the second step of the wizard, there is a place where you select the specific project you are trying to import from. Can you get to that ReqWeb server in a browser from the machine where RQM is installed? |
The instructions for importing requirements from ReqPro into RQM begin with the following: RQM is looking for the ReqWeb Sever URL. So I typically use http://:11080. In the second step of the wizard, there is a place where you select the specific project you are trying to import from. Can you get to that ReqWeb server in a browser from the machine where RQM is installed? I don't get to the second step because the first fails. I am able to connect ReqWeb from a browser on the RQM server. |
I've always had to put port 80 (the default port ReqWeb listens on). When I didn't put the port, I got the error you posted.
|
I've always had to put port 80 (the default port ReqWeb listens on). When I didn't put the port, I got the error you posted. Adding port 80 has not changed teh symptom. It may be helpful for everyone to know that we didn't seem to have this problem until we upgraded from RQM 1.0.1 to 1.0.1.1. Since then, we've not been able to import requirements. Our ReqPro Web and projects are version 7.1 |
Have you tried this format for the hostname?
http://servername.com (or https: if that is the case) Then the port number in that field. |
|
After seeing your message, I tried using the fully qualified name of the ReqWeb server after pinging it successfuly from the RQM server. That did not work. I also tried the IP address. Same result.
Has anyone gotten this function to work in RQM 1.0.1.1? It worked for us in 1.0.1 |
Are there firewalls on your RQM server or Reqweb server machine? If have, pls shutdown the firewalls and try again.
After seeing your message, I tried using the fully qualified name of the ReqWeb server after pinging it successfuly from the RQM server. That did not work. I also tried the IP address. Same result. |
Perry, you can try the following steps to diagnose this strange issue.
1. Try to access http://ReqRroServerAddress:ReqProPort/ReqWeb/Servlet/project/* from 2. Open https://RQMSERVER:9443/jazz/web/console/Quality%20Manager#action=com.ibm.rqm.planning.home.actionDispatcher&subAction=viewSystemProperties Click ReqPro Host Properties -> select your reqpro server -> click "Test Connection" to see whether the connection is really working. Hope it helps. |
|
The result of "Test Connection" is the message "The connection is not available"
I am able to connect to ReqWeb via a browser on the RQM server. |
|
Perry, it seems your ReqPro has some problems. ReqPro REST API is not working even though your ReqWeb works well. Please restart your ReqWeb and try again. If ReqPro 7.1 is running on windows, you can try following steps in Services panel
1. Shutdown 2. Shutdown 3. Start IBM HTTP Server 6.1 4. Start IBM WebSphere Application Server V6.1 - RWP ReqWeb Servlet After that, try to access http://ReqRroServerAddress:ReqProPort/ReqWeb/Servlet/project/* It should work now. If still failed, try to restart that machine. Hope it helps this time The result of "Test Connection" is the message "The connection is not available" |
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.