IBM Support

Rational Team Concert Interim Fix 4 for 5.0.2

Download


Abstract

IBM Rational Team Concert 5.0.2_iFix004 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 Team Concert 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.

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

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

Defects resolved in this iFix.

This server patch contains fixes for the following defects:
APAR (WorkItem URL) Description
Data Collection Component
PI29074

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

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.

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 502] DW data source SQL queries do not handle a schema prefix.

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.

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

PI37117

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

Rational Team Concert
PI22400

repotools -renindex gives an error: SEVERE: Failed to register SecureProtocolSocketFactory.

PI25929

RTC Planned-For drop down shows limited values.

PI27899

Build subset not building all dependent items as expected.

PI28266

Missing color expressions in 5.0.1. and newer (Server).

PI28775

Adding literal to enumeration shows error.

PI28849

Removing the summary from the header section causes formatting problems - Advanced Fix.

PI28849

Removing the summary from the header section causes formatting problems.

PI28909

SetBuildMapComponentUUIDTask - only the first 512 build maps are migrated.

PI28965

Kanban/Taskboard group by owner is slow with many users.

PI29142

Poor plan loading performance when there is a tree display with many layers.

PI29144

Dependency build failed when a stream is locked by a scan that was interrupted.

PI29150

Clicking on "Select More Items" does not open the window "Access Context Selection" in the web client.

PI29386

Long option labels are not shown in QueryableComboView.

PI29812

parent links label when generated from work item template does not reflect latest summary when printed from the WebUI.

PI29832

[5.0.2 iFix 002] Improve user experience when dealing with large (1000+ 2048+) numbers of components.

PI29946

[Oracle] ROWNUM limit is applied before ORDER BY.

PI30420

Records marked as softdeleted in TIMESHEET could be active again - Java ETL.

PI30454

ORA-01795 maximum number of expressions in a list is 1000 during CCM rebuildTextIndices.

PI30729

WebUI - infinite calls to PlanRestService#postGetItems2() when loading a plan that has restricted visibility children.

PI30751

DependencyQueryService should run against the file without dependencies once.

PI30880

custom enum-type attribute is unexpectedly displayed in the history without "Synchronize Attributes" operation.

PI30901

Removed team member is still visible in the Work Breakdown view on WebUI.

PI30946

Dependency build automatically unlock the stream after 10 minutes.

PI31096

Source Code Data scanning service not picking up file name changes.

PI31109

Back-port defect 327641 to 5.0.2 iFix003 - Visual Studio: Cannot resolve a conflict because of this error message "Sync item with id '...' is not a conflict".

PI31196

Unexpected tab "Ups..." after creating new plan.

PI31765

Work items incorrectly linked to build when using subset builds.

PI31814

Clicking "Owned by" header in the plan view sorts the owners based on UUID, not the name.

PI31829

WorkItemPublisher does not check for array size in tagWorkItems().

PI32139

Correct NPE when non-BF engine is defined for a BF definition for 5.0.2.

PI32552

Browser gets locked up in taskboard plan view with many owners.

PI32589

Backport blocking synchronization requests from 3rd party tool with an external system (RTC) to 5.0.2.

PI32910

class ISparqlQueryService failed to load for SystemDefinitionService.

PI32965

Fix defect 342786 for 5.0.2 iFix stream.

PI33410

Back-port defect 343463 to 5.0.2 iFix003 - RTC warehouse job SCM fails due to the error: [SQL0199] Keyword CONTENT not expected.

PI33548

Slow performance accepting change sets on MS SQL Server.

PI33717

Plans with Circular Tracks References do Not Open.

PI34027

Adopt Only enumeration display name or value can be returned by Reportable REST API and not both (344297).

PI34063

Getting errors when executing concurrent builds during accept changes.

PI34210

Work Item Promotion creates a build property that can grow large enough to terminate the BFA process.

PI34450

Backport defect 340225 to 5.0.2 iFix004 - Unable To View .h and .c Files in Web Client.

PI34496

Drag & Drop Edit of "Work Item" Editor Presentation Layout is not working in 5.0.2.

PI34523

Investigate using transactional caches during history for versionable.

PI34523

[Defect 344131] Investigate using transactional caches during history for versionable.

PI35066

Promotion fails when there are more than 41 work-items.

PI35071

buildReport.xml not available in post-build script.

PI35370

Can't query buildPath from build maps anymore.

PI35372

When a gap is detected during promotion preview the error message displays the wrong change set.

PI35420

Cross repository tracks links with Accumulated Time column causes refresh loop and empty summary.

