Update from SAP DITA CMS (squashed):

commit f77db8d123b26704421a89dfcaa8ca7cae767f95
Author: REDACTED
Date:   Tue May 14 19:37:04 2024 +0000

    Update from SAP DITA CMS 2024-05-14 19:37:04
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

commit ca160b7856ad8ebf852875ad7d33205c82c47c5e
Author: REDACTED
Date:   Tue May 14 16:12:39 2024 +0000

    Update from SAP DITA CMS 2024-05-14 16:12:39
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

commit 45e0c1448cec39617d3412d3fec00d7b10127623
Author: REDACTED
Date:   Tue May 14 15:48:38 2024 +0000

    Update from SAP DITA CMS 2024-05-14 15:48:38
    Project: dita-all/jjq1673438782153
    Project map: c2f780f61c744155b0bd42b6f38fb70c.ditamap
    Output: loiob2927cc326be495da9f4fea0b6bda2b3
    Language: en-US
    Builddable map: c590d25af285407ba12a69179a940c19.ditamap

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

docs/1-connectivity-documentation/alerting-87bffd9.md

@@ -20,9 +20,9 @@ You must specify the receivers of the alert e-mails \(*E-mail Configuration*\) a
 2.  Enter the sender's e-mail address \(*<Sent From\>*\).
 3.  In *<SMTP Server\>* provide the host of the mail server.
 4.  You can specify an *<SMTP port\>*, if the server is not using the default ports. For details, contact your e-mail administrator or provider.
-5.  Mark the *TLS Enabled* check box if you want to establish a TLS-encrypted connection.
+5.  Mark the *TLS Enabled* check box if you want to establish a potential TLS-encrypted connection using STARTTLS.
 6.  If the SMTP server requires authentication, provide *<User\>* and *<Password\>*.
-7.  In the *Additional Properties* section you can provide any property supported by the [Java Mail library](https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html). All specified properties will be passed to the SMTP client.
+7.  In the *Additional Properties* section you can provide any property supported by the [Java Mail library](https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html). Additionally, you can set `mail.debug` to `true` in order to get SMTP protocol debug output. All specified properties will be passed to the SMTP client.
 8.  Select *Save* to change the current configuration.
 
 ![](images/SCC_Alerting_-_Email_0c3698f.png)

docs/1-connectivity-documentation/configure-identity-propagation-for-https-a8bb87a.md

