A web application can use dynamic parameters to store session or user-related data, for example, a session ID or a user ID. A client gets the parameters from the server and then uses them in subsequent requests to access the needed server resources.
Such parameters usually change between application sessions. For a recorded scenario to run successfully, during the run, it must catch the actual dynamic parameters the server returns, and use them in requests rather than reuse the recorded values. The procedure of extracting actual data from server responses and inserting them to appropriate subsequent requests is called data correlation.
In LoadComplete, you can create data correlation rules that define how LoadComplete searches for dynamic parameters in server responses, extracts them from the responses and inserts them into subsequent requests.
By default, LoadComplete has a number of data correlation rules defined for common dynamic parameters that the most widespread web frameworks use –
-
.NET
-
JSF
-
Java
-
ADF
-
E-Business
-
GWT
-
ICEFaces
-
Lightstreamer
-
RTMPT
-
Siebel
-
Silverlight
-
WebSync
| Note: | LoadComplete applies the rules regardless of the framework, on which the web application is built. |
You can view the full list of supported dynamic parameters in the Recording | Data Correlation Options dialog.
You can also create custom correlation rules. See Creating Custom Data Correlation Rules Manually.