SK SKYVVA Documentation

How to Configure the HTTP Protocol?

1. Overview

The SKYVVA SAP BTP Integration Suite Adapter supports the HTTP protocol for communication between Salesforce and SAP BTP Integration Suite.

When HTTP is selected as the protocol, the adapter supports:

Both payload formats support: The SFDC2SAPI Payload Format is not supported with the HTTP protocol.

In addition, HTTP supports both JSON and XML for the request and response message formats.

image

2. HTTP Protocol

When HTTP is selected in the SKYVVA SAP BTP Integration Suite Adapter, the following payload formats are available:

  1. V3 Payload Format
  2. SAP-PO Payload Format
Unlike the SOAP protocol, SFDC2SAPI Payload Format is not available for HTTP.

2.1 HTTP Payload Format Support

Payload FormatInterface API V2Interface API V3
V3 Payload FormatSupportedSupported
SAP-PO Payload FormatSupportedSupported
SFDC2SAPI Payload Format❌ Not Supported❌ Not Supported
Testing Result: The HTTP protocol supports V3 Payload Format and SAP-PO Payload Format with both Interface API V2 and Interface API V3. SFDC2SAPI Payload Format is not supported with HTTP.

3. HTTP Request Format

The HTTP protocol supports the following request message formats:

3.1 JSON Request

When the request format is configured as JSON, the adapter sends the HTTP request body in JSON format.

Example:

{
  "Account": {
    "BillingCity": "Phnom Penh",
    "BillingCountry": "Cambodia",
    "Name": "Coca"
  }
}

3.2 XML Request

When the request format is configured as XML, the adapter sends the HTTP request body in XML format.

Example:

<Account>
    <BillingCity>Phnom Penh</BillingCity>
    <BillingCountry>Cambodia</BillingCountry>
    <Name>Coca</Name>
</Account>

3.3 Request Format Support

Request FormatHTTP Protocol
JSONSupported
XMLSupported

4. HTTP Response Format

The HTTP protocol also supports the following response message formats:

The response format defines how the response returned from SAP BTP Integration Suite is processed by the SKYVVA SAP BTP Integration Suite Adapter.

4.1 JSON Response

Example:

{
  "status": "success",
  "message": "Message processed successfully"
}

4.2 XML Response

Example:

<Response>
    <Status>success</Status>
    <Message>Message processed successfully</Message>
</Response>

4.3 Response Format Support

Response FormatHTTP Protocol
JSONSupported
XMLSupported

5. HTTP Protocol Compatibility

The complete HTTP protocol testing result is:

ConfigurationInterface API V2Interface API V3
V3 Payload Format✅ Supported✅ Supported
SAP-PO Payload Format✅ Supported✅ Supported
SFDC2SAPI Payload Format❌ Not Supported❌ Not Supported
JSON Request Format✅ Supported✅ Supported
XML Request Format✅ Supported✅ Supported
JSON Response Format✅ Supported✅ Supported
XML Response Format✅ Supported✅ Supported

6. SOAP and HTTP Protocol Comparison

Based on the SOAP testing from the previous section and the HTTP testing, the protocol support can be summarized as follows:

FeatureSOAPHTTP
Interface API V2✅ Supported✅ Supported
Interface API V3✅ Supported✅ Supported
V3 Payload Format✅ Supported✅ Supported
SAP-PO Payload Format✅ Supported✅ Supported
SFDC2SAPI Payload Format✅ Supported❌ Not Supported
JSON Request Format✅ Supported
XML Request Format✅ SOAP/XML✅ Supported
JSON Response Format✅ Supported
XML Response Format✅ SOAP/XML✅ Supported
Important: The key difference in payload-format support is that SOAP supports V3 Payload Format, SAP-PO Payload Format, and SFDC2SAPI Payload Format, while HTTP supports only V3 Payload Format and SAP-PO Payload Format.

7. HTTP Testing Result Summary

The testing confirms that the HTTP protocol of the SKYVVA SAP BTP Integration Suite Adapter supports:

The SFDC2SAPI Payload Format is not supported with the HTTP protocol.

The HTTP configuration can be represented as follows:

HTTP Protocol
│
├── Interface API V2
│   ├── V3 Payload Format ────────> Supported
│   └── SAP-PO Payload Format ────> Supported
│
├── Interface API V3
│   ├── V3 Payload Format ────────> Supported
│   └── SAP-PO Payload Format ────> Supported
│
├── Request Format
│   ├── JSON ─────────────────────> Supported
│   └── XML ──────────────────────> Supported
│
├── Response Format
│   ├── JSON ─────────────────────> Supported
│   └── XML ──────────────────────> Supported
│
└── SFDC2SAPI Payload Format ─────> Not Supported
Key Testing Result: With the HTTP protocol, both V3 Payload Format and SAP-PO Payload Format support Interface API V2 and Interface API V3. HTTP requests and responses can use either JSON or XML. The SFDC2SAPI Payload Format is not supported with HTTP.
Open this article in the interactive viewer →