Rational DOORS Next Generation Interim Fix 9 for 4.0.7

Download

Abstract

IBM Rational DOORS Next Generation 4.0.7_iFix009 has been made generally available and contains fixes to version 4.0.7 including all predecessor fixes.

Download Description

*Table of Contents*
Sections	Description
What's new	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.
Impact assessment	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.
Prerequisites	The Prerequisites section provides important information to review prior to the installation of this interim fix.
Download package	The Download package section provides the direct link to obtain the download package for installation in your environment.
Installation instructions	The Installation instructions section provides the installation instructions necessary to apply this interim fix into your environment.
Fix List	Click to review a complete list of the defects (APARs) resolved in this interim fix.
Known problems	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
Detailed System Requirements	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	IBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.
jazz.net product page	The Jazz initiative consists of three elements: Platform, Products and Community. Explore the jazz.net product page.
developerWorks	Find technical developer content and resources.

Prerequisites

**Prerequisites include:**
IBM Rational DOORS Next Generation 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

Click the corresponding tab below to review the installation instructions to apply the iFix on a server or client host:

Tab navigation

Server update- selected tab,
Client update

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:

Stop the CLM server.

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.

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

Clean the application server cache. Follow your application server's documentation on cache cleaning. Use "To clean the application cache in WebSphere" and "To clean the application cache in Tomcat" below as a reference.

Start the CLM server.

Run repotools-<app> -clean for each application that is installed to clear the repotools cache. Note: This will also display the help output. For instance:
- repotools-jts -clean
- repotools-ccm -clean
- repotools-qm -clean
- repotools-rm -clean

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

Procedure to uninstall the server patch:

Stop the CLM server.

Back up and remove the contents of the following directory: <server_installation_directory>/server/patch

Clean the application server cache. Follow your application server's documentation on cache cleaning. Use "To clean the application cache in WebSphere" and "To clean the application cache in Tomcat" below as a reference.

Start the CLM server.

Run repotools-<app> -clean for each application that is installed to clear the repotools cache. Note: This will also display the help output. For instance:
- repotools-jts -clean
- repotools-ccm -clean
- repotools-qm -clean
- repotools-rm -clean

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

To clean the application cache in WebSphere:

Remove contents from these directories under the profile root: temp,tranlog,wstemp,workspace.

For example, "rm -rf <WebSphere_profile_root_directory>/{temp,tranlog,wstemp,workspace}/*" on linux.

To clean the application cache in Tomcat:

Remove contents from these directories under the tomcat root: temp,work.

For example, "rm -rf <server_installation_directory>/server/tomcat/{temp,work}/*" on linux.

Procedure to install the client update site:

Extract the update site file to the computer where the client is installed.

In the Rational Team Concert client, click Help > Install New Software.

In the Install window, click Add.

In the Add Repository window, click Local and navigate to the extracted update site file.
Note: The update site root directory contains a site.xml file.

Select the patches to install.

If you agree to the terms, accept the license agreement and click Install.

After the installation is complete, restart the Rational Team Concert client.

Note: To update the feature patch, you can install the new version directly over the old patch. You do not have to uninstall the old patch.

Procedure to uninstall the client update site:

In the Rational Team Concert client, click Help > About Rational Team Concert > Installation Details.

Select the patches to uninstall and click Uninstall.

After the uninstall process is complete, restart the Rational Team Concert client.

WARNING:

If you run the uninstall process on a Rational Team Concert client that was installed by using a .zip file, the feature patch will be removed along with the original feature. Removing the patch will break the functionality of the affected feature.

For a client that was installed by using a .zip file, reinstall the features by downloading the Rational Team Concert p2 repository from Jazz.net, and use the same installation steps with the following exception:

For step 4, click Archive and select the p2 repository .zip file and install the Rational Team Concert feature. This step will remove the patched plug-ins and replace the missing features with the original versions of the feature from the p2 repository.

