Challenge with SAP Event Mesh: Status Code 200 in Postman and ABAP, but 503 in Event Mesh

[AlexandrosNtontsov]

Problem Statement:

In our current architecture, we use SAP Event Mesh to transmit messages to SAP IS-U (R3). The process involves an SAP Event Mesh webhook calling a SICF service under the path /sap/event_mesh_api/ via the URL /sap/event_mesh_api/events?sap-client=XXX within our IS-U environment. However, in tests with Postman and an ABAP report, we get different results: 

Test with Postman and ABAP Report: 

When testing the target URL /sap/event_mesh_api/events?sap-client=XXX using Postman or an ABAP report, we receive an HTTP status code 200, indicating a successful connection and response. 

Test with SAP Event Mesh Webhook: 

However, when the Event Mesh webhook calls the same URL, an HTTP status code 503 is logged in Event Mesh. This suggests that the target URL is either unreachable or there is a failure in server-side processing. 

Monitoring and Troubleshooting: 

No messages are displayed in Cloud Connector Monitoring. This could mean that the message either never reaches the Cloud Connector or that an error in processing prevents the message from being correctly logged. 

Internal Test Service: 

To further test the functionality of Event Mesh, we connected an internal test service. When triggering the service through the webhook, we observed that the messages were successfully delivered via Event Mesh to the service. This confirms that the basic configuration of Event Mesh is working. 

Issue with the Cloud Connector: 

However, a problem arises when the Cloud Connector is involved in the communication. The messages that are supposed to be sent via the Event Mesh webhook to the IS-U environment do not reach the Cloud Connector. We suspect that the issue lies within the Cloud Connector configuration, but we have not yet identified the exact cause. 

Contact with SAP Support: 

SAP Support was unable to reproduce the problem in their environment; the connection worked flawlessly on their side. 

Question to the Community: We are facing the challenge that the Event Mesh webhook does not provide the same response as the tests in Postman or ABAP. Instead, it returns a status code 503, indicating a service failure. 

Has anyone in the community experienced similar issues with SAP Event Mesh? If so, what steps or solutions were helpful in troubleshooting? 

Some specific questions where we need assistance: 

Different Status Codes: Why might the Event Mesh webhook return a status code 503, while direct tests with Postman or ABAP return a status code 200? 

Monitoring Issue: Why do the messages not appear in Cloud Connector Monitoring? Are there specific settings or logs that could provide more insight into the cause of the problem? 

Cloud Connector Issue: Has anyone experienced similar issues related to Cloud Connector configuration? What specific points should we check? 

Additional Tests or Configurations: What other tests or configuration changes could be helpful in identifying the root cause of the problem? 

We look forward to your experiences, tips, and solutions to help resolve this issue. 

Thank you in advance for your support! 

Attachment: Following this post, you will find screenshots documenting the issues described, configuration and our previous tests. 

 

 

 

#SAPEventMesh #SAPBTP #CloudConnector #SAPIntegration #ISU #ABAP #SAPTechWebhooks #SAPSupport #SAPArchitectur

[Ryan-Crosby]

One thing I would notice from your screenshots is that you are testing with a GET from Postman but the webhook should be a POST if you are passing an event to the system.

[AlexandrosNtontsov]

Hello Ryan, Thank you very much for pointing that out. Indeed, the GET request might seem confusing at first glance. However, we've already conducted multiple and varied tests, and the method used doesn't seem to have a significant impact on the issue we're facing. We appreciate your input and are open to any other suggestions you might have. Best regards, Alexandros

[Ryan-Crosby]

Probably a good idea to activate your traces on the CC to see if it can provide any clues because I'm assuming your Postman test is not passing through it.

[Willem_Pardaens]

You mentioned you tried an internal testing service as a receiver of the webhook, which was successful. I would suggest to take this same testing service and put it behind the cloud connector as a test.

Also, I'd pay close attention to the payload of the event: in postman you set your manual payload, but with event mesh it might be possible the payload gets changed (cloudEvents format? string-to-binary? Stringified JSON?) and hence your ABAP rejecting the message (choking on it).)