Jazz Reporting Service (JRS) and Rational Publishing Engine (RPE) Workshop

This workshop is intended to provide insight into the Jazz Reporting Service (JRS) introduced in CLM v5.0 and updated recently in v6.0.1.  Jazz Reporting Service (JRS) is a lightweight reporting solution that provides practitioners the ability to create their own reports in a powerful yet easy to use interface (without requiring Cognos expertise).  The JRS interface is designed to be intuitive without any technical knowledge of the underlying data warehousing technology. Users can create table based or graphical reports for single artifact types, specify the set of characteristics and filter on the artifact type that determines which data will be displayed.

You can also control the formatting of results with an interactive preview and which data of the artifact will be displayed. The resulting report can be run inside the JRS user interface and subsequently exported to Excel or Rational Publishing Engine, if desired. Alternatively the report can be added to a dashboard as a widget alongside the existing reports provided by CLM or the out of the box reports from JRS.

To manage these new reports, there is an explorer view that shows the reports stored in the JRS. The reports can be organized by tags, visibility and / or filtered through a text search. This is also a launch page for editing or duplicating existing reports shared by other team members.

What’s New in 6.0.1

The 6.0.1 release of JRS improves the simple and easy way to build practitioner defined reports. This latest release now supports the ability to create reports on historical trends and how a set of metrics has changed over time. In addition, you can look at the aging of a set of work items at a single point in time. For more details, see the blog post Improved CLM project reporting with Jazz Reporting Service 6.0.1

Jazz Reporting Service 6.0.1 Release Highlights:
  • Historical trending or time-series reports
  • Report customizations (color, legend labels)
  • Configuration-aware reporting
  • Aging reports (point in time)
  • Near live operation reporting with LQE

The 6.0 release of JRS made major advancements on the foundation of the JRS and DCC components of 5.0.x.  Jazz Reporting Service (JRS) was adopted as the umbrella name for the whole set of reporting components: Report Builder (formerly known as Jazz Reporting Service in 5.0.x, Data Collection Component (DCC), Lifecycle Query Engine (LQE, in technical preview) and the ALM Cognos Connector (repacking of RRDI). For more details, see the blog post What’s new in Reporting for Collaborative Lifecycle Management 6.0

Jazz Reporting Service 6.0 Release Highlights

  • Roll-up/summary Reports
  • Dynamic Conditions
  • Graphical reports with drill down
  • Traceability report improvements
  • Ready to Copy reports which provide a quick template for novice users
  • Interactive runtime filters
  • New OOTB reports for operational reporting of burn up/down, velocity, and trending
  • Export to Excel and Rational Publishing Engine for further analysis

Videos & Tutorials

There is a YouTube video series on JRS and RPE as well as a few Jazz.net articles listed below:


Exercises

The exercises included in this workshop are designed to introduce the JRS and RPE user interfaces and then demonstrate how to use those interface effectively to create simple cross-project and traceability reports.

You will need the following configuration in order to complete the exercises.

Environment

  • Collaborative Lifecycle Management (CLM) 6.0.1 with Money that Matters Sample project
  • Jazz Reporting Service (JRS) 6.0.1
  • Data Collection Component (DCC) 6.0.1
  • Rational Publishing Engine (RPE) 2.0.1
  • Rational License Key Server
  • DB2 10.5.0.1 Express

Instructions

  1. Download the JRSLabs.pdf
  2. Download the RPELabs.pdf
  3. Begin the workshop.

Contents of the workshop

JRS

Lab 1: Exploring the Jazz Reporting Service interface

Lab 2: Creating a simple cross-project report

Lab 3: Creating a traceability report

Lab 4: Summary Reports

Lab 5: Dynamic Filters

Lab 6: Historical Trend Reports

Lab 7: Aging Reports

RPE

Lab 1: Exploring the Rational Publishing Engine Desktop Interface

Lab 2: Creating a Requirements document

Lab 3: Create a traceability document with RPE

Lab 4: Create a traceability document with RPE & JRS

Lab 5: Formatting a document

Lab 6: Create a test plan document from RQM

Lab 7: Create a sprint document from RTC

Lab 8: Create a traceability document with details using RPE and JRS

Lab 9: Explore the RPE Web UI

Lab 10: Create and run a custom report in the RPE Web UI

Appendix A – Troubleshooting



About the author

Rosa Naranjo is a member of the Watson Internet of Things Unleash the Labs team.  The Unleash the Labs team is a worldwide group of development specialists who assist customers with the Collaborative Lifecycle Management solutions.

Dragos Cojocari was the Rational Publishing Engine (RPE) architect from the product’s inception. His blog, RPE Actual contains many great RPE articles for document generation users and continues to be active with articles from the RPE development team.

Nithya Rajagopalan is the Rational Publishing Engine (RPE) architect and has been a member of the development team for many years. She has presented on RPE topics at Interconnect and other internal and external conferences.

Feedback
Was this information helpful? Yes No 6 people rated this as helpful.