If you run the uninstall process on a Rational Team Concert client that was installed by using the p2 repository, to remove the patch, you must uninstall the entire Rational Team Concert p2 feature and then reinstall the entire Rational Team Concert feature through the p2 repository.

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
Corrective	This is a maintenance interim fix. It contains fixes for client-reported and internally found defects.
Test Results Close [x] 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.
PSIRT Blog	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
PI14143	Parse error when running reports on server in Turkish locale.
PI16116	[Process] Investigate an active migration fix for defect 262994.
PI16349	Bring back the 'Remember my user ID' checkbox in the login widget/dialog.
PI19783	bottleneck in ComponentRegistry.getComponentDescriptorForServiceUri (206501).
PI19421	CLM database migration [DB2 to Oracle] failed due to 'CRJAZ1150E' The repository was not verified.
PI22170	Too much synchronization on ComponentConfigurationRegistry.ensureMapsAreInitialized().
PI22153	Reduce Lock Contention in a mixed client (N-1) environment (Backport 295511 to 407 ).
PI23880	Expand RTC report: error CRJAZ0368I A SQL query..
PI25057	Workaround missing resource content during deletion.
PI26888	Deadlock issue in JNDI due to classloader problem.
PI37388	Incorrect third argument to substr SQL function for server rename.
PI28526	NPE in ManagedFloatingLicenseClient$LeaseCache.getCheckoutOperations.
PI33829	Make Fix lock contention, performance issues, and memory leaks in OAuthServiceProvider (270894) safe for clustering.
PI40009	Lucene crashes because of Mmap issue (Backport to 407).
PI40126	TeamAreaRole ETL flips two columns (354920).
PI22400	Workaround: Action is required for a remote floating license server after an upgrade to version 4.0.7.
PI22400	Backport JFS bulk delete can cause a OOM (371253). to 407.
PI48839	[RTC407][352082]Tolerate attempt to sync userId containing a double quote backport to 407.
Rational DOORS Next Generation
PI10850	Web Client does not provide associated folder when creating new artifact via Artifact Template, causing Team Area association to fail.
PI13270	Background color of Quick Search in IE causes the results to be almost invisible.
PI22400	407 reporting services return incorrect resources for delta loads.
PI22400	Suspicion reindex fails for QM / CCM apps in distributed environment - errors in log.
PI26592	Grid menu does not work for a module in an informal review.
PI20693	Locks which existed before a server rename are unusable after the rename operation.
PI23288	RM Suspicion Indexing taking long time to complete.
PI14737	NPE in ChangeSetReportExtractor.extractAndSetBindingETags on bluestg.
PI18262	Business Priority in Use Case Requirements Template has a null default value.
PI18961	In a server-renamed environment, false locks can appear in modules and lead to duplicated artifacts.
PI21155	Importing a RequisitePro baseline into RRC fails to import document content when the document name contains Russian characters.
PI22400	Don't return a meaningless Exception class name as an error message, if we also have a full Message_ID and message from the server.
PI22500	Users with JazzProjectAdmins role can initiate a RequisitePro project import, but the import fails.
PI22568	Users with a Contributor license cannot export individual artifacts to a CSV file.
PI23011	Query to determine whether resource has OSLC link is poor performing.
PI23188	Unable to import RequisitePro baseline if its size is huge (3Gb).
PI23940	Carriage returns are added in module artifact.
PI24817	Artifact containing table with empty cell not exported to CSV.
PI25130	ReqPro database (non-Word doc based) requirements are imported without CRLF/LF.
PI26055	"Location" does not default to highlighted folder when importing a rich text document.
PI26753	ReqPro Migration does not import documents properly when certain characters are included in the filename.
PI04747	Table in table truncated in export.
PI28365	CSV Export performs very poorly when the exported View definition contains Link terms.
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.
PI32920	View queries involving links require optimization.
PI33913	Alternate Spelling attribute is set to null on OSLC PUT.
PI35333	Spaces in links are double-encoded when opening from a converted document.
PI41789	Merge - User is allowed to remove attribute type in child configuration using merge even when it is still associated with attribute definition _ Firefox 24.2.0 ESR.

Additional fixes:

APAR (WorkItem URL)	Description	Steps to apply
Rational Jazz Foundation
PI22400	Use TLS instead of SSL by default.	Stop the Apache Tomcat server. Back up the <JAZZ_HOME>/tomcat/conf/server.xml file to server.xml.bak. Extract the ServerConfigurationToUseTLS_RJF-I20150211-0806.zip file to a temporary directory. Copy the server.xml file to the <JAZZ_HOME>/tomcat/conf directory. 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. If you are using Windows: Back up the <JAZZ_HOME>/server/server.startup.bat file to server.startup.bat.bak. Copy the server.startup.bat file to the <JAZZ_HOME>/server/ directory. If you made any customizations to the server startup file, manually copy them from server.startup.bat.bak to server.startup.bat If you are using Linux: Back up the <JAZZ_HOME>/server/server.startup file to server.startup.bak. Copy the server.startup file to the <JAZZ_HOME>/server/ directory. If you made any customizations to the server startup file, manually copy them from server.startup.bak to server.startup Start the server If you are running Tomcat as a Windows Service, you must change the Java Options being used: Remove "jazz.connector.sslProtocol" option (eg -Djazz.connector.sslProtocol=TLSv1.2 ) Add this line: -Djazz.connector.sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"
PI22400	Workaround: Action is required for a remote floating license server after an upgrade to version 4.0.7.	After the upgrade of 4.0.7, if you use a floating license server that is not on the same sever as the JTS application you will need to apply the steps at https://jazz.net/library/article/1514. The steps for 4.0.7 are the same as the steps for 6.0. You will see an error numbered CRJAZ1507E indicating that there was an error communicating with the floating license server.
PI33829	Make Fix lock contention, performance issues, and memory leaks in OAuthServiceProvider (270894) safe for clustering.	Most customers will not need this change. If you have been advised to enable the change, set this system property to true: com.ibm.team.repository.service.internal.oauth.OAuthServiceProvider.useAccessTokenCache For example, use the vm arg: -Dcom.ibm.team.repository.service.internal.oauth.OAuthServiceProvider.useAccessTokenCache=true The change will have no effect (even when enabled) if the CLM is clustered.
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/.
WebSphere Application Server
PI22400	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 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 Backup these files: <JAZZ_HOME>/server/webapps/jts.war <JAZZ_HOME>/server/webapps/ccm.war <JAZZ_HOME>/server/webapps/qm.war <JAZZ_HOME>/server/webapps/rm.war <JAZZ_HOME>/server/webapps/admin.war 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) 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. Update the jts_war file: Select the checkbox next to jts_war and click on Update. 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. Save the configuration changes when prompted after the update completes. Start the jts application: select the checkbox next to jts_war and click on Start. Repeat 2-7 with all other WAR files that you need to upgrade. DEPLOYING ON TOMCAT Backup these files: <JAZZ_HOME>/server/tomcat/webapps/jts.war <JAZZ_HOME>/server/tomcat/webapps/ccm.war <JAZZ_HOME>/server/tomcat/webapps/qm.war <JAZZ_HOME>/server/tomcat/webapps/rm.war <JAZZ_HOME>/server/tomcat/webapps/admin.war Copy the war files to the <JAZZ_HOME>/server/tomcat/webapps directory. Stop the Tomcat server. Delete the <JAZZ_HOME>/server/tomcat/webapps/jts directory Delete the <JAZZ_HOME>/server/tomcat/webapps/ccm directory Delete the <JAZZ_HOME>/server/tomcat/webapps/qm directory Delete the <JAZZ_HOME>/server/tomcat/webapps/rm directory Delete the <JAZZ_HOME>/server/tomcat/webapps/admin directory Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/jts directory Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/ccm directory Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/qm directory Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/rm directory Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/admin directory

Known Side Effects

**The following defects were not resolved in this interim fix:**
In Rational Requirements Composer, the About This Application dialog box does not indicate that a patch is applied. The patch information is only visible from the rm/rmadmin page.
Review the 4.0.7 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 4.0.7 New and Noteworthy page on jazz.net for a description of the new features included in this release.

          [{"DNLabel":"RDNG 4.0.7_iFix009","DNDate":"22 Dec 2015","DNLang":"English","DNSize":"309805681","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=4.0.7&platform=All&function=fixId&fixids=4.0.7-Rational-DNG-ifix009&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":"4.0.7","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}},{"Product":{"code":"SSWMEQ","label":"Rational Requirements Composer"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Product Synonym

Rational DOORS Next Generation

Problems (APARS) fixed
PI33829;PI16349;PI48839;PI23940;PI35333;PI14143;PI16116;PI19783;PI19421;PI22170;PI22153;PI23880;PI25057;PI26888;PI37388;PI28526;PI40009;PI40126;PI10850;PI13270;PI22400;PI26592;PI20693;PI23288;PI14737;PI18262;PI18961;PI21155;PI22500;PI22568;PI23011;PI23188;PI24817;PI25130;PI26055;PI26753;PI04747;PI28365;PI29880;PI29882;PI32920;PI33913;PI41789

Tips