QV Scalability Tools (QV10,QV11,QV12) - Page 15 - Qlik Community

Daniel_Larsson · ‎2014-06-02

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:

Standalone application for creating a JMeter script
Support files for launching the script by utilizing the JMeter engine (JMeter installed is a pre-requisite)
Documentation on how to use the package

Version 1.2.7->1.2.8

Changes Section Access requests

Changelog 1.2.6->1.2.7

NTLM support removed due current solution broken and lack of a new secure solution.
Small updates for static content, for future product releases.

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

Added support for QlikView 12.50 and 12.20SR10

Changelog 1.2.4->1.2.5

Added support for QlikView 12.30

Changelog 1.2.3->1.2.4

Added support for JMeter 4.0 and Java 9.
Bugfixes for regression testing
Added actions: Select Excluded, Select All, Select Possible
Added support for 12.20 SR3

Changelog 1.2.2->1.2.3

Bugfix for export to excel action
Added transfer state (bookmark) support for document chaining
GUI: Template selection more accurately show supported Qv versions

Changelog 1.2.1->1.2.2

Bugfixes, make sure minimum amount of selections are respected in certain corner cases

Changelog 1.2->1.2.1

Improved performance for high throughput scenarios

Changelog 1.1 -> 1.2

Improved assertions logic to show faulty actions as errors
Change JMeter template scripts to use groovy instead of beanshell
New prerequisites:
- JMeter version 3.0
- Java 64-bit JRE 8

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

Kritika · ‎2021-07-08

Hi Daniel,

We have verified the settings and we are using DMS and QVUSER Header.

It prompts us for credentials and logs in with QVUSER. (It says Welcome QVUSER on right most corner)

Also, after enabling DMS authorization, the 200M-PTSalesAnalyticsv2.qvw is no longer visible on the access point.

Is there some other setting missing from our end wrt authentication and authorization?

Kritika · ‎2021-07-08

Hi @Daniel_Larsson ,

We have verified the settings and we are using DMS and QVUSER Header.

It prompts us for credentials and logs in with QVUSER. (It says Welcome QVUSER on right most corner)

Also, after enabling DMS authorization, the 200M-PTSalesAnalyticsv2.qvw is no longer visible on the access point.

Is there some other setting missing from our end wrt authentication and authorization?

PawelF · ‎2021-07-08

Hi Kritika,

after enabling DMS authorization, the 200M-PTSalesAnalyticsv2.qvw is no longer visible on the access point.

This means that the Document Settings were not set correctly.

Document Settings
To use the embedded document license, set the users authorized to access the document and
enable dynamic document CAL assignment.

Go to Documents > User documents > select the host of the QlikView Server > select 200mptsalesanalyticsv2.qvw in the QMC.

Select the Document CALs tab and check that the Document CALs section contains information
on “2000 Embedded Document CALs”. In addition, select the Allow dynamic CAL assignment
checkbox.
In some cases, the Document CALs tab is not present. If so, restart the QlikView Server services to
resolve the issue.

Select the Authorization tab and then the green plus icon next to User Authorized to Access
Document to display a new entry. Set Access to Always and User Type to All Authenticated
Users.

Kritika · ‎2021-07-09

Hi @PawelF/ @Daniel_Larsson,

Thanks, the authorization tab was not visible when we had enabled Allow dynamic CAL assignment.

I am able to see that tab now and after allowing all users I can see the application with DMS authorization.

However, we are still getting the prompt for the user credentials when we open the access point even with Header and DMS enabled.

When we select Type as Header, the Header value is QVUSER by default and Prefix is CUSTOM\

We are using the ModHeader Chrome extension, where we have set Name and Value as QVUSER.

The header profile is enabled in the extension.

While executing the script, we are getting the error 401 unauthorized access when the below cmd is executed:

Measure-Command { $request = Invoke-WebRequest -Uri http://accesspointip/qlikview }

Can you please help me out on this issue?

Kritika · ‎2021-07-09

Hello @Daniel_Larsson and @PawelF,

Thank you for your help!

We were able to resolve the credential prompt issue by enabling Anonymous authentication and disabling windows in the IIS.

However, when the script was executing the 1st Preload it failed and restarts the services again, and so on.

In the Jmeter logs, we can see the 401 error again.

While opening the document 200mptsalesanalyticsv2.qvw it prompts for credentials again and the preload fails.

Can you please let us know whether there's some setting to disable prompts while opening qlik dashboards too?

T

Kritika · ‎2021-07-15

Hello,

We were able to resolve the credential prompt issue by disabling windows authentication in Qlikview, QVAJAX, QVPlugin, SCripts, and authentication.aspx and enabling anonymous for the same in IIS.

However, post this we are facing some issues while running the preload test, in logs, we can see the error :

Not Storing Valid Cookie:

URL http://hostname/QVAJAXZfc/AccessPoint.aspx?mark-&platform-browser.gecko.3.6&dpi=96&xrfkey-xrfkeyvalu...

(Cookie name may not contain blanks)

Can anyone please help us out in this please?

Kritika · ‎2021-07-16

Hi @Daniel_Larsson,

We have tried using JMeter 5.3, 4.0, and 3.0.

With the 5.0 and 4.3 versions, we are getting the Not storing invalid cookie: error.

However, when we used 3.0 the preload test is failing with 11 errors, and no errors are being written in the log file which has become difficult for us to debug.

Can you please help us and let us know if we need to enable or change some other settings or try another version?