To send messages over a SOAP adapter to an integration flow, you must use the POST method. The POST method is used to create or update a resource on the server using the SOAP message body as the input. The SOAP adapter supports both SOAP 1.1 and SOAP 1.2 protocols and can handle both one-way and request-reply message exchange patterns. The SOAP adapter can be configured as a sender or a receiver channel in an integration flow. Reference: SOAP (SOAP 1.x) Adapter | SAP Help Portal, SOAP Sender Adapter: Example Integration Flow | SAP Help Portal

To connect an SAP backend system through the Cloud Connector with an API provider, you must use the on-premise connection type. The Cloud Connector acts as a link between SAP Integration Suite and on-premise systems, enabling secure and controlled access to the backend resources. The on-premise connection type allows you to specify the internal host and port of the backend system, as well as the virtual host and port that will be exposed to SAP Integration Suite. You can also define access control rules and protocols for the on-premise connection. Reference: Part 2: Connect to on-premise APIs from SAP Cloud Platform API Management Cloud Foundry Environment | SAP Blogs, How to configure SAP Cloud Connector & Create API using SCP API Management | SAP Blogs

To avoid duplicate entries when using a Data Store Operation of the type Write, you must select the Overwrite Existing Message parameter. The Overwrite Existing Message parameter allows you to overwrite an existing data store entry with the same key if it already exists. If you do not select this parameter, the Write operation will fail if there is a duplicate key in the data store. Reference: Modernize Integration with SAP Integration Suite | openSAP

To use an API key for authentication in an HTTPS API call, you must include the API key in the message header of the content modifier step. The message header contains information related to the message, such as addressing, routing, or metadata. You can use the content modifier step to create or modify message headers using expressions or constants. The API key is typically passed as a value of a specific header field, such as Authorization or X-API-Key, depending on the API provider's requirements. You can use the Camel Simple Expression Language to access or construct the API key value from variables, properties, or system information. Reference: Content Modifier | SAP Help Portal, Using Camel Simple Expression Language | SAP Help Portal

A Content Modifier is a step in an integration flow that allows you to modify the message header or body using expressions or constants. You can use a Content Modifier to delete namespaces from a message by using expressions that remove the namespace declarations or prefixes from the XML elements or attributes. For example, you can use the expression replace($body,"xmlns:ns[0-9]+=\"[^\"]+\"","") to remove all namespace declarations from the message body. An XSLT mapping is a step in an integration flow that allows you to transform the message body using an XSLT stylesheet. You can use an XSLT mapping to delete namespaces from a message by using XSLT instructions that strip or exclude the namespace information from the output XML document. For example, you can use the instruction <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" exclude-result-prefixes="#all"> to exclude all namespace prefixes from the output document. Reference: Content Modifier | SAP Help Portal, XSLT Mapping | SAP Help Portal