Understanding this process is important when using the SAP BTP, Kyma runtime to run your extensions, which should be executed when a certain event gets emitted. For example, the SAP SuccessFactors systems publishes the event that a new hire joined the company. The extension can subscribe to the event and can be used to carry out further actions with this data. For example to enroll the new hire to an onboarding session.
While having the delivery and processing flow of Kyma in mind, Kyma Eventing can be used within the SAP BTP framework for two scenarios:
- When Business Events are consumed from connected SAP & Non-SAP Solutions (Note: Only CX solutions support Kyma Eventing, for example: SAP Commerce Cloud, SAP Sales Cloud, FSM. Other solutions like SAP S/4HANA currently do not send events via Kyma Eventing, as they send them directly to event mesh from where one needs to setup a webhook. For further information on this, please visit this page):
- When In-Cluster Events are used for event-driven microservices:
In the Kyma Dashboard, you can view and update the subscriptions for a specific workload,
or you can do it on a namespace-level under Configuration.
In Kyma, you can send and receive events with the help of the Kyma Eventing processing back end. While doing that, technologies like NATS (in the SAP BTP, you can switch this back end to SAP Event Mesh), JetStream, HTTP-post requests as well as (Subscription) Custom Resources are used. You can use Eventing in the SAP BTP, Kyma runtime for two fundamental scenarios:
- Business Events are consumed from connected SAP and non-SAP Solutions,
- In-Cluster Events are used for event-driven microservices.
Furthermore, in the SAP BTP, Kyma runtime you can use the Dashboard to access useful features and to review Events.