Default connection error from reporting files in CLM 3.0.1
I downloaded the configuration files for reporting (XDC files) from my CLM server to use in my Insight 1.0.1.1 system. I tested the connection in the XML Data Configuration tool, and found that the rqm301.xdc connection tested just fine.
From both the jfs301.xdc and workitem301.xdc file, when I tested the connection I get the message:
I checked the documentation and did not see anything about updating the default URL that came with the XDC file. The only help text I found on that error message was "Provide a valid URL or correct authentication of the resource group." Could this possibly be a licensing issue, or is it really the URL? Do you need a specific RTC license assigned to the user doing the reporting? I don't see anything in the documentation that indicates this. Any help would be great - thanks!
From both the jfs301.xdc and workitem301.xdc file, when I tested the connection I get the message:
"CRRRE2841E: The resource group cannot be accessed."
I checked the documentation and did not see anything about updating the default URL that came with the XDC file. The only help text I found on that error message was "Provide a valid URL or correct authentication of the resource group." Could this possibly be a licensing issue, or is it really the URL? Do you need a specific RTC license assigned to the user doing the reporting? I don't see anything in the documentation that indicates this. Any help would be great - thanks!
2 answers
To give some additional info.... the URL listed in the Workitems.xdc file is: https://<host>:<port>/ccm
This URL fails, but if I add /rpt to the end, testing the connection succeeds. However, the Resource Groups all have /rpt listed so while the connection works, the ETL will fail.
Has anyone else seen this?
This URL fails, but if I add /rpt to the end, testing the connection succeeds. However, the Resource Groups all have /rpt listed so while the connection works, the ETL will fail.
Has anyone else seen this?
Hello.
The message that you see is actually not an error, but the tools way of
saying that it is unable to complete the test. The problem is that this
field contains a base url that is not complete. The different resources
append to this url and then those provide correct http error codes by
the servers. A workaround would be to append to the url the missing
parts for any resource such as /rpt/repository/workitem. Run the test
and then remove it again to restore the correct base url and save.
This issue is currently tracked here. Feel free to add your comments and
requirements to it:
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/46859
Best regards,
Peter Haumer.
On 8/5/2011 7:53 AM, jmw2 wrote:
The message that you see is actually not an error, but the tools way of
saying that it is unable to complete the test. The problem is that this
field contains a base url that is not complete. The different resources
append to this url and then those provide correct http error codes by
the servers. A workaround would be to append to the url the missing
parts for any resource such as /rpt/repository/workitem. Run the test
and then remove it again to restore the correct base url and save.
This issue is currently tracked here. Feel free to add your comments and
requirements to it:
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/46859
Best regards,
Peter Haumer.
On 8/5/2011 7:53 AM, jmw2 wrote:
To give some additional info.... the URL listed in the Workitems.xdc
file is: https://<host>:<port>/ccm
This URL fails, but if I add /rpt to the end, testing the connection
succeeds. However, the Resource Groups all have /rpt listed so while
the connection works, the ETL will fail.
Has anyone else seen this?