From 338bbae5ae4d1f952d357b33d96b5c97a347e3e1 Mon Sep 17 00:00:00 2001 From: ditaccms-bot Date: Tue, 10 Oct 2023 04:23:41 +0000 Subject: [PATCH] Update from SAP DITA CMS (squashed): commit a42d7ff065ae87cd4041fc3f990efb06a57fb807 Author: REDACTED Date: Tue Oct 10 04:08:19 2023 +0000 Update from SAP DITA CMS 2023-10-10 04:08:19 Project: dita-all/cvv1690968981196 Project map: 4e3938135e8b4504abd2de738751b03a.ditamap Language: en-US commit 71b8f88a0d00faff8dd18f764581d2950708fafb Author: REDACTED Date: Mon Oct 9 15:40:01 2023 +0000 Update from SAP DITA CMS 2023-10-09 15:40:01 Project: dita-all/ccm1691418051317 Project map: 6d6c94be23b547a19d534f13dd6d51a7.ditamap Language: en-US commit 03567f23049bcf27794fd5e20978361d65d9e875 Author: REDACTED Date: Fri Oct 6 10:34:24 2023 +0200 Update dep5 commit 0a5093dd8f61fb6a26ed47121e8e059dbd370037 Author: REDACTED Date: Fri Oct 6 10:33:53 2023 +0200 Update README.md commit 1547c02ceaf1b5a49f1fb451cafcce431bd80a19 Author: REDACTED ################################################## [Remaining squash message was removed before commit...] --- .reuse/dep5 | 2 +- README.md | 4 +- ...ustom-domain-for-a-virtual-host-6b9e5a3.md | 2 +- .../advanced-event-mesh-adapter-dd7e034.md | 14 + ...ced-event-mesh-receiver-adapter-881f656.md | 4 + ...anced-event-mesh-sender-adapter-abd2efc.md | 622 ++++++++++++++ ...ctors-odata-v2-receiver-adapter-d16dd12.md | 11 +- docs/ISuite/50-Development/flow-08b40d9.md | 3 + ...-flow-configuration-version-2-0-6d4cdd1.md | 3 +- .../50-Development/message-status-733a57b.md | 4 +- ...ion-steps-for-2-0-compatibility-8631960.md | 26 + .../sender-communication-flow-v2-5b946c5.md | 2 +- docs/ISuite/index.md | 4 + ...ustom-domain-for-a-virtual-host-6b9e5a3.md | 2 +- .../APIM-Development/flow-08b40d9.md | 3 + .../what-is-api-management-0aef763.md | 23 + ...-key-for-inbound-authentication-19af5e2.md | 90 +- ...g-a-certificate-signing-request-b199dbe.md | 2 +- ...flow-processing-neo-environment-778c7e7.md | 2 +- ...ing-up-inbound-sftp-connections-d8fb958.md | 4 +- ...nbound-sftp-connections-details-e72eba4.md | 2 +- ...ng-up-outbound-sftp-connections-6e4de95.md | 4 +- ...tbound-sftp-connections-details-15401a7.md | 2 +- ...igure-the-amqp-receiver-adapter-d5660c1.md | 2 +- ...nfigure-the-amqp-sender-adapter-99ce674.md | 2 +- ...igure-the-idoc-receiver-adapter-018aa88.md | 4 +- ...-soap-soap-1-x-receiver-adapter-57f7b34.md | 2 + ...ctors-odata-v2-receiver-adapter-d16dd12.md | 11 +- ...ules-for-json-to-xml-conversion-232a9cf.md | 2 +- ...ules-for-xml-to-json-conversion-66d099d.md | 4 +- ...-message-mapping-as-a-flow-step-3d5cb7f.md | 7 +- ...-message-mapping-as-an-artifact-1d52a7b.md | 172 ++-- ...flow-with-the-post-exit-mapping-988e5e3.md | 2 +- ...g-the-standard-integration-flow-4da82ad.md | 2 +- .../define-content-modifier-8f04a70.md | 18 +- .../define-xml-to-json-converter-a60a282.md | 4 +- ...s-using-esr-process-integration-57a6b6e.md | 2 +- .../integration-content-d1679a8.md | 2 +- ...ions-for-json-to-xml-conversion-3a02829.md | 2 +- ...ions-for-xml-to-json-conversion-4bf5a05.md | 4 +- ...esources-of-an-integration-flow-b5968b2.md | 4 +- ...nsion-step-by-step-demo-example-2c3a543.md | 2 +- ...nd-process-the-integration-flow-f08cca6.md | 4 +- ...nario-with-https-sender-adapter-ccdb189.md | 6 +- .../smoke-test-scenario-8c83fcf.md | 2 +- ...nario-with-external-data-source-e4bef74.md | 8 +- ...d-scenario-with-a-mail-receiver-bfee17e.md | 8 +- ...rking-with-integration-packages-45423ba.md | 2 +- ...abling-and-configuring-a-tenant-6807119.md | 2 +- docs/ci/InitialSetup/security-faqs-58ff94f.md | 2 +- .../code-value-mapping-eb6dad8.md | 34 + .../exporting-mig-mag-c8bba26.md | 13 + ...ing-the-source-and-target-nodes-9ea58d6.md | 5 +- ...ng-with-a-mapping-guideline-mag-0803ca6.md | 4 +- ...ping-content-from-es-repository-e18fc05.md | 23 +- .../adding-members-to-an-account-eb6d612.md | 2 +- ...ns-for-integration-team-members-3ec7679.md | 2 +- .../managing-message-queues-cdcce24.md | 4 +- docs/ci/Operations/message-status-733a57b.md | 4 +- ...oring-audit-log-neo-environment-2d6031f.md | 2 +- ...nd-monitoring-cloud-integration-c401afc.md | 2 +- ...rtifact-renewal-for-ws-security-169b0b5.md | 2 +- .../specific-data-assets-0e4e511.md | 4 +- .../specific-data-assets-f922344.md | 6 +- ...loud-based-integration-scenario-762289a.md | 4 +- .../partner-directory-e7fa1e2.md | 2 +- .../what-is-sap-cloud-integration-e12c09c.md | 18 + ...4-sap-cloud-integration-archive-59a5f82.md | 36 +- ...5-sap-cloud-integration-archive-723dddb.md | 84 +- ...6-sap-cloud-integration-archive-2f5d4f1.md | 118 +-- ...7-sap-cloud-integration-archive-f3b13e4.md | 86 +- ...8-sap-cloud-integration-archive-5a4ff04.md | 46 +- ...r-sap-cloud-integration-archive-eca4d78.md | 2 +- ...-releases-for-cloud-integration-023a472.md | 35 + .../sap-cloud-integration-72ef31d.md | 801 ++++++++++++++++++ docs/ci/sap-cloud-integration-2fb0aa4.md | 4 +- 76 files changed, 2089 insertions(+), 371 deletions(-) create mode 100644 docs/ISuite/50-Development/advanced-event-mesh-adapter-dd7e034.md create mode 100644 docs/ISuite/50-Development/configure-the-advanced-event-mesh-receiver-adapter-881f656.md create mode 100644 docs/ISuite/50-Development/configure-the-advanced-event-mesh-sender-adapter-abd2efc.md create mode 100644 docs/ISuite/50-Development/migration-steps-for-2-0-compatibility-8631960.md diff --git a/.reuse/dep5 b/.reuse/dep5 index e89e0cba..b378c181 100644 --- a/.reuse/dep5 +++ b/.reuse/dep5 @@ -4,5 +4,5 @@ Upstream-Contact: srutisagaram@sap.com Source: https://github.com/sap-docs/btp-integration-suite Files: * -Copyright: 2022 SAP SE or an SAP affiliate company and btp-integration-suite contributors +Copyright: 2022-2023 SAP SE or an SAP affiliate company and btp-integration-suite contributors License: CC-BY-4.0 diff --git a/README.md b/README.md index c71785d8..94a599f3 100644 --- a/README.md +++ b/README.md @@ -23,8 +23,8 @@ We recommend using the documentation on SAP Help Portal as a starting point for 1. Open one of the guides that support contributions, listed above. 1. You can either: - * Choose *Edit* to suggest a change for the current page you see in the Help Portal viewer, or - * Choose *Feedback* to open a GitHub issue in this repository. + * Choose *Feedback* > *Edit page* to suggest a change for the current page you see in the Help Portal viewer, or + * Choose *Feedback* > *Create issue* to open a GitHub issue in this repository. If you only make a small contribution, that's the quickest way to propose a change. For larger contributions, we recommend forking this repository to work locally. The filenames in the [docs](docs) directory are created based on the title of the page on SAP Help Portal. diff --git a/docs/ISuite/20-Working_with_SAP_Integration_Suite_Home/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md b/docs/ISuite/20-Working_with_SAP_Integration_Suite_Home/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md index c1ed02a6..7ee87aa2 100644 --- a/docs/ISuite/20-Working_with_SAP_Integration_Suite_Home/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md +++ b/docs/ISuite/20-Working_with_SAP_Integration_Suite_Home/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md @@ -10,7 +10,7 @@ Virtual host is an entity where the API proxy gets deployed, and API proxies can ## Context -During onboarding, when you enable the API Management capability within Integration Suite , a virtual host is created by default, and you can execute the APIs using the URL of this virtual host. The domain for this virtual host URL is specific to the SAP data center where the tenant is onboarded. +During onboarding, when you enable the API Management capability within Integration Suite, a virtual host is created by default, and you can execute the APIs using the URL of this virtual host. The domain for this virtual host URL is specific to the SAP data center where the tenant is onboarded. Once onboarding is completed, you can create an additional virtual host. You have the option to create the virtual host with a domain that is specific to your organization. This domain is referred to as a Custom Domain. diff --git a/docs/ISuite/50-Development/advanced-event-mesh-adapter-dd7e034.md b/docs/ISuite/50-Development/advanced-event-mesh-adapter-dd7e034.md new file mode 100644 index 00000000..54813d18 --- /dev/null +++ b/docs/ISuite/50-Development/advanced-event-mesh-adapter-dd7e034.md @@ -0,0 +1,14 @@ + + +# Advanced Event Mesh Adapter + +The Advanced Event Mesh \(AEM\) adapter enables SAP Integration Suite to connect to the Advanced Event Mesh via the SMF protocol.Use the AEM Sender adapter to receive messages from AEM. Use the AEM Receiver adapter to send messages to AEM. + +> ### Note: +> Only SMF allowed headers are forwarded on the Sender and Receiver. To store any custom headers on the Receiver, use the UserProperties header. + +**Related Information** + + +[Configure the Advanced Event Mesh Sender Adapter](configure-the-advanced-event-mesh-sender-adapter-abd2efc.md "") + diff --git a/docs/ISuite/50-Development/configure-the-advanced-event-mesh-receiver-adapter-881f656.md b/docs/ISuite/50-Development/configure-the-advanced-event-mesh-receiver-adapter-881f656.md new file mode 100644 index 00000000..a8e18a28 --- /dev/null +++ b/docs/ISuite/50-Development/configure-the-advanced-event-mesh-receiver-adapter-881f656.md @@ -0,0 +1,4 @@ + + +# Configure the Advanced Event Mesh Receiver Adapter + diff --git a/docs/ISuite/50-Development/configure-the-advanced-event-mesh-sender-adapter-abd2efc.md b/docs/ISuite/50-Development/configure-the-advanced-event-mesh-sender-adapter-abd2efc.md new file mode 100644 index 00000000..5bad3d82 --- /dev/null +++ b/docs/ISuite/50-Development/configure-the-advanced-event-mesh-sender-adapter-abd2efc.md @@ -0,0 +1,622 @@ + + +# Configure the Advanced Event Mesh Sender Adapter + +The Advanced Event Mesh \(AEM\) sender adapter allows you to consume messages in SAP Integration Suite from queues or subscriptions on an AEM broker using the SMF message protocol. + +The *General* tab displays general information about the adapter itself. + +**General** + + + + + + + + + + + + + + + + + + + + + + + +
+ +Parameter + + + + + +Description + + + +
+ +*Name* + + + + + +AdvancedEventMesh + + + +
+ +*Adapter Type* + + + + + +AdvancedEventMesh + + + +
+ +*Transport Protocol* + + + + + +TCP + + + +
+ +*Message Protocol* + + + + + +SMF + + + +
+ +Switch to the *Connection* tab to configure the adapter's connection details. + +**Connection** + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Parameter + + + + + +Description + + + +
+ +*Host* + + + + + +The host name of the event broker. + + + +
+ +*Message VPN* + + + + + +The name of the Message VPN to attempt to join when connecting to the event broker. + + + +
+ +*Username* + + + + + +The client username used for authentication with the event broker. + + + +
+ +*Authentication Type* + + + + + +The authentication mechanism to be used while connecting to AEM. The available options are: + +- Basic + +- Client Certificate + +- OAuth2 + + + + +
+ +*Password Secure Alias\(Only when using Basic authentication\)* + + + + + +The alias which defines the client password used for authentication with the event broker, stored as Secure Parameter. + + + +
+ +*Keystore Alias\(Only when using Client Certificate authentication\)* + + + + + +The alias of the private Key Pair in the Integration Suite's Keystore. + + + +
+ +*Truststore Alias\(Only when using Client Certificate authentication\)* + + + + + +The alias of the Certificate in the Integration Suite's Keystore. This is optional and maybe necessary only if event broker host certificate requires to be trusted or not recognized by the JRE. + + + +
+ +*OAuth2 Credential Type\(Only when using \`OAuth2\` authentication\)* + + + + + +The type of OAuth2 credential type to be used. The available options are: + +- OAuth2 Client Credentials \(Integration Suite managed OAuth2 credential store\) + +- OAuth2 Authorization Code \(Integration Suite managed OAuth2 credential store\) + +- OAuth2 - Custom \(Adapter managed OAuth2 credential store\) + + + + +
+ +*Access Token Fetch/Refresh Interval \(in secs\) \(Only when using \`OAuth2\` authentication\)* + + + + + +The interval in seconds for fetching the access token from the respective Integration Suite's credential store when OAuth2 credential type is *Client Credentials* or *Authorization Code*. When *OAuth2 - Custom* type is selected, it is the interval at which the token is refreshed. By default, the value is 300 secs. + + + +
+ +*OAuth2 Client Credentials Credential Name \(Only when using \`OAuth2\` authentication and \`OAuth2 Client Credentials\` OAuth2 credential type\)* + + + + + +The alias of the deployed OAuth2 Client Credentials artifact in the Integrations Suite's Credential Store. See \[Deploying an OAuth2 Client Credentials\]\(https://help.sap.com/docs/cloud-integration/sap-cloud-integration/deploying-oauth2-client-credentials-artifact\) know more. + + + +
+ +*OAuth2 Authorization Code Credential Name\(Only when using \`OAuth2\` authentication and \`OAuth2 Authorization Code\` OAuth2 credential type\)* + + + + + +The alias of the deployed OAuth2 Authorization Code artifact in the Integrations Suite's Credential Store. See \[Deploying an OAuth2 Authorization Code\]\(https://help.sap.com/docs/cloud-integration/sap-cloud-integration/deploying-oauth2-authorization-code\) know more. + + + +
+ +*OAUTH2 Access Token Secure Alias\(Only when using \`OAuth2\` authentication and \`OAuth2 - Custom\` OAuth2 credential type\)* + + + + + +The alias of OAuth2 Access token, stored as Secure Parameter. + + + +
+ +*OAUTH2 Refresh Token Secure Alias\(Only when using \`OAuth2\` authentication and \`OAuth2 - Custom\` OAuth2 credential type\)* + + + + + +The alias of the OAuth2 Refresh token, stored as Secure Parameter. + + + +
+ +*OAUTH2 Client ID Secure Alias\(Only when using \`OAuth2\` authentication and \`OAuth2 - Custom\` OAuth2 credential type\)* + + + + + +The alias of the OAuth2 Client ID, stored as Secure Parameter. + + + +
+ +*OAUTH2 Refresh Token URL Secure Alias\(Only when using \`OAuth2\` authentication and \`OAuth2 - Custom\` OAuth2 credential type\)* + + + + + +The alias of the OAuth2 Refresh token URL, stored as Secure Parameter. + + + +
+ +*JCSMP Properties* + + + + + +A map of key-value pairs to configure additional connection properties. See [JCSMP Properties](https://docs.solace.com/API-Developer-Online-Ref-Documentation/java/com/solacesystems/jcsmp/JCSMPProperties.html) and [JCSMP Channel Properties](https://docs.solace.com/API-Developer-Online-Ref-Documentation/java/com/solacesystems/jcsmp/JCSMPChannelProperties.html) for the available options. + +> ### Note: +> JCSMP channel property keys must be prepended by \`CLIENT\_CHANNEL\_PROPERTIES.\`. For example: +> +> - \`GENERATE\_SENDER\_ID\` \(regular JCSMP property\) +> +> - \`CLIENT\_CHANNEL\_PROPERTIES.ReconnectRetries\` \(JCSMP channel property\) + + + +
+ +Switch to the *Processing* tab to configure the adapter's message processing details. + +**Processing** + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ +Parameter + + + + + +Description + + + +
+ +*Consumer Mode* + + + + + +The adapter's consumer mode. The available options are: + +- Direct + +- Guaranteed + + + + +
+ +*Topic Subscriptions\(Only when using \`Direct\` consumer mode\)* + + + + + +The list of AEM topic subscriptions from which messages will be consumed. + +> ### Note: +> Special characters may need to be UTF-8 encoded. For example: \`\>\` as \`%3E\`. + + + +
+ +*Parallel Consumers\(Only when using \`Guaranteed\` consumer mode\)* + + + + + +The number of concurrent consumer flows. + +> ### Note: +> If the IFlow is running with more than 1 worker, this will be a multiple of the number of workers. For eg. if you configure this value to 3 and the IFlow is running with 2 workers, in total there will be 6 consumers. + + + +
+ +*Selector\(Only when using \`Guaranteed\` consumer mode\)* + + + + + +A SQL-92 selector to filter messages for consumption. + + + +
+ +*Acknowledgment Mode\(Only when using \`Guaranteed\` consumer mode\)* + + + + + +The strategy to be used when acknowledging messages. The possible options are: + +- Automatic Immediate + +- Messages are acknowledged immediately after being read from the event broker. + +- Automatic On Exchange Complete. + +- Messages are acknowledged upon exchange completion. + + + + +
+ +*Settlement Outcome After Maximum Attempts\(Only when using \`Guaranteed\` consumer mode and \`Automatic On Exchange Complete\` acknowledgment mode\)* + + + + + +Settlement outcome for failed messages after all processing attempts have been exhausted. The possible options are: + +- Failed: This negative acknowledgment notifies the event broker that the message was not processed. The event broker will attempt to redeliver the message while adhering to delivery count limits. + +- Rejected: This negative acknowledgment notifies the event broker that the message was not accepted. The event broker will remove the message from its queue and then move the message to the Dead Message Queue \(DMQ\) if it is configured. + + + + +
+ +*Maximum Message Processing Attempts* + + + + + +The maximum number of attempts to process a message. + + + +
+ +*Retry Interval \(in ms\)\(Only when using more than 1 maximum message processing attempts\)* + + + + + +The initial time interval to delay retrying to process a message. + + + +
+ +*Maximum Retry Interval \(in ms\)\(Only when using more than 1 maximum message processing attempts\)* + + + + + +The maximum time interval to delay retrying to process a message. + + + +
+ +*Exponential Backoff Multiplier\(Only when using more than 1 maximum message processing attempts\)* + + + + + +The multiplier to apply to the current time interval delay after every subsequent retry of a message. If set to \`1\`, this is equivalent to applying a fixed delay. + + + +
+ +*Message Headers* + + + + + +The adapter accepts headers on both Sender and Receiver side. + +The Sender adds the following headers: ApplicationMessageId, ApplicationMessageType, CoS, CorrelationId, DeliveryCount, Destination, DestinationEndpointType, Expiration, HttpContentEncoding, HttpContentType, IsDiscardIndication, IsDMQEligible, IsElidingEligible, IsRedelivered, IsReplyMessage, Priority, ReceiveTimestamp, ReplicationGroupMessageId, ReplyToEndpointType, ReplyToDestination, SenderId, SenderTimestamp, SequenceNumber, TimeToLive, UserProperties. When setting up the integration flow, add them to the allowlist via Integration Flow -\> Runtime Configuration -\> Allowed Header\(s\), if required. See [Specify the Runtime Configuration](https://help.sap.com/docs/cloud-integration/sap-cloud-integration/specify-runtime-configuration) + + + +
+ diff --git a/docs/ISuite/50-Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md b/docs/ISuite/50-Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md index aab0fc6b..3097fbe3 100644 --- a/docs/ISuite/50-Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md +++ b/docs/ISuite/50-Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md @@ -465,16 +465,9 @@ By default the value is set to *Server Snapshot-Based* which is the recommended -Maximum number of records in one page of results fetched from the service. If set to Zero or empty, it fetches the default page size. +Maximum number of records in one page from the available results fetched from the service. The value is set to *Empty* by default. -The value is set to *Empty* by default. - -If no value is set, then Server-side pagination\(**\_next** link\) is considered. - -If a value is entered, Client-side pagination is considered with the value provided. - -> ### Note: -> It's recommended to leave the value *Empty*. +If set to empty, fetches the default page size which is 1000 records. diff --git a/docs/ISuite/50-Development/flow-08b40d9.md b/docs/ISuite/50-Development/flow-08b40d9.md index 70a71bd7..16c10d82 100644 --- a/docs/ISuite/50-Development/flow-08b40d9.md +++ b/docs/ISuite/50-Development/flow-08b40d9.md @@ -10,6 +10,9 @@ A processing pipeline comprises of a Request and a Response stream. Proxy endpoi - **Conditional Flow**: A condition associated to a flow. A flow can contain one or more conditions. However, only the first condition met is executed. Configure a conditional Flow when you want a set of policies to be executed only when a condition is met. You can define multiple conditional Flows. However, a conditional flow segment is executed only when a match is found with the criteria defined in the Conditional String. Once a conditional Flow is executed, all other succeeding conditional Flows along the chain will not be executed. For example, you want to convert XML to JSON only when the requesting application is running on a mobile device. This scenario can be configured by setting up conditional Flows. + > ### Note: + > If you need a custom ordering of conditional flows, you can modify it in the proxy zip. The proxy zip can be exported and in the *proxyzip* \> *APIProxy* \> *APIProxyEndPoint* \> *default.xml file*, you can order the sequence of the conditional flows as needed. However, please note that the DefaultFaultFlow will always be appended at the end, regardless of the sequence order assigned to other flows. + - **PostFlow**: This flow is always executed as the last step in the segment where it is applied, after the conditional flow. Configure a PostFlow when you want to log some data or send a notification that something happened. A PostFlow is always executed regardless of the situation. - **PostClientFlow**: This is an optional flow that executes after the response message has been sent to the requesting client application. You can add a PostClientFlow only to the response flow of a ProxyEndpoint. PostClientFlow reduces API proxy latency and makes information available for logging that is not calculated until after the response is returned to the client. diff --git a/docs/ISuite/50-Development/integration-flow-configuration-version-2-0-6d4cdd1.md b/docs/ISuite/50-Development/integration-flow-configuration-version-2-0-6d4cdd1.md index 1d33ddbc..ed2d5e6a 100644 --- a/docs/ISuite/50-Development/integration-flow-configuration-version-2-0-6d4cdd1.md +++ b/docs/ISuite/50-Development/integration-flow-configuration-version-2-0-6d4cdd1.md @@ -10,7 +10,7 @@ The AS2 Adapter has two configuration modes - *Profile* and *Channel*. The Profi To know more on how to configure this profile mode, see [Creating a Trading Partner Profile](creating-a-trading-partner-profile-542fb11.md). -If you want to make your active agreement compatible with this version, follow the steps mentioned here . +If you want to make your active agreement compatible with this version, follow the steps mentioned here [Migration Steps for 2.0 Compatibility](migration-steps-for-2-0-compatibility-8631960.md). > ### Note: > This is a configure-only package and hence, you cannot edit the integration flows. @@ -219,6 +219,5 @@ Follow the steps below to copy the integration package to your *Design* space. - [Interchange Processing Flow V2](interchange-processing-flow-v2-cd26ea5.md) - [Receiver Communication Flow V2](receiver-communication-flow-v2-3897ded.md) - - diff --git a/docs/ISuite/50-Development/message-status-733a57b.md b/docs/ISuite/50-Development/message-status-733a57b.md index ca735dd1..df4d2eae 100644 --- a/docs/ISuite/50-Development/message-status-733a57b.md +++ b/docs/ISuite/50-Development/message-status-733a57b.md @@ -146,7 +146,7 @@ For example, assume that an integration flow is initiated by a Timer event \(sch -ABANDONDED +ABANDONED @@ -156,7 +156,7 @@ ABANDONDED Message processing was interrupted or log wasn't updated for an uncommonly long time. The status can change in case processing is resumed. > ### Note: -> When the message processing is interrupted because of a re- or undeployment of an integration flow, or a controlled worker node shutdown, the MPL is immediately set to ABANDONDED. This status isn’t final and the processing can be resumed if retries are configured. If there are hard worker node crashes, the status is changed to ABANDONDED by an asynchronous system job, after some time of inactivity +> When the message processing is interrupted because of a re- or undeployment of an integration flow, or a controlled worker node shutdown, the MPL is immediately set to ABANDONED. This status isn’t final and the processing can be resumed if retries are configured. If there are hard worker node crashes, the status is changed to ABANDONED by an asynchronous system job, after some time of inactivity diff --git a/docs/ISuite/50-Development/migration-steps-for-2-0-compatibility-8631960.md b/docs/ISuite/50-Development/migration-steps-for-2-0-compatibility-8631960.md new file mode 100644 index 00000000..1fe4d49e --- /dev/null +++ b/docs/ISuite/50-Development/migration-steps-for-2-0-compatibility-8631960.md @@ -0,0 +1,26 @@ + + + + +# Migration Steps for 2.0 Compatibility + +Migrate an active agreement that uses AS2 Sender adapter to make it compatible with the 2.0 version of the generic integration flow. + +The 2.0 version of the generic integration flow is not compatible with all existing active agreements. The AS2 adapter now consists of two configuration modes -*Profile* and *Channel* mode and the latest integration flow configuration works only with the *Profile* mode of the AS2 adapter. + +Let us say, you have an active agreement that uses the AS2 Sender adapter and is not compatible with this version but you would like to make it work with this version. If that is the requirement, you need to make few configuration changes. Follow the steps mentioned below: + +1. Login to your application. + +2. Navigate to *Design* \> *B2B Scenarios*. +3. Choose the *Agreements* tab. +4. Search and open the active Agreement that you want to migrate. +5. Choose *Deactivate* and select *OK* in the resulting dialog. This will deactivate the agreement. +6. Close your agreement and navigate to the *Trading Partners* tab. +7. Select and open the trading partner that you have used in the agreement that you deactivated. +8. Navigate to the *Systems* tab and open the system that you have used in the agreement. +9. Navigate to the *Communications* tab and select Edit :pencil2: button next to the AS2 Sender entry. This will add the *Security Configuration Mode* to the communication channel. +10. Choose *Save*. +11. Close the partner profile and navigate back to the *Agreements* tab. +12. Open the deactivated agreement and choose *Activate*. This updated agreement is now compatible with the 2.0 generic integration flow version. + diff --git a/docs/ISuite/50-Development/sender-communication-flow-v2-5b946c5.md b/docs/ISuite/50-Development/sender-communication-flow-v2-5b946c5.md index 8cded45b..829e5621 100644 --- a/docs/ISuite/50-Development/sender-communication-flow-v2-5b946c5.md +++ b/docs/ISuite/50-Development/sender-communication-flow-v2-5b946c5.md @@ -28,7 +28,7 @@ Follow the procedure below to configure these integration flows. > The activation will create two new PD entries for the values above and these entries are specific to an user account. So, if there are multiple agreements that use the AS2 Sender Communication of the same user account with no changes made to the *Security* or *Processing*, then you need to activate only one agreement so that the entries are created for this user account. > > - If you have configured AS2 Partner ID based security configurations in the *Security* tab of the partner profile, then on activation of agreements using these configurations can potentially overwrite similar AS2 Partner ID based configurations done outside of Trading Partner Management solution. To know more about the IDs that could be potentially impacted, see [Creating a Trading Partner Profile](creating-a-trading-partner-profile-542fb11.md). -> - If you have an active agreement that consists of the AS2 adapter but is not compatible with 2.0 version of the integration flow, you need to deactivate the agreement and follow few more steps to make it work with this version. To know more, see +> - If you have an active agreement that consists of the AS2 adapter but is not compatible with 2.0 version of the integration flow, you need to deactivate the agreement and follow few more steps to make it work with this version. To know more, see [Migration Steps for 2.0 Compatibility](migration-steps-for-2-0-compatibility-8631960.md) diff --git a/docs/ISuite/index.md b/docs/ISuite/index.md index 14e304f8..e5c57c63 100644 --- a/docs/ISuite/index.md +++ b/docs/ISuite/index.md @@ -304,6 +304,9 @@ - [Consuming Integration Adapters from SAP Business Accelerator Hub](50-Development/consuming-integration-adapters-from-sap-business-accelerator-hub-b9250fb.md) - [Import Integration Adapters](50-Development/import-integration-adapters-386d7d0.md) - [Configure Adapter in Communication Channels](50-Development/configure-adapter-in-communication-channels-1f06633.md) + - [Advanced Event Mesh Adapter](50-Development/advanced-event-mesh-adapter-dd7e034.md) + - [Configure the Advanced Event Mesh Sender Adapter](50-Development/configure-the-advanced-event-mesh-sender-adapter-abd2efc.md) + - [Configure the Advanced Event Mesh Receiver Adapter](50-Development/configure-the-advanced-event-mesh-receiver-adapter-881f656.md) - [AMQP Adapter](50-Development/amqp-adapter-5cc1a71.md) - [Configure the AMQP Sender Adapter](50-Development/configure-the-amqp-sender-adapter-99ce674.md) - [AMQP Sender for SAP Event Mesh](50-Development/amqp-sender-for-sap-event-mesh-7d8a83f.md) @@ -1185,6 +1188,7 @@ - [Interchange Processing Flow V2](50-Development/interchange-processing-flow-v2-cd26ea5.md) - [Receiver Communication Flow V2](50-Development/receiver-communication-flow-v2-3897ded.md) - [Reusable Groovy Scripts](50-Development/reusable-groovy-scripts-77bc3ee.md) + - [Migration Steps for 2.0 Compatibility](50-Development/migration-steps-for-2-0-compatibility-8631960.md) - [Integration Content Development](50-Development/integration-content-development-4524e53.md) - [Custom Type Systems](50-Development/custom-type-systems-884bb25.md) - [Adding a Custom Message](50-Development/adding-a-custom-message-8b7eb45.md) diff --git a/docs/ISuite/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md b/docs/ISuite/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md index bd20bb63..57685079 100644 --- a/docs/ISuite/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md +++ b/docs/ISuite/requesting-a-custom-domain-for-a-virtual-host-6b9e5a3.md @@ -10,7 +10,7 @@ Virtual host is an entity where the API proxy gets deployed, and API proxies can ## Context -During onboarding, when you enable the API Management capability within Integration Suite , a virtual host is created by default, and you can execute the APIs using the URL of this virtual host. The domain for this virtual host URL is specific to the SAP data center where the tenant is onboarded. +During onboarding, when you enable the API Management capability within Integration Suite, a virtual host is created by default, and you can execute the APIs using the URL of this virtual host. The domain for this virtual host URL is specific to the SAP data center where the tenant is onboarded. Once onboarding is completed, you can create an additional virtual host. You have the option to create the virtual host with a domain that is specific to your organization. This domain is referred to as a Custom Domain. diff --git a/docs/apim/API-Management/APIM-Development/flow-08b40d9.md b/docs/apim/API-Management/APIM-Development/flow-08b40d9.md index fcb7574d..dbdea0ed 100644 --- a/docs/apim/API-Management/APIM-Development/flow-08b40d9.md +++ b/docs/apim/API-Management/APIM-Development/flow-08b40d9.md @@ -10,6 +10,9 @@ A processing pipeline comprises of a Request and a Response stream. Proxy endpoi - **Conditional Flow**: A condition associated to a flow. A flow can contain one or more conditions. However, only the first condition met is executed. Configure a conditional Flow when you want a set of policies to be executed only when a condition is met. You can define multiple conditional Flows. However, a conditional flow segment is executed only when a match is found with the criteria defined in the Conditional String. Once a conditional Flow is executed, all other succeeding conditional Flows along the chain will not be executed. For example, you want to convert XML to JSON only when the requesting application is running on a mobile device. This scenario can be configured by setting up conditional Flows. + > ### Note: + > If you need a custom ordering of conditional flows, you can modify it in the proxy zip. The proxy zip can be exported and in the *proxyzip* \> *APIProxy* \> *APIProxyEndPoint* \> *default.xml file*, you can order the sequence of the conditional flows as needed. However, please note that the DefaultFaultFlow will always be appended at the end, regardless of the sequence order assigned to other flows. + - **PostFlow**: This flow is always executed as the last step in the segment where it is applied, after the conditional flow. Configure a PostFlow when you want to log some data or send a notification that something happened. A PostFlow is always executed regardless of the situation. - **PostClientFlow**: This is an optional flow that executes after the response message has been sent to the requesting client application. You can add a PostClientFlow only to the response flow of a ProxyEndpoint. PostClientFlow reduces API proxy latency and makes information available for logging that is not calculated until after the response is returned to the client. diff --git a/docs/apim/API-Management/what-is-api-management-0aef763.md b/docs/apim/API-Management/what-is-api-management-0aef763.md index e53b643c..91f9781c 100644 --- a/docs/apim/API-Management/what-is-api-management-0aef763.md +++ b/docs/apim/API-Management/what-is-api-management-0aef763.md @@ -1,5 +1,7 @@ + + # What is API Management Create simple digital experiences for your consumers, partners, and employees. @@ -11,6 +13,27 @@ The Cloud Foundry environment gives you the ability to subscribe to the API Mana > ### Tip: > This is the documentation for API Management for Cloud Foundry. If you are looking for information about the Neo environment, see [here](https://help.sap.com/viewer/38c3df3f8da44a809f937220b3579607/Cloud/en-US). +> ### Tip: +> The English version of this guide is open for contributions and feedback using GitHub. This allows you to get in contact with responsible authors of SAP Help Portal pages and the development team to discuss documentation-related issues. To contribute to this guide, or to provide feedback, choose the corresponding option on SAP Help Portal: +> +> - *Feedback* \> *Create issue*: Provide feedback about a documentation page. This option opens an issue on GitHub. +> +> - *Feedback* \> *Edit page*: Contribute to a documentation page. This option opens a pull request on GitHub. +> +> +> You need a GitHub account to use these options. +> +> More information: +> +> - [Contribution Guidelines](https://help.sap.com/docs/open-documentation-initiative/contribution-guidelines/readme.html) +> +> - [Introduction Video: Open Documentation Initiative](https://www.youtube.com/watch?v=WJ0oarMlVW4) +> +> - [Blog Post: Introducing the Open Documentation Initiative](https://blogs.sap.com/2021/05/20/introducing-the-open-documentation-initiative/) + +> ### Tip: +> Contextual help is available for some screens of the SAP Integration Suite. To activate this help, from the top toolbar, choose Help. A panel with help topics opens alongside your current screen to your right. You will also find green Help icons on the screen. Choose these icons to know more about the associated element. + ## Features diff --git a/docs/ci/ConnectionSetup/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md b/docs/ci/ConnectionSetup/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md index e2967be8..6683013a 100644 --- a/docs/ci/ConnectionSetup/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md +++ b/docs/ci/ConnectionSetup/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md @@ -142,7 +142,7 @@ Create a service instance to implement inbound communication. A service instance > ### Note: > We recommend you use a CLI-friendly name to enable the managing of your instances with the SAP BTP command line interface as well. > - > CLI-friendly name is a short string \(up to 32 characters\) that only contains alphanumeric characters \(A-Z, a-z, 0-9\), periods, underscores, and hyphens. + > CLI-friendly name is a short string \(up to 32 characters\) that only contains alphanumeric characters \(A-Z, a-z, 0–9\), periods, underscores, and hyphens. > > Your instance name can't contain white spaces if you want your instance name to be CLI-friendly. @@ -156,7 +156,7 @@ Create a service instance to implement inbound communication. A service instance 8. Configure instance parameters. Choose how to enter your details, via *Form* or *JSON*. - We recommend to choose *Form* as the more convenient option. + We recommend choosing *Form* as the more convenient option. Specify the following parameters. @@ -192,7 +192,7 @@ Create a service instance to implement inbound communication. A service instance - When as *Plan* you've chosen *integration-flow*, you can either keep the standard role `ESBMessaging.send` or enter a custom role \(see [Managing User Roles, Cloud Foundry Environment](../Operations/managing-user-roles-cloud-foundry-environment-4e86f0d.md)\). - You are able to add multiple roles by pressing enter after each role. The default is set to the standard role \(`ESBMessaging.send`\). + You're able to add multiple roles by pressing enter after each role. The default is set to the standard role \(`ESBMessaging.send`\). > ### Tip: > When defining a service instance with *integration-flow* plan, you assign a role to it that enables the associated user to process the integration flow on the worker node. Simply spoken, this role defines permission for a sender to process an integration flow. @@ -253,6 +253,29 @@ Create a service instance to implement inbound communication. A service instance + + + + + + *Access Token Validity* \(in seconds\) + + + + + + + Define the period of time for which your access token is valid in seconds. Enter any value from `3600` to `86400` \(1- 24 hours\). + + The following values have been set as default: + + - for plan `api`: `4300` \(12 hours\) + + - for plan `integration-flow`: `3600` \(1 hour\) + + + + @@ -343,7 +366,9 @@ With this step, you create a service key for the instance. - *External Certificate* \(only applicable if for *Key Type* the option *External Certificate* has been chosen\) + *External Certificate* + + \(only applicable if for *Key Type* the option *External Certificate* has been chosen\) @@ -368,7 +393,48 @@ With this step, you create a service key for the instance. Make sure that the certificate is signed by a certification authority supported by the load balancer \(see [Load Balancer Root Certificates Supported by SAP](load-balancer-root-certificates-supported-by-sap-4509f60.md)\). - You can only use a single certificate once across all existing service instances. To assign multiple roles, don't create multiple service instances. Instead of this, maintain multiple roles within one service instance. + You can only use a single certificate once across all existing service instances. To assign multiple roles, don't create multiple service instances. Instead, maintain multiple roles within one service instance. + + + + + + + + + *Pin Certificate* + + \(only available for plan `integration-flow` and only applicable if for *Key Type* the option *External Certificate* has been chosen\) + + + + + + + Defines whether the exact client certificate is required for authentication. + + If this setting is **enabled** \(=default\), the incoming client certificate used during authentication must match the stored certificate in the service key exactly. In case the client certificate is renewed, a new service key with the new certificate has to be created. See: [Service Key Types](service-key-types-0fc1446.md). + + If this setting is **disabled**, only the subjectDN and issuerDN of the incoming client certificate will be compared. This allows you to use renewed client certificates for authentication without changing the service key thus reducing configuration efforts. + + The following conditions need to be fulfilled for a renewed certificate: + + - The renewed certificate has the same subjectDN and issuerDN as the certificate configured in the service key. + + - The issueDate of the renewed certificate must be issued after the previously accepted certificate. + + + > ### Note: + > Once a new certificate was used for authentication purposes, the previously used certificate \(with an older issueDate\) won't be accepted anymore. + + > ### Caution: + > You must ensure that there are no conflicts between certificates uploaded in different service keys. A call with such a certificate will be rejected at runtime, if there are: + > + > - multiple certificates with the same subjectDN and issuerDN where pinning is disabled; + > + > - or one certificate with pinning enabled and another certificate with the same subjectDN and issuerDN where pinning is disabled. + + . @@ -377,7 +443,9 @@ With this step, you create a service key for the instance. - *Validity in days* \(only applicable if for *Key Type* the option *Certificate* has been chosen\) + *Validity in days* + + \(only applicable if for *Key Type* the option *Certificate* has been chosen\) @@ -393,7 +461,9 @@ With this step, you create a service key for the instance. - *Key Size* \(only applicable if for *Key Type* the option *Certificate* has been chosen\) + *Key Size* + + \(only applicable if for *Key Type* the option *Certificate* has been chosen\) @@ -519,11 +589,11 @@ With this step, you create a service key for the instance. > ### Note: > The generated certificate also contains additional parameters under *certificatedetails*. > - > When for *Key Type* you have chosen *Certificate*, the following applies for these parameters: + > When for *Key Type*, you've chosen *Certificate*, the following applies for these parameters: > > - The values for the parameters *issuerdn*, *serialnumber*, and *subjectdn* are determined by SAP. > - > - The value of parameter *validuntil* is calculated from the entry that you have selected for *Validity in days* when defining the service key. + > - The value of parameter *validuntil* is calculated from the entry that you've selected for *Validity in days* when defining the service key. > > > See: [Service Key Types](service-key-types-0fc1446.md) @@ -568,7 +638,7 @@ With this step, you create a service key for the instance. > ### Note: - > You have 2 options to display these parameters: + > You have two options to display these parameters: > > - *Form* > diff --git a/docs/ci/ConnectionSetup/downloading-a-certificate-signing-request-b199dbe.md b/docs/ci/ConnectionSetup/downloading-a-certificate-signing-request-b199dbe.md index 7c78dfa8..32f13729 100644 --- a/docs/ci/ConnectionSetup/downloading-a-certificate-signing-request-b199dbe.md +++ b/docs/ci/ConnectionSetup/downloading-a-certificate-signing-request-b199dbe.md @@ -49,7 +49,7 @@ You send the CSR to a certification authority, who will provide a signing respon **Related Information** - + [Updating a Key Pair with a Signing Response](../Operations/updating-a-key-pair-with-a-signing-response-4242f01.md "Upload a signing response from a certification authority and use it to update the key pair in your keystore, keeping the alias of the keystore entry unchanged.") diff --git a/docs/ci/ConnectionSetup/setting-up-inbound-http-connections-integration-flow-processing-neo-environment-778c7e7.md b/docs/ci/ConnectionSetup/setting-up-inbound-http-connections-integration-flow-processing-neo-environment-778c7e7.md index b6e0a04d..9d2f2079 100644 --- a/docs/ci/ConnectionSetup/setting-up-inbound-http-connections-integration-flow-processing-neo-environment-778c7e7.md +++ b/docs/ci/ConnectionSetup/setting-up-inbound-http-connections-integration-flow-processing-neo-environment-778c7e7.md @@ -278,7 +278,7 @@ More information: [Authentication and Authorization Options \(Inbound\)](authentication-and-authorization-options-inbound-983f2a5.md "When a client calls a server using a secure communication channel, two different kinds of checks are performed subsequently.") - + [Setting Up Inbound HTTP Connections \(with Certificate-to-User Mapping\), Neo Environment](setting-up-inbound-http-connections-with-certificate-to-user-mapping-neo-environment-9949c61.md "Using this option, authentication of a sender is performed based on a client certificate. With a certificate-to-user mapping, the certificate is mapped to a user, whose authorizations are checked on the tenant.") diff --git a/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-d8fb958.md b/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-d8fb958.md index dda3d326..8f8b5b0f 100644 --- a/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-d8fb958.md +++ b/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-d8fb958.md @@ -57,7 +57,7 @@ Recommended configuration option for secure communication is public key authenti More information: - + @@ -104,7 +104,7 @@ Using this authentication option, the user \(performing the file transfer\) is a More information: - + diff --git a/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-details-e72eba4.md b/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-details-e72eba4.md index 2a913484..3fb7a1d6 100644 --- a/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-details-e72eba4.md +++ b/docs/ci/ConnectionSetup/setting-up-inbound-sftp-connections-details-e72eba4.md @@ -48,7 +48,7 @@ Configure the **sender SFTP adapter** to specify the technical details of how th **Related Information** - + [Creating SFTP Keys](creating-sftp-keys-3485a75.md "You can set up reliable file transfer based on SSH File Transfer Protocol (SFTP). SFTP is an enhancement of the Secure Shell (SSH) network protocol.") diff --git a/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-6e4de95.md b/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-6e4de95.md index ff5b792b..936695b3 100644 --- a/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-6e4de95.md +++ b/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-6e4de95.md @@ -55,7 +55,7 @@ With this is authentication option, the user \(performing the file transfer\) is More information: - + @@ -104,7 +104,7 @@ Supported by SFTP sender adapter. More information: - + diff --git a/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-details-15401a7.md b/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-details-15401a7.md index d68de714..6c53cb82 100644 --- a/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-details-15401a7.md +++ b/docs/ci/ConnectionSetup/setting-up-outbound-sftp-connections-details-15401a7.md @@ -61,7 +61,7 @@ Open the related integration flow and configure the **SFTP receiver adapter** to [Blog: Dynamically Configure the SFTP Receiver Adapter](https://blogs.sap.com/2020/05/29/cloud-integration-dynamically-configure-the-sftp-receiver-adapter/) - + [Creating SFTP Keys](creating-sftp-keys-3485a75.md "You can set up reliable file transfer based on SSH File Transfer Protocol (SFTP). SFTP is an enhancement of the Secure Shell (SSH) network protocol.") diff --git a/docs/ci/Development/configure-the-amqp-receiver-adapter-d5660c1.md b/docs/ci/Development/configure-the-amqp-receiver-adapter-d5660c1.md index 7f17223d..1ddefe1a 100644 --- a/docs/ci/Development/configure-the-amqp-receiver-adapter-d5660c1.md +++ b/docs/ci/Development/configure-the-amqp-receiver-adapter-d5660c1.md @@ -264,7 +264,7 @@ Select the authentication method the message broker supports. *SASL* is selected > ### Note: > This authentication option implies that Transport Layer Security \(TLS\) is used for the connection. - More information: + More information: - *None* diff --git a/docs/ci/Development/configure-the-amqp-sender-adapter-99ce674.md b/docs/ci/Development/configure-the-amqp-sender-adapter-99ce674.md index e3aedb38..a33522d6 100644 --- a/docs/ci/Development/configure-the-amqp-sender-adapter-99ce674.md +++ b/docs/ci/Development/configure-the-amqp-sender-adapter-99ce674.md @@ -264,7 +264,7 @@ Select the authentication method the message broker supports. *SASL* is selected > ### Note: > This authentication option implies that Transport Layer Security \(TLS\) is used for the connection. - More information: + More information: - *None* diff --git a/docs/ci/Development/configure-the-idoc-receiver-adapter-018aa88.md b/docs/ci/Development/configure-the-idoc-receiver-adapter-018aa88.md index 98a3fede..1836bf61 100644 --- a/docs/ci/Development/configure-the-idoc-receiver-adapter-018aa88.md +++ b/docs/ci/Development/configure-the-idoc-receiver-adapter-018aa88.md @@ -173,7 +173,9 @@ There are the following options: - Enables Exactly-Once processing. > ### Note: - > Enables Exactly-Once processing in the backend, if the header `SapMessageId` is set. + > The IDoc adapter uses the header `SapMessageId` within the integration flow processing. If header `SapMessageId` isn't defined, the IDoc receiver adapter automatically generates a unique ID. This may lead to duplicates in situations where an already delivered message is retried. If however the header `SapMessageId` is set, the IDoc receiver adapter reuses its value. For `Exactly-Once` processing in the backend, you need to ensure that the header `SapMessageId` remains the same in case that the message is retried. + > + > See: [Quality of Service Exactly Once](quality-of-service-exactly-once-f96cf27.md) *Text/XML* diff --git a/docs/ci/Development/configure-the-soap-soap-1-x-receiver-adapter-57f7b34.md b/docs/ci/Development/configure-the-soap-soap-1-x-receiver-adapter-57f7b34.md index 13c09a90..b8e16ada 100644 --- a/docs/ci/Development/configure-the-soap-soap-1-x-receiver-adapter-57f7b34.md +++ b/docs/ci/Development/configure-the-soap-soap-1-x-receiver-adapter-57f7b34.md @@ -212,6 +212,8 @@ To select the WSDL from a source, you have the following options: > ### Note: +> - If you’ve configured SAP Cloud Connector with the SOAP receiver adapter, you cannot access WSDL via Cloud Connector. +> > - If you specify a WSDL, you also have to specify the name of the selected service and the name of the port selected for this service. These fields must have a namespace prefix. > > Expected format: `:` diff --git a/docs/ci/Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md b/docs/ci/Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md index e9d65d3c..8601c70e 100644 --- a/docs/ci/Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md +++ b/docs/ci/Development/configure-the-successfactors-odata-v2-receiver-adapter-d16dd12.md @@ -465,16 +465,9 @@ By default the value is set to *Server Snapshot-Based* which is the recommended -Maximum number of records in one page of results fetched from the service. If set to Zero or empty, it fetches the default page size. +Maximum number of records in one page from the available results fetched from the service. The value is set to *Empty* by default. -The value is set to *Empty* by default. - -If no value is set, then Server-side pagination\(**\_next** link\) is considered. - -If a value is entered, Client-side pagination is considered with the value provided. - -> ### Note: -> It's recommended to leave the value *Empty*. +If set to empty, fetches the default page size which is 1000 records. diff --git a/docs/ci/Development/conversion-rules-for-json-to-xml-conversion-232a9cf.md b/docs/ci/Development/conversion-rules-for-json-to-xml-conversion-232a9cf.md index 7238fa8b..7811f09b 100644 --- a/docs/ci/Development/conversion-rules-for-json-to-xml-conversion-232a9cf.md +++ b/docs/ci/Development/conversion-rules-for-json-to-xml-conversion-232a9cf.md @@ -86,5 +86,5 @@ The conversion from JSON format to XML format follows the following rules: [Define JSON to XML Converter](define-json-to-xml-converter-5a7c0cd.md "The JSON to XML converter enables you to transform messages in JSON format to XML format.") - + diff --git a/docs/ci/Development/conversion-rules-for-xml-to-json-conversion-66d099d.md b/docs/ci/Development/conversion-rules-for-xml-to-json-conversion-66d099d.md index 2e2b5dff..87f06ec9 100644 --- a/docs/ci/Development/conversion-rules-for-xml-to-json-conversion-66d099d.md +++ b/docs/ci/Development/conversion-rules-for-xml-to-json-conversion-66d099d.md @@ -92,7 +92,7 @@ The conversion from XML format to JSON format follows the following rules: [How Streaming in the XML-to-JSON Converter Works](how-streaming-in-the-xml-to-json-converter-works-4e05044.md "During streaming the XML document is processed in parts or segments:") - + - + diff --git a/docs/ci/Development/creating-message-mapping-as-a-flow-step-3d5cb7f.md b/docs/ci/Development/creating-message-mapping-as-a-flow-step-3d5cb7f.md index 6a2bd76a..32b856de 100644 --- a/docs/ci/Development/creating-message-mapping-as-a-flow-step-3d5cb7f.md +++ b/docs/ci/Development/creating-message-mapping-as-a-flow-step-3d5cb7f.md @@ -191,7 +191,7 @@ The supported file types for source and target messages are: 2. Specify a name for the mmap file and choose *Create*. - 3. Add source and target messages. If you want to consume Message Types, see . + 3. Add source and target messages. If you want to consume Message Types, see . 4. Drag fields from the source to the required field in the target to create a mapping. @@ -203,6 +203,9 @@ The supported file types for source and target messages are: > While modeling message mapping, if you've nodes whose outputs aren't connected in the mapping expression then on saving the mapping, these nodes get removed automatically. + +Now that you've defined the mapping, proceed with further actions. + 5. You can create your own custom mapping function. Here's how: 1. In the *Mapping Expression* screen area, choose \(Create\) . @@ -213,7 +216,7 @@ The supported file types for source and target messages are: 3. Enter the script for the custom function you want to create and choose *OK* - 4. To assign a function library object as an user-defined function, see: . + 4. To assign a function library object as an user-defined function, see: . 6. Configure the settings of the message mapping to handle basic data types in the target JSON schema. diff --git a/docs/ci/Development/creating-message-mapping-as-an-artifact-1d52a7b.md b/docs/ci/Development/creating-message-mapping-as-an-artifact-1d52a7b.md index 003bd8f2..94cc287c 100644 --- a/docs/ci/Development/creating-message-mapping-as-an-artifact-1d52a7b.md +++ b/docs/ci/Development/creating-message-mapping-as-an-artifact-1d52a7b.md @@ -1,142 +1,188 @@ - - # Creating Message Mapping as an Artifact Helps you to reuse message mapping resources in different integration scenarios by directly accessing the mapping artifacts. > ### Note: -> There's the following limitation when you've chosen a runtime profile for SAP Process Orchestration \(any support package\) and you intend to use an integration flow on an SAP Process Orchestration runtime: Don't use message mapping artifacts. Instead of this, define the message mapping as part of the integration flow. +> There's the following limitation when you've chosen a runtime profile for SAP Process Orchestration \(any support package\) and you intend to use an integration flow on an SAP Process Orchestration runtime: Don't use message mapping artifacts. Instead, define the message mapping as a flow step in the integration flow. + +Message mapping as an artifact consists of a mapping definition \(\*.mmap\) file that is created or imported by a user. When you build your integration scenario, you can refer these artifacts from a message mapping step in the integration flow. + + + + + +## Benefits of Using Message Mapping Artifacts + +- **Reusability** – Refer the mapping artifacts in multiple integration scenarios instead of manually uploading them every time and avoid duplicates. + +- **Reduce Maintenance Efforts** – By referring the artifact from a single place, you only have to edit the artifact once if there are changes needed. + +- **Reduce File Size and Memory Usage** – By avoiding multiple upload instances you can get extra storage space. + + + + + + +## Create a Message Mapping Artifact + + + + + +## Prerequisites -Message mapping as an artifact consists of a mapping definition \(\*.mmap\) file that is created or imported by a user. When you build your integration scenario, you can refer these artifacts to the message mapping step configured in the integration flow. +You've created an integration package and opened it in edit mode. - + -## Adding Message Mapping Artifact in an Integration Package +## Context -**Ways to Define a Message Mapping Artifact:** +Create a new message mapping artifact that consists of source and target schema files. With the help of the mapping editor you can add schema files, define mapping between source and target messages, and create a groovy script to consume user-defined Functions \(UDFs\). - - - - - - - - - - - - - - - - - -
-Action + +## Procedure +1. In the *Artifacts* tab of the integration package, choose *Add* \> *Message Mapping*. - +2. In the dialog box that comes up, choose *Create*. -Description +3. Provide a name, ID, and an optional description for the message mapping. +4. Choose *Add*. + A message mapping artifact is created. -
+5. Open the message mapping artifact and choose *Edit* to add source and target messages, create mappings, and perform operations. Choose *Save*. -*Create* +6. Choose *Deploy*. + Before consuming a message mapping artifact, you must first deploy it. - + -You use it to create new message mapping artifact project that consists of source and target schema files. With the help of the mapping editor you can add schema files, define mapping between source and target messages and create a groovy script to consume user-defined Functions \(UDFs\). + +## Upload a Message Mapping Artifact -
-*Upload* + +## Prerequisites +- You've created an integration package and opened it in edit mode. - +- You've a message mapping artifact downloaded in your file system. The downloaded artifact can be from the same tenant or a different one. -You use this option to upload a message mapping artifact stored on your computer. Once selected, you can upload a message mapping definition as a zip file from your file system. + + + + + +## Context + +Use this option to upload a message mapping artifact stored on your computer. Once selected, you can upload a message mapping definition as a zip file from your file system. > ### Note: -> While uploading a message mapping artifact, make sure that the file is compatible with the service plan of your tenant. If your tenant doesn't support function libraries or message type artifacts and you attempt to upload a message mapping artifact that contains them, you must rework on your mapping which is not a good experience. See SAP Note [2903776](https://launchpad.support.sap.com/#/notes/2903776). +> While uploading a message mapping artifact, make sure that the file is compatible with the service plan of your tenant. If your tenant doesn't support function libraries or message type artifacts and you attempt to upload a message mapping artifact that contains them, you must rework on your mapping that isn't a good experience. See SAP Note [2903776](https://launchpad.support.sap.com/#/notes/2903776). > -> If the function libraries or message type artifacts are consumed in the mapping, you face an error stating that you cannot consume the mapping. If the function libraries or message type artifacts are just referred \(not consumed\) in the mapping, you don't see the references at all in the mapping. +> If the function libraries or message type artifacts are consumed in the mapping, you face an error stating that you can't consume the mapping. If the function libraries or message type artifacts are referred \(not consumed\) in the mapping, you don't see the references at all in the mapping. -
+ -*ES Repository* +## Procedure +1. In the *Artifacts* tab of the integration package, choose *Add* \> *Message Mapping*. +2. In the dialog box that comes up, choose *Upload*. - +3. Choose *Browse* to upload a .zip file that contains the message mapping content. -You use this option to import a message mapping created in the Enterprise Services Repository \(ES Repository\). For more information on importing such content, see [Importing Mapping Content from ES Repository](../IntegrationSettings/importing-mapping-content-from-es-repository-e18fc05.md). +4. Provide a name, ID, and an optional description for the message mapping. +5. Choose *Add*. + A message mapping artifact is created. -
+6. Open the message mapping artifact and choose *Edit* to change the source and target messages, create mappings, and perform operations. Choose *Save*. +7. Choose *Deploy*. + Before consuming a message mapping artifact, you must first deploy it. - -## How to Refer a Message Mapping Artifact in an Integration Flow? + -We assume that you've added a mapping step in your integration flow. See: [Working with Mapping](working-with-mapping-68d816a.md). + -Consuming a mapping artifact is a two-step process in your integration flow. +## Import a Message Mapping from ES Repository -1. To add message mapping artifacts as reference resources in your integration flow, perform the following steps: - 1. Open your integration flow in edit mode. - 2. In the property sheet, choose *Resources* \> *References* \> *Add References* \> *Message Mapping*. + - 3. Select one or more message mapping artifacts that you like to reuse in your integration scenario. +## Prerequisites - 4. Choose *OK*. +- You've created an integration package and opened it in edit mode. +- You've established connection to your SAP Process Orchestration system. See: [Configuring Connectivity to an SAP Process Orchestration System](../IntegrationSettings/configuring-connectivity-to-an-sap-process-orchestration-system-8c36fd2.md). -2. To reuse mapping artifacts in a message mapping step, perform the following steps: - 1. Choose the quick action in the *Message Mapping* step, and then choose . - 2. In the *Select Mapping Resource* dialog box, choose the *Referenced Resources* tab. - 3. In the message mapping resources-pane, select the referenced mapping artifact. + - 4. Choose *OK*. +## Context +Use this option to import a message mapping object from the Enterprise Services Repository \(ES Repository\). -Make sure that you first deploy the message mapping artifact and then the integration flow that reuses the message mapping artifact. For more information, check out the following SAP Community blog: [Message Mapping as Artifact](https://blogs.sap.com/2021/06/17/sap-cloud-integration-message-mapping-as-artifact/). + +## Procedure - +1. In the *Artifacts* tab of the integration package, choose *Add* \> *Message Mapping*. -## Benefits of Using Message Mapping Artifacts +2. In the dialog box that comes up, choose *ES Repository*. -- **Reusability** – Refer the mapping artifacts in multiple integration scenarios instead of manually uploading them every time and avoid duplicates. +3. In the *Name* list, select an ES Repository from the list of connected systems. -- **Reduce Maintenance Efforts** – By referring the artifact from a single place, you only have to edit the artifact once if there are changes needed. + The *Address* and *Location ID* of the selected ES Repository comes up. -- **Reduce File Size and Memory Usage** – By avoiding multiple upload instances you can get extra storage space. +4. Choose *Connect*. + + A list of message mapping objects from the ES Repository comes up. + +5. Select a message mapping object that you want to import. Choose *Next*. + +6. In the *Dependent Resources* tab, provide a name, ID, and an optional description for the message mapping artifact. You also see a list of dependent files of the message mapping object like function library objects and WSDL files that are to be imported too. Choose *Next*. + +7. Optional, only if the source message mapping object has function library objects: Select one or more Function Libraries artifacts to contain all dependent function library objects of the source mapping object. + + In , a function library object from ES Repository must be imported to a Function Libraries artifact. You can't add a function library object directly to a message mapping or an integration package. See: . + +8. Choose *Add*. + + A message mapping artifact is created. + + If there are dependent function library objects, they are imported to the selected Function Libraries artifact. References to the dependent function library objects are also created. + +9. Open the message mapping artifact and choose *Edit* to change the source and target messages, create mappings, and perform operations. Choose *Save*. + +10. Choose *Deploy*. + + Before consuming a message mapping artifact, you must first deploy it. diff --git a/docs/ci/Development/creating-the-custom-integration-flow-with-the-post-exit-mapping-988e5e3.md b/docs/ci/Development/creating-the-custom-integration-flow-with-the-post-exit-mapping-988e5e3.md index 1bf3e44c..98e0661c 100644 --- a/docs/ci/Development/creating-the-custom-integration-flow-with-the-post-exit-mapping-988e5e3.md +++ b/docs/ci/Development/creating-the-custom-integration-flow-with-the-post-exit-mapping-988e5e3.md @@ -17,7 +17,7 @@ This integration flow is kept very simple. **Related Information** - + [Configuring the ProcessDirect Sender Adapter](configuring-the-processdirect-sender-adapter-4787d80.md "") diff --git a/docs/ci/Development/creating-the-standard-integration-flow-4da82ad.md b/docs/ci/Development/creating-the-standard-integration-flow-4da82ad.md index 44535472..1e131613 100644 --- a/docs/ci/Development/creating-the-standard-integration-flow-4da82ad.md +++ b/docs/ci/Development/creating-the-standard-integration-flow-4da82ad.md @@ -13,7 +13,7 @@ This is a summary of the elements of the integration flow. Check out the detaile - Sender and SOAP sender adapter - The sender is simulated by using a SOAP client that calls the integration flow endpoint using the SOAP 1.x sender adapter. The SOAP client sends message A to Cloud Integration. + The sender is simulated by using a SOAP client that calls the integration flow endpoint using the SOAP 1.x sender adapter. The SOAP client sends message A to SAP Cloud Integration. - Content Modifier diff --git a/docs/ci/Development/define-content-modifier-8f04a70.md b/docs/ci/Development/define-content-modifier-8f04a70.md index 9c44cd45..508cf606 100644 --- a/docs/ci/Development/define-content-modifier-8f04a70.md +++ b/docs/ci/Development/define-content-modifier-8f04a70.md @@ -44,7 +44,7 @@ Note that data written to the message header during a processing step, for examp 2. Place *Content Modifier* step in the integration process. -3. Go to the *Message Header* tab or choose *Exchange Property* \(depending on whether you want to modify a message header or write data to the exchange property\). +3. Go to the *Message Header* or *Exchange Property* tab \(depending on whether you want to modify a message header or write data to the exchange property\). > ### Note: > Name defined for an *Exchange Property* is case-sensitive. This is a known behavior of the camel framework. @@ -244,6 +244,8 @@ Note that data written to the message header during a processing step, for examp *Data Type* + \(If you've selected *XPath* or *Expression* as *Type*\) + @@ -251,11 +253,11 @@ Note that data written to the message header during a processing step, for examp Valid Java data type - The *Data Type* column is used only for the types *XPath* and *Expression*. The data type can belong to any Java class. For example, if you are addressing a string-type element, enter `java.lang.String` as the Java data type. For more information about supported data types, see [https://camel.apache.org/components/latest/languages/simple-language.html](https://camel.apache.org/components/latest/languages/simple-language.html). + The data type can belong to any Java class. For example, if you are addressing a string-type element, enter `java.lang.String` as the Java data type. For more information about supported data types, see [https://camel.apache.org/components/latest/languages/simple-language.html](https://camel.apache.org/components/latest/languages/simple-language.html). If the XPath contains a namespace prefix, specify the association between the namespace and the prefix on the Runtime Configuration tab page of the integration flow Properties view. - To enter an XPath, select *XPath* in the *Type* column and browse for an XPath from the lookup in the *Value* column. + To enter an XPath, browse for an XPath from the lookup in the *Value* column. @@ -266,7 +268,7 @@ Note that data written to the message header during a processing step, for examp *Default Value* - \(Only relevant if you have selected *Local Variable* or *Global Variable* as *Type*\) + \(If you've selected *Local Variable* or *Global Variable* as *Type*\) @@ -281,7 +283,11 @@ Note that data written to the message header during a processing step, for examp -6. Go to the *Message Body* tab, and define the fields as shown below. +6. If you have multiple entries, use the *Move Up* or *Move Down* actions to sort your entries. + + Headers and properties in a content modifier are processed from top to bottom. Therefore, if you want to process the header or properties in a certain order, first add all your entries and then use the "move" actions to sort them in the order of your choice. + +7. Go to the *Message Body* tab, and define the fields as shown below. @@ -338,7 +344,7 @@ Note that data written to the message header during a processing step, for examp
-7. Save or deploy the changes. +8. Save or deploy the changes. > ### Note: > - If you add a Content Modifier step without a header, body, and property, you cannot trace the element. diff --git a/docs/ci/Development/define-xml-to-json-converter-a60a282.md b/docs/ci/Development/define-xml-to-json-converter-a60a282.md index ce974d4a..9fe9f404 100644 --- a/docs/ci/Development/define-xml-to-json-converter-a60a282.md +++ b/docs/ci/Development/define-xml-to-json-converter-a60a282.md @@ -14,11 +14,11 @@ The XML to JSON converter enables you to transform messages in XML format to JSO - You are familiar with the conversion rules for XML to JSON conversion. - For more information see . + For more information see . - You are familiar with the limitations for XML to JSON conversion. - For more information see . + For more information see . - You are familiar with streaming for XML to JSON conversion. diff --git a/docs/ci/Development/generating-xsd-wsdl-for-function-modules-using-esr-process-integration-57a6b6e.md b/docs/ci/Development/generating-xsd-wsdl-for-function-modules-using-esr-process-integration-57a6b6e.md index 0c9d4efd..488b5bea 100644 --- a/docs/ci/Development/generating-xsd-wsdl-for-function-modules-using-esr-process-integration-57a6b6e.md +++ b/docs/ci/Development/generating-xsd-wsdl-for-function-modules-using-esr-process-integration-57a6b6e.md @@ -38,7 +38,7 @@ Generate an XSD/WSDL file for a function module using the Enterprise Services Re **Related Information** - + [RFC Receiver Adapter](rfc-receiver-adapter-5c76048.md "Connects an SAP Cloud Integration tenant to a remote receiver system using Remote Function Call (RFC).") diff --git a/docs/ci/Development/integration-content-d1679a8.md b/docs/ci/Development/integration-content-d1679a8.md index f80dc1a2..84cd36ac 100644 --- a/docs/ci/Development/integration-content-d1679a8.md +++ b/docs/ci/Development/integration-content-d1679a8.md @@ -390,7 +390,7 @@ MDI Delta Token Represents the delta token for the SAP Master Data Integration receiver adapter \(MDI receiver adapter\). -See: +See: diff --git a/docs/ci/Development/limitations-for-json-to-xml-conversion-3a02829.md b/docs/ci/Development/limitations-for-json-to-xml-conversion-3a02829.md index 2e838662..cc459872 100644 --- a/docs/ci/Development/limitations-for-json-to-xml-conversion-3a02829.md +++ b/docs/ci/Development/limitations-for-json-to-xml-conversion-3a02829.md @@ -58,5 +58,5 @@ See also: [3112970 - JSON-to-XML Converter Exception Caused by Invalid JSON Memb [Conversion Rules for JSON to XML Conversion](conversion-rules-for-json-to-xml-conversion-232a9cf.md "To ensure a successful conversion of you data, you should make yourself familiar with the conversion rules.") - + diff --git a/docs/ci/Development/limitations-for-xml-to-json-conversion-4bf5a05.md b/docs/ci/Development/limitations-for-xml-to-json-conversion-4bf5a05.md index b2d1c1ef..5b3858ff 100644 --- a/docs/ci/Development/limitations-for-xml-to-json-conversion-4bf5a05.md +++ b/docs/ci/Development/limitations-for-xml-to-json-conversion-4bf5a05.md @@ -27,9 +27,9 @@ The XML to JSON conversion has the following limitations: [Define XML to JSON Converter](define-xml-to-json-converter-a60a282.md "The XML to JSON converter enables you to transform messages in XML format to JSON format.") - + [How Streaming in the XML-to-JSON Converter Works](how-streaming-in-the-xml-to-json-converter-works-4e05044.md "During streaming the XML document is processed in parts or segments:") - + diff --git a/docs/ci/Development/manage-resources-of-an-integration-flow-b5968b2.md b/docs/ci/Development/manage-resources-of-an-integration-flow-b5968b2.md index af0237c1..4a244436 100644 --- a/docs/ci/Development/manage-resources-of-an-integration-flow-b5968b2.md +++ b/docs/ci/Development/manage-resources-of-an-integration-flow-b5968b2.md @@ -415,7 +415,7 @@ Upload individual files or an archive file that contains only XSL resources. ## Adding Local Resources -Under the *Resources* tab, choose *Local*. +Under the *References* tab, choose *Local*. A table in the resources view displays files grouped by categories and their filenames alphabetically sorted. Expanding each resource category shows the files within the category. Resource files with a link allow you to view or modify the content in a file-specific editor. You can modify the file content only when the integration content is in edit mode. @@ -473,7 +473,7 @@ See: [Importing Mapping Content from ES Repository](../IntegrationSettings/impor Apart from adding resources that are local your integration flow, you can also refer to reusable message mappings and script collections. You can refer to such artifacts from the package that you're in and other packages too. This way, when the reusable artifact is updated in the source, all referring integration flows are also automatically updated. -1. In the *References* tab, choose *Add References* and select a reusable artifact type. +1. In the *References* tab, choose *Global* \> *Add References* and select a reusable artifact type. 2. Select one or more integration packages. diff --git a/docs/ci/Development/mapping-extension-step-by-step-demo-example-2c3a543.md b/docs/ci/Development/mapping-extension-step-by-step-demo-example-2c3a543.md index 6bacd828..b04c3ae4 100644 --- a/docs/ci/Development/mapping-extension-step-by-step-demo-example-2c3a543.md +++ b/docs/ci/Development/mapping-extension-step-by-step-demo-example-2c3a543.md @@ -42,7 +42,7 @@ This section covers the following extension scenario with a post-exit. In this scenario, the standard integration flow passes a message to a post-exit integration flow \(which contains the custom mapping\). -In this demo scenario, the sender system is simulated by a SOAP client, which sends a SOAP message toCloud Integration. The original message has a simple structure \(only four elements\). The standard mapping is also kept simple and concatenates \(me.res\) two of the original fields +In this demo scenario, the sender system is simulated by a SOAP client, which sends a SOAP message to SAP Cloud Integration. The original message has a simple structure \(only four elements\). The standard mapping is also kept simple and concatenates \(me.res\) two of the original fields More information: [Standard Mapping](standard-mapping-56c3bf5.md) diff --git a/docs/ci/Development/send-the-http-request-and-process-the-integration-flow-f08cca6.md b/docs/ci/Development/send-the-http-request-and-process-the-integration-flow-f08cca6.md index fd77c559..e4d448d1 100644 --- a/docs/ci/Development/send-the-http-request-and-process-the-integration-flow-f08cca6.md +++ b/docs/ci/Development/send-the-http-request-and-process-the-integration-flow-f08cca6.md @@ -88,7 +88,7 @@ You can now send the POST request to the integration flow. **Related Information** - + - + diff --git a/docs/ci/Development/sender-initiated-scenario-with-https-sender-adapter-ccdb189.md b/docs/ci/Development/sender-initiated-scenario-with-https-sender-adapter-ccdb189.md index c75a8c06..7fcb97f9 100644 --- a/docs/ci/Development/sender-initiated-scenario-with-https-sender-adapter-ccdb189.md +++ b/docs/ci/Development/sender-initiated-scenario-with-https-sender-adapter-ccdb189.md @@ -53,11 +53,11 @@ When you have finished the integration flow design, you can send the message thr [Add the JSON to XML Converter](add-the-json-to-xml-converter-2c49c10.md "Add a JSON-to-XML converter to convert the HTTP request, which is in JavaScript Object Notation (JSON) format, to XML for further processing.") - + - + - + [Create the Mail Receiver Channel](create-the-mail-receiver-channel-a6966fd.md "Add a Mail receiver channel to enable the integration flow to send messages to an e-mail account.") diff --git a/docs/ci/Development/smoke-test-scenario-8c83fcf.md b/docs/ci/Development/smoke-test-scenario-8c83fcf.md index a7320272..261df9e6 100644 --- a/docs/ci/Development/smoke-test-scenario-8c83fcf.md +++ b/docs/ci/Development/smoke-test-scenario-8c83fcf.md @@ -35,7 +35,7 @@ You can then monitor message processing. **Related Information** - + [Create a Content Modifier to Define the Message Body](create-a-content-modifier-to-define-the-message-body-766db40.md "Add a Content Modifier step to create the message body.") diff --git a/docs/ci/Development/smoke-test-scenario-with-external-data-source-e4bef74.md b/docs/ci/Development/smoke-test-scenario-with-external-data-source-e4bef74.md index 1d0c0a06..64199889 100644 --- a/docs/ci/Development/smoke-test-scenario-with-external-data-source-e4bef74.md +++ b/docs/ci/Development/smoke-test-scenario-with-external-data-source-e4bef74.md @@ -47,13 +47,13 @@ You can then run the integration flow and monitor message processing as describe **Related Information** - + - + - + - + [Create the Script Step to Log the Payload](create-the-script-step-to-log-the-payload-613181e.md "Add a Script step to log the message payload.") diff --git a/docs/ci/Development/timer-initiated-scenario-with-a-mail-receiver-bfee17e.md b/docs/ci/Development/timer-initiated-scenario-with-a-mail-receiver-bfee17e.md index 5625673a..4271225e 100644 --- a/docs/ci/Development/timer-initiated-scenario-with-a-mail-receiver-bfee17e.md +++ b/docs/ci/Development/timer-initiated-scenario-with-a-mail-receiver-bfee17e.md @@ -55,13 +55,13 @@ This integration flow introduces you to a number of important aspects of integra [Create and Deploy a User Credentials Artifact for the E-Mail Account](create-and-deploy-a-user-credentials-artifact-for-the-e-mail-account-1c1fced.md "Deploy a User Credentials artifact that contains the user name and password for your receiver mail account.") - + - + - + - + [Create the Mail Receiver Channel](create-the-mail-receiver-channel-a6966fd.md "Add a Mail receiver channel to enable the integration flow to send messages to an e-mail account.") diff --git a/docs/ci/Development/working-with-integration-packages-45423ba.md b/docs/ci/Development/working-with-integration-packages-45423ba.md index efc25b76..61e16f12 100644 --- a/docs/ci/Development/working-with-integration-packages-45423ba.md +++ b/docs/ci/Development/working-with-integration-packages-45423ba.md @@ -5,7 +5,7 @@ **Related Information** - + [Working with Prepackaged Integration Content](working-with-prepackaged-integration-content-bd2ed3e.md "") diff --git a/docs/ci/InitialSetup/enabling-and-configuring-a-tenant-6807119.md b/docs/ci/InitialSetup/enabling-and-configuring-a-tenant-6807119.md index 7c4865d8..77d9b645 100644 --- a/docs/ci/InitialSetup/enabling-and-configuring-a-tenant-6807119.md +++ b/docs/ci/InitialSetup/enabling-and-configuring-a-tenant-6807119.md @@ -62,7 +62,7 @@ Once the tenant is activated, you need to assign the roles on the tenant before **Related Information** - + [Managing Users and Role Assignments, Neo Environment](../Operations/managing-users-and-role-assignments-neo-environment-1d470b0.md "You specify the members of the account and assign roles to them.") diff --git a/docs/ci/InitialSetup/security-faqs-58ff94f.md b/docs/ci/InitialSetup/security-faqs-58ff94f.md index 5045b9b7..26d9b164 100644 --- a/docs/ci/InitialSetup/security-faqs-58ff94f.md +++ b/docs/ci/InitialSetup/security-faqs-58ff94f.md @@ -162,7 +162,7 @@ More information: **Related Information** - + [Connecting a Customer System to Cloud Integration](../ConnectionSetup/connecting-a-customer-system-to-cloud-integration-7cfe913.md "You can set up the technical connection between a tenant and different kinds of remote systems (in many cases located in the customer landscape).") diff --git a/docs/ci/IntegrationAdvisor/code-value-mapping-eb6dad8.md b/docs/ci/IntegrationAdvisor/code-value-mapping-eb6dad8.md index ee998505..45085200 100644 --- a/docs/ci/IntegrationAdvisor/code-value-mapping-eb6dad8.md +++ b/docs/ci/IntegrationAdvisor/code-value-mapping-eb6dad8.md @@ -34,6 +34,40 @@ You can use the following options only if you have used a standard code list. + + +## N:1 Local Code Value Mapping + +The local code value mapping now supports N:1 mapping cardinality. You can map more than one source node with a target node for the local code value mapping. + +> ### Note: +> You cannot create a global code value mapping out of this N:1 local code value mapping. +> +> You cannot assign a global code value mapping to this mapping. + +1. Once the mapping is set, the *Code Value Mapping* tab appears with the following details. + +2. The *Default Value* field allows you to set a default value for the mapping in case no mapping values are matched for the target code value. Select the value help and set a default from the list. You can only set a default value from the rules other than the ones mentioned in the table below and you can also select only the target code values for the default value. +3. The table displays the source code values from left to right in the top-down order of the source MIG node.The target code values are displayed at the rightmost-end of the table. + + Let us take for example, you have mapped the source nodes `AddressTypeCode` and `CountryCode` with the target node `AddressType`. The *Code Value Mapping* tab would display a table with three columns - two for each source node and one for the target node. + +4. You can now start setting the code values using the value help button provided for each entry in the table. + + > ### Note: + > You need to ensure that there are no duplicate code value mappings. In such cases, the row entry will be marked as an error. + +5. Choose the Add :heavy_plus_sign: button provided above the table to add more code values. +6. The sort code value mapping button automatically reorders the code value mappings to ensure that more specific mappings are applied first thereby increasing the accuracy of mapping each source code value to its corresponding target code value. +7. If you had applied the *Proposal* service and then tried 1:1 code value mapping, the proposals are automatically applied to the target code values. In case of N:1 code value mapping, the proposals are not applied automatically. You need to choose the*Proposal* option provided under the *Code Value Mapping* tab to apply proposals on the code values. + + > ### Note: + > The *Proposal* option appears under the *Code Value Mapping* tab only if you have used the Proposal service on the entire MAG. + +8. Selecting the *Proposal* button for N:1 mapping displays the list of proposals. You can select the necessary proposals from the list and choose *Add*. + + + ## Deprecated Code Values diff --git a/docs/ci/IntegrationAdvisor/exporting-mig-mag-c8bba26.md b/docs/ci/IntegrationAdvisor/exporting-mig-mag-c8bba26.md index 6e2c1eb3..27768eea 100644 --- a/docs/ci/IntegrationAdvisor/exporting-mig-mag-c8bba26.md +++ b/docs/ci/IntegrationAdvisor/exporting-mig-mag-c8bba26.md @@ -29,3 +29,16 @@ You can now export a list of message implementation guidelines\(MIG\) or mapping 4. Use the filter option provided under each column header to search for a particular MIG/MAG. 5. Choose *Export*. This will download the files in the `.zip` format. + + + + +## Exporting a single MIG/MAG + +If you want to export only one MIG/MAG, follow the procedure below: + +1. Select and open your MIG/MAG. + +2. Choose and select *MAG Version \(ZIP\)*/*MIG Version \(ZIP\)* from the list. +3. This will download only that specific version of MIG/MAG into a `.zip` file. + diff --git a/docs/ci/IntegrationAdvisor/mapping-the-source-and-target-nodes-9ea58d6.md b/docs/ci/IntegrationAdvisor/mapping-the-source-and-target-nodes-9ea58d6.md index ca66e5d6..5cce19fd 100644 --- a/docs/ci/IntegrationAdvisor/mapping-the-source-and-target-nodes-9ea58d6.md +++ b/docs/ci/IntegrationAdvisor/mapping-the-source-and-target-nodes-9ea58d6.md @@ -567,14 +567,13 @@ If you want to search for a particular entry in the *Mapping List* tab, select t ## Deletion of Mapping Lines -You can delete both mapping lines and mapping entities that aren't required. Select the mapping line or entity, and press the [Delete\] key. +You can delete both mapping lines and mapping entities that aren't required. In *Edit* mode, select the mapping line or entity, and press the [Delete\] key. Alternatively, you can - - Right-click the mapping line or entity and choose *Delete* from the context menu. -- On the *Mapping List* tab, in the mapping pane, choose the *Delete* icon against the mapping line or entity in the *Source* column. - +- Delete multiple mapping entities by selecting the check box of the entries you want to delete under the *Mapping List* tab and selecting *Delete* button provided above the table. You can also delete an individual mapping line from a mapping entity. You can select the mapping entity and right-click the individual mapping line, and choose *Delete Line* from the context menu. diff --git a/docs/ci/IntegrationAdvisor/working-with-a-mapping-guideline-mag-0803ca6.md b/docs/ci/IntegrationAdvisor/working-with-a-mapping-guideline-mag-0803ca6.md index 53e6f4a0..0d4bd7ca 100644 --- a/docs/ci/IntegrationAdvisor/working-with-a-mapping-guideline-mag-0803ca6.md +++ b/docs/ci/IntegrationAdvisor/working-with-a-mapping-guideline-mag-0803ca6.md @@ -42,7 +42,9 @@ There could be scenarios where there are significant differences between the Mes 2. Choose Proposals: Select *Best Proposal* to automatically select all proposed mapping entities or select single proposed mapping entities by clicking on the checkboxes within the mapping list. - If you want to search for a particular value in the *Mapping List* tab, select the relevant column name and enter the search value in the filter field. This filter option is also available for *Code Value Mapping* tab. + If you want to search for all XSLT snippets and XPath expressions for a certain text pattern and want the list of mapping elements to be filtered by those elements that contain the search pattern, you can use the *Search* field provided above the *Mapping List* table. Use the search field to enter the function pattern and select :mag: . This will display the list of mapping elements pertaining to that function pattern. + + You can also search for a particular value in the *Mapping List* tab by selecting the relevant column name and entering the search value in the filter field. This filter option is also available for *Code Value Mapping* tab. You can add or manage additional information about each element in the *Properties* tab. You can also view these details by selecting the element. diff --git a/docs/ci/IntegrationSettings/importing-mapping-content-from-es-repository-e18fc05.md b/docs/ci/IntegrationSettings/importing-mapping-content-from-es-repository-e18fc05.md index 484a4958..af3fe5f0 100644 --- a/docs/ci/IntegrationSettings/importing-mapping-content-from-es-repository-e18fc05.md +++ b/docs/ci/IntegrationSettings/importing-mapping-content-from-es-repository-e18fc05.md @@ -10,15 +10,16 @@ ## Prerequisites -You've configured a connection to ES Repository under *Settings* \(:gear:\) tab. For more information, see [Configuring Connectivity to an SAP Process Orchestration System](configuring-connectivity-to-an-sap-process-orchestration-system-8c36fd2.md). +- You've configured a connection to ES Repository under *Settings* \(:gear:\) tab. For more information, see [Configuring Connectivity to an SAP Process Orchestration System](configuring-connectivity-to-an-sap-process-orchestration-system-8c36fd2.md). + +- You've opened the integration flow in which you want to add the integration content and you are editing it. -You've opened the integration flow in which you want to add the integration content and you are editing it. ## Context -After you've configured the connection to ES Repository, you can import content from it in the *Resources* tab of the integration flow editor. Currently, you can import: +After you've configured the connection to ES Repository, you can import content from it in the *References* tab of the integration flow editor. Currently, you can import: - Message mapping @@ -39,7 +40,7 @@ After you've configured the connection to ES Repository, you can import content > > - The import process fails if the message mapping contains: > -> - User Defined Functions with function libraries or imported archives +> - Imported archives > > - Parameters > @@ -54,21 +55,23 @@ Here's how you can do it: ## Procedure -1. Choose *Resources* \> *Local* tab in the integration flow settings. +1. Choose *References* \> *Local* tab in the integration flow properties sheet. + + If you don't see the *References* tab, click the empty space in the integration flow editor. You see the *References* tab at the bottom of the integration flow editor. - If you don't see the *Resources* tab, click the empty space in the integration flow editor. You see the *Resources* tab at the bottom of the integration flow editor. +2. Choose *Add* and select a supported resource. See the supported sources here: [Manage Resources of an Integration Flow](../Development/manage-resources-of-an-integration-flow-b5968b2.md). -2. Choose *Add* and select a supported resource. +3. Choose *ES Repository* as the source. -3. Choose *ES Repository* as the source. You see the details populated in *Name*, *Address*, and *Location ID* fields. Choose *Connect*. +4. Select a ES Repository from the *Name* list. Choose *Connect*. A connection is established to the ES Repository. A table with the list of available content is displayed. -4. Choose the resource that you want to import and choose *Select*. +5. Choose the resource that you want to import and choose *Select*. A summary of all the artifacts that are available for import is displayed. -5. Choose *Add*. +6. Choose *Add*. You see a confirmation about all the artifacts that are successfully imported. diff --git a/docs/ci/Operations/adding-members-to-an-account-eb6d612.md b/docs/ci/Operations/adding-members-to-an-account-eb6d612.md index 56ff78d0..0a06f992 100644 --- a/docs/ci/Operations/adding-members-to-an-account-eb6d612.md +++ b/docs/ci/Operations/adding-members-to-an-account-eb6d612.md @@ -43,7 +43,7 @@ Perform the following steps. [Persona](../SecurityNeo/persona-2937e5c.md "When you perform user management tasks using SAP BTP SAP BTP cockpit, you find a set of predefined roles that you can assign to users of the account. According to the main tasks associated with integration projects, these roles are associated to certain persona relevant for an integration project.") - + [Support Tasks](support-tasks-01f4d21.md "") diff --git a/docs/ci/Operations/defining-authorizations-for-integration-team-members-3ec7679.md b/docs/ci/Operations/defining-authorizations-for-integration-team-members-3ec7679.md index 61f61219..948830e0 100644 --- a/docs/ci/Operations/defining-authorizations-for-integration-team-members-3ec7679.md +++ b/docs/ci/Operations/defining-authorizations-for-integration-team-members-3ec7679.md @@ -55,5 +55,5 @@ Perform the following steps for all users for which to assign authorizations. [Persona](../SecurityNeo/persona-2937e5c.md "When you perform user management tasks using SAP BTP SAP BTP cockpit, you find a set of predefined roles that you can assign to users of the account. According to the main tasks associated with integration projects, these roles are associated to certain persona relevant for an integration project.") - + diff --git a/docs/ci/Operations/managing-message-queues-cdcce24.md b/docs/ci/Operations/managing-message-queues-cdcce24.md index 2493c482..5dd668d0 100644 --- a/docs/ci/Operations/managing-message-queues-cdcce24.md +++ b/docs/ci/Operations/managing-message-queues-cdcce24.md @@ -220,7 +220,7 @@ Sort the table entries according to the displayed sorting criteria. [JMS Adapter](../Development/jms-adapter-0993f2a.md "You configure the JMS adapter to enable asynchronous messaging using message queues.") - + - + diff --git a/docs/ci/Operations/message-status-733a57b.md b/docs/ci/Operations/message-status-733a57b.md index 2d7a41d0..6b4231c6 100644 --- a/docs/ci/Operations/message-status-733a57b.md +++ b/docs/ci/Operations/message-status-733a57b.md @@ -146,7 +146,7 @@ For example, assume that an integration flow is initiated by a Timer event \(sch -ABANDONDED +ABANDONED @@ -156,7 +156,7 @@ ABANDONDED Message processing was interrupted or log wasn't updated for an uncommonly long time. The status can change in case processing is resumed. > ### Note: -> When the message processing is interrupted because of a re- or undeployment of an integration flow, or a controlled worker node shutdown, the MPL is immediately set to ABANDONDED. This status isn’t final and the processing can be resumed if retries are configured. If there are hard worker node crashes, the status is changed to ABANDONDED by an asynchronous system job, after some time of inactivity +> When the message processing is interrupted because of a re- or undeployment of an integration flow, or a controlled worker node shutdown, the MPL is immediately set to ABANDONED. This status isn’t final and the processing can be resumed if retries are configured. If there are hard worker node crashes, the status is changed to ABANDONED by an asynchronous system job, after some time of inactivity diff --git a/docs/ci/Operations/monitoring-audit-log-neo-environment-2d6031f.md b/docs/ci/Operations/monitoring-audit-log-neo-environment-2d6031f.md index 317b8620..20a3127a 100644 --- a/docs/ci/Operations/monitoring-audit-log-neo-environment-2d6031f.md +++ b/docs/ci/Operations/monitoring-audit-log-neo-environment-2d6031f.md @@ -160,5 +160,5 @@ You can also sort the audit log list by *Time*, *Action*, *Object Type* or *Obje **Related Information** - + diff --git a/docs/ci/Operations/operating-and-monitoring-cloud-integration-c401afc.md b/docs/ci/Operations/operating-and-monitoring-cloud-integration-c401afc.md index 771c1498..1d2f5aae 100644 --- a/docs/ci/Operations/operating-and-monitoring-cloud-integration-c401afc.md +++ b/docs/ci/Operations/operating-and-monitoring-cloud-integration-c401afc.md @@ -13,7 +13,7 @@ There are the following tasks: [Understanding the Basic Concepts](understanding-the-basic-concepts-bf8316e.md "This section provides an overview of the concepts and terms.") - + [Monitor](monitor-05446d0.md "Check the status of messages and integration content artifacts for a tenant cluster.") diff --git a/docs/ci/Operations/security-artifact-renewal-for-ws-security-169b0b5.md b/docs/ci/Operations/security-artifact-renewal-for-ws-security-169b0b5.md index 7cdf2f30..79c0f147 100644 --- a/docs/ci/Operations/security-artifact-renewal-for-ws-security-169b0b5.md +++ b/docs/ci/Operations/security-artifact-renewal-for-ws-security-169b0b5.md @@ -208,7 +208,7 @@ Tenant decrypts outbound response message. **Related Information** - + [WS-Security Configuration for the Sender SOAP 1.x Adapter](../Development/ws-security-configuration-for-the-sender-soap-1-x-adapter-e53bb5c.md "") diff --git a/docs/ci/SecurityCF/specific-data-assets-0e4e511.md b/docs/ci/SecurityCF/specific-data-assets-0e4e511.md index d7bd2936..10bf04dc 100644 --- a/docs/ci/SecurityCF/specific-data-assets-0e4e511.md +++ b/docs/ci/SecurityCF/specific-data-assets-0e4e511.md @@ -388,11 +388,11 @@ Lock entries that are created \(in the in-progress repository\) to avoid the sam [Message Processing Log](../Operations/message-processing-log-b32f8cd.md "The message processing log displays structured information of a message.") - + [Define Data Store Operations](../Development/define-data-store-operations-79f63a4.md "You can use the data store to temporarily store messages.") - + [Managing Security Material](../Operations/managing-security-material-b8ccb53.md "The Manage Security Material area provides an overview of security-related artifacts.") diff --git a/docs/ci/SecurityNeo/specific-data-assets-f922344.md b/docs/ci/SecurityNeo/specific-data-assets-f922344.md index f571cca5..df045ca2 100644 --- a/docs/ci/SecurityNeo/specific-data-assets-f922344.md +++ b/docs/ci/SecurityNeo/specific-data-assets-f922344.md @@ -542,13 +542,13 @@ Limited retention times make sure that data is stored in the system only for a l **Related Information** - + - + [Define Data Store Operations](../Development/define-data-store-operations-79f63a4.md "You can use the data store to temporarily store messages.") - + [Managing Security Material](../Operations/managing-security-material-b8ccb53.md "The Manage Security Material area provides an overview of security-related artifacts.") diff --git a/docs/ci/WhatIsCloudIntegration/elements-of-a-cloud-based-integration-scenario-762289a.md b/docs/ci/WhatIsCloudIntegration/elements-of-a-cloud-based-integration-scenario-762289a.md index b6efbdea..259c8c06 100644 --- a/docs/ci/WhatIsCloudIntegration/elements-of-a-cloud-based-integration-scenario-762289a.md +++ b/docs/ci/WhatIsCloudIntegration/elements-of-a-cloud-based-integration-scenario-762289a.md @@ -34,9 +34,9 @@ The following figure provides a simplified and generalized representation of an **Related Information** - + - + [Runtime in Detail](../Operations/runtime-in-detail-bdbc3f0.md "For different customers, separate resources (in terms of: memory, CPU, file system) of the cloud-based integration platform are allocated – although all customers share the same hardware. This concept is also referred to as tenant isolation.") diff --git a/docs/ci/WhatIsCloudIntegration/partner-directory-e7fa1e2.md b/docs/ci/WhatIsCloudIntegration/partner-directory-e7fa1e2.md index 911af374..5e4b3b8e 100644 --- a/docs/ci/WhatIsCloudIntegration/partner-directory-e7fa1e2.md +++ b/docs/ci/WhatIsCloudIntegration/partner-directory-e7fa1e2.md @@ -160,7 +160,7 @@ For detailed step-by-step descriptions how to use the Partner Directory, see the **Related Information** - + [Partner Authorization \(Inbound\)](../Development/partner-authorization-inbound-c0c9950.md "For inbound calls (when a partner sends a message to the integration platform), a partner authorization check evaluates whether the logged-in user has permission to execute messages with a particular sender partner ID.") diff --git a/docs/ci/WhatIsCloudIntegration/what-is-sap-cloud-integration-e12c09c.md b/docs/ci/WhatIsCloudIntegration/what-is-sap-cloud-integration-e12c09c.md index 9229204d..08006956 100644 --- a/docs/ci/WhatIsCloudIntegration/what-is-sap-cloud-integration-e12c09c.md +++ b/docs/ci/WhatIsCloudIntegration/what-is-sap-cloud-integration-e12c09c.md @@ -9,6 +9,24 @@ SAP Cloud Integration helps you to connect cloud and on-premise applications wit > ### Note: > SAP Integration Suite combines Cloud Integration, API Management, Integration Advisor, Open Connectors, and other integration capabilities into a cohesive and simplified toolkit for enterprise integration. To provide a comprehensive integration experience, these services are not available separately, but only as part of the Integration Suite service plan. To learn more on different service plans, see the [Integration Suite](https://discovery-center.cloud.sap/#/serviceCatalog/f810c887-8d25-4942-9849-354837951066) service catalog. +> ### Tip: +> The English version of this guide is open for contributions and feedback using GitHub. This allows you to get in contact with responsible authors of SAP Help Portal pages and the development teams for SAP Cloud Integration to discuss documentation-related issues. To contribute to this guide, or to provide feedback, choose the corresponding option on SAP Help Portal: +> +> - *Feedback* \> *Create issue*: Provide feedback about a documentation page. This option opens an issue on GitHub. +> +> - *Feedback* \> *Edit page*: Contribute to a documentation page. This option opens a pull request on GitHub. +> +> +> You need a GitHub account to use these options. +> +> More information: +> +> - [Contribution Guidelines](https://help.sap.com/docs/open-documentation-initiative/contribution-guidelines/readme.html) +> +> - [Introduction Video: Open Documentation Initiative](https://www.youtube.com/watch?v=WJ0oarMlVW4) +> +> - [Blog Post: Introducing the Open Documentation Initiative](https://blogs.sap.com/2021/05/20/introducing-the-open-documentation-initiative/) + ## Environment diff --git a/docs/ci/WhatsNewInCloudIntegration/2014-sap-cloud-integration-archive-59a5f82.md b/docs/ci/WhatsNewInCloudIntegration/2014-sap-cloud-integration-archive-59a5f82.md index c26b1899..d73f2a74 100644 --- a/docs/ci/WhatsNewInCloudIntegration/2014-sap-cloud-integration-archive-59a5f82.md +++ b/docs/ci/WhatsNewInCloudIntegration/2014-sap-cloud-integration-archive-59a5f82.md @@ -169,7 +169,7 @@ You can use the *Upsert* operation to perform both *Insert* and *Update* operati - + @@ -199,7 +199,7 @@ The enhanced message from content enricher contains all the content from the loo - + @@ -436,7 +436,7 @@ Using the XML-to-JSON Converter you can now transform messages in XML format to - + @@ -736,7 +736,7 @@ You use Write Variables to define variables, which you access across message flo - + @@ -770,7 +770,7 @@ The XML Digital Signer has been enhanced by the following attributes: - + @@ -830,7 +830,7 @@ The Aggregator step allows you to combine multiple incoming messages into a sing - + @@ -969,7 +969,7 @@ You can use Data Store to store messages. Data Store supports four types of oper - + @@ -1378,7 +1378,7 @@ You can use this task if you want to catch any thrown exception in the integrati - + @@ -1408,7 +1408,7 @@ You can set headers before calling the HTTP adapter in case you want to dynamica - + @@ -1438,9 +1438,9 @@ Detached XML Signatures are now supported. - + - + @@ -1808,7 +1808,7 @@ You can configure username token \(password digest, plain text\) authentication - + @@ -1838,7 +1838,7 @@ Use this method to update or create the enclosed data on the receiver side. - + @@ -2058,7 +2058,7 @@ The SOAP 1.x Adapter allows the configuration of WS-Security options. - + @@ -2088,7 +2088,7 @@ You use content modifier if you want to modify the content of the incoming messa - + @@ -2120,7 +2120,7 @@ This feature has now been made available externally. - + @@ -2150,7 +2150,7 @@ You use this task to assign javascript or groovy script for message processing. - + @@ -2180,7 +2180,7 @@ You use content modifier if you want to modify the content of the incoming messa - + diff --git a/docs/ci/WhatsNewInCloudIntegration/2015-sap-cloud-integration-archive-723dddb.md b/docs/ci/WhatsNewInCloudIntegration/2015-sap-cloud-integration-archive-723dddb.md index 6445b166..a84210d5 100644 --- a/docs/ci/WhatsNewInCloudIntegration/2015-sap-cloud-integration-archive-723dddb.md +++ b/docs/ci/WhatsNewInCloudIntegration/2015-sap-cloud-integration-archive-723dddb.md @@ -475,7 +475,7 @@ You can use the Facebook receiver adapter to extract information from Facebook b - + @@ -505,9 +505,9 @@ You can use the encoding/decoding scheme *MIME multipart encode/decode* to trans - + - + @@ -537,7 +537,7 @@ You can add an enveloped transform to a detached signature for XML Digital Signa - + @@ -780,7 +780,7 @@ You can use the delete method in HTTP Adapter - + @@ -1088,7 +1088,7 @@ You can use the Twitter receiver adapter to extract information from the Twitter - + @@ -1144,7 +1144,7 @@ You can set the message-id manually - + @@ -1344,7 +1344,7 @@ You can externalize different parameters in WS-Security configuration in SOAP Ad - + @@ -1594,7 +1594,7 @@ Enhanced - + @@ -1624,7 +1624,7 @@ Product profile is a collection of capabilities such as success factor adapter, - + @@ -1682,7 +1682,7 @@ You can now specify multiple key value pairs in SFAPI paramters while configurin - + @@ -1974,7 +1974,7 @@ You can dynamically configure the Address and Query field of the HTTP adapter. - + @@ -2004,7 +2004,7 @@ You can set Body MIME type and Body Encoding - + @@ -2034,7 +2034,7 @@ You can add all attachments contained in the message exchange to the e-mail - + @@ -2064,7 +2064,7 @@ You can create the JSON message without the root element tag - + @@ -2445,7 +2445,7 @@ You can now validate the incoming message paylod against the configured XML sche - + @@ -2541,7 +2541,7 @@ You can now dynamically configure the mail adress and the attachment names in Ma - + @@ -2627,7 +2627,7 @@ You can externalize the timer parameters. Refer to documentation for handling ol - + @@ -3140,7 +3140,7 @@ There are the following additional Java interfaces for the message processing lo - + @@ -3170,7 +3170,7 @@ You configure sender and receiver channels of an integration flow with the Ariba - + @@ -3200,7 +3200,7 @@ You can use the IDoc adapter to connect to on-premise systems via SAP Cloud Conn - + @@ -3230,7 +3230,7 @@ You can specify the namespace in Xpath if the incoming XML contains namespace. - + @@ -3260,7 +3260,7 @@ You can specify the key and value using header or property variables in the para - + @@ -3290,7 +3290,7 @@ You have the option of specifying *UTF-8* as the character encoding format for e - + @@ -3320,7 +3320,7 @@ You can create your own custom functions by using groovy scripts and use them as - + @@ -3350,7 +3350,7 @@ You can use the SAP Cloud Connector with HTTP adapter receiver channels to conne - + @@ -3610,7 +3610,7 @@ When defining the error handling strategy for SOAP messages, you can now define - + @@ -3640,7 +3640,7 @@ You can define custom query options other than the options available as a part o - + @@ -3670,11 +3670,11 @@ You can use the SAP Cloud Connector with SOAP and OData adapter receiver channel -- +- -- +- -- +- - [SAP Cloud Connector](https://help.hana.ondemand.com/help/e6c7616abb5710148cfcf3e75d96d596.html) @@ -3707,7 +3707,7 @@ You can use the OData adapter and SuccessFactors OData adapter with content enri - + @@ -4009,7 +4009,7 @@ You can configure the mail adapter on the receiver to send encrypted e-mails/att - + @@ -4039,7 +4039,7 @@ You can find the polling parameters under the new Scheduler tab - + @@ -4286,7 +4286,7 @@ You can now configure a receiver mail adapter to send out messages by e-mail. - + @@ -4316,7 +4316,7 @@ The XML-to-JSON converter supports streaming. - + @@ -4348,7 +4348,7 @@ A new message status *ESCALATED* has been introduced for the message monitoring. - + @@ -4378,7 +4378,7 @@ You can specify additional SFAPI parameters for SuccessFactors SOAP adapter when - + @@ -4643,7 +4643,7 @@ If the file contains any backward path traversals, this can lead to a potential - + @@ -4673,7 +4673,7 @@ You can now select the required layout type. Options are *strict*or *lax*. - + @@ -4703,7 +4703,7 @@ The documentation of this feature has been improved. - + @@ -4733,7 +4733,7 @@ You can use *Gather* after *Splitter* while modeling an integration flow. - + diff --git a/docs/ci/WhatsNewInCloudIntegration/2016-sap-cloud-integration-archive-2f5d4f1.md b/docs/ci/WhatsNewInCloudIntegration/2016-sap-cloud-integration-archive-2f5d4f1.md index 7c68d0a5..67fcd146 100644 --- a/docs/ci/WhatsNewInCloudIntegration/2016-sap-cloud-integration-archive-2f5d4f1.md +++ b/docs/ci/WhatsNewInCloudIntegration/2016-sap-cloud-integration-archive-2f5d4f1.md @@ -115,7 +115,7 @@ For the following adapter types, the authorization option has been enhanced to a [HTTPS Sender Adapter](../Development/https-sender-adapter-0ae4a78.md) - + @@ -263,7 +263,7 @@ You can change the context of a field in the source message of the mapping defin - + @@ -364,9 +364,9 @@ For the following adapter types, the authorization option has been enhanced to a - + - + @@ -396,7 +396,7 @@ You can now dynamically provide the Data Store Name for the transient data store - + @@ -426,7 +426,7 @@ Post message processing, the trace data is deleted after 60 minutes. - + @@ -456,7 +456,7 @@ You can now use the SuccessFactors OData V4 adapter to perform *Update* operatio - + @@ -486,7 +486,7 @@ You can now define \(on integration process and local integration process level\ - + @@ -856,9 +856,9 @@ Configuration of inbound authorization for SOAP-based adapters \(SOAP 1.x, SAP R [SOAP \(SAP RM\) Adapter](../Development/soap-sap-rm-adapter-6bd724f.md) - + - + [Assign Sender and Receiver Components](../Development/assign-sender-and-receiver-components-f0eb056.md) @@ -1082,13 +1082,13 @@ Configuration of inbound authorization for SOAP-based adapters \(SOAP 1.x, SAP R - + - + - + - + @@ -1174,7 +1174,7 @@ You can now find an example how to use the query string in the HTTP Receiver Ada - + @@ -1204,7 +1204,7 @@ This fix ensures that integration flows with *Run Once* setting in *Timer*/*Sche - + @@ -1234,7 +1234,7 @@ You can now pass filter conditions via header or properties while performing asy - + @@ -1300,7 +1300,7 @@ The server certificate chain now also contains the SAN \(SubjectsAlternativeName - + @@ -1613,7 +1613,7 @@ You can now configure a proxy server to AS2 receiver communication channel. - + @@ -1709,7 +1709,7 @@ You can now add, set, get, remove headers to/from an attachment and add, set att - + @@ -1775,7 +1775,7 @@ Integration flow developers and/or tenant admin personas can now enable tracing - + @@ -1805,7 +1805,7 @@ If you configure the *Timer* or *Scheduler* with *Run Once* setting, message is - + @@ -1946,9 +1946,9 @@ The OData API has been extended by the following entities: - + - + @@ -2320,7 +2320,7 @@ You can now select product profiles while creating integration project for an in - + @@ -2350,7 +2350,7 @@ You can now select mapping source from partner directory and also set header and - + @@ -2387,7 +2387,7 @@ You can now use the mail sender adapter for the following tasks: - + @@ -2761,7 +2761,7 @@ You can now not just create but also delete headers and properties. - + @@ -2832,9 +2832,9 @@ Outbound connectivity test for SSL and SSH connections has been enhanced in the - + - + @@ -3014,7 +3014,7 @@ In a Content Modifier step, you can set the property `SAP_CorrelateMPLs` to swit - + @@ -3104,7 +3104,7 @@ You can now use the Content Modifier to reset the header SAP\_Receiver. - + @@ -3200,7 +3200,7 @@ You can now select None as authentication method. - + @@ -3268,7 +3268,7 @@ With this release, OData sender adapter is not available for editing in the inte [Editing an Integration Flow](../Development/editing-an-integration-flow-ccd062a.md) - + @@ -3592,7 +3592,7 @@ You can now access and use integration content from partners in the public catal - + @@ -3718,7 +3718,7 @@ You can use the*Use Temporary File* function to write the data to a temporary fi - + @@ -3748,7 +3748,7 @@ When *Add Multipart Header Inline* is selected and the inbound message is, other - + @@ -3778,7 +3778,7 @@ You can use the new Read Lock Strategy *Done File Expected*to signal that the fi - + @@ -3808,7 +3808,7 @@ You can now use Create\(POST\) operation with SuccessFactors adapter with OData - + @@ -3838,7 +3838,7 @@ You can now configure timeout or the maximum time the adapter waits for a respon - + @@ -4112,7 +4112,7 @@ The maximum number of iterations for the looping process call has been increased - + @@ -4142,7 +4142,7 @@ Certain Post Processing parameters are now externalizable. - + @@ -4172,7 +4172,7 @@ You can now configure a temporary file name for the *Override* option of the SFT - + @@ -4202,7 +4202,7 @@ You cannot download configure-only content any more. - + @@ -4232,7 +4232,7 @@ You can externalize the*Allow Chunking* parameter. - + @@ -4262,7 +4262,7 @@ The AS2 adapter will no longer generate an additional message processing log \(M - + @@ -4643,7 +4643,7 @@ The Integration Designer and the Integration Operations feature now run on Eclip - + @@ -4673,7 +4673,7 @@ You can dynamically configure the *Credential Name*property \(when basic authent - + @@ -4738,9 +4738,9 @@ The SFTP adapter has been enhanced by the following new capabilities: - + - + @@ -4770,7 +4770,7 @@ Enhanced - + @@ -4836,7 +4836,7 @@ The Integration Designer and the Integration Operations feature now run on Eclip - + @@ -4866,7 +4866,7 @@ The *CorrelationId* was added that allows you to identify correlated messages. - + @@ -4980,7 +4980,7 @@ You can now assign an OData adapter to the sender channel in an integration proj - + @@ -5196,7 +5196,7 @@ You can now assign an OData adapter to the sender channel in an integration proj - + @@ -5226,7 +5226,7 @@ You can now access SuccessFactors OData V4 service using the SuccessFactors adap - + @@ -5570,7 +5570,7 @@ You can find a list of parameters that can be externalized. - + @@ -5636,7 +5636,7 @@ A new property *Profile* is displayed for nodes in the Properties view. - + @@ -5874,7 +5874,7 @@ You can add an additional header \(`SAP_MessageType`\) to a message using the Co - + diff --git a/docs/ci/WhatsNewInCloudIntegration/2017-sap-cloud-integration-archive-f3b13e4.md b/docs/ci/WhatsNewInCloudIntegration/2017-sap-cloud-integration-archive-f3b13e4.md index 565912b0..c95e0048 100644 --- a/docs/ci/WhatsNewInCloudIntegration/2017-sap-cloud-integration-archive-f3b13e4.md +++ b/docs/ci/WhatsNewInCloudIntegration/2017-sap-cloud-integration-archive-f3b13e4.md @@ -69,7 +69,7 @@ For more information, see: - [RFC Receiver Adapter](../Development/rfc-receiver-adapter-5c76048.md) -- +- @@ -240,7 +240,7 @@ For more information, see: [JMS Adapter](../Development/jms-adapter-0993f2a.md) - + @@ -425,7 +425,7 @@ For more information, see: - [RFC Receiver Adapter](../Development/rfc-receiver-adapter-5c76048.md) -- +- @@ -517,9 +517,9 @@ The Scheduler of SFTP and Mail sender adapter has been changed so that the optio For more information, see: - + - + [Mail Adapter](../Development/mail-adapter-f1145cc.md) @@ -551,9 +551,9 @@ In the WS Security settings, you can now specify a signature algorithm to be app For more information, see: - + - + @@ -687,7 +687,7 @@ RFC receiver adapter version 1.2.0 and higher supports: For more information, see: - + [RFC Receiver Adapter](../Development/rfc-receiver-adapter-5c76048.md) @@ -939,7 +939,7 @@ More information: You can now use content assist feature for groovy script which means that you can view list of existing methods of message class, once you start typing initial letters of the required method. You can add content assist jar file in integration project to use this feature. -For more information, see . +For more information, see . @@ -967,9 +967,9 @@ This feature is available in the Web UI and in Eclipse. For more information, see \(for the Web UI\): - + - + [SOAP \(SAP RM\) Adapter](../Development/soap-sap-rm-adapter-6bd724f.md) @@ -1025,7 +1025,7 @@ Cloud Connector Proxy in Mail Sender Adapter is supported. For more information, see -- +- - [Mail Adapter](../Development/mail-adapter-f1145cc.md) @@ -1055,7 +1055,7 @@ This feature is available in the Web UI and in Eclipse. For more information, see - + [Define a Send Step](../Development/define-a-send-step-9b83f10.md) @@ -1081,9 +1081,9 @@ For more information, see The **Dead-letter** queue option has been introduced in AS2 adapter. This option enables you to place those messages that cannot be processed after two retries. -- For more information, see . +- For more information, see . -- For more information, see . +- For more information, see . @@ -1192,7 +1192,7 @@ For more information, see You can now disable a field in the target structure in a mapping definition resource. This helps you in testing or simulating the mapping without mapping the mandatory fields. -For more information, see . +For more information, see . @@ -1319,7 +1319,7 @@ RFC is the standard interface used for integrating On-premise ABAP systems to th For more information, see -- +- - [RFC Receiver Adapter](../Development/rfc-receiver-adapter-5c76048.md) @@ -1396,7 +1396,7 @@ Cloud Connector Proxy in Mail Receiver Adapter is supported. You can now use the For more information, see -- +- - [Mail Adapter](../Development/mail-adapter-f1145cc.md) @@ -1422,7 +1422,7 @@ Enhancement You can now configure the script in the custom function to return multiple string values. -For more information, see . +For more information, see . @@ -1450,7 +1450,7 @@ You can now place messages in the dead-letter queue if it cannot be processed af For more information, see -- +- - [JMS Adapter](../Development/jms-adapter-0993f2a.md) @@ -1479,7 +1479,7 @@ You can now configure HTTP Session Handling in the Runtime Configuration. For more information, see -- +- - [Specify the Runtime Configuration](../Development/specify-the-runtime-configuration-0c1c96e.md) @@ -1554,7 +1554,7 @@ More information: [Downloading Single Keystore Entries](../Operations/downloadin Authentication via principal propagation is now available in the OData adapter. -For more information, see . +For more information, see . @@ -1776,7 +1776,7 @@ For more information, see: The OData API was enhanced to support keystore management activities by the tenant administrator. -For more information, see +For more information, see @@ -1800,7 +1800,7 @@ For more information, see +For more information, see @@ -1848,7 +1848,7 @@ New JMS Adapter and Message Queue Monitor is available for Cloud Integration Customer only if you have *Enterprise Edition* license. -For more information, see +For more information, see @@ -1896,7 +1896,7 @@ New Parameter *CRAM-MD5* in Sender/Receiver Mail Adapter was renamed to *Encrypted User/Password* -For more information, see +For more information, see @@ -2039,7 +2039,7 @@ For methods GET, DELETE, and HEAD you can now send the body of a message with th More information: -- +- - [HTTP Receiver Adapter](../Development/http-receiver-adapter-2da452e.md) @@ -2103,7 +2103,7 @@ More information: - [Define EDI Splitter](../Development/define-edi-splitter-584a3be.md) \(Web UI\) -- \(Eclipse\) +- \(Eclipse\) @@ -2129,7 +2129,7 @@ The SMTP Outbound Connection Test has been enhanced in the Eclipse tooling of Cl You can now download certificates, check for mail addresses and validate the server certificate. -More information: +More information: @@ -2155,7 +2155,7 @@ The following feature is available in the Eclipse tooling of Cloud Integration. The *Data Store* viewer now also downloads headers. -More information: +More information: @@ -2316,9 +2316,9 @@ The OData API allows you now to access the HTTP access log files \(about authent More information: - + - + @@ -2346,9 +2346,9 @@ In the SAP SOAP 1.x Sender Adapter, you can now configure the Message Exchange P More information: -- +- -- +- @@ -2493,7 +2493,7 @@ The following feature is available in Eclipse and in the Web UI of Cloud Integra In the SAP SOAP 1.x Receiver Adapter, you can now clean up the adapter-specific headers after the receiver call. -More information: +More information: @@ -2523,16 +2523,16 @@ You define the Location ID in the destination configuration on the cloud side. More information: -- +- -- +- -- +- -- +- @@ -2565,7 +2565,7 @@ The provider invokes service synchronously and the processing errors are returne More information: -- +- - [SOAP \(SAP RM\) Adapter](../Development/soap-sap-rm-adapter-6bd724f.md) @@ -2596,9 +2596,9 @@ For the SOAP \(SOAP 1.x\) receiver adapter *Principal Propagation* is now availa More information: -- +- -- +- @@ -2651,7 +2651,7 @@ More information:[Define JSON to XML Converter](../Development/define-json-to-xm In the mapping definition resource editor of Cloud Integration WebUI, you can map two selected fields and all the fields with identical names in their corresponding sub-tree by choosing ![](images/map_all_4bf8289.png). You can delete all the definitions by choosing ![](images/clear_all_8bde6f9.png). -For more information, see . +For more information, see . diff --git a/docs/ci/WhatsNewInCloudIntegration/2018-sap-cloud-integration-archive-5a4ff04.md b/docs/ci/WhatsNewInCloudIntegration/2018-sap-cloud-integration-archive-5a4ff04.md index a77ed57d..3980091e 100644 --- a/docs/ci/WhatsNewInCloudIntegration/2018-sap-cloud-integration-archive-5a4ff04.md +++ b/docs/ci/WhatsNewInCloudIntegration/2018-sap-cloud-integration-archive-5a4ff04.md @@ -820,7 +820,7 @@ More information: [Configure the OData V2 Receiver Adapter](../Development/confi You can call the remote API for copying an integration package from *Discover* section to *Design* section. -More information: . +More information: . @@ -1054,7 +1054,7 @@ Enhanced You can not only update but also call the remote API to create an integration flow. -More information: +More information: @@ -1237,9 +1237,9 @@ You can also create and update a resource with content in zip folder. In this ca More information: - + - + @@ -1480,9 +1480,9 @@ More information: [Updating a Certificate](../Operations/updating-a-certificate-1fa04fa.md) \(Web UI\) - \(OData API\) + \(OData API\) - \(OData API\) + \(OData API\) @@ -1506,7 +1506,7 @@ New You can call the remote API to download integration artifact. -More information: . +More information: . @@ -1532,17 +1532,17 @@ You can call the remote API for reading, creating, updating, deleting and downlo More information: - + - + - + - + - + - + @@ -1566,7 +1566,7 @@ New You can call the remote API to delete integration artifact. -More information: . +More information: . @@ -2040,7 +2040,7 @@ New You can call the remote API to create integration flow. - + @@ -2184,11 +2184,11 @@ You can call the remote API for reading an integration artifact which will retur More information: - + - + - + @@ -2214,7 +2214,7 @@ This feature is available for Web. Now tenant administrators can disable a tenant in Cloud Integration service. -More information: . +More information: . @@ -2467,11 +2467,11 @@ In case you have as *Authorization* chosen the option *User Role*, the value hel More information: - + [SOAP \(SAP RM\) Adapter](../Development/soap-sap-rm-adapter-6bd724f.md) - + @@ -3279,7 +3279,7 @@ More information: - [SOAP \(SAP RM\) Adapter](../Development/soap-sap-rm-adapter-6bd724f.md) -- +- - [HTTP Receiver Adapter](../Development/http-receiver-adapter-2da452e.md) @@ -3421,7 +3421,7 @@ This feature is available in Web application. SAP BTP now offers Consumption-based model for consuming services in Cloud Integration. -For more information, see . +For more information, see . diff --git a/docs/ci/WhatsNewInCloudIntegration/2022-what-s-new-for-sap-cloud-integration-archive-eca4d78.md b/docs/ci/WhatsNewInCloudIntegration/2022-what-s-new-for-sap-cloud-integration-archive-eca4d78.md index e22f4e4f..d792325f 100644 --- a/docs/ci/WhatsNewInCloudIntegration/2022-what-s-new-for-sap-cloud-integration-archive-eca4d78.md +++ b/docs/ci/WhatsNewInCloudIntegration/2022-what-s-new-for-sap-cloud-integration-archive-eca4d78.md @@ -5753,7 +5753,7 @@ Self-Service to Delay Software Update -Tenant administrators can now configure their tenants to delay the monthly updates from SAP. See: . +Tenant administrators can now configure their tenants to delay the monthly updates from SAP. See: . diff --git a/docs/ci/WhatsNewInCloudIntegration/patch-releases-for-cloud-integration-023a472.md b/docs/ci/WhatsNewInCloudIntegration/patch-releases-for-cloud-integration-023a472.md index 44945460..5b7f55ee 100644 --- a/docs/ci/WhatsNewInCloudIntegration/patch-releases-for-cloud-integration-023a472.md +++ b/docs/ci/WhatsNewInCloudIntegration/patch-releases-for-cloud-integration-023a472.md @@ -91,6 +91,41 @@ The following patch release information covers the most recent changes made to t + + +## October 2023 + +**Software Increment: 2308** + + + + + + + + +
+ +Technical Component + + + + + +Software Version + + + + + +Description + + + +
+ + + ## September 2023 diff --git a/docs/ci/WhatsNewInCloudIntegration/sap-cloud-integration-72ef31d.md b/docs/ci/WhatsNewInCloudIntegration/sap-cloud-integration-72ef31d.md index 4fe8d81f..e93dd810 100644 --- a/docs/ci/WhatsNewInCloudIntegration/sap-cloud-integration-72ef31d.md +++ b/docs/ci/WhatsNewInCloudIntegration/sap-cloud-integration-72ef31d.md @@ -117,6 +117,807 @@ Software Version Update + + + +- SAP Cloud Integration: 6.44.\* +- SAP Integration Advisor: 1.78.\* +- Increment: 2308 + + + + + + + +Info only + + + + + + +General Availability + + + + + + +Changed + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Cloud Integration + + + + + + +- Neo + + + + + + +Software Version Update + + + + + + +- SAP Cloud Integration: 5.52.\* +- SAP Integration Advisor: 1.78.\* +- Adapter Development Kit for SAP Cloud Integration: 2.54.\* + +- Increment: 2308 + + + + + + + +Info only + + + + + + +General Availability + + + + + + +Changed + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Cloud Integration + + + + + + +- Cloud Foundry + + + + + + +Adjust the Validity Time of Access Token during Instance Creation + + + + + + +You can now manually adjust the validity time of your access token during the creation of your service instance. + +See: [Creating Service Instance and Service Key for Inbound Authentication](../ConnectionSetup/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md) + + + + + + +Info only + + + + + + +General Availability + + + + + + +New + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Cloud Integration + + + + + + +- Cloud Foundry + + + + + + +Deactivate Pin Certificates Option during Service Instance Creation + + + + + + +You can now manually deactivate the pin certificate functionality to be able to use renewed certificates without additional configuration. + +See: [Creating Service Instance and Service Key for Inbound Authentication](../ConnectionSetup/creating-service-instance-and-service-key-for-inbound-authentication-19af5e2.md) + + + + + + +Info only + + + + + + +General Availability + + + + + + +New + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Cloud Integration + + + + + + +- Cloud Foundry +- Neo + + + + + + +Multi Mapping for JSON Schemas + + + + + + +In message mapping, you can now design a multi-mapping definition by using JSON schemas. + + + + + + +Info only + + + + + + +General Availability + + + + + + +New + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Cloud Integration + + + + + + +- Cloud Foundry + + + + + + +Move Properties and Headers In A Content Modifier Step + + + + + + +You can now move the properties and headers in a content modifier step up and down to decide the order of processing them. See: [Define Content Modifier](https://help.sap.com/docs/cloud-integration/sap-cloud-integration/define-content-modifier?version=Cloud#loio8f04a707843a40bf9f6e07ed55b93034__move). + + + + + + +Info only + + + + + + +General Availability + + + + + + +New + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Integration Advisor + + + + + + +- Cloud Foundry +- Neo + + + + + + +Mapping Guidelines + + + + + + +- You can now search and filter the mapping entities in a MAG based on a specific function pattern. + + See: [Working with a Mapping Guideline \(MAG\)](../IntegrationAdvisor/working-with-a-mapping-guideline-mag-0803ca6.md) + +- You can now delete multiple mapping entities together in a Mapping Guideline. + + See: [Mapping the Source and Target Nodes](../IntegrationAdvisor/mapping-the-source-and-target-nodes-9ea58d6.md) + + + + + + + +Info only + + + + + + +General Availability + + + + + + +Changed + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Integration Advisor + + + + + + +- Cloud Foundry +- Neo + + + + + + +Export a single MIG/MAG version + + + + + + +You can now export a single version of MIG or MAG into a `.zip` file. + +See: [Exporting MIG/MAG](../IntegrationAdvisor/exporting-mig-mag-c8bba26.md) + + + + + + +Info only + + + + + + +General Availability + + + + + + +Changed + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Integration Advisor + + + + + + +- Cloud Foundry +- Neo + + + + + + +Code Value Mapping + + + + + + +Code value mapping in a MAG now supports N:1 mapping cardinality. + +See: [Code Value Mapping](../IntegrationAdvisor/code-value-mapping-eb6dad8.md) + + + + + + +Info only + + + + + + +General Availability + + + + + + +Changed + + + + + + +Technology + + + + + + +Not applicable + + + + + + +SAP Business Technology Platform + + + + + + +2023-10-01 + + + + + + +2023-10-01 + + + + + + + + +Cloud Integration + + + + + + +- Cloud Foundry + + + + + + +Software Version Update + + + diff --git a/docs/ci/sap-cloud-integration-2fb0aa4.md b/docs/ci/sap-cloud-integration-2fb0aa4.md index 256fabe2..e1cd7479 100644 --- a/docs/ci/sap-cloud-integration-2fb0aa4.md +++ b/docs/ci/sap-cloud-integration-2fb0aa4.md @@ -7,7 +7,7 @@ SAP Cloud Integration facilitates the integration of business processes spanning **Related Information** - + [SAP Cloud Integration](WhatsNewInCloudIntegration/sap-cloud-integration-72ef31d.md) @@ -29,7 +29,7 @@ SAP Cloud Integration facilitates the integration of business processes spanning [Operating and Monitoring Cloud Integration](Operations/operating-and-monitoring-cloud-integration-c401afc.md "Operate a Cloud Integration cluster and monitor messages and integration artifacts at runtime") - + [API Documentation](Development/api-documentation-3fd9fc9.md "Cloud Integration provides various application programming interfaces (APIs) with which you can access data.")