Question & Answer
Question
Answer
- For upgrade from earlier versions of ERM DOORS (version 9.1,9.2, and so on) to a new version of ERM DOORS, read this documentation.
- For upgrades from a version that is older than ERM DOORS 9.0 (such as 8.3 and 8.2), read this documentation.
Note
If you have multiple DOORS instances on the same DOORS server system, upgrading the DOORS software upgrades all the DOORS instances that share DOORS installation. For example, if you have two DOORS 9.6 instances (DOORS DB Server 9.6 00001 and DOORS DB Server 9.6 00002) and you upgrade from 9.6 to 9.7, both 9.6 instances are upgraded to 9.7 when the 9.6 software is replaced with the 9.7 software.
However, if you also have DOORS instances for a different major version, for example version 8.3, these instances are not affected by the DOORS 9.x upgrade.
Before you upgrade
Refer the installation and upgrade instructions, as well as the release notes (also known as readme files), for all the components you plan to upgrade before you begin the upgrade process.
Upgrade recommendations
Here are some general DOORS upgrade recommendations that complement the instructions in the documentation.
IMPORTANT
Make sure you can successfully log in to your IBM ERM DOORS database as an Administrator before you start.
Here are some general DOORS upgrade recommendations that complement the instructions in the documentation:
- If needed, upgrade the license server (and licenses) first. Verify that the license server is configured correctly and successfully serving licenses. The license server is compatible with an earlier version, so you can use a newer license server with an older IBM ERM DOORS version.
- Prior starting the upgrade, stop IBM ERM DOORS and back up your data.
- When you install the new server, point to the location where your current database is located.
When you start the new client for the first time, you need to log in as Administrator (by using the same Administrator password that was valid before the upgrade) to migrate the database to the new version.
- After the upgrade is complete, test any customizations as needed.
Note
Data migration is only needed during major version upgrades, for example from 8.3 to 9.7; it is not required for a minor version upgrade such as from 9.6 to 9.7.
Testing your upgrade
Do a dry run of the upgrade, migration on a test system first. The test system needs to be set up similar to the system you are upgrading, and contain all your customizations and enough data from your production system that you can do a thorough test after the upgrade.
More reasons to do a dry run of the upgrade, migration on a test system first:
- You get to become familiar with the upgrade and data migration process in a safe environment.
- You can test your DXL customizations in advance, and address any upgrade-related issues before the production system is affected.
- You can determine whether any data-specific upgrade issues are impacting your environment in advance. If any are found, you are able to choose and test work-arounds before productivity is impacted.
- You can see how long it takes to upgrade the test system and use that to schedule adequate downtime for the production system upgrade.
- Upgrade-related problems can be addressed in a safe environment before the production system is brought down.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2023
UID
swg21420785