Node.js: Support for Event Mesh in SAP Integration Suite

node.js/messaging.md

@@ -334,6 +334,7 @@ For local environments, use [`cds bind`](../tools/cds-bind#cds-bind-usage) in a
 For local testing use [`kind`: `enterprise-messaging-shared`](#event-mesh-shared) to avoid the complexity of HTTP-based messaging.
 :::
 
+
 ### SAP Event Mesh (Shared) { #event-mesh-shared}
 
 `kind`: `enterprise-messaging-shared`
@@ -383,6 +384,7 @@ For optimal performance, you should set the correct access type.
 To make sure your server is not flooded with messages, you should set the incoming session window.
 :::
 
+
 ### SAP Event Mesh
 
 `kind`: `enterprise-messaging`
@@ -472,14 +474,58 @@ If you enable the [cors middleware](https://www.npmjs.com/package/cors), [handsh
 
 <span id="aftereventmesh" />
 
-### SAP Cloud Application Event Hub { #event-broker }
 
-`kind`: `event-broker`
+### Event Mesh in SAP Integration Suite <Beta /> { #integration-suite-event-mesh }
+
+[Event Mesh in SAP Integration Suite](https://help.sap.com/docs/integration-suite/sap-integration-suite/event-mesh) is supported via two `kind` entries, mirroring the SAP Event Mesh variants:
+
+| Kind | Protocol | Equivalent to |
+|------|----------|---------------|
+| `event-mesh` | HTTP + webhooks | `enterprise-messaging` |
+| `event-mesh-shared` | AMQP | `enterprise-messaging-shared` |
+
+::: tip Setup via `cds add`
+Use `cds add event-mesh` or `cds add event-mesh-shared` to automatically configure `package.json`, `mta.yaml`, `event-mesh.json`, and Kyma deployment descriptors. Both support a `--cloudevents` flag.
+:::
+
+#### `event-mesh`
+
+Same as `enterprise-messaging` except it connects to an Event Mesh in SAP Integration Suite service instance (`event-mesh-message-client`).
+
+Example:
+
+```json
+{
+    "requires": {
+        "messaging": {
+            "[production]": { "kind": "event-mesh" }
+        }
+    }
+}
+```
+
+The configuration options are the same as for [`enterprise-messaging`](#sap-event-mesh).
+
+#### `event-mesh-shared`
+
+Same as `enterprise-messaging-shared` but connects to an Event Mesh in SAP Integration Suite service instance. Best suited for local hybrid testing.
+
+Example:
+
+```json
+{
+    "requires": {
+        "messaging": {
+            "[production]": { "kind": "event-mesh" },
+            "[hybrid]": { "kind": "event-mesh-shared" }
+        }
+    }
+}
+```
+
+The configuration options are the same as for [`enterprise-messaging-shared`](#event-mesh-shared).
 
-Use this if you want to communicate using [SAP Cloud Application Event Hub](https://help.sap.com/docs/event-broker).
 
-The integration with SAP Cloud Application Event Hub is provided using the plugin [`@cap-js/event-broker`](https://github.com/cap-js/event-broker).
-Please see the plugin's [setup guide](https://github.com/cap-js/event-broker/blob/main/README.md#setup) for more details.
 
 ### SAP Integration Suite, Advanced Event Mesh <Beta />  { #advanced-event-mesh }
 
@@ -490,10 +536,23 @@ Use this if you want to communicate using [SAP Integration Suite, advanced event
 The integration with SAP Integration Suite, advanced event mesh is provided using the plugin [`@cap-js/advanced-event-mesh`](https://github.com/cap-js/advanced-event-mesh).
 Please see the plugin's [setup guide](https://github.com/cap-js/advanced-event-mesh/blob/main/README.md#setup) for more details.
 
+
+### SAP Cloud Application Event Hub { #event-broker }
+
+`kind`: `event-broker`
+
+Use this if you want to communicate using [SAP Cloud Application Event Hub](https://help.sap.com/docs/event-broker).
+
+The integration with SAP Cloud Application Event Hub is provided using the plugin [`@cap-js/event-broker`](https://github.com/cap-js/event-broker).
+Please see the plugin's [setup guide](https://github.com/cap-js/event-broker/blob/main/README.md#setup) for more details.
+
+
 <div id="queuing-sap" />
 
+
 <div id="kafka-sap" />
 
+
 ### Redis PubSub <Beta />
 ::: warning
 This is a beta feature. Beta features aren't part of the officially delivered scope that SAP guarantees for future releases.
@@ -551,6 +610,7 @@ When using `file-based-messaging` in a multitenant scenario, only the provider a
 
 You can use local messaging to communicate inside one Node.js process. It's especially useful in your automated tests.
 
+
 ### Composite-Messaging
 
 `kind`: `composite-messaging`