Troubleshooting the Jazz Reporting Service

This page is the starting point to find information and techniques that you can use to diagnose and troubleshoot issues related to reporting, Lifecycle Query Engine (LQE), Data Collection Component (DCC), Report Builder (also know as JRS - Jazz Reporting Service). This page is expected to be used by administrators of IBM Engineering Jazz Reporting Service as supplemental guidance to the IBM Documentation.

IBM Engineering Jazz Reporting Service users should use the IBM Support Jazz Reporting Service 101 which contains links to News; Must gathers; Technical Notes; JRS video tutorials; and more.

Where is the issue?

Reporting issues usually involve multiple products. For example, when a report shows incorrect or stale data:

• is it an issue with the query in Report builder?
• is it an issue with the datasource within LQE or DCC
• does the application expose the right data to LQE or DCC?

If the issue is related to performance, then use Mustgather: Investigating LQE or LDX performance problems and raise a ticket with IBM Support.

Lifecylce Query Engine issues

Configuration aware reporting Troubleshootingcovers many of the known issues for those who use Lifecycle Query Engine reporting on configurations.

• Reindex operations
  • What to check before requesting a reindex on a LQE or LDX datasource
  • Reasons and considerations for reindexing all datasources again
• How can I make sure the set of data from a data provider is complete in LQE/LDX?
• What can happen from the Data Provider (TRS)?
• What can happen fetching resources identified by TRS?
• In a configuration-aware report, what controls which artifacts are within scope?
  • Report Builder - Data Completeness Checker
• What can be done to check that selection resources are correct?
• LQE status information

Data Warehouse Datasource

describe here a use case that involves a data warehouse report

Additional Log4j traces

Prior to versions 7.0.1 SR1 / 7.0.2 SR2: here are some traces that can be added in log4j.properties per product

For versions 7.0.1 SR1 / 7.0.2 SR2 and beyond: traces are to be added in log4j2.xml per product

• Report Builder

• Lifecycle Query Engine
• Data Collection Component

Other scenarios

Related topics: Deployment web home, Deployment web home

External links:

• IBM, IBM Support Jazz Reporting Service 101

Additional contributors: TWikiUser, TWikiUser