HP Application Lifecycle Management Readme
Software version: 12.00
Publication date: March 2014
This file provides information about HP Application Lifecycle Management (ALM) 12.00:
For detailed information about ALM, refer to the documentation set. To access the ALM Documentation Library from the main ALM window, choose Help > ALM Help.
Note: Documentation for ALM extensions is available from: https://hpln.hp.com/group/application-lifecycle-management.
Documentation
The first page of this document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals
To retrieve a document, select the:
You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.
What's New
For a list of new features in ALM 12.00, refer to the HP Application Lifecycle Management What's New, available from: http://update.external.hp.com/ALM/WhatsNew_Addins_Movies/index.html?StartTabIndex=0.
Note: HP Performance Center now includes a Community License Bundle. The bundle includes: 1 Controller allowing 1 concurrent run, 1 PC Lifecycle user and 50 virtual users of all protocols other than DCOM/GUI/Templates perpetually. The virtual users do not include support.
Installation Instructions and System Requirements
For installation instructions, refer to HP Application Lifecycle Management Installation and Upgrade Guide and HP ALM Performance Center Installation Guide. The guides are located on the installation DVDs.
This section describes the system configurations required for installing HP Application Lifecycle Management (ALM) on a server machine, and ALM on client machines. This section also includes system requirements for the Performance Center Server and components.
Important: For the most up-to-date system requirements and supported environments information, see
https://hpln.hp.com/page/alm-qc-enterprise-technical-specifications.Note: HP ALM 12.00 has been tested against FDCC regulations.
This section includes:
ALM Server-Side System Requirements
This section includes the server-side system requirements and configurations for installing HP ALM 12.00 on Windows and Linux.
ALM Server-Side Hardware Requirements
The following table includes hardware requirements for installing ALM on a server machine.
Recommended ALM Server-Side Environments
The following table includes recommended configurations for each operating system.
Supported ALM Server-Side Configurations
This section describes the ALM server-side supported configurations. To ensure best performance and quick support resolutions, we recommend using the recommended environments, described in the above section Recommended ALM Server-Side Environments.
ALM Client System Requirements
This section describes the client system requirements for installing ALM on client machines.
Recommended ALM Client Environments
The following section includes recommended configurations for each operating system.
ALM Desktop Client Supported Environments
This section describes the ALM desktop client supported environments.
- Microsoft Windows 7 SP1 32 Bit
- Microsoft Windows 7 SP1 64 Bit
- Microsoft Windows 8 32 Bit (Requires Microsoft Fix 449677. For more details, see http://support.microsoft.com/kb/2870007).
- Microsoft Windows 8 64 Bit (Requires Microsoft Fix 449677. For more details, see http://support.microsoft.com/kb/2870007).
- Microsoft Windows Server 2008 R2 SP1 64 Bit
Note:
- If you are integrating Quality Center with other HP testing tools, you must modify the DCOM permissions on your client machine.
- DCOM is not required for running Functional test sets (server-side execution).
- Functional test sets are available only in ALM Edition.
- HP ALM Client on Windows 64 bit runs in WOW64 mode.
- You can work with the HP ALM desktop client using a remote desktop.
ALM Web Client Supported Environments
This section describes the ALM Web client supported environments.
HP ALM Lab Service for Remote Test Execution System Requirements
This section describes the system requirements for installing HP ALM Lab Service for remote test execution.
ALM Performance Center System Requirements
This section describes the system requirements for installing ALM for Performance Center, and Performance Center components.
Performance Center Server Configurations
This section describes the system requirements for installing a Performance Center Server.
Recommended ALM and Performance Center Configurations
The following table describes the recommended configuration for Performance Center server components. They should be used along with the recommended ALM server configurations above. For more information, see Recommended ALM Server-Side Environments.
Host and Windows Standalone Load Generator Configurations
This section describes the system requirements for installing a Performance Center Host and a standalone Load Generator on Windows.
Linux Standalone Load Generator Configurations
This section describes the supported operating systems and CPU types for installing a standalone Load Generator on Linux systems.
Standalone VuGen and Standalone Analysis Configurations
This section describes the system requirements for installing Standalone VuGen and Standalone Analysis.
MI Listener System Requirements
This following table describes the system requirements for the MI Listener.
Notes and Limitations
ALM Installation
- Trial Version: If you run the HP ALM Server Configuration Wizard more than once in order to renew a 30-day ALM trial version, you violate the evaluation license policy, and are in breach of compliance. You run the risk of being assessed the full license cost.
- License Administration: ALM has been updated to support management of a new license type, Named License. For the ALM 12.00 release, the only edition available with Named Licenses is the ALM Essentials Edition. HP Quality Center Enterprise Edition continues to support concurrent license types, but does not support the Named License type.
- User Account Control: If UAC is enabled during ALM installation, the ALM Configuration Wizard may not launch, and the ALM server may not start automatically.
Workaround: Disable UAC on the ALM machine.- When a project is restored or imported onto a server which has a confidential data passphrase that differs from the one on the server on which the project was originally created, an error occurs. The message, Failed to Get Simple Key Entity, appears when the data encrypted on the database layer is accessed. To avoid this issue, make sure to install the server with the same confidential data passphrase as the original server.
- Windows Systems: The system tray ALM icon is not available on remote desktop sessions.
- Unix Systems: ALM does not calculate free disk space on linked subfolders.
- If a PDF viewer is not installed on the server machine, the Help button in the HP ALM Server Configuration Wizard does not respond.
Workaround: Install Acrobat Adobe or compatible software, and verify that the software is configured to automatically open PDF files. You can also open the HP Application Lifecycle Management Installation and Upgrade Guide directly from: <ALM installation folder>\application\20qcbin.war\Help\doc_library\pdfs\Install.pdf.- When setting the database server configuration options, ALM does not support an empty Site Administration database schema password.
- Microsoft SQL database: When you upgrade the existing Site Administration schema or upgrade a copy of the existing schema on an SQL server with SQL Server Authentication, the td user must exist in the database and be the owner of all user tables.
Workaround: Use the following SQL command to update the table owner in the database: sp_changeobjectowner '<table_name>', 'td'.- Shortcuts: After you install ALM, shortcuts are not created on the desktop.
Workaround: Use the shortcuts in the HP ALM Platform Start menu, or create a shortcut on the desktop from the <ALM installation directory>\bin folder.- Install Anywhere is the third party product used for the ALM server installation. The dollar sign ($) is a reserved sign in Install Anywhere. To use the dollar sign ($) in any editable text parameter, replace $ with $DOLLAR$.
- Oracle:
ALM Client Installation
- Client Certification: When trying to load the ALM client, you may receive an error indicating that initialization has failed. This can occur if the client machine is missing the new root certificate. For information about Verisign code signing, see this Verisign article: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=AR1747&actp=search&viewlocale=en_US.
Workaround: Install the 2048-bit code signing root and intermediate certificates. For information, see this Verisign article: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=SO19140.- Antivirus software installed on a client machine may interfere with the deployment of client ALM files. Deployment may slow down significantly.
Workaround: Update the antivirus software and virus definition files. If this does not solve the problem, disable the antivirus software, and then install ALM.- Connecting to ALM with the server name and connecting to the server with the server IP address from the same workstation results in ALM files deploying twice on the workstation.
- If a non-administrator user with privileges to install ActiveX controls clicks the yellow information bar to install ALM, client installation fails.
Workaround: Non-administrator users should be prevented from installing ActiveX controls, and should only use the link on the launch page to download the ALM Platform Loader.- The following prerequisite applies if there is a forward proxy with Basic Authentication between the server and client machines. Before the first connection to the ALM server, each ALM client must configure the proxy credentials by using the Webgate Customization Tool. To run the tool, on the ALM client machine, browse to the following path and click the appropriate link:
http://<ALM server name>[<:port number>]/qcbin/Apps/
In WebGate Customization, navigate to the Proxy Credentials area, select the Use these credentials check box, and type values in the Proxy Username and Proxy Password boxes. Click Save and then Close.
For full documentation of the tool, refer to the document available from the above location.
Project Upgrade
- Project Repository Migration:
- While repository migration is in progress, you cannot export the project, or create a new project by copying data from the existing project.
- While repository migration is in progress, if you deactivate a project on an ALM 12.00 server, and restore the project on another ALM 12.00 server, the project is not synchronized between both servers and may be corrupted.
Workaround: Instead of deactivating the project, remove the project from the first ALM 12.00 server.
Note: There is no limitation between an ALM 12.00 server and a previous Quality Center server.- The following limitation may occur when editing a file in the repository (for example, an attachment, script, or report) while the repository migration is in progress. The edited file may remain in the old repository without a record in the repository migration report.
Workaround: After the repository migration has completed, remove the file manually from the repository.- Repository migration may take a long time due to numerous debug messages.
Workaround: Set the log level to "Warning".- While repository migration is in progress, you must not perform a backup of the database or file system.
Workaround: If it is essential to back up the database or file system before repository migration is complete, first suspend the repository migration, and deactivate the project. For more information, refer to the HP Application Lifecycle Management Installation and Upgrade Guide.- To upgrade a project that has extensions enabled, the same extensions must be available in the new version. Before upgrading the project, the availability of these extensions in the new version should be verified. Contact your system administrator for more information.
- Upgrade fails if the History flag has been checked for a virtual field in Customization.
Workaround: Before upgrade, make sure that the History flag has been unchecked for all virtual fields in Customization. .- Stored Procedures: ALM upgrade fails when trying to upgrade projects which contain stored procedures created by a user who doesn't have the required permissions for the upgrade project process.
Workaround: Save and remove the stored procedures before the upgrade and put them back in after the upgrade succeeds. Alternatively, change the DB user of the stored procedures to a user that has the required permissions for upgrade.- ALM fails to upgrade projects where the ALM repository uses a mapped drive (non-UNC path) as the base repository path.
Workaround: In the Site Configuration tab of Site Administration, modify the base repository path from an absolute path to a UNC path.- Project Upgrade Prioritization: When upgrading projects, ALM does not use the priority values defined in the Project Prioritization dialog box.
- Database schema:
- When the project schema on Oracle contains user defined tables or views which have field names which are the same as the ALM project's predefined field names, it leads to inconsistent behavior.
Workaround: Rename the field names of the user defined tables and views so that they are unique.- ALM fails to upgrade projects if the size of the field LN_LINK_TYPE is changed.
- Fields of type Date are converted in ALM 12.00 to type DateTime. If any of these fields contain the value 0, the 12.00 ALM client may crash.
Workaround: Search for all rows that contain DateTime fields with the value 0, and replace with the current date/time.- Project verification checks whether a project used version control based on the Site Administration PROJECTS table alone, and does not verify that the VER_CTRL table is empty.
- When you upgrade a project, ALM creates a new requirement type for each distinct value of the Type field and assigns them to the requirements in the original project. If there are many such values, a large number of requirement types are created in the upgraded project.
Workaround: Before upgrading a project, clear the Type field of values that you do not want to be converted to requirement types.- Microsoft SQL database:
- Oracle: When you upgrade ALM projects on an Oracle database, the size of the Oracle rollback segment (RBS) may increase when running large transactions. When you upgrade large projects (with a database size greater than 2 GB), it is recommended that you increase the RBS size for the duration of the upgrade so that it has at least 3 GB free. After the upgrade, you can change the RBS size to its size before the upgrade.
- To benefit from ALM's session reconnect feature, use of the Major Change option for saving customization changes should be minimized. After a project is upgraded to ALM 12.00, the project administrator should review the Allow Major Change permission for custom user groups, and adjust accordingly to minimize the number of users who are granted this permission.
Documentation
- The ALM COM Custom Test Type Developer Guide and the ALM .NET Custom Test Type Developer Guide are not available in the ALM 12.00 documentation set.
- A new document, HP ALM Security Best Practices Guide, describes security best practices and addresses frequently asked questions from customers regarding secure ALM deployment. The document is for ALM site administrators, and serves as a reference to information located in other ALM documents. The guide is in draft status. If there are additional security requirements that are not covered by this guide, please open a support case with the HP support team to document them and we will include them in future editions of this guide. This guide is available from the HP Software support web site at: www.hp.com/go/hpsoftwaresupport.
- You can view video demonstrations of main HP Application Lifecycle Management features by choosing Help > Movies in the ALM main window.
Site Administration
- Templates: When creating a template by copying an existing template or project, or when importing an existing template, the option to enable versioning is mistakenly displayed. ALM creates the template with versioning enabled or disabled based on the source template or project.
- Project Import: When importing a project file into ALM, you cannot import a file larger than 2GB.
- When creating a project, you cannot use characters °, µ, or § in the project name or domain name.
- Copy Project:
- When a project is copied, non-default values in the DATACONST table are not copied. For example, the REPLACE_TITLE parameter.
Workaround: Manually insert the values into the DATACONST table of the target project after the project has been copied.- Copying a project may lead to an execution timeout error if the project is too large.
- When applying the REPLACE_TITLE parameter to the Management, Test Resources, and Dashboard modules, only the module name in the ALM sidebar is replaced.
- When restoring a project, you should select the dbid.xml file located in the project repository. This ensures that the project retains its original ID. If a project does not have its original ID, the following cross project features may not function properly: cross project customization, importing and synchronizing libraries, and cross project graphs.
- In some cases when there is a proxy server between the user and the ALM server, the user may receive an email with the URL of the ALM server instead of the proxy server. The user cannot navigate to ALM based on the URL in the email.
Workaround: Configure the URL with the ENTITY_LINK_HOST and ENTITY_LINK_PORT site parameters.- Importing a QCP file from an earlier major version is not supported. The error message you receive is not clear and does not provide a failure reason.
"Failed to Import Project;
Failed to create HP ALM project;
Failed to create project 'FS_Demo';
Failed to import new project 'FS_Demo';
Failed to extract information from dbid.xml;
Stack Trace:
java.lang.UnsupportedOperationException: Cannot import project. Source project properties are not specified.
at com.hp.alm.platform.siteadmin.api.logics.CProjectLogic.validateImport
Operation(CProjectLogic.java:5374)"- When adding a non-nullable column to BP_ITERATION (or to it's corresponding BL and HIST tables), the upgrade of the project to ALM 12.00 fails with an error of "not enough columns".
Workaround: Drop the extra columns from the table.Project Customization
- Permissions:
- The following limitation applies in upgraded projects, where user groups are assigned a Create permission without an Update permission. When trying to create a new entity, all the entity fields are read-only. As a result, the user is unable to create the entity.
Workaround: For any entity where a Create permission is assigned, assign the Update permission as well.- User groups created based on the Performance Test Specialist group, are unable to add private hosts, even if such permission in granted in Project Customization.
- Project Planning and Tracking: In the General tab, the following limitations apply when creating, updating, or deleting KPI types:
- When working with an upgraded project, only users that belong to already-existing groups created in a previous version, can create, update, or delete KPI types. This is in addition to users that belong to TDAdmin and Project Manager groups.
- Users that belong to a user-defined group created in ALM based on groups created in a previous version, can create, update, or delete KPI types. This is in addition to users that belong to TDAdmin and Project Manager groups.
Users that do not belong to the groups mentioned above are unable to create, update, or delete KPI types.
Cross Project Customization
General
- IPv6 support: ALM can work on IPv6 enabled systems. However, ALM is still developed within an IPv4 environment. This means that in ALM:
- Logging in to ALM with the same username on machines with different locales may result in an error upon login, or when navigating between modules or to Project Customization.
- Microsoft Windows 2008 R2 SP: When using the Save As dialog box, if a file is selected, the entered filename is ignored. The file is saved as the selected file name.
- If you are working with the Text Search feature or Advanced Filters, and there is a high load on the system, you may experience an impact on performance. In this case, further iterative tuning and optimization of your environment and specifically your database server is required. If necessary, patches will be provided in the future to address these issues.
- If you use the data-hiding filter to hide data in a particular folder from a particular user group, and subsequently delete the folder, a user that belongs to the group is unable to log into ALM.
Workaround: A project administrator should modify the data-hiding filter in Project Customization.- Unicode support: The following ALM features are not included in Unicode support:
- Workflow script editor: Available in Project Customization.
- Automatic Runner: Available from the Test Lab module
- System Information: Available from Attachment views, when clicking the System Info button
- Screen capture / Snapshot: Available from Attachment views, when clicking the Snapshot button
- Requirement to Test Wizard: Available from the Requirements module, when executing the Convert to Test command
- Generate Test: Available from the Requirements module, when executing the Generate Test command
- VAPI-XP script editor: A control embedded in the Script view in the Test Lab module
- Document Generator: Available from the main ALM menu
- Excel reports: Available from the Dashboard module, when viewing an excel report
- Site Administration
- Files that are larger than 4 gigabytes cannot be uploaded to ALM. For example, attachments, test results, or test resources.
- Shortcut keys. To focus on the module menu options, use ALT.
- Service Test Management. The Service Test Management module is no longer included with ALM. For more information, see HP Software Self-solve knowledge base article KM00748092 (http://support.openview.hp.com/selfsolve/document/KM00748092).
- Internet Explorer 7. When opening ALM from an unsupported browser, the following message appears: "You are using an unsupported browser. ALM supports Internet Explorer 7, 8, 9 and 10". Internet Explorer 7 is not supported in ALM 12.00.
Version Control
- Filtering: If you filter on entities using the "Version checked out by" and "Version owner" fields, checked-in entities are still included in the filter.
Workaround: To exclude checked-in entities, use the "Version Status" field.- When enabling version control on an existing project, the first check-in time is set when the first version control action occurs (check-out, check-in, view history of versions, etc.).
- Version control is not supported when working with the following test types: Vuser Script and LoadRunner scenario.
- In a version control enabled project, you cannot copy and paste entities that you have checked out. You also cannot copy and paste entities with related entities that you have checked out.
Workaround: Check in the entities or undo the check-out before you copy and paste them.Releases Module
Releases Module - Project Planning and Tracking
- For projects that have been upgraded, the Test Instances Executed out-of-the-box KPI type contains a KPI analysis graph named Not Executed Test Instances by Responsible Tester. The name of the KPI analysis graph should be changed to Not Run Test Instances By Responsible Tester. This needs to be manually implemented for upgraded projects.
- In the Scorecard tab, the scorecard can contain no more than 600 cells. User must take into account the number of scope items and KPIs defined for each milestone.
Libraries Module
- After importing a library, the roots of the imported library are not marked in the content view when the original filter contained entity IDs.
- Sharing of libraries is not supported between version control enabled projects and non-version control enabled projects.
- When creating a baseline, if an attachment or script is missing from the file system, a warning is written to the ALM log file. The baseline is created nonetheless.
- After synchronizing a source library with an imported library's baseline, you cannot view, in the Imported By tab, from which baseline the imported library was originally imported. In addition, after synchronizing an imported library with a source library's baseline, in the Imported From tab, you cannot view with which baseline the imported library was synchronized.
- In the Comparison Settings dialog box, selecting the Coverage check box in either the Requirements or Tests tab instructs ALM to consider coverage. To ignore coverage, the Coverage check box in both the Requirements and Tests tabs must be cleared. Therefore, if you select or clear the Coverage check box in a library that contains only requirements, for example, this setting is saved and also applied when comparing a library that contains only tests.
- In a version control enabled project, if you synchronize libraries when there are entities checked out by another user, the checked out entities are not synchronized. When you compare the libraries after synchronization, the entities that were not synchronized because they were checked out by another user are not displayed as Modified in the Compare Libraries Tool dialog box, despite the fact that they are different.
- Unable to capture a baseline. The user receives an error message during the baseline verification process that indicates that the feature "capture_baseline" has exceeded size limit fuse for some entity. Workaround: Add the following site parameters to the Server Configuration tab in Site Administration:
- LIBRARY_FUSE - 300000
The parameter value indicates the base number for calculating the maximum number of entities for a library, in order to maintain optimal performance. By default, the value is 2500.
Calculation is performed as follows:
Maximum number of tests in a library = LIBRARY_FUSE * 1 (2500 by default)
Maximum number of resources in a library = LIBRARY_FUSE * 0.25 (625 by default)
Maximum number of business components in a library = LIBRARY_FUSE * 0.25 (625 by default)
A validation of this value is performed when you create baselines, import libraries, or synchronize libraries.
- CLOSURE_ROWS_FUSE_FACTOR_PCT – 300000
The parameter value is used to adjust the limitation on the number of rows of each table (Entity) allowed in a closure for all features (such as baseline, version control, copy/paste). The default value is 100, which means 100% of the original limitation defined on the number of rows for each entity. Setting this value to 300000, for example, means 3000 times the original limitation.
Requirements Module
Risk-Based Quality Management
Business Models Module
- If you remove a model from the business models tree without deleting the representative requirements. If you then reimport the same model, new representative requirements are created with the suffix _1.
- Colors and fonts of model activities are not imported into ALM. Activities are displayed in default colors and fonts.
- If a model path includes a loop, the loop is ignored, and activities are listed only once in the path. Paths that begin or end with a loop are not considered.
- If reimported models change drastically, paths may not resolve automatically.
Workaround: An icon indicates unresolved paths. Resolve the paths manually.Test Resources Module
Test Lab Module
- Test Execution: When non-latin characters are used for the Domain Name and Project Name fields, the notification email for test set execution summary may contain corrupted characters in those fields.
- Pinned test sets: The following test types cannot be added to pinned test sets: Vuser Script, and LoadRunner scenario.
Lab Management/Server Side Execution
- Jenkins Integration: An open source Jenkins plugin has been developed that enables you to trigger a server side execution (functional test set or build verification suite) as a Jenkins build step. The results are reported in Jenkins and in the ALM Test Runs module.
Support for this open source plugin is provided by the Jenkins community. For download and documentation, go to:
https://wiki.jenkins-ci.org/display/JENKINS/HP+Application+Automation+Tools.- Timeslots: If you use a customized version of one of the predefined time formats for your client's system time, timeslots do not function properly.
- Customizing Lab Entities: After customizing an entity in the Lab project, you may receive an error when you log back in to ALM.
Workaround: Delete the TD_80 folder on the client machine before logging in to the project.- In the Host module, the Host Purpose values include "Quick Test Professional" and "Service Test" instead of "UFT (GUI Testing)" and "UFT (API Testing)".
Workaround: For "UFT (GUI Testing)" use "Quick Test Professional" and for "UFT (API Testing)" use "Service Test".- When scheduling a maintenance timeslot for 30 minutes (by default), in order to install a Performance Center patch on a Performance Center host, the following error occurs: "Can't reboot hosts".
Workaround: Schedule a longer maintenance timeslot (at least 45 minutes) and resume the install patch operation.- Functional test sets:
- If you try to delete a functional test set that contains a test instance with a past run in an active state, an error occurs, and the test set is not deleted.
- If you create a test set with at least one test instance with a specific host requirement, and that specific host's purposes include the purposes necessary for the rest of the test instances in the test set, that specific host will be the only host requested for the test set. In that case, if that specific host fails, it will not be replaced by another host, and the test set will not be able to run.
Workaround: In the Requested Hosts tab, add an Automatch host which includes the purposes of the rest of the test instances.- If you try to execute a Functional test set that contains a test with a manual component, an error occurs. See the event log for the full error.
- Execution Report:
- If your project includes non-latin characters, the Execution Report does not open.
Workaround: Rename the project.- The Execution report does not support 125% scale or a non-medium font size.
Workaround: Using the View > Zoom menu in Internet Explorer, reset the zoom to 100%. Using the View > Text Size menu, change the font size to medium.- After working in ALM Web Client or Performance Center, a failure error occurs when attempting to open the Server Side Execution report.
Workaround 1: Close all instance of Internet Explorer and make sure no iexplore processes are running in Task Manager. Reopen ALM and open the report.
Workaround 2: If ALM Web Client is open, log off and reopen the report.- Users that belong to a group based on Viewer (default user group), are unable to run BPT tests in Server Side Execution.
Workaround: In Project Customization, navigate to the Groups and Permissions page, select the user group in the group list, and click the Permissions tab. Click the Test Lab tab. Under the Run entity, select Timeslot ID.Text Search
- When you use the Text Search feature to search for a string that is also part of an HTML tag, such as body or html, all records containing formatted text that uses the tag are found, as well as records containing the search string as text within a searchable field.
- Oracle: When you use the Text Search feature in ALM on an Oracle database, note that Oracle has a default stoplist for each supported language containing a list of stopwords. The search does not find words that are in the stoplist for the language in which the search is being performed. For more information, refer to the Oracle Text Supply Stoplist (http://docs.oracle.com/cd/B19306_01/text.102/b14218/astopsup.htm#CEGBGCDF).
- Oracle: When you use the Text Search feature in ALM on an Oracle database, note that there are some special characters that function as search operators within Oracle. If you use some of them in the search expression, the search may not find the expected results. For example, if you search for the expressions 'a* a' or 'a%a', which contain the operators * or %, an error message may display.
Defects Module
Dashboard Module
- Project Reports: In attachments, hyperlinks to files with I18N letters in the filename appear distorted. Clicking on the hyperlink leads to an error.
- Project reports generated using the Design Step Tabular Template contain a formatting error: The font of the step names in the Design Steps table changes after the second word. The error is fixed in projects created in ALM 11.51 and later, but persists in projects created in older versions of ALM.
Workaround: In Project Customization, navigate to the Project Report Templates module. Select Design Steps Folder > Design Step Tabular Template. Click the Download Template button and save it to your file system. Navigate to the file and open it. Highlight the field of the text containing <<Step Name>>, and change the font size to 9. Save the document. Return to ALM, click the Upload Template button, and select the saved template from your file system.- Graphs: When you generate a Progress Graph in the Dashboard module, the graph may display different information from that displayed in previous versions of ALM. This can occur when the field that you group by does not have the History option enabled in Project Customization, or the History option was not enabled at some time during the period shown in the graph.
- Requirements: When creating a Requirement Coverage report section as a child of a Tests report section, if you include Test fields in the filter for Requirement Coverage, these fields are ignored when filtering the coverage.
- Requirements: When creating a Requirement Coverage report section as a child of a Tests report section, if you include Test fields in the report template, these fields are empty in the generated report.
Integrations
- Unified Functional Testing (UFT):
- After re-saving a UFT test, the broken relations are deleted and the user can no longer view them in the ALM Dependencies tab. If a UFT test has a dependency that is broken (for example, because the dependent asset was deleted), it is displayed, as expected, as a broken relation in ALM. If you later add another dependency to the UFT test, ALM displays the new dependency. The Dependencies tab no longer displays the broken dependency as a dependency at all, even though the action is still referencing an asset that does not exist, and the test fails when it runs. In UFT, the missing asset still shows up as a missing asset, as expected.
- If the environment variable file associated with your test or component is stored in ALM and you modify it from the ALM Attachments tab, the changes are not applied until you reopen the test.
- When launching a UFT script from ALM, the user running the script must have read/write permissions for the system cache folder.
- Unicode: The integration of ALM with other products is not Unicode compliant. Therefore:
- When working with tests or components stored in ALM, you should not use Unicode values (such as the name of the test or component, the name of an application area, the default value of a test, action, component parameter, or method argument values).
- Data sent to UFT from ALM (such as values for test, action, or component parameters) is not Unicode compliant.
Open Test Architecture/API and Workflow
- REST: Since ALM 11.52, the REST API provides resources to carry out most day-to-day tasks with ALM data. At this stage, the REST API is still a technical preview. We anticipate withdrawing this status in an upcoming 12.x service pack, and announcing that the API is production-quality code.
- You cannot change the attributes of a user-defined action via the workflow. For example,
Actions.Action("UserDefinedActions.action_name").Enabled = false
does not disable the action. In addition, if you use a user-defined action in a workflow script without the "UserDefinedActions." prefix, an error is displayed.- If you change the workflow script of a created entity, the change does not occur in copied entities.
- When you use an Open Test Architecture (OTA) list, note that list numbering begins at 1. For example, mylist.Item(1) refers to the first item in the list myList. If you have used OTA lists with numbering beginning at 0 in previous versions of ALM, you must manually update them to begin at 1.
- Favorites: You cannot retrieve favorite filters from the OTA connection's common or private settings, or from the COMMON_SETTINGS table. Use the new API for the Favorite entity.
- Creating Users: If LDAP is enabled, you cannot add users with API.
- Defects: When setting defect comments to read-only, the Add Comment button is not disabled.
- Defects: When changing view setting to show\hide the grid filters, the act_HideColumnFiltering action is triggered instead of _dxact_GridFilters1_WebDefectFrm.
- Attachments: When deleting an attachment in the New Defect dialog box, an incorrect action is triggered.
- No workflow action is available for closing the requirements tree or Req Coverage tab.
- The NewValue parameter in the FieldCanChange workflow event does not return a value when changes occur to the Target Cycle or Target Release field values.
Workaround: Run the following script:Function <entity>_FieldCanChange(FieldName,NewValue)
For i = 1 To NewValue.Count
MsgBox NewValue.Item(i).Name
Next
End Function
where New Value is a list of ISysTreeNode objects.
- Existing Open Test Architecture applications that change data fail in a project with Version Control enabled. You must change your code to check out items before you change them in code, and check them in after posting.
- Workflow scripts and Open Test Architecture applications run with the privileges of the logged-in user, not the privileges of the user who created the script. Scripts and applications that use protected objects, like the Command object, may fail, depending on the project security settings and the group to which the user belongs.
Workflow Backward Compatibility
The issues described below relate to workflow events, actions, and objects that have been changed. When necessary, instructions for modifying existing scripts for purposes of backward compatibility are provided.
- The naming convention for actions has been changed to context.action. For purposes of backward compatibility, the naming convention used in previous ALM versions for upgraded projects is still supported.
- In Project Customization, the following workflow events are not listed in the Scripts Tree in the Workflow Script Editor. These workflow events are supported for purposes of backward compatibility and are only available in upgraded projects.
GetNewReqPageName
GetReqDetailsPageName
GetNewBugPageName
MoveToFolder
MoveToSubject
MoveToComponentFolder (renamed to ComponentFolder_MoveTo)
The GetDetailsPageName is now supported for all entities, not just defect entities and replaces GetNewReqPageName, GetReqDetailsPageName, and GetNewBugPageName.- The CanDelete event has been added to tests, test folders, test sets, test set folders, business components, and business component folders. The Quality Center 10.00 syntax is still supported for purposes of backward compatibility in upgraded projects.
- The DeleteInTreeAct action is no longer supported for the ActionCanExecute event.
Workaround: Modify scripts to use the new action name instead.- The page (tab) number for the GetDetailsPageName, GetNewBugPageName, GetReqDetailsPageName, and GetNewBugPageName events now represents the absolute page number, regardless of the page's relative position in relation to the other displayed pages in the New Defect dialog box.
Workaround: Modify scripts to use the absolute page number instead of the relative page number.- When using the Fields objects in workflow scripts, ALM throws an exception if the script attempts to access a non-active or non-existing field. In Quality Center 10.00, a dummy field object was created.
Workaround: Modify scripts so they do not access non-active or non-existing fields. You can also add On Error Resume Next to scripts as a precaution.- In workflow scripts, the Lists object can be used only with fields that are defined as the Lookup List type in Project Customization of project entities. In previous ALM/Quality Center versions, you could use the Lists object on fields defined as type Lookup List and String.
Workaround: In Project Customization, change the type to Lookup List. To be able to specify values that do not appear in the defined lookup list, clear the Verify Value check box.- When creating a new requirement, the Req_New event is called immediately upon opening the New Requirement dialog box, at which point the requirement type for the requirement is the default. If changes are made to the requirement type, the Req_FieldChange event sets the requirement type when submitting the new requirement. This impacts workflow scripts in a Quality Center 10.00 project that are dependant on the requirement type (for example, a script that arranges the order of fields in a dialog box differently depending on the requirement type) because the relevant code is triggered only by the Req_New event.
Workaround: Execute the same code on the Req_FieldChange event in addition to the Req_New event (in case the changed field is the requirement type).- ActionCanExecute event actions for changing the view in the Requirements module now consistently reflect the name of the target view.
Workaround: Modify scripts as follows:
Change the action actCoverageView to Requirements.DETAILS
Change the action actDocumentView to Requirements.TREE
Change the action _dxact_btReqGridView_wreq to Requirements.GRID
Change the action actCoverageAnalysisView to Requirements.ANALYSIS- The following Test Lab ActionCanExecute event actions are no longer triggered and should be removed from scripts:
- Legacy action names are not called for Analysis menu commands in the Requirements and Test Plan modules.
- New HTML tags added in ALM 11.50 might not be supported by Workflow scripts or external tools which rely on the specific Memo fields' HTML structure.
Workaround: Update the Workflow script/external data tool to the new HTML structure.Business Process Testing
The issues described below relate to working with business components, flows, and business process tests in ALM. For information on issues related to working with business components in QuickTest, refer to the relevant product's readme file.
- Sharing:
- When synchronizing from a baseline which contains automated components that were automated only after they were initially imported, the following issues may occur in the target library:
- Business process tests that include such components fail when executed from the target library using UFT.
- Business process tests that include such components run successfully when executed from the target library using QuickTest Professional 11.00, but the execution is done in non-wrapper mode, and execution might be slower.
- The keyword view of such components, when selected using the UFT plugin, is not displayed properly.
Workaround: After automating the components, capture a new baseline and re-import it to a new library.
- Remote execution: When executing a test remotely on a host, if the host is already running a test that was started locally, the remote test execution is cancelled.
Workaround: If you know that a certain host is used for remote executions, do not run local tests on that host.- Application Areas: When trying to launch an imported scripted component that is associated with the default UFT application area in the Automation tab, a UFT error message is displayed and the component cannot be opened. This limitation is relevant only for the default application area.
- Version History: The canvas view of a business process test's version history disappears as the mouse cursor hovers over an object, or as the mouse is clicked on elements such as the parameter filter.
- Deleting: Deleting a business process test in a versioned project may take longer than expected. A warning message is displayed that describes this limitation.
- Automatic execution:
- 64-bit .NET applications cannot be tested by running business process tests with QuickTest-automated components.
- In Test Lab, test results do not include information about a business component whose run condition was not met during test run.
- QuickTest business components do not support parameter values from a local data sheet. If a component refers to a parameter from a local data sheet, it fails during execution from ALM.
Workaround: In the script used by ALM to run the business process test (called a wrapper test), change the reference to the sheet of the local data table.
To view the contents of a Business Process Testing wrapper test, from the Test Lab module > Test Runs tab, double-click the attachment icon next to the business process test or flow run in the grid.
Example
Change the line:
param = DataTable.GetSheet("[sheet name]").GetRowCount
to
param = DataTable.GetSheet("1").GetRowCount
For more information on wrapper tests, see the task about running automated business process tests and flows in the HP Business Process Testing User Guide.- You cannot run a business process test or flow remotely on a Windows 2008 32 bit host if the Com+ Network access application server role is not installed on the host machine. The following message is displayed: The component or application containing the component has been disabled.
Workaround: Manually install the Com+ Network access application server role:
1. Open the Server Manager.
2. Install the Application Server role that includes the Com+ Network access application server role.- Localization:
- Microsoft Windows 7:
- In the Business Components module, the ALM client terminates when clicking the Automation tab for a business component with QuickTest keyword-driven automation.
Workaround: Set the Data Execution Prevention (DEP) flag to AlwaysOff. To do so, run the Command Prompt as an administrator and paste: bcdedit.exe /set {current} nx AlwaysOff.Web Client
- In Author Mode, when the user modifies a requirement name or description and then clicks a blank space in the browser, the Save and Restore buttons become disabled and changes cannot be restored or saved. This also happens when opening the Insert Image dialog box. Although the user cannot restore the changes, navigating to another requirement or module or returning to Manage mode will implicitly save the changes.
- Including single or double quote signs in values of fields that can be used for categorization, results in an exception being thrown when attempting to expand the terminal category (last category of a category view) node. Breadcrumbs will not work well either. There is no error message but the breadcrumb does not present any values.
- When a memo-type text field (such as Description and Comments fields of Defects) is opened from a column of a grid or a tree view, the field is presented in read-only mode if it contains images added by a Web Client user.
Workaround: Edit of those fields is possible either by using the preview pane (typically below the grid area) or via the Details form of the entity. Image appears as a placeholder.- User names cannot contain the ampersand symbol (&).
- Business rule conditions evaluate to true only if the case of the entity's values matches the case as specified in the condition (for example, "MyString" does not match "MYSTRING)." The Web Client is not case-sensitive and values should match regardless of capitalization.
- When defining a category view and adding a filter that results in no matching records, an infinite error results when switching between Children and Details view and then clearing the filter. The problem is not resolved with Refresh.
Workaround: Remove categorization OR switch module and then return (in this case one more error will be shown, but the tree/grid/details content is correct).- If Apache is configured to require SSL, Web Client cannot open.
Workaround: Change httpd.conf:- When Multi value fields (lists and reference fields) are used as categories in define view the following known issues may occur:
- The actual number of entities in the grid under each multi-list value category (or its sub-categories) may not match the number displayed in the category header in the tree or in the list of sub-categories in a non-terminal categories children view.
- Entities may not be displayed at all if they contain multiple-values that are not contained as a single value in any other entity (for example entity with value `M;N' will not be displayed if there is no category `M' and no category `N').
- Google Chrome browser. Unable to use CTRL - V to paste text in the Requirements or Details view.
Workaround: Instead, use the Paste from Word button.- If the user adds a table in a memo field (such as Description or Comments) and then edits that field in the Web client and saves the changes, the Desktop client will render the background color of some of the table columns in black. Workaround: Change the background color of the darkened table cells.
- When the user types text in a memo field (such as Description, Comments, or Rich Text) some of the characters might not be saved if the user navigates away from the entity or clicks the Save button immediately after typing the text.
Workaround: After updating a memo field, the user should wait 1-2 seconds before navigating away from the entity or clicking the Save button.- If the users triggers a second save operation of an entity before the first save operation is complete, the following error occurs '$save was called during another save operation is in progress'.
When the user has enabled 'Auto Save' in their user settings, a double save operation can be triggered by clicking twice on any button that causes navigation to another entity. Although the second save operation will fail with this error, no data loss will occur and the user can continue working without issue once the error is acknowledged.
This defect occurs mainly when working with ALM over WAN, where response times for save operations are higher.
- In the ALM Web Client, users:
- Cannot enter values for fields when creating defects
- Cannot create defects
This occurs if the By Owner Only check box is selected for fields' Defect Update permission levels in the ALM Desktop Client's Site Administration.
Workaround: The administrator should clear the By Owner Only check boxes for required defect fields.Additional Notes and Limitations - Performance Center
For notes and limitations on LoadRunner, see the HP LoadRunner 12.00 Readme. Available from HP Software Manuals Web site (http://support.openview.hp.com/selfsolve/document/KM00589225/binary/LoadRunner12.00_Readme.htm) and HP Live Network (HPLN) (https://hpln.hp.com/page/hp-loadrunner-1200-readme).
Performance Center Installation
- If Oracle is installed on the machine intended for the Performance Center Server, the IIS port will be in use by HTTPOra service. To use the machine as a Performance Center Server, you must stop and disable the HTTPOra service, run IIS, and install the Performance Center Server.
- For standalone installations, you must manually install the prerequisite application, .NET Framework 4.
Performance Test Execution
- In a version-enabled project, you can run a performance test only if it has been checked in once first.
- To see the Vusers Log in an environment where the system user is non-administrative, grant the non-administrative system user full control of the following directory on the Controller machine: %windir%\system32.
Network Virtualization with Shunra NV
Running Vuser Scripts
- When uploading a script to Performance Center, the length of the script file name combined with the length of the Performance Center Server installation path cannot exceed 256 characters.
- Performance Center does not support running Sybase Vusers on UNIX platforms.
- HTML-based Vusers using Auto Proxy configuration may influence Performance Center host memory usage during a large performance test run.
- You cannot view a snapshot on an error if a Vuser is running on a UNIX load generator.
- Performance Center does not support HTTP protocol with certificates on secure connection (SSL) over the firewall.
- When the Vuser script is a compiled Vuser, the Controller does not send the .dll to the remote machine. Workaround: Using VuGen, add the .dll to the list of script files and upload the script to your project.
- The following Vusers are not supported over the firewall: Corba-Java, RMI-Java, Jacada, and Java.
- Replaying a VB Vuser on a load generator machine with Windows 7 requires administrator privileges.
Monitor Profiles
Online Monitoring
- A Load Generator Over Firewall machine can act either as a Load Generator or as the source machine for the Network Delay monitor at a given time, but not both of them concurrently.
- If the Total Processor Time does not appear on the Host Monitor graph, this is due to a Microsoft limitation related to time synchronization between the client and server machines.
- To change the default monitor settings of the Network Delay monitor, use ICMP instead of TCP.
- If you install a SAPGUI client that is logged in with a specific user, the SAPGUI may not work when logging in with a different user. Workaround: Install the SAPGUI client with the IUSR_METRO or equivalent Performance Center user (PC Identity).
HP Diagnostics Data
- If you configure Performance Center to postpone result collation to a later time, you need to configure an additional setting for Diagnostics data. Modify the server.properties file on the Diagnostics server <Diagnostics_HOME>\Server\etc directory and set distributor.offlinedelivery.preserveFiles = true.
The results are saved for up to five days. To extend this time, Modify the webserver.properties file on the Diagnostics server <Diagnostics_HOME>\Server\etc directory and change the default facade.run_delete_delay=5d to extend the number of days.
- Performance Center will not postpone results collation to a later time when using the Controller as the only load generator machine in the performance test run. Workaround: Manually copy the Diagnostics .eve files from the Diagnostics Server to the <LT_Result_Folder>\j2ee_bd Performance Center results folder.
- To view Diagnostics data in Analysis, use the Analysis option to open the complete data rather than the summary data.
- Performance Center cannot collate Collector metrics, Probe metrics, and Host metrics. This data will not appear in Analysis, but it is available online during the performance test run.
- If the Performance Center host cannot access the Diagnostics Server during data collation, the Performance Center collation for the Diagnostics metrics will fail.
- When running a performance test using the Controller as the only load generator machine, diagnostics data might not be collated. Workaround: Do not run Vusers on the Controller machine.
Hosts
Secure Channels
- On the Performance Center Server, use the Host Security Manager utility to change security settings, and not the Host Security Setup utility.
- When running in secure mode, the name of the host machine may be decrypted.
- When using the Host Security Manager utility to update security settings on a host, if a host is in non-secure mode, and you try to update it to non-secure mode, an update failure occurs.
- When trying to run a performance test over secure channels, if the security keys on the Controller and load generator do not match, the performance test run fails, and the status of the load generators changes to Resource Failure. To re-enable the load generators, you must manually reset the status on each affected load generator to Operational.
General
- When setting the td password to include the equal sign (=), Performance Center functions, such as System Health and run load test, do not work. Avoid using = in the td user's password.
- If you configured ALM to work with a proxy server using NTLM authentication, Performance Center load tests fail to collate results if the Performance Center server was added to ALM with the Internal URL field value of the proxy server used for NTLM authentication. Workaround: When adding a Performance Center server to ALM, enter the direct URL to the Performance Center server in the Internal URL field.
- Fails to collate when running a performance test over a firewall load generator with a host with only one purpose load generator.
- The maximum number of files that can be zipped for the collate or analysis process is limited by WinZip to 65,535. If you change the run-time logging settings to debug mode (Run-time Settings > General:Log > Extended log), it is likely, when running a performance test with a few hundred Vusers for more than an hour, that you will exceed this limit and WinZip will fail to create a zip file.
- The Citrix Connection Center may prevent record and replay of Citrix ICA scripts, if it is running in a different user session on the same machine.
Workaround: Close all instances of the concenter.exe process for all users. To prevent the Citrix Connection Center from starting automatically, set the ConnectionCenter registry key to an empty value"". This key can be found at:- When working with PC in a "lockdown" mode (i.e. the PC system user is not an administrator), the following error occurs when uploading a script from ALM: "Script upload failed. Error: Failed Downloading ALM Client. Please check network connection and user network credentials."
Workaround: Upload a script once as an administrator user. This process will install the ALM client tools for all users on the PC Server machine. After you have successfully uploaded at least one script, you can change the PC system user to a non-administrator user.
Note: When working with several PC servers, you must repeat this workaround for each PC server before changing the user. In this case you will need to add a PC server, perform the upload, set the server's state to 'Unavailable', add a second server, and upload another script.- Usage reports. When a new user name is created using a previously deleted user name, the statistical data is combined and presented in the reports as data from one user name.
Workaround: Do not reuse previously deleted user names.- PAL. When creating subfolders in the PAL Reports and Manage Production Data Sets panes, the user interface hangs.
Workaround: Refresh the user interface (F5), your data will not be lost.VuGen
Analysis
Multilingual Support
This section includes the following sections:
Internationalization Limitations
- To enable multi-language support, the DB and FS servers must support Unicode. Unicode is a feature of MS-SQL that allows multi-language support. In Oracle, multi-language support is defined when installing the server.
- When working with an Oracle UTF-8 database, you can enter text in more than one non-English language. For MS-SQL databases, you can define your projects as Unicode to allow multi-language support. You can also modify existing MS-SQL projects to be Unicode compliant. In addition, you can enter non-English text regardless of the system locale setting on the ALM client machine. However, if the ALM servers are not Unicode compliant, non-English characters entered on the ALM client machine appear as question marks.
- You can only work with localized versions of Performance Center that match the localization of the corresponding ALM version. For example, to work with Performance Center in Korean, your ALM version must also be in Korean.
- You cannot type Japanese characters in the ALM Login window Password field. Workaround: Paste text from the clipboard.
- Opening and updating a project that contains characters different from those set in the ClientOSLocale or ClientOSAdvanceLocale may cause irreversible damage.
- The InputLanguage inserted from an external component to ALM must be the same as the ClientOSLocale and ClientOSAdvanceLocale. For example, you cannot insert a UFT script that contains Japanese characters in a client that runs on an OSLanguage with ClientOSLocale or ClientOSAdvanceLocale that is not Japanese.
- When sending mail that contains non-English characters from the ALM/Quality Center client, it must be sent from the ClientOSLocale and ClientOSAdvanceLocale that are the same as the mail characters locale.
- To send mail that contains non-English characters, the MailServerVersion and MailClientVersion mail server must support non-English characters.
- To display non-English characters, the OSLanguage needs to include the proper fonts for the language.
- The SiteAdminDBCollation and ProjectDBCollation must be set to the same language as the data insert. For example, inserting Japanese characters in a Korean collation is not supported.
- The Spell Checker tool is available only in English.
- Due to a problem in the JDBC driver's specific version, using Chinese and Japanese collation in MS-SQL may cause an error while executing some actions.
- You cannot create ALM/Quality Center projects with Thai characters in the project name.
- The number of double-byte characters you can enter in a ALM edit box may be more limited than the number of characters specified in the relevant error messages. The number of characters that can actually be used depends on the database definitions and the character set collation that is being used. For example, one character can occupy 3 bytes when using Japanese characters with a database that is defined to work with UTF8.
- ALM/Quality Center versions 9.2 and later support LDAP authentication using non-English character sets. Previously, login failed when passwords for LDAP-authenticated users contained non-English characters. To use non-English character sets, set the LDAP_CHARSET parameter in Site Administration to Default or add the relevant value listed in the Basic Encoding Set list.
- Hebrew locale: On Hebrew locale client machines, to ensure that ALM memo fields (for example, Description, Comments, Rich Text) are displayed properly, configure the following settings in the Control Panel > Regional and Language Options window:
- HP ALM Client MSI Generator: Unable to install ALM Client MSI Generator to a folder that contains non-English characters. Workaround: Install to a folder that contains only English characters.
- ALM installation: The path in which installation files for ALM are located, and the path in which ALM is installed, can contain only English characters.
- When downloading a VuGen script from ALM, the file name displayed in the Save As dialog box might be truncated. Due to a Microsoft Internet Explorer limitation, this problem occurs if the original script name contains more than 160 letters, or if script name contains non-english letters. Workaround: Download the script from My Performance Center.
- Non-English national characters are not supported in project names.
Workaround: Use English characters in project names.Localization Limitations
- Demo project. The demo project is available in English only. Localized Demo projects will be available with the first patch on the language packs. Some of the lessons in the ALM Tutorial rely on the demo project for accurate results. You can still perform the tutorial, but some of your results may not match the results described in the lessons.
- The UI language is defined by the ALM server and only one language can be defined per server.
- ALM Language Pack must be installed and operated on Windows where Windows native language (MLU*) is identical to the MUI* language.
- An ALM project created in an English edition cannot be upgraded to a localized edition.
- In the French localized version on Windows XP (SP3), you may not be able to export defects to Microsoft Excel.
- When working with a localized version of Performance Test, you must install Arial Unicode MS - version 1.00 or later on your PC server.
- Web Client is not available in localized versions.
- To support Unicode characters when exporting Trend reports to PDF, install Arial Unicode MS on the Performance Center Server.
- When running system health on a Performance Center machine, the SiteScope health check might fail when parsing the SiteScope version number. This problem occurs on localized machines that treat the decimal point as a comma.
Workaround: Ignore the error.HP Software Support
You can visit the HP Software support web site at:
www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:
- Search for knowledge documents of interest
- Submit and track progress on support cases
- Submit enhancement requests online
- Download software patches
- Manage a support contract
- Look up HP support contacts
- Review information about available services
- Enter discussions with other software customers
- Research and register for software training
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
Legal Notices
© Copyright 1992 - 2014 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
For information about third-party and/or open source license agreements, see the Licenses directory on the product installation media.
Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.
Intel® Core™ are trademarks of Intel Corporation in the U.S. and other countries.
Microsoft®, Windows®, Windows® 7, Windows® 8, Windows Server™ 2008 are U.S registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.
Unix® is a registered trademark of The Open Group.
| © Copyright 2014 Hewlett-Packard Development Company, L.P. |