SAP Community - SAP Event Mesh

Eventmesh POST getting HTTP 403 frobidden error in Postman.

2024-02-08T10:49:14.801000+01:00

hello Experts,

I am developing a scenario on Event Mesh and following the blog: https://community.sap.com/t5/technology-blogs-by-members/guide-step-by-step-procedure-to-send-and-receive-messages-in-a-sap-event/ba-p/13539647

I have created a queue named "SAP/BTP/Ravi/test_queue".

I am trying to post data in this queue using Postman but I am getting 403 Forbidden error in Postman.

Method: POST
URL: https://<URI from key service key>/messagingrest/v1/queues/SAP/BTP/Ravi/test_queue/messages
Authentication: OAuth

Can you please guide me on how I can find what is the issue here?

Thanks,

Ravi

Unable to access Event Mesh in BTP Trial account

2024-02-13T16:02:53.865000+01:00

Hi,

I subscribed to the Event Mesh, and the plan was Standard. However, I didn't see the dev plan or any other plan options while subscribing to the Event Mesh in both regions, Singapore and US East.

When I opened the Event Mesh application, it asked me to create an instance.

FYI-Added roles after subscription

Can't we use event mesh in trial account?

Ref:

EventMesh Issue

2024-02-13T18:49:09.416000+01:00

Hello Experts,

We have been experiencing issues in the events being triggered to Events Mesh to CPI from SAP S4 on prem.

Target system is not able to receive the data as CPI is not receiving the events from SAP event mesh.

We are not able to figure out where and what exactly is the issue as this happens every now and then and not all the time.

I'm new to event mesh, I'm not able to understand how do I troubleshoot this issue as we are getting multiple incidents for having not received the data from the target system.

Kindly pointers on this is highly appreciated.

Relaunching Integration Suite, Advanced Event Mesh – Repackaging Summary

2024-02-14T07:43:40.482000+01:00

We are thrilled to announce that we are launching a new and repackaged version of Integration Suite, advanced event mesh. The initial version of Advanced Event Mesh was launched back in 2022, and we were delighted by the interest and attention it garnered. In our endeavor to offer customer-centric services, we decided to incorporate all the feedback we had received since the initial launch of the service in 2022 and offer a refreshed version of Advanced Event Mesh that can help you in building real-time, event-driven landscapes. This refreshed plan also contains some key innovations that will enable you to build business processes that can help you gain a competitive edge.

All these new features and innovations will be available under the new “Standard” service plan.

For more information on pricing of these new SKUs, please visit the Discover Center. Read on to find out more…

What’s New?

Our guiding philosophy for this new offering was to keep the licensing as simple as possible while ensuring that all the key innovations and mission critical features are available across the board.

Reduced Number of SKUs

We have reduced the total number of SKUs from 10 to 8, by incorporating the dedicated region and customer private region in all the broker types. In addition, you have a new SKU to extend the memory spool of your brokers up to 6TB in increments of 500GB. Here’s the list of new SKUs:

SAP Integration Suite, advanced event mesh, 100
SAP Integration Suite, advanced event mesh, 250
SAP Integration Suite, advanced event mesh, 1K
SAP Integration Suite, advanced event mesh, 5K
SAP Integration Suite, advanced event mesh, 10K
SAP Integration Suite, advanced event mesh, 50K
SAP Integration Suite, advanced event mesh, 100K
SAP Integration Suite, advanced event mesh, spooling add-on

The number attached to each broker size indicates the number of client connections that it can support. For more details on the technical capabilities of each broker, refer to the official documentation on help.sap.com.

New Features and Innovations

As mentioned earlier, all brokers get the dedicated and private region deployment options included. You also get distributed tracing with the newly launched brokers, enabling the admin user to track the lifecycle of an event though the Event Mesh. For more information on distributed tracing, see the official documentation.

In addition to all this, you can also extend the message spool size of each broker in increments of 500GB by purchasing the spooling add-on. This message spool size will be available in addition to the already included spool memory with each broker. For example, the Enterprise 1K broker comes with 50GB of message spool. If you purchase and assign the entitlement for 2 units of the spooling add-on, you will get an additional 1TB of message spool, giving you a total message spool size of 1050GB.

Your Choice of Licensing Model

The new Advanced Event Mesh SKUs will be available on both subscription and consumption based pricing models, meaning you will be able to activate the new brokers on Cloud Platform Enterprise Agreement (CPEA) and Pay-as-you-Go (PayGo) licensing models in addition to the standard subscription-based licensing. This, combined with the hourly broker pricing gives you full flexibility to use the brokers as per your requirement and optimize your total cost of ownership (TCO).

