IBM Support

Rational DOORS Next Generation Interim Fix 5 for 5.0.2

Download


Abstract

IBM Rational DOORS Next Generation 5.0.2_iFix005 has been made generally available and contains fixes to version 5.0.2 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 jazz.net product page.

Find technical developer content and resources.

Prerequisites

Prerequisites include:

IBM Rational DOORS Next Generation 5.0.2 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:

Tab navigation

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.

Procedure to install the Data Collection Component patch:

  1. Stop the DCC server.

  2. Verify whether the following directory exists: server_installation_directory/server/patch.

  3. If the directory exists, back up and remove its contents.

  4. If the directory does not exist, create it.

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

  6. Start the DCC server.

Procedure to uninstall the Data Collection Component patch:

  1. Stop the DCC server.

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

  3. Start the DCC server.

Procedure to install the patch with JRS deployed on Apache Tomcat server:

  1. Stop the JRS Tomcat server

  2. Copy the following file to a backup directory in the event you need to revert the patch:
    • JRS_Install\server\tomcat\webapps\rs.war

  3. Delete the following file:
    • JRS_Install\server\tomcat\webapps\rs.war

  4. Delete the following directories:
    • JRS_Install\server\tomcat\webapps\rs
    • JRS_Install\server\tomcat\work\Catalina\localhost\rs

  5. Place the new rs.war file under JRS_Install\server\tomcat\webapps

  6. Start the server

Procedure to uninstall the patch with JRS deployed on Apache Tomcat server:

  1. Stop the JRS Tomcat server
  2. Restore the original rs.war that was backed up in step 2 of the install instructions to the following directory
    • JRS_Install\server\tomcat\webapps\
  3. Delete the following directories:
    • JRS_Install\server\tomcat\webapps\rs
    • JRS_Install\server\tomcat\work\Catalina\localhost\rs
  4. Start the server

Procedure to install the patch with JRS deployed on WebSphere Application Server:

  1. Unzip the reporting-war zip file somewhere either on your local machine or on the JRS server.

  2. In the WAS Admin Console, stop the JRS application: Go to Applications > Application Types > Websphere enterprise applications, select the checkbox next to rs_war and click on Stop.

  3. Update the rs_war file: Select the checkbox next to rs_war and click on Update.

  4. Select "Replace the entire application", then browse to the new rs.war file from the unzipped directory 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 the JRS server. Follow the Fast Path installation, and accept all of the defaults.

  5. Save the configuration changes when prompted after the update completes.

  6. Start the JRS application: select the checkbox next to rs_war and click on Start.

Procedure to uninstall the patch with JRS deployed on WebSphere Application Server:

  1. Locate the rs.war file in the original JRS installation.

  2. In the WAS Admin Console, stop the JRS application: Go to Applications > Application Types > Websphere enterprise applications, select the checkbox next to rs_war and click on Stop.

  3. Update the rs_war file: Select the checkbox next to rs_war and click on Update.

  4. Select "Replace the entire application", then browse to the rs.war file in the original JRS installation 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 the JRS server. Follow the Fast Path installation, and accept all of the defaults.

  5. Save the configuration changes when prompted after the update completes.

  6. Start the JRS application: select the checkbox next to rs_war and click on Start.

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

Definitions

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


Notes:
  • 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
Data Collection Component
PI28909

[Backport 5.0.2] Dashboard report is showing the last time the Java ETLs were run not when the last DCC ETLs were run.

PI29074

[Backport 5.0.2] CQPAR00108139: Job status shows failure for all resource groups even though only one of them actually failed.

PI30420

[Backport 5.0.2] [DCC] Records marked as softdeleted in TIMESHEET could be active again - DCC.

PI39043

[Backport 5.0.2] DCC - Timesheet ETL issues.

Jazz Reporting Service
PI31540

[Backport 5.0.2] JRS data source issues when using LDAP and custom DW extension names that end with “.‿.

PI33336

[Backport 5.0.2] CQPAR00118878: Custom Enumerations in certain case display as literal ID instead of name.

PI33321

[Backport 5.0.2] CQPAR00118829: JRS Not able to Handle RQM Categories like Attributes.

PI28909

[Backport 5.0.2] Missing custom link types for requirements.

PI36076

[Backport 5.0.2] Issues with RM custom attributes.

PI28909

[Backport 5.0.2] Able to download query spreadsheet non-authenticated/authorized, potential for malicious use and phishing attack.

PI28909

[Backport 5.0.2] JRS using the data warehouse is showing no results in non CM-enabled project traceability reports from requirements.

PI36678

[Backport 5.0.2] DW data source SQL queries do not handle a schema prefix.

PI37951

[Backport 5.0.2] Report Builder lists Soft Deleted project areas when selecting Scope.

PI28909

[Backport 5.0.2] JRS Failing to Input Validate and output encode data, leading to potential XSS (Cross Site Scripting) Vulnerability.

Rational Jazz Foundation
PI28526

NPE in ManagedFloatingLicenseClient$LeaseCache.getCheckoutOperations.

PI28909

Diagnostics Oracle JDBC Driver version check does not accept 12.1.0.2.

PI28909

Error during creation of Life Cycle Project in CLM 5.0.2RC1 with JazzProjectAdmins permission.

PI28909

Investigate implications of two components having the same ID.

PI28909

Issue #1 Maintenance 5.0.2 - PMC 341917.

PI28909

Issue #3 Maintenance 5.0.2 - PMC 341970.

PI30407

RTC ETL's should be able to handle date values where the year is not 4 digits long.

PI30488

DelegatedAuthHandler and LoginPageStatusHandler ignores com.ibm.team.jfs.app.oauth.OAuthHelper.disableSecureCookies property.

PI31655

The LPA templates can not be retrieved after a migration from 5.0.1 (with a server rename) to 5.0.2.

PI31729

5.x Indexer for Excel can run out of memory.

PI33689

All Project Areas are deleted during upgrade to RDNG 5.0.2 if finalizeApplicationMigration is rerun following a failure.

PI34460

Adopt Report caching slow on Oracle (344963).

PI35764

Modify ClientHttpUtil to deal with an unexpected extra redirect when hitting /authenticated/identity (in 5.0.2 iFix).

PI36337

Project Dashboard shows incorrect content after loading a WI or Query Result and then performing a browser refresh in IE.

PI37026

Online Migration can skip states in the event of a retry-able DB exception (fix in 5.0.2).

PI37053

Creating iterations can break if translation is wrong (Fix in 5.0.2).

PI37117

Handle the query cancellation in query iterator and QueryFilter (resource context filter).

PI38110

Deleting resource in no-history storage area should not update history index to 502.

TBD

Online migration can skip states on subsequent runs.

Rational DOORS Next Generation
PI32049

Module Audit History not shown after artifact deleted.

PI04747

Table in table truncated in export.

PI07072

Module report only displays the first paragraph of heading artifacts.

PI19370

Some characters are encoded when using rich hover in graphical artifacts.

PI26591

Expanding a collapsed module row sometimes shows the wrong content.

PI28204

Web client runs query for all artifacts when all filters are cleared, introducing unnecessary load on the server for large projects.

PI28321

Unable to duplicate uploaded artifacts without delete permissions.

PI28365

CSV Export performs very poorly when the exported View definition contains Link terms.

PI28595

RM Widget Catalog does not display properly in FF and Chrome when response content type is text/plain.

PI28689

View queries involving Modified By and Modified On/After/Before terms perform poorly.

PI28909

Collapsing module row sometimes results in an error and incorrect display.

PI28909

Deleting a folder which contains modules with asset folders underneath fails on WAS.

PI28909

DnD and copy/paste from grid to module does not preserve order.

PI28909

Filter by attributes in module does not find any requirements.

PI28909

Image Loading in Modules can push down selected artifact.

PI28909

Recently Viewed widget broken when used in RM dashboard.

PI28909

Validated By (and Affected By) links column is missing for modules in the "Configure page setting".

PI28909

When user clicks on Edit for a module, the Overview section related fields never go into edit mode.

PI28909

rich hover should show entire folder path, not just parent folder.

PI29190

In non-English environments, the compare collections feature does not show changes to artifacts' primary text.

PI29339

View query for artifacts "Locked By" a given user performs poorly.

PI29368

Artifact URLs behave differently from different locations.

PI29683

Copy/paste will result in circular references.

PI29683

Don't process minimized artifacts when opening editor.

PI29803

Extra line inserted before/after embedded artifact when printing using the publish service/text schema.

PI29880

Rich Hover of artifact with 1000s of links returns a 400 (Bad Request) response due to StackOverflow in SPARQL.

PI29882

Links Sidebar in artifact editor only loads a maximum of 1024 links for an artifact.

PI30744

Safari - Enter key jumps to beginning of text.

PI31321

Exporting module views containing approximately 1200 artifacts fails if there is a link column.

PI31789

Optimize generated SPARQL with custom attributes.

PI31820

Modules that were created in 4.x do not print their headings properly in 5.0.2, both in table of contents and text.

PI32084

Module heading text is printed twice when exporting a module.

PI32086

Link selection button disappears when attempting to select it from a column in a module.

PI32714

Adding multiple existing artifacts to a module adds them in reverse order (and fix Shift-select ordering issue with picker).

PI32747

Module display can become invalid on browser.

PI32847

Attribute is locked for editing during artifact creation in a module.

PI32920

View queries involving links require optimization.

PI33016

Cannot remove an artifact created by file upload, from a module, that is used in more than one module.

PI33041

Sensitive boundaries impact drag and drop usability.

PI33354

Artifact version id should be available in RRDG reporting API.

PI33913

Alternate Spelling attribute is set to null on OSLC PUT.

PI34242

Type feed initialization taking too long for large number of projects.

PI36611

DNG handling of image uploads to modules.

PI36708

OSLC PUT stops working.

PI36893

Attempting to link a Module View by Tag from QM Test Plan results in "Forbidden" error - Backport.

PI37333

Tags are way too easy to delete from system and are confusing to remove from artifacts.

PI37733

Baseline is not displaying previously existing embedded artifacts.

PI37741

Only load wellknown type uris when loading webui.

PI37775

The temporary doc reports are not deleted during cleanup.

PI37776

Excessive data caching for reporting causes high load on server, affecting usability.

PI37796

Performance: Doc reports are generating responses with traceability info that gets discarded.

PI38167

Unnecessary assertion for JazzAdmin roles causes misleading PermissionDeniedException for JazzProjectAdmin users.

PI38269

Text imported from ReqPro baseline loses formatting.

PI38795

Error when trying to duplicate artifacts with cross-project links.

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

Fix defect in redirect web page.

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 jazz.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.

DEPLOYING ON WEBSPHERE APPLICATION SERVER

  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
  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.

DEPLOYING ON TOMCAT

  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
  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/work/Catalina/localhost/jts directory.
  9. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/ccm directory.
  10. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/qm directory.
  11. Delete the JAZZ_HOME/server/tomcat/work/Catalina/localhost/rm directory.
PI28909

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 ServerConfigrurationToUseTLSFor407iFix004.zip 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
PI31655

The LPA templates can not be retrieved after a migration from 5.0.1 (with a server rename) to 5.0.2.

  1. Go to the JAZZ_HOME/server directory.
  2. Execute the following command:
    repotools-jts -clean
PI33587

[5.0.2] LocalGroupLDAP doesn't support case insensitive mode (343625).

