EMIS details updated

Author: ajmaradiaga

exercises/03-cloudevents-at-sap/README.md

@@ -88,7 +88,7 @@ Kyma contains an [Eventing module](https://kyma-project.io/#/06-modules/README
  SAP offers various services that can help customers embrace event-driven architectures. The different offerings can meet customers where they are in their EDA adoption/implementation journey. These are:
 
 * SAP Cloud Application Event Hub
-* SAP Event Mesh
+* Event Mesh capability in SAP Integration Suite
 * SAP Integration Suite, advanced event mesh
 
 ### [SAP Cloud Application Event Hub](https://discovery-center.cloud.sap/serviceCatalog/sap-event-hub?service_plan=standard&region=all&commercialModel=btpea "https://discovery-center.cloud.sap/serviceCatalog/sap-event-hub?service_plan=standard&region=all&commercialModel=btpea")
@@ -107,20 +107,20 @@ CloudEvents are first-class citizens in SAP Cloud Application Event Hub, as even
 
 If all your event needs are within the SAP cloud world, e.g. exchange events between SAP cloud applications and SAP BTP, this service can fulfill your needs.
 
-### [SAP Event Mesh](https://discovery-center.cloud.sap/serviceCatalog/event-mesh?region=all "https://discovery-center.cloud.sap/serviceCatalog/event-mesh?region=all") 
+### [Event Mesh capability in SAP Integration Suite (EMIS)](https://help.sap.com/docs/integration-suite/sap-integration-suite/event-mesh "https://help.sap.com/docs/integration-suite/sap-integration-suite/event-mesh") 
 
 <p align = "center">
-  <img alt="SAP Event Mesh" src="assets/event-mesh.png" width="25%"/><br/>
+  <img alt="Event Mesh capability in SAP Integration Suite" src="assets/event-mesh.png" width="25%"/><br/>
 </p>
 
-SAP Event Mesh allows applications to communicate through asynchronous events. It can be used to publish and consume business events from SAP and non-SAP sources across hybrid landscapes from the digital core (ERP products, e.g. SAP S/4HANA Cloud public edition and SAP S/4HANA) to extension applications through event-driven architecture. It is a fully managed [centralised event-oriented](https://help.sap.com/docs/event-mesh/event-mesh/event-mesh-default-plan-concepts?locale=en-US "https://help.sap.com/docs/event-mesh/event-mesh/event-mesh-default-plan-concepts?locale=en-US") service part of SAP BTP.
+The Event Mesh capability in SAP Integration Suite allows applications to communicate through asynchronous events. It can be used to publish and consume business events from SAP and non-SAP sources across hybrid landscapes from the digital core (ERP products, e.g. SAP S/4HANA Cloud public edition and SAP S/4HANA) to extension applications through event-driven architecture. It is a fully managed [centralised event-oriented](https://help.sap.com/docs/event-mesh/event-mesh/event-mesh-default-plan-concepts?locale=en-US "https://help.sap.com/docs/event-mesh/event-mesh/event-mesh-default-plan-concepts?locale=en-US") service part of SAP BTP.
 
 > [!IMPORTANT]
-> SAP Event Mesh is intended to move into SAP Integration Suite, as a new capability, in Q2 2024. You can find more details in [https://roadmaps.sap.com](https://roadmaps.sap.com/board?PRODUCT=000D3A47875C1EDB98A8A910864AC24B&range=FIRST-LAST#;INNO=C1FBB5A935A51EDDA5E7942074F76CBC).
+> Event Mesh is now a capability part of SAP Integration Suite, you can find more details about the new capability here - [https://community.sap.com/t5/technology-blogs-by-sap/meet-your-new-friend-emis-event-mesh-in-sap-integration-suite/ba-p/13731129](https://community.sap.com/t5/technology-blogs-by-sap/meet-your-new-friend-emis-event-mesh-in-sap-integration-suite/ba-p/13731129). The standalone version - SAP Event Mesh - is still available to customer in CPEA contracts.
 
 ![event-mesh-diagram.png](assets/event-mesh-diagram.png "event-mesh-diagram.png")
 
-The [service supports the use of REST APIs for Events](https://help.sap.com/docs/event-mesh/event-mesh/rest-apis-for-events?locale=en-US "https://help.sap.com/docs/event-mesh/event-mesh/rest-apis-for-events?locale=en-US"), for publishing and consuming events that are compliant with the CloudEvents specification. Related to event-based integrations, events that flow through SAP Event Mesh between SAP applications must all conform to the CloudEvents specification.
+The [service supports the use of REST APIs for Events](https://help.sap.com/docs/integration-suite/sap-integration-suite/publish-and-consume-events "https://help.sap.com/docs/integration-suite/sap-integration-suite/publish-and-consume-events"), for publishing and consuming events that are compliant with the CloudEvents specification. Related to event-based integrations, events that flow through EMIS between SAP applications must all conform to the CloudEvents specification.
 
 > You can check out how to enable the consumption of SAP S/4HANA Cloud public edition events in your SAP BTP account - [https://youtu.be/4LspIL3NxqQ](https://youtu.be/4LspIL3NxqQ "https://youtu.be/4LspIL3NxqQ")
 
@@ -146,7 +146,7 @@ AEM offers these categories of services:
 
 * **Event Monitoring and Insights**: Availability out-of-the-box of dashboards and easy-to-understand visualizations based on historical and real-time metrics, and timely notifications about the event broker services deployed.
 
-Similar to SAP Event Mesh, it can be used to publish and consume business events from SAP and non-SAP sources across hybrid landscapes. Meaning, if your event data needs to exit the SAP cloud world, you can use any of these two services.
+Similar to the Event Mesh capability in SAP Integration Suite, it can be used to publish and consume business events from SAP and non-SAP sources across hybrid landscapes. Meaning, if your event data needs to exit the SAP cloud world, you can use any of these two services.
 
 ## Summary
 

exercises/09-rest-delivery-points/README.md

@@ -4,15 +4,15 @@ Now that we are familiar with the SAP Integration Suite, advanced event mesh, ho
 
 ![Final data flow](assets/diagrams/final-diagram.png)
 
-There are scenarios where the target system/application can't consume messages directly from an event broker but we still want these systems/applications to be part of our event-driven world and react to events as they are produced. Fortunately, some of these systems might expose APIs (REST endpoints) through which we can notify them of an event. For these cases, we can leverage REST Delivery Points to forward messages from a queue to that system. For example, the integration between SAP S/4HANA Cloud and SAP Build Process Automation goes through SAP Event Mesh. In SAP Event Mesh we end up configuring a [webhook subscription](https://help.sap.com/docs/event-mesh/event-mesh/manage-webhook-subscriptions) to [forward the events received and start a process](https://help.sap.com/docs/build-process-automation/sap-build-process-automation/create-event-triggers) in SAP Build Process Automation.
+There are scenarios where the target system/application can't consume messages directly from an event broker but we still want these systems/applications to be part of our event-driven world and react to events as they are produced. Fortunately, some of these systems might expose APIs (REST endpoints) through which we can notify them of an event. For these cases, we can leverage REST Delivery Points to forward messages from a queue to that system. For example, the integration between SAP S/4HANA Cloud and SAP Build Process Automation goes through SAP Event Mesh. In SAP Event Mesh we end up configuring a [webhook subscription](https://help.sap.com/docs/event-mesh/event-mesh/manage-webhook-subscriptions) to [forward the events received and start a process](https://help.sap.com/docs/build-process-automation/sap-build-process-automation/create-event-triggers) in SAP Build Process Automation. Also, it is now possible to configure this scenario in the Event Mesh capability part of SAP Integration Suite.
 
 > [!TIP]
 > It is now also possible to configure a REST Delivery Point in SAP Integration Suite, advanced event mesh to forward messages from a queue to SAP Build Process Automation and trigger a process. You can check out this [SAP Tech Bytes: SAP S/4HANA Cloud + SAP Integration Suite, AEM + SAP Build Process Automation](https://community.sap.com/t5/application-development-blog-posts/sap-tech-bytes-sap-s-4hana-cloud-sap-integration-suite-aem-sap-build/ba-p/13706661).
 
 If you remember the CodeJam's [integration scenario](../../../README.md#integration-scenario), we have an SAP S/4HANA Cloud System that generates events whenever a performer is added to the system (BusinessPartner) and we would like to trigger the "*Performer requirement checks*" process in SAP Build Process Automation. Although we will not be creating a process/interacting with SAP Build Process Automation in this CodeJam, it is important to understand the mechanism available to forward events to systems that expose REST endpoints. Therefore, we will forward messages from a queue to a REST consumer similar to how we would do it if we would like to forward the message to SAP Build Process Automation. From now on, we will refer to these types of systems as **REST consumers**.
 
 > [!TIP]
-> If you are interested in exploring how you can configure the webhook subscription mentioned above in SAP Event Mesh, you can check out this [SAP Tech Bytes: Deliver events from SAP EventMesh to SAP Build Process Automation](https://community.sap.com/t5/technology-blogs-by-sap/sap-tech-bytes-deliver-events-from-sap-eventmesh-to-sap-build-process/ba-p/13574547).
+> If you are interested in exploring how you can configure the webhook subscription mentioned above in the Event Mesh capability of SAP Integration Suite, you can check out the documentation here: [https://help.sap.com/docs/integration-suite/sap-integration-suite/create-webhook-subscription](https://help.sap.com/docs/integration-suite/sap-integration-suite/create-webhook-subscription).
 
 By the end of this exercise, we will achieve a communication scenario like the one below.