Srihari,
Looks like you have the correlation done wrong.
Let me see if I can explain how it works:
1. Client goes to a page
2. Server responds with a HTTP response, including a dynamic value
3. Client request then uses the dynamic value it got from step 2 in this request as an authentication
4. Server always checks if the value recieved from step 3 from the client matches the value server sent out in step 2.
So when you record, all you are seeing is the step 3, and thats why the two scripts have different values.
The web_reg_save_param works by instructing VUGEN to save as a parameter, the specific value returned by server in step2. Note that VUGEN is recording requests and not responses, hence, your vugen script should have the web_reg_save_param just before the step1.
In the correlation you are attempting, you are trying to correlate step 3, which is why it fails.
What you should be doing is identifying in both the scripts, where the value is returned from the server in step 2. To do this use the generation log and search for the dynamic value. the first time you see this value should be in a response from the server. The request for this page should then be correlated by including the web_reg_save_param BEFORE the request.
Hope this helps.
Regards,
AJ
