IBM Support

Rational Quality Manager Interim Fix 6 for 4.0.7



IBM Rational Quality Manager 4.0.7_iFix006 has been made generally available and contains fixes to version 4.0.7 including all predecessor fixes.

Download Description

Table of Contents
Sections Description

The Change history section provides an overview on what is new in this interim fix with a description of any new functions or enhancements when applicable.

The How critical is this fix section provides information related to the impact of this interim fix to allow you to assess how your environment may be affected.

The Prerequisites section provides important information to review prior to the installation of this interim fix.

The Download package section provides the direct link to obtain the download package for installation in your environment.

The Installation instructions section provides the installation instructions necessary to apply this interim fix into your environment.

Click to review a complete list of the defects (APARs) resolved in this interim fix.

The Known side effects section contains a link to the known problems (open defects) identified at the time of this interim fix.

Supporting Documentation
Document Description

Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.

IBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.

The Jazz initiative consists of three elements: Platform, Products and Community. Explore the product page.

Find technical developer content and resources.


Prerequisites include:

IBM Rational Quality Manager 4.0.7 must be installed to apply this iFix.

Note: Before you install the server patch file, verify that no other test fixes are installed. If other fixes are installed, contact IBM Software Support.

Installation Instructions

Review the installation instructions to apply the iFix on the server:

Note: Before you install this server patch file, verify that no other test fixes or hot fixes are installed. If other fixes are installed, contact IBM Software Support.

For a CLM deployment on a single server, complete the following steps once.

For a distributed CLM deployment, complete the same steps on each server.

Procedure to install the server patch:

  1. Stop the CLM server.

  2. Verify whether the following directory exists: server_installation_directory/server/patch.
    • If the directory exists, back up and remove its contents.
    • If the directory does not exist, create it.

  3. Copy the server patch file into the /server/patch directory.

  4. Start the server.

Note: For a distributed CLM deployment, complete the same steps on each server.

Procedure to uninstall the server patch:

  1. Stop the CLM server.

  2. Back up and remove the contents of the following directory: server_installation_directory/server/patch

  3. Start the CLM server.

Note: For a distributed CLM deployment, complete the same steps on each server.

Download Package

The following sections provide detailed information related to this interim fix.

Click the FC link below to obtain the interim fix from Fix Central.

How critical is this fix?

Impact Assessment
Impact Description

This is a maintenance interim fix. It contains fixes for client-reported and internally found defects.

Test Results


Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:

  • Coding errors that cause a regression
  • Documentation or packaging problems that cause a regression
  • Errors reported in a new function delivered in a MDV that cause a regression

Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:

  • Fixed APARs which did not solve the original problem but did not break anything new
  • APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression

  • Regression and incomplete APARs are considered fix-in-error or MDV-in-error
  • Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
  • Issues in major releases due to new functionality do not apply in this definition

There are no known regressions to report.

In addition to the fixes listed in this document, the iFix may also contain fixes for security issues.

For more details, please refer to the IBM Product Security Incident Response (PSIRT) Blog.

Problems Solved

Defects resolved in this iFix.

This server patch contains fixes for the following defects:

APAR (WorkItem URL) Description
Rational Jazz Foundation

Parse error when running reports on server in Turkish locale.


[Process] Investigate an active migration fix for defect 262994.


bottleneck in ComponentRegistry.getComponentDescriptorForServiceUri (206501).


CLM database migration [DB2 to Oracle] failed due to 'CRJAZ1150E' The repository was not verified.


Too much synchronization on ComponentConfigurationRegistry.ensureMapsAreInitialized().


Reduce Lock Contention in a mixed client (N-1) environment (Backport 295511 to 407 ).


Expand RTC report: error CRJAZ0368I A SQL query..


Workaround missing resource content during deletion.


Deadlock issue in JNDI due to classloader problem.


Incorrect third argument to substr SQL function for server rename.


NPE in ManagedFloatingLicenseClient$LeaseCache.getCheckoutOperations.


Lucene crashes because of Mmap issue (Backport to 407).


TeamAreaRole ETL flips two columns (354920).

Rational Quality Manager

repository.common.ItemNotFoundException: Querying Lookup table, can not find any records for ManualExecutionScript.


Can't select test plan to generate TSER when Running Test suite.


Duplicating a Test Cases using the option 'Duplicate with copies' does not duplicate the Requirements Links.


