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 @Johannes23,if you create the service instance for the messaging client, this automatically "bound" to the Event Mesh capability of the SAP Integration Suite.Creating a messaging client instance will just create and expose credentials to access th...
Hi @Johannes23,if you have created the message client on space level, inside the CF runtime environment, you can just create a service key to get the credentials.Runtime Environment = other -> application bindingRuntime Environment = Cloud Foundry ->...
Hi @Tukutupap,In the SAP Customizing Implementation Guide (IMG), choose ABAP Platform->Enterprise Event Enablement->Administration->Channel Connection Settings->Manage Channel and Parameters and execute the node, or go to transaction /IWXBE/CONFIG to...
Hi @Tukutupap, the source parameter is part of your channel configuration in the S/4 system.I don't know what type of system you are using (Cloud or OP). For the Cloud version there are several ways how you can create that channel (SAP_COM_0092 manua...
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