In RTC (ccm), while adding Association to other OSLC project getting error
In RTC (in ccm), logged in as admin mode. I want to add Association with a third party project named(PP_s) which is OSLC enabled. Even I have added the "rootservices" url in the "Friends (Outbound)" field and logged in. This Third party project (PP_s) has Oauth implemented. Rootservices even catalog urls are tested separately and the pages are opening in OSLC format.
Now when I wanted to add an association by clicking add and selecting this PP_s project then I am getting follwing things
1. Not getting any value in "Association" dropdown.
2. in "Artifact Containers:" field getting the message as follows- "No artifact container catalogs available in the selected application for the possible associations. "
Now when I wanted to add an association by clicking add and selecting this PP_s project then I am getting follwing things
1. Not getting any value in "Association" dropdown.
2. in "Artifact Containers:" field getting the message as follows- "No artifact container catalogs available in the selected application for the possible associations. "
One answer
1.Have you defined the link to your service provider catalog in the root services document?
A typical entry would look like
<oslc_cm:cmServiceProviders rdf:resource="<%= catalogUri %>" />
2.Have you defined the oslc:domain correctly in the catalog and the service?
an example would be (Assuming your 3rd party tool is a CM provider)
<ns9:domain ns5:resource="http://open-services.net/ns/cm#"/>
where xmlns:ns9="http://open-services.net/ns/core#"
and xmlns:ns5="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
3. You can also debug the break point in the provider to check whats being requested from RTC and the corresponding response. This should tell you if any exceptions are thrown at the provider
A typical entry would look like
<oslc_cm:cmServiceProviders rdf:resource="<%= catalogUri %>" />
2.Have you defined the oslc:domain correctly in the catalog and the service?
an example would be (Assuming your 3rd party tool is a CM provider)
<ns9:domain ns5:resource="http://open-services.net/ns/cm#"/>
where xmlns:ns9="http://open-services.net/ns/core#"
and xmlns:ns5="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
3. You can also debug the break point in the provider to check whats being requested from RTC and the corresponding response. This should tell you if any exceptions are thrown at the provider