My Oracle Support Banner

Upgrade from 7.5: content of generated WSDL and format of SOAP payload, used in Siebel 7.5 for document/literal binding is CHANGED in newest Siebel releases (7.7 and onwards) (Doc ID 480372.1)

Last updated on DECEMBER 19, 2019

Applies to:

Siebel System Software - Version 7.7 [18104] BETA and later
Generic (Platform Independent)

Symptoms

Format of SOAP Payload of "document" SOAP-binding style, accepted by Siebel Web Services Framework at run-time and described in generated WSDL file, HAS BEEN CHANGED from Siebel 7.5 to Siebel 7.7 and onwards releases.

The actual  (NEW) format introduces the root element to enclose in SOAP payload all Web Service Operation parameters, whether these are arguments of simple type, such as "String" or complex structures, such "Integration Object".

Below are format examples of SOAP requests for the "QueryById" (uses one simple type parameters) and the "InsertOrUpsert" (uses one complex type parameter and a simple type one) operations of the Siebel Inbound Web Service (Application Service Interface - ASI): "Siebel Contact" one should send to Siebel CRM in case of document/literal SOAP binding:

In 7.5:

QueryById:
<soapenv:Envelope xmlns:soapenv:="..." xmlns:asi="...
   ...
   <soapenv:Body>
      <asi:PrimaryRowId>...
      ...



InsertOrUpdate:
<soapenv:Envelope xmlns:soapenv:="..." xmlns:asi="..." xmlns:intobj="..." ...
   ...
   <soapenv:Body>
      <intobj:ListOfContactInterface>
          <Contact ...>
             <Id>...
          ...
      </intobj:ListOfContactInterface>
      <asi:StatusObject>...
      ...



In 7.7-8.1.1 and above:

QueryById:
<soapenv:Envelope xmlns:soapenv:="..." xmlns:asi="..." ...
    ...
   <soapenv:Body>
     <asi:SiebelContactQueryById_Input>
          <asi:PrimaryRowId>...
     </asi:SiebelContactQueryById_Input>




InsertOrUpdate:
<soapenv:Envelope xmlns:soapenv:="..." xmlns:asi="..." xmlns:intobj="..." ...
    ...
    <soapenv:Body>
     <asi:SiebelContactInsertOrUpdate_Input>  
          <intobj:ListOfContactInterface>
             <intbj:Contact ...
                <intbj:Id>...
             ...
          </intbj:ListOfContactInterface>
          <asi:StatusObject>...
     </asi:SiebelContactInsertOrUpdate_Input>
       ...


As RESULT, the external clients, that were communicating with Siebel Web Services will not work correctly after upgrade.

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.