SAP Knowledge Base Article - Public

3089975 - How to test a C4C Inbound Service Interface via SOAP UI using Reliable Messaging


You would like to test a C4C integration scenario by using the Reliable Message option in SOAP UI

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."


SAP Cloud for Customer



Whenever you are using Web Services in business-critical applications, it is important that messages are exchanged in a reliable manner. Web Services Reliable Messaging (WSRM) ensures that message exchange is performed correctly – without messages getting lost or being duplicated. WSRM ensures a reliable exchange of messages even when the connection to the network is lost.

To guarantee message exchange and also to control the sequence of incoming messages, the WSRM protocol combines one or multiple messages into sequences. Sequences contain a unique identifier. Messages in a sequence are numbered consecutively. The WSRM sequence header in the SOAP message identifies the sequence to which a message belongs.

WS Reliable Messaging implementations at the sender and receiver sides ensure that messages are transferred securely. A prerequisite for this is that incoming messages are confirmed by the receiver. For this purpose, the specification defines the format of an acknowledgment that the receiver sends to the sender as confirmation. The sender waits for the confirmation and, if necessary, keeps sending the message until the confirmation is received.


In order for you to test a C4C Inbound Service Interface using Reliable Message in SOAP UI, you need to follow the below steps:

  1. You need to import the WSDL file downloaded from C4C in SOAP UI.
  2. Double click on the Request.
  3. Paste the payload to be used.
  4. Add Credentials.
  5. Then click on the WS-RM button on the bottom of the Request window.
  6. Flag the option Enable WS-Reliable Messaging.
  7. Select the 1.2 value on the dropdown for WS-RM Version.
  8. Change the URL being called in the Request window by deleting everything after the question mark (?).
  9. Add an UUID generator to it: MessageId=${=java.util.UUID.randomUUID()}.


See Also

2981094 - How to test the SOAP API request and response using SOAP UI


KBA , LOD-CRM-INT-ERP , Integration of C4C with ERP , How To


SAP Cloud for Customer add-ins all versions