What happens to the old brokers and pricing plan?

As of today, we are announcing that we will deprecate the old Advanced Event Mesh brokers on CPEA and Pay-as-you-go pricelists. Following a 6-month notice period, these older plans will be deprecated. Current CPEA and PayGo customers will be able to access both the old and new brokers till the end of your current contract period. After your current contract is renewed, the brokers which you have activated from the older plans will continue to run till you deactivate them. However, we strongly recommend that you consider migrating to the newly launched SKUs owing to all the advantages and benefits that it offers.

We hope you are as excited as we are to experience the new Integration Suite, advanced event mesh. We strive to deliver solutions that can help you digitally transform your enterprise to be future-ready and gain a competitive edge. We look forward to any feedback and thoughts you have on this new launch via the comments section of this post.

Connect S/4aha with Event Mesh Sap CPI

2024-02-20T17:43:51.083000+01:00

Hi everyone,

I would like to use the Event Mesh tool to trigger the event.
I would like the event mesh to be called when a material from MM01 is created on S/4hana, how do I connect the Event Mesh to sap?

SAP CPI and Event Mesh Connectivity

2024-02-23T08:01:34.760000+01:00

We wanted to make a connection between SAP CPI(Neo) and Event Mesh, where we wanted to initialize the flow via scheduler, we just wanted to run our flow connect to Event mesh at specific time but what we observed is if we have to put scheduler in flow then used the request reply and added AMQP adapter but it gives us the error stating that "not compatible" . then we thought of using the rest endpoint via http adapter to consume message from EM queue, but we are getting 401 error statating "HTTP method not found" but it working via postman.

Just wanted to know can we connect CPI and EM via REST or not and is there other way where we can use scheduler and AMQP adapter

S/4HANA cloud extensibility service on BTP - not available?

2024-03-04T15:30:50.612000+01:00

Hi all,

I'm struggling a little bit. I'm working on an event mesh implementation from S4Public Cloud. I'm trying to connect a BTP environment to receive events. But here is the case:

- I already linked my S4HPC environment to the BTP using the Tokens. The system is registered in BTP

My main goal now is to activate the entitlements to use the cloud extensibility. Somehow I'm not able to assign those.

so unless I have not assigned this to a subaccount, I'm not able to generate communication arrangements and actually create the link to the system. (item 7)

https://community.sap.com/t5/technology-blogs-by-members/enable-events-from-s-4hana-cloud-to-event-mesh/ba-p/13559401

Any ideas? I do have all roles in BTP and S4HPC and the cpea credits are there. I watched the tutorial of Antonio @ajmaradiaga but I just can't get it to work.

All the best

Laurens

Principal Propogation, Event Mesh setup and User Context in CAP Nodejs application

2024-03-07T09:28:22.788000+01:00

Dear all,

We have a landscape with SAP S4 on premise system -> Connected to a Event Mesh service on BTP -> and a CAP NodeJS based application which is the consumer of the event received from S4 .

There is a principal propagation in place between BTP and S4.

When an event is raised from S4 , it reaches to the Message client in Event Mesh service on BTP. The CAP Nodejs based application is subscribed to the queue/topic of the same. It immediately receives the event and starts handling it in an event handler.

Now, during the processing within CAPM, it makes oData calls to the backend S4 via Principle Propagation and fetch some more data.

When running locally ( BAS ), this works fine because we have a user context available and that helps in making the connection with S4 via Principle Propagation.

However, If the app is deployed on the space, then even though the event is received successfully, the application cannot make calls to the backend because there is no user context available.

How can we make this work? We can pass the User Id via the event payload but how can we create/get a context out of a simple user id and pass it in the header while making oData calls ?

Please advice.

Nilesh

Event mesh error condition = amqp:not-allowed

2024-03-07T23:39:09.205000+01:00

Hi,

Trying to send message to Event Mesh queue via SAP CPI AMQP Receiver adapter and getting the message as

"com.sap.it.rt.adapter.http.api.exception.HttpResponseException: An internal server error occured: publishing target (queue:queue_name) forbidden (220056) [condition = amqp:not-allowed]."

Can you please let me know what could be the cause of this queue being forbidden as I can test it locally within event mesh.

Regards,

Abhi

Topic Name Queue Event Mesh

2024-03-12T16:56:49.019000+01:00

hi,

I created a queue on the Event Mesh, how can I direct just one event to this queue? For example, when creating the Business Partner on S/4hana.

I saw that it is necessary to insert the topic name of the queue but it doesn't work for me.

