Working with SAP Event Mesh (formerly known as SAP Enterprise Messaging), you might have seen this or similar errors before:
[connection rejected (too much connections)]
Until recently each SAP Event Mesh service instance supported only 10 connection...
There are quiet a few blog posts about SAP Cloud Platform Enterprise Messaging and Enterprise Event Enablement. Check out taranam's excellent blog post using the SAP S/4HANA Cloud Extensibility service, pradeep.panda's blog post describing the manual...
The main focus of OData and SAP Gateway is to provide a slim and lightweight protocol for data consumption. In the majority of use cases, CREATE operations are performed for single entities only. However, there are valid scenarios where it’s necessar...
Hi,yes this service key will contain all the needed credentials, if you had enabled them while creating the service instance (according to your posted JSON config, you have enabled them). Best regards,Tobias
Hi @mark_fryu,It looks like you just need to provide the correct topic subscription pattern in the queue configuration.If you are able to consume all events when using the "*" topic subscription, we can easily identify the correct topic patterns from...
Hi @Ilyass01,you have already linked the answer for your question. When creating a service-key you only need to provide a name for the service-key but no JSON parameters - this is not required. As a result you will get the service-key containing the...
Hi amir_moeini,
Showkath's blog post is fokusing on general messaging concepts of the service offering "Event Mesh", he is not talking about the service "Integration Suite, advanced event mesh".
Anyways for both service offerings a queue always tre...