Update from SAP DITA CMS (squashed):

commit e28e8e39f2915856fb582b46295a00d53cd3e074
Author: REDACTED
Date:   Wed Apr 30 11:16:53 2025 +0000

    Update from SAP DITA CMS 2025-04-30 11:16:53

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

commit a370b995989e267348eb77147b3253355e48f8e5
Author: REDACTED
Date:   Wed Apr 30 07:26:02 2025 +0000

    Update from SAP DITA CMS 2025-04-30 07:26:02

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

commit 26db0e7c301efb70a4b19c59676f1045cdc40dc8
Author: REDACTED
Date:   Wed Apr 30 07:08:50 2025 +0000

    Update from SAP DITA CMS 2025-04-30 07:08:50

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

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

Author: ditaccms-bot

docs/10-concepts/kyma-cli-292454b.md

@@ -60,7 +60,7 @@ Kyma CLI provides the following features:
 **Related Information**  
 
 
-[Adding and Deleting a Kyma Module Using Kyma CLI](../50-administration-and-ops/adding-and-deleting-a-kyma-module-1b548e9.md#loio5a3666c015fb476b8b94b8abcbe9a17d "Use Kyma CLI to add and delete a Kyma module.")
+[Adding and Deleting a Kyma Module](../50-administration-and-ops/adding-and-deleting-a-kyma-module-1b548e9.md#loio1b548e9ad4744b978b8b595288b0cb5c "To use a Kyma module, you must add it first. Use Kyma dashboard or Kyma CLI to do that. If you don't need the module anymore, delete it to save resources.")
 
-[Setting Your Module to the Unmanaged and Managed State in Kyma CLI](../50-administration-and-ops/setting-your-module-to-the-unmanaged-and-managed-state-c071680.md#loio2a0ba7160e5145688f1b8cc21f89651d "Use Kyma CLI to set your module to the unmanaged state.")
+[Setting Your Module to the Unmanaged and Managed State](../50-administration-and-ops/setting-your-module-to-the-unmanaged-and-managed-state-c071680.md#loioc07168072c8340ecbb392260cf52c165 "In some cases, for example, for testing, you may need to modify your module beyond what is supported by its configuration. By default, when a module is in the managed state, Kyma Control Plane governs its Kubernetes resources, reverting any manual changes during the next reconciliation loop. To modify Kubernetes objects directly without them being reverted, you must set the module to the unmanaged state. In this state, reconciliation is disabled, ensuring your manual changes are preserved.")
 

docs/10-concepts/kyma-dashboard-482ae2f.md

@@ -36,7 +36,7 @@ You can use Kyma dashboard to perform the following actions:
 
 [Adding and Deleting a Kyma Module](../50-administration-and-ops/adding-and-deleting-a-kyma-module-1b548e9.md#loio1b548e9ad4744b978b8b595288b0cb5c "To use a Kyma module, you must add it first. Use Kyma dashboard or Kyma CLI to do that. If you don't need the module anymore, delete it to save resources.")
 
-[Setting Your Module to the Unmanaged and Managed State using Kyma Dashboard](../50-administration-and-ops/setting-your-module-to-the-unmanaged-and-managed-state-c071680.md#loiod281d803c7d946f4adcc28ee72700119 "Use Kyma dashboard to set your module to the unmanaged state.")
+[Setting Your Module to the Unmanaged and Managed State](../50-administration-and-ops/setting-your-module-to-the-unmanaged-and-managed-state-c071680.md#loioc07168072c8340ecbb392260cf52c165 "In some cases, for example, for testing, you may need to modify your module beyond what is supported by its configuration. By default, when a module is in the managed state, Kyma Control Plane governs its Kubernetes resources, reverting any manual changes during the next reconciliation loop. To modify Kubernetes objects directly without them being reverted, you must set the module to the unmanaged state. In this state, reconciliation is disabled, ensuring your manual changes are preserved.")
 
 [Using RBAC Authorization](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)
 

docs/10-concepts/regions-and-api-endpoints-for-the-abap-environment-879f373.md

@@ -980,6 +980,53 @@ Google Cloud
 </td>
 <td valign="top">
 
+br30
+
+</td>
+<td valign="top">
+
+Brazil \(São Paulo\)
+
+</td>
+<td valign="top">
+
+cf-br30
+
+</td>
+<td valign="top">
+
+southamerica-east1
+
+</td>
+<td valign="top">
+
+34.95.137.184, 35.247.201.68, 34.39.150.8, 35.247.226.31, 34.95.150.147, 34.95.207.43
+
+</td>
+<td valign="top">
+
+api.cf.br30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+br30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://amer.cockpit.btp.cloud.sap/](https://amer.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
 eu30
 
 </td>
@@ -1074,6 +1121,53 @@ Google Cloud
 </td>
 <td valign="top">
 
+jp30
+
+</td>
+<td valign="top">
+
+Japan \(Osaka\)
+
+</td>
+<td valign="top">
+
+cf-jp30
+
+</td>
+<td valign="top">
+
+asia-northeast2
+
+</td>
+<td valign="top">
+
+34.97.109.65, 34.97.169.121, 34.97.118.229, 34.97.49.120, 34.97.5.235, 34.97.12.103
+
+</td>
+<td valign="top">
+
+api.cf.jp30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+jp30.hana.ondemand.com
+
+</td>
+<td valign="top">
+
+[https://apac.cockpit.btp.cloud.sap/](https://apac.cockpit.btp.cloud.sap/)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+Google Cloud
+
+</td>
+<td valign="top">
+
 us30
 
 </td>

docs/10-concepts/commercial-information-for-sap-btp-abap-environment-b7f5a93.md renamed to docs/10-concepts/service-plans-and-metering-for-sap-btp-abap-environment-b7f5a93.md

@@ -1,6 +1,6 @@
 <!-- loiob7f5a93ce3804963ab7fd547f3c4fdf9 -->
 
-# Commercial Information for SAP BTP ABAP environment
+# Service Plans and Metering for SAP BTP ABAP environment
 
 This page explains the relationship between the service plans of the SAP Discovery Center and the service plans of the SAP BTP cockpit and provides information to help you understand how the service is billed.
 

docs/30-development/api-gateway-module-f323ab1.md

@@ -72,6 +72,8 @@ The `apigateways.operator.kyma-project.io` CRD describes the APIGateway CR that
 
 The `apirules.operator.kyma-project.io` CRD describes the APIRule CR that APIRule Controller uses to expose and secure APIs. See [APIRule Custom Resource](https://kyma-project.io/#/api-gateway/user/custom-resources/apirule/README).
 
+The `ratelimits.gateway.kyma-project.io` CRD describes the kind and the format of data that RateLimit Controller uses to configure the request rate limits for applications. See [RateLimit Custom Resource](https://kyma-project.io/#/api-gateway/user/custom-resources/ratelimit/04-00-ratelimit).
+
 
 
 <a name="loiof323ab16595a47779bc74344969c0133__section_u2c_qr2_qbc"/>

docs/30-development/configuring-istio-access-logs-d3f20b6.md

@@ -2,7 +2,7 @@
 
 # Configuring Istio Access Logs
 
-Use the Telemetry API to selectively enable the Istio access logs.
+Use the Telemetry API to selectively enable the Istio access logs and filter them if needed.
 
 
 
@@ -11,7 +11,7 @@ Use the Telemetry API to selectively enable the Istio access logs.
 ## Prerequisites
 
 -   You have the Istio module added. See [Adding and Deleting a Kyma Module](../50-administration-and-ops/adding-and-deleting-a-kyma-module-1b548e9.md#loio1b548e9ad4744b978b8b595288b0cb5c).
--   To use CLI instructions, you must install [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) and [curl](https://curl.se/). Alternatively, you can use Kyma dashboard.
+-   You have access to Kyma dashboard. Alternatively, to use CLI instructions, you must install [kubectl](https://kubernetes.io/docs/tasks/tools/#kubectl) and [curl](https://curl.se/).
 
 
 
@@ -31,7 +31,7 @@ extensionProviders:
           tracestate: "%REQ(TRACESTATE)%"
 ```
 
-The [log format](https://github.com/kyma-project/istio/blob/main/internal/istiooperator/istio-operator.yaml#L160) is based on the Istio default format enhanced with the attributes relevant for identifying the related trace context conforming to the [w3c-tracecontext](https://www.w3.org/TR/trace-context/) protocol. See [Traces](traces-f98cda5.md) for details. See [Istio tracing](https://kyma-project.io/#/telemetry-manager/user/03-traces?id=istio) on how to enable trace context propagation with Istio.
+The [log format](https://github.com/kyma-project/istio/blob/main/internal/istiooperator/istio-operator.yaml#L160) is based on the Istio default format enhanced with the attributes relevant for identifying the related trace context conforming to the [w3c-tracecontext](https://www.w3.org/TR/trace-context/) protocol. To learn how to enable trace context propagation with Istio, see [Kyma Modules with Tracing Capabilities: Istio](traces-f98cda5.md#loiof98cda5d058e48ff808ade541a64a6ad__subsection_traces_istio).
 
 > ### Caution:  
 > Enabling access logs may drastically increase logs volume and quickly fill up your log storage.
@@ -179,7 +179,7 @@ To configure label-based selection of workloads, use a [selector](https://istio.
 
 <!-- task\_et1\_wnf\_scc -->
 
-## Configuring Istio Access Logs for a Selecitve Gateway
+## Configuring Istio Access Logs for a Selective Gateway
 
 Instead of enabling the access logs for all the individual proxies of the workloads you have, you can enable the logs for the proxy used by the related Istio Ingress Gateway.
 
@@ -313,3 +313,29 @@ Enable access logs for all individual proxies of all your workloads and Istio In
 
 
 
+<a name="concept_gbq_rz4_s2c"/>
+
+<!-- concept\_gbq\_rz4\_s2c -->
+
+## Filtering Access Logs
+
+To filter the enabled access logs, you can edit the Telemetry API by adding a filter expression.
+
+Often, access logs emitted by Envoy do not contain data relevant to your observations, especially when the traffic is not based on an HTTP-based protocol. In such a situation, you can directly configure the Istio Envoys to filter out logs using a filter expression. To filter access logs, you can leverage the same [Istio Telemetry API](https://istio.io/latest/docs/reference/config/telemetry/#AccessLogging) that you used to enable them. To formulate which logs to **keep**, define a filter expression leveraging the typical [Envoy attributes](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/advanced/attributes).
+
+For example, to filter out all logs having no protocol defined \(which is the case if they are not HTTP-based\), you can use a configuration similar to this example:
+
+```
+apiVersion: telemetry.istio.io/v1
+kind: Telemetry
+metadata:
+ name: access-config
+ namespace: istio-system
+spec:
+ accessLogging:
+ - filter:
+     expression: 'has(request.protocol)'
+   providers:
+   - name: stdout-json
+```
+

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-service-keys-4514a14.md

@@ -6,7 +6,7 @@ You can use service keys to generate credentials to communicate directly with a
 
 You can usethe SAP BTP cockpit or the Cloud Foundry Command Line Interface to create service keys:
 
--   [Creating Service Keys Using the Cockpit](https://help.sap.com/docs/service-manager/sap-service-manager/creating-service-keys-in-cloud-foundry)
+-   [Create Service Keys Using the Cockpit](create-service-keys-using-the-cockpit-cdf4f20.md)
 
 -   [Create Service Keys Using the Cloud Foundry Command Line Interface](create-service-keys-using-the-cloud-foundry-command-line-interface-7de6b31.md)
 

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/customizing-the-default-credentials-and-access-15f22d5.md

@@ -65,7 +65,9 @@ data:
 
 ## Results
 
-Your customized `sap-btp-manager` Secret is now the default Secret of the SAP BTP Operator module. It generates the SAP BTP service operator's resources, as shown in the following diagram:![](images/Customized_Module_Credentials_412b368.png)
+Your customized `sap-btp-manager` Secret is now the default Secret of the SAP BTP Operator module. It generates the SAP BTP service operator's resources, as shown in the following diagram:
+
+![](images/Customized_Module_Credentials_412b368.png)
 
 The reconciliation of the Secret stops and your changes are not reverted.
 

docs/30-development/enable-on-premise-connectivity-9b6510e.md

@@ -16,18 +16,25 @@ Create an HTTP and an RFC destination to enable communication from the ABAP envi
 
 -   If you want to use principal propagation as authentication type, the Cloud Connector must be configured to support this authentication type. See [Cloud Connector: Configuring Principal Propagation](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/c84d4d0b12d34890b334998185f49e88.html).
 
-    Also, make sure that no communication arrangement to the deprecated communication scenario SAP\_COM\_0200 exists.
+    Also, make sure that no communication arrangement to the deprecated communication scenario `SAP_COM_0200` exists.
 
--   If you use more than one Cloud Connector in your subaccount, you have assigned a location ID to each of these Cloud Connectors. See [Managing Subaccounts](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/f16df12fab9f4fe1b8a4122f0fd54b6e.html) \(section **Procedure**, step 4\).
+-   If you use more than one Cloud Connector in your subaccount, you have assigned a location ID to each of these Cloud Connectors. See [Managing Subaccounts](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/f16df12fab9f4fe1b8a4122f0fd54b6e.html).
 
 
 
 <a name="loio9b6510edf4d844a28f022b3db41f3202__section_p43_dm3_43b"/>
 
 ## Procedure
 
-To enable on-premise connectivity, you must set up or reuse an HTTP destination or an RFC destination with *<Proxy Type\>* `OnPremise`:
+To enable on-premise connectivity, you must use the Cloud Connector in your communication system:
 
--   [Create HTTP Destinations](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/create-http-destinations?version=Cloud)
--   [Create RFC Destinations](https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/create-rfc-destinations?version=Cloud)
+-   [Creating a Communication System for Outbound HTTP](https://help.sap.com/docs/abap-cloud/abap-integration-connectivity/create-communication-system-for-outbound-http?version=sap_btp)
+-   [Creating a Communication System for Outbound RFC](https://help.sap.com/docs/abap-cloud/abap-integration-connectivity/create-communication-system-for-outbound-rfc?version=sap_btp)
+
+**Related Information**  
+
+
+[Outbound Communication](https://help.sap.com/docs/abap-cloud/abap-integration-connectivity/outbound-communication-48d3624d9f7d47d7ab712d110cb02d77?version=sap_btp)
+
+[Communication System](https://help.sap.com/docs/abap-cloud/abap-integration-connectivity/communication-system?version=sap_btp)
 

docs/30-development/implementing-the-business-logic-99dcde1.md

@@ -26,7 +26,7 @@ The ABAP class mentioned here is considered the main class of each application j
 
 [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.")
 
 [Application Logs](application-logs-091bec9.md "You can use the Application Logs to display and check if any errors occurred during runtime.")
 

docs/30-development/integrating-on-premise-systems-c95327f.md

@@ -10,33 +10,30 @@ Set up the Cloud Connector to enable communication from the ABAP environment to
 
 ## Concept
 
-For each subaccount, both a default Connectivity and Destination service instance are set up automatically in the SAP provider account. Using these default instances, you only need to configure the required destinations on subaccount level to enable communication to your on-premise systems.
+For each subaccount, a Connectivity service instance is set up automatically in the SAP provider account. To use this instance, activate the Cloud Connector in your communication system.
 
-In this default scenario, you must connect the Cloud Connector to and configure trust for your Cloud Foundry subaccount as described in [SAP BTP Connectivity: Cloud Connector](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e6c7616abb5710148cfcf3e75d96d596.html).
+In this scenario, you must connect the Cloud Connector to and configure trust for your Cloud Foundry subaccount as described in [SAP BTP Connectivity: Cloud Connector](https://help.sap.com/viewer/cca91383641e40ffbe03bdc78f00f681/Cloud/en-US/e6c7616abb5710148cfcf3e75d96d596.html).
 
 > ### Restriction:  
-> This scenario requires a Cloud Connector as of version 2.12.3.
-
-The host name of the Cloud Connector is not needed because the Cloud Connector itself connects **to the Cloud**, but it is **never connected from the Cloud**.
+> This scenario requires a Cloud Connector as of version 2.12.3 or higher.
 
 > ### Note:  
 > For more information on the deprecated scenario that uses the Connectivity service in the Neo environment, see [Create a Communication Arrangement for Cloud Connector Integration \(Deprecated\)](create-a-communication-arrangement-for-cloud-connector-integration-deprecated-16c9c3d.md).
 
 After you have completed the setup, a connection from the ABAP environment tenant to an on-premise system is established in the following order:
 
-1.  The ABAP environment tenant fetches the destination from the Destination service instance.
-2.  The ABAP environment tenant requests to open the tunnel connection through the Connectivity service.
-3.  The Connectivity service tells the Cloud Connector to open the connection to this specific ABAP environment tenant using the admin connection.
-4.  The Cloud Connector opens a tunnel connection to the ABAP environment tenant using its public tenant URL.
-5.  After the tunnel is established, it can be used for actual data connection using RFC and HTTP\(S\) protocols.
+1.  The ABAP environment tenant requests to open the tunnel connection through the Connectivity service.
+2.  The Connectivity service tells the Cloud Connector to open the connection to this specific ABAP environment tenant using the admin connection.
+3.  The Cloud Connector opens a tunnel connection to the ABAP environment tenant using its public tenant URL.
+4.  After the tunnel is established, it can be used for actual data connection using RFC and HTTP\(S\) protocols.
 
 
 
 <a name="loioc95327fbed6c4efeb1855f12f826301d__section_szl_1qb_smb"/>
 
 ## Next Steps
 
-To set up your actual data connections between your ABAP environment and on-premise systems, you must configure the required destinations. See [Enable On-Premise Connectivity](enable-on-premise-connectivity-9b6510e.md).
+To set up your actual data connections between your ABAP environment and on-premise systems, you must enable the required Cloud Connector in your communication system. See [Enable On-Premise Connectivity](enable-on-premise-connectivity-9b6510e.md).