...
The following URLs will match this correlation criteria:
http://myserver:9080/MyAsset/MyPath/segment1/segment2
http://myserver:9080/MyAsset/MyPath/segment1/segment2/
http://myserver:9080/MyAsset/MyPath/segment1/segment2/segment3?param1=value1&m2=value2
The following URLs will NOT match:
http://myserver:9080/MyAsset/MyPath/segment1/
http://myserver:9080/MyAsset/MyPath/segment3/segment1/segment2
Ant-style wildcards can be used, where * matches one or more characters and ** matches one or more directories. Using this format:
/**/abc matches /abc or /this/that/abc
/abc/** matches /abc or /abc/this/that/theother
...
- Enable Enable correlation or Use for grouping.
- 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 Correlate only when the list of parameters matches exactly or Include only when the list of parameters matches exactly. 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 Add. A new entry row appears.
- Enter the Parameter Name.
- Do one of the following:
- If you want to match messages where this parameter 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 in group whenever the parameter name is present (regardless of value).
SOAtest Example
For an endpoint of http://myserver:9080/MyAsset/MyPath, the following URL Parameters are specified in the grouping criteria:
...
- Enable Enable correlation or Use for grouping.
- Click Edit. An Edit XPath Function dialog opens.
- Do one of the following:
- Choose an element from the Element tree and select a function from the Function dropdown menu. Use this option if a tree representation of the incoming request message is displayed.
Provide an XPath expression manually. Use this option if a tree representation is not available or if the tree does not fully display interesting elements or attributes for extraction and evaluation. The XPath expressions supported for correlation/grouping purposes is based on the standard XPath 1.0 standard by W3C.
Note that several categories of requests are shown in the left hand panel:
- Archetypal Requests: A selection of messages that represent the different message structure variations that were detected when analyzing the traffic file.
- Messages in this Group: Messages from the message group whose grouping criteria you are currently configuring. This is not available if the group doesn’t have any messages.
- All Messages: All the messages from the traffic file.
...