Reset User Settings on ALM Octane

On some scenarios user might report that they cannot access certain modules or perform certain actions they were able to do before. Most of the times the issue is related to a corrupted user profile in ALM Octane. To clean the settings you need to follow these steps:

1. Logon with the user credentials to the correct workspace

2. Paste the following url to the browser’s address bar after verifying that the sharedspace id and workspace id are correct:

https://<Octane Server>.<domain>.com/ui/?p=<sharedspace>/<workspace>#/clear-settings

Set Proxy Settings from ALM Excel Add-in

Default configuration is using Internet Explorer’s connection settings. In specific situation ( using proxy authentication or multiple proxy servers) a successful connection to the ALM server might not be possible and this would require setting manually the proxy settings.
In case that no Proxy Server should be used, user should click on Show Proxy Settings button, then select Use a Proxy Server option and leave Proxy & Port fields empty.
Error message when the Add-in cannot connect to the ALM server because of incorrect proxy settings or wrong ALM connection string/URL:
“Unable to connect to the ALM server. Please check the server URL.”

Collect logs for integration between ALM and SAP/Solution Manager

For this integration Solution Manger consumes some web services from ALM. The events executed by these web services are no triggered in QC nor SA logs as default so additional settings are required to do it.

1- Enable EI web service logs

a. Open C:\ProgramData\HP\ALM\webapps\qcbin\WEB-INF\classes\,

b. Add or uncomment the following definitions and restart ALM service. # Settings for CXF, CONSOLE, QcLogAppender, CONSOLE, QcLogAppender # Settings for EI, CONSOLE, QcLogAppender, CONSOLE, QcLogAppender

2- Set QC and SA logs to debug mode.

a. Navigate to the Servers tab

b. Select the ALM Server on the left side

c. For sections “Client Log File Settings” and “Site Administration Log File Settings”, click on the “Log Level” link and set it to Debug.

3- Reproduce the issue.

4- Collect QC, SA and wrapper logs, besides the timestamp when the issue was reproduced

JMeter – Version 5.0

A new Apache JMeter Version 5.0 was released this week.

Below are some of the important updates that are available in JMeter 5.0.

Core improvements

Rest support has been improved in many fields

  • Multipart/form-data requests now work for PUTDELETE …
  • It is now also possible to send a JSON Body with attached file
  • Parameters entered in Parameters Tab are now used in body instead of being ignored

In distributed testing, JMeter now automatically prefixes thread names with engine host and port, this makes the counting of threads correct in the HTML report without any other configuration as it was required before

XPath 2.0 is supported in a new element called XPath2 extractor providing easier XML namespaces handling, up to date XPath syntax and better performances

Upgrade to HTTP Components 4.6 last APIs has been completed and JMeter does not rely anymore on deprecated APIs of this library

It is now possible to control in an easier way Loop breaking and Loop switching to next iteration. This is available in Flow Control Action and Result Status Action Handler elements

While Controller now exports a variable containing its current index named __jm__<Name of your element>__idx. So for example, if your While Controller is named WC, then you can access the looping index through ${__jm__WC__idx}

Scripting / Debugging enhancements

Search feature has been improved to allow you to iterate in the tree over search results and do necessary replacements through Next/Previous/Replace/Replace/Find buttons

In View Results Tree, the request and response headers/body are clearly separated to allow you to better inspect requests and responses. You can also search in all those tabs for a particular value

Recording feature has been improved to provide a popup that is always on top when you navigate in browser allowing you to name transactions while you navigate in your application.

You can now restart JMeter from menu File → Restart

Live Reporting and Web Report

Reporting feature has been enhanced

A new Graph Total Transactions per second has been added to the HTML Web Report

It is now possible to graph over time custom metrics available as JMeter Variables through sample_variables. Those custom metrics graphs will be available in the HTML Report in Custom Graphs section

Hits per second graph now takes into account the embedded resources

In Live reporting, the sent and received bytes are now sent to Backends (InfluxDB or Graphite)


Micro Focus introduces New Protocol : TruWeb

Micro Focus has introduced a brand-new protocol to its outstanding line up of protocols. TruWeb is created with a developer mindset. It is a protocol that focuses on the HTTP (transport) level, providing a lightweight, scalable and cross-platform solution for web protocol testing.

This protocol is available in version 12.60 of LoadRunner and Performance Center as well as StormRunner Load. You can start to take advantage of the capabilities that TruWeb has to offer. You can write a TruWeb script using Virtual User Generator (VuGen),, JetBrains WebStorm (IntelliJ), or other IDEs and tools.

TruWeb allows performance engineers, testers and developers create scripts on any platform. It supports Windows, MacOS and Linux. You can record scripts via HAR files or the TruWeb Proxy Recorder. On top of this, TruWeb can also be ran as a standalone solution. You can run TruWeb in single mode, which runs a single iteration for a single Vuser, or in load mode, which runs the script use the scenario settings defined in the scripts scenario.yml file.

TruWeb is currently in Tech Preview. It is in its first phase of its release. The below links will allow you to read more of the current capabilities as well as download and give it a test drive.

TruWeb is currently in Tech Preview. Meaning you do not need a license to run it. However, this may change in future versions.

Debugging problems when recording with the JMeter Proxy

How to debug problems when recording

JMeter Proxy does not record samples

If the browser is working OK, but the Proxy is not recording samples, then check that the browser really is using the JMeter Proxy.

One way to do this is to stop the JMeter Proxy. If the browser continues working, then it is clearly not using the Proxy.

Double-check the browser proxy settings. Clear the browser cache.

The JMeter proxy works by capturing the browser request, creating a sampler and adding it to the test plan, and then it runs the sampler. The response from the sampler is returned to the browser.

It’s very unlikely that the JMeter Proxy could return a response to the browser without the sampler appearing in the test plan. However, it’s worth checking the JMeter log file just in case.

Amount of log files captured in LogGrabber zip in SiteScope

Check ageInDays attributes in .xml configuration files.

To limit the size of generated LogGrabber zip files, by default LogGrabber should be capturing logs for a few days.


<server name=”Logs” logPath=”logs” includeSub=”true” isSiteScopeRelative=”true” ageInDays=”3″>

We can use full.loggrabber.conf.xml to collect more logs.

<server name=”Logs” logPath=”logs” includeSub=”true” isSiteScopeRelative=”true” ageInDays=”14″>

Or we can use Configuration Tool > Export configuration > [v] Include log files method as well.