LoadRunner passes every OTHER iteration…

  • Questions
  • LoadRunner passes every OTHER iteration...
Question ID: 104341

PROBLEM: SAP script written on standard Web protocol fails on every OTHER iteration

We have a portal single sign on application that in a basic sense works like this:
1) The first time a user signs on his authentication details are stored in a cookie
2) the user gets access to an sapwebdynpro dynamically generated javascript web page, and enters data
3) after he hits save or submit, and the transaction is accepted, he returns to the same page with a frame at the top that says "data saved sucessfully"
4) On the second iteration, the SAP application looks for the previously stored cookie and if if it the cookie not there the system re-authenticates the user through the single sign on portal rather than the previously generated cookie

If the second iteration fails – why would the third fail, and the fourth pass?

Our hunch is system corruption, as when signing on as the official administrative user the problem goes away. Since I use a different administrative sign on, I potentially have write permissions to the registry (thank you Steve Antonoff of Orasi for this idea) and could have corrupted it.

If it is not system corruption, I had one more idea, what is the ORD in web_reg_save_paran is alternating between two different values? Simple enough problem to solve if this is true. Just check if the iteration number is even ( using MOD 2) and conditionally change the value based on the iteration. This can be easily solved by setting the ORD value in web_reg_save_paran to all, replaying the script, and setting parameter substitution to on, and seeing if the value changes.



Marked as spam
Posted by (Questions: 2, Answers: 0)
Asked on March 13, 2011 5:43 pm
Answers (1)
Private answer

Have you tried recording multiple iterations to see what the generation log shows for iteration 2 and 3?

Marked as spam
Posted by (Questions: 3, Answers: 16)
Answered on March 13, 2011 6:49 pm
Yes, my co worker says that the requests and responses from iterartion 1 and 2 are exactly the same - although I have not confirmed thaton personally. I've seen you on sqaorums.com. The ''clincher'' is that when the a different administrative user logs in -- he can run the same script without this issue. Let's say a company has a single sign on portal, and after signing in a cookie is set so that after he signs in the cookie is used for authenticating him to submit his second transaction. QUESTION: should the web_set_cookie be deleted, parameterized, or???
( at March 13, 2011 8:08 pm)
I usually comment out the web_set_cookie functions that are recorded into the script. I would try a few things to see if they help: 1) comment out the web_set_cookie statements and see if LR can handle the cookies on the fly behind the scene 2) try inserting a web_set_user statement in the vuser_init section of the script (check the function reference for syntax). 3) if the above two fail, parameterize the data in web_set_cookie (without seeing the code/statement I cannot say if this will be helpful or not).
( at March 14, 2011 5:39 pm)