How to Pass Custom SOAP Headers Using 'HeaderContext' Property Set to the Actual Workflow Exposed as Inbound Web service?
(Doc ID 1325659.1)
Last updated on JUNE 17, 2019
Applies to:Siebel Public Sector Call Center - Version 126.96.36.199 SIA  and later
Information in this document applies to any platform.
How to pass custom soap headers using 'HeaderContext' Property Set to the actual workflow (or business service) exposed as Inbound Web service?
The Bookshelf content that says this is possible is EAI Vol 2 > Web Services > About Custom SOAP Filters > Inputting a SOAP Envelope to a Filter Service :-
" To pass the information in the headers further down the stack to the actual business service method or workflow being invoked the HeaderContext property set is passed to the business service or
workflow that is invoked. For example, on a call to an inbound Web Service, if there are a couple of headers in the SOAP message, the filter service extracts the header information. In order to use it in the business service or workflow execution call, this information has to be contained in the HeaderContext. Internally, the Siebel Web Services infrastructure passes HeaderContext to the eventual business service or workflow that is invoked."
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document