Rational Quality Manager and Rational Test Lab Manager 2.0.1.1 iFix5 - Release Notes

Important: Reporting Documentation updates

Fixed APARs

The 2.0.1.1 iFix5 APARS query shows the APARs fixed in this release.

Defect fixes

The Workitems fixed in 2.0.1.1 iFix5 query shows the defects fixed in this release. iFix5 also includes the fixes made available in the previous iFixes and fix packs.

Migration export performance from 2.0.1.1 ifix5

We recommend using the following options to improve the migration export performance from 2.0.1.1 iFix5.

Reordering of packages - this is enabled by default. It should not affect performance of export, but should improve import performance. A tar exported with packages reordered can be imported into any of the 3.x versions, but only 3.0.1.2 and beyond can take advantage of this reordering.

Filtering of history from Execution - This is not enabled by default. There are 2 flags that you may use to activate filtering:

To set these flags, edit the DEFINE section of the appropriate repotools script. For Windows, this would be the appropriate repotools.bat file. You will need to add the following lines:

For Linux this would be the appropriate repotools.sh file. You will need to add the following lines:

These flags control the export of history for the following artifacts:

With the exportHistoricalArchivedStates=false flag, the historical states for archived instances of these artifacts will not be exported to the tar file. With the flag exportHistoricalStates=false set to false, those same artifact types will have history pruned for archived AND non-archived. The two flags may be used together.

Note: In RQM 2.x, the StepResults are contained in the ExecutionResults. Each time you execute a step, the ExecutionResults are updated (another element in the history) including a copy of all the StepResults. So, if you execute a long script of N steps, you will create N instances of ExecutionResults, and about N*N contained StepResults. So pruning non-archived history may save a lot.

A tar with history filtered can be safely imported into any of the 3.x versions.

Import into 3.0.1.2

The following options can be used to improve the performance of the import into 3.0.1.2.

Take advantage of reordered packages - this is enabled by default. A tar that was exported from 2.0.1.1 ifix5 with the package reordering will have meta data indicating that the packages are reordered and this will trigger the optimizations. This will appear in the repotools_import.log as:

2011-11-16 13:36:54,869 Namespace URI = com.ibm.team.packageReorder, Version = 1

Disable full text indexing during import - this is not enabled by default. By default, the import will reindex the full text indices. Fulltext indexing can be deferred, and then the indexing can be run later, against either a running or stopped server. To defer the indexing, use the following:

-Dcom.ibm.rqm.migration.options.createLuceneIndex=false

Rebuilding Text Indices in 3.0.1.2

As before, there is a repotools command, -rebuildTextIndices, which can be used when the server is not running. This will delete the old indices and rebuild them entirely. So if you disable full text indexing during import, you could run this command immediately afterwards, or you could bring up the repository, and then at a later date, bring down the server and rebuild.

When you start up the 3.0.1.2 server, if the workitemindex directory does not exist or is empty, the server will automatically rebuild the text indices in the background. If you stop the server before the indices rebuilding is completed, and then restart the server, the server will not complete the reindexing. Should it be necessary to stop the server before the reindexing is completed, you may delete the workitemindex directory, thus triggering a complete rebuild when you restart the server. You can see if the reindexing is completed by by looking to see if the StandAloneFulltextIndexingTask asynchronous task is running - if it is still running, the indexing is still in progress..


Release note items from the previous iFixes

Upgrading data collection jobs (ETLs) for iFix4

These upgrades include performance improvements for running data collection jobs and is required for this iFix.

These upgrades replace the existing data movement task 'RQMAll' with a new data movement task of the same name which performs delta updates by default. An additional data movement task 'RQMAll_FullLoad' is added which can be used in the event a full load of the data warehouse is required.  The package to import is 'rqm-etl'. For additional information about deploying updated data collection jobs, see Importing the Rational Quality Manager packages.

Updating Report templates

There are two versions of the report templates, and you must choose the version appropriate for the reporting software you have installed.

The updated report templates then need to be deployed using Importing the Rational Quality Manager packages as a reference.

Note: If you are using Insight 1.0.1, substitute the appropriate path and rqm-reports-insight_1.0.1.zip when following the installation directions.

Upgrading the XDC files

