...

• Logs produced by Virtualize message proxies or recording proxies (e.g.for example, for JMS, MQ, HTTP).
• Logs produced from other sources; , for example:
  • Message traces or logs captured at the network level using network sniffing tools.
  • HTTP logs obtained by having your application log its traffic.

...

Virtualize also expects there to be two line endings (Windows or Unix) between a message body and the and the next HTTP header.

This format is similar to what would be captured by the Virtualize message proxy, recording wizard, or other HTTP traffic sniffing tools that can record HTTP traffic as it gets transmitted over the HTTP socket connection. HTTP chunking and traffic files that are recorded with chunked traffic are supported. However, raw HTTP traffic files that include chunked messages or "continue" headers are not supported. 

Values can be encoded or decoded. For instance, if a request comes in at path /some/url?q=harrystar+potterwars, this should correlate the same as /some/url?q=harry%20potterstar%20wars, even if the "q" URL Parameter Correlation is set to 'harry potterstar wars'. If you are using encoded values and data source correlations, see the notes for Data Source Correlation Tab.

...

• Generate parameterized messages creates Message Responders that are automatically parameterized with values from a Parasoft Data Repository (which is also automatically created when you use this option). This option allows you to rapidly add and modify response message values using a graphical interface designed for manipulating large, complex data sources. Data values are stored and manipulated independently of the Message Responder and .pva. This process is described in Creating Fixed Parameterized Message Responders from Traffic.
• Generate fixed messages creates Message Responders that specify each response literally via Multiple Response format. All response message data is stored and manipulated within the Message Responder. Response message elements can be parameterized with data extracted from incoming messages. This process is described in  in Creating Fixed Message Responders from Traffic.

...

To understand the difference, consider the following example from a simple HTTP traffic file with 9 messages, including 3 three messages for the getItemByTitle operation. 

Parameterized Messages

With "generate parameterized messages," Virtualize configures the Message Responder’s getItemByTitle responses as follows.

Additionally, it creates the following editable and extensible Data Repository.

...

With "generate fixed messages," Virtualize configures the Message Responder’s getItemByTitle responses as follows.