This topic explains how to manually add and configure Message Responders.
Sections include:
| Table of Contents |
|---|
Overview
If you want to virtualize a service that is not available and is not described by a WSDL or schema, you can virtualize it by manually adding Message Responders that represent the related behavior. In this section:
| Table of Contents | ||
|---|---|---|
|
Adding a Message Responder
To add Message Responders manually:
...
A project contains one ore more Parasoft Virtual Asset files (.pva). These files contain one or more Responder Suites, which contain one or more Message Responders. Before you can manually add a Message Responder, you must build out this structure. See Adding Projects, Virtual Assets, and Responder Suites for details.
- Add a Message Responder tool to the .pva file.See Right-click on a Responder Suite and choose Add New> Responder. You can also click the Add Responder or Output button in the toolbar (see Adding Responders, Output Tools, and Validations for details.).
- Choose a type of Message Responder and click Finish. See Virtualization Tools for details about the Message Responders in Virtualize.
- Configure the Message Responder in In the tool configuration panel, configure the Message Responder. See Message Responder Overview for details. Note that the Response tab’s You can customize the Form Input controls can be tailored to under the Response tab to either SOAP messages or plain XML messages.
Tips:
- Use multiple response mode
- Select Always match under XPath function, and clear Always match under HTTP URL Parameters. This will allow the response message we are configuring to be correlated to values that come in the URL parameters (instead of values in an XML request).
- Enable always match xpath, clear always match http url. This will allow the response message we are configuring to be correlated to values that come in the URL parameters (instead of values in an XML request). add a parameter under http url parameters
Deploying the Virtual Assets
| Excerpt |
|---|
If the .pva is created directly in the VirtualAssets project, it will be deployed automatically. Otherwise, the simplest way to deploy the virtual asset is to copy the containing .pva file into the VirtualAssets project. Alternatively, you could right-click the Virtualize Server view’s Local machine node, choose Add Virtual Asset, specify the .pva file that includes the virtual assets you want to deploy, then click Finish. When the wizard completes, Virtualize will automatically copy the .pva file to the VirtualAssets project. For a more detailed discussion of deployment procedures and options, see Deploying Virtual Assets Virtualize. |
Customizing the Virtual Assets
...