Update from SAP DITA CMS (squashed):

commit fcb6ec37fe1e605b9d8438b5e7d026db35facb2c
Author: REDACTED
Date:   Fri Nov 21 10:37:28 2025 +0000

    Update from SAP DITA CMS 2025-11-21 10:37:28

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 391f06db2ac1cfcc19465a7c85126864d5b90a1d
Author: REDACTED
Date:   Fri Nov 21 10:04:27 2025 +0000

    Update from SAP DITA CMS 2025-11-21 10:04:27

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loio2080d0faf9d84ce6aa14caa4caa32935
    Language: en-US
    Builddable map: 0fcfe38e11674227bb0a8d014337319b.ditamap

commit 684b7875f9f468d34beefdb6adbcd80fea503916
Author: REDACTED
Date:   Fri Nov 21 09:31:21 2025 +0000

    Update from SAP DITA CMS 2025-11-21 09:31:21

    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap

##################################################
[Remaining squash message was removed before commit...]

Author: ditaccms-bot

docs/10-concepts/kyma-modules-0dda141.md

@@ -208,8 +208,7 @@ At the moment, the SAP Event Mesh default plan and NATS are supported. If you ch
 </td>
 <td valign="top">
 
--   [Configure SAP Event Mesh for Kyma Eventing](../30-development/configure-sap-event-mesh-for-kyma-eventing-407d126.md)
--   [kyma-project.io: Eventing module](https://kyma-project.io/#/eventing-manager/user/README)
+-   [Eventing Module](../30-development/eventing-module-07b2d1d.md)
 -   [GitHub repository: Eventing](https://github.com/kyma-project/eventing-manager) 
 
 
@@ -252,7 +251,7 @@ NATS deploys a NATS cluster within the Kyma cluster. You can use it as a backend
 </td>
 <td valign="top">
 
--   [kyma-project.io: NATS module](https://kyma-project.io/#/nats-manager/user/README)
+-   [NATS Module](../30-development/nats-module-2c504f5.md)
 -   [GitHub repository: NATS](https://github.com/kyma-project/nats-manager)
 
 

docs/10-concepts/payment-card-industry-data-security-standard-in-the-kyma-environment-1ece56b.md

@@ -0,0 +1,16 @@
+<!-- loio1ece56b2b5854a91a2c8f32c1db17fb8 -->
+
+# Payment Card Industry Data Security Standard in the Kyma Environment
+
+Payment Card Industry Data Security Standard \(PCI DSS\) ensures businesses protect cardholder data, and SAP BTP Kyma runtime's compliance attestation confirms its security measures.
+
+[PCI DSS](https://www.pcisecuritystandards.org/standards/pci-dss/) is a set of rules and requirements for businesses that store, process, or transmit payment card information, designed to protect cardholder data from fraud. SAP BTP, Kyma runtime holds the PCI DSS Attestation of Compliance \(AoC\) v4.0.1. The AoC defines how Kyma is compliant with the PCI standard. To request a copy of SAP Business Technology Platform Kyma Runtime 2025 PCI DSS AoC Report, visit [SAP Trust Center](https://www.sap.com/about/trust-center/certification-compliance/sap-btp-kyma-runtime-pci-2025.html).
+
+
+
+## Responsibility Matrix
+
+Kyma, as a PCI service provider, defines the scope of responsibilities. Some responsibilities belong to Kyma, some to you as a customer, and some are shared.
+
+To view the Responsibility Matrix, request access using the support procedure. To get support, report a case in SAP for Me using the Kyma support component: BC-CP-XF-KYMA. For more information, see  <?sap-ot O2O class="- topic/xref " href="948d2ff28da847739fda67cd8cd1f1d4.xml" text="" desc="" xtrc="xref:3" xtrf="file:/home/builder/src/dita-all/jjq1673438782153/loio2080d0faf9d84ce6aa14caa4caa32935_en-US/src/content/localization/en-us/1ece56b2b5854a91a2c8f32c1db17fb8.xml" output-class="" outputTopicFile="file:/home/builder/tp.net.sf.dita-ot/2.3/plugins/com.elovirta.dita.markdown_1.3.0/xsl/dita2markdownImpl.xsl" ?> .
+

docs/30-development/accessing-the-nats-server-using-cli-8eefbd5.md

@@ -0,0 +1,51 @@
+<!-- loio8eefbd54171c492b89ffe855344a04ef -->
+
+# Accessing the NATS Server Using CLI
+
+Interact directly with your NATS server deployment in Kyma using the NATS command-line interface \(CLI\). Use the CLI to inspect server status, manage streams and consumers, and troubleshoot message flow.
+
+
+
+<a name="loio8eefbd54171c492b89ffe855344a04ef__prereq_d52_gvs_dhc"/>
+
+## Prerequisites
+
+-   You have installed kubectl and [NATS CLI](https://github.com/nats-io/natscli).
+
+
+
+## Context
+
+Accessing certain resources in NATS requires [system account privileges](https://docs.nats.io/running-a-nats-service/configuration/sys_accounts). Kyma automatically generates a `system account` user using a Secret named `eventing-nats-secret` in the `kyma-system` namespace.
+
+
+
+## Procedure
+
+1.  Get the credentials. Run:
+
+    ```
+    kubectl get secrets -n kyma-system eventing-nats-secret -ogo-template='{{index .data "resolver.conf"|base64decode}}'| grep 'user:'| tr -d '{}'
+    ```
+
+    If you changed the default NATS instance name from `eventing-nats`, replace `eventing-nats-secret` with `{your_NATS_CR_name}-secret`.
+
+    You receive the credentials for the `system account` user in the following format:
+
+    ```
+    user: admin, password: <your password>
+    ```
+
+2.  To access the NATS server with the NATS CLI tool, forward its port:
+
+    ```
+    kubectl port-forward -n kyma-system svc/eventing-nats 4222
+    ```
+
+3.  To send your NATS commands, pass the credentials:
+
+    ```
+    nats server info --user admin --password <your password>
+    ```
+
+

docs/30-development/choose-an-eventing-backend-08dfcdc.md

@@ -59,18 +59,8 @@ If you want to choose another backend, edit the `Eventing` resource again, selec
 
 You can no longer return to an empty eventing backend.
 
-
-
-<a name="loio08dfcdcaf4ff4914b70c8173731a9188__postreq_i2m_jms_5zb"/>
-
-## Next Steps
-
-Learn more about the [Eventing Module](https://kyma-project.io/#/eventing-manager/user/README).
-
 **Related Information**  
 
 
-[Configure SAP Event Mesh for Kyma Eventing](configure-sap-event-mesh-for-kyma-eventing-407d126.md "If you want to use SAP Event Mesh as backend for the Eventing module, you must first set up the credentials.")
-
 [SAP Event Mesh](https://help.sap.com/viewer/product/SAP_EM/Cloud/en-US)
 

docs/30-development/creating-a-job-catalog-entry-and-a-job-template-949ba00.md

@@ -22,5 +22,5 @@ Follow these steps to run your business coding in an application job.
 **Related Information**  
 
 
-[Setting up the Authorizations](setting-up-the-authorizations-bb559a5.md "Some further activities in ABAP development tools for Eclipse and in the administrator’s launchpad are necessary to be able to schedule the job template in the Fiori app Application Jobs.")
+[Setting up the Authorizations](setting-up-the-authorizations-bb559a5.md "Some further activities in ADT and in the administrator’s launchpad are necessary to be able to schedule the job template in the Fiori app Application Jobs.")
 

docs/30-development/creating-the-job-catalog-entry-1cff59e.md

@@ -13,5 +13,5 @@ Job catalog entries and job templates are created with a package assignment and
 
 [Creating the Job Template](creating-the-job-template-1f04ad2.md "")
 
-[Setting up the Authorizations](setting-up-the-authorizations-bb559a5.md "Some further activities in ABAP development tools for Eclipse and in the administrator’s launchpad are necessary to be able to schedule the job template in the Fiori app Application Jobs.")
+[Setting up the Authorizations](setting-up-the-authorizations-bb559a5.md "Some further activities in ADT and in the administrator’s launchpad are necessary to be able to schedule the job template in the Fiori app Application Jobs.")
 

docs/30-development/creating-the-job-template-1f04ad2.md

@@ -9,5 +9,5 @@ The creation of a job template follows the same technical rules as a *Job Catalo
 **Related Information**  
 
 
-[Setting up the Authorizations](setting-up-the-authorizations-bb559a5.md "Some further activities in ABAP development tools for Eclipse and in the administrator’s launchpad are necessary to be able to schedule the job template in the Fiori app Application Jobs.")
+[Setting up the Authorizations](setting-up-the-authorizations-bb559a5.md "Some further activities in ADT and in the administrator’s launchpad are necessary to be able to schedule the job template in the Fiori app Application Jobs.")
 

docs/30-development/deploy-workloads-in-the-kyma-environment-to-extend-sap-systems-fe4ba5b.md

@@ -52,7 +52,7 @@ Follow these steps to get familiar with workloads and learn how to use them.
 
 1.  Connect the SAP system you want to extend \([Extending SAP Solutions Using Automated Configurations](https://help.sap.com/docs/BTP/65de2977205c403bbc107264b8eccf4b/346864df64f24011b49abee07bbd79af.html)\).
 
-2.  Choose a namespace in your cluster and create a simple Function \([Create an Inline Function](https://kyma-project.io/#/serverless-manager/user/tutorials/01-10-create-inline-function)\) or a microservice \([Create a Workload](https://kyma-project.io/#/api-gateway/user/tutorials/01-00-create-workload)\).
+2.  Choose a namespace in your cluster and create a simple Function \([Create an Inline Function](https://kyma-project.io/external-content/serverless/docs/user/tutorials/01-10-create-inline-function)\) or a microservice.
 
 3.  If you want to expose your workload outside the cluster, read [Expose a Workload](https://kyma-project.io/#/api-gateway/user/tutorials/01-40-expose-workload/01-40-expose-workload-apigateway).
 
@@ -78,5 +78,5 @@ Follow these steps to get familiar with workloads and learn how to use them.
 **Related Information**  
 
 
-[Kyma: Serverless](https://kyma-project.io/#/serverless-manager/user/README)
+[Serverless Module](serverless-module-eb84ff5.md "Learn more about the Serverless module. Use it to run lightweight Functions in a cost-efficient and scalable way using JavaScript and Node.js.")
 

docs/30-development/event-naming-and-cleanup-97f5d77.md

@@ -0,0 +1,56 @@
+<!-- loio97f5d77d27af4f5a91c98a5502975de6 -->
+
+# Event Naming and Cleanup
+
+The Eventing module uses event names to identify and route events to subscribers. Learn about the supported event types, the naming conventions, and how the Eventing module handles event names with prohibited characters.
+
+
+
+<a name="loio97f5d77d27af4f5a91c98a5502975de6__section_event_types"/>
+
+## Event Types
+
+Event names depend on the type of event. Eventing supports the following event types:
+
+-   CloudEvents: Events that conform to the [CloudEvents specification](https://cloudevents.io/). This is the recommended standard for describing event data in a common way. The specification is currently under the [CNCF](https://www.cncf.io/).
+-   Legacy events: Events or messages published to Kyma that do not conform to the CloudEvents specification. The Eventing Publisher Proxy converts all legacy events into CloudEvents before processing them.
+
+
+
+<a name="loio97f5d77d27af4f5a91c98a5502975de6__section_event_name_format"/>
+
+## Event Name Format
+
+The event name format ensures compatibility with CloudEvents specifications and underlying messaging backends.
+
+For a Subscription custom resource \(CR\), the fully qualified event name follows a structure like `order.created.v1` or `Account.Root.Created.v1`.
+
+An event type consists of the following components:
+
+-   Event: Typically, has two or three segments separated by a dot \(`.`\); for example, `order.created` or `Account.Root.Created`
+-   Version: A version identifier, typically `v1`
+
+For publishers, the event type takes these sample forms:
+
+-   `order.created` or `Account.Root.Created` for legacy events coming from the `commerce` application
+-   `order.created.v1` or `Account.Root.Created.v1` for CloudEvents
+
+
+
+<a name="loio97f5d77d27af4f5a91c98a5502975de6__section_event_name_cleanup"/>
+
+## Event Name Cleanup
+
+The Eventing Publisher Proxy modifies event names to filter out prohibited characters. This ensures compliance with CloudEvents specifications and the underlying messaging backend \(such as [NATS JetStream specifications](https://docs.nats.io/running-a-nats-service/nats_admin/jetstream_admin/naming)\).
+
+If an event name contains prohibited characters, the Eventing Publisher Proxy removes these characters and uses the cleaned name for internal processing and routing. For example, if an event type is `order.payment*success.v1`, the Eventing module cleans it to `order.paymentsuccess.v1`.
+
+To check the Subscription's cleaned event type, run: `kubectl get subscriptions {SUBSCRIPTION_NAME} -o=jsonpath="{.status.types}"`
+
+This cleanup happens internally; you can still publish and subscribe using the original event names \(with prohibited characters\). However, the Eventing module processes the cleaned version.
+
+> ### Caution:  
+> This can lead to a naming collision if two different original event names clean up to the same internal name. For example, both `system>prod` and `systemprod` become `systemprod`. While this does not result in an error, a naming collision can cause subscribers to receive irrelevant events or miss expected events. For details, see [Subscriber Receives Irrelevant Events](subscriber-receives-irrelevant-events-d4f3166.md).
+
+When you verify event delivery in your Function logs, the received event type reflects the cleaned name, not the original name you defined in the `Subscription` or published with.
+

docs/30-development/eventing-module-07b2d1d.md

@@ -0,0 +1,96 @@
+<!-- loio07b2d1db518b441780d1ea981eb77bb9 -->
+
+# Eventing Module
+
+Use the Eventing module to set up event-driven communication between applications in your Kyma cluster using a publish-subscribe model.
+
+
+
+## What is Eventing?
+
+The Eventing module enables event-driven communication between applications in your Kyma cluster. One application publishes an event \(the publisher\), and other applications \(subscribers\) subscribe to receive it.
+
+This decouples your services, as publishers and subscribers don't need to know about each other. They can communicate asynchronously and evolve independently.
+
+
+
+## Features
+
+The Eventing module provides the following features:
+
+-   Publish-subscribe \(pub/sub\) messaging: Decouples applications so you can build resilient and scalable event-driven systems.
+-   Flexible backend support: Use the in-cluster NATS backend \(see [NATS Module](nats-module-2c504f5.md)\) or configure SAP Event Mesh \(see [SAP Event Mesh](https://help.sap.com/docs/SAP_EM/bf82e6b26456494cbdd197057c09979f/df532e8735eb4322b00bfc7e42f84e8d.html?version=LATEST&locale=en-US)\) for enterprise messaging.
+-   Standardized event format: All events follow the [CloudEvents](https://cloudevents.io/) specification, ensuring a consistent and portable format.
+-   Automatic legacy event conversion: Converts older, non-standard Kyma event formats into valid CloudEvents automatically. For details, see [Event Name Cleanup](event-naming-and-cleanup-97f5d77.md#loio97f5d77d27af4f5a91c98a5502975de6__section_event_name_cleanup).
+-   At-least-once delivery: Ensures that each event is delivered at least one time when you use the NATS backend, preventing message loss during temporary failures.
+-   Declarative subscriptions: Manage event subscriptions with a simple [Subscription](https://kyma-project.io/#/eventing-manager/user/resources/subscription-cr) custom resource \(CR\).
+-   Built-in observability: Exposes key health and performance metrics in Prometheus format \(see [Eventing Metrics](https://kyma-project.io/#/eventing-manager/user/evnt-eventing-metrics)\). Use the Telemetry module to collect, process, and forward these metrics to your observability backend.
+
+
+
+## Scope
+
+The Eventing module focuses on in-cluster, asynchronous communication using the CloudEvents standard. It uses only one stream, with `file` storage, for all the events.
+
+For cross-cluster or hybrid scenarios, configure SAP Event Mesh as the backend.
+
+
+
+## Architecture
+
+The Eventing module uses the Eventing Manager, a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/), to manage the components that process and deliver events within your cluster.
+
+The architecture involves the following flows:
+
+-   Subscription: The Eventing Manager watches for Subscription custom resources and configures the eventing infrastructure.
+-   Delivery: The Eventing Publisher Proxy receives events, and the configured backend \(NATS or SAP Event Mesh\) delivers them.
+
+![](images/Kyma_Eventing_Architecture_96d2a93.png)
+
+1.  You create a Subscription CR. In the resource manifest, you specify the type of event you want to receive and the sink where to send it.
+2.  The Eventing Manager, continuously watching for Subscription resources, detects your Subscription CR.
+3.  Based on the backend configured in the Eventing CR, the Eventing Manager connects to the backend \(NATS or SAP Event Mesh\) and creates a subscription mechanism \(a consumer or webhook\).
+4.  A publisher app sends an event to the Eventing Publisher Proxy.
+5.  The Eventing Publisher Proxy forwards the event in CloudEvents format to your eventing backend.
+6.  The eventing backend processes the event and pushes it to the Eventing Manager.
+7.  The Eventing Manager receives the event, looks up the sink from the Subscription CR, and sends the event to your subscriber app. Your application can now process the event payload.
+
+
+
+### Eventing Manager
+
+The Eventing Manager is the module's controller. It watches for Subscription custom resources and configures the underlying eventing infrastructure.
+
+When you create or update a Subscription, the Eventing Manager performs the following tasks:
+
+-   Configures the selected eventing backend to manage event streams and consumers for subscriptions.
+-   Ensures that events are routed from the correct publisher to the specified subscriber \(the sink\).
+-   Creates and manages Kubernetes resources, such as `ConfigMap`, `Services`, and `DestinationRules`, adapting them to the desired state.
+
+
+
+### Eventing Publisher Proxy
+
+The [Eventing Publisher Proxy](https://github.com/kyma-project/eventing-publisher-proxy) provides a single, stable endpoint for your applications to publish events using a standard HTTP POST request \(endpoint: `/publish` for CloudEvents and `<application_name>/v1/events` for legacy events\). This simplifies integration, as you can use common tools like curl or any standard HTTP client.
+
+The proxy performs the following tasks:
+
+-   Receives inbound events from your applications.
+-   Converts events from legacy formats into the standard CloudEvents format.
+-   Forwards validated CloudEvents to the configured eventing backend for delivery.
+
+
+
+## API/Custom Resource Definitions
+
+You configure the Eventing module by creating and applying Kubernetes Custom Resource Definitions \(CRD\), which extend the Kubernetes API with custom additions:
+
+-   To understand and configure the module's global settings, see the [Eventing CRD](https://kyma-project.io/#/eventing-manager/user/resources/eventing-cr).
+-   To create a subscriber, define a [Subscription CRD](https://kyma-project.io/#/eventing-manager/user/resources/subscription-cr). You cannot delete the Eventing module as long as Subscription CRs exist.
+
+
+
+## Resource Consumption
+
+To learn more about the resources used by the Eventing module, see [Kyma Modules' Sizing](../50-administration-and-ops/kyma-modules-sizing-3a92490.md).
+