How to publish the Customized Advanced burndown out of the box BIRT report and re-publish to the Master Project
Hello,
I have customized two out of the box Advanced Burndown Report (Micro & regular).
* I modified the out of the box report in CCM 4.0.5 (by pulling it out of the com.ibm.team.examples.reports.common_3.1.500.v20131025_0102.jar) and overwrote the report file in the jar file and re-deployed it successfully.
Now there is a need to keep the out of the box report separate from out of the box reports (e.g.. like creating the custom reports into a separate jar file) and deploy it (to existing and future Master Projects and to Child Projects). Can someone help with the steps involved please.
* How do I add it to the existing Master Project (we have a Master and Child Project setup).
* When I directly add the reportDesign file as a report resource where is the report file stored? In the DB? How can I make new reports added to the process template? ( I am assuming using the custom report jar). Would like to understand the structure inside the Jar file and setting the dependency (when I click on the "Advanced Burndown chart" Widget title it takes it to the regular "Advanced Burndown chart" ).
Thanks
RK
2 answers
Check out the "Upload the report to the Rational Team Concert server" section of the below article.
http://www.ibm.com/developerworks/rational/library/10/creatingcustomreportswithbirtandrtc-part1/
http://www.ibm.com/developerworks/rational/library/10/creatingcustomreportswithbirtandrtc-part1/
Comments
The best way to manage custom reports is the following:
1) Never modify the out of the box reports. Instead, you should clone them and publish the custom report using a new identifier.
2) Publish all the custom reports to some chosen project area.
3) Use "Deploy New Resources" Action from the "Report Resources" page in the web UI to propagate the custom reports to other project areas. The page will let you import reports from other project areas. The imported reports will be automatically synched when the original copy created in step 2 changes.
1) Never modify the out of the box reports. Instead, you should clone them and publish the custom report using a new identifier.
2) Publish all the custom reports to some chosen project area.
3) Use "Deploy New Resources" Action from the "Report Resources" page in the web UI to propagate the custom reports to other project areas. The page will let you import reports from other project areas. The imported reports will be automatically synched when the original copy created in step 2 changes.
Comments
showing 5 of 9
show 4 more comments