Jazz Foundation 7.0

For customized upgrade instructions for your environment, use the Interactive Upgrade Guide:

• If you are upgrading from version 6.0 or later, see Upgrading to version 7.0.
• Upgrading from a version 5 release to a version 7 release is a two-step process. First, you must upgrade your server to the latest fix pack of the version 6 release, start the server, and ensure that the upgrade is successful. Then, you can upgrade to the version 7 release. For details, see Upgrading from version 5 to the current version.
• Before you upgrade to version 7.0, review your data sources and make sure no skipped resources are present. To manage your data sources and identify if you have skipped resources and fix them, see Managing data sources for Lifecycle Query Engine and Validating TRS feeds for more information.

For a complete list of changes to the installation and upgrade process, see the ELM 7.0 Installation and Upgrade Notes.

If you upgrade to this release, be aware of the following items:

For Configuration Management enabled project areas, install ELM 7.0 iFix001 before upgrading to the next version.
If you enable Configuration Management in a project area and run the upgrade script, the upgrade process might leave some data in an incorrect state leading to unexpected changes in the requirements. Install ELM 7.0 iFix001 on version 7.0 before running the rm_upgrade script . See Work Item 130288 for more information.

Important points to note when you upgrade Requirements Management

• To ensure your Requirements Management application upgrade and indexing during product runtime completes faster, it is recommended to apply ELM 7.0 iFix001. Make sure you update the teamserver.properties file for RM by adding com.ibm.team.jfs.reindex.all.by.storageArea=true.
  See Work Item 499982 for more information.


• When you upgrade the Requirements Management application on IBM i operating system, additional considerations are required. In the section titled Run the upgrade script on IBM i in the Interactive Upgrade guide, instead of the step Enter this command to upgrade the Requirements Management application, perform the steps provided in the Deployment wiki in section titled Migrating the link validity data in a single-server topology using upgrade script with interaction, whether your server has link validity data or not. This section provides steps to upgrade a server with Requirements Management and Jazz Team Server installed on the same application server. You can use the same procedure for a distributed server as well. After you complete the steps in the wiki, resume with the remaining steps in the Interactive Upgrade Guide.


• When you upgrade Requirements Management application and select the Upgrade script as the upgrade method, after the configuration files are merged, an editor opens where you can check the Requirements Management teamserver.properties file. Note that first the Jazz Team Server teamserver.properties file opens, then the application teamserver.properties opens for review. If the com.ibm.team.repository.minimumClientCompatibilityVersion property exists in the teamserver.properties file, review if the value is a supported version. If it is not a supported version, update the value or delete the entire property.



• If you used the Configuration Management feature of the Requirements Management application prior to version 7.0, there might be more than one version of an artifact in a configuration with the same timestamp. This could lead to ambiguity when determining the correct version of an artifact in a baseline. Before you upgrade to version 7.0, run the repotools -repairVersionsWithIdenticalTimestamp command in the IBM Engineering Requirements Management - DOORS Next application. For more details, see Repository tools command to repair versions with identical timestamps for details.




Important points to note when you upgrade IBM Engineering Systems Design Rhapsody - Model Manager

• IBM Engineering Systems Design Rhapsody - Model Manager (RMM) version 6.x did not contribute to LQE and LDX. However; during the upgrade, RMM is converted to Change and Configuration Management with AM Extension for Change and Configuration Management application which supports Tracked Resource Set (TRS) specification. Therefore, you must register the corresponding TRS feeds as data sources in both LQE and LDX applications. If LQE/LDX are installed on a separate JTS from the CCM application, then perform the steps described in Connecting Lifecycle Query Engine to applications that use a different Jazz Team Server article, else perform the steps described in Connecting Lifecycle Query Engine to applications that use the same Jazz Team Server article.

If you do not register the corresponding TRS feeds, you will not be able to fetch details of OSLC links established between EWM artifacts owned by the upgraded server and artifacts owned by other EWM or ETM applications. Details of such OSLC links are fetched from LQE when generating JRS reports, where LDX is used to display data in Web Clients.



• IBM Engineering Systems Design Rhapsody - Model Manager (RMM) application V6.x is a standalone application that uses "/am" context root by default. In version 7.0, RMM is removed from the solution as a standalone application and is replaced by an extension to the Change and Configuration Management (CCM) application. The upgrade of RMM application V6.x to CCM application 7.x with extension must be treated in the same way as the upgrade of CCM application V6.x to CCM V7.x with the custom context root "/am". When you perform this migration using the Interactive Upgrade Guide, make sure you select Yes for Did you use a custom context root in your previous deployment? option. In the Enter the context root you used for your application section, specify the context root used by RMM 6.x ("am" or the other root if it is not equal to the default one).



General recommendations when you upgrade to 7.0

• If the ELM applications to upgrade are co-located in the same WebSphere Application Server profile or WebSphere Liberty, you must upgrade all the applications at the same time.


• The required runtime environment and preferred server versions for the ELM applications are as follows:
  
  
  • Java 8 with WebSphere Liberty 19
  • Java 8 with WebSphere Application Server 9
  
  Note: Do not use Oracle JDBC driver 12.1.0.2.0 because this version of the driver contains a defect. For details, see repotools -createTables command fails with ORA-01000 on Oracle 12 on the IBM Support Community page.


• You must obtain new licenses for version 7 applications if you are upgrading from any version 6 release. Version 7 applications do not work with version 6.x licenses. However, version 6.x applications work with version 7 licenses.


• If you use the Lifecycle Query Engine for reporting on Engineering Requirements Management DOORS Next, you might have to reindex the data sources after the upgrade. For details, see the Interactive Upgrade Guide.


• If you upgrade to version 7.0 from a version 6.0.2 or later release of Engineering Requirements Management DOORS Next, the Interactive Upgrade Guide instructs you to query for whether artifacts have more than one current version, and, if so, to run the -repairMultipleVersionsMarkedAsCurrent repository tools command before the upgrade. This command addresses a known issue where concurrent changes to an artifact can cause version issues in configurations. The -repairMultipleVersionsMarkedAsCurrent repository tools command is available in 6.0.5 and in interim fixes of the earlier version 6 releases. For versions 6.0.2 through 6.0.4, you must apply the interim fix that contains the command before you can run it:
  
  
  • 6.0.2 interim fix 013 or later
  • 6.0.3 interim fix 008a or later
  • 6.0.4 interim fix 003 or later
  
  If you run the query and it detects more than one current version of an artifact, but the -repairMultipleVersionsMarkedAsCurrent repository tools command is not available, do not upgrade to version 7.0.
  
  
• If you upgrade to 7.0, you must rebuild the full-text search indexes because the Apache Lucene full-text search engine was upgraded to a more recent version. For details, see Work Item 467854.