Skip to Content
0
Jan 05, 2023 at 05:29 PM

Runtime daemon for the Enterprise Event Enablement

275 Views

Dear all,

I found this nice architecture diagram regarding the event enablement component inside s/4hana used for the business event in this video https://www.youtube.com/watch?v=hPCe0E8Wp5o. From that architecture picture, I have learned that the business event is automatically pushed to the SAP Event Mesh. I have also read that this is the only option that SAP currently provides. But we have use cases where we want to push the event to another application vendor event bus instead o the SAP Event Mesh.

In the diagram picture in minute 45 we see the block 'Runtime Daemon', which is responsible for pushing the event to the SAP Event Mesh using the MQTT protocol. Is this daemon somehow extensible by custom code so we can plug in our own code to send the event using HTTP protocol somewhere else? This requirement is similar to the use case with the webhook in the sap event mesh. Here I can provide an endpoint URL as a webhook so that the event is sent to that endpoint through the HTTP protocol.

The other event platform bus can only be connected with the HTTP protocol and not with the MQTT or AMQP. But if we can plug in our own abap code like a Badi or user-exit we can use the HTTP client library from abap and build the HTTP callout. That would not be an issue. The question is if there is a user-exit, custom-exit or Badi for the daemon.

Thanks,

Ly-Na Phu