3.

4 Quality of Service

The Cloud Integration runtime supports quality of service "at least once".

This means that Cloud Integration guarantees to process an inbound

message at least once on the tenant.

When you use the one of the following adapters, you can configure
additional quality of service settings:

• AS2 sender adapter

• AS4 sender adapter

• XI sender and receiver adapter

20 PUBLIC

Feature Scope Description for SAP Cloud Integration

Features

3.5 Adapter Development

Integration developers can define custom adapters to extend the

connectivity options of Cloud Integration.

The Adapter Development Kit allows integration developers to define new

adapter types and to integrate them

into the Cloud Integration tool environment. A public application

programming interface (API) is available for

adapter development.

The Adapter Development Kit requires an Eclipse Oxygen (4.7) installation

(not supported for MAC OS).

More information on SAP Release Train for Eclipse (SRTE) at

https://tools.hana.ondemand.com/ .

The tool is available in English.

3.6 API-Based Integration Development

SAP Cloud Integration supports API-based integration development (as an

alternative to coding).

The SAP Cloud Integration Design application provides graphical editors to

design the following kinds of APIs:
• 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

• SOAP API (a SOAP API-based integration scenario with SOAP 1.x sender
adapter)

The SAP Cloud Integration Monitor application allows you to deploy and
manage SOAP, REST, and OData APIs

and to monitor message processed through these APIs.

Certain constraints might apply with regard to the usage of some of these
features (as described in the product

documentation).

OData API

The following features are available for OData API development.

Integration developers can develop OData APIs that expose existing data
sources, such as SOAP, as OData

endpoints. These OData APIs can be consumed by SAP Fiori apps, SAP
Mobile Services, or any other custom

app, to address user-centric scenarios.

You can develop OData APIs that expose existing data sources, such as
SOAP, as OData endpoints. These

OData APIs can be consumed by SAP Fiori apps, SAP BTP Mobile Services,
or any other custom app, to

implement user-centric scenarios.

OData API Development Features

Feature Description

Import from SOAP Create an OData model or add to an existing one by

importing the model definition from

SOAP Web services.

Feature Scope Description for SAP Cloud Integration

Features PUBLIC 21

Feature Description
Import from OData Create an OData model or add to an existing one by
importing the model definition from an

existing OData API.

Import from ODC Create an OData model or add to an existing one by

importing the model definition from

an OData API that is created in the IW_BEP component of an on-premise

Gateway system

(ODC).

Edit an OData model Create an OData model from scratch or edit an

existing model using the OData Model

Editor.

View an OData model View the overall layout of an OData model in the
Graphical Model Viewer.

Bind to SOAP Bind function imports and operations of entity sets in your
OData model to the corresponding SOAP Web service operations.

Bind to OData Bind function imports and operations of entity sets in your
OData model to the corresponding OData APIs.

Bind to REST Bind function imports and operations of entity sets in your
OData model to the corresponding REST services.

Bind to ODC Bind function imports and operations of entity sets in your
OData model to the corresponding OData APIs that are created in the
IW_BEP component of an on-premise Gateway

system (ODC).

Edit predefined integration

flows

Edit and update predefined integration flows that have an OData sender
adapter to suit

your business scenario. The SAP Cloud Integration Web application sets up
predefined

integration flows when OData objects are bound to a data source.

Deploy OData API Deploy an OData API once it's ready. SAP Cloud
Integration also helps you monitor the

service after deployment.

3.7 Monitoring and Operations

Enable integration developers to monitor the processing of messages and

the components of Cloud Integration

at runtime, to manage artifacts required to set up a secure connection of

the tenant and remote systems, and

to manage tenant-specific data stores.

Certain constraints might apply with regard to the usage of some of these
features (as described in the product

documentation).

22 PUBLIC

Feature Scope Description for SAP Cloud Integration

Features

Feature Description

Monitor message processing Provides an overview of the messages

processed on a tenant and displays the detailed

sequence of processing steps for individual messages (message

processing log).

Different log levels are available (no logging information, all messages
logged and displayed, only error messages logged and displayed).

Manage integration content Provides an overview of integration content

artifacts, such as integration flows or security

artifacts, that have been deployed on the tenant.

Allows you to deploy or undeploy artifacts.

Manage security artifacts and

deploy them on the tenant

Allows you to deploy security-relevant artifacts (for example: user

credentials, PGP public

keyring, PGP secret keyring, SSH known hosts artifact, secure parameter
artifact, and

OAuth2 credentials).

Manage keystore entries Allows you to manage the tenant keystore and its
entries (X.509 certificates and key
pairs).

Supported functions:

• Creating a key pair

• Creating an SSH key

• Showing details of a keystore entry

• Uploading a keystore entry

You can upload or add individual entries to an existing keystore. In the

latter case,

you can overwrite existing entries or keep them (SAP-owned keystore

entries can't

be changed or deleted).

• Downloading the public content of a keystore or a single keystore entry

• Deleting a keystore entry (not supported for SAP-owned keystore

entries)

• Backing up keystore entries owned by the tenant administrator

• Restoring backed-up keystore entries

Certain constraints apply with regard to the size of the keystore (as
described in the

product documentation).

Manage the lifecycle of keys Eases the tenant administrator's task of

renewing keys provided by SAP on the tenant.

Supported functions:

• Activating a new key pair provided by SAP to replace an old key pair that
expires

soon

• Restoring an old key pair

Manage certificate-to-user

mappings

(only available in the Neo environment)

Allows you to display and add certificate-to-user mappings (for the

tenant).
A certificate-to-user mapping maps a certificate to a user, which enables
the user to be

authenticated based on a certificate.

Manage access policies Allows you to guard access to message processing

log attachments and trace data on the

level of individual integration flows.

Feature Scope Description for SAP Cloud Integration

Features PUBLIC 23

Feature Description

Manage JDBC data sources Allows you to manage access to database

systems a tenant can connect to (using the

JDBC receiver adapter).

Test connectivity Allows you to test outbound TLS, SSH, FTP, SMTP, IMAP,
POP3, AMQP, and Kafka connections. You can also check whether a certain
Cloud Connector instance can be reached.

Manage user roles

(only available in the Cloud

Foundry environment)

Allows you to manage user roles to grant permissions to execute an

integration flow.

Manage stores Provides an overview of the stores on the tenant that are
temporarily used to persist

different types of data during message processing.

Supported kinds of stores:

• Data stores

• Variables

• Message queues (only available if a message broker has been

provisioned)

Queues that are active for a tenant (including retry of selected messages
in the

queue, deleting messages, or downloading messages as file archive).

• Number ranges
Access audit logs and system

log files

(only available in the Neo environment)

Allows you to display security-relevant events and system changes (for

example, undeployment of an integration flow).

Manage locks Allows you to display and manage lock entries, which are
created to avoid the same

message being processed several times in parallel (for example, by

different runtime

nodes).

Archive data

(only available in the Cloud

Foundry environment)

You can connect Cloud Integration to a remote content management

system and use this

system to archive data.

You can archive the following kind of data:

• Messages received from a sender and responses returned to a sender

• Messages sent to a receiver and responses returned from a receiver

• Messages stored by the Persist integration flow step

• Message processing log attachments

Note that the content management system isn't part of the Cloud
Integration feature

scope.

24 PUBLIC

Feature Scope Description for SAP