Used by scripts list does not reflect changes.


Duplicate cases with associated archived scripts to a different project area problem.


AQXIN5014E error when generating PDF reports on test artifacts containing external IDs with URL-reserved characters.


The Built-in variables of RQM_TESTCASE_RESULT_WEBID and RQM_TESTCASE_RESULT_NAME are not created when running a command-line adapter test.


Incorrect use of operator causes performance issues with CQ Integration.


When updating a custom attribute on a Test Suite Result, while the test for the result is running, the custom attribute value is removed when the test completes(117722).


Exception while updating the script (script name); Failed to find delta predecessor.


Duplicating a Test Plan which is in Published state throws two types of errors.


409 (conflict) error response when updating a test case referencing an archived category using the OSLC QM V2 API.


Required Categories are not being validated in the backend.


Manual Test Script fields with long strings in Derby cause migration problems.


ReqPro - RRC Migration does not validate whether a Collection belongs to the migrating project correctly, leading to HTTP 412 errors.


Duplicating a test script that uses a datapool variable that is linked to an archived test script step will fail.


QM: Execution Variable created as a step doesn't work properly when copied using the REST API.


Bulk update of TCER fails with no permissions on team areas.


Unhandled NPE is thrown while retrieving test case with a work item itemReference.


RQM outputs TCER 'blocking' status incorrectly.


QM Built-in variables are visible in the result data even though the option to "Include built-in Variables" is disabled.


Migration to new script type is broken when script history is truncated.


Manual Script fails to be exported to PDF when an HTML table tag with no content is included in RTE section.


[RIT Integration] A failed icon is shown in the Test Details although the test result's verdict is "passed".


Error on execution console when displaying deleted Test Case Result "Item Handle must not be null ".


Project feed does not support paging.


QM: Back Link Errors when linking RTC Defect and bulk RQM test cases.


Unable to see TestScripts in Test case Section from a TestSuite.


Duplicating test case with "Duplicate with copies" option creates orphaned keyword copies.


QM Japanese character corruption in file name after run offline in RQM.


Requirement back link is not deleted when deleting a test case deleted.


RQM Test Plans->Requirement Section->Rational RequisitePro tab (no option to sort ascending/descending by any of the columns).


HiddenMenusWebUIInitializer loads data for all projects causing performance issues with many PAs.


QM: Unexpected behavior when deleting category values.


QM : Duplicating Test Scripts across project areas including Keywords.


Links new requirement to test case under coverage view,it shows as updated status in the Reconcile Requirement window.


Irrelevant TCERs for a TSER.


QM: TER creation does not get latest version of test script if the recent change in the test script is a keyword removal.


Multiple test script links are referencing to a keyword.


updating custom sections via a PUT has no effect.


Improve the performance of the QM - DNG Reconcile operation.


testBulkUpload() failed.

Additional fixes:
APAR (WorkItem URL) Description Steps to apply
Rational Jazz Foundation

Use TLS instead of SSL by default.

  1. Stop the Apache Tomcat server.
  2. Back up the JAZZ_HOME/tomcat/conf/server.xml file to server.xml.bak.
  3. Extract the file to a temporary directory.
  4. Copy the server.xml file to the JAZZ_HOME/tomcat/conf directory.
  5. If you made any custom configuration changes to your server (such as changing port numbers), manually copy them from server.xml.bak to the new server.xml file.
  6. If you are using Windows:
    1. Back up the JAZZ_HOME/server/server.startup.bat file to server.startup.bat.bak.
    2. Copy the server.startup.bat file to the JAZZ_HOME/server/ directory.
    3. If you made any customizations to the server startup file, manually copy them from server.startup.bat.bak to server.startup.bat
  7. If you are using Linux:
    1. Back up the JAZZ_HOME/server/server.startup file to server.startup.bak.
    2. Copy the server.startup file to the JAZZ_HOME/server/ directory.
    3. If you made any customizations to the server startup file, manually copy them from server.startup.bak to server.startup
  8. Start the server
WebSphere Application Server

Fix defect in redirect web page.

WAR files changed in iFix006 and must be re-deployed. Follow the instructions for the web server you use (WAS or Tomcat).

NOTE: If the context root used by the any application is not the default, it will be necessary to rename the war file (and adjust some of the directory paths referenced below) based on the context root currently in use.

For example:

  • if your current context root for Requirements Management is 'rdm', you must rename the rm.war file to rdm.war
  • if your current context root for Quality Management is 'jazz', you must rename the qm.war file to qm.war
  • if your current context root for Change and Configuration Management is 'jazz', you must rename the ccm.war file to jazz.war

In summary, the name of the war file needs to be the same as the respective context root in use

NOTE: For users of the RDNG browser add-on, the rm.war file must be properly matched with the browser plugin files.

This only applies during installation of the plugin, so for those users that have already installed the plugin, no action is required.

For any new installations of the browser plugin, the customer should contact IBM Support and request a refresh of the browser add-on files along with the properly paired version of the rm.war file that includes this fix.

  1. 1. Backup these files:
    1. JAZZ_HOME/server/webapps/jts.war
    2. JAZZ_HOME/server/webapps/ccm.war
    3. JAZZ_HOME/server/webapps/qm.war
    4. JAZZ_HOME/server/webapps/rm.war
    5. JAZZ_HOME/server/webapps/admin.war
  2. Copy the jts.war file somewhere either on your local machine or on the CLM server (you may copy to the JAZZ_HOME/server/webapps directory)
  3. In the WAS Admin Console, stop the jts application: Go to Applications>Application Types>Websphere enterprise applications, select the checkbox next to jts_war and click on Stop.
  4. Update the jts_war file: Select the checkbox next to jts_war and click on Update.
  5. Select "Replace the entire application", then browse to the new jts.war file from step 2 and click on Next. Browse locally if the file was saved on the local machine in step 1, or do a remote browse if the file was saved on a different machine. Follow the Fast Path installation, and accept all of the defaults.
  6. Save the configuration changes when prompted after the update completes.
  7. Start the jts application: select the checkbox next to jts_war and click on Start.
  8. Repeat 2-7 with all other WAR files that you need to upgrade.
  1. 1. Backup these files:
    1. JAZZ_HOME/server/tomcat/webapps/jts.war
    2. JAZZ_HOME/server/tomcat/webapps/ccm.war
    3. JAZZ_HOME/server/tomcat/webapps/qm.war
    4. JAZZ_HOME/server/tomcat/webapps/rm.war
    5. JAZZ_HOME/server/tomcat/webapps/admin.war
  2. Copy the war files to the JAZZ_HOME/server/tomcat/webapps directory.
  3. Stop the Tomcat server.
  4. Delete the JAZZ_HOME/server/tomcat/webapps/jts directory
  5. Delete the JAZZ_HOME/server/tomcat/webapps/ccm directory
  6. Delete the JAZZ_HOME/server/tomcat/webapps/qm directory
  7. Delete the JAZZ_HOME/server/tomcat/webapps/rm directory
  8. Delete the JAZZ_HOME/server/tomcat/webapps/admin directory
  9. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/jts directory
  10. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/ccm directory
  11. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/qm directory
  12. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/rm directory
  13. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/admin directory

Known Side Effects

The following defects were not resolved in this interim fix:

Review the 4.0.7 Release Notes page on for links to queries that list known problems and workaround articles for this release.

Open defects

Review the following list of open APARs for Rational Quality Manager on the IBM Support Portal.

Review technote 1461170: Open APARs for Rational products available on the Web for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.

Change History

What's new

No new features or functions in this iFix.

Review the 4.0.7 New and Noteworthy page on for a description of the new features included in this release.

[{"DNLabel":"RQM 4.0.7_iFix006","DNDate":"17 Apr 2015","DNLang":"English","DNSize":"223620000","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"","DNURL_FTP":" ","DDURL":null}]

Technical Support

Tab navigation

IBM Rational Software Support Communities

  • Visit the IBM Support Portal to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.

  • Visit developerWorks to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community.

  • Visit the Jazz Community if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track development progress.

Helpful Hints For Obtaining Technical Assistance:

Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:

  • What software versions were you running when the problem occurred?
  • Do you have logs, traces, or messages that are related to the problem?
  • Can you reproduce the problem? If so, what steps do you take to reproduce it?
  • Is there a workaround for the problem? If so, be prepared to describe the workaround.

If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support.

Follow IBM Rational Client Support on Twitter | Facebook | YouTube | devWorks Blog

[{"Product":{"code":"SSUVV6","label":"IBM Engineering Test Management"},"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.0.7","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Product Synonym

Rational Quality Manager

Problems (APARS) fixed

Document Information

Modified date:
20 July 2018