This topic provides details on completing the Request Matching wizard screen when generating parameterized messages from traffic using the wizard. In this topic:
| Table of Contents | ||
|---|---|---|
|
Introduction
This screen enables you to specify the following settings:
...
page in the "Generate Parameterized Messages from Traffic" wizard. This page allows you to remap the request/response pairs, customize which parameter values are used to determine
...
the response messages
...
of the virtual asset
...
, and specify the WSDL or schema associated with this message.
Sections include:
| Table of Contents | ||
|---|---|---|
|
Remapping
...
The Request Matching screen appears when the Autoconfig option is disabled in Message Grouping Review screen of the traffic wizard.
The Autoconfig option may be disabled if Virtualize is unable to automatically determine message grouping or correlations.
The wizard will present a page for each message group that you want to manually configure.
Request/Response Pairs
You can remap the request/response pairs by clicking on a connecting line and dragging its and dragging the endpoint to a different request or response. For example, if response 3 actually correlates to request 2, you would indicate this as follows:
...
To view message details, select the related message block.
Request Correlation
You can configure the responder mode and specify custom correlations based on request body, URL paths, and request headers in the Request Correlation tab.
Initial Correlations
Virtualize automatically configures initial correlations based on the traffic file, template file, and/or service definition file according to the following scenarios.
...
Customizing Correlations
If you want to customize which parameter values are used to determine the response messages of the virtual asset, disable the Autoconfig option and configure the correlation options in the Request Correlation tab in the Request Matching screen of the wizard pages. The wizard will present a page for each message group. The Request Correlation tab automatically populates the following correlations (if applicable) and allows you to customize the initial correlations:
The Parameterized responses responder mode must be enabled to configure the data source correlations in the Request Matching screen (see Configuring the Default Responder Mode).
If you did not specify a template, the page’s initial state shows the data source correlations that were automatically-generated from the current traffic file. If you specified a template, the page’s initial state shows the data source correlations defined in the template. In this case, data source correlations won’t be automatically-generated from the current traffic file
...
.
Understanding How Correlations are Used
...
| Parameterized responses | This option enables you to configure the data source correlations in the Request Matching screen. The generated responder will be parameterized with values from a data repository. |
|---|---|
| Sequence responses | This option generates a responder in sequence responses mode. See Sequence Responses for additional information. |
| Single response | This option selects a single message pair from the message group and generates the responder in Literal mode. See Literal View Options_SOA. |
Modifying the Initial Correlations
You can modify the initial correlations that were automatically-configured configurations using the controls available in the various correlation sections. If you've modified any of the configurations, you can click the Restore Default button discard changes and restore the initial, automatically-configured settings. The Parameterized Responses responder mode must be enabled to configure the data source correlations (see Configuring the Responder Mode).
If you specify the same column name multiple times (e.g., in URL Parameters and URL Paths), only one value will be set; the previous value(s) will be overwritten.
Request Body Correlations
| Anchor | ||||
|---|---|---|---|---|
|
Virtualize will generate a "name"-based XPath for each operation/group; this will be used to set the Responder Correlation for that operation. For example, if the element name under the SOAP Body is "SubmitOrder", then the XPath expression set to the responder correlation section would resemble the following:
...
| Info | ||||
|---|---|---|---|---|
| ||||
Sometimes it’s desirable to ignore certain values (such as timestamps) for matching purposes. Virtualize is automatically configured to ignore timestamps—based on the following regular expression:
If you want to review, modify, or add exclusions, click the Exclusions button at the bottom of the page, then edit the values in the table. Element names are specified as exact matches or using a wildcard (*) to match everything. Values are specified as regular expressions.
If you always want to ignore certain values for matching purposes, you can enter them once in the Preferences> Parasoft> Traffic File Processing area, and have them applied every time that a parameterized virtual asset is created from traffic. See Traffic File Processing Settings for details. |
Request URL Parameter Correlations
| Anchor | ||||
|---|---|---|---|---|
|
For request URL parameters, if there is any difference in the URL parameters in the invocations belonging to a message group, such as a different number of parameters, different parameters (names), or different parameter values, then Virtualize’s auto-configuration from traffic will automatically configure correlations based on those differences.
...
If you want to override the initial configuration shown in the wizard page, use the available controls to specify the parameter(s) and column name(s) that you want to use.
Request URL Path Correlations
| Anchor | ||||
|---|---|---|---|---|
|
For URL path, if there is any difference in the URL paths in the invocations belonging to a group, then Virtualize’s auto-configuration from traffic will configure correlations based on those differences.
...
If you want to override the initial configuration shown in the wizard page use the available controls to specify which path segment to use for correlations. Path segments can be matched with one or more data source column name, then be parameterized with various data source columns. In the dialog that opens, specify the path segment you want to use (you can click the related path segment or enter the desired path index), then specify a name for the data source column.
Request Header Correlations
Request header correlations are not added during Virtualize’s auto-configuration from traffic. If you want to correlate based on header values, provide the headers for the request values you want to extract and match, then map each to a data source column. The extracted values will be matched with values from the mapped data source columns.
Specifying a
...
WSDL or Schema
If you want to provide a WSDL or Schema for this traffic, enter it in the WSDL/Schema tab. Advantages of specifying the WSDL or schema include:
- The generated Form Input model will be based on that WSDL/Schema, which provides type richness when you are editing and maintaining the resulting Form Input.
- Change Advisor (described in Change Management Virtualize) is available to help you keep your assets in sync with evolving services and changing environment conditions.
...