This topic explains how to virtualize traffic that is captured in traffic logs.
Sections include:
| Table of Contents | ||
|---|---|---|
|
Introduction
Virtualize can virtualize simulate application behavior that is captured in traffic logs—including:
...
logs, such as logs produced by Virtualize message proxies or recording proxies (e.g., for JMS, MQ, HTTP).
...
Virtualize can also simulate behavior captured in traffic logs produced from message traces, logs captured at the network level using network sniffing tools
...
, and from HTTP traffic logs
...
created by
...
the application
...
This "virtualization" is achieved by using a . Specify the log file describing the behavior you want to virtualize in the wizard to create and deploy Message Responders within a virtual asset.
...
Values can be encoded or decoded. For instance, if a request comes in at path /some/url?q=harry+potter, this should correlate the same as /some/url?q=harry%20potter, even if the "q" URL Parameter Correlation is set to 'harry potter'. If you are using encoded values and data source correlations, see the notes for Data Source Correlation Tab.
Virtualize treats body content sent in form URL encoded POST requests as URL parameters, rather than putting them into the request body. This enables greater flexibility to create correlations based on individual parameters.
JMS and MQ Traffic Logs
Virtualize supports the creation of .pvas from JMS and MQ traffic files produced by Virtualize message proxies and the traffic recording wizard.
...
With "generate parameterized messages," Virtualize configures the Message Responder’s getItemByTitle responses as follows.
Additionally, it creates the following editable and extensible Data Repository.
Fixed Messages
With "generate fixed messages," Virtualize configures the Message Responder’s getItemByTitle responses as follows.
| Scroll pdf ignore |
|---|
Video Tutorial: Creating Virtual Assets from Sample Request/Response PairsIn this video you'll learn how to create a virtual asset from a sample piece of XML. |
...
|
...
|
...
|
...
|
...
|