Issues related to RQM/RTC Integration for defect managment.

When you manually login, are you prompted to add an exception for a secure connection? This is how it works in our environment. Once this exception is made, you will be good until the next time you clear your browser's cache.

I don't get prompts for adding security certificates because I already installed them permanently.

To help illustrate my problem here are the steps that I am trying to perform:

- log into RQM
- generate a new (or open an existing) Execution Result record, scroll-down to Defects section
- click on the "Add New Defect" icon

At this point I would expect one of the following to happen:

1. to be presented with a login page for the RTC server and then taken to the defect submission form in RTC
OR
2. to be taken directly to the defect submission form in RTC using my current login credentials (since I am using the same LDAP-enabled id in both systems)

That doesn't happen, instead I get a progress indicator saying:
"Create Draft Work Item..." that never finishes.

I was also getting the "Fetching Project Areas" message. When I changed the Hostname values in the Server Properties to the IP address of the server it fixed this problem.

I can't remember if prior to the change I had just localhost specified or the actual hostname, but using IP definitely fixed it for me.

Thanks Michael for the suggestion but unfortunately it doesn't work for me... I am still stuck on this never ending "Fetching ...." message.

Hi Bogdan,

I understand your use case and what you expect is exactly what should happen. It sounds like you followed the steps described in the online help correctly. The only things I can think of to make sure you don't get the "fetching project areas" message forever is:

1.) Ensure the URL names for the RQM server in the 'Cross Domain Host Whitelist' property contain all the different variations. I always use :
https://myserver:9443/jazz, https://myserver.ourdomain.mycompany.com:9443/jazz, https://ip address:9443/jazz

2.) Ensure the host name (not IP) of the RTC server is entered in the: com.ibm.team.repository.servlet.internal.ServletConfigurationService component in RTC

3.) Ensure the host name (not IP) of the RQM server is entered in the: com.ibm.team.repository.servlet.internal.ServletConfigurationService component in RQM

4.) Ensure that in the system properties dialog in RQM, you use the host name of the RTC server and not the IP.

The only other thing I can think of that may cause problems is if the versions of RTC and RQM you are using are not aligned. I know you mentioned both are v2, but there are different iterations within v2 and they could be based on different builds. I will have to get back to you on that...

I double-checked all the settings and they are set as you suggested but the problem still exists.

Here are more details on the versions of RQM and RTC that we're using:

RTC:
Server version: 2.0 M2 (I20090316-0438)

RQM:
Rational Quality Manager Version 2.0.0 Standard Edition
Internal Version 2.0.0.20090318_0818

The RQM integration was broken during the 2.0 development. The issues were addressed for beta1. Can you pls try it again with the beta1 version.

https://jazz.net/downloads/rational-team-concert/betas/2.0Beta1

Just to verify, you're refering to RTC server that needs to be updated, right?

It wasn't I who setup our RTC server so I am not sure where/how our infrastructure team obtained RTC server code but I thought we were already using Beta1 version of RTC. If 2.0 M2 (I20090316-0438) is not the beta1 what version number should we be seeing for beta1?

Just to verify, you're refering to RTC server that needs to be updated, right?

It wasn't I who setup our RTC server so I am not sure where/how our infrastructure team obtained RTC server code but I thought we were already using Beta1 version of RTC. If 2.0 M2 (I20090316-0438) is not the beta1 what version number should we be seeing for beta1?

Hi Bogdan,

I do think its an alignment issue with the RQM and RTC builds you are using. Where did you download the RQM build from? As Eric suggests, the Rational Team Concert 2.0 Beta 1 driver was available on 2009/3/17.

I tested the integration using an internal version of RQM in mid-April and Rational Team Concert 2.0 M3D1.

I have the exact same problem. I'm running RQM 2.0 Beta 1 and RTC 2.0 Beta 1. I was not even able to get passed "Fetching Project Areas", even though I have accepted the security certificates, and can login to both RTC and RQM from both machines without prompts. Anything else I'm missing here?

Thanks!