When using RESTful XML
SAS BI Web Services endpoints, all types of input and output are supported.
You should send XML requests using the same format as for SOAP messages.
Always omit SOAP elements from requests to the RESTful XML endpoints,
and you can also omit namespaces.
SOAP Message Versus Plain XML Message
|
|
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:biw="http://www.sas.com/xml/namespace/biwebservices">
<soapenv:Header/>
<soapenv:Body>
<biw:addfloats>
<biw:parameters>
<biw:num1>2.3</biw:num1>
<biw:num2>4.2</biw:num2>
</biw:parameters>
</biw:addfloats>
</soapenv:Body>
</soapenv:Envelope>
|
<addfloats>
<parameters>
<num1>2.3</num1>
<num2>4.2</num2>
</parameters>
</addfloats>
|
The other difference
between SOAP and plain XML messages is how binary content is handled.
Data sources, data targets, and packages can all contain binary data.
SOAP endpoints use WS-* standards to handle binary content. Specifically,
SOAP can use attachments to include the binary content out-of-band
of the SOAP envelope (but still within the same HTTP request or response)
using multi-part responses. Plain XML messages contain Base64-encoded
data inline in the XML request or response. This is less efficient
than SOAP attachments because serializing the binary content to Base64
takes extra processing time and also bloats the size of the binary
data compared to its original size. Therefore, avoid using plain XML
messages when using multiple large binary resources.
If you need to retrieve
only a single output resource (binary or otherwise), you can access
the specific output resource that you need by using the appropriate
resource suffix on your Web service endpoint URL. When accessing a
single binary output resource with resource suffixes, the binary data
is not transcoded to Base64 data.
See Accessing RESTful JSON and XML Web Service Endpoints for more information about how to access these resources
using suffixes.