Correct syntax for reqpro host properties
I have a Reqpro 7.1 install that is up and running. In the system properties, I'm attempting to add the reqpro values .. what exactly is it expecting ?
My reqpro project files are in a c:\temp\reqpro directory on my server so I used in the host properties \\rackic.blr.can.ibm.com\temp\reqpro with the port of 82 It saves correctly and says its enabled. When I use the import from reqpro, it says there are not projects enabled on this connection. Our help files could do with an example of what the tool is expecting. Please advise. |
5 answers
In the Server Properties/RequisitePro Host Properties on our test server, I see Host Name set to the IP address (9.xx.xx.xx) where ReqPro is running, and Port set to 11080 (which is the default ReqPro port number). I would try changing the port number first. Then check the box next to that server and click the Test Connection icon, and it should say "This connection is available". After that I am able to do an Import Requirements in RQM and select the ReqPro hostname and project name.
There is some ReqPro setup information here - https://publib.boulder.ibm.com/infocenter/rpcmpose/v7r1m0/index.jsp?topic=/com.ibm.rational.rrc.help.doc/topics/t_config_reqpro.html |
In the Server Properties/RequisitePro Host Properties on our test server, I see Host Name set to the IP address (9.xx.xx.xx) where ReqPro is running, and Port set to 11080 (which is the default ReqPro port number). I would try changing the port number first. Then check the box next to that server and click the Test Connection icon, and it should say "This connection is available". After that I am able to do an Import Requirements in RQM and select the ReqPro hostname and project name. all good information, but my reqpro install is using port 82 - the URL is on a redirect to this port as 80 was already in use. |
In the Server Properties/RequisitePro Host Properties on our test server, I see Host Name set to the IP address (9.xx.xx.xx) where ReqPro is running, and Port set to 11080 (which is the default ReqPro port number). I would try changing the port number first. Then check the box next to that server and click the Test Connection icon, and it should say "This connection is available". After that I am able to do an Import Requirements in RQM and select the ReqPro hostname and project name. all good information, but my reqpro install is using port 82 - the URL is on a redirect to this port as 80 was already in use. Used the https:<server>:11080/reqweb .. get a connection not available ... transpose 11080 for 82 still the same result. Unfortunately I can't change the reqpro install - reqweb is definitely up and running |
|
Oh, is your ReqPro on a secure server? (That was my next question!) There was an issue with ReqPro and HTTPS that is fixed in 1.0.1.1 but was probably not in the available 2.0 beta. Let me check details and get back to you.
|
In the Server Properties/RequisitePro Host Properties on our test server, I see Host Name set to the IP address (9.xx.xx.xx) where ReqPro is running, and Port set to 11080 (which is the default ReqPro port number). I would try changing the port number first. Then check the box next to that server and click the Test Connection icon, and it should say "This connection is available". After that I am able to do an Import Requirements in RQM and select the ReqPro hostname and project name. all good information, but my reqpro install is using port 82 - the URL is on a redirect to this port as 80 was already in use. Used the https:<server>:11080/reqweb .. get a connection not available ... transpose 11080 for 82 still the same result. Unfortunately I can't change the reqpro install - reqweb is definitely up and running You can try to set the Host Name as |
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.