JRS, LQE, RB, DCC… When it comes to reporting for the IBM Collaborative Lifecycle Management (CLM) and Continuous Engineering (CE) solutions, there are enough acronyms to make alphabet soup! In this post, I’ll define the acronyms and describe the components and how they fit together, as illustrated in this architecture overview:
The links in this article go primarily to the IBM Knowledge Centre topics and Jazz.net pages for the components and offerings.
Let’s start with the data stores used for reporting. There are two data stores:
- Data warehouse (DW)
The DW uses a database you specify when you configure your CLM/CE environment. It includes operational data store (ODS) tables for reporting on current data about the resources, and fact and dimension tables to support metric and trend reports.
To populate the DW, the Data Collection Component (DCC) application runs scheduled jobs that extract and load data from the CLM/CE applications. You register the DCC application when you configure your environment.
Reports use SQL to query the DW.
- Lifecycle Query Engine (LQE)
LQE is both a data store and an application; you register LQE when you configure your environment. LQE stores data in an index based on Resource Description Framework (RDF) graphs – essentially an aggregation of RDF triple statements.
To generate and maintain the index, LQE consumes Tracked Resource Set (TRS) feeds that are provided by the CLM/CE applications.
Reports use SPARQL to query LQE.
Note: If you are using configuration management to version requirements or tests, you’ll also see a third data source: “LQE scoped by a configuration”. This is another endpoint to the LQE data source to ensure correct reporting on versioned artifacts.
There are various ways to report on the application data:
- The Jazz Reporting Service (JRS) comprises multiple applications and services, including DCC and LQE, to provide interactive reporting across the solution. The “face” of JRS is Report Builder (RB), a graphical tool for authoring and running reports which also includes administrative tools and tutorials.
You can report against data in either the DW or LQE; when you author the report in RB, you choose which data source to use.
- Rational Engineering Lifecycle Manager (RELM) is a separate application that provides advanced visualizations to support impact analysis and other explorations of linked data. RELM uses data from LQE.
- Rational Publishing Engine (RPE) is a separate offering for generating document-style reports from CLM/CE as well as other applications. RPE extracts “live” data from the CLM/CE applications directly using reportable REST APIs.
- BIRT (Business Intelligence and Reporting Tools) is an open-source platform for visualization and reports. The Rational Team Concert and Rational Quality Manager applications include several BIRT reports and dashboard widgets, although we recommend using JRS to build any new reports. BIRT reports use data from the data warehouse, and in a few cases, directly from the application.
- For those looking for advanced business intelligence beyond the scope of the CLM/CE applications, IBM Cognos provides stand-alone solutions that can integrate data from many sources for advanced mining and insight. The optional ALM Cognos Connector exposes CLM/CE data to IBM Cognos.
There are additional nuances to the CLM/CE reporting story, especially when it comes to global configuration management (which you can read more about in this Jazz.net article), specific applications, and previous releases. Read more about reporting in the IBM Knowledge Center.
I hope this has helped clarify the various components and acronyms related to CLM/CE reporting. Below is the alphabetical list of acronyms and definitions for reference. Have fun exploring these data sources and technologies as you implement your CLM/CE reporting strategy!
BIRT – Business Intelligence and Reporting Tools. Open source project for interactive reports on data warehouse and some live data.
DCC – Data Collection Component. Extracts data from CLM/CE applications and loads data warehouse.
DW – Data Warehouse. Database store for current data and metric/trend reporting, using SQL.
JRS – Jazz Reporting Service. Component that comprises DCC, LQE, RB, and other services to support interactive reporting for CLM/CE applications.
LQE – Lifecycle Query Engine. Data index based on RDF graphs, using SPARQL. Also an application that creates and maintains the index using TRS feeds from the CLM/CE applications.
ODS – Operational Data Store. DW tables for reporting on current data representation of the resources.
RB – Report Builder. Graphical tool for authoring and running reports against DW or LQE data.
RDF – Resource Description Framework. A framework for describing resources on the web using triple statements.
RELM – Rational Engineering Lifecycle Manager. Application for data visualization using LQE data.
RPE – Rational Publishing Engine. Application for generating document-style reports using reportable REST APIs to extract data directly from the CLM/CE applications.
TRS – Tracked Resource Set. An RDF representation of application resources or artifacts; LQE consumes TRS feeds to collect data from theh CLM/CE applications.