Note: The following changes are related to installation and upgrade procedures. Other changes and fixes are not included.
| Description | |
|---|---|
| Backup and recovery |
New interactive guide for backing up databases, indexes, and configuration files A new interactive guide is available that enables you to generate customized instructions for backing up databases, indexes, and configuration files for the Collaborative Lifecycle Management (CLM) and Continuous Engineering (CE) applications. You can find the guide in IBM Knowledge Center on the landing page for interactive guides, and in the Administering section of the help. |
| Clustering |
Distributed Cache Microservice The Distributed Cache Microservice is a small Java application that provides a centralized management and storage location for distributed data for clustered Collaborative Lifecycle Management (CLM) applications. For details about installing and configuring the microservice, see the Interactive Installation Guide. |
|
Using an LDAP backend with the Distributed Cache Microservice If your CLM environment uses an LDAP user registry, you must configure the User Registry settings in the distributedCache.cfg file for the Distributed Cache Microservice to work. In addition, most user interface resources of the microservice require the user to have a JazzAdmins role. |
|
| Java |
Defect in Oracle JDBC driver 12.1.0.2 Do not use Oracle JDBC driver version 12.1.0.2 because this version of the driver contains a defect. For details, see this IBM Support article: repotools -createTables command fails with ORA-01000 on Oracle 12. |
| Monitoring |
System log feed feature is no longer supported in 6.0.5 Starting in version 6.0.5, the system log feed feature was replaced with MBeans. |
| Rhapsody Model Manager |
New application in version 6.0.5 As part of the IoT Continuous Engineering Solution, IBM Rhapsody Model Manager is an evolution of Rhapsody Design Manager and provides web-based model management and traceability. For a product overview, see IBM Rhapsody Model Manager. For installation details, see the Interactive Installation Guide. |
| Security |
Non-administrative users can see some server configuration parameters In the web client, users who do not have administrative privileges can see some server configuration parameters; however, they cannot modify them. If this situation is a security concern for your organization, you can set the disableEnhancedAdminSecurity parameter to false. For instructions on how to set this parameter on WebSphere Liberty, Apache Tomcat, or WebSphere Application Server, see Security considerations for the Rational solution for Collaborative Lifecycle Management. |
|
Sensitive information in work item links The Summary field for a work item is displayed as a link when work items are shared between private and public project areas. If users in a public project area do not have permissions to the private project area, they cannot access the private work item by clicking the link, but they can see its summary. To avoid sharing sensitive information outside a private project area, do not include sensitive information in a work item summary. |
|
| Servers |
Connecting to the SMTP server Starting in version 6.0.3 of the Rational solution for Collaborative Lifecycle Management (CLM), the Apache Geronimo javax.mail library is used for email settings instead of the Oracle javax.mail library . This change might affect your system if it has a firewall between the SMTP server and Jazz Team Server and a monitoring solution such as MailGaurd that monitors SMTP traffic. For details, see Troubleshooting the SMTP server. |
|
Jazz Authorization Server with SCIM is not compatible with electronic signatures in Rational Team Concert If your Jazz Authorization Server is configured for the System for Cross-domain Identity Management (SCIM), you cannot use the electronic signature features in Rational Team Concert. |
|
|
Server rename operations might hang if applications start at different times To ensure a successful server rename operation, complete these steps to start Jazz Team Server and the other CLM applications after the server rename:
|
|
| UNIX platforms |
Running the repository tools -compacttdb command on UNIX platforms On UNIX platforms such as Linux or AIX, the -compacttdb command must be run with the same user ID that starts the application to ensure that the application can access and change files when needed. |
| Description | |
|---|---|
| Backup and recovery |
New interactive guide for backing up databases, indexes, and configuration files A new interactive guide is available that enables you to generate customized instructions for backing up databases, indexes, and configuration files for the Collaborative Lifecycle Management (CLM) and Continuous Engineering (CE) applications. You can find the guide in IBM Knowledge Center on the landing page for interactive guides, and in the Administering section of the help. |
| Design Management |
Before an upgrade, repair multiple versions of an 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 upgrade 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. |
| Java |
Defect in Oracle JDBC driver 12.1.0.2 Do not use Oracle JDBC driver version 12.1.0.2 because this version of the driver contains a defect. For details, see this IBM Support article: repotools -createTables command fails with ORA-01000 on Oracle 12. |
| Licensing |
Installing trial license keys during an upgrade In most cases, when you install a new version of the product to upgrade from an earlier version, you do not have to install trial licenses because your purchased licenses are included with the previous installation. However, if you use Enterprise Extension builds, when you install a new version of the product to upgrade, you must also install the trial licenses. |
|
Obtain updated licenses after upgrading to version 6.0.5 If you use WebSphere Liberty or a version of Java that was built after April 2017, after you upgrade your server to version 6.0.5 you must obtain updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses. For details, see the upgrade instructions in the Interactive Upgrade Guide or the release notes for your applications. |
|
| Rational DOORS Next Generation |
Before an upgrade, repair multiple versions of an artifact marked as current in a configuration 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 upgrade 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. |
|
|
Run the link direction tools after upgrade, if necessary With the indication of link direction in version 6.0.5, after an upgrade, the direction of custom link types might not be as intended and cross-project or cross-component links might not be stored in the proper project or component. You can correct these issues by using a link swapper tool and a link storage tool. For details, see Rational DOORS Next Generation 6.0.5 Link Tools. |
|
| Rational Quality Manager |
Before an upgrade, repair multiple versions of an artifact marked as current in a configuration If you enabled the configuration management capabilities in Rational Quality Manager 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 upgrade 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. |
| Reporting |
Lifecycle Query Engine users must reindex data sources
|
|
Requirements Management prerequisites for upgrading to Data Collection Component 6.0.5 If you upgrade Data Collection Component to version 6.0.5 but do not upgrade the Requirements Management application to 6.0.5, you must have one of the following Rational DOORS Next Generation versions installed for ETLs to run properly.
|
|
|
Upgrading from a version 4 release with reporting capabilities to 6.0.5 Upgrading from any version 4 release to any version 6 release is a two-step process. You must first upgrade your server to the latest fix pack of version 5, start the server, ensure that the version 5 upgrade was successful, and then upgrade to the version 6 release. Important: If you use the reporting capabilities, after you upgrade to version 5, you must run an ETL job at least once before you upgrade to 6.0.5. Running the ETL job ensures that your reports will be migrated to 6.0.5. Starting in version 6.0, Data Collection Component replaced the Java ETL. Ensure that you install Data Collection Component in your 6.0.5 environment. |
|
| Upgrading |
Interactive Upgrade Guide now includes entries for custom context roots The Interactive Upgrade Guide now includes extra entries where you can add custom context roots, and those entries are used in the guide where appropriate. When you provide this information in the form, your guide is dynamically generated according to your custom context roots. The root affects your unique repository tools (repotools) commands, installation paths, server URLs, and so on. To simplify the upgrade process, you can copy the customized command syntax from the guide and use it at the command prompt. |
|
Migrating custom themes If you are upgrading from any version 5 releases to 6.0.5, and if your version 5 installation contains custom themes, you must manually migrate them after you upgrade your server to 6.0.5. However, if you are upgrading from any releases of version 6 to 6.0.5, the upgrade script automatically completes the migration task. To manually migrate your custom themes, see the Interactive Upgrade Guide. |
|
| 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