Using Data Protocols

Using CA Service Virtualization › Using the Workstation and Console with CA Service Virtualization › Creating Service Images › Using Data Protocols

Using Data Protocols

A data protocol is also known as a data handler or a data protocol handler. A data protocol is responsible for parsing requests. Some transport protocols allow (or require) a data protocol to which the job of creating requests is delegated. As a result, the data protocol has to know the payload of the request. One transport protocol can have many data protocols. Some transport protocols (for example, JDBC) do not allow a data protocol.

During recording, all transport protocols try to detect the request or response payload and default appropriate data protocols on either the request or response side. The indicated data protocol handlers are added for the following payloads:

SOAP: Web Services (SOAP) data protocol handler
XML: XML data protocol handler
HTML: No data protocol handler
Signed SOAP: A request-side WS-Security Request and a response-side WS-Security Response data protocol handler
Encrypted SOAP: A request-side WS-Security Request and a response-side WS-Security Response data protocol handler
SOAP Security: A request-side WS-Security Request and a response-side WS-Security Response data protocol handler

You can add more data protocols, reorder the defaulted ones, or delete the defaults. If you are creating a service image from request/response pairs, a raw traffic file, or means other than recording and you have specified data protocol handlers, the defaults are not added.

You can chain data protocol data handlers to work with each other. For example, on the request side, you can use the Delimited Text data protocol, the Generic XML Payload Parser, and the Request Data Manager together.

Each available data protocol is described in the following sections.

Auto Hash Transaction Discovery

EDI X12 Data Protocol

Generic XML Payload Parser Data Protocol

JSON Data Protocol

Request Data Copier Data Protocol