Using CA Service Virtualization › Using the DevTest Portal with CA Service Virtualization › Editing Virtual Services › Find the Transactions that Match a Request

Find the Transactions that Match a Request

Assume that when you send a request to a virtual service, the response is not what you expect.

You can open the virtual service and then enter the request. The DevTest Portal indicates which components in the virtual service are a match for the request. The results can help you determine how to fix the problem.

The request must be in text or XML format.

The DevTest Portal lets you enter the actual contents of the request, or specify a request file. The request file name must include a prefix followed by the string -req (for example, depositMoney-req.txt).

If the results include stateless signatures or stateless specific transactions, the order in which they appear is the same order in which they are matched during playback.

The order of conversational results is not significant.

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:

VRS file

Generated by the Virtual Service Image Recorder in DevTest Workstation.

VR2 file

Generated by the CA Service Virtualization Recorder in the DevTest Portal.

Follow these steps:

1. Open a virtual service.
2. Click Find a Match by Request.
3. Do one of the following actions:
   • Paste the request into the text area.
   • Drag the request file into the dialog.
   • Click Select Request File and select the request file from a file system.
4. Click Find a Match.

   The Search Results table displays any matches that are found.

5. To display the original request, click View Request.
6. Click an entry in the Search Results table.

   The matching component is displayed.