PI37399

Creating a new linked WI in another Project Area is not working anymore. It will always create a new WI in the SAME Project Area/.

This client update site contains fixes for the following defects:

APAR (WorkItem URL) Description
Rational Team Concert Eclipse Client
PI28266

Missing color expressions in 5.0.1. and newer (Eclipse Client).

PI30775

Issue with cross component re-factor (move).

PI31109

Fix for "327641: Cannot resolve a conflict because of this error message Problem running 'resolve conflict': is not in conflict".

PI31251

[RichUI] Item is not located under the correct Folder.

PI33972

Back-port defect 344241 to 5.0.2 iFix003 - scm [not lscm] move path command leads to RuntimeException of the type CLIClientException: Attempted to beginRule: P/* does not match outer scope rule: F/*.

PI34880

Back-port defect 345551 to 5.0.2 iFix004 - NPE from scm show history.

PI34940

Fix for Conflict move needs to include unparented adds or moves (345423).

PI36861

Backport defect 348599 to 5.0.2 iFix004 - Moving an eclipse project in repository causes original project to become unshared, pending changes view still says its loaded.

SE59241

SE59241 Language definitions appear in random order.

Rational Team Concert Visual Studio Client
PI28909

Request for multiple RTC 5.0.2 Backports [defects : 339231, 307440].

PI28909

address issue in item 340443 - 5.0.2 iFix004.

PI29663

Visual Studio: 414 Request-URI Too Long error is thrown when Searching for Change set.

PI30674

Change set search filters - "Created before" and "Created after" should work from beginning of day.

PI30675

Clicking on a link that reports problems with multiple work items in Team Advisor fails.

PI31109

Back-port defect 327641 to 5.0.2 iFix003 - Visual Studio: Cannot resolve a conflict because of this error message "Sync item with id '...' is not a conflict".

PI33273

In intermediate history on a file, disable context menu options in case of Undo state.
Additional fixes:
APAR (WorkItem URL) Description Steps to apply
Rational Jazz Foundation
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
      1. 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
Rational Team Concert
PI22400

repotools -renindex gives an error: SEVERE: Failed to register SecureProtocolSocketFactory.
  1. Go to the JAZZ_HOME/server directory.
  2. Execute the following command: 
    repotools-ccm -clean
  3. Execute the following command: 
    repotools-qm -clean
PI28909

SetBuildMapComponentUUIDTask - only the first 512 build maps are migrated.

This patch must be added to the 5.0.2 installation's patch directory after the 5.0.2 server is installed but BEFORE an attempt is made to migrate the 4.x or 5.0 data to 5.0.2.

Since the fix is in the migration code itself, the issue can not be resolved if the 4.x or 5.0 has already been migrated to 5.0.2.

In case for the migrated build definitions, customers have to set the property for each build definition in Properties tab as the following: 

team.enterprise.build.buildmaps.needMigrateComponent=true

Then apply the fix and restart the 5.0.2 server, the migrated build definitions will be migrated again. Once the migration completed, the property above will be set to false by the migration service.

Back to top

Known Side Effects

The following defects were not resolved in this interim fix:

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 Team Concert 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":"RTC 5.0.2 iFix_004","DNDate":"6 Apr 2015","DNLang":"English","DNSize":"245534556","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ERational&product=ibm%2FRational%2FRational+Team+Concert&release=5.0.2&platform=All&function=fixId&fixids=5.0.2-Rational-RTC-ifix004&includeSupersedes=0&source=fc","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SSUC3U","label":"IBM Engineering Workflow Management"},"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 Team Concert

Problems (APARS) fixed
PI36678;PI36076;PI33321;PI33336;PI31540;PI29074;PI28526;PI28909;PI30407;PI30488;PI31655;PI31729;PI33689;PI34460;PI37117;PI22400;PI25929;PI27899;PI28266;PI28775;PI28849;PI28965;PI29142;PI29144;PI29150;PI29386;PI29812;PI29832;PI29946;PI30420;PI30454;PI30729;PI30751;PI30880;PI30901;PI30946;PI31096;PI31109;PI31196;PI31765;PI31814;PI31829;PI32139;PI32552;PI32589;PI32910;PI32965;PI33410;PI33548;PI33717;PI34027;PI34063;PI34210;PI34450;PI34496;PI34523;PI35066;PI35071;PI35370;PI35372;PI35420;PI37399;PI30775;PI31251;PI33972;PI34880;PI34940;PI36861;SE59241;PI33587

Document Information

Modified date:
20 July 2018

UID

swg24039646

Page Feedback