but it only works when I enter * but in this case it intercepts all events:

Can you provide me with the string to insert in the topic name for the creation of the business partner?

thank you

Subscribe/Webhook S4Hana Public Cloud to its own events. Is that possible?

2024-03-14T19:21:59.195000+01:00

Hi all,

this is the case. We have a specific change on an object (not a bopf object so no option to catch the events on-stack) and we send the events to the event mesh. All is fine. It looks like this:

The events are received in the Event mesh instance triggered by the creation of the Cloud Extensibility Service.

We also created a second instance which subscribes to the initial generated event mesh instance. This instance has a different namespace and is subscribed to the topics. I adjusted the Service Descriptor to accept queues/topics from different namespace.

The thing is: I want to subscribe my S4HPC instance to one of the queues which is available, but everytime I want to subscribe, the namespace needs to be the same as the initial eventmesh instance setup by the cloud extensibility service. The problem is that I can't create a queue on that initial instance because the topics are not conform the rules (which I can't change because it is generated by the cloud extensibility service). Still with me? 🙂

So what I want is: Trigger an event from s4hpc and receive it in eventmesh. The subscribed eventmesh should be able to push the message to the s4hpc system using a webhook. Or.... s4hpc needs to be able to subscribe to the queue and receive the events (which I can tackle using Event consumption model class in abap).

The questions:

is it even possible to receive events from event mesh IN s4h public cloud?
If we would go for a webhook, what would the address be of the public cloud tenant?
I can reroute the event mesh to CPI and trigger an API on the s4hpc side, but I really would like to use the event consumption model idea.

I hope you can help. I know the tutorials of S4 to Eventmesh to build or whatever, but it really is about the way back to S4HPC.

Kind regards and all the best

Laurens

Cloud extensibility generated instance

my own subscriber instance

The subscription attempt in my communication scenario:

The cloud extensibility generated one can't actually have a queue with the two events being received in the queue. It is only a distributer.

Event Mesh Webhook to Integration Suite

2024-03-26T10:25:05.825000+01:00

Hello together,

i have created an event mesh queue, subscription and now a Webhook. I want the message from the event to go directly to an endpoint in the integration suite that i have configured. But every time i get an 401 Error when the message should be send to the Webhook URL. I tried to put in my credentials from the BTP where i have this UserRole, but it´s not working. In the HTTPS configuration in the integration suite you just have the options for UserRole and ClientCertificate (which is not available in the webhook configuration in the event mesh).

How can i solve this problem?

Thanks in advance

Unable to consume messages in S/4 Hana system that are published in Event Mesh

2024-03-26T16:54:07.920000+01:00

Hi there,

we have created a event consumption Model as suggested in below blog till step 8.

Event Processing in an SAP S/4HANA on-premise system | SAP Tutorials

We want consume the message that is published in Event mesh queue. Kindly help.

AIF Setup for Event Mesh

2024-03-27T06:51:13.356000+01:00

Hi All,

I am working on POC of AIF setup for Event. For this I am using Topic "sap/s4/beh/businesspartner/v1/BusinessPartner/*" to trigger BusinessPartner.

Does anybody know the step-by-step process to setup AIF for Event.

Please note that I have referred below link of SAP Help Portal.

Define Event Settings | SAP Help Portal

https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/810dfd34f2cc4f39aa8d946b5204fd9c/d4f5487b82774e9683e1ae03b5ac0b04.html

Thank you in advance.

Filtering the Events in S4 HANA on premise System

2024-04-01T16:22:20.702000+02:00

Hello,

We have done the Event Enablement Setup in our system (S4 HANA on premise 2022) and we are getting all the enabled outbound topics to our Event Mesh on BTP but here we will not need every event to be coming in the event mesh queue, we need to filter the events coming to our Event Mesh.
Example: For business partner we are getting events for all the business partner created but we need event triggered only for business partner created for specific country.

Question: What are the possible ways using which we can filter the events at S4 HANA side?

Event mesh S/4hana on-premise

2024-04-04T11:58:09.257000+02:00

hi,

I created a queue on the Event Mesh, how can I direct just one event to this queue? For example, when creating the Business Partner on S/4hana on-premise

I saw that it is necessary to insert the topic name of the queue but it doesn't work for me.

but it only works when I enter * but in this case it intercepts all events:

Does anyone know what might be missing?

thank you

SAP CAP with Event Mesh - Error: JWT with audience is not issued for clientIds

2024-04-08T09:14:24.325000+02:00

