Note: The following changes are related to installation and upgrade procedures. Other changes and fixes are not included.
| Description | |
|---|---|
| All servers |
Configure TLS Extended Master Secret (EMS) for WebSphere Application Server and WebSphere Liberty to avoid performance issues A new Java security requirement for TLS Extended Master Secret (EMS) might cause performance issues. Java EMS support requires a full handshake in every SSL/TLS connection between the application server and the proxy server. At this time, not all proxy or HTTP servers support EMS. If you enable EMS on servers that don't support it, Collaborative Lifecycle Management (CLM) applications on WebSphere Application Server or WebSphere Liberty might experience performance problems. For more information about which environments are affected by this problem and how to diagnose and resolve it, see Configuring TLS Extended Master Secret for WebSphere Application Server and WebSphere Liberty on the Deployment wiki. |
| Databases |
Repository tools command to verify database integrity You can use the repotools -verify command to verify your database as part of a weekly or monthly maintenance schedule, or before upgrades or other major deployment activities. This command enables the logical verification of objects, in addition to mid-level concepts, such as context checking. For details, see Repotools Verify command - Additional information on the Deployment wiki. |
| Distributed environments |
Start Jazz Team Server before other applications for build engines to start correctly After an upgrade or a server restart in a distributed environment, ensure that you start Jazz Team Server before any other applications. If you start the Change and Configuration Management (CCM) application before Jazz Team Server, the CCM build engines will not start. |
| Global Configuration Management |
New capabilities in version 6.0.6 In the Global Configuration Management application, you can now detect deep component skew in composite contributions from Rational Team Concert or Rhapsody Model Manager. You can also install multiple Global Configuration Management instances to support external global contributions. Both of these new capabilities require the installation of IBM IoT MessageSight as an MQTT broker. For details, see the Interactive Installation Guide. |
| Java runtime |
Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported on the Windows platform Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. For details, see Work Item 455371 and Work Item 452307. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime. |
| Jazz Authorization Server |
Basic authentication is not supported Jazz Authentication Server is not supported for use with basic authentication. |
|
Clusters are now supported You can set up a cluster of Jazz Authorization Servers to reduce server downtime. Jazz Authorization Server is bundled with the Apache Derby database, but a cluster requires an enterprise database such as Db2, Oracle, or SQL Server. For details, see Setting up a cluster of Jazz Authorization Servers on the Deployment wiki. |
|
|
Setup instructions are now in the Interactive Installation Guide You can now use the Interactive Installation Guide to set up Jazz Authorization Server. |
|
| Rational DOORS Next Generation |
New repository tools command to fix incorrect unreferenced versions You can run the repairUnreferencedVersions command to fix the versions that are marked as unreferenced in local versioning. For details, see Repository tools command to repair incorrect unreferenced versions. |
|
New repository tools command to fix versions with identical timestamps During a baseline lookup, more than one version in a configuration might be found with an identical timestamp. You can run the repairVersionsWithIdenticalTimestamp command in Rational DOORS Next Generation to fix the versions that have identical timestamps for the same concept in the same configuration. For details, see Repository tools command to repair versions with identical timestamps. |
|
| Rational Engineering Lifecycle Manager |
IBM Continuous Engineering Connector for IoT IBM Continuous Engineering Connector for IoT extends your development environment by linking IoT platform artifacts to artifacts, such as requirements, work items, test cases, and model elements, to help you visualize traceability and analyze the impact of changes. For installation details, see the Interactive Installation Guide. |
| Rational Rhapsody Design Manager |
New repository tools command to fix incorrect unreferenced versions You can run the repairUnreferencedVersions command to fix the versions that are marked as unreferenced in local versioning. For details, see Repository tools command to repair incorrect unreferenced versions. |
|
New repository tools command to fix versions with identical timestamps During a baseline lookup, more than one version in a configuration might be found with an identical timestamp. You can run the repairVersionsWithIdenticalTimestamp command in Rational Rhapsody Design Manager to fix the versions that have identical timestamps for the same concept in the same configuration. For details, see Repository tools command to repair versions with identical timestamps. |
|
| Rational Team Concert |
Windows 10 is supported for the Shell Client and the Client for Microsoft Visual Studio IDE In addition to Windows 7 and Windows 8.1, you can now install the Rational Team Concert Shell Client and the Client for Microsoft Visual Studio IDE on the Windows 10 platform. Note: In the Rational Team Concert preferences, you might also need to enable TLS 1.2. Depending on which Microsoft Windows update is installed, logging in to the Rational Team Concert repository might fail because the connection times out. This issue is caused by a Windows 10 update that requires TLS 1.2. For more information, see the Windows 10 devices can't connect to an 802.1X environment Microsoft support article. To enable TLS 1.2 in Rational Team Concert, see Configuring Rational Team Concert clients and build engines to support TLS 1.2 for NIST SP 800-131. |
| Reporting |
Lifecycle Query Engine application pages might be unresponsive If Lifecycle Query Engine application pages become unresponsive because of memory issues, see this IBM Support technote: Lifecycle Query Engine application pages become unresponsive. |
|
Lifecycle Query Engine requires Java 1.8 In version 6.0.6, Lifecycle Query Engine requires a Java 1.8 runtime and does not work with Java 1.7. |
|
| Security |
Non-administrative users can view setup information Users without administrative privileges have the ability to view setup information by invoking a service, for example, in a web browser. If your setup contains sensitive information or is a security concern for your organization, after you install and set up your applications, enforce authentication for setup information. For details, see Security considerations for the Rational solution for Collaborative Lifecycle Management. |
| Server setup |
Use the command-line for a silent setup in express mode You can use the command line to silently set up a Continuous Engineering (CE) or Collaborative Lifecycle Management (CLM) installation in express mode. For detailed instructions, open the Interactive Installation Guide and, under Select the setup method, select Command-line (silent) setup in express mode. |
| Description | |
|---|---|
| All servers |
Configure TLS Extended Master Secret (EMS) for WebSphere Application Server and WebSphere Liberty to avoid performance issues A new Java security requirement for TLS Extended Master Secret (EMS) might cause performance issues. Java EMS support requires a full handshake in every SSL/TLS connection between the application server and the proxy server. At this time, not all proxy or HTTP servers support EMS. If you enable EMS on servers that don't support it, Collaborative Lifecycle Management (CLM) applications on WebSphere Application Server or WebSphere Liberty might experience performance problems. For more information about which environments are affected by this problem and how to diagnose and resolve it, see Configuring TLS Extended Master Secret for WebSphere Application Server and WebSphere Liberty on the Deployment wiki. |
| Customized scripts |
Apply any custom changes to the new server.startup script file If you previously customized the server.startup script file, such as changing the JVM values, you must manually apply those customized values to the new server.startup file. Do not replace the new file with your old file. |
| Databases |
Repository tools command to verify database integrity You can use the repotools -verify command to verify your database as part of a weekly or monthly maintenance schedule, or before upgrades or other major deployment activities. This command enables the logical verification of objects, in addition to mid-level concepts, such as context checking. For details, see Repotools Verify command - Additional information on the Deployment wiki. |
| Distributed environments |
Start Jazz Team Server before other applications for build engines to start correctly After an upgrade or a server restart in a distributed environment, ensure that you start Jazz Team Server before any other applications. If you start the Change and Configuration Management (CCM) application before Jazz Team Server, the CCM build engines will not start. |
| Java runtime |
Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported on the Windows platform Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. For details, see Work Item 455371 and Work Item 452307. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime. |
| Licensing |
WebSphere users might need to update license files to ensure Java compatibility If you use WebSphere Application Server and you updated your Java version, or you use WebSphere Liberty, the new Java version that is shipped with version 6.0.6 is not compatible and blocks the access to MD5 signed license files. The licenses were updated in the IBM Rational License Key Center to use a newer signature algorithm. To update your current license files, see the Interactive Upgrade Guide. Important: If you are not upgrading all applications to 6.0.6 at the same time, you must apply an interim fix to the applications at earlier versions. The following releases contain the compatible version of Java: • 6.0.5 or later • 6.0.4 interim fix 007 or later • 6.0.3 interim fix 010 or later • 6.0.2 interim fix 015 or later • No version of 5.0.2 contains a compatible Java version. For 5.0.2, complete the steps in the IBM Support flash article. If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues. |
| Rational DOORS Next Generation |
Confirm that the CleanupUnusedIndexesVersionsTask task is enabled In version 6.0.6, the indexing task named CleanupUnusedIndexesVersionsTask is enabled by default. However, when you upgrade from an earlier version, this task might be disabled. After the upgrade, log in to the server, go to Application > Advanced Properties, and ensure that the CleanupUnusedIndexesVersionsTask task is enabled. For details, see the Interactive Upgrade Guide. |
| Rational Rhapsody Design Manager |
Confirm that the CleanupUnusedIndexesVersionsTask task is enabled In version 6.0.6, the indexing task named CleanupUnusedIndexesVersionsTask is enabled by default. However, when you upgrade from an earlier version, this task might be disabled. After the upgrade, log in to the server, go to Application > Advanced Properties, and ensure that the CleanupUnusedIndexesVersionsTask is enabled. For details, see the Interactive Upgrade Guide. |
| Reporting |
Clear the browser cache after upgrading Report Builder After you upgrade Report Builder to version 6.0.6, clear the browser cache, including the cookies, to ensure that dashboard widgets are displayed correctly. |
|
Lifecycle Query Engine application pages might be unresponsive If Lifecycle Query Engine application pages become unresponsive because of memory issues, see this IBM Support technote: Lifecycle Query Engine application pages become unresponsive. |
|
|
Lifecycle Query Engine data sources might need to be reindexed After you upgrade to version 6.0.6, you might have to reindex the Lifecycle Query Engine data sources depending on which application and version you upgrade from. Rational DOORS Next Generation
For details, see the Interactive Upgrade Guide. |
|
|
Lifecycle Query Engine requires Java 1.8 In version 6.0.6, Lifecycle Query Engine requires a Java 1.8 runtime and does not work with Java 1.7. |
|
|
Reporting applications must be the same version as Jazz Team Server In a distributed environment, the reporting applications, such as Jazz Reporting Service, Report Builder, and Lifecycle Query Engine, must be upgraded to the same version as Jazz Team Server. |
|
| WebSphere Liberty |
Upgrading WebSphere Liberty Profile The WebSphere Liberty Profile that you download with the Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) solutions is tested to ensure that it works with the supported products and applications. However, in some cases, you might want to upgrade the WebSphere Liberty Profile that is installed on your system. For details, see Upgrading a WebSphere Liberty Profile on the Deployment wiki. |
| Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here. |
© Copyright IBM Corporation 2018 | Contact | Privacy Policy | Terms of Use