Example Filter Business Service Script To Customize SOAP Message/Envelope
(Doc ID 1324943.1)
Last updated on AUGUST 26, 2024
Applies to:
Siebel CRM - Version 8.0.0.3 [20416] and laterSiebel CRM Call Center - Version 8.0.0.3 [20416] and later
Information in this document applies to any platform.
Goal
Siebel is integrated with .NET application in real time using Outbound Web Services.
The .NET service WSDL was imported into Siebel and a Filter Business Service was written to add custom soap headers.
Requests can be successfully posted from Siebel except for the fact that .Net system expects the <soap:Envelope> instead of <SOAP-ENV:Envelope>.
<SOAP-ENV:Envelope> is the default one that Siebel generates and uses.
SOAP request expected by .NET :
<soap:Header>
...
</soap:Header>
<soap:Body>
...
</soap:Body>
</soap:Envelope>
SOAP request generated by Siebel :
<soap:Header>
...
</soap:Header>
<SOAP-ENV:Body>
...
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
How to modify the soap request message that Siebel sends out to conform to what the external system expects?
Solution
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
Goal |
Solution |
References |