Upgrade from Quality Center 9.2 or Quality Center 10.00 to A Lifecycle Management 11

Steps to Upgrade from QC 9.2 or QC 10.00 to ALM 11:

********Recommendation is to try on a Test server, then production**************

Pre-requisites:

1. Check the following page for system requirements of ALM 11:

http://www.hp.com/go/TDQC_SysReq

3. Move the project repository from the Database (DB) to the File System (QC 9.2 only)

Note: Repository over DB is not supported in ALM11

Workarounds:

1. Document ID KM203670 - How to move a QC project repository from the database to the file system

2. Install the latest QC patch for the QC 9.2 version which includes a tool to download the repository to the file system

4. Before migration, deactivate all projects from the Site Administrator

Migration of QC 9.2 or QC 10.00 to ALM 11

1. Backup the projects’ databases/schemas and Site administration database/schema (default name “qcsiteAdmin_db”) from the QC 9.x database server
   1. For SQL server:

i. Document ID KM169526 - How to backup and restore MS SQL database

ii. Document ID KM186582 - What are the minimum permissions for MS SQL in Quality Center

2. For Oracle Server:

i. Document ID KM205839 - How to export and import an Oracle database to dump files

ii. Document ID KM186580 - What are the minimum permissions for Oracle in Quality Center

2. Backup the projects’ repositories from the QC 9.x or QC10.00 server. Each project has the location of the repository at the project properties in the Site Administration web site.

1. Document ID KM189097 - What needs to be backed up when backing up Quality Center

3. Restore the project databases/schemas and the Site administration’s database/schema at the ALM 11 database server (if you are using a new database server)

Note: If upgrading QC, there’s no need to move projects databases/schemas however is important to take backups.

4. Install ALM11, if you are using the same application server you must uninstall QC 9.2 or QC10.00

QC has 2 different databases, the project databases and the site admin database. When migrating, to keep users, user configurations, and site administration parameters you must install using the same database name that was used to restore the project in your DB server. Select “Upgrade a copy” or “Upgrade the existing schema” option during installation.

5. Paste/Restore the repositories in the expected repository location in the new installation
6. Restore the projects

a) Login Site Administrator and create a new empty project.

b) Go to the new empty project’s folder repository and make a copy of the dbid.xml file.

c) Remove your projects from the Site Administration (Reason: it has connections to the old database server). Do not delete the project because it will remove the project schema from the database server.

d) Go to the project’s folder and rename the existing “dbid.xml” file to “dbidold.xml”

e) Paste a copy of the “dbid.xml” file from the empty new project.

f) Edit the “dbid.xml” to match your project environment description as follow:

** Put the project name **

XXXXX

XXXXX

XXXXX

XXXXX

** Put the project schema name **

XXXXX

XXXXX

XXXXX

** Put the correct path of the repository folder of this project**\

XXXXX

XXXXX

XXXXX

XXXXX

XXXXX

82a311c5-a440-4ecd-97a2-e97331a447XX

PROJECT_NAME: the name of the project, for example: NEW_PROJECT.

DB_NAME: the name shown in the database list, for example: NEW_PROJECT_DB

PHYSICAL_DIRECTORY: by default, this values is: :\Program Files\Mercury\Quality Center\repository\qc\\

PROJECT_UID: Keep the same amount of digits and modify the last two values to get a unique ID

8. From the site administrator restore projects using the “dbid.xml” file edited for all projects.
9. Verify, repair and upgrade projects
   1. Right click on it and select “Maintain Project”
   2. Select Verify Project
   3. After verification finished, select Repair project
   4. After project repair, select Upgrade project

Notes:

• After upgrade the project you can not change its repository folder location, the reason of that is that there is a new feature in ALM that optimizes the project’s repository, there will be a job implementing this after upgrade the project for at least 1 day if the project is small and 5 days if the project is large.

Here is the information from the administrator guide (page 97):

After upgrading a project to ALM 11.00, ALM migrates the project repository directories to a new file structure in the default project repository location. If the migration process fails, you must fix the problems manually in the project repository. You can also configure the speed at which the migration is performed. For more information, see "Repository Migration" from Administrator Guide on page 120.

Documents useful in this process can be downloaded from here :

HP ALM User Guide in PDF

HP ALM Installation Guide in PDF

HP ALM Whats New in PDF

HP ALM Upgrade Best Practice in PDF

HP Administrator Guide in PDF