|Bookshelf Home | Contents | Index | PDF|
SOAP headers provide the option of providing optional or mandatory processing information. To process optional custom headers that are provided by external applications, a special business service known as a filter might be defined. Filters can process both request and response headers. A special attribute, mustUnderstand, is used to indicate whether or not the custom header is to be processed:
You must keep SOAP body and header processing isolated. The inbound dispatcher and outbound proxy can process the SOAP body, but cannot set or consume headers. Headers are application-specific. Some customization is needed to set and consume custom headers. To process optional custom headers that are provided by external applications, a special business service, a filter, is defined. You can configure the Web service outbound proxy and the Web service inbound dispatcher to call specific filters for the processing of individual (custom) headers.
NOTE: The SOAP header will not be passed to the underlying business service or workflow of the inbound Web service. Any processing that must be done with the SOAP header must be done on the filter business service.
|Integration Platform Technologies: Siebel Enterprise Application Integration||Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.|