Reporting architecture overview

Reporting requires data sources to provide the data for the report, a way of getting data from the sources to the output, and a way of specifying which data to report on and how to present it. This section describes the basic architecture that supports these steps for reporting on IBM® Engineering Lifecycle Management (ELM) application data.
Figure 1. Reporting architecture
Reporting architecture

Data warehouse reporting architecture

With data warehouse reporting, there are three main required architectural components in ELM: applications and their data storage; Jazz™ Team Server and its data storage; and the data warehouse. There is also an optional reporting component: Jazz Reporting Service, which includes Data Collection Component, Report Builder, and Lifecycle Query Engine. See Deciding which ELM reporting option to use. The data warehouse does not contain information about configuration-enabled projects. To report on configuration data, use Lifecycle Query Engine.

All of the components can be installed together or separately.

Lifecycle Query Engine

You can use indexed data from Lifecycle Query Engine data sources to report on artifacts across projects or versioned data in configurations.

Live reporting architecture

With live reporting, data in the application and Jazz Team Server data storage is accessed using REST APIs and transform files, the same way that the data collection jobs access the information in data warehouse reporting, but the data is immediately pulled from the application data store and transformed into report output, rather than getting stored in the data warehouse.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki