Note: The following changes are related to installation and upgrade procedures. Other changes and fixes are not included.
| Description | |
|---|---|
| All applications |
Monitor application performance and usage To help monitor the overall health of a production system, application metrics are now available in the form of MBeans. These MBeans can be integrated into most enterprise-monitoring tools and can help analyze trends and report on operational data. To publish the MBeans, you must enable them from the Advanced Property section of the application administration page. For details about MBeans, see the Jazz.net Deployment wiki: https://jazz.net/library/article/88924. |
|
Monitor resource-intensive scenarios A Resource-intensive scenarios page lists server operations that can use a large number of system resources, which can degrade server performance and negatively affect the user experience. For details, see Resource-intensive scenarios. |
|
|
Starting in 6.0.3, all applications require Java 7.1 Starting in 6.0.3, the CLM and IoT CE applications are built with and must run with Java 7.1:
|
|
| Change and Configuration Management |
Set up a clustered environment You can set up a clustered environment to host a Jazz Team Server and multiple Change and Configuration Management (CCM) nodes. For details, see Change and Configuration Management clustered environment. |
| DB2 |
Recommended transaction log settings New recommended transaction log settings for Lifecycle Query Engine and Data Warehouse DB2 databases are documented in Setting up a DB2 database. |
| Design Management |
WAR file to deploy the product documentation has changed Starting in version 6.0.4, if you use WebSphere Application Server, the WAR file that you deploy to enable the Design Management documentation and context-sensitive help has changed from rdmhelp.war to clmhelp.war. For details about deploying WAR files, see Deploying applications for the Rational solution for Collaborative Lifecycle Management on WebSphere Application Server. |
| Jazz Team Server |
Compact the index files When you create, delete, or update resources, the index files are updated. New artifacts can increase the size of the index. To keep the index size optimal, you can create a task to compact the index and configure the frequency of the task. For details, see Compacting index files. |
| Lifecycle Query Engine |
Generate a mappings.txt file before a server rename operation Before you unregister the Lifecycle Query Engine and Link Index Provider applications for a server rename operation, ensure that you generate a mappings.txt file and modify it so that the Lifecycle Query Engine entry corresponds to the new server. For information about generating and preparing mapping files, see Preparing the mapping file. |
| WebSphere Application Server |
Restrict cookies to HTTPS sessions You can set a "Restrict cookies to HTTPS sessions" option to ensure that the session cookies include a secure field. Enabling this feature restricts the exchange of cookies to HTTPS sessions. For details, see Setting up WebSphere Application Server. |
| WebSphere Liberty |
TLS 1.2 for NIST SP 800-131 support The Configuring WebSphere Liberty to support TLS 1.2 for NIST SP 800-131 topic was updated in this release to correct existing errors and to add a step about restarting the servers. |
| Description | |
|---|---|
| All applications |
Starting in 6.0.3, all applications require Java 7.1 Starting in 6.0.3, the CLM and IoT CE applications are built with and must run with Java 7.1:
|
| Data Collection Component |
Trend metrics are no longer collected by user Starting in version 6.0.4, Data Collection Component no longer collects trend metrics by users (owners or creators). This change was necessary to avoid metric data growth, which degrades performance over time. You can disable the new behavior by following the steps in the readme file, which is located at <server_installation_directory>/server/conf/dcc/mapping/legacy. |
| Design Management |
Before an upgrade, repair multiple versions of the same artifact marked as current in a configuration If you enabled the configuration management capabilities in Design Management 6.0.2 or earlier, if multiple users updated an artifact in a configuration at the same time, inconsistent versions of the artifact might be displayed in the configuration. This problem occurs because multiple versions of the artifact are internally marked as the current version. This issue no longer occurs in version 6.0.3 and later, but might be present in those versions if you upgraded to them from an earlier release. You can fix this issue before the upgrade by running the -repairMultipleVersionsMarkedAsCurrent repository tools command. For details, see the Interactive Upgrade Guide. |
| Rational DOORS Next Generation |
Before an upgrade, repair multiple versions of the same artifact marked as current in the configuration before the upgrade If you enabled the configuration management capabilities in Rational DOORS Next Generation 6.0.2 or earlier, if multiple users updated an artifact in a configuration at the same time, inconsistent versions of the artifact might be displayed in the configuration. This problem occurs because multiple versions of the artifact are internally marked as the current version. This issue no longer occurs in version 6.0.3 and later, but might be present in those versions if you upgraded to them from an earlier release. You can fix this issue before the upgrade by running the -repairMultipleVersionsMarkedAsCurrent repository tools command. For details, see the Interactive Upgrade Guide. |
|
Change the level of migration verification After an upgrade, a migration verification occurs for Rational DOORS Next Generation that generates a report in the server directory. By default, this report contains 10% (value of 1) of the migration verification. You can create an environment variable and set the verification to the level that you want. A value of 0 does not validate anything and no report is generated. A value of 10 produces a report with all data validation. For details, see the Interactive Upgrade Guide. |
|
|
Oracle performance issues To avoid performance issues on Requirements Management servers, ensure that Oracle Bug ID13077335.8 is applied and enabled on the Oracle system that hosts the Rational DOORS Next Generation application. For details, see the Oracle documentation and Performance issues and CRRRW7556E after upgrading repository. |
|
|
Track the progress of project migration A new log file named rm_addTablesProgress.log is generated when you upgrade the Requirements Management server to a new version. This log file tracks the progress of project migration and displays the number of formal reviews, URIs, review baselines, module baselines, and project baselines grouped by project. |
|
|
Windows server dependency for file previews The Requirements Management application must have a Windows package installed on the server to display file previews correctly. If you receive this message, you must obtain the following redistributable package for Visual Studio from the Microsoft website and install it on your Windows server: CRSSS0980W A preview of the file is not available because of a server-side configuration issue. If you are upgrading from CLM version 6.0.2 or earlier: Visual C++ Redistributable Packages for Visual Studio 2005 If you are upgrading from CLM version 6.0.3 or later: Visual C++ Redistributable Packages for Visual Studio 2013 |
|
| Reporting |
Lifecycle Query Engine users must reindex data sources If you use Lifecycle Query Engine for reporting, you must reindex your application data sources after you upgrade to version 6.0.4. If you are upgrading from 6.0.1 or earlier versions to 6.0.4, you must reindex the following application data sources after the upgrade:
|
| 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 2017 | Contact | Privacy Policy | Terms of Use