Thanks Justin. (Note: I think Justin meant that there was a bug in
2.0.0.2, since work item 104828 is filed against 2.0.0.2).

I tried clearing the browser cache (which appears to be the source of
the problem in 104828), but that did not help.

Just for interests sake, does anyone have the RQM/RTC Build integration
working with RTC-2.0.0.2?

Cheers,
Geoff

jukutti wrote:

Hi Geoff,

What versions of RTC and RQM are you using? I know there was a bug in
RTC 2.0.0.1 where this integration was not working properly. It's
should be fixed in the next ifix. See jazz work item 104828 for more
details.

Regards,
Justin

I've gotten all the CALM work-item integrations running between RTC,
RQM, and RRC. So my RTC, RQM, and RRC servers (running on the same
machine) are all friends of each other, and I can create and traverse
those various links between projects in the different servers.

But I'm stuck on the RTC/RQM build integration.

I've currently followed all of the instructions on setting up the build
integration between RTC and RQM, as detailed in:

https://jazz.net/help-dev/rational-quality-manager/topic/com.ibm.rational.test.qm.doc/topics/t_config_rtc_build_integration.html

But at step 3.h. (after I've select "Configure"), it pauses for a goodly
while with "Fetching Project Areas", and then fails with the pop-up
message: "Failed to contact server".

There was nothing in the RQM or RTC logs indicating what caused this
failure, but there was the following warning in the RQM log:

22 Feb 2010 13:03:40,015 WARN
com.ibm.rqm.defects - Couldn't retrieve
latest states from remote url - https://rtc.localhost.org:19443/jazz,
please check your server or network configuration.
The detail exception is
CRJAZ1247I The request to the server failed. The server returned the
http error 500 with error text "Internal Server Error". Examine any
further details here or look in the server log files for more
information on how to resolve the issue.

I've verified that the URL mentioned in that warning message is valid
when dropped into the browser. The different port number is to allow
RTC and RQM to run on the same machine. (And I've played the usual game
with creating aliases for localhost in the hosts file, to work around
the cookie problem).

Cheers,
Geoff

FYI - the RTC ifix that contains the necessary fixes for the build integration has been released:
https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2iFix1

Regards,
John Nason

I've gotten all the CALM work-item integrations running between RTC,
RQM, and RRC. So my RTC, RQM, and RRC servers (running on the same
machine) are all friends of each other, and I can create and traverse
those various links between projects in the different servers.

But I'm stuck on the RTC/RQM build integration.

I've currently followed all of the instructions on setting up the build
integration between RTC and RQM, as detailed in:

https://jazz.net/help-dev/rational-quality-manager/topic/com.ibm.rational.test.qm.doc/topics/t_config_rtc_build_integration.html

But at step 3.h. (after I've select "Configure"), it pauses for a goodly
while with "Fetching Project Areas", and then fails with the pop-up
message: "Failed to contact server".

There was nothing in the RQM or RTC logs indicating what caused this
failure, but there was the following warning in the RQM log:

22 Feb 2010 13:03:40,015 WARN
com.ibm.rqm.defects - Couldn't retrieve
latest states from remote url - https://rtc.localhost.org:19443/jazz,
please check your server or network configuration.
The detail exception is
CRJAZ1247I The request to the server failed. The server returned the
http error 500 with error text "Internal Server Error". Examine any
further details here or look in the server log files for more
information on how to resolve the issue.

I've verified that the URL mentioned in that warning message is valid
when dropped into the browser. The different port number is to allow
RTC and RQM to run on the same machine. (And I've played the usual game
with creating aliases for localhost in the hosts file, to work around
the cookie problem).

Cheers,
Geoff

I'm still having the same problem, even using the latest releases of RTC (2.0.0.2. iFix1) and RQM (2.0.1).

Here is the error:

21 Apr 2010 09:34:02,312 ERROR
com.ibm.rqm.defects.service - class
com.ibm.rqm.defects.service.internal.ChangeRequestCollector:runTask
AQXCM5001E An error was encountered trying to connect to a remote server:
CRJAZ1247I The request to the server failed. The server returned the http error 500 with error text "Internal Server Error". Examine any further details here or look in the server log files for more information on how to resolve the issue..

FYI - the RTC ifix that contains the necessary fixes for the build integration has been released:
https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2iFix1

Regards,
John Nason

I've gotten all the CALM work-item integrations running between RTC,
RQM, and RRC. So my RTC, RQM, and RRC servers (running on the same
machine) are all friends of each other, and I can create and traverse
those various links between projects in the different servers.

But I'm stuck on the RTC/RQM build integration.

I've currently followed all of the instructions on setting up the build
integration between RTC and RQM, as detailed in:

https://jazz.net/help-dev/rational-quality-manager/topic/com.ibm.rational.test.qm.doc/topics/t_config_rtc_build_integration.html

But at step 3.h. (after I've select "Configure"), it pauses for a goodly
while with "Fetching Project Areas", and then fails with the pop-up
message: "Failed to contact server".

There was nothing in the RQM or RTC logs indicating what caused this
failure, but there was the following warning in the RQM log:

22 Feb 2010 13:03:40,015 WARN
com.ibm.rqm.defects - Couldn't retrieve
latest states from remote url - https://rtc.localhost.org:19443/jazz,
please check your server or network configuration.
The detail exception is
CRJAZ1247I The request to the server failed. The server returned the
http error 500 with error text "Internal Server Error". Examine any
further details here or look in the server log files for more
information on how to resolve the issue.

I've verified that the URL mentioned in that warning message is valid
when dropped into the browser. The different port number is to allow
RTC and RQM to run on the same machine. (And I've played the usual game
with creating aliases for localhost in the hosts file, to work around
the cookie problem).

Cheers,
Geoff

Hi,

I am also still getting errors trying to set up RTC/RQM integration.

We just upgraded our RTC server to V2.0.0.2, iFix2 (from v2.0.0.2). I also upgraded a couple of my RTC clients (Eclipse and Visual Studio client) to RTC v2.0.0.2, iFix2. Our RQM server is at v2.0.0.1 (I20091214_0623). I think that is one of the iFixes for RQM, v2.0.0.1.

When I go onto the RTC Web UI of a new project and try to "Add" the link to an RQM project for testing, I get the following error:

"Failed to read service provider catalog resource:

Unable to load URL: /jazz/proxy?uri=https://tpaccpvas247rqm.caremedic.net:9443/jazz/rootservices, Status: 500"

I know that this is documented, as per the previous replies.

Here is an interesting note:

I can create a link from a new RQM project to a new RTC project using the RQM Web UI.

I have done just as Geoff did and followed all of the instructions for setting up C/ALM integration on the RTC and RQM servers. In fact, the RTC/RQM interop was working fine before we upgraded RTC to v2.0.0.2.

-Walter

I'm still having the same problem, even using the latest releases of RTC (2.0.0.2. iFix1) and RQM (2.0.1).

Here is the error:

21 Apr 2010 09:34:02,312 ERROR
com.ibm.rqm.defects.service - class
com.ibm.rqm.defects.service.internal.ChangeRequestCollector:runTask
AQXCM5001E An error was encountered trying to connect to a remote server:
CRJAZ1247I The request to the server failed. The server returned the http error 500 with error text "Internal Server Error". Examine any further details here or look in the server log files for more information on how to resolve the issue..

FYI - the RTC ifix that contains the necessary fixes for the build integration has been released:
https://jazz.net/downloads/rational-team-concert/releases/2.0.0.2iFix1

Regards,
John Nason

I've gotten all the CALM work-item integrations running between RTC,
RQM, and RRC. So my RTC, RQM, and RRC servers (running on the same
machine) are all friends of each other, and I can create and traverse
those various links between projects in the different servers.

But I'm stuck on the RTC/RQM build integration.

I've currently followed all of the instructions on setting up the build
integration between RTC and RQM, as detailed in:

https://jazz.net/help-dev/rational-quality-manager/topic/com.ibm.rational.test.qm.doc/topics/t_config_rtc_build_integration.html

But at step 3.h. (after I've select "Configure"), it pauses for a goodly
while with "Fetching Project Areas", and then fails with the pop-up
message: "Failed to contact server".

There was nothing in the RQM or RTC logs indicating what caused this
failure, but there was the following warning in the RQM log:

22 Feb 2010 13:03:40,015 WARN
com.ibm.rqm.defects - Couldn't retrieve
latest states from remote url - https://rtc.localhost.org:19443/jazz,
please check your server or network configuration.
The detail exception is
CRJAZ1247I The request to the server failed. The server returned the
http error 500 with error text "Internal Server Error". Examine any
further details here or look in the server log files for more
information on how to resolve the issue.

I've verified that the URL mentioned in that warning message is valid
when dropped into the browser. The different port number is to allow
RTC and RQM to run on the same machine. (And I've played the usual game
with creating aliases for localhost in the hosts file, to work around
the cookie problem).

Cheers,
Geoff

Karen,

You are right. My reply was for a different subject. One that is much worse than getting the RQM/RTC Build Integration to work. I can't get the basic RTC/RQM Integration to work for new projects after upgrading from RTC v2.00.1 to v2.0.0.2. But, that may be because of another issue that is being fixed by the RTC development team and is the subject of another topic in the forum.

Sorry. I'm subscribed to too many topics, I guess.

-Walter