Update from SAP DITA CMS (squashed):

commit e27ab497370cbc2ea22b8893d3277e1abb186e9f
Author: REDACTED
Date:   Mon Dec 9 08:54:43 2024 +0000

    Update from SAP DITA CMS 2024-12-09 08:54:43

    Project: dita-all/slu1713332208086
    Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap
    Output: loiocc0ab4c7365e43bbbee9eae27deb32da
    Language: en-US
    Builddable map: 446771d4951c4a6988252269c21d94ba.ditamap

commit ce2ace9215818f8b1349cf9ff95982b579ffb476
Author: REDACTED
Date:   Mon Dec 9 05:52:16 2024 +0000

    Update from SAP DITA CMS 2024-12-09 05:52:16

    Project: dita-all/djr1548327031813
    Project map: 035865251b5d4135a8b461c55ee9a8e9.ditamap
    Output: loiocf0e5a9be9804817aa649f51a84b9f39
    Language: en-US
    Builddable map: 668ddc52b4c54429a3abb37be25b57df.ditamap

commit 5ad103f1154b459f13c29cc3ddcbbf0a5c81d3eb
Author: REDACTED
Date:   Mon Dec 9 00:44:06 2024 +0000

    Update from SAP DITA CMS 2024-12-09 00:44:06

    Project: dita-all/djr1548327031813
    Project map: 035865251b5d4135a8b461c55ee9a8e9.ditamap

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

docs/ISuite/10-InitialSetup/initial-setup-of-sap-integration-suite-3dcf507.md

@@ -1,9 +1,16 @@
 <!-- loio3dcf507f92f54597bc203600bf8f94c5 -->
 
+<link rel="stylesheet" type="text/css" href="../css/sap-icons.css"/>
+
 # Initial Setup of SAP Integration Suite
 
 Get onboarded to SAP Integration Suite.
 
