Tool for easy creation of load/performance tests of QlikView (v.10 and 11)

[Jens_Argentzell]

Document replaced by QV Scalability Tools (QV10,QV11)

[prabhu0505]

I think sometime back I searched for 32-bit version and ended-up concluding

it is unavailable. And also from my experience I think 64 bit version

machine is required to simulate loads against the server.

Regards,

Prabhu0505

[#3]

Field not found - <LogFileShortName> is a codepage issue.

Check the codepage of the csv file file. It needs to be ANSI, not UTF-8.

Regards,

Wei

[Anonymous]

this is really awesome tool and I appreciate the detailed documentation and all the QVWs that came with it!

But i cannot make it work. I am using QVS 11.2 SR5 on Windows 2008 Server. No IIS. HTTPs protocol enabled for AccessPoint.

I was able to create test actions but when I run my script, nothing happens - no errors, it just doing nothing. JMeter log files are empty when I run from QV scalability GUI. If I run manually from JMeter, this is what I see in log file:

timeStamp,elapsed,label,responseCode,responseMessage,threadName,dataType,success,bytes,grpThreads,allThreads,Latency

1397677623531,53383,/qlikview/,Non HTTP response code: java.net.SocketException,Non HTTP response message: socket closed,QlikView 1-5,text,false,2391,5,5,0

1397677623244,53670,/qlikview/,Non HTTP response code: java.net.SocketException,Non HTTP response message: socket closed,QlikView 1-4,text,false,2391,5,5,0

Any ideas how to make it run?

Also i noticed that when I was creating actions, the tool does not show object names for sheets, listboxes etc - I had to type them manually. I made sure I did not create any blank actions.

[lse]

Hi, Borys.

To get the names of the objects you have to save the document structure and add the path to this folder in the "Project files folder:" in the Settings part of the Scenario-tab. Manually typing the IDs for the sheets and objects will work but you need to ensure that the IDs are correct.

A simulation must adhere to he same rules as a "real" user: authentication, authorization and finally licensing. Section access must also be ensured, if used. The Tools can't circumvent these rules by "magic". To reach the goals, of your test, the environment and the simulation must align to make this possible. At the moment the tools only support http and not https.

First test: can you open the application with a real browser from the same machine and user that is running the tool? JMeter will execute as the NTLM-user that started it. The entries, above, doesn't seem to reach the machine at all.

/lars

[Anonymous]

Hi Lars, thanks for the reply! I am running this under my windows account and we do not use IIS for QVS, all is using windows authentication. I can open access point just fine and i simply copied and pasted a link to the document. Also accesspoint is running using HTTPS - hope this is not a problem. I was careful to copy object ID - and for now my actions were just open AccessPoint, Open Document, Change Sheet.

now I noticed I have a space in my URL - could it be a problem? this is how my url looks like:

domain/QvAJAXZfc/AccessPoint.aspx?open=&id=QVS%40lkmsappbi01%7CPROD%20PhysEnt%2FPhysicianEnterpriseDashboard.qvw&client=Ajax

where domain is https://ourdomain,org

[Anonymous]

hi lars, thanks for your reply.

I am running this under my windows account and we do not use IIS for QVS, all is using windows authentication. I can open access point just fine and i simply copied and pasted a link to the document. Also accesspoint is running using HTTPS - hope this is not a problem. I was careful to copy object ID - and for now my actions were just open AccessPoint, Open Document, Change Sheet.

now I noticed I have a space in my URL - could it be a problem? I wanted to post my URL but QV forum does not like that. Basically all accesspoint mounts are named like "PROD Something" or "DEV Something"

[lse]

Hi, Borys.

The name of the AP shouldn't be a problem.
At the moment the tools only support http and not https.
You have two options and the first is to change the environment to be http, but that might not be an option for you. The other is to create a script and generate the JMX and open the jmx-file in a text editor and replace http with https in the appropriate places.

You can execute the jmx from the tools as long as the original xml/scrtipt changes. A change in the scenario or any other parameter will re-generate the JMX and you will have to repeat the search/replace. Best way to validate the search/replace is to execute the test from JMeter with result-tree enabled. There you can monitor both the submitted requests and the responses.
/lars

[Anonymous]

this is did the trick! I replaced all instances of  >http</stringProp> string with >https</stringProp> and after that I was able to run it just fine!

just one last question - how do I enable result-tree in JMeter? for now I just ran JMX file from the scalability tool and it wrote the results back to analyzer folder.

[Sebastian_Fredenberg]

Hi Borys,

The Results tree is enabled by opening the jmx in jmeter, then you will see it as a greyed out componenet that you can right click on and enable. Jmeter can conveniently be started from the GUI, by right clicking your test in the Exection tab and then selecting "open in jmeter".

Note that having the Results Tree enabled will affect performance, so it is only recommended to use for troubleshooting or confirmation that the script works - not for the "real" tests.

Cheers

/sebastian

[Anonymous]

thank you, Sebastian!