IBM Support

Collaborative Lifecycle Management Interim Fix 9 for 4.0.7

Download


Abstract

IBM Collaborative Lifecycle Management 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

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.

Prerequisites

Prerequisites include:

IBM Collaborative Lifecycle Management 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

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

  5. Start the CLM server.

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

  1. Stop the CLM server.

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

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

  4. Start the CLM server.

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

  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.

Download Package

The following sections provide detailed information related to this interim fix.

Click the FC link below to obtain the interim fix from Fix Central.


How critical is this fix?

Impact Assessment
Impact Description

This is a maintenance interim fix. It contains fixes for client-reported and internally found defects.

Test Results

Definitions

Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:

  • Coding errors that cause a regression
  • Documentation or packaging problems that cause a regression
  • Errors reported in a new function delivered in a MDV that cause a regression

Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:

  • Fixed APARs which did not solve the original problem but did not break anything new
  • APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression


Notes:
  • Regression and incomplete APARs are considered fix-in-error or MDV-in-error
  • Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
  • Issues in major releases due to new functionality do not apply in this definition

There are no known regressions to report.

In addition to the fixes listed in this document, the iFix may also contain fixes for security issues.

For more details, please refer to the IBM Product Security Incident Response (PSIRT) Blog.

Problems Solved

Defects resolved in this iFix.

This server patch contains fixes for the following defects:

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

Rational Quality Manager
PI20380

repository.common.ItemNotFoundException: Querying Lookup table, can not find any records for ManualExecutionScript.

PI22502

Can't select test plan to generate TSER when Running Test suite.

PI23440

Duplicating a Test Cases using the option 'Duplicate with copies' does not duplicate the Requirements Links.

PI36741

Used by scripts list does not reflect changes.

PI19071

Duplicate cases with associated archived scripts to a different project area problem.

PI21934

AQXIN5014E error when generating PDF reports on test artifacts containing external IDs with URL-reserved characters.

PI22501

The Built-in variables of RQM_TESTCASE_RESULT_WEBID and RQM_TESTCASE_RESULT_NAME are not created when running a command-line adapter test.

PI22524

Incorrect use of oslc.select operator causes performance issues with CQ Integration.

PI22759

When updating a custom attribute on a Test Suite Result, while the test for the result is running, the custom attribute value is removed when the test completes(117722).

PI22794

Exception while updating the script (script name); Failed to find delta predecessor.

PI23688

Duplicating a Test Plan which is in Published state throws two types of errors.

PI25723

409 (conflict) error response when updating a test case referencing an archived category using the OSLC QM V2 API.

PI15196

Required Categories are not being validated in the backend.

PI19069

Manual Test Script fields with long strings in Derby cause migration problems.

PI22656

ReqPro - RRC Migration does not validate whether a Collection belongs to the migrating project correctly, leading to HTTP 412 errors.

PI23807

Duplicating a test script that uses a datapool variable that is linked to an archived test script step will fail.

PI24042

QM: Execution Variable created as a step doesn't work properly when copied using the REST API.

PI24229

Bulk update of TCER fails with no permissions on team areas.

PI24658

Unhandled NPE is thrown while retrieving test case with a work item itemReference.

PI24690

RQM outputs TCER 'blocking' status incorrectly.

PI25371

QM Built-in variables are visible in the result data even though the option to "Include built-in Variables" is disabled.

PI25609

Migration to new script type is broken when script history is truncated.

PI25687

Manual Script fails to be exported to PDF when an HTML table tag with no content is included in RTE section.

PI25689

[RIT Integration] A failed icon is shown in the Test Details although the test result's verdict is "passed".

PI25865

Error on execution console when displaying deleted Test Case Result "Item Handle must not be null ".

PI25924

Project feed does not support paging.

PI26043

QM: Back Link Errors when linking RTC Defect and bulk RQM test cases.

PI26068

Unable to see TestScripts in Test case Section from a TestSuite.

PI26255

Duplicating test case with "Duplicate with copies" option creates orphaned keyword copies.

PI22400

QMI tests failing on D1 deployment.

PI22400

RQM Reportable REST API JUnit and OSLC API JUnit failures.

PI28778

QM Japanese character corruption in file name after run offline in RQM.

PI28859

Requirement back link is not deleted when deleting a test case deleted.

PI29010

RQM Test Plans->Requirement Section->Rational RequisitePro tab (no option to sort ascending/descending by any of the columns).

PI29222

HiddenMenusWebUIInitializer loads data for all projects causing performance issues with many PAs.

PI29865

QM: Unexpected behavior when deleting category values.

PI30267

QM : Duplicating Test Scripts across project areas including Keywords.

PI30764

Links new requirement to test case under coverage view,it shows as updated status in the Reconcile Requirement window.

PI33606

Irrelevant TCERs for a TSER.

PI34877

QM: TER creation does not get latest version of test script if the recent change in the test script is a keyword removal.

PI34972

Multiple test script links are referencing to a keyword.

PI38754

updating custom sections via a PUT has no effect.

PI39506

Improve the performance of the QM - DNG Reconcile operation.

PI22400

TestsuitelogJaxbHelperTest:testInvalidXmlCharacters() failed in 502M pipeline.

PI22400

testBulkUpload() failed.

Rational Team Concert
PI12890

Archived users show up on 'Owned By' inline combo search in Web UI.

PI14219

dependency build not building files when a new component is added to the build stream.

PI14497

Normalize and fix duration based attributes behavior in WorkItems and Planning - Server Fix.

PI14552

promotionInfo.xml temp file not unique and can get clobbered.

PI14710

WebUI - work item fails to load after changing Links layout.

PI15109

Copybook in comment gets added to dependency data in some cases.

PI15272

[Server] Promotion does not target the correct PDS in some cases.

PI15686

ccm log filled up with many Premature end of file. exceptions caused by the Packaging Pruner Task.

PI16128

"Time Spent" attribute only shows hour value of "actual spend time" input.

PI17289

[Server] Override credentials not taken into account by work-item promotion.

PI17383

Nothing gets rebuilt on first dependency build.

PI19391

Kanban tasks disappear after changing owner.

PI19549

SCD Scanners convert file contents to String using default system encoding.

PI21194

No files are rebuilt even if it's personal build with no previous successful team build.

PI23698

add pre-build SCM check in Build Forge integration.

PI52565

[RTC 4.0.7 ifix9] Export as CSV downloads as .txt when in compatibility mode.

PI15699

Presence of Eclipse project references in the scratch directory makes scm daemon track more than one sandbox automatically.

PI15910

WebUI - Duplicate attributeDefinition id found in PA source when using "reuse existing attribute".

PI15911

WebUI - The same attribute can be added more than once to a given type.

PI16233

Users get email notification when they create a workitem.

PI16549

Loading a Plan owned by a Team area with more than 2048 members throws error.

PI17199

The due date can't be recognized correctly by DateBulkEditDialog in Eclipse client with Japanese locale.

PI17733

Plan editor shows archived work item categories in Filed Against column.

PI17862

Subset created from a work item with a deleted file causes a NPE.

PI17872

Wrong project area appears when creating a build definition.

PI18050

WebUI - Unable to sort results when querying from Quick Search box.

PI18284

Overlapping timespans are not handled correctly while adding timespans in traditional scheduler.

PI18292

Subset initialized from work-item does not contain the related files.

PI18631

Backport of Build Forge connections should retry on APIAccessDenied exceptions.

PI19121

System z scanner creating bad INCL dependencies for Assembler files.

PI19650

[wi 319401] - Build WorkspaceStatistics is very expensive and should be configurable.

PI20212

Two-way sync export fails to make folders visible if an uncheckout trigger to remove empty branch is configured on the CC VOB.

PI20946

There is an inconsistency of timing to consume RTC Developer Floating license.

PI20967

Work Item query chooser does not load after copying / pasting the WorkItemViewlet statistics viewlet ...

PI21266

Query editor throws TypeError: node is undefined setting condition title of deleted condition.

PI21525

Buildmap Storage Area and JFS Indexes are growing too large.

PI23423

Opening a Cross project plan with gantt chart throws error 'TypeError: transform(...) is undefined'.

PI26677

Allow disabling the Complex Custom Attribute ETL.

PI43764

RTC server migrated from RTC 4.0.3 to RTC 5.0.1 throws ConcurrentCreationException during dependency build.

PI15296

Time Tracking problem after change Time/Date (Brazilian DST) on WebClient.

PI22274

Missing dependency in PLI source file - following statement with no ending ;.

PI23154

Plan load takes a massive amount of time in getWorkItemAttributeValueSets.

PI23456

Classification problems with C source files.

PI23603

Dependency build not finding C dependency files in SCM.

PI24376

COBOL copybook missing dependencies because it is misidentified as PLI by System z scanner.

PI24393

Classification problems with 11 source files.

PI24394

classificationScan - PL/I file classified as language UNKN.

PI24821

Create work items from the template causes validation error due to exceeded size limit.

PI25128

C and PLI source files are being miss-classified.

PI26287

Add a check to prevent concurrent promotions.

PI26802

Dependency Build Query throws a HTTP/1.1 400 Bad Request error.

PI27804

SCD for Cobol source file missing COPY and INCLUDE references backport.

PI37148

Defect with the pre-condition "prevent adding user owned component".

PI38707

Collecting buildable files takes a long time for dependency build after all the files changed.

PI40984

Promoting multiple changes to a file can fail validation.

PI44643

[RTC 4.0.7iFix005] [WI 326811] Error while computing history -> java.lang.IllegalArgumentException: Auditable State Handle array cannot exceed 2048 elements.

SE60268

Backport of Paste text into a string attribute does not enable the save button for 4.0.7.

PI22400

Attempting to run repotools-jazz -rebuildTextIndices results in java.lang.IllegalArgumentException: CRJAZ8081E: Name must not be empty (PRD2).

PI22400

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

PI29144

Dependency build baseline creation should fail the build if the stream resource does not exist.

PI29144

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

PI29832

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

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.

PI30751

DependencyQueryService should run against the file without dependencies once.

PI30946

Dependency build automatically unlock the stream after 10 minutes.

PI31096

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

PI31765

Work items incorrectly linked to build when using subset builds.

PI31829

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

PI32139

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

PI32589

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

PI32908

Excessive value provider exception floods the log.

PI32910

class ISparqlQueryService failed to load for SystemDefinitionService.

PI34210

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

PI38881

Backport fix for collectLogsPerStep to the 4.0.7 stream.

PI40893

Backport of Opening item from Recent Work Items list while a plan is open causes web browser to hang for over a minute for 4.0.7.

PI39163

Backport Service for script based value set provider may be running for long if http connector doesn't return response for 4.0.7.

PI40247

Source code data scanning not handling component replacement correctly.

PI46581

[RTC 4.0.7] [WI 364981] ccm.log is flooded by CRJAZ0368E A database query could not run on the server.

PI49090

EE Garbage collection should delete more BuildBaselines to 407.

PI51888

Backport fix for more than 1000 build definitions with JBE for 4.0.7.

PI22400

correctly handle duplicate buildPath entries for buildmaps to 407.

This client update site contains fixes for the following defects:

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

Assigning Language Definitions through UI is too performance-intensive.

PI13508

System Definition dependency types not resolving correctly when created from Ant export file.

PI14497

Normalize and fix duration based attributes behavior in WorkItems and Planning - Client Fix.

PI15553

[Defect 306852] error Job found still running after platform shutdown.

PI17289

[Client] Override credentials not taken into account by work-item promotion.

PI22510

Both included children and impacted files options are not taken into account in package wizard.

PI21782

"Read-only" text/html presentation is implemented badly in Eclipse client.

PI21848

import/export of system defs. Import does not set output property if a variable is involved in an allocation.

PI22400

Address XML parser security issue in Eclipse client.

PI24316

Strange boolean attribute behaviour when moving a WI.

PI25025

Merge issue - modified lines inserted multiple time by Autoresolve.

PI30873

Backport SVN fix from workitem 323740 in 4.0.x.

PI31251

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

PI38141

Missing files in subset definition when adding files manually.

PI39460

Wrong association to WI after build subset is reset.

SE59241

SE59241 Language definitions appear in random order.

Rational Team Concert Visual Studio Client
PI10581

Non-empty baselines getting hidden, Escalation 296747.

PI14313

Visual Studio: forgets "flow only components..." changes when you have to scroll.

PI14789

Unloaded projects during accept not getting automatically reloaded, Escalation 9688.

PI30421

Visual Studio Client can't display the Check-In History of a Change Set if in this Change Set is an undo.

PI15699

Presence of Eclipse project references in the scratch directory makes scm daemon track more than one sandbox automatically.

PI28909

Add component to stream fails if no permission to change stream name.

PI30422

First right click doesn't work in Pending Changes View in Visual Studio.

PI26179

"Search Change Set" -> "Search by Name" searches in change set comment, ER.

PI22400

address issue in item 340443 - 4.0.7 iFix005.

PI28909

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

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.

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
PI22400

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 ServerConfigurationToUseTLS_RJF-I20150211-0806.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"
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/.
Rational Team Concert
PI22400

Backport defect 336076 into the 4.0.7 maintenance stream.

This fix must also be applied to the Jazz build engine.

In order to apply it take the attached jar file com.ibm.team.build.engine_3.0.801.v20141107_0149.jar and replace the existing jar file com.ibm.team.build.engine_3.0.801.v20140505_2247.jar in the Build Toolkit install directory under /buildsystem/buildengine/eclipse/plugins.

When the new jar is in place start the jbe with -clean once.

The engine is then ready to go with normal parameters.

In addition to that fix, the client-side update site must be installed as well.

To install the update site follow the directions above.

PI22400

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

  • Go to the <JAZZ_HOME>/server directory.
  • Execute the following command:
    repotools-ccm -help -clean
  • Execute the following command:
    repotools-qm -help -clean
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
  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
    5. <JAZZ_HOME>/server/webapps/admin.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
    5. <JAZZ_HOME>/server/tomcat/webapps/admin.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/webapps/admin directory
  9. Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/jts directory
  10. Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/ccm directory
  11. Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/qm directory
  12. Delete the <JAZZ_HOME>/server/tomcat/work/Catalina/localhost/rm directory
  13. 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 will not indicate that a patch is applied. This 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 Collaborative Lifecycle Management 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.

On
[{"DNLabel":"CLM 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+Collaborative+Lifecycle+Management+Solution&release=4.0.7&platform=All&function=fixId&fixids=4.0.7-Rational-CLM-ifix009&includeSupersedes=0&sourc","DNURL_FTP":" ","DDURL":null}]
[{"Product":{"code":"SSPRJQ","label":"IBM Engineering Lifecycle Management Base"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.0.7","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Product Synonym

Rational Collaborative Lifecycle Management Solution

Problems (APARS) fixed
PI33829;PI16349;PI48839;PI23940;PI35333;PI44643;SE60268;PI38881;PI40893;PI39163;PI17872;PI43764;PI40247;PI39460;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;PI20380;PI22502;PI23440;PI36741;PI19071;PI21934;PI22501;PI22524;PI22759;PI22794;PI23688;PI25723;PI15196;PI19069;PI22656;PI23807;PI24042;PI24229;PI24658;PI24690;PI25371;PI25609;PI25687;PI25689;PI25865;PI25924;PI26043;PI26068;PI26255;PI28778;PI28859;PI29010;PI29222;PI29865;PI30267;PI30764;PI33606;PI34877;PI34972;PI38754;PI39506;PI12890;PI14219;PI14497;PI14552;PI14710;PI15109;PI15272;PI15686;PI16128;PI17289;PI17383;PI19391;PI19549;PI21194;PI23698;PI15699;PI15910;PI15911;PI16233;PI16549;PI17199;PI17733;PI17862;PI18050;PI18284;PI18292;PI18631;PI19121;PI19650;PI20212;PI20946;PI20967;PI21266;PI21525;PI23423;PI26677;PI15296;PI22274;PI23154;PI23456;PI23603;PI24376;PI24393;PI24394;PI24821;PI25128;PI26287;PI26802;PI27804;PI37148;PI38707;PI40984;PI29144;PI29832;PI30420;PI30454;PI30751;PI30946;PI31096;PI31765;PI31829;PI32139;PI32589;PI32908;PI32910;PI34210;PI12485;PI13508;PI15553;PI22510;PI21782;PI21848;PI24316;PI25025;PI30873;PI31251;PI38141;SE59241;PI10581;PI14313;PI14789;PI30421;PI28909;PI30422;PI26179;PI29663;PI30674;PI30675;PI33273;PI52565;PI46581;PI49090;PI51888

Document Information

Modified date:
28 April 2021

UID

swg24041595