Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
This package (referred to as QVScalabilityTools) contains a complete set of tools for easy creation, execution and analyzing of load/performance tests and regression tests.
QlikView documents to help analyze result and log files(This was previously included in this package):Scalability Results Analyzer
Older versions of the tool can be found here: Tool for easy creation of load/performance tests of QlikView (v.10 and 11)
Tools for Qlik Sense can be found here: Qlik Sense Scalability Tools
Note: Using windows built-in unzip functionality will not allow the .exe to launch unless unblocking zipped package first (properties -> unblock).
Note: Regarding Apache Log4j, reference CVE-2021-44228 (also referred to as Log4Shell), these set of tools are not directly vulnerable to the exploit, however JMeter, the tool required as a separate download, is. How to mitigate the vulnerability for JMeter has been documented here : https://community.qlik.com/t5/Knowledge/Qlik-Scalability-tools-and-log4j/ta-p/1872009
Included parts are:
Version 1.2.7->1.2.8
Changelog 1.2.6->1.2.7
2019-08-26
Documentation updates due to:
- New recommended JMeter version (4.0)
- Changes to the licensing for the Oracle Java implementation (seehttps://www.oracle.com/technetwork/java/javase/overview/oracle-jdk-faqs.html)
- Open-source Java Development Kits (JDKs) have been verified for use with JMeter and the QlikView Scalability Tools
Changelog 1.2.5->1.2.6
Changelog 1.2.4->1.2.5
Changelog 1.2.3->1.2.4
Changelog 1.2.2->1.2.3
Changelog 1.2.1->1.2.2
Changelog 1.2->1.2.1
Changelog 1.1 -> 1.2
Your use of QVScalabilityTools will be subject to the same license agreement between you and QlikTech for QlikView Server. QlikTech does not provide maintenance and support services for QVScalabilityTools, however please check QlikCommunity for additional information on use of these products.
PLEASE NOTE:
The supported versions of Java are 8 and 9. Supported version of JMeter are 3.0 and 4.0, but not 3.2
Hi,
First, this question belong more to the Result analyzer page than here.
If you perform a test using the exerciser (i.e Qlik Sense) the result file should be put in the exerciser folder.
If you perform a test using JMeter (i.e. QlikView) the result file should be put in the JmeterLogs folder.
The same file should never be put in two folders.
I will assume you're testing qlikview since you're posting on this page. To "fix" the problem the copy of the file needs to be removed and the corresponding qvd needs to be deleted. The result analyzer has functionality to help you delete the correct qvd by helping you compose a console delete command.
The only "mandatory" file is the result file, an exerciser result file for Qlik Sense and a jmeter one for QlikView. All other files are there to provide more information, i.e. without the performance counters you will not see any cpu/memory used by the servers etc. Any file missing will have corresponding missing information in the analyzer app.
Hi, i'm trying to use this tools for cache warming purpose but i having a strange issue.
here is my test scenario:
But in audit log of the server i found the following lines after the execution of the scenario:
20161014T072538.000+0100 | 20161014T090657.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Document | BFL\bosti | Open | Document\SH14 | 12 |
20161014T072538.000+0100 | 20161014T090657.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Action | BFL\bosti | action(32)[%AcquisitionCostBasis, Gross Of Acquisition Cost, ] | Doc | 12 |
20161014T072538.000+0100 | 20161014T090657.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Action | BFL\bosti | action(32)[%CurrencyCode, USD, ] | Doc | 12 |
20161014T072538.000+0100 | 20161014T090657.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Action | BFL\bosti | action(32)[%EntityPerspective, Combined View, ] | Doc | 12 |
20161014T072538.000+0100 | 20161014T090657.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Action | BFL\bosti | action(32)[%RateType, PIM, ] | Doc | 12 |
20161014T072538.000+0100 | 20161014T090657.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Action | BFL\bosti | action(32)[%ShareType, Beazley Share, ] | Doc | 12 |
20161014T072538.000+0100 | 20161014T090806.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Selection | BFL\bosti | Month: Apr | Document\LB510 | 12 |
20161014T072538.000+0100 | 20161014T090859.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Selection | BFL\bosti | Clear Month | Document\LB510 | 12 |
20161014T072538.000+0100 | 20161014T090932.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Selection | BFL\bosti | Month: Sep | Document\LB510 | 12 |
20161014T072538.000+0100 | 20161014T091003.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Selection | BFL\bosti | Clear Month | Document\LB510 | 12 |
20161014T072538.000+0100 | 20161014T091039.000+0100 | D:/Test_Environment/Server_Documents/executive dashboard v005.qvw | Selection | BFL\bosti | Month: Jun | Document\LB510 | 12 |
Why the second loop doesnt execute? Any ideea?
Hi,
The reason is that the tool do not handle nested test loops, so your inner loop will be empty of actions. Having them after each other should work fine though, but there are some considerations and caveats when it comes to the using loops so it is a good idea to have "regular" action in between the loops or start with clear all. Note: It will not work properly with clear object actions in the beginning, they need to extract the name of the object to clear which is not possible to do from the action outside of the loop.
Regards
/Sebastian
Hi,
I started using the Scalability Tools for Regression testing.
So far, so good, except, when the regression results of a Straight Table are stored for comparison, it only does the first 100 rows.
How do I get it to store all the rows of a straight table in the regression results?
Thanks,
Andre
Andre van der Merwe wrote:
How do I get it to store all the rows of a straight table in the regression results?
The tool will only save the values which are sent in the protocol, so the only way I can think of is to modify the app to have the straight table show all values, e.g. extend the size of the straight table to show all the values, not very feasible of you have millions of rows though.
Hi guys,
i have a Qlikview server set up to use qlikview web server and i'm trying to run this tool with basic authentication for a stress test but i cant setup up right. Somehow i miss some configuration and dont know what.
What i did:
i constructed a small script for testing
In property tab of the tool i've put at concurrent user: 2 and in authentication section i checked anonymous.
On qlikview server side i've set up DMS authorization
On Document Tab i've set up the value as Appendix C - Setting up Basic Authentication from documentation.
After that i start the script but in event log of the server i see only lines with user under which the tests are started.
What i miss?
Hi,
Very interested to start using QV Scalability Tools for load testing, but getting the following record in the JMeterLog:
timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success,bytes,grpThreads,allThreads,Latency
0,0,,Non HTTP response code: java.lang.RuntimeException,Non HTTP response message: java.lang.IllegalArgumentException: Illegal base64 character 2c,QlikView 1-1,text,false,2197,1,1,0
Timestamp and elapsed are 0, which causes problems in the analyser.
Any idea what is going on here? This record seems to occur near the authentication on the access point.
I tried running the same test on the demo dashboards (which do not require authentication) at us-b.demo.qlik.com without any issues.
Thanks in advance
Hi, first of all I strongly recommend using header authentication as this is a much simpler solution.
However in your case, I see you write that you are using qvws which might be the cause for the failures as the documentaion (Appendix C) is for modifying IIS settings to handle BA.
Hello,
You could check if there are any special characters in the url. If not, I to get more information on what is actually failing I recommend you to run the script (with 1 user) from the jmeter GUI and look at the response and errors there. To do so, in the execution pane, right click on your script and choose "open in jmeter". Then enable the component "View Results Tree". Once running the script all requests and responses will be shown in that component.
cheers
So are you saing that for BA to work IIS is needed? BA doens work when Qlikview Web Server is used?