IBM Support

Rational DOORS Next Generation Interim Fix 11 for 5.0.2

Download


Abstract

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

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

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.


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:

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.

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.

Problems Solved

Defects resolved in this iFix.

This server patch contains fixes for the following defects:

APAR (WorkItem URL) Description
Rational 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.

PI40747

[Backport 5.0.2] DCC open file descriptor Leaks behavior.

PI40912

[Backport 5.0.2] DCC: ODS Collector jobs are in waiting state forever if there was a temporary DB connection problem.

PI42419

[Backport 5.0.2] CQPAR00140514: DCC Quality Management job failing.

PI43701

[Backport 5.0.2] CQPAR00143712: DCC handling of Oracle BINARY_DOUBE is wrong.

PI45649

[Backport 5.0.2] DCC Web UI corrupts the delta time when web browser language is e.g., french.

PI46442

[Backport 5.0.2] [363201] DCC should log SQLException when failing to prepare statement.

PI52655

[Backport 5.0.2] 375622: CQPAR00163680: Delete Fact Table Data DCC job took long time but could not finish.

PI48537

[Backport 5.0.2] 360532: Ghost links appearing in traceability report.

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.

PI38981

[Backport 5.0.2] Project List Excludes Project Areas that do not have team areas.

PI41444

[Backport 5.0.2] Metamodel initialization should happen on server startup.

PI44060

[Backport 5.0.2] CQPAR00143896: Statement that checks if connection is valid can cause problems.

PI41440

[Backport 5.0.2] CQPAR00139305: JRS - Set Conditions - No values to select for Filed Against Attribute.

PI41944

[Backport 5.0.2] Version check fails for Oracle 12c data warehouse.

PI28909

[Backport 5.0.2] JRS server rename fails with multiple mapping events or if server is restarted during rename process.

PI44469

[Backport 5.0.2] IE9 Report name, title and visibility all disabled.

PI43835

[Backport 5.0.2] Help > Help contents link in the Report Builder UI should point to the information for the respective version.

PI52228

[Backport 5.0.2] The unparser should handle the INTERSECT clause.

Rational Jazz Foundation
PI43630

Workaround: Action is required for a remote floating license server after an upgrade to version 5.0.2.

PI28526

NPE in ManagedFloatingLicenseClient$LeaseCache.getCheckoutOperations.

PI28909

Backport defect 342550 to 5.0.2 Maintenance Staging to correct the JVM threads names once they are reused from the Thread pool.

PI28909

Adding new roles in Web UI makes it VERY easy to seriously corrupt roles database - Chrome only.

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.

PI29645

Don't cause an SQLException to determine if a MARKER exists (5.0.2iFix007).

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.

PI31126

The iteration type should not be restored if it's not archived.

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

PI36337

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

PI36961

Full Text Search stemming doesn't work correctly in non-English European languages (Backport 345158 to 5.0.2 ).

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

PI37378

VVC cache storage to concept misses causes bad performance.

PI37679

Query Results from performQuery can be unexpectedly cached (Backport 348143 to 502ifix ).

PI37709

Online migration can skip states on subsequent runs.

PI38110

Deleting resource in no-history storage area should not update history index to 502 (Backport 351405 to 502).

PI40009

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

PI40126

TeamAreaRole ETL flips two columns (354920).

PI40589

[RTC 5.0.2] [wi 356278] - ETL should ignore Item not found exceptions.

PI41256

RRC Project Baselines are inaccessible after migration from 4.0.x in a server renamed environment.

PI42477

Text query service doesn't work after server rename.

PI43630

IACS should support Functional outbound to local targets - backport (334135) to 502.

PI47081

Production Data Warehouse shows duplicate work item records [Defect 356581].

PI49462

Timelines widget does not display team area timeline assignments.

PI52893

Login to fronting apps (other than RTC and RQM) is broken.

PI52896

Auth challenge issued by DelegatedAuthHandler not detected by IACS.

PI28909

Backport JFS bulk delete can cause a OOM (371253). to 502.

PI28909

DM needs to be able to change dependencies of immutable configurations managed by VVCConfigurationCacheService [backport to 5.0.2].

PI41335

SimpleDateFormat is not thread safe and cannot be shared among threads (Extracting Work Items via reportable API can return wrong modification dates for history entries).

PI44128

[wi 361771] Ability to filter certain WI types out of DCC ETL.

PI44578

ItemStateQueue must account for differences in collation order of non alphanumeric characters.

PI44578

Online Migration may repeat states if DB collate order is not IDENTITY.

PI48537

[RTC 5.0.2iFix009] WI: 360995: Ghost links appearing in traceability report.

PI49375

(5.0.2) No Secure Token Error for JRS Widgets using Internet Explorer 11.

PI50923

Backport defect 369390 TransactionalStateCache stores stale state data 502 Maintenance.

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.

PI33354

The module artifacts do not expose the correct version label.

PI33913

Alternate Spelling attribute is set to null on OSLC PUT.

PI34242

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

PI35333

Spaces in links are double-encoded when opening from a converted document.

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.

PI38125

ForbiddenException when attempting to view deleted module in a baseline.

PI38167

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

PI38269

Text imported from ReqPro baseline loses formatting.

PI38396

Update ReqPro migration to behave the same as the UI when requirement has no title.

PI38550

Audit History displays incomplete information when changelogs contain an unresolvable user URL.

PI38594

Project Templates cannot be displayed in project creation wizard if any template returns an error response.

PI38722

Review report results show not started when votes were completed.

PI38795

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

PI38912

No compact rendering after drag and drop of an artifact from the Links section in to the editor.

PI39749

Data in the data warehouse should be updated after server rename.

PI39859

Unable to pause/continue review when review contains a deleted artifact.