If you did not upgrade your XDC files in iFix02 or iFix03, then you must perform these steps for iFix04. If you already performed these steps in a previous iFix, you can skip this step.

IMPORTANT: Do not overwrite old XDC with new XDC. Update must be performed with the XDC tool.

  1. Back up the XDC files that are included with Rational Common Reporting located in directory ([Rational_Common_Reporting_installation_directory]\dataconfig\configs )
  2. Open the XML Data Configuration tool, and then open the data warehouse XDC file at the following path: [Rational_Common_Reporting_installation_directory]\dataconfig\configs\Configurations\rqm.xdc
  3. Import the new data warehouse rqm.xdc file located at the following path: [Rational_Quality_Manager_installation_directory]\server\cognos\deployment\xdc\Configurations\rqm.xdc by clicking File > Import, browsing to the file, and selecting Merge attributes of elements with matching identifiers.
  4. Click OK. You might get warnings during the import process, as many of the elements in the source file already exist in the file that is being imported.
  5. Change the URL Type for each Resource Group to "Data service".
    1. Expand XML Data Configuration/Resources/RationalQualityManager/ResourceGroupName. The default resource group name is RQM. If you have multiple projects, find one resource group for each project.
    2. Double-click each resource group to open its editor.
    3. Set the value for the "URL type" drop down box to "Data service" for each resource group and save each editor.
  6. Modify the configurations for each resource 'Relative path' as indicated below.
    1. Expand XML Data Configuration > Resources > RationalQualityManager > Resource Group Name. The default resource group name is RQM.
    2. Double-click each resource to open its general information. Set the value of the 'Relative path' as indicated below for each resource.


      3. Resource name Relative path
      ExecutionResult /executionresult?metadata=UUID&abbreviate=false&calmlinks=true&richtext=false&nosteps=true
      TestCase /testcase?metadata=UUID&abbreviate=false&calmlinks=true&aliases=true&richtext=false
      TestPlan /testplan?metadata=UUID&abbreviate=false&calmlinks=true&aliases=true&richtext=false&includeTestPlanPhases=true
      TestScript /testscript?metadata=UUID&abbreviate=false&nosteps=true
      TestSuite /testsuite?metadata=UUID&abbreviate=false&richtext=false

  7. Save the updated XDC file.
  8. Next, update the live XDC file.
  9. Using the XML Data Configuration tool, open the data warehouse XDC file at the following path: [Rational_Common_Reporting_installation_directory]\dataconfig\configs\live data config\rqm.xdc
  10. Expand XML Data Configuration > Resources > Resource Group Name. The default resource group name is RQM.
  11. Expand the resource 'TestScript'. Right click on 'TestScriptStepLookup' and select delete. This step is required to prevent a conflict when performing the import which follows.
  12. Import the new data warehouse rqm.xdc file located at the following path: [Rational_Quality_Manager_installation_directory]\server\cognos\deployment\xdc\live data config\rqm.xdc by clicking File > Import, browsing to the file, and selecting Merge attributes of elements with matching identifiers.
  13. Click OK. You might get warnings during the import process, as many of the elements in the source file already exist in the file that is being imported.
  14. Modify the configurations for each resource 'Relative path' as indicated below.
    1. Expand XML Data Configuration > Resources > Resource Group Name. The default resource group name is RQM.
    2. Double-click each resource to open its general information. Set the value of the 'Relative path' as indicated below for each resource.

      Resource name Relative path
      ExecutionResult /executionresult?metadata=UUID&abbreviate=false&richtext=false&nosteps=true
      TestCase /testcase?metadata=UUID&abbreviate=false&richtext=false
      TestPlan /testplan?metadata=UUID&abbreviate=false&richtext=false
      TestScript /testscript?metadata=UUID&abbreviate=false&nosteps=true
      TestSuite /testsuite?metadata=UUID&abbreviate=false&richtext=false

  15. Save the updated XDC file.

Additional Documentation issues

Links to information center topics in the context-sensitive help fail

Currently, if you click a link to the information center in a context-sensitive help topic, the link will fail. The work around is to right-click the link and select Open in new window. See work item 36264 - The links in the help window of test case don't work.

Note that this issue has been resolved in Rational Quality Manager version 3.0.1.