A request/response pair consists of one request file and one or more response files.
When you import a request/response pair, the request is processed against the virtual service.
If the virtual service contains a signature with the same arguments, a specific transaction is added to the signature.
If the virtual service does not contain a signature with the same arguments, a signature is added. The details of the request and response are added as a specific transaction in the signature. A default transaction is also added.
The request/response pair must be in text or XML format.
The following list contains an example of the file names in a request/response pair:
The request file name must include a prefix followed by the string -req.
The response file name must include the same prefix followed by the string -rsp. As the preceding example shows, you can provide multiple response files by adding a number after the string -rsp. Multiple response files are applicable to messaging scenarios.
You can specify request and response metadata by including one or more sidecar files. For more information, see Sidecar Files with Request/Response Pairs.
Note: If the virtual service is based on a transport protocol other than HTTP, this feature has the following prerequisite: Open the corresponding virtual service model in DevTest Workstation and enter the path to the recording session file in the Documentation field. A recording session file is one of the following files:
Generated by the Virtual Service Image Recorder in DevTest Workstation.
Generated by the CA Service Virtualization Recorder in the DevTest Portal.
Follow these steps:
The Import Request/Response Pairs dialog opens.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|