PI39940

Amount of data to pre-load in a module should be configureable.

PI40016

Baselines display the current revision of Folder data, throws error when Folder has been deleted.

PI40191

Suspicion Profile Administration page does not show list of projects if the server's Region and Language Format is set to Japanese.

PI40915

Error CRRRW7342E when saving an attribute value, using a role with permissions that allows modifying the attribute for a specific artifact type.

PI41205

Module view wrong in create link to rows in module menu.

PI41213

Copying artifact "changes" artifact name.

PI41228

Printing a module with a Visio artifact does not include the Vision artifact in the generated 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.

PI42162

IE: TypeError occurs when browsing baselines.

PI42647

Not showing suspect flag for changes made in QM and CCM in not opted-in mode.

PI42675,PI26758

DNG doesn't show system messages in banner.

PI47776

Artifacts not loading in module when opened in new tab/window.

PI49265

Remove embedded artifact from embedded resource toolbar does not dirty editor.

PI49593, PI41218

Module & project baselines are not immutable.

PI49616

Assignment of roles in team area does not allow users to do allowed actions in module context.

PI49619

Add lifecycle link to more than 1 artifact from inside a module is not possible.

PI50421

Copy and paste of a section from a module results in incorrect requirement order.

PI40115

Attempting to save business process diagram results in "Saving...." that never completes.

PI41498

WellKnownTypeUrisCache fails with bad typesystem.

PI41556

NPE and potential memory leak when TRS member cannot be retrieved from OSLC services.

PI42352

Embedded images are not displayed properly in modules after server rename.

PI42771

RRC Report fails for an artifact that contains a text link to an image artifact stored in the RM server.

PI43990

Suspicion Profile Administration page does not show list of projects if Registered Application name for RM does not contain "rm".

PI44829

Importing "requirements from within a text document" results in missing requirements in simple case.

PI45386

Tables are getting imported with varying number of columns per row & corrupt table errors on some of the resulting XHTML artifacts exported via RRDG (using public schema).

PI45650

Links Explorer shows duplicate data when using Configure Link Display.

PI45869

Double-byte characters in a table do not export properly to CSV.

PI46449

Bad content inserted when pasting a numbered heading/list from MS Word in CKE using Chrome.

PI46541

It's taking a long time to load the project dashboard when go to the dashboard from an open artifact.

PI47026

Columns don't align properly in imported tables when not all rows start at the same position.

PI47305

RM migration fails when Role ID contains unescaped apostrophe.

PI49589, PI45234

After sorting has been changed, artefact type can not be changed any more.

PI50400

DnD on IE11 causes cursor to flicker.

PI50584

Baseline viewer in DNG 5.x does not display folders properly for baselines upgraded from 4.x.

PI51290

Deselect previously selected artifact when you drag artifacts..

PI52669

Query timeout during SuspectLinkIndexService.clearIndexedLinks could result in unbounded growth of RM on-disk indices.

PI52746

StackOverflow when reporting a sketch with duplicate ids through uisketches schema.

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

PI22400

PI28909

Fix defect in redirect web page.

UPDATING APPLICATION WAR FILES

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

Workaround: Action is required for a remote floating license server after an upgrade to version 5.0.2.

After the upgrade of 5.0.2, 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 5.0.2 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.

PI28909

"java.lang.IllegalStateException: zip file closed" error in patch service (Fix for 346222 for 5.0.2 release).

See "UPDATING APPLICATION WAR FILES" section.

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

If you are running Tomcat as a Windows Service, you must change the Java Options being used:

  1. Remove "jazz.connector.sslProtocol" option (eg -Djazz.connector.sslProtocol=TLSv1.2).
  2. Add this line:
    -Djazz.connector.sslEnabledProtocols="TLSv1,TLSv1.1,TLSv1.2"
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
PI36961

Full Text Search stemming doesn't work correctly in non-English European languages (Backport 345158 to 5.0.2 ).

Language specific stemming is not enabled by default. To enable specific language stemming:

  1. Select the Advanced property page of each application (e.g. ccm, qm, jts...).
  2. Change the value of
    com.ibm.team.fulltext.lucene.language.stemmer.enabled
    to
    true
    .
  3. Run
    repotools reindex -rebuildTextIndices
  4. Restart the server.

The setting has three values:

  1. "legacy" (the default) for compatibility with the existing indices. In this case the English stemmer is used for all languages (except for the Asian languages).
  2. "true" which enables a stemmer specific to the language defined by the "Indexing Language" property or by the server locale if the property is not set.
  3. "false" which disables stemming all together

The stemmer uses the default language specified on the server machine.

PI41256

RRC Project Baselines are inaccessible after migration from 4.0.x in a server renamed environment.

NOTE: You only need to do this once per iFix install. If you have done these steps as the result of another fix, you can skip them. Performing the steps multiple times will not cause problems.

  • Go to the <JAZZ_HOME>/server directory.
  • Execute the following command:
    repotools-jts -clean
PI44578

ItemStateQueue must account for differences in collation order of non alphanumeric characters.

NOTE: You only need to do this once per iFix install. If you have done these steps as the result of another fix, you can skip them. Performing the steps multiple times will not cause problems.

  • Go to the <JAZZ_HOME>/server directory.
  • Execute the following commands:
    repotools-jts -clean
    repotools-qm -clean
PI43630

Workaround: Action is required for a remote floating license server after an upgrade to version 5.0.2.

After the upgrade of 5.0.2, 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 5.0.2 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.

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_011","DNDate":"1 Dec 2015","DNLang":"English","DNSize":"306039232","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-ifix011&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;PI52669;PI52746;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

Document Information

Modified date:
20 July 2018

UID

swg24041488