This change is only relevant if you need to use LocalGroupLDAP in case insensitive mode.

  1. Stop the Apache Tomcat server
  2. Rename JAZZ_HOME/server/tomcat/lib/com.ibm.team.repository.localgroups.realm_1.1.2100.v20140602_2352.jar to JAZZ_HOME/server/tomcat/lib/com.ibm.team.repository.localgroups.realm_1.1.2100.v20140602_2352.jar.orig
  3. Copy the attached plugin com.ibm.team.repository.localgroups.realm_1.1.2100.v20150214_0216.jar into the JAZZ_HOME/server/tomcat/lib
  4. Add the line
    ignorecase="true"
    as below to tomcat/conf/server.xml:
    Resource name="LocalRoleMap" auth="Container"
    			type="com.ibm.team.repository.localgroups.IUserRoleMap"
    			descripion="Role mapping file"
    			factory="com.ibm.team.repository.localgroups.realm.RoleMappingResourceFactory"
    			ignorecase="true"
    			pathname="/opt/jazz/server/mapping.csv" />
    	
  5. Start the Apache Tomcat server
PI33689

All Project Areas are deleted during upgrade to RDNG 5.0.2 if finalizeApplicationMigration is rerun following a failure.

  1. Go to the JAZZ_HOME/server directory.
  2. Execute the following command:
    repotools-jts -clean
Rational DOORS Next Generation
PI04747

Table in table truncated in export.

After you stop the CLM server, delete the contents of the directory:
  • If you use an Apache Tomcat server, the directory is server_installation_directory/server/tomcat/temp/rrc_reports/.
  • If you use WebSphere Application Server, the directory is /tmp/rrc_reports/.

Known Side Effects

The following defects were not resolved in this interim fix:

As a result of RDNG APAR PI28204 (Web client runs query for all artifacts when all filters are cleared, introducing unnecessary load on the server for large projects (92439)), the "Default View" behavior in the Grid View has now changed. Once all filters have been cleared in the Grid, a message will be displayed indicating, "To show artifacts, select a folder or other filter," and no artifacts will be displayed.

This behavioral change required a new message to be displayed when the user hovers over the "eraser" button for the Filter by Folder section. When the browser locale is English, the hover text will display as, "Clear Folder Filters"; however, for all other browser locales, the hover text will continue to display the appropriate translation of the previous string, "Show Artifacts from All Folders", although the action of clicking the button will still be to return no artifacts.

Review the 5.0.2 Release Notes page on jazz.net 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 DOORS Next Generation 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 5.0.2 New and Noteworthy page on jazz.net for a description of the new features included in this release.

Click the link in the Download Options column:

On
[{"DNLabel":"RDNG 5.0.2 iFix_005","DNDate":"1 May 2015","DNLang":"English","DNSize":"269786183","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ERational&product=ibm%2FRational%2FRational+DOORS+Next+Generation&release=5.0.2&platform=All&function=fixId&fixids=5.0.2-Rational-DNG-ifix005&includeSupersedes=0&source=fc","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SSUVLZ","label":"IBM Engineering Requirements Management DOORS Next"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Installation","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"5.0.2","Edition":"","Line of Business":{"code":"LOB02","label":"AI Applications"}}]

Product Synonym

Rational DOORS Next Generation

Problems (APARS) fixed
PI31540;PI33336;PI33321;PI36076;PI36678;PI37951;PI28526;PI28909;PI30420;PI29074;PI39043;PI30407;PI30488;PI31655;PI31729;PI33689;PI34460;PI35764;PI36337;PI37026;PI37053;PI37117;PI38110;PI32049;PI04747;PI07072;PI19370;PI26591;PI28204;PI28321;PI28365;PI28595;PI28689;PI29190;PI29339;PI29368;PI29683;PI29803;PI29880;PI29882;PI30744;PI31321;PI31789;PI31820;PI32084;PI32086;PI32714;PI32747;PI32847;PI32920;PI33016;PI33041;PI33354;PI33913;PI34242;PI36611;PI36708;PI36893;PI37333;PI37733;PI37741;PI37775;PI37776;PI37796;PI38167;PI38269;PI38795;PI22400;PI33587

Document Information

Modified date:
20 July 2018

UID

swg24039882