IBM Rational Quality Manager
Quality management · Manual testing · Continuous improvement
This is not the most recent version. We recommend Rational Quality Manager 6.0.6.1 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog. Rational Quality Manager 3.0.1.1 Release Notes
This release is a service release of Rational Quality Manager 3.0.1. It contains fixes for product defects including important security updates. As such, it is a recommended upgrade for all RQM 3.0.1 customers.
The following notes detail important fixes and known issues in this release of Rational Quality Manager. For information about fixes and known issues in the Jazz Team Server and the Requirements Management and Change and Configuration Management applications, please ensure that you also read the Jazz Foundation 3.0.1.1 Release Notes, the Rational Requirements Composer 3.0.1.1 Release Notes, and the Rational Team Concert 3.0.1.1 Release Notes.
Applying the 3.0.1.1 fix packKnown issues and workarounds
Fixes included in this release
Applying the 3.0.1.1 fix pack
The upgrade from 3.0.1 to 3.0.1.1 is a straightforward set of steps that extracts configuration information from, but does not alter, the 3.0.1 installation. For details, see Upgrading to version 3.0.1.1.
Known issues and workarounds
The RQM 3.0.1.1 Release Notes query lists the known issues and workarounds in this release.
New features that impact customizations for users who integrate with Rational Insight 1.0.1.1
If you are using Insight 1.0.1.1 with CLM 3.0.1 and have created customizations, then please review the following list of changes made to the RQM XDC and Data Manager ETL files for the 3.5 release and merge your changes accordingly into the new versions of these artifacts.
RQM XDC
- Support soft-delete for categories (46186): Created two new template tables and resources "Category" and "CategoryType" to load category and categoryType feeds
- Not All DOORS Requirements Included in BIRT Reports (52963): Added a new uuid reference to the RQMTestPlan_Relationships resource
- ETL needs to fill in linkage between build record and Test Suite Log (52984): Added buildrecord_uuid to RQMTestSuiteLog resource
RQM Data Manager ETL
- Support soft-delete for categories (46186): New RQM3_Category and RQM3_CategoryType builds, removed RQM3_ProjectCategory build from the job
- ETL needs to fill in linkage between build record and Test Suite Log (52984): Updated Test Suite Log build with buildrecord_uuid
- RQM 3011 DM ETL job is hanging on RQM3_TestSuite build on MS SQL Server 2005 (54116): Unchecked the "Share database connection" in the two deliveries in the RQM3_TestSuite build
- ETL Catalog should rename the version from RQM3.0 to RQM3.0.1 (51207): Renamed all packages from 3.0 to 3.0.1, because RTC 3.0 must use the RTC 2.x ETL jobs; added new folder with QM 3.0.1.1 specific changes to support 3.0.1 and 3.0.1.1 server with the same catalog.
- RQM3_TestPhase ETL build deliver null value to non-nullable column (52653):
- Test Phase: Set the default values expectedTotalPoints: 0, expectedDefects: 0, expectedValidityRate: 0.00,
- Iteration Exec Detail: added 0 as default value to points attempted and points completed, Test Plan Objective Status: provided default values for actual value as 0 and group order as -1
Manual fix for Data Warehouses migrated from Common Reporting 1.0 to RRDI 2.0.1
If you have migrated your data warehouse from Common Reporting 1.0 when you installed CLM 3.0.1, then you need apply the following fixes to your database schemas. For further details, see Upgrade of existing data warehouse did not update the VW_REQUIREMENT_TESTPLAN_LOOKUP view (177623).
DB2
DROP VIEW RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP; CREATE VIEW RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP (TESTPLAN_ID, TESTPLAN_NAME, REQUIREMENT_ID, REQUIREMENT_NAME) AS ( SELECT RC.TESTPLAN_ID, C.NAME AS TESTPLAN_NAME, RC.REQUIREMENT_ID, R.NAME AS REQUIREMENT_NAME FROM RIODS.REQUIREMENT_TESTPLAN_LOOKUP RC JOIN RIODS.REQUIREMENT R ON R.REQUIREMENT_ID=RC.REQUIREMENT_ID JOIN RIODS.TESTPLAN C ON C.TESTPLAN_ID=RC.TESTPLAN_ID UNION SELECT RT.TESTPLAN_ID, T.NAME AS TESTPLAN_NAME, RRL.REQUIREMENT_ID, R.NAME AS REQUIREMENT_NAME FROM RIODS.REQUICOL_TESTPLAN_LOOKUP RT JOIN RIODS.REQUIREMENT_COLLECTION RC ON RC.REQUIREMENT_COLLECTION_ID=RT.REQUIREMENT_COLLECTION_ID JOIN RIODS.TESTPLAN T ON T.TESTPLAN_ID=RT.TESTPLAN_ID JOIN RIODS.REQUICOL_REQUIREMENT_LOOKUP RRL ON RRL.REQUIREMENT_COLLECTION_ID=RT.REQUIREMENT_COLLECTION_ID JOIN RIODS.REQUIREMENT R ON R.REQUIREMENT_ID=RRL.REQUIREMENT_ID); GRANT SELECT ON RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP TO USER RPTUSER;
Oracle
DROP VIEW RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP; CREATE VIEW RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP (TESTPLAN_ID, TESTPLAN_NAME, REQUIREMENT_ID, REQUIREMENT_NAME) AS ( SELECT RC.TESTPLAN_ID, C.NAME AS TESTPLAN_NAME, RC.REQUIREMENT_ID, R.NAME AS REQUIREMENT_NAME FROM RIODS.REQUIREMENT_TESTPLAN_LOOKUP RC JOIN RIODS.REQUIREMENT R ON R.REQUIREMENT_ID=RC.REQUIREMENT_ID JOIN RIODS.TESTPLAN C ON C.TESTPLAN_ID=RC.TESTPLAN_ID UNION SELECT RT.TESTPLAN_ID, T.NAME AS TESTPLAN_NAME, RRL.REQUIREMENT_ID, R.NAME AS REQUIREMENT_NAME FROM RIODS.REQUICOL_TESTPLAN_LOOKUP RT JOIN RIODS.REQUIREMENT_COLLECTION RC ON RC.REQUIREMENT_COLLECTION_ID=RT.REQUIREMENT_COLLECTION_ID JOIN RIODS.TESTPLAN T ON T.TESTPLAN_ID=RT.TESTPLAN_ID JOIN RIODS.REQUICOL_REQUIREMENT_LOOKUP RRL ON RRL.REQUIREMENT_COLLECTION_ID=RT.REQUIREMENT_COLLECTION_ID JOIN RIODS.REQUIREMENT R ON R.REQUIREMENT_ID=RRL.REQUIREMENT_ID); GRANT SELECT ON RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP TO RPTUSER;
SQL Server
DROP VIEW RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP GO CREATE VIEW RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP (TESTPLAN_ID, TESTPLAN_NAME, REQUIREMENT_ID, REQUIREMENT_NAME) AS ( SELECT RC.TESTPLAN_ID, C.NAME AS TESTPLAN_NAME, RC.REQUIREMENT_ID, R.NAME AS REQUIREMENT_NAME FROM RIODS.REQUIREMENT_TESTPLAN_LOOKUP RC JOIN RIODS.REQUIREMENT R ON R.REQUIREMENT_ID=RC.REQUIREMENT_ID JOIN RIODS.TESTPLAN C ON C.TESTPLAN_ID=RC.TESTPLAN_ID UNION SELECT RT.TESTPLAN_ID, T.NAME AS TESTPLAN_NAME, RRL.REQUIREMENT_ID, R.NAME AS REQUIREMENT_NAME FROM RIODS.REQUICOL_TESTPLAN_LOOKUP RT JOIN RIODS.REQUIREMENT_COLLECTION RC ON RC.REQUIREMENT_COLLECTION_ID=RT.REQUIREMENT_COLLECTION_ID JOIN RIODS.TESTPLAN T ON T.TESTPLAN_ID=RT.TESTPLAN_ID JOIN RIODS.REQUICOL_REQUIREMENT_LOOKUP RRL ON RRL.REQUIREMENT_COLLECTION_ID=RT.REQUIREMENT_COLLECTION_ID JOIN RIODS.REQUIREMENT R ON R.REQUIREMENT_ID=RRL.REQUIREMENT_ID) GO GRANT SELECT ON RIDW.VW_REQUIREMENT_TESTPLAN_LOOKUP TO RPTUSER GO
Changes to project area permissions
Project area read-access permission in version 3 is handled differently than it was in version 2. Any version 2 project areas with a read-access policy set to Everyone will be exposed as a Public Project Area in version 3. For details, see Rational Quality Manager version 3 upgrade considerations.
User assistance
If you deploy RQM on a different server from where the help web application (clmhelp.war) is deployed, you must configure the location of the help war in the services.xml and teamserver.properties files. For details, see Configuring the location of the help in a distributed environment.
Fixes included in this release
The RQM Resolved APARs query shows the APARs fixed in this release.
Fixes to Rational Reporting
In addition, this release includes fixes to numerous defects related to RQM reporting. These include issues with Oracle support, migration support, data collection fixes, and many individual report fixes.
For Rational Insight users, this release contains a new version of the xdc file, called rqm3011.xdc. After applying the fix, you need to re-download the xdc file and configure it to be used with Insight. The new rqm3011.xdc replaces the old rqm301.xdc file. If you made customization to the old file, you need to manually re-apply or merge your customizations For details, see New features in Rational Insight and Importing and merging configurations files.
Also for Rational Insight users, this release includes a new version of the Cognos Data Manager Package (RQM).pkg. You need to download it from the patched server and import it into your Data Manager catalog. You will see new RQM jobs labeled with a 3.0.1.1 postfix. You need to use these jobs with this release. The Cognos Data Manager Package (CLM).pkg jobs provided by the Jazz Team Server have also been updated to automatically use these new 3.0.1.1 jobs. For details, see Integrating report packages with Rational Insight.
Note: This release does not include a fix to the following Rational Reporting enhancement request: There should be a message indicating why QM ETLs are not executing after upgrading using an existing data warehouse but before running migrateDatawarehouse command (56032)