+> ### Note:  
+> [SAP Integration Suite Documentation Survey](https://sapinsights.eu.qualtrics.com/jfe/form/SV_9WxzBXTWeQe5nq6) <span class="SAP-icons-V5"></span>
+> 
+> You can help us improve the SAP Integration Suite documentation by sharing your experience. Please take a moment to complete this short [survey](https://sapinsights.eu.qualtrics.com/jfe/form/SV_9WxzBXTWeQe5nq6).
+
 
 
 <a name="loio3dcf507f92f54597bc203600bf8f94c5__section_uyh_v3g_brb"/>

docs/ISuite/10-InitialSetup/production-account-24ef511.md

@@ -9,7 +9,7 @@ This account model includes services for you to start working in SAP Integration
 
 [Setting Up Your Account](setting-up-your-account-079c68f.md "Create a subaccount in your assigned global account using the SAP BTP cockpit.")
 
-[Subscribing and Configuring Initial Access to SAP Integration Suite](subscribing-and-configuring-initial-access-to-sap-integration-suite-8a3c8b7.md "Subscribe to the SAP Integration Suitein SAP BTP cockpit and assign the Integration_Provisioner role to gain access.")
+[Subscribing and Configuring Initial Access to SAP Integration Suite](subscribing-and-configuring-initial-access-to-sap-integration-suite-8a3c8b7.md "Subscribe to the SAP Integration Suite in SAP BTP cockpit and assign the Integration_Provisioner role to gain access.")
 
 [Configuring User Access to SAP Integration Suite](../configuring-user-access-to-sap-integration-suite-2c6214a.md "Assign the required roles and role collections to users for accessing the individual capabilities.")
 

docs/ISuite/10-InitialSetup/setting-up-your-account-079c68f.md

@@ -10,52 +10,10 @@ Create a subaccount in your assigned global account using the SAP BTP cockpit.
 
 ## Context
 
-After you've received your logon data by email, follow the steps here to create subaccounts in your global account:
+You are a global account administrator. After you've received your logon data by email, follow the steps detailed in[Create a Subaccount](https://help.sap.com/docs/btp/sap-business-technology-platform/create-subaccount?version=Cloud) to create subaccounts in your global account:
 
 > ### Note:  
+> Integration Suite service runs only on the SAP BTP, Cloud Foundry environment.
+> 
 > If you’ve subscribed to Process Integration, API Management, and/or Open Connector services in your existing subaccount, then please subscribe to the Integration Suite service in a new subaccount.
 
-
-
-## Procedure
-
-1.  In the overview page, choose *Subaccounts* from the left pane and choose *New Subaccount*.
-
-2.  Specify a display name.
-
-3.  *Optional*: Specify a description.
-
-4.  Leave the *Neo Environment* checkbox deselected and choose the desired infrastructure provider and region for your subaccount.
-
-    > ### Note:  
-    > Integration Suite service runs only on the SAP BTP, Cloud Foundry environment.
-
-5.  Enter a *Subdomain* for your subaccount. This subdomain becomes part of the URL for accessing applications that you subscribe to from this subaccount.
-
-    > ### Note:  
-    > The subdomain must be unique across all subaccounts in the same region, and can contain only:
-    > 
-    > -   letters
-    > -   digits
-    > -   hyphens \(although hyphens aren’t allowed at the beginning or at the end of the subdomain\)
-    > 
-    > Uppercase and lowercase letters can be used, however that alone doesn’t qualify as a means to differentiate between subdomains \(for example, SUBDOMAIN and subdomain are considered to be the same\).
-
-6.  *Optional*: If your subaccount is to be used for production purposes, select the *Use for production* option.
-
-    > ### Note:  
-    > -   By flagging your subaccount with this option, you can help SAP Support to take appropriate action when handling incidents that are related to mission-critical accounts in production systems.
-    > 
-    > -   Don’t select this option if your subaccount isn’t intended for production purposes, such as development, testing, or demos. You can change your selection at any time by editing the subaccount properties.
-
-7.  Save your changes.
-
-
-
-
-<a name="loio079c68f35a634f55bf3ee88462aa2f07__result_b3q_sfw_4lb"/>
-
-## Results
-
-A new tile appears in the global account page with the subaccount details. The subaccount is also listed in the *System Landscape* page.
-

docs/ISuite/10-InitialSetup/subscribing-and-configuring-initial-access-to-sap-integration-suite-8a3c8b7.md

@@ -4,14 +4,19 @@
 
 # Subscribing and Configuring Initial Access to SAP Integration Suite
 
-Subscribe to the SAP Integration Suitein SAP BTP cockpit and assign the Integration\_Provisioner role to gain access.
+Subscribe to the SAP Integration Suite in SAP BTP cockpit and assign the Integration\_Provisioner role to gain access.
 
 
 
 <a name="loio8a3c8b7a6b1c4f249bb81d11644ef806__prereq_nbs_lth_vlb"/>
 
 ## Prerequisites
 
+> ### Note:  
+> [SAP Integration Suite Documentation Survey](https://sapinsights.eu.qualtrics.com/jfe/form/SV_9WxzBXTWeQe5nq6) <span class="SAP-icons-V5"></span>
+> 
+> You can help us improve the SAP Integration Suite documentation by sharing your experience. Please take a moment to complete this short [survey](https://sapinsights.eu.qualtrics.com/jfe/form/SV_9WxzBXTWeQe5nq6).
+
 -   You’ve created a subaccount in your assigned global account using the SAP BTP cockpit and added the desired service plans for Integration Suite to the subaccount. For more information on service plans, see [SAP Discovery Center - Integration Suite](https://discovery-center.cloud.sap/serviceCatalog/integration-suite?region=all).
 
 -   If you want to use Integration Suite with the **Starter** service plan, additionally assign the entitlement *integration\_flows* to your subaccount. This entitlement along with the appropriate quota assignment is a prerequiste to create custom integration flows. For more information about the service plans, see SAP Note [2903776](https://me.sap.com/notes/2903776).

docs/ISuite/20-Working_with_SAP_Integration_Suite_Home/working-with-integration-suite-home-a53dce3.md

@@ -109,6 +109,11 @@ Trading Partner Management
 
 Integration Advisor
 
+</th>
+<th valign="top">
+
+OData Provisioning
+
 </th>
 </tr>
 <tr>
@@ -141,6 +146,11 @@ Discover <span class="SAP-icons-V5"></span>
 
 <span style="color:#2B7D2B;"><span class="SAP-icons-V5"></span></span> *Discover* \> *Type Systems*
 
+</td>
+<td valign="top">
+
+<span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
+
 </td>
 </tr>
 <tr>
@@ -173,6 +183,11 @@ Design :pencil2:
 
 <span style="color:#2B7D2B;"><span class="SAP-icons-V5"></span></span> *Design* \> *Custom Messages, MIGs, and MAGs*
 
+</td>
+<td valign="top">
+
+<span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
+
 </td>
 </tr>
 <tr>
@@ -205,6 +220,11 @@ Test <span class="SAP-icons-V5"></span>
 
 <span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
 
+</td>
+<td valign="top">
+
+<span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
+
 </td>
 </tr>
 <tr>
@@ -237,6 +257,11 @@ Configure <span class="SAP-icons-V5"></span>
 
 <span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
 
+</td>
+<td valign="top">
+
+<span style="color:#2B7D2B;"><span class="SAP-icons-V5"></span></span> *Configure* \> *OData Services*
+
 </td>
 </tr>
 <tr>
@@ -269,6 +294,11 @@ Engage <span class="SAP-icons-V5"></span>
 
 <span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
 
+</td>
+<td valign="top">
+
+<span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
+
 </td>
 </tr>
 <tr>
@@ -301,6 +331,11 @@ Monitor <span class="SAP-icons-V5"></span>
 
 <span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
 
+</td>
+<td valign="top">
+
+<span style="color:#2B7D2B;"><span class="SAP-icons-V5"></span></span> *Monitor* \> *OData Services*
+
 </td>
 </tr>
 <tr>
@@ -333,6 +368,11 @@ Inspect Resource Consumption <span class="SAP-icons-V5"></span>
 
 <span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
 
+</td>
+<td valign="top">
+
+<span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
+
 </td>
 </tr>
 <tr>
@@ -365,6 +405,11 @@ Monetize <span class="SAP-icons-V5"></span>
 
 <span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
 
+</td>
+<td valign="top">
+
+<span style="color:#BB0000;"><span class="SAP-icons-V5"></span></span>
+
 </td>
 </tr>
 <tr>
@@ -399,6 +444,11 @@ NA
 
 NA
 
+</td>
+<td valign="top">
+
+NA
+
 </td>
 </tr>
 <tr>
@@ -439,6 +489,13 @@ NA
 
 <span style="color:#2B7D2B;"><span class="SAP-icons-V5"></span></span>*Settings* \> *MIGs and MAGs*
 
+</td>
+<td valign="top">
+
+<span style="color:#2B7D2B;"><span class="SAP-icons-V5"></span></span> 
+
+*Settings* \> *OData Services*
+
 </td>
 </tr>
 </table>
@@ -550,7 +607,7 @@ News and Announcement. Lets you know what is new in the Integration Suite.
 **Related Information**  
 
 
-[Subscribing and Configuring Initial Access to SAP Integration Suite](../10-InitialSetup/subscribing-and-configuring-initial-access-to-sap-integration-suite-8a3c8b7.md "Subscribe to the SAP Integration Suitein SAP BTP cockpit and assign the Integration_Provisioner role to gain access.")
+[Subscribing and Configuring Initial Access to SAP Integration Suite](../10-InitialSetup/subscribing-and-configuring-initial-access-to-sap-integration-suite-8a3c8b7.md "Subscribe to the SAP Integration Suite in SAP BTP cockpit and assign the Integration_Provisioner role to gain access.")
 
 [Configuring User Access to SAP Integration Suite](../configuring-user-access-to-sap-integration-suite-2c6214a.md "Assign the required roles and role collections to users for accessing the individual capabilities.")
 

docs/ISuite/40-RemoteSystems/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md

@@ -141,6 +141,9 @@ Create a service instance to implement inbound communication. A service instance
 
     We recommend choosing *Form* as the more convenient option.
 
+    > ### Note:  
+    > Selecting *JSON*, you can also pass these parameters in a valid JSON object that contains service-specific configuration parameters, provided either in-line or in a file \(see [Specifying Service Instance and Service Key Parameters in JSON Format](specifying-service-instance-and-service-key-parameters-in-json-format-ae419b6.md)\).
+
     Specify the following parameters.
 
 
@@ -243,7 +246,7 @@ Create a service instance to implement inbound communication. A service instance
 
     The following values have been set as default:
 
-    -   for plan `api`: `4300` \(12 hours\)
+    -   for plan `api`: `43200` \(12 hours\)
 
     -   for plan `integration-flow`: `3600` \(1 hour\)
 
@@ -254,9 +257,6 @@ Create a service instance to implement inbound communication. A service instance
     </tr>
     </table>
 
-    > ### Note:  
-    > Selecting *JSON*, you can also pass these parameters in a valid JSON object that contains service-specific configuration parameters, provided either in-line or in a file \(see [Specifying Service Instance and Service Key Parameters in JSON Format](specifying-service-instance-and-service-key-parameters-in-json-format-ae419b6.md)\).
-
 9.  Optional: Choose *Next* to review and verify the instance details.
 
 10. Choose *Create*.

docs/ISuite/40-RemoteSystems/creating-x-509-keys-ec605c7.md

@@ -4,14 +4,20 @@
 
 You need X.509 keys to configure communication with certificate-based authentication over HTTPS and if you want to configure digital encryption and signing of messages with security standards PKCS\#7 and XML Digital Signature.
 
-**Related Information**  
+1.  Generate a key pair.
 
+    See: [Generating a Key Pair](generating-a-key-pair-abb324d.md)
 
-[Generating a Key Pair](generating-a-key-pair-abb324d.md "")
+2.  Upload the signing response that you receive from the CA to the keystore.
 
-[Downloading a Certificate Signing Request](downloading-a-certificate-signing-request-b199dbe.md "Download a certificate signing request to send to a certification authority.")
+    See:  <?sap-ot O2O class="- topic/xref " href="f50c159542f04f888424bdbc6a4e203f.xml" text="" desc="" xtrc="xref:2" xtrf="file:/home/builder/src/dita-all/slu1713332208086/loiocc0ab4c7365e43bbbee9eae27deb32da_en-US/src/content/localization/en-us/ec605c708daf4c7fb56b456345a2c43a.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" ?> 
 
-[Requesting a Signed Certificate from a Certification Authority](requesting-a-signed-certificate-from-a-certification-authority-2a19480.md "To enable the tenant to communicate as client with the customer system, you have to import a client certificate to the tenant client keystore. This certificate has to be signed by a certification authority (CA).")
+3.  Request a signed certificate from a certification authority
+
+    To enable the tenant to communicate as client with the customer system, you have to import a client certificate to the tenant client keystore. This certificate has to be signed by a certification authority \(CA\). The procedure depends on the CA and is not documented here.
+
+4.  Upload the signing response that you received from the CA to the keystore.
+
+    See: [Updating a Key Pair with a Signing Response](../50-Development/updating-a-key-pair-with-a-signing-response-4242f01.md)
 
-[Securely Exchanging Key Material](securely-exchanging-key-material-908d93e.md "In many cases, communication partners need to exchange public keys in order to establish a secure connection.")
 

docs/ISuite/40-RemoteSystems/introduction-10dc4a3.md

@@ -258,6 +258,22 @@ See: [Amazon DynamoDB Receiver Adapter](../50-Development/amazon-dynamodb-receiv
 <tr>
 <td valign="top">
 
+*Amazon EventBridge*
+
+Receiver adapter
+
+</td>
+<td valign="top">
+
+Connects SAP Integration Suite to Amazon EventBridge.
+
+See: [AmazonEventBridge Receiver Adapter](../50-Development/amazoneventbridge-receiver-adapter-ff3f9ed.md)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
 *AmazonWebServices* 
 
 Sender adapter
@@ -628,6 +644,22 @@ See: [Configure the AMQP Receiver Adapter](../50-Development/configure-the-amqp-
 <tr>
 <td valign="top">
 
+*Anaplan*
+
+Receiver adapter
+
+</td>
+<td valign="top">
+
+Connects SAP Integration Suite to Anaplan.
+
+See: [Anaplan Receiver Adapter](../50-Development/anaplan-receiver-adapter-364ab57.md)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
 *Ariba*
 
 Sender adapter
@@ -961,6 +993,22 @@ See: [HTTP Receiver Adapter](../50-Development/http-receiver-adapter-2da452e.md)
 <tr>
 <td valign="top">
 
+*HubSpot*
+
+Receiver adapter
+
+</td>
+<td valign="top">
+
+Allows SAP Integration Suite to connect to HubSpot.
+
+See: [HubSpot Receiver Adapter](../50-Development/hubspot-receiver-adapter-48cfaa8.md)
+
+</td>
+</tr>
+<tr>
+<td valign="top">
+
 *IDoc*
 
 Sender adapter
@@ -1369,7 +1417,7 @@ Receiver adapter
 </td>
 <td valign="top">
 
-Connects SAP Integration Suite to NetSuite. NetSuite is an integrated cloud business software suite, including business accounting, ERP, CRM, and e-commerce software.
+Connects SAP Integration Suite to NetSuite.
 
 See: [NetSuite Receiver Adapter](../50-Development/netsuite-receiver-adapter-618127a.md)
 
@@ -1703,7 +1751,7 @@ Sender adapter
 </td>
 <td valign="top">
 
-Connects SAP Integration Suite to a remote SMB Server using TCP \(Transmission Control Protocol\) to perform a read operation on the system. SMB stands for Server Message Block.
+Allows SAP Integration Suite to connect to a remote SMB Server using TCP \(Transmission Control Protocol\) to perform a read operation on the system. SMB stands for Server Message Block.
 
 Supported Versions:
 

docs/ISuite/40-RemoteSystems/keys-provided-by-sap-9d8a60b.md

@@ -4,7 +4,7 @@
 
 
 
-When SAP first provides a tenant to a customer, it delivers an X.509 certificate chain, which has to be renewed every 2 years.
+When SAP first provides a tenant to a customer, it delivers an X.509 certificate chain, which has to be renewed every 1 year.
 
 SAP key pairs delivered with the tenant have the following aliases: sap\_cloudintegrationcertificate, hcicertificate, or hcicertificate1.