Page History

...

Form Input, Form XML, Literal, Multiple Response, Scripted, and Form JSON Views

These views are similar across multiple Parasoft tools; they are The input interface for each mode is described in the following areas:

• Form Input View Options
• Form XML View Options
• Literal View Options
• Scripted View Options

• Multiple Responses View Options

• Form JSON View Options
• Form ISO 8583 View Options

Notes

...

Form-based views allow you to build the response and parameterize values from a data source.

If an operation selector is enabled in the Form Input or Form JSON view, you can use it to select the operation for your response. When you select an operation, the Form Input/JSON view will be populated with appropriate values and UI controls (e.g., radio buttons for

...

Booleans, different controls for numbers vs. integers, etc.).

In Form Input mode, the operation selector will show all operations for which the associated service definition 1) defines the response as XML and 2) specifies an XML schema.

In Form JSON mode, the operation selector will show all operations for which the associated service definition 1) defines the response as JSON and 2) specifies a JSON schema.

Image Modified

In Multiple Responses mode, each possible response has its own correlation to the incoming request, static response message, and performance (time) options.

...

Transport Header Tab

The Transport Header tab allows you to specify the HTTP, JMS, or MQ message header that will be returned with the response message. You can use table view or literal view.

...

For JMS, you can define any miscellaneous property values to be set into the javax.jms.Message object before it gets sent to a queue or published to a topic. For instance, you could define JMSPriority, JMSDeliveryMode, JMSExpiration, and other properties as follows:

Image Modified

Responder Correlation Tab

Anchor
Responder Correlation Tab Responder Correlation Tab

The Responder Correlation tab allows you to specify which messages this Message Responder the tool accepts and processes. Various messages Messages sent to the virtual asset URL are routed to specific Message Responder tools (, each of which handle different operations) , based on the Responder Correlation settings here. For example, one Message Responder tool might may respond to customer registration messages, another might respond to payment messages, and another might may function as a default "catch all" that is used when none of the others match. 

...

You can configure one type of correlation, multiple types of correlation, or no correlations. If no correlations are configured, everything in the message will be processed. 

Transport Correlation

To configure a transport correlation:

1. Select the Enable correlation check box.
2. Click the Add button. A new entry row displays.
3. Enter the Header Name.
4. Do one of the following:
   • If you want to match messages where this header is set a specific value: Enter that value under Value of Header.
   • If you want to match all messages that include this header (no matter what value it is set to): Check Correlate whenever the named header is present regardless of value.

Anchor
requestBodyCorrelation requestBodyCorrelation

Request Body Correlation

To configure a request body correlation:Request body correlations are based on XPath values. 

1. Select the Enable correlation check box.
2. Click the Edit button. An Edit XPath Function dialog displays.
3. Select an element from the Element tree, select a function from the Function drop-down menu, and click OK.
4. Do one of the following:
   • If a tree representation of the incoming request message is displayed, then select an element from the tree and select a function from the Function drop-down menu.
   • If a tree representation of the requests is not available—or if the tree does not fully display the elements or attributes that are of interest for extraction and evaluation—then provide an XPath expression manually. The XPath expressions supported by Virtualize for correlation purposes is based on the standard XPath 1.0 standard by W3C.
5. If you want to specify any additional XPaths, add them in the same manner.

...

URL parameter correlations apply to virtual assets that will be accessed over HTTP/HTTPS.

To configure a URL parameter correlation:

1. Select the Enable correlation check box.
2. If you want the correlation to be applied only if the request has the exact URL parameters specified in this table—no more and no less—check the Correlate only when the list of parameters matches exactly. Otherwise, any request that contains listed parameters as well as other parameters will correlate. Whether this option is enabled or disabled, a message that lacks one of the specified parameters will not match.
   
   Image Modified
   
   
3. Click the Add button. A new entry row displays.
4. Enter the Parameter Name.
5. 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 it is set to): Check Correlate whenever the parameter name is present regardlessof value. 
     
     

...

URL path correlations apply to virtual assets that will be accessed over HTTP/HTTPS.

This Note that the matching strategy has changed since Virtualize 9.7; existing virtual assets will automatically be reconfigured to use the current paradigm when they are modified. 

...

1. Select the Enable correlation check box.
2. Specify the HTTP methods you want to use for correlation.
   
   Image Modified
   
   

For example, if GET, POST, and PUT are checked, the responder will match HTTP requests with the method GET, POST, or PUT.  HTTP requests with CONNECT, DELETE, HEAD, etc. will not match. 

...