No, but the steps in the document supplied with the tool is how to change IIS to handle BA. QVWS modification is not included but might be found in the help documentation.
But, unless there is a specific reason for not using headers I do recommend that
Hi Rajesh Vaswani,
I posted a thread regarding the pre-caching in community. But, I didn't get any reply.
I have a issue in finding the Pre-Caching files.
Please let me know if you have idea on my post.
Here is the thread URL
I seen most of the posts regarding the pre-caching is from Sebastian Fredenberg. Can we post our issue directly to him? Let me know if it is possible.
I think I know what the issue is or at least what you should look at. The error likely comes at the authentication point, which means the script has not been modified to handle the authentication as setup in the system. As an example you will get that error if you have enabled header authentication in the system but not changed to header auth in the properties pane in the tool.
Unfortunately we don't support a webform as a login as we cannot know which requests are necessary. Depending on your JMeter proficiency, you can however solve the problem by modifying the generated JMeter script yourself to handle the webform.
Thanks for your answer.
Do you have the sample how to solve this problem?
Could you, please give a small sample how we should change the JMeter script to connect as AD\user (password:1111) to the QlikView server.
We are using QV12 SR5 Default Login Page and jakarta-jmeter-2.5
It will be very helpful.
As we do not know how the communication looks when using the webform it is not something we can easily do, but we can say how you need to go about it.
The scalability tools sends the same requests thata browser would for a regular user. So you need to look at the communication, and then modify the existing jmx script to handle the differences introduced by the webform login (that can be modifications to existing requests or completely new requests). Useful example tools to look at the communication are Fiddler2 or chrome developer tools (if using chrome).
I haven't really understood how this scalibility tool handles QlikView Server Clusters. If I have a Cluster with 4 nodes, should I run four different tests on these nodes seperately? Or can I add all the nodes into the configuration and analyse them in one test?
I could use the jMeter with AD\user. I actually created a local group in the machine and create all the users there. I have tested with a mix of both, local users and ad network users and everything worked well. I tried up to 2000 users and everything went well.
The jmx filed generated byt the Script Generating tool (provided in the zip file) only need a change in the the /QvAJAXZfc/Authenticate.aspx method.
I used Fiddler2 to track how the authentication works, then put that into the jMeter instead of the Autth generated by the tool.