Display ALM tray icon after stopping installation of patch 1 for ALM 12.6

To restore the ALM tray icon:

  1. Cut and paste the conf folder from C:\ProgramData\Micro Focus\ALM to C:\ProgramData\HP\ALM.
  2. Edit <ALM Installation folder>\scripts\RunALMTrayIcon.bat. Modify the following:

    set InstallLocation=<ALM Installation folder>

    set TrayMain=com.hp.alm.platform.trayicon.ALMTrayIconMain

  3. Run the bat file.

Error when resetting a valid ALM Connection URL in PC Servers module of ALM Lab Management project

In the Lab Management project (“LAB_PROJECT” project in “DEFAULT” domain available in http://<server&gt;:<port>/qcbin/start_a.jsp?projectType=LabManagement) of Application Lifecycle Management (ALM), one of the configurations required for allowing integration of Performance Center (PC) server with ALM server is in the ALM Connection button available in the Servers\PC Servers module. In ALM12.0x\PC12.0x, using this button more than once to set a valid and available URL of ALM server will cause a popup error message: “Host is unreachable. Please ensure that host’s name is correct.”

This is a defect in PC12.0x.

If there is a need to reset this ALM Connection settings after having it already changed in the same ALM session, it is recommended to logout and login back from the Lab Management project and then try to reset ALM Connection settings (it is recommended to avoid changing this setting more than once in a single ALM session).

Uninstall process of ALM 11.52 Patch 2 never ends

On some Windows operating systems, uninstall of Application Lifecycle Management (ALM) 11.52 Patch 2 and hotfixes freezes about halfway through. There is no log in the Event Viewer, Application or System logs.
The msiexec process in the Task Manager is still active but CPU usage is zero. Cancelling ALM uninstall process does nothing.

ALM 11.52 can be manually removed from Windows Installer database using “MsiZap” tool. MsiZap.exe is a Microsoft Windows system tool in Windows Software Development Kit (http://msdn.microsoft.com/en-us/library/aa370523.aspx) that can be used to remove ALM11.52 by running the following command in a command prompt window (Start -> Run -> type cmd):

MsiZap.Exe T {3195D561-2F3C-4373-A218-DA9BEB4F439A}

{3195D561-2F3C-4373-A218-DA9BEB4F439A} is the product code for ALM 11.52.

Note: Instruction for ALM 11.52 Patch 3 requires uninstall of previous ALM 11.52 and hotfixes version.

Quality Center Server logs are not created anymore

Quality Center (QC) or Application Lifecycle Management (ALM) server stops writing server logs.

When the QC \ ALM server is installed on a Linux\Solaris operating system and the log files that are currently used by QC \ ALM process for writing are deleted, QC \ ALM server will stop writing new logs until it is restarted.

Restart of the QC / ALM process resolves the situation

Create ALM encrypted password for the dbid.xml file

1. Locate dbid.xml file
For example). C:\ProgramData\HP\ALM\repository\qc\Default\demo\dib.xml
It is need dbid.xml file backup

2 . In Site admin->Site projects tab->domain_name->project_name select “DB user Password” link under Project details tab.
Project is deactivated and you can type the new password
3. Remove the project
4. In Oracle Enterprise Manager edit project_db (project_name) user and type the new password (same as from step 1)
5. Restore and activate the project
The password for qcsiteadmin schema may need to be changed with a new one when using Oracle as a database in Application Lifecycle Management (ALM) 11. This can be achieved by following the next steps.
Note that the new password will be only applied to ALM user password for qcsiteadmin schema (different from project schema) and the projects password will not be affected.

Response

Before proceeding with the following steps and making any changes in site administration, the best would be backing up the DB_USER_PASS value that is located in the qcsiteadmin database/schema DBSERVERS table, or ideally backup the whole siteadmin database(qcsiteadmin_db).

Steps to change the default ALM user password for ALM qcsiteadmin_db:

1. First the “Application Lifecycle Management User password” from Site Administration -> DB Servers Tab should be changed with the new one.
This operation updates the DB_USER_PASS column (new password encryption) in the DBSERVERS table in qcsiteadmin_db (Site Administration database/schema)
2. In Oracle Enterprise Manager edit qcsiteadmin_db user and type the new password (same as one)
3. Go and display the contents of DB_USER_PASS column (new password encryption) in the DBSERVERS table in qcsiteadmin_db (Site Administration database/schema) and copy the encrypted value.
Save it somewhere.
4. On the application Server go to the ALM deployment location. For example it would be:

C:\ProgramData\HP\ALM\jboss\server\default\deploy\20qcbin.war\WEB-INF\

There you will find the siteadmin.xml file preserving information for the created siteadmin schema.
Backup this file just in case.

Update:
<DefaultUserPassword>put_here_encrypted_password</DefaultUserPassword>
with the new (updated) DB_USER_PASS value from the DBSERVERS table

5. Save the changes in the siteadmin.xml file.
6. Go to the following location on your Server:
C:\ProgramData\HP\ALM\conf and edit the “qcConfigFile.properties”

Find the places where the old Encryption of the password is written and change it with the new one. You need to focus over:

DefaultUserPassword=QCC\:PDvevcW2I7swsx85ave5GQ\=\=
7. Restart the HP ALM Service from Services.
8. Try logging to ALM Site Admin page and to any ALM project.
Note that this change does not affect projects’ user password and they will keep the old ones.

Verify if SAP Solution Manager is configured to integrate with HP ALM

If there are indications showing that SAP Solution Manager server is not configured correctly:

-The “Connect to HP QC project” option is missing in the menu of the Project Administration section of SAP Solution manager (SOLAR_PROJECT_ADMIN transaction).

1

-There is no calculated URL address for BPCA_WS_API (related to BPCA integration).

2

The reason is that the SAP Solution Manager server was probably not correctly configured.

To fix this issue, the HP QC Add-on should be installed on the SAP Solution Manager system. This add-on is part of the HP QC Adapter license (in the past this was installed on the GTE server).
The documentation for the HP QC adapter configuration is available in the following SAP guide: https://service.sap.com/~sapidb/011000358700000210952014E.PDF (SAP Solution Manager Adapter for SAP Quality Center by HP.pdf).
The document for the “BPCA integration” (complement to the above configuration to additionally allow BPCA integration) is available in the SAP guide: https://service.sap.com/~sapidb/011000358700000043712014E.PDF (Business Process Change Analyzer How-to Guide.pdf).

Access to the SAP documentation from SAP domain requires an SAP account and it is recommended to consult SAP support for further help with SAP Solution Manager configuration.

Creation of logical ports in SOAMANAGER failed accessing the URL of EI webservices of HP ALM

During the creation of logical ports in SOAMANAGER of SAP Solution Manager, errors can be seen:

– Logical port creation error: “Error in HTTP Framework 404 Connection”

1

– Proxy error after setting proxy settings during creation of logical port: “Error in HTTP Framework 500 Internal Server Error”.

2

3

SAP server (and proxy server) are not able to access the URL of HP Application LifeCycle Management server.

ABAP program – RSHTML01 (run via SE38 transaction in SAP Solution Manager) can be used to check if the URL of HP Application LifeCycle Management server is accessible from the server side of SAP Solution Manager system.