I started working as a Technical Support Engineer, initially on Telelogic Synergy/Change products, later on IBM Rational ClearCase for the past couple of years, and lately with IBM Rational CLM (Collaborative Lifecycle Management) solutions.
Unlike with Telelogic Synergy or IBM Rational ClearCase, issues with CLM are so diverse, with less repetition of similar questions or difficulties. Here is one of the many interesting issues with CLM that I happened to work on.
Rational Team Concert (RTC) 18.104.22.168 server running on JFS 22.214.171.124 on server machine 'A'.
Rational Quality Manager (RQM) / Rational Requirements Composer (RRC) 126.96.36.199 running on JTS 188.8.131.52 on server machine 'B'.
Each having their own database servers, running on their respective server machines.
The client was looking to integrate RTC 184.108.40.206 with RQM 220.127.116.11 so that users can raise defects from RQM 18.104.22.168, which in turn is a Work Item in RTC 22.214.171.124. So they tried to establish friend relationship at RQM 126.96.36.199 server but were unable to establish communication as outlined in this help topic:
They were able to successfully register RQM 188.8.131.52 application on the RTC 184.108.40.206 server, however, trying to register RTC 220.127.116.11 on RQM 18.104.22.168 server failed with the following error:
CRJAZ2082E : An error occurred while attempting to access the Application
About service listed in the Discovery document for this application.
Please ensure that the application has been installed and provisioned correctly.
Unsupported RDFEntity Content-Type: text/html
--> They were in a situation where they did not have the option to upgrade from RTC 22.214.171.124 to RTC 126.96.36.199, due to IT and resource constraints. But they did want to get these products to work and roll out to users. Trying to register RTC 188.8.131.52 at RQM 184.108.40.206 server always failed with the errors as above.
--> Based on the error and configuration, we informed the customer that it is an unsupported scenario. With RTC 3.0 or 220.127.116.11 the integration for RQM, RQM must be 2.0.1 or 18.104.22.168. This was not the case in their set-up and hence would not work.
However, they had a concern in why there were able to link RQM 22.214.171.124 in RTC 126.96.36.199 server, whereas the reverse did not work. They were in a strange scenario, where the lower version (RTC) linked correctly to the higher (RQM), while the opposite did not happen. We understood in Support, that the combination they had is not supported and should not work.
However, the solution for their problem was to delete the existing server friend relationship between RTC 188.8.131.52 and RQM 184.108.40.206 at RQM 220.127.116.11 server and redefine them. This made the integration work and they were able to see the RQM Projects areas from RTC and the RTC project areas from RQM. They were then able to open defects from RQM to RTC.
While I haven't been able to reflect upon why the specific setup did or did not work here, I thought it's worth a time to write a note on this behavior and note the steps we saw achieve some success in this unsupported configuration.
I welcome any comments or suggestions on this article.