Workarounds: Reporting problems in Rational Quality Manager 4.0.2
The table of contents lists the known problems, workarounds, and limitations related to the Reporting functionality in the Rational Quality Manager 4.0.2 release.
Workarounds
Use the links below to learn more about the issues and workarounds in this release:
- When you run the Requirement Traceability Report, a report error is generated if there is a test plan that is not linked to a requirement collection populated with requirements.
- The QM reporting ETL jobs may fail when the ETL is configured to use JTS (oAuth) authentication and there is a HTTP fronting server in the application topology.
Limitations
[A limitation is defined as an issue that does not have a workaround; enter a descriptive summary that serves as a TOC entry below. The TOC entry should be identical to the first sentence or phrase used in the issue. If your component does not have any limitations, delete this section.]
Use the links below to learn more about the limitations (an issue, without a workaround) in this release:
- When you run the Requirement Traceability Report, a report error is generated if there is a test plan that is not linked to a requirement collection populated with requirements.
- Enter the next summary here
Problem Summary
When you run the Requirement Traceability Report, a report error is generated if there is a test plan that is not linked to a requirement collection populated with requirements.
Problem
The problem occurs in the following instances:
- At least one test plan is not linked with a Requirement Collection
- One or more test plans are linked with Requirements Collections, but all those Requirement Collections are empty (they do not have any associated requirements)
If any of the cases given above is true (point 1 or 2), then the error appears, even if the test plans contain test cases that are linked to requirements.
Workaround
Complete the following steps:
- In the Rational Qualtiy Manager project area, link all test plans with a non-empty requirement collection.
- Run all data collection jobs.
- Run the report again.
Related Information
The following link points to related information:
Problem Summary
The QM reporting ETL jobs may fail when the ETL is configured to use JTS (oAuth) authentication and there is a HTTP fronting server in the application topology.
Problem
The QM ETL data collection jobs fail. You will see entries similar to the following in qm-etl.log:
RQMPriorityETL:execute AQXRE5002E Artifact data was not pulled into the reporting data warehouse because of the following exception: com.ibm.rational.etl.common.exception.ETLException: org.xml.sax.SAXParseException: Content is not allowed in prolog.
java.sql.SQLException: com.ibm.rational.etl.common.exception.ETLException: org.xml.sax.SAXParseException: Content is not allowed in prolog.
The following two conditions must be met:
- You are using JTS (oAuth) authentication for the ETL user
- You have a HTTP fronting server or reverse proxy, such as Apache HTTP or IBM HTTP Server
Workaround
Complete the following steps:
- In the IBM HTTP Server, add “SetEnv websphere-nocanon 1” to httpd.conf.
- In Apache Mod Proxy, add a ProxyPass directive “nocanon” for the QM web application URL.
Related Information
The following links point to related information:
Copyright © 2013 IBM Corporation
Yes