I am trying to record the script for ADF framework (by Oracle) using Loadrunner 9.5 version and facing some issues in completing the script. I have correlated almost all the dynamic values and still not working as recorded.
I have analyzed and correlated the below mentioned 5 dynamic values:
JsessionId ADF Control state ViewState Afr Loop ID WindowID.
I think there are some more activities or java scripts which is executing internally and I think those activities are not recorded by LR.
Sometimes the recorded and the replayed snapshots are not same and eventually the response is also not same. This situation is arosed when we navigate to second page which is a pop-up where some updation is happening.
I think LR is not recording the internal activity from navigating the pages, the script is getting failed.
Application is a Java based, built on ADF frame work which is driven by Weblogic server.
If some one have solution or idea, please help me as the project is in a critical stage to complete it.
P.S. This thread has been moved from Performance Center Support and News Forum to LoadRunner Support Forum. -HP Forum Moderator
I tried recording Oracle ADF11g application using LR11.0,But after doing correlation of above mentioned 5 parameters we are not able to replay it correctly.
I need to verify that does LR11.0 supports Flex 4.5 (spark) or not but i'm not able to reach to that step during replay as we are gettig error message.
Attaching my recorded script (action.doc)
And Error file (Replay log.doc)
The error we are getting is "Error -26377: No match found for the requested parameter "STATETOKEN61". Check whether the requested boundaries exist in the response data. Also, if the data you want to save exceeds 1024 bytes, use web_set_max_html_param_len to increase the parameter size " in adf.login.success.
But it can be clearly seen that statetoken61 parameter is used in the custom request. but LR is not able to pick that up while replaying.Moreover we have increased the size to 1000000 but no joy!!!!
I feel that there are few more parameters in oracle ADF11g which is not intercepted by LR11.0 while recording which is causing the failure while replay.