we are currently trying to integrate the event mesh into our SAP CAP application. We followed this tutorial here: https://cap.cloud.sap/docs/guides/messaging/event-mesh Therefore our files looks like the following:

event mesh config:

{
  "options": {
    "management": true,
    "messagingrest": true,
    "messaging": true
  },
  "rules": {
    "topicRules": {
      "publishFilter": ["${namespace}/subaccounts"],
      "subscribeFilter": ["${namespace}/subaccounts"]
    },
    "queueRules": {
      "publishFilter": ["${namespace}/subaccounts"],
      "subscribeFilter": ["${namespace}/subaccounts"]
    }
  },
  "authorities": ["$ACCEPT_GRANTED_AUTHORITIES"],
  "xs-security": {
    "oauth2-configuration": {
      "credential-types": ["binding-secret", "x509"]
    }
  },
  "version": "1.1.0",
  "emname": "our-cool-event-mesh",
  "namespace": "cool/event/mesh"
}

package json:

{
...
"cds": {
  "requires":  {
         "messaging": {
        "[production]": {
          "queue": {
            "name": "$namespace/subaccounts"
          },
          "kind": "enterprise-messaging"
        },
        "[hybrid]": {
          "kind": "enterprise-messaging-shared"
        }
      },   
}
}
}

However, when we deploy the application, we get the error:

Error: Jwt token with audience: [ "here the event mesh client id is shown", uaa ] is not issued for these clientIds: [ here our srv application is shown ]

ERR at returnError (/home/vcap/deps/0/node_modules/@sap/xssec/lib/validator.js:308:25)

ERR at /home/vcap/deps/0/node_modules/@sap/xssec/lib/validator.js:392:36

We googled a bit about this error and we came accross this issue for the SAP cloud sdk: https://github.com/SAP/cloud-sdk-js/issues/3050

In the ticket it says that: " it looks like the error is because the jwt is not how the xssec library expects it to be" which also the error message kind of says that a validator returned this error. However we are using the latest sap/xssec library (3.6.1) and cannot influence it any further.

We also tried to delete the event mesh and deploy it again, but this also didnt fix the issue.

Is this an issue with the xssec library and I need to open a ticket for SAP or do we have the event mesh falsely configured?

Thank you very much i advance!

SAP Event Mesh Service Key Creation failed

2024-04-08T13:40:57.922000+02:00

Hi All,
Last week i created an SAP Event Mesh Instance based on this tutorial, https://developers.sap.com/tutorials/cp-enterprisemessaging-instance-create.html.

To generate this instance i used the following JSON-File based on the service descriptor that SAP offers in the Help Section.

Instance Creation JSON:

Unfortunately when creating the OAuth2.0 service Keys (for AMQP / MQTT & HTTPREST) for external connection it didnt work out.

the JSON I used:

The System tells me that he cannot find messaging and management.

Based on the tutorial and on this blog here I choose to leave all the placeholders as delivered from the Tutorial but it still doesnt work: https://community.sap.com/t5/technology-q-a/service-key-creation-for-event-mesh/qaq-p/12527257

Can anyone Help me with this Issue?

Thanks

SAP Event Mesh - Maintain source for outbound bindings

2024-05-08T23:23:30.298000+02:00

Hello!

First of all, I want to apologize if this question has been answered already. I am still trying to find my way around this new site, and I have not seen any reference to it.

We have copied down our Prod environment to test. I have redone all the configuration for event mesh, and this is what my outbound message looks like:

{

"type":"sap.s4.beh.product.v1.Product.Changed.v1",

"specversion":"1.0",

"source":"/default/sap.s4.beh/PROD",

"id":"0675e911-ee96-1eef-83ae-bd428725c8db",

"time":"2024-05-08T20:02:36Z",

"datacontenttype":"application/json",

"data":{"Product":"RANDOMMATERIAL"}

}

My question is, where do I go to update the source? I needs to reflect that is coming from test and not from production.

Thanks so much in advance!

SAP Event Mesh - Message processing status "Retry" for failed messages

2024-05-16T16:22:27.179000+02:00

Hello

I have a query on the "Retry" message processing status in Cloud Integration.

When messages polled from Event Mesh using AMQP adapter fails due to some reason during the iflow processing in Cloud Integration, the messages end up in "Retry" status in the "Monitor Message Processing" view. After the message is retried based on the configuration mentioned in Event Mesh Queue/AMQP adapter, the message should apparently go into "Failed" status but it remains in "Retry" status.

Is there an adjustment in configuration that can be done either at Event Mesh Queue or AMQP adapter, so that message processing status is displayed as "Failed" instead of "Retry" (screenshot below) ?