Download Release

IBM Rational Team Concert

Task tracking Source control Agile planning

Rational Team Concert 4.0.7

Product Release / Trial | July 11, 2014
This is not the most recent version. We recommend Rational Team Concert . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Upgrading to Rational Team Concert 4.0.7

Before you upgrade to this version, review the following information. For advanced information about upgrading, see the Deployment wiki.

Rational Reporting for Development Intelligence

If you use the optional program Rational® Reporting for Development Intelligence to customize reports, upgrade the Rational solution for CLM applications before you upgrade to the corresponding Rational Reporting for Development Intelligence release. For more information about Rational Reporting for Development Intelligence, see the related section in Reporting and the upgrade process.

Rational Insight

The Rational Insight fix pack is compatible with the 4.0.3 through 4.0.7 releases. If you want to use 4.0.7 and have not upgraded to Insight, you must first upgrade Jazz Team Server to version 4.0.7. The CLM applications can stay at earlier versions, but you must configure the "new with" data manager ETLs from Jazz Team Server 4.0.7. For more information about Rational Insight, see the related section in Reporting and the upgrade process and Upgrading to Rational Insight

Change and Configuration Management, Quality Management, and Requirements Management.

If you are upgrading any of the Change and Configuration Management (CCM), Quality Management (QM), and Requirements Management (RM) applications from version 3.0.1.x, or version 4.0 and later, see Upgrading to version 4.0.7. If you are upgrading from a version 2 release, you must first upgrade to a version 3 release, preferably the latest 3.0.1.x release. For more information, see Upgrading from version 2 to the current version.

If you are upgrading from a release that is earlier than 4.0.1 in a distributed environment (CLM applications are on separate servers) and you will not upgrade all CLM applications to 4.0.7, a mandatory workaround provides the appropriate base licenses that are required for the upgrade. See Work item 251460: Incorrect documentation for upgrading JTS and apps in a staged fashion when going from pre-4.0.1 to post 4.0.1 CLM release.

  1. Install the new Jazz Team Server.
  2. Install any missing licenses from the 4.0 functional client access licenses (CALs) .zip file by using the Admin licensing page in the web client. Use the file, which is available to download from this page.
  3. If you are upgrading the CCM application, first go to the Admin licensing page in the web client and delete the following CALs:
    • CCM Data Collector
    • Build System
    • ClearCase Synchronizer
    • ClearQuest Synchronizer
    Then, proceed with the upgrade of the CCM application.
  4. If you are upgrading the QM application, go to the Admin licensing page in the web client and delete the following CALs:
    • QM Data Collector
    • RQM Connector
    Then, proceed with the upgrade of the QM application.
  5. Restart Jazz Team Server.

Migrate self-signed certificates on Apache Tomcat installations

If you use Apache Tomcat, you can import self-signed certificates when you upgrade. In the Jazz_Installation_Directory/server/tomcat/conf/server.xml file, Apache Tomcat is configured to read the server certificate from the Jazz_Installation_Directory/server/tomcat/ibm-team-ssl.keystore file. Typically, the default certificate is transferred during an upgrade. However, if you had a self-signed certificate from a Certificate Authority (CA) in your previous Tomcat installation, you can import and use it with your new server by completing the following steps:

  1. Copy the certificate file from the old installation to the new installation directory.
  2. Open the Jazz_Installation_Directory/server/tomcat/conf/server.xml file for editing.
  3. In the keystoreFile section, specify the self-signed certificate to use.
  4. Save and close the server.xml file.
  5. Restart the server.