Example Filter Business service script to customize SOAP Message/Envelope (Doc ID 1324943.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel CRM Call Center - Version 8.0.0.3 [20416] and later
Siebel CRM - 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 web services. The .NET service WSDL was imported in Siebel and a filter BS was written to add custom soap headers.

Request can be successfully posted from Siebel except otherwise for the fact that .Net system expects the <soap:Envelope>  instead of <SOAP-ENV:Envelope> , which was being, by default sent by Siebel.

SOAP response expected by .NET :-

<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
...
</soap:Header>
<soap:Body>
...
</soap:Body>
</soap:Envelope>


SOAP response generated by Siebel :-

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
...
</soap:Header>
<SOAP-ENV:Body>
...
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>


How to send the expected SOAP response from siebel?

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