Appearance
SAP Cloud Integration
Discover, design, and operate scenarios for end-to-end process integration with Cloud Integration.
SAP Cloud Integration facilitates the integration of business processes spanning different companies, organizations, or departments within an organization.
| Feature | Description |
|---|---|
| Discover | Consume prepackaged integration scenarios. |
| Design | Build integration scenarios. |
| Monitor | Operate and observe artifacts. |
| Settings | Manage your tenant. |
How to get started?
Find relevant SAP Tutorials for Developers or SAP Community Blogs.
Integration Artifact Types
You can design the following integration artifact types with the Cloud Integration capability activated:
| Type | Description |
|---|---|
| Integration flow | Specifies how messages are exchanged within an integration scenario. |
| Value mapping | Maps two ways of representing the same object with each other. You use value mappings when you need to exchange messages between two systems that represent the same object in different ways. |
| SOAP API | A SOAP API-based integration flow with a SOAP 1.x sender adapter. |
| OData API | An OData API-based integration scenario with OData V2 sender adapter. |
| REST API | A REST API-based integration scenario with HTTPS sender adapter. |
| Message mapping | Transforms a source into a target message. |
| Script collection | A set of scripts that can be used in a Script integration flow step. |
| Function Libraries | Contains functions from ESR that can be used in a mapping. |
| Imported Archives | Contains imported archives from ESR that can be used in a mapping. |
| Integration adapter | Allows you to import a custom adapter into your integration package. |
| Data type | Contains the structure of data that defines the message. |
| Message type | Describes the structure of a message. |
Content Transport
Reuse content across multiple tenants. Export integration content from one (source) tenant and import it on another (target) tenant. SAP Help
| Transport Option | Description |
|---|---|
| CTS+ | With a single step, transport integration content from one tenant to another through the CTS+ system. |
| Transport Management Service | With a single step, transport integration content from one tenant to another through the Cloud Transport Management service. |
| MTAR Download | Download an MTAR file from the source tenant and manually upload the same file to a CTS+ system or Cloud Transport Management service. |
| Manual export and import | Manually export integration content from the source tenant and manually import this content to the target tenant. |
External Logging
The external logging feature enables customers to send message processing logs to an external system, independently of available database storage.
The major customer use cases for the external logging feature are the integration into existing monitoring solutions in Splunk, or the consolidation of logs of multiple tenants.
What is splunk>?
Splunk is a software platform that collects, indexes, and analyzes machine-generated data, providing insights for various purposes like security, operations, and business intelligence. It acts as a centralized platform for searching, monitoring, and visualizing data from diverse sources.
Destination
Set up your external logging destination to enable the external logging feature:
| Property | Description |
|---|---|
| Name:* | The name must be CloudIntegration_MonitoringDataConsumer. |
| Type:* | The type HTTP is used for both HTTP and HTTPS connections. |
| URL:* | Add the destination URL to the Splunk HTTP Event Collector without the endpoint. For a detailed description how the event collector URL is structured. |
| Proxy Type:* | Choose Internet for a Splunk Cloud Platform instance and On Premise for a Splunk Enterprise installation. |
| Authentication:* | Choose Basic Authentication. |
| User:* | Specify the value "Splunk". |
| Password:* | Specify the HTTP Event Collector token (generated when configuring HEC in Splunk). |
| IndexName:* | Enter an index name. |
Additional Properties:
| Property | Description |
|---|---|
| TargetSystem* | Splunk |
| Source | Any value, used to fill in the source attribute Splunk events. |
| Host | Any value, used to fill in the host attribute Splunk events. |
| SourceType | If the source type is specified, it's set to the defined value in Splunk events. |
| DynamicSourceType | If set to true, the source type is set to a value matching one of the following event types:
|
| SourceTypePrefix | If DynamicSourceType is true, and the SourceTypePrefix property is, the property value is prepended to the source type. For example: for a prefix of Custom and an MPL run event, the source type is to CustomRun. |
| SubValuesInline | If the property is set to true, values like custom header attributes and adapter attributes are added as JSON structures to the base Run event. This property is independent from the SubValuesExtra property. |
| SubValuesExtra | If the property is set to true, values like custom header attributes and adapter attributes are added as separate stand-alone events, following the base Run event. This property is independent of the SubValuesInline property. |
API
Activate
To enable external logging, send a POST call to the following URL:
http
POST https://path-to-odata-api/api/v1/activateExternalLogging
[?defaultLogLevel=(NONE|INFO|ERROR)]Disabling External Logging
After activation, you can cancel the logging to an external destination by deactivating the external logging feature:
http
POST https://path-to-odata-api/api/v1/deactivateExternalLoggingExternal Logging Status Information API
To retrieve status information , send a GET call to the following URL:
http
GET https://path-to-odata-api/api/v1/ExternalLoggingEventsIf external logging is activated, it returns a list of events that occurred in the last 14 days for these possible events:
- External Logging was activated.
- External logging was deactivated.
- Errors causing failures in sending data to an external system.
- Resuming sending data to an external system once an error is cleared.
Query the message processing logs:
http
GET https://path-to-odata-api/api/v1/ExternalLoggingActivationStatus('tenant-name')Blog
- Message Monitoring – Standard Out of the Box Features to use in your Iflows
- External Logging to Splunk and Current Limitations
- External Logging (To Splunk)- Under the Hood
- Custom Headers – Reusable Groovy Script
- Archive Message Processing Logs (MPLs) to SAP BTP Document Management Service (DMS)
Support
| Component Name | Component Description |
|---|---|
| LOD-HCI-PI | Support component for this service |
| LOD-HCI-PI-OP | For on-premise adapters (e.g., SAP Cloud Connector, Agent) |
| LOD-HCI-PI-CON | Connectivity issues (e.g., endpoints, proxies, certificates) |
| LOD-HCI-PI-MON | Monitoring-related issues |
| LOD-HCI-PI-IFL | IFlow-specific issues |
When creating an SAP incident, it's helpful to include:
- IFlow ID & version
- Tenant (e.g., EU10, US30…)
- Timestamp of the issue (with timezone)
- Error message & trace logs