WSDL files include information about how to encode SOAP request and response messages. SOAP encoding determines the format of the SOAP message body. Web service developers can use a variety of toolkits to create web services. Different toolkits support different ways of encoding SOAP messages.

PowerExchange for Web Services supports the following SOAP encoding styles:

You can import web service operations that support RPC/encoded or document/literal encoding styles. The WSDL use attribute is defined in the SOAP body. The use attribute value is either encoded or literal.

When the use is encoded, the WSDL must have a type attribute in the message part.

<message name="SystemNotAvailableException">
  <part 
type="ns3:SystemNotAvailableException" name="SystemNotAvailableException">
  </part>

When the use is literal, the WSDL must have an element attribute in the message part.

<message name="hypostoresPreferencesService_getAlertsProfile">
    <part name="getAlertsProfile" 
element="tns:getAlertsProfile">
    </part>

You can view the SOAP encoding style of the web service operation when you edit a web service source definition, a web service target definition, or a Web Services Consumer transformation.