July 7, 2020
Jazz Reporting Service
Default reporting option for Jazz solutions
Jazz Reporting Service 6.0
Jazz Reporting Service 6.0 New & Noteworthy
Jazz Reporting Service is a new offering that provides an alternative to Rational Insight. It is not based on Cognos and it includes these components:
- Report Builder (formerly Jazz Reporting Service)
- Lifecycle Query Engine
- Data Collection Component
- ALM Cognos Connector
Jazz Reporting Service is an optional program for Collaborative Lifecycle Management
The 6.0 release is a continuation of the 5.x releases.
Jazz Reporting Service can now be installed using the CLM Web Installer and is also included in the IBM Installation Manager CLM repositories.
Report Builder is a new capability that provides some useful ready-to-use reports for software lifecycle
management. The service is easy to set up and provides integration with the CLM dashboards through the widget
catalog. The widget catalog includes 21 ready-to-use reports that cut across testing, requirements management,
and change management. Some reports show a table of information and others visualize the information in the
chart format that is best suited to the data being displayed.
In the Report Builder you can quickly set up your data sources and import the ready-to-use reports to start working with them from the dashboard widget catalog. If new reports become available in the future, you can import the updates or additions.
New operators for the Planned For condition
Now, if you add a condition to the planned for attribute for work items, the parent and its immediate children are implied to be part of the selection. Use one of these new operators:
- is any of selected or immediate children - for any selection, any immediate children become part of the condition.
- is not any of selected or immediate children - for any selection, any immediate children are also part of the condition that excludes records that match them.
The default operators, "is" and "is not", consider only the explicitly selected elements in the report. For existing reports, you must edit and modify the planned for condition to use one of the new operators if you want to include children.
Ability to specify whether a condition is required at run time
In previous releases and milestones of the Report Builder, the Status Group Category attribute allowed users to query on work items thatare open, in progress, or closed. Selection is now consistent with Rational Team Concert, so that you can add a condition to find resolved or unresolved work items. Existing reports are automatically converted to this new representation at run time or on subsequent edits.
Unassigned option available for hierarchical attribute conditions
Previously, you could not report on unassigned values for hierarchical attribute conditions. This ability is important for tracking work items that might not have their fields set properly or are pending, as well as when filed against categories are typically owned or associated with a team. If the team is missing, it is assumed to be the root project area. To create a condition in this scenario, you must specify that the team is unassigned.
Ability to specify whether a condition is required at run time
Now you can require a condition when a report is run on the dashboard. If the condition is unlocked and required, before someone can run the report for the first time, they must choose values for the condition.
Then, before they can run the report on the Use page or the dashboard, users must provide a value for the required filter.
Icon indicating whether results are cached
When paging through report results, Report Builder caches the initial results on the server, so that the query doesn't have to be re-run when a user switches to the next page or changes the number of items per page. This ability dramatically improves the performance of complex queries.
If you want to force the results to be current with the data warehouse, jsut click the icon to re-run the query and display new results for the current page. If you don't see the icon when running your report, the results are current.
Filters view refresh
Some minor updates clarify actions in the Filters pane when running a report. The Clear button has changed to the Revert to default choices link, which changes all filter values back to those selected when the report was created. Also, for a particular filter, the actions are now more explicit.
Easier-to-read pie chart percentages
The percentage numbers on pie chart graphs are bigger and have better contrast so that they are easier to read.
Lifecycle Query Engine
Lifecycle Query Engine (LQE) implements a linked lifecycle data index over data provided by one or more lifecycle tools. A lifecycle tool makes its data available for indexing by exposing its data by using a tracked resource set, whose members MUST be retrievable resources with RDF representations, called index resources. An LQE index built from one or more tracked resource sets allows SPARQL queries to be run against the RDF dataset that aggregates the RDF graphs of the index resources. Thus, data from multiple lifecycle tools can be queried together, including cross-tool links between resources.
Lifecycle Query Engine
Support with Rational Engineering Lifecycle Manager
Lifecycle Query Engine is supported as a data source for use with Rational Engineering Lifecycle Manager, but is an unsupported technical preview feature for any other CLM 6.0 application. LQE as a data source for reporting on configurations is also in technical preview, even with Rational Engineering Lifecycle Manager.
Jazz Single Sign-On (SSO) support
Lifecycle Query Engine (LQE) now supports Jazz single sign-on for both inbound and outbound authentication. LQE can delegate authentication to a Jazz authentication server. When configured with Jazz SSO for inbound authentication, LQE can index data sources that also use Jazz SSO authentication.
LQE automatically detects configuration resources and their selections and gives users the option to scope queries to a configuration. The default SPARQL endpoint is still the “all data” endpoint, which queries all data in the index; to include configuration information in queries, you must select one of the new configuration scoped SPARQL endpoints.
Base Log Indexing
When certain error conditions are detected, base log processing is retried, just as with current change log indexing.
Federated Query Support from LQE to LQE supporting Oauth and SSO
JTS setup and configuration enablement for LQE
Multiple data partitions
LQE can store indexed data in multiple partitions, so data can be compartmentalized into separately queryable indexes, leading to better query performance. For each partition, administrators can specify a SPARQL ASK query that determines which resources to add to that partition. Administrators can specify a SPARQL CONSTRUCT query for each partition to alter data before it is added to a partition.
RDF patch for creation events
LQE supports RDF patch for creation events, so that it is easy to efficiently propagate through the tracked resource set created resources that are derived from existing sources but differ only in small ways. For example, the RDF patch helps you quickly create new artifacts from copies when the changes are minor.
Data Collection Component
The CLM Java ETLs have been replaced with the Data Collection Component. Install and configure the Data Collection Component to report on data warehouse data. Designed to address key performance and deployment concerns with the current ETL solutions, Data Collection Component employs parallel processing and optimizes system resource utilization by using available system resources to process the data efficiently. Overall execution time for the ETL process for CLM data is reduced, whether there is a single instance or multiple instances to process.
ALM Cognos Connector
ALM Cognos Connector enables a Jazz server to connect to an existing Cognos BI server already deployed in a WebSphere Application Server environment. This component provides the configuration for connecting the Jazz and Cognos BI servers. When it is configured, users can create and manage Cognos-based reports based on the artifacts from the Jazz server, similar to the capability provided by Rational Reporting for Development Intelligence in previous versions.
For more information on how to use the ALM Cognos Connector with a Cognos BI server and move existing reports to the new Cognos BI server refer to this topic: Migrating Rational Reporting for Development Intelligence reports to Cognos Business Intelligence using the ALM Cognos Connector