IBM Support

Rational DOORS Next Generation Interim Fix 14 for 5.0.2

Download


Abstract

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

Back to top

Installation Instructions

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

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.

  5. Run "repotools-<app> -clean" for each application that is installed.

Note: For a distributed CLM deployment, complete the same steps on each server. Also, the "-clean" parameter is the OSGI framework command which runs repotools with the default argument "help". The output is captured in the reptools-<app>_help.log which resides in the <JazzInstallDir>/server/ directory where reptools-<app>.bat resides.

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.

  4. Run "repotools-<app> -clean" for each application that is installed.

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

Procedure to install the client update site:

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

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

  3. In the Install window, click Add.

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

  5. Select the patches to install.

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

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

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

  2. Select the patches to uninstall and click Uninstall.

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

WARNING:

There are two update sites provided as part of the iFix and which one is deployed depends on the installed version of RTC that is currently in use. Refer to the file list above to determine which update site to use. The update site for the 5.0.2 GA full client installation will not work with Eclipse 3.6 based Rational Team Concert client installed using the IBM Installation Manager. Alternatives are to use the Eclipse 3.6 based Rational Team Concert client zip install, or use IBM Installation Manager to install the Eclipse 4.2 based Rational Team Concert client. The iFix008 update site is specifically for those users who have installed the RTC iFix008 client from Install Manager. That update site will not work on the GA clients.

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.

Procedure to install the Visual Studio client update:

  1. Close all the running Visual Studio client(s).

  2. Extract the patch zip file to the computer where the RTC Visual Studio client is installed.

  3. In the IBM Installation Manger, click File > Preferences > Repositories > Add Repository and provide the path to the folder extracted in the second step.

  4. Click Ok to close Preferences window.

  5. Make sure that the check box File > Preferences > Files for Rollback > "Save files for rollback" is checked.

  6. Now click on Update in the Installation Manager.

  7. Select IBM Rational Team Concert Client for Microsoft Visual Studio IDE package group and click Next.

  8. Select the RTC version that needs to be updated and click Next.

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

  10. Select the Visual Studio version(s) and click Next.

  11. Click on Update

  12. Click Finish to complete update.

  13. After the installation is complete, start the Rational Team Concert Visual Studio client.

To update the feature patch, you can install the new version directly over the old patch if the Visual Studio IDE version is 2010 or 2012. You do not have to uninstall the old patch.

Procedure to roll back to the previous client version:

  1. Close all the running Visual Studio client(s).

  2. In the IBM Installation Manager, click Roll Back.

  3. Select the IBM Rational Team Concert Client for Microsoft Visual Studio IDE package group and click Next.

  4. Select the patch to roll back to.

  5. Click on Roll Back.

  6. Click Finish.

WARNING:

The 5.0.2 patch can be installed only on top of 5.0.2 GA release.

To remove a patch, only Roll Back should be used in the Installation Manager.

Uninstalling the patch will completely remove the GA release along with the patch(s) installed on top of it.

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.

Back to top

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.

Back to top

Problems Solved

See Fix list for IBM Rational Collaborative Lifecycle Management.

Back to top

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.

Back to top

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.

Back to top

Click the link in the Download Options column:

On
[{"DNLabel":"RDNG 5.0.2 iFix_014","DNDate":"19 Apr 2016","DNLang":"English","DNSize":"352016111","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-ifix014&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":"LOB59","label":"Sustainability Software"}}]

Product Synonym

Rational DOORS Next Generation

Problems (APARS) fixed
PI28526;PI28909;PI29645;PI30407;PI30488;PI31126;PI31655;PI31729;PI33689;PI34460;PI36337;PI36961;PI37026;PI37053;PI37117;PI37679;PI37709;PI38110;PI40009;PI40126;PI40589;PI41256;PI41335;PI29074;PI44469;PI44128;PI44578;PI37378;PI43630;PI47081;PI48537;PI45649;PI46442;PI49462;PI49375;PI42477;PI52893;PI52896;PI50923;PI52655;PI52228;PI51290;PI54238;PI54573;PI52669;PI44107;PI52746;PI54963;PI49265;PI49593;PI41218;PI49616;PI49619;PI50421;PI42352;PI47305;PI49589;PI45234;PI50400;PI50584;PI40915;PI42675;PI26758;PI47776;PI45650;PI46449;PI46541;PI47026;PI30420;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;PI38125;PI38167;PI38269;PI38396;PI38550;PI38594;PI38722;PI38795;PI38912;PI39749;PI39859;PI39940;PI40016;PI40191;PI41205;PI41213;PI41228;PI41789;PI42647;PI40115;PI41498;PI41556;PI42771;PI43990;PI35764;PI39043;PI40747;PI40912;PI42419;PI43701;PI35333;PI42162;PI44829;PI45386;PI45869;PI51483;PI56301;PI55318;PI37604;PI54878;PI56370;PI56704;PI55602;PI56191;PI52036

Document Information

Modified date:
20 July 2018

UID

swg24042218

Page Feedback