SOAP request and http request , configuration. from postman, also. SAP BTP training.

 The differences between the two SOAP requests can be broken down into the specific elements and namespaces involved in the SOAP message structure.

Original SOAP Request:

xml
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://tempuri.org/">
   <soapenv:Header/>
   <soapenv:Body>
      <tem:Add>
         <tem:intA>3</tem:intA>
         <tem:intB>5</tem:intB>
      </tem:Add>
   </soapenv:Body>
</soapenv:Envelope>

Modified SOAP Request:

xml
<p1:Add xmlns:p1="http://tempuri.org/">
   <p1:intA>4</p1:intA>
   <p1:intB>2</p1:intB>
</p1:Add>

Differences:

1. Envelope and Body Tags:

   • Original Request: Contains the Envelope and Body tags from the SOAP 1.1 protocol.
   • Modified Request: Directly starts with the Add operation without the Envelope and Body tags.

2. Namespace Prefixes:

   • Original Request: Uses tem as the namespace prefix for elements specific to the web service.
   • Modified Request: Uses p1 as the namespace prefix.

3. Namespaces Declaration:

   • Original Request: The namespaces soapenv and tem are declared in the Envelope tag.
   • Modified Request: The namespace p1 is declared directly within the Add element.

4. Values of intA and intB:

   • Original Request: The values of intA and intB are 3 and 5, respectively.
   • Modified Request: The values of intA and intB are changed to 4 and 2, respectively.

SOAP Protocol Differences:

The original request follows the SOAP 1.1 structure, which includes an Envelope containing optional Header and required Body elements. The modified request, as presented, is not wrapped in the typical SOAP envelope and body, and is rather a direct payload of the operation. This can be appropriate if the service endpoint expects a direct XML payload instead of a full SOAP envelope.

Configuration Details in SAP CPI:

• Address: http://www.dneonline.com/calculator.asmx
• Proxy Type: Internet
• WSDL URL: Uploaded
• Service: p1:Calculator
• Endpoint: p1:CalculatorSoap
• Operation Name: p1:Add
• Sender: HTTP with context httpadd

This configuration indicates that SAP CPI is set up to call the Add operation on the CalculatorSoap endpoint. The p1 prefix is mapped to the namespace http://tempuri.org/, consistent with the web service's WSDL definitions.

Summary:

• The main difference lies in the SOAP message structure: full SOAP envelope vs. direct operation payload.
• Both requests are valid but serve different contexts of SOAP messaging based on the endpoint's expected input.
• The configuration in SAP CPI is designed to ensure the correct namespace and endpoint operation are called, aligning the payload accordingly.