How to define Siebel CRM specific service fields (Fault, Header) in .WSDL, generated for a Siebel Inbound Web Service?

(Doc ID 1234516.1)

Last updated on OCTOBER 11, 2017

Applies to:

Siebel CRM - Version 7.5.2 [15051] and later
Information in this document applies to any platform.

Goal

An external application, that consumes WSDL file, generated by Siebel CRM for an Inbound Web Service,  may need  to know details (schema) about Siebel CRM standard fields, appearing in SOAP message (request or response).

Siebel Web Services Framework use at run-time some standard fields in SOAP Header and SOAP Fault parts of SOAP message. Such definitions are not produced by WSDL Generator of Siebel User Interface (design-time).

This documents provides some usage examples, how scheme for some standard Siebel fields could be explicitly included in .WSDL file, after it has generated.

WARNING:  XSD/WSDL code examples, given in this document, are provided just FOR ILLUSTRATION purpose.
Please notice, WSDLs can, but are not expected to describe a specific header in details as mentioned at  https://www.w3.org/TR/wsdl#_soap:header "It is not necessary to exhaustively list all headers that appear in the SOAP Envelope using soap:header."
And in fact, many applications are unable to make sense of header details included in a WSDL.
That is because applications should be using WS-Policy to choose which headers to add to their SOAP requests.
Both sides should be able to change the policy (the headers) without a need for a new WSDL to describe the new header.
In any case, the document below offers one possible way to explicitly describe headers in a WSDL.

References:

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms