Question & Answer
Question
How to plan your installation or upgrade to IBM Engineering Lifecycle Management version 7.0.x versus previous versions.
Cause
There are some changes to the system requirements and architectural changes that might pose a challenge in some larger or complex environments. In particular, there is a significant change to the Engineering Requirements Management application that moves the application index from the local application server to the database repository.
Here we detail the resources are available to help plan the upgrade and provide some steps.
Answer
Here is a list of resources to get the process started:
- [IMPORTANT NOTE] While IBM® Engineering Requirements Management DOORS® Next 7.0.x can scale to higher levels of data and concurrent users than 6.0.x, the techniques that improve query performance with Db2® and Oracle® are not sufficient with Microsoft® SQL Server®, and our analysis is ongoing. We recommend that clients who are using IBM® DOORS® Next Generation 6.0.x with Microsoft® SQL Server® do not upgrade to ELM 7.0.x. For more information, see Performance considerations: Microsoft® SQL Server® and IBM® DOORS® Next 7.0.x (Engineering Lifecycle Management)
- [IMPORTANT NOTE] Thresholds for determining whether your DOORS Next instance has exceeded the capacity of Microsoft® SQL Server.
- [IMPORTANT NOTE] IBM recommends upgrading with 7.0.2 SR1 and iFix021 or higher.
- Download the latest interim fixes from
- Stay up to date with IBM support updates with My Notifications
- Updated instructions for Engineering Lifecycle Management Interactive Upgrade Guide when upgrading to 7.0.2 SR1 release
- Interactive upgrade guide
- System Requirements
- Jazz.net Deployment Wiki
- Understanding DOORS Next sizings in ELM 6.x to estimate timings when upgrading to DOORS Next 7.x
- Planning for the upgrade or migration of Rhapsody Model Manager to version 7.0
- ELM 7.0.x Downloads:
Download, review, and complete the "ELM7 Upgrade Run Book" document template to assist with your planning efforts.
ELM7 Upgrade Runbook Template.docx
Once you have a tentative plan for scheduling your upgrade, open a Support Case with the following information:
- What version of ELM you are currently running, including any patches applied?
- What version of ELM you are upgrading to?
- When do you plan on performing the upgrade?
- In QA?
- In Production?
- What database server vendor are you using?
- What version are you currently running?
- How large are your Application databases?
- Which ELM applications are you running?
- Are any of your applications clustered?
- Do you currently have Rhapsody Design Manager installed?
- If so, is it colocated with Engineering Workflow Management or distributed?
- Which Operating Systems are your servers running?
- What version?
- How large are the Application indexes?
- This information can be obtained by calculating the size of the <JAZZ_HOME>/server/config/<app> directory.
- Are Global Configurations enabled?
- Is the Global Configuration Manager deployed?
- Do you have projects that are enabled to use Global Configurations?
- If you are using Engineering Requirements Management, include the output of the following query from your database.
SELECT 'concepts' AS metric, COUNT(DISTINCT CONCEPT) AS value FROM VVCMODEL.VERSION UNION ALL SELECT 'versions' AS metric, COUNT(DISTINCT VERSION) AS value FROM VVCMODEL.VERSION UNION ALL SELECT 'configs' AS metric, COUNT(*) AS value FROM VVCMODEL.CONFIGURATION UNION ALL SELECT 'changesets' AS metric, COUNT(*) AS value FROM VVCMODEL.CHANGE_SET UNION ALL SELECT 'version mappings' AS metric, COUNT(*) AS value FROM VVCMODEL.VERSION UNION ALL SELECT 'resources' AS metric, COUNT(*) AS value FROM RESOURCE.RESOURCE UNION ALL SELECT 'resource revisions' AS metric, COUNT(*) AS value FROM RESOURCE.RESOURCE res INNER JOIN REPOSITORY.ITEM_STATES states ON states.ITEM_UUID = res.ITEM_ID UNION ALL SELECT 'item states' AS metric, COUNT(*) AS value FROM REPOSITORY.ITEM_STATES
SELECT 'concepts' AS metric, COUNT(DISTINCT CONCEPT) AS value FROM VVCMODEL_VERSION UNION ALL SELECT 'versions' AS metric, COUNT(DISTINCT VERSION) AS value FROM VVCMODEL_VERSION UNION ALL SELECT 'configs' AS metric, COUNT(*) AS value FROM VVCMODEL_CONFIGURATION UNION ALL SELECT 'changesets' AS metric, COUNT(*) AS value FROM VVCMODEL_CHANGE_SET UNION ALL SELECT 'version mappings' AS metric, COUNT(*) AS value FROM VVCMODEL_VERSION UNION ALL SELECT 'resources' AS metric, COUNT(*) AS value FROM RESOURCE_RESOURCE UNION ALL SELECT 'resource revisions' AS metric, COUNT(*) AS value FROM RESOURCE_RESOURCE res INNER JOIN REPOSITORY_ITEM_STATES states ON states.ITEM_UUID = res.ITEM_ID UNION ALL SELECT 'item states' AS metric, COUNT(*) AS value FROM REPOSITORY_ITEM_STATES
- Once completed, attach a copy of your ELM7 Upgrade Run Book to the Support Case
Related Information
[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSPRJQ","label":"IBM Engineering Lifecycle Management Base"},"ARM Category":[{"code":"a8m50000000Cj1MAAS","label":"DOORS Next Generation-\u003EUpgrade"},{"code":"a8m0z000000CbM5AAK","label":"Jazz Reporting Service-\u003EUpgrade"},{"code":"a8m0z000000CbPJAA0","label":"Jazz Team Server-\u003EUpgrade"},{"code":"a8m50000000CjL7AAK","label":"Quality Manager-\u003EUpgrade"},{"code":"a8m50000000CjdLAAS","label":"Team Concert-\u003EUpgrade"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.0.0;7.0.1;7.0.2"}]
Was this topic helpful?
Document Information
Modified date:
20 April 2023
UID
ibm16156021