...
Open the Grouping Criteria dialog (e.g., by clicking Add or Duplicate, or by double-clicking) an existing grouping criteria entry.
If desired, customize the name of the responder/test client and/or data set that will be generated.
Conditional Content Product: (SOAVirt, Virtualize) Product: (SOAVirt, Virtualize) sv-attr:0A010204015A9054C88481D043445E2F 0A010204015CF6008A11EEF43AC91334 0A010204015A9054C88802B9600247DF In the Grouping Criteria tab, modify the grouping criteria as desired. Each grouping criteria entry can specify grouping by any combination of the following: HTTP Methods, URL Paths, URL Parameters, and/or Request Body.
Grouping Strategy Description HTTP Methods Grouping Configuration Virtualize: Specifies HTTP methods that will determine whether or not the message is processed.
SOAtest: Groups messages by HTTP methods. Customization of HTTP methods grouping criteria is automatically disabled to prevent the creation of groups with mixed methods (e.g., both POST and GET).
URL Paths Grouping Configuration Virtualize: Specifies URL paths that will determine whether or not the message is processed.
SOAtest: Groups messages by URL paths.
URL Parameters Grouping Configuration Virtualize: Specifies URL parameters that will determine whether or not the message is processed. You can configure the correlation to match all messages that include specific parameters (no matter what value they are set to), or only match messages where specific parameters are set to specific values. You can also indicate whether a correlation should be applied if the request has the exact URL parameters present—no more and no less.
SOAtest: Groups messages by URL parameters that will determine whether or not the message is processed. You can configure the criteria to include all messages that include specific parameters (no matter what value they are set to), or only include messages where specific parameters are set to specific values. You can also indicate whether a message should be included if the request has the exact URL parameters present—no more and no less.
Request Body Grouping Configuration Virtualize: Specifies XPaths within the message that will determine whether or not the message is processed.
SOAtest: Groups messages using XPaths.
To see the details of the detected messages, open the Message Details tab and select the related message block.
...
HTTP methods grouping criteria apply to assets that will be accessed over HTTP/HTTPS.
...
...
To configure the HTTP methods correlation:
- Select the Enable correlation check box.
- Specify the HTTP methods you want to use for correlation.
For example, if GET, POST, and PUT are checked, the responder will match HTTP requests with the method GET, POST, or PUT. HTTP requests with CONNECT, DELETE, HEAD, etc. will not match.
URL Paths Grouping Configuration
Anchor | ||||
---|---|---|---|---|
|
...
- Enable the Enable correlation or Use for grouping option.
- If you want the correlation or grouping to be applied only if the request has the exact URL parameters specified in this table—no more and no less—enable the Correlate only when the list of parameters matches exactly or Include only when the list of parameters matches exactly option. Otherwise, any request that contains listed parameters as well as other parameters will match. Whether this option is enabled or disabled, a message that lacks one of the specified parameters will not match.
- Click the Add button. A new entry row displays.
- Enter the Parameter Name.
- Do one of the following:
- If you want to match messages where this parameters is set a specific value: Enter that value under Value.
- If you want to match all messages that include this parameter (no matter what value they are set to): Enable Correlate whenever the parameter name is present (regardless of value) or Include in group whenever the parameter name is present (regardless of value).
...
Virtualize Example
For an asset deployed under the path http://myserver:9080/MyAsset/MyPath,
the following URL Parameters are specified in a responder:
Parameter Name | Value |
---|---|
param1 | value1 |
param2 | value2 |
...
The following request URLs will match this correlation or grouping criteria:
...