Micro Focus Performance Center
Software Version: 12.56 and 12.57
Publication date: May 01, 2018
This file provides the following information about Performance Center 12.56 and 12.57:
Performance Center includes many new features, enhancements, and usability improvements from Performance Center 12.56 and 12.57.
You can find information on What's New in this version in the Performance Center Help.
For information about the features in previous versions, use the following links:
If you have already installed Performance Center 12.55 or 12.56, you just need to install the Performance Center 12.57 patch on the Performance Center server, hosts, and load generators, and optionally install the latest ALM 12.55 patch (Patch 2).
The following sections provide step-by-step instructions for users that are installing Performance Center 12.57 from scratch, or for users that require more detailed instructions:
Installing ALM 12.55 is a prerequisite to installing Performance Center (we recommend installing the latest ALM 12.55 patch—Patch 2). You can install ALM 12.55 Patch 2 directly, or you can install it on top of ALM 12.5x versions.
If you are installing ALM 12.55 Patch 2 on a machine that does not contain a previous version of ALM, follow the full ALM installation instructions.
If you are upgrading from version 12.5x, install ALM 12.55 Patch 2 on top of your previous version, and follow the full ALM installation instructions.
If you are upgrading from version 12.2x or earlier, uninstall the existing version of ALM, and follow the full ALM installation instructions.
For ALM installation instructions, see the ALM Installation and Upgrade Guide - Windows / Linux.
For details about the supported integrations for ALM, see the ALM Integration Support Matrix.
Performance Center 12.57 is a patch that must be installed on top of Performance Center 12.55 or 12.56.
Installing Performance Center in interactive mode
On the Performance Center machine, run the Performance Center installation files, and follow the onscreen installation and deployment instructions.
For Performance Center 12.57, run PC_00345.exe for Performance Center server, and PC_00347.exe for Performance Center host.
For Performance Center 12.56, run PC_00314.exe for Performance Center server, and PC_00346.exe for Performance Center host.
Remote patch installation
For Performance Center Hosts and Standalone Load Generators, you can install the patch from Performance Center Administration.
To upload the relevant patch (.msp) for Performance Center Host and/or Standalone Load Generators, in Management > Hosts > Patches tab, enter the details for the patch, and click Upload.
For details, see Upload Patches in the Performance Center Help.
To install the patch, (in the Hosts tab, select the relevant hosts on which to install the patch, and select Maintenance > Install Patch.
For details, see Install patches on hosts in the Performance Center Help.
Installing the patch in silent mode
You can install the patch from the command line in silent or non-interactive mode. This option is useful when installing the patch on multiple machines (for example, when working with Microsoft SMS):
msiexec.exe /update <full path to msp file> [/qn] [/l*vx <full path to log file>]
/qn option sets the silent mode and
/l*vx enables the logging in verbosity mode.)
Verify that you have full local administrative permissions (root account for Linux systems) to install the patch on the machine.
Before starting the installation, make sure there are no active runs or jobs on the machine (if necessary close mdrv.exe, TruClientIELauncher.exe, firefox.exe, or chrome.exe).
Install Performance Center 12.57 by launching the appropriate installation file.
Make sure the Performance Center standalone applications are updated with the appropriate patch.
After installing Performance Center 12.57, make sure you clear the browser cache on your client machine, before accessing the application.
Note: To uninstall Performance Center 12.57 that was initially installed from the network, you need to remove the installation file separately from each Performance Center host machine on which it was installed.
You can find information and components for the installation as follows:
For information on Performance Center system requirements and supported versions, see System Requirements (previously named Product Availability Matrix or PAM).
For details about supported integrations for Performance Center, see the Integrations Catalog.
For details on installation and upgrade, see the Performance Center Installation Guide.
All of the additional components (such as the Citrix Agent and so on) can be found in the installation package's Additional Components folder.
Troubleshooting patch installation issues
When installing Performance Center 12.57 or 12.56, you might encounter the following error messages, which can occur as a result of your antivirus software interfering with the installation process:
This section includes:
Important: Performance degradation may occur in ALM when working with more than 500 projects in Oracle. To improve performance, it is recommended to disable a PAL related maintenance task (a Performance Center feature). For more details, see Software Self-solve knowledge base article KM01357239.
Oracle Container DB mode is not supported.
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.
Resolution: Use the following SQL command to update the table owner in the database: sp_changeobjectowner '<table_name>', 'td'.
When a project is restored or imported onto a server with 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.
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
Starting in ALM 12.20, ALM uses Jetty 9, which no longer supports the AJP protocol. If you have previously used an AJP connection to ALM Jetty from a front-end Web server (Apache or IIS), it is recommended that you switch to an HTTP connector. For more details, see http://wiki.eclipse.org/Jetty/Howto/Configure_AJP13.
In ALM 12.20, Jetty is upgraded from version 5 to version 9. Before you upgrade to ALM 12.55, review the settings in jetty.xml (<ALM Server directory>\conf\jetty.xml). If SSL is enabled, obtain a new server certificate, or copy the existing certificate by performing the following steps:
Copy the certificate file to the destination server after installing ALM 12.55.
Configure a secure connection on Jetty. Follow the procedure on how to secure Jetty, as described in the ALM Installation and Upgrade Guide.
ALM installation: The DNS name cannot contain an underscore character "_" in the repository location.
Replace the name with an IP address.
Alternatively, in Site Administration, click the Site Configuration tab. Then edit BASE_REPOSITORY_PATH and change the default repository location. For more information, see Software Self-solve knowledge base article KM189843.
Unsupported databases: When installing ALM on an unsupported database, a license validation error occurs. For more information, see Software Self-solve knowledge base article KM02307970.
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. Previously, that CA was Verisign. Now we have moved to a new certificate issued by Comodo.
Resolution: Follow the Comodo Code Signing Certificate instructions provided in the Legal Notices section of the readme file.
When the Microsoft Root Certificate Program is disabled, the root CA may not be downloaded or updated automatically.
If the root CA is not installed, when downloading the ALM client on a client machine, you may see the error:
“Windows has found a problem with this file.
Publisher: Unknown Publisher”
The digital signature detail dialog of the required certificate shows that it is issued by “GlobalSign Timestamping CA – G2”. With this error, ALM client cannot be installed.
Resolution: Follow the instructions in Software Self-solve knowledge base article KM02863020.
Antivirus software installed on a client machine may interfere with the deployment of client ALM files. Deployment may slow down significantly.
Resolution: Update the antivirus software and virus definition files. If this does not solve the problem, disable the antivirus software, and then install ALM.
If a non-administrator user with privileges to install ActiveX controls clicks the yellow information bar to install ALM, client installation fails.
Resolution: 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.
If you have a slow connection from VuGen or Analysis to ALM, this may be because the VuGen or Analysis machine does not have access to the WAN, and so cannot verify the digital signature of the relevant files.
Resolution: Download and import the certificates from https://support.globalsign.com/customer/portal/articles/1426602-globalsign-root-certificates using certmgr MMC until the issue is resolved (you might not need to import all the certificates). This information is also available in a knowledge base article.
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 server and restore the project on another ALM server, the project is not synchronized between both servers and may be corrupted.
Resolution: Instead of deactivating the project, remove the project from the first ALM server.
The following limitation may occur when adding a file manually or renaming an existing file name directly in the repository while the repository migration is in progress: The file may remain in the old repository without a record in the repository migration report.
Resolution: 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.
Resolution: Set the log level to Warning.
While repository migration is in progress, you must not perform a backup of the database or file system.
Resolution: 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 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.
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 project upgrade process.
Resolution: 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.
Resolution: 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.
When the project schema on Oracle contains user defined tables or views that have field names which are the same as the ALM project’s predefined field names, it leads to inconsistent behavior.
Resolution: 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.
Microsoft SQL database: When working with a case-sensitive SQL database, the upgrade process fails if the exception file contains an extra table in which the name is in lowercase.
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.
Oracle: After installing ALM 12.x using Upgrade a copy of the existing schema, if ALM succeeded to create a copy of the LAB_PROJECT, the verify report shows missing indexes, triggers, sequences, and constraints. For more information, see Software Self-solve knowledge base article KM00912265.
After importing a version control-enabled project from a project that has the Enterprise Integration Module for SAP Solutions extension enabled, the user is unable to create tests from the Test Plan module.
Resolution: Repair the project from Site Administration.
IPv6 support: ALM can work on IPv6 enabled systems. However, ALM is developed within an IPv4 environment. This means that in ALM:
Data communication is possible using IPv4 transport.
Management communication can be over IPv4 transport.
The presence of the IPv4 network stack is required.
Logging in to ALM with the same user name 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 file name is ignored. The file is saved as the selected file name.
Files that are larger than 4 gigabytes cannot be uploaded to ALM. For example, attachments, test results, or test resources.
New dialogs cannot be opened if you enable the 'Prevent this page from creating additional dialogs' option in Firefox.
Resolution: Do not enable the 'Prevent this page from creating additional dialogs' option in Firefox.
While most of the Performance Center administration tasks can now be performed in Performance Center Administration (in addition to being performed in ALM Lab Management), the following modules are not accessible from ALM Lab Management and can only be used from Performance Center Administration:
PC Licenses (for maintaining the Performance Center and Performance Center host licenses)
Usage Reports (for analyzing Performance Center site users and resource usage)
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.
When installing UFT on a machine with a load generator SA, you must restart the LoadRunner Agent Service to be able to replay UFT scripts.
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.
This section includes:
For notes and limitations on LoadRunner, see the LoadRunner 12.57 Readme.
When trying to run the Performance Center Configuration Wizard, it displays the error: “Failed to load object HP.Software.HPX.ConfigurationModel.Pages.PageInstaller. Would you like to continue with the configuration?"
Resolution: This is an indication that the Windows operating system is corrupted. We recommend performing a clean installation of the Windows operating system on the affected machine.
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.
When installing Performance Center 12.55 or later over a previous version, the installation replaces the SSL certificate files. If you are working with cloud-based load generators you might experience connectivity issues.
Resolution: Before installing Performance Center 12.55 or later, back up the certificate files in the following directory: <Performance Center root>\dat\cert. After installing Performance Center 12.55 or later, copy the backed up certificate files to <Performance Center root>\dat\cert.
When adding/reconfiguring a Performance Center 12.x server in Lab Management, the operation fails and one of the following IIS configuration or change identity errors occur:
Change Machine Identity failed. Reason: Value cannot be null
The IIS configuration of Performance Center server failed. Reset IIS and add or reconfigure the Performance Center server
javax.xml.ws.WebServiceException: Could not send message
Resolution: See Software Self-solve knowledge base article KM00966287.
Performance Center server and host components are not FIPS complaint and cannot operate on a FIPS enabled Windows machine. For details on how to work with Performance Center on a FIPS enabled Windows machine, see Software Self-solve knowledge base article KM01420828.
Upgrading from Performance Center 12.50/12.53/12.55 to 12.57
After restoring LAB_PROJECT from a previous version, or upgrading LAB_PROJECT when using a version earlier than 12.50, you must restart the ALM service to apply the additional database updates (such as Publish Runs for Trending to LAB_MAINTENANCE_TASKS).
After upgrading from ALM 12.50/12.53 to ALM 12.55 Patch 1, the details of the Performance Center servers, hosts, and the ALM internal/external URLs are not removed from the LAB_PROJECT. You will not be able to work properly where ALM 12.55 Patch 1 refers to Performance Center servers and hosts created in previous versions (12.50/12.53).
Upgrade from Performance Center 12.50/12.53 to 12.55
There are two scenarios depending on the way the system was upgraded.
Use case 1: Upgrading an existing ALM/PC environment to PC 12.55
In this case, the machine names and URLs are the same and the values are correct in the LAB_PROJECT.
The only action that is required is to reconfigure the machines:
Reconfigure the Performance Center servers.
In Lab Management, select Servers > PC Servers. Reconfigure the Performance Center servers.
Reconfigure the Performance Center hosts.
In Performance Center Administration, select Management > Hosts. Select the hosts you want to reconfigure in the Hosts grid, and click Reconfigure Host.
Verify the system configurations.
In Performance Center Administration, select Management > System Health. Click Check System, select all the system components, and then click Start to check system health for each machine.
Use case 2: Installing ALM/PC on a new environment using a copy of 12.50/12.53 LAB_PROJECT
In this case, the copied LAB_PROJECT is still pointing to the original ALM 12.50/12.53 server, Performance Center server, and Performance Center hosts.
Perform the following steps (make sure you perform them in the order set out below):
Delete the Performance Center servers.
In Lab Management, select Servers > PC Servers. Delete the Performance Center servers.
Update the ALM URL.
In Lab Management, select Servers > PC Servers. Update the ALM internal/external URLs to point to the new ALM 12.55 Patch 1 server.
Add the new Performance Center servers.
In Lab Management, select Servers > PC Servers. Add the Performance Center 12.56 servers.
Delete the Performance Center hosts.
In Performance Center Administration, select Management > Hosts. In the Hosts tab, select the hosts that are still active in 12.50/12.53, or that are not relevant for 12.57, and click Remove Selected Host.
Add the new Performance Center hosts.
In Performance Center Administration, select Management > Hosts. In the Hosts tab, click Create New Host, and add the Performance Center 12.55 hosts.
Verify the system configurations.
In Performance Center Administration, select Management > System Health. Click Check System, select all the system components, and then click Start to check system health for each machine.
Upgrade from Performance Center 12.55 to 12.57 (install patch)
For Performance Center Server, install the patch by running the Performance Center 12.57 installation file (.msp). For details, see Performance Center Installation.
For Performance Center Hosts and Standalone Load Generators, you can install the patch in one of the following ways:
In Performance Center Administration:
(i) Upload the relevant patch (.msp) for Performance Center Host and/or Standalone Load Generators (in Management > Hosts > Patches tab, enter the details for the patch, and click Upload). For details, see Upload Patches in the Performance Center Help.
(ii) Install the patch (in the Hosts tab, select the relevant hosts on which to install the patch, and select Maintenance > Install Patch). For details, see Install patches on hosts in the Performance Center Help.
Manually install the relevant 12.57 package on the Performance Center Hosts and/or Standalone Load Generators.
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.
If one of the diagnostics probes is offline, Performance Center does not try to establish a connection to the remaining probes in the list. The performance test runs with no issues, but no diagnostic metrics are collected. Wait until the performance test starts and check if all probes were successfully connected. If they were not, stop the test, remove the problematic probe and restart the performance test.
When the URL Authorization feature is installed and enabled as part of the IIS role, the My Performance Center pages are not rendered correctly and some functionality issues, such as uploading a script and starting a performance test, can occur.
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 100 characters.
HTML-based Vusers using Auto Proxy configuration may influence Performance Center host memory usage during a large performance test run.
You cannot view the "Snapshot on Error" if a Vuser is running on a Linux load generator.
When the Vuser script is a compiled Vuser, the Controller does not send the .dll to the remote machine.
Resolution: Using VuGen, add the .dll to the list of script files and upload the script to your project.
Java Vusers are not supported over the firewall.
Checked out scripts opened from VuGen using ALM Connection cannot be checked in from Performance Center. This limitation occurs if the same user is used to log in to VuGen and Performance Center.
Resolution: Check in the scripts from VuGen.
If you create a Load Test with a monitor profile and copy it to a different project, but choose not to copy linked entities, you cannot remove the monitor profile.
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.
Resolution: Install the SAPGUI client with the IUSR_METRO or equivalent Performance Center user (PC Identity).
You might experience a degradation in online graph performance when using SiteScope monitors with a large number of measurements.
Resolution: If possible, use less measurements in SiteScope. If the SiteScope server is also used for purposes other than performance testing, try allocating another SiteScope server specifically for performance testing with less measurements configured in it.
The Network Delay Time monitor shows "No Data" in the online graphs when using Windows Server 2008 R2 SP1.
Resolution: On the Windows 2008 R2 machine:
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 be able to collate Diagnostics results when using the Controller as the only load generator machine in the performance test run.
Resolution: Manually copy the Diagnostics .eve files from the Diagnostics Server /data/<RunID> 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.
Resolution: Do not run Vusers on the Controller machine.
The remote patch installation feature should be used for installing Performance Center certified patches only.
Before running the IP Wizard to define multiple IPs on a host, make sure to first add the host to ALM.
If you are using cloud load generators, Performance Center 12.57 out-of-the box templates do not exist. If you want to deploy cloud load generators with 12.57 installed, you need to create them manually.
If you have not upgraded to ALM 12.55 Patch 1 or 2, the following out-of-the box cloud Host Templates cannot be used for provisioning Cloud Hosts:
Amazon EC2_Asia_Pacific_Mumbai_Windows_Load Generator 12.55_Medium
Amazon EC2_Asia_Pacific_Mumbai_Unix_Load Generator 12.55_Medium
Amazon EC2_Asia_Pacific_Mumbai_Windows_Load Generator 12.55_Large
Amazon EC2_Asia_Pacific_Seoul_Windows_Load Generator 12.55_Medium
Amazon EC2_Asia_Pacific_Seoul_Unix_Load Generator 12.55_Medium
Amazon EC2_Asia_Pacific_Seoul_Windows_Load Generator 12.55_Large
If you want to provision cloud hosts on those locations you need to create your own custom template with the following configuration:
Host Installation: Windows Standalone Load Generator or Unix Load Generator.
Location: <according to your need>
If the location is Seoul, you can use any of the T2, P2, R3, or I2 instance types.
If the location is Mumbai, you can use any of the T2, R3, or I2 instance types.
If the instance types available for Seoul or Mumbai do not fit your needs, please contact Software Support.
The cloud account creation may fail with the following error in the server log:
sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
Resolution: Before you create a cloud account, you must first define network settings for communicating with the cloud and create digital certificates. For details, see the ALM Lab Management Guide and Software Self-solve knowledge base article KM00891595.
When creating a new cloud host template, the default value of the Host Installation field is set to
Windows Standalone LG. If you are working with a Linux environment image, make sure to set the Host Installation field to
Unix Load Generator.
Provisioning a load generator on Amazon EC2 Cloud, when the Amazon security group name contains spaces, results in the following error:
"Invalid expression [<security group name>]. Message: literal ['xxx'] is illegal".
Resolution: Create a new security group in Amazon with no spaces.
Microsoft Azure Cloud: When provisioning a large number of hosts ( ~ 50), a high failure rate occurs due to an Azure Active Directory Access Control Service limitation.
Provisioning fails, and the following error appears in the Site Administration log:
The supplied password must be 8-123 characters long and meet password complexity requirements.
Resolution: Run provision again and select a password that meets the operating system passwords complexity requirements.
When setting the td password to include the equal sign (=), Performance Center functions such as System Health and run performance 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 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.
Resolution: When adding a Performance Center server to ALM, enter the direct URL to the Performance Center server in the Internal URL field.
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 runtime 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.
Resolution: 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:
For 32 bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
For 64 bit systems: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Wind ows\CurrentVersion\Run
When working with Performance Center in "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."
Resolution: Upload a script once as an administrator user. This process will install the ALM client tools for all users on the Performance Center server machine. After you have successfully uploaded at least one script, you can change the Performance Center system user to a non-administrator user.
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.
Resolution: Do not reuse previously deleted user names.
The CDA Servers module is unavailable for the PC Standalone license type.
Service Virtualization. Service Virtualization monitors are not shown in the Performance Test Run window. The following error is displayed in the Transactions view: “Cannot access HKEY_PERFORMANCE_DATA on host <host_name> with error Access is denied”.
Resolution: See Software Self-solve knowledge base article KM02234113.
Network Virtualization. Microsoft Internet Explorer 11.00 is not supported when working with Network Virtualization from Performance Center.
Resolution: See Software Self-solve knowledge base article KM00959046.
When creating subfolders in the PAL Reports and Manage Production Data Sets panes, the user interface hangs.
Resolution: Refresh the user interface (F5). The data will not be lost.
When defining a Webtrends host in the PAL Data Set Creator wizard, make sure to enter the Webtrends Data Extraction API Host URL (
http://<Webtrends Data Extraction API machine>:<port>). Do not enter the Webtrends Server URL.
When opening SiteScope from the Topology Designer window or the Performance Test Run window, most of the SiteScope options are disabled except for the options needed for configuring SiteScope monitors.
Topology integration is not supported in Community edition for the last supported SiteScope version. To enable the integration, you must upgrade your SiteScope license. For details on upgrading your license, see the SiteScope Deployment Guide available from the Software Documentation Portal at https://docs.microfocus.com/, or contact Micro Focus Software Support.
Starting at Google Chrome 45 (http://www.java.com/en/download/faq/chrome.xml) and Mozilla Firefox 42 (http://www.java.com/en/download/), NPAPI plugins are no longer supported (technology required for Java applets).
Analysis fails when trying to connect to a version of the ALM server that is different from the server you are connected to in your browser.
Resolution: Connect to the other version of ALM in your browser and download the client files by clicking on the Application Lifecycle Management link.
Offline results. There might be small discrepancies in the number of successful and unsuccessful transactions displayed in offline results (next to the bar chart), and the actual number that is displayed in Analysis and the HTML report. This is because the number in the offline results is based on data stored in ALM just before the test ended, and not the actual raw data stored on the load generator machines.
If you have updated the Performance Center server and hosts to 12.57, but not updated ALM 12.55 to Patch 1, to include test run data for MQTT, Streaming, TruClient Native Mobile, AppDynamics, New Relic, Dynatrace, Network Virtualization, and MQTT monitors in trend reports, you must add items to the ALM database. For details, see Software Self-solve knowledge base article.
When using an IE 10 browser on Windows 10 operating systems, help pages all open to the Help front page.
Resolution: Open the Help and search for the required information manually by using the search or index fields, or use a different browser.
This section includes the following sections:
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, My Performance Center, and Performance Center Administration machines. However, if the ALM and Performance Center servers are not Unicode compliant, non-English characters entered on these machines appear as question marks.
You can work with localized versions of Performance Center only if they 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.
Resolution: 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 an 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 UTF-8.
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 settings in the Control Panel > Regional and Language Options window. Set Languages For Non-Unicode Programs (Administrative tab) and Current Format (Format tab) to Hebrew.
ALM Client MSI Generator. You cannot install the ALM Client MSI Generator to a folder that contains non-English characters.
Resolution: 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.
Resolution: Download the script from My Performance Center.
Non-English national characters are not supported in project names.
Resolution: Use English characters in project names.
Non-English Cyrillic URLs are not supported when creating noise scripts.
Resolution: Use English characters when creating noise script URLs.
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 a Windows machine where the 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.
When working with a localized version of Performance Center, you must install Arial Unicode MS - version 1.00 or later on your Performance Center server.
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.
Resolution: Ignore the error.
When clicking context-sensitive help, Performance Center now links directly to the online Performance Center Help. This enables you to use the most recent version available of the Performance Center online help.
If your organization has firewall restrictions that prevent you from using the online Help Center, you can download and deploy the Help Center on your local server. For details, follow the Download Help Center instructions in the Performance Center Help.
This product includes limited functionality entitlements – these can be either “beta” or “tech preview” features (as indicated in the What’s New). This means that these beta or tech preview features may be undergoing further testing before their full capabilities are released. These features, including their capabilities and content, are provided on an “as is” basis. Micro Focus disclaims all other warranties. Micro Focus shall not be responsible for any loss or damage suffered by any customer as a result of their use of any beta or tech preview feature.
Micro Focus reserves the right to change or remove a beta or tech preview feature at any time, without further notice. These features, which include basic capabilities, are currently offered as embedded features accompanying the product license. In the future, Micro Focus may offer advanced capabilities for the same features at a separate cost.
Should you encounter any bugs, glitches, lack of functionality, or other problems with any beta or tech preview feature, please let us know immediately. Your help in this regard is greatly appreciated. Send your feedback to Performance Center Feedback.
Certain versions of software and/or documents (“Material”) accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.
The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
Contains Confidential Information. Except as specifically indicated otherwise, a valid license is 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 code signing certificate for Performance Center was changed from Verisign to Comodo starting on January 1, 2017.
If you are installing this product on a computer with an older version of Windows, or on a computer without automatic Windows updates, the Comodo root certificate may not automatically be included as a trusted root certificate.
In such cases, we recommend manually configuring Comodo as a trusted root certificate.
For more details, see: https://technet.microsoft.com/en-gb/library/dn265983.aspx.
© Copyright 2001-2018 Micro Focus or one of its affiliates
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
Oracle and Java are registered trademarks of Oracle and/or its affiliates.
Send documentation feedback