Upgrade from HP QC 9.2 or QC 10.0 to ALM 11 (QC 11.0)
星期二, 8三月2011 16:17 byokan.cakmak
Hello everybody,
Would you like to upgrade your QC to ALM 11 ? Follow these steps. Ok, upgrading process might be terrible for some cases, but don't lose your hopes. I've already made some upgrades to ALM 11 for my clients.
BTW, don't forget to apply ALM 11 Patch level 1 after upgrade process, that's really important and huge patch, also Level 2 will be publishing soon.
Wish you delightful upgrade process :p
Steps to Upgrade from QC9.2 or QC10 to ALM11:
Pre-requisites:
准备事项
1. Check the following page for system requirements of ALM 11:http://www.hp.com/go/TDQC_SysReq
1、了解ALM11的安装要求
2. Move the project repository from the Database (DB) to the File System (QC9.2 only)
2、把项目仓库从数据库转移到文件系统。（仅适用QC9.2）
Note: Repository over DB is not supported in ALM11
3. Before migration, deactivate all projects from the Site Administrator
3、移植前，通过site Administrator关闭所有项目。
Migration of QC9.2 or QC 10 to ALM11
从QC9.2/QC10移植到ALM11
1. Backup the projects’ databases/schemas and Site administration database/schema (default name “qcsiteAdmin_db”) from the QC9.x database server
1、从数据库服务器中备份项目的数据库以及Site Site administration database/schema (default name “qcsiteAdmin_db”)
2. Backup the projects’ repositories from the QC 9.x or QC10 server. Each project has the location of the repository at the project properties in the Site Administration web site.
2、从QC9.2/QC10的服务器上备份项目repositories。每个项目都在服务器本地拥有“repository”。
3. Restore the project databases/schemas and the Site administration’s database/schema at the ALM11 database server (if you are using a new database server)
3、如果ALM11使用新的数据库服务器，则把前面两部导出的数据库导入到新的数据库服务器
Note: If upgrading QC, there’s no need to move projects databases/schemas however is important to take backups.
注：如果只是本地升级QC服务器，则无需移动数据库相关信息。不过最好还是做好备份。
4. Install ALM11, if you are using the same application server you must uninstall QC9.2 or QC10
4、安装ALM11，如果在同一台服务器上，则必须先卸载QC9.2/QC10
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.
QC系统拥有2种不同类型的数据库，一个是项目数据库，还有一个是site admin数据库。移植的时候，为了保证users，user configurations，以及site administration parameters的前后一致性，新安装的系统使用的数据库的名称必须和从之前系统移植过来的的数据库名称保持一致。在安装的时候，选择“Upgrade a copy” or “Upgrade the existing schema”
5. Paste/Restore the repositories in the expected repository location in the new installation
5、安装完成后，在新的安装路径下，使用之前保存好的repositories覆盖掉新的repositories。
6. Restore the projects
6、恢复原有的项目
a) Login Site Administrator and create a new empty project.
登录site administrator，创建一个空的项目
b) Go to the new empty project’s folder repository and make a copy of the dbid.xml file.
进入新项目的repositories路径，copy一份dbid.xml文件
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.
移除（Remove）需要移植的项目（理由：它和老的数据库服务器还有连接关系）不要删除（delete）项目，因为这样会同时删除掉数据库服务器中的相关数据。
d) Go to the project’s folder and rename the existing “dbid.xml” file to “dbidold.xml”
进入移植项目文档路径，把“dbid.xml”重命名为“dbidold.xml”
e) Paste a copy of the “dbid.xml” file from the empty new project.
把新建项目的“dbid.xml” copy到该项目路径下
f) Edit the “dbid.xml” to match your project environment description as follow:
编辑“dbid.xml”，使其和项目环境的描述保持一致。
<?xml version="1.0" encoding="UTF-8" ?>
<ProjectDescription>
<PROJECT_NAME>** Put the project name **</PROJECT_NAME>//项目名称
<DB_TYPE>XXXXX</DB_TYPE>//数据库类型
<DESCRIPTION>XXXXX</DESCRIPTION>
<DB_CONNSTR_FORMAT>XXXXX</DB_CONNSTR_FORMAT>
<DB_NATIVE_AUTHENTICATION>XXXXX</DB_NATIVE_AUTHENTICATION>
<DB_NAME>** Put the project schema name **</DB_NAME>
<DBSERVER_NAME>XXXXX</DBSERVER_NAME>
<DB_USER_PASS>XXXXX</DB_USER_PASS>
<PR_HAS_VCSDB>XXXXX</PR_HAS_VCSDB>
<PHYSICAL_DIRECTORY>** Put the correct path of the repository folder of this project**\</PHYSICAL_DIRECTORY>
<USERS_QUOTA>XXXXX</USERS_QUOTA>
<PR_IS_ACTIVE>XXXXX</PR_IS_ACTIVE>
<SAQ_IS_ACTIVE>XXXXX</SAQ_IS_ACTIVE>
<PR_REPOSITORY_IN_DB>XXXXX</PR_REPOSITORY_IN_DB>
<PR_LANGUAGE>XXXXX</PR_LANGUAGE>
<PROJECT_UID>82a311c5-a440-4ecd-97a2-e97331a447XX</PROJECT_UID>
</ProjectDescription>
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: <Drive>:\Program Files\Mercury\Quality Center\repository\qc\<Domain_Name>\<Project_Name_Folder>
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.
8、在site administrator页面，使用编辑过的“dbid.xml”文件恢复项目。
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
9、验证，修复以及更新项目：1）右键选择“Maintain Project”，2）选择Verify Project，3）verify完成后，选择repair peoject，4）repair完成后，选择Upgrade项目。
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.
* Recommendation is to try on a Test server, then production.
