Using CA Service Virtualization › Using the Workstation and Console with CA Service Virtualization › Creating Service Images › Using Data Protocols › Web Services (SOAP Headers)

Web Services (SOAP Headers)

The SOAP Headers data protocol converts elements from the header of a SOAP message into arguments for requests in a virtual service image. This data protocol is compatible with any transport protocol that generates SOAP messages (typically HTTP/S).

To use the SOAP Headers data protocol, generate a VS Image either by recording or from request/response pairs. You typically use the HTTP/S transport protocol. Add the SOAP Headers data protocol as a Request Side data protocol. This data protocol does not require any extra configuration.

This data protocol can be used with the SOAP data protocol to process both SOAP headers and the SOAP body.

Arguments are named based on the structure of the XML.

Example

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>username</wsse:Username>
<wsse:Password>password</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<n1:ServiceControl xmlns:n1="http://localhost:8080/examples.xsd">
<n1:VersionID>2.0</n1:VersionID>
<n1:Asynchronous>
<n1:ReplyRequiredIndicator>false</n1:ReplyRequiredIndicator>
<n1:PassThroughData>
<n1:Key>InteractionID</n1:Key>
<n1:Value>444831</n1:Value>
</n1:PassThroughData>
</n1:Asynchronous>
</n1:ServiceControl>
</soapenv:Header>
...

This example would be parsed into elements that are named as follows:

• Security_UsernameToken_Username
• Security_UsernameToken_Password
• ServiceControl_VersionID
• ServiceControl_Asynchronous_ReplyRequiredIndicator
• ServiceControl_Asynchronous_PassThroughData_Key
• ServiceControl_Asynchronous_PassThroughData_Value

Duplicate elements are named with _1, _2, and so on, appended to the name.