When the first installation was performed on Windows Server 2008 R2, the Configuration Wizard could not be loaded.
The following installation is performed on Windows Server 2008 SP2 and 64-bit systems. The installation process is smooth.
- First Install SQL Server 2008 web with SP1. First install. NET Framework and the new version of Windows Installer (Microsoft. NET Framework 3.5 (SP1) is required)
- Before installation, set the locale of the system to Chinese. Set the time zone to Chinese.
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
The SA password is aa000000.
Capture Time of on-screen editing :,
Capture Time of on-screen editing :,
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Then you need to install SQL Server 2008 SP1
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Next, install ALM 11.0. The previous steps are the same as those of the first attempt.
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Click here to create a new schema. The schema name is the default, and the password is also the default tdtdtd.
Capture Time of on-screen editing:
Here, set the account password of site admin to siteadmin, aa000000
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Capture Time of on-screen editing:
Click Finish to installProgramJBoss is started, which occupies a large amount of system resources. If the system resources are insufficient, the JBoss may fail to be started.
Capture Time of on-screen editing:
After the startup is successful, the system will
Capture Time of on-screen editing:
Capture Time of on-screen editing:
I have not restarted. Then there is tragedy.
After I installed ALM directly, I directly installed the ALM explorer, and the following tragedy appeared. It never works.
Therefore, restart the instance after installation.
Http: // localhost: 8080/qcbin/
Http: // localhost: 8080/qcbin/addins.html
Http: // localhost: 8080/qcbin/start_a.jsp this is the front-end login page
Http: // localhost: 8080/qcbin/siteadmin. jsp this is the site administration page
Next, you need to install the ALM explorer. Click add-ins page on the above page, click More hp alm add-ins on the open page, find the ALM explorer on the page, download and install it.
Capture Time of on-screen editing:
Access http: // localhost: 8080/qcbin/using ALM Explorer will show the following pop-up box:
Capture Time of on-screen editing:
After entering the pop-up boxes, the following error occurs:
Capture Time of on-screen editing:
After Microsoft Visual C ++ 2005 Service Pack 1 redistributable package ATL Security Update is installed, it is still unavailable.
Later, I saw
I uninstalled the installed ALM explorer and accessed it using a browser.
In QC 10.0, there is an add-in called HP Quality Center client side setup add-in, after the plug-in is installed, you do not need to download the files required by the client every time you connect to the QC server.
Capture Time of on-screen editing:
The add-ins page of alm11.0 cannot be found.
However, after careful searches, I can find this file in the installed directory file: C: \ Program Files \ HP Application lifecycle management platform \ Application \ 20qcbin. war \ plugins \ clientsideinstallation qcclient under this directory. MSI file.
However, it seems useless after the installation. Each time I access QC, I load it again.
Then I saw an add-in named msigenerator. After the plug-in is installed, an MSI installer for deploying the client file can be generated. However, after the MSI is installed, the client files will be loaded each time you enter QC. This issue is to be studied.