How to fetch BIRT reports design files from the server?
![]()
Prasad Rachuri (16●3●2)
| asked Sep 24 '13, 2:00 p.m.
edited Feb 17 '14, 4:47 a.m. by Krzysztof Kaźmierczyk (7.5k●4●80●103)
Hi Team,
I have created few BIRT reports and uploaded to RTC server and using them currently. Due to OS migration I lost Birt reports in my machine. Is there any way to download my reports back to my system from RTC server?. |
4 answers
![]()
Here is an example where I am trying to load the report design whose ID is: workitems.Burndown from a project area named P1.
The following URL will give me the ID of the attached design file:
Comments Rafik,
Quick question here: What other attributes of this can be added to (key|value/contentId) ? Links references are ok (make me fish).
Hello!
Thanks!
The same approach works in Rational Quality Manager with Rational Publishing Engine DTA files after some modifications.
|
![]()
I don't think that is possible, currently. It would be a Swell Thing (r) to have, though as sometimes users can induce RTC coma from ill-written reports and it would be helpful to be able to extract the report design (as an admin) for expert examination.
|
![]()
Tried it on CLM version 5.0.2 using the method provided by Rafik above, and I am able to get the BIRT report design that I deployed. You need to know the Identifier that you specify when deploying the BIRT report as Report Resource to the CCM server. It does not work for me for the IBM built-in reports "workitems.Burndown", as it does not show the contentId. However, it provides a way for you to get the report design from the server, if your local one on your pc is corrupted.
|
![]()
The out of the box reports that get bundled with RTC can be found in one of the server bundles:
<server install location>\server\conf\ccm\sites\rtc-commons-update-site\plugins\com.ibm.team.examples.reports.common_XXXXXXXXXXXXXXXXXX.jar Please use any zip utility to unjar the above and you will find the BIRT design files. |
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.
Comments
To go along with Rafik's workaround, I have filed 2 enhancement requests related to this post: