IBM Engineering Lifecycle Management 7.0.3

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

• If you are upgrading from version 6.0.2 or later, see the Interactive Upgrade Guide.
• Upgrading from a version 5.0.x or V6.0.0-V6.0.2 to this 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 this release. For details, see Upgrading from version 5 to the current version.

If you upgrade DOORS Next from V6 to this release, be aware of the following items:

• For a successful upgrade and to reduce temp dbspace consumption, if you are using Oracle, make sure you refer to the Oracle settings in Understanding DOORS Next sizings in ELM 6.x to estimate timings when upgrading to DOORS Next 7.x.
• To understand DOORS Next sizings in ELM 6.x and to estimate timings when upgrading to DOORS Next 7.x, see the Deployment Wiki.
• Before you upgrade the DOORS Next V6 application, make sure you verify the Jena index.
  • Validate the DOORS Next indexes using the repotool_rm verifyJFSIndexes command. See verifyjfsindexes for more details.
  • If the Index verification reports an error, rebuild the Jena indexes using the repotools-rm -reindex all command. See reindex for more details.
• If you upgrade from DOORS Next 6.x to 7.x 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 003a 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.x.

If you upgrade from DOORS Next V7.0.0 to 7.0.3, be aware of the following:

• You must apply the latest available 7.0 iFix before running the repair tool (repairVersionsWithIdenticalTimestamp) command.

For more information, see ELM installation and upgrade notes.

If you are upgrading any DOORS Next release to V7.0.3, be aware of the following:

• If you use the Lifecycle Query Engine for reporting on data from DOORS Next and wish to use either (A) the new log-based TRS service in V7.0.3 (turned off by default except for new deployments); or (B) the new optional Lifecycle Query relational store (LQE rs), you will need to rebase and reindex the data sources after the upgrade. For details, see the Interactive Upgrade Guide.

General recommendations when upgrading from V6 to 7.0.3

If you are upgrading ELM applications from V6 to this release, be aware of the following items:

• If you upgrade from V 6.x to this release, you must rebuild the full-text search indexes because the Apache Lucene full-text search engine was upgraded to a more recent version.
• When you upgrade the Engineering Lifecycle Management applications, make sure you preview your theme and verify that it works. The theme might have to be updated in the new version of ELM.

General recommendations when upgrading to 7.0.3

Consider the following points:

• If the ELM applications to upgrade are co-located in the same application server profile, you must upgrade all the applications at the same time.
• You must obtain new licenses for version 7.0.3 applications in all cases. Licenses for prior releases will not work.
• If you use the Lifecycle Query Engine for reporting and wish to use the new optional Lifecycle Query relational store (LQE rs), you will need to rebase and reindex the data sources after the upgrade. For details, see the Interactive Upgrade Guide.
• If you are upgrading ELM to version 7.0.3 from an earlier release and have associated EWM releases with global configurations, you must import release links into the GCM application as described in Adding release links in global configurations. If you do not perform this step, incoming links from work items might not be displayed correctly in the DOORS Next and Test Management applications after upgrade.
• After you successfully upgrade to 7.0.3, retain the upgrade logs for a year. IBM Support might need these logs if you open a support case.