RQM / ClearQquest / RTC cross-server communication
I am hoping you might be able to help me or point me towards someone or some documentation that can. I am in need of documentation that tells me how I can configure an RQM cross-server communication with RTC, on top of an existing RQM <---> Rational ClearQuest communication.
I tried to create a new RTC to RQM friends request but it failed and also took down the existing ClearQuest bridge. Do you you happen to know about any documentation anywhere that tells me how to achieve this? RTC 3.0.1 RQM V3.0.1 as for the CQ version, I am not sure RQM error message is: Friend: the discovery resource at <cq_url> for "<cq_connection_name>" cannot be accessed: The returned HTTP status was 302 The response body was RQM is on a different server to the RTC CQ is configured on the RQM Friends (Outbound) The RTC server is fine but RQM shows the above error And when I try and add the Association in the RQM project to the RTC project as Defects, or re-add the existing CQ, I get this error: For the CQ: Unable to load URL: <cq_url>, Status 404 and a similar one for the RTC. Interestingly RQM now let's me see the RTC projects when trying to add the RTC Defects association. Before it was giving me a similar error to the above CQ one. The RQM project has now let me add the RTC project as a Defects association - Project area saved successfully. But the RQM application still shows the above mentioned error. The RQM project still has the original CQ Defects Association (I've not removed it) but it's obviously broken. If I try the RQM web console to see if I can raise defect against the RTC or the CQ I receive this message: <cq_connection> Loading... and sometimes I receive a hyperlink message saying "Log in to see content", but when I click on the hyper link I receive this error: HTTP Status 404 - type Status report message description The requested resource () is not available. Apache Tomcat <version> do you know of any documentation that describes how to set up this 3-way linkage? Currently the RTC is configured with the Consumers (inbound) authorized key for the RQM as trusted and the RQM is configured with 2 Friends (Outbound); the RTC and the CQ and the RQM project is set up with 2 Associations, the CQ and the RTC Do I need to add the CQ to the RTC Consumers (inbound) to complete the set up? or somehow set up some linkage between CQ and RTC? It would be good to understand how this is supposed to work/what the desired objective is for this, and to then understand/have some documentation that describes how to configure this. I've been searching in the CLM info center and on Jazz.net, and I cannot find any concept topics about this 3-way linkage (if that's what it is) or any task topics that describe how to achieve this. Any help will be much appreciated. |
2 answers
Adding the RQM to RTC cross-server communication will break any existing RQM to ClearQuest bridge, because the configuration for adding an RTC into the equation must be as follows:
RQM ---> RTC (cross-server communication), then RTC ---> CQ. This then allows CQ defects to be seen from the RQM, and also RTC defects to be seen from the RQM. The RQM ----> RTC cross-server communication task is covered in the CLM info center, but ClearQuest is not mentioned. Likewise, the RTC to CQ task topic is covered in the CLM info center, but RQM is not mentioned. We must have a task topic that covers RQM --> RTC ---> CQ, which must be added as a related link from the above to task topics. I will raise a defect against the docs for this new task topic, which describes that users must remove the RQM to CQ bridge, then configure the RQM to RTC link, and then link the RTC to CQ bridge. I will also ask for the addition of a prereq against the RQM to RTC task topic to state that users must check for an RQM ---> CQ bridge before configuring the RQM to RTC linkage, otherwise they will break the CQ link to RQM, and cause a defect outage to RQM users. |
Defect created:
https://jazz.net/jazz/web/projects/Jazz%20Collaborative%20ALM#action=com.ibm.team.workitem.viewWorkItem&id=184003 |
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.