@@ -100,10 +100,14 @@ Back to [Step](configure-identity-propagation-for-https-a8bb87a.md#loioa8bb87a72
     > -   `icm/HTTPS/trust_client_with_subject`: this is the subject of the system certificate \(example data: `CN=SCC`, `OU=BTP Scenarios`, `O=Trust Community`, `C=DE`\).
 
     > ### Caution:  
-    > The ICM expects *blanks after the separating comma* for the issuer and subject elements. So, even if the Cloud Connector administration UI shows a string without blanks, for example: *CN=SCC,OU=BTP Scenarios,O=Trust Community,C=DE*, you must specify in ICM: *CN=SCC, OU=BTP Scenarios, O=Trust Community, C=DE*.
+    > In all kernel releases below 7.53, the ICM expects *blanks after the separating comma* for the issuer and subject elements. Even if the Cloud Connector administration UI shows a string without blanks, for example: *CN=SCC,OU=BTP Scenarios,O=Trust Community,C=DE*, you must specify in ICM: *CN=SCC, OU=BTP Scenarios, O=Trust Community, C=DE*.
+    > 
+    > As of kernel release 7.53, this restriction does not exist any more. For more information, see SAP note [3335949](https://me.sap.com/notes/3335949).
 
     > ### Caution:  
-    > Make sure that `icm/HTTPS/verify_client` is set to either `1` \(request certificate\) or `2` \(require certificate\). If the parameter is set to `0`, trust cannot be established.
+    > Make sure the parameter `icm/server_port` you are using has the attribute `VCLIENT`=1 \(request certificate\) or 2 \(require certificate\). The default value is 1.
+    > 
+    > If `VCLIENT` is set to 0, trust cannot be established. In this case, you may change the value to 1, but beware that this may have a negative influence on the user experience. Alternatively, create a new parameter `icm/server_port` with `VCLIENT`=1 and configure the Cloud Connector to use this parameter.
 
 5.  Save the profile.
 6.  Open the *ICM Monitor* \(transaction `SMICM`\) and restart the ICM by choosing *Administration* \> *ICM* \> *Exit Hard* \> *Global*.

docs/1-connectivity-documentation/invoke-abap-function-modules-in-cloud-abap-systems-55c9d13.md

@@ -6,6 +6,9 @@ Call a function module in a cloud ABAP system via RFC, using a sample Web applic
 
 This scenario performs a remote function call to invoke an ABAP function module, by using the Destination service in the Cloud Foundry environment, as well as a Cloud Foundry application router.
 
+> ### Note:  
+> For more information on invoking ABAP function modules via WebSocket RFC in SAP BTP, ABAP environment, see tutorial [WebSocket RFC to Cloud](https://developers.sap.com/tutorials/abap-websocket-rfc.html).
+
 
 
 <a name="loio55c9d13251dd451caac129594ac6dd68__tasks_tutorial_rfc"/>

docs/1-connectivity-documentation/recommendations-for-secure-setup-e7ea82a.md

@@ -127,6 +127,9 @@ Ciphers are either enabled or disabled, and they are either compatible or incomp
 > 
 > As the set of supported ciphers may differ, the selected ciphers may not be supported by the new JVM. In that case, the Cloud Connector will not start anymore, and you must fix the issue by manually adapting the file *conf/server.xml*. After a successful switch, you can adjust the list of eligible ciphers again.
 
+> ### Tip:  
+> As of Cloud Connector version 2.17.0, you can run the script `resetCiphers` from the `scc` folder in the Cloud Connector installation directory to reset the ciphers if UI access is blocked due to wrong cipher settings.
+
 **Related Information**  
 
 

docs/1-connectivity-documentation/repository-configuration-4c4b83b.md

@@ -64,6 +64,27 @@ Represents the password for a repository user. If you use such a user, this prop
 
 
 
+</td>
+</tr>
+<tr>
+<td valign="top">
+
+`jco.destination.repository.check_interval`
+
+</td>
+<td valign="top">
+
+Time interval in minutes after which the associated repository is regularly checked for outdated metadata in its local cache. If outdated metadata are identified, they will be removed from the cache.
+
+The default value is 0 \(repository checking feature is disabled\).
+
+If multiple repository destination configurations refer to the same repository instance, the smallest configured *non-zero* value of all destinations will be effective for the repository. Therefore, the repository checking feature is only switched off if *all* repository destinations for the repository instance are configured with value 0, or do not specify this property.
+
+> ### Note:  
+> The configured value will only be considered if the respective destination can be used for repository metadata queries. It will be ignored if `jco.destination.repository_destination` has been configured. In this case, the property `jco.destination.repository.check_interval` must be configured in the referred repository destination instead to activate this checking feature.
+
+
+
 </td>
 </tr>
 </table>

docs/1-connectivity-documentation/troubleshooting-e7df7f1.md

@@ -39,7 +39,7 @@ If you encounter problems that seem to be caused by some trouble in the communic
 -   *CPIC Trace Level* allows you to set the level between 0 and 3 and provides traces for the CPIC-based RFC communication with ABAP systems.
 -   When the *Tunnel Traffic Trace* is activated for a subaccount, all the HTTP and RFC traffic crossing the tunnel for that subaccount going through this Cloud Connector, is traced in files with names `tunnel_traffic_<account id>_on_<landscapehost>.trc`. This is helpful if you need to understand what documents have been exchanged between the involved systems.
 -   **ABAP Cloud SNC Traffic Trace**: When the *ABAP Cloud SNC traffic trace* is activated for an account, all RFC SNC-based traffic crossing a service channel for that account \(going through this Cloud Connector\), is traced in files with names *snc\_traffic\_<account id\>\_on\_<landscapehost\>.trc*. This is helpful if you need to understand issues with SNC termination in the Cloud Connector.
--   *SSL Trace*: When the SSL trace is activated, the `ljs_trace.log` file includes information for SSL-protected communication. To activate a change of this setting, a restart is required. Activate this trace only when requested by SAP support. It has a high impact on performance as it produces a large amount of traces.
+-   *SSL Trace*: When the SSL trace is activated, the `scc_core.trc` file includes information for SSL-protected communication. To activate a change of this setting, a restart is required. Activate this trace only when requested by SAP support. It has a high impact on performance as it produces a large amount of traces.
 
 -   *Automatic Cleanup* lets you remove old trace files that have not been changed for a period of time exceeding the configured interval. You can choose from a list of predefined periods. The default is `Never`.
 

docs/1-connectivity-documentation/update-the-certificate-for-a-subaccount-071708a.md

@@ -38,6 +38,8 @@ Proceed as follows to update your subaccount certificate:
     > ### Note:  
     > In the **Cloud Foundry** environment, you must provide your `Login E-mail` instead of a user ID as *<User Name\>*.
 
+
+
     > ### Tip:  
     > When using SAP Cloud Identity Services - Identity Authentication \(IAS\) as platform identity provider with two-factor authentication \(2FA / MFA\) for your subaccount, you can simply append the required token to the regular password. For example, if your password is "eX7?6rUm" and the one-time passcode is "123456", you must enter "eX7?6rUm123456" into the *<Password\>* field.
 

docs/1-connectivity-documentation/use-a-config-json-to-create-or-update-a-destination-service-instance-6816d3c.md

@@ -4,7 +4,10 @@
 
 Configure specific parameters in a `config.json` file to create or update a Destination service instance.
 
-When creating or updating a Destination service instance, you can configure the following settings, which are part of the `config.json` input file \(see [Open Service Broker API](https://www.openservicebrokerapi.org/)\), both via SAP BTP cockpit or Cloud Foundry command line interface \(CLI\):
+> ### Note:  
+> By default, creating or updating a Destination service instance does not require passing any configuration settings.
+
+When creating or updating a Destination service instance, you can optionally configure the following settings, which are part of the `config.json` input file \(see [Open Service Broker API](https://www.openservicebrokerapi.org/)\), both via SAP BTP cockpit or Cloud Foundry command line interface \(CLI\):
 
 
 <table>
@@ -28,34 +31,39 @@ Description
 <tr>
 <td valign="top">
 
-`init_data`
+`HTML5Runtime_enabled`
 
 </td>
 <td valign="top">
 
-JSON
+Boolean
 
 </td>
 <td valign="top">
 
-The data \(destinations, certificates\) to initialise or update the service instance with. The data can be stored on both *service instance* data and *subaccount* data.
+Optional. Indicates whether the SAP BTP HTML5 runtime should be enabled to work with the service instance on behalf of the HTML5 applications associated with it during deployment.
+
+> ### Note:  
+> Check if the SAP BTP HTML5 runtime is available for the region in which the service instance is being created or updated.
+
+
 
 </td>
 </tr>
 <tr>
 <td valign="top">
 
-`HTML5Runtime_enabled`
+`init_data`
 
 </td>
 <td valign="top">
 
-Boolean
+JSON
 
 </td>
 <td valign="top">
 
-Indicates whether the SAP BTP HTML5 runtime should be enabled to work with the service instance on behalf of the HTML5 applications associated with it during deployment.
+Optional. The data \(destinations, certificates\) to initialise or update the service instance with. The data can be stored on both *service instance* data and *subaccount* data.
 
 </td>
 </tr>

docs/1-connectivity-documentation/what-is-sap-btp-connectivity-daca64d.md

@@ -258,7 +258,7 @@ One of these roles:
 -   *Space Manager*
 -   *Space Developer* 
 
-See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management happens at all levels from global account to environment, while user management is done for business applications.") :arrow_upper_right:.
+See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management takes place at all levels from global account to environment, while user management is relevant for business applications.") :arrow_upper_right:.
 
 </td>
 </tr>
@@ -485,7 +485,7 @@ One of these roles:
 -   *Space Manager*
 -   *Space Developer* 
 
-See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management happens at all levels from global account to environment, while user management is done for business applications.") :arrow_upper_right:.
+See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management takes place at all levels from global account to environment, while user management is relevant for business applications.") :arrow_upper_right:.
 
 </td>
 </tr>
@@ -510,7 +510,7 @@ One of these roles:
 -   *Space Manager*
 -   *Space Developer* 
 
-See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management happens at all levels from global account to environment, while user management is done for business applications.") :arrow_upper_right:.
+See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management takes place at all levels from global account to environment, while user management is relevant for business applications.") :arrow_upper_right:.
 
 </td>
 </tr>
@@ -535,7 +535,7 @@ One of these roles:
 -   *Space Manager*
 -   *Space Developer* 
 
-See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management happens at all levels from global account to environment, while user management is done for business applications.") :arrow_upper_right:.
+See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management takes place at all levels from global account to environment, while user management is relevant for business applications.") :arrow_upper_right:.
 
 </td>
 </tr>
@@ -560,7 +560,7 @@ One of these roles:
 -   *Space Manager*
 -   *Space Developer* 
 
-See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management happens at all levels from global account to environment, while user management is done for business applications.") :arrow_upper_right:.
+See [User and Member Management](https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/cc1c676b43904066abb2a4838cbd0c37.html "On SAP BTP, member management takes place at all levels from global account to environment, while user management is relevant for business applications.") :arrow_upper_right:.
 
 </td>
 </tr>