Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update this example to Cloud Foundry? #2

Open
gregorwolf opened this issue Nov 27, 2020 · 1 comment
Open

Update this example to Cloud Foundry? #2

gregorwolf opened this issue Nov 27, 2020 · 1 comment

Comments

@gregorwolf
Copy link

Hello,

are there plans to update this example to Cloud Foundry? The Neo environment is more or less in maintenance mode and shouldn't used for new implementations or?

Also It might make sense to use CAP as it has the possibility to hook into business events by using SAP Enterprise Messaging.

Best regards
Gregor

@grenik
Copy link
Contributor

grenik commented Nov 27, 2020

Hello Gregor,

many thanks for your enhancement proposals.

There are two different Eventing features in SAP S/4HANA Cloud system as per 1NN scope item:

1. Enterprise Event Enablement

The enterprise event enablement framework enables the exchange of events in different platforms for
seamless event-driven communication. You use this feature to publish event from your SAP S/4HANA system
and consume these events via Enterprise Messaging Service, e.g. in the app built on SAP Cloud Platform.

Our team has two sample applications for Enterprise Eventing Enablement:

Apart from CAP framework, there are also other frameworks and libraries that simplify messaging:

  • SAP Cloud SDK has a library that contains model and service classes generated for SAP S/4HANA Cloud events published on SAP Business API Hub. In addition to that, several helper libraries and samples are published in the com.sap.cloud.sdk.datamodel group on Maven Central.
  • Java samples for Enterprise Messaging Service are using Java API for Enterprise Messaging from SAP Service SDK.

2. Business Event Handling

With this feature, upon subscription, the events are created and saved in the Outbound Event Queue in SAP S/4HANA system. Using OData service, you can retrieve the events from the event queue with your own application.

This is exactly what this application does. As this approach is not as popular as the first one, we have no plans to update it in the near future. Please refer to the above mentioned samples if you are more interested in the Enterprise Eventing Enablement feature.

If you have any further questions or ideas, please don't hesitate to contact us.

Best regards,
Nikolay

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants