r4 - 2022-08-01 - 17:55:32 - MichaelRoweYou are here: TWiki > 
Deployment Web > DeploymentTroubleshooting > ReportingTroubleshooting
Deployment Web > DeploymentTroubleshooting > ReportingTroubleshooting Troubleshooting the Jazz Reporting Service 
Authors: MatthieuLeroux, PhilippeCheavlier, FrancescoChiossi Build basis: Build basis: JRS 6.x and later
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.
Where is the issue?
Reporting issue usually involve multiple products, for example when a report shows the wrong data, is it an issue with the query in Report builder, is it an issue with the datasource (LQE or DCC), does the application exposes the right data to LQE or DCC?Data Warehouse Datasource
describe here a use case that involves a data warehouse reportLQE Datasource
describe here a use case that involves an LQE 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
Related topics: Deployment web home, Deployment web home
External links:
Additional contributors: TWikiUser, TWikiUser
-
Deployment web
-
Planning and design
- Installing and upgrading
- Migrating and evolving
- Integrating
- Administering
- Monitoring
- Troubleshooting
- ELM SaaS
Community information and contribution guidelines 
Topic list 
Search 
Advanced search 
Notify 
RSS 
Atom 
Changes 
Statistics 
Web preferences 
NOTE: Please use the Sandbox web for testing -
To do
- Under construction
-
New
-
Updated
-
Constant change
- None - stable page
- Smaller versions of status icons for inline text:
-
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use. Please read the following disclaimer.