Problem with OSLC link of changeset to ClearQuest with RTC Embedded Visual Studio client
- ClearQuest v7.1.2.6
- OSLC v1.2
- Visual Studio 2012
- RTC Embedded VS Client 4.0.5
- Win7
- links used for friends relations: ClearQuest: https://<clearquest webserver>/cqweb/oslc/repo/<database name>/discovery, not trusted
- links used for friends relations: RTC: https://<rtc web server>/ccm/rootservices, not trusted
- Self signed CCL certificates (we're using a sandbox environment. Our production servers have proper SSL certificates)
- Why does it do that?
- Is there a configuration file we've missed?
- Where can we find it?
- Is there a TechNote explaining these settings?
One answer
1. Ensure you have network connectivity from the client where you have VS installed and server where CQ Web located. You should be able to ping the server from the client machine.
2. Ensure you can open a CQWeb page in the browser on the client machine to the CQ Web Server using the same URLs you indicate above. If you can't you need to trouble shoot that problem before involving the VS client. For example your HTTPS SSL Keys...
3. You need to make sure your servers for CQWeb and RTC are Oauth friends. Establish OAuth friend relationships between the RTC JTS server and CQ servers. These friend relationships allow JTS servers to authenticate and communicate with each other and other server. This enables provide the OSLC artifact preview capabilities. You should clearly document the required JTS friend relationships and in what direction the requests will be made. For the JTS being administrated, what requests for information being received are "inbound" from other servers, versus requests for information being made "outbound" to other servers. For example for the OSLC artifact previews to work in RTC, the tool that owns the linked object has CQ has to be registered as an Outbound friend on the JTS server RTC is installed on. If you get an error message "Unknown Provider" with the OSLC previews, this means the artifact's JTS is not registered as a friend. If you get a permission errors check also that you have assigned Client Access Licenses to each user for the each of the products being accessed by the user.
Here is a link to a doc that might help.
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/topic/com.ibm.team.rcm.doc/topics/t_configuring_cq_bridge.html
4. Once you have that working then debug the Visual Studio problem separately.
Hope this helps.
Carlos
Comments
Hi Carlos,
The functionality to create a link a changeset to a ClearQuest record works from the RTC Eclipse client. It doesn't work from the RTC Embedded Visual Studio client. Removing a ClearQuest link from a changeset in VS works as well.
Looking at the trace-logfile:
04-30-2014 13:24:13 FilesystemUILibrary: com.ibm.team.repository.OSLCTeamRepositoryException: Error executing https://clm-sandbox.ta.philips.com:9443/ccm/proxy?uri=https://nlybstqvp4ms183.code1.emi.philips.com/cqweb/oslc/repo/CQMS.PMS_TEST.BST_VALIDATION/db/PMSlc, status code: BadRequest
If I copy+past the mentioned URL (https://clm-sandbox.ta.philips.com:9443/ccm/proxy?uri=https://nlybstqvp4ms183.code1.emi.philips.com/cqweb/oslc/repo/CQMS.PMS_TEST.BST_VALIDATION/db/PMSlc) into FireFox (Debugger mode), the webpage replies:
Only using the later part of the URL (thus: https://nlybstqvp4ms183.code1.emi.philips.com/cqweb/oslc/repo/CQMS.PMS_TEST.BST_VALIDATION/db/PMSlc) works fine. I'm asked to log in, and the XML page opens.
imho the login dialog is what I expected to get, as I do when linking Work Items to ClearQuest records from VS. Instead I get an error message, when I do this for changesets.