Developer's Guide: Managing Integration Content: Public SAP Cloud Platform Integration For Processes 2019-02-15

PUBLIC
SAP Cloud Platform Integration for Processes

2019-02-15
Developer's Guide: Managing Integration Content

© 2019 SAP SE or an SAP affiliate company. All rights reserved.
THE BEST RUN

Content
1 Managing Integration Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Developing Integration Content Using the Eclipse Integration Designer. . . . . . . . . . . . . . . . . . . 6

2.1 Understanding the Basic Concepts and the Development Environment . . . . . . . . . . . . . . . . . . . . . . . 6
Elements of an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Understanding the Integration Content Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2 Installing and Configuring the Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Opening the Integration Designer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring the SAP Cloud Platform Integration Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Uninstalling a Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
2.3 Developing Integration Flows and Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Creating Integration Project for an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
(Optional) Creating a Working Set of Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Importing SAP NetWeaver PI Objects from On-Premise Repository. . . . . . . . . . . . . . . . . . . . . . .26
Modifying an Integration Flow Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Saving Integration Flow as a Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Using Custom Functions in Message Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.4 Developing Value Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Creating a Value Mapping Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Editing the Value Mapping Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Exporting and Importing Value Mapping Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Referencing Value Mappings from a Message Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Checking the Value Mapping Consistency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.5 Configuring an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Assigning the Sender and Receiver Participants. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Defining Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Defining Message Transformers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Defining Message Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260
Validating Message Payload against XML Schema. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
Defining Message Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272
Defining Security Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Defining Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Defining Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Defining Additional Elements (Others). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Defining the Error Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Error Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .367

2 PUBLIC Content
Specifying Runtime Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Defining Transaction Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
Externalizing Parameters of Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
2.6 Working with the Mapping Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Creating a Message Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
Handling Inconsistencies in Mapping Editor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Exporting Mapping Details to Excel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
2.7 Testing an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Checking the Consistency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
2.8 Operations-Related Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Deploying an Integration Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Viewing Error Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .390
Activating Tracing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .391
2.9 References to Additional Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
3 Packaging Integration Content in SAP Cloud Platform Integration Web Application. . . . . . . 396
3.1 Uploading Integration Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
3.2 Creating an Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
3.3 Working with an Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
3.4 Editing an Integration Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
3.5 Locking Integration Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
3.6 Updating Integration Packages and their Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
3.7 Exporting Integration Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
4 Developing Integration Content With the SAP Cloud Platform Integration Web Application
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
4.1 Understanding the Basic Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Elements of an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Adapter and Integration Flow Step Versions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Versioning of Artifacts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Product Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
4.2 Generating Integration Content using APIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
4.3 Working with Prepackaged Integration Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
4.4 Add Integration Packages to the Customer Workspace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
4.5 Creating an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415
4.6 Integration Flow Extension. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Integration Flow Extension - Concepts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Mapping Extension Step by Step (Demo Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Mapping Extension Step by Step (Example from SAP Hybris C4C). . . . . . . . . . . . . . . . . . . . . . 446
4.7 Content Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .453
Enabling Content Transport. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455

Content PUBLIC 3
Creating HTTP Destination in Solutions Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . 456
Content Transport Using CTS+. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Content Transport Using Transport Management Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Content Transport using MTAR Download. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Content Transport using Manual Export and Import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
4.8 Importing Content from ES Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Configuring Connectivity to ES Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Importing Mapping Content from ES Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
4.9 Working with Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .464
Message Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Creating Value Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Configuring Value Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Create XSLT Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
4.10 Migrate to New Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
4.11 Specify the Runtime Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
4.12 Configure Externalized Parameters of an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
4.13 Configure Multiple Integration Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
4.14 Externalize Parameters of an Integration Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
4.15 Configure Integration Flow Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
New and Improved Integration Flow Editor for SAP Cloud Platform Integration. . . . . . . . . . . . . 485
Assign Sender and Receiver Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Assign Adapter to Communication Channel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Configure Adapter in Communication Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Define Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Define Routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Define Message Transformers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Define Security Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Define Message Persistence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Validating Message Payload against XML Schema in Web UI. . . . . . . . . . . . . . . . . . . . . . . . . . 835
Define Call. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836
Define Additional Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .846
Defining Transaction Handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .848
Dynamically Configure Integration Flow Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
Define Error Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Manage Resources of an Integration Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Problems View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Error Classification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .872
4.16 Deploying Data Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873

4 PUBLIC Content
1 Managing Integration Content
Design integration content in order to specify how messages are to be exchanged between the connected
components.
SAP Cloud Platform Integration provides a set of tools and applications that help you perform end-to-end tasks
on development and deployment, packaging and publishing, accessing and editing the integration content.
This topic provides an overview of roles, working environment and tasks involved in managing integration
content.
Quick Links:
● Developing Integration Content With the SAP Cloud Platform Integration Web Application [page 403]
● Developing Integration Content Using the Eclipse Integration Designer [page 6]
Since the tasks are performed by different roles, in different working environment such as, Integration Designer
on Eclipse platform or SAP Cloud Platform Integration Web application on SAP UI5, the figure below helps you
understand the relationship between the roles, tools/applications, and tasks:

Managing Integration Content PUBLIC 5
2 Developing Integration Content Using the
Eclipse Integration Designer
SAP Cloud Platform Integration provides integration tools on the Eclipse platform to model integration flows,
configure attributes of the integration flows, and deploy them to the runtime.
You can work with the integration tools in the local development mode, which means that you create an
integration project in your local Eclipse workspace and start developing integration content using the features
available in the Integration Designer perspective. Once the content is ready, you deploy the project to the
runtime in the SAP Cloud Platform Integration infrastructure.
Installing Features of SAP Cloud Platform Integration
To develop and configure integration content, install the features as described on the installation page SAP
Cloud Platform Integration Tools.
2.1 Understanding the Basic Concepts and the

Development Environment
2.1.1 Elements of an Integration Flow
An integration flow allows you to specify how a message is processed on a tenant.
You can use integration flows to specify specific integration patterns like mapping or routing.
A graphical editor allows you, the integration developer, to model the message processing steps and specify in
detail what happens to the message during processing.
In detail, you define the following aspects in an integration flow:
● The senders and receivers of the message

● How the senders and receivers are connected to the tenant (adapters)
● The steps that define the message processing
The following figure provides a simplified and generalized representation of an integration flow.

6 PUBLIC Developing Integration Content Using the Eclipse Integration Designer
Senders and Receivers
You define a participant of an integration scenario as a sender or receiver. The senders and receivers typically
represent the customer systems that are connected to the tenant and exchange messages with each other.
Connectivity (Adapters)
An integration flow channel allows you to specify which technical protocols should be used to connect a sender
or a receiver to the tenant.
 Note
To specify an adapter, click the connection arrow between the sender/receiver and the Integration Process
box.
Message Processing (Steps)

You use integration flow steps to specify what should happen to a message during processing. Various step
types support the wide range of integration capabilities of the Cloud-based integration platform.
 Note
To insert a step into an integration flow, drag and drop the desired step type from the palette on the right of
the graphical modeling area.
Message Flows
You use message flows to connect various integration flow elements.
2.1.1.1 Headers and Exchange Properties
The integration framework gives you options to evaluate certain parameters at runtime, which allows you to
define sophisticated ways of controlling message processing. There are two different kinds of parameter:

Developing Integration Content Using the Eclipse Integration Designer PUBLIC 7
● Message header
This is transferred as part of the message header.
When you use an HTTP-based receiver adapter, these parameters are converted to HTTP headers and
transferred asi such to the receiver.
 Note
Note that data written to the message header during a processing step (for example, in a Content
Modifier or Script step) will also be part of the outbound message addressed to a receiver system
(whereas properties will remain within the integration flow and will not be handed over to receivers).
Because of this, it is important to consider the following header size restriction if you are using an
HTTP-based receiver adapter: If the message header exceeds a certain value, the receiver may not be
able to accept the inbound call (this applies to all HTTP-based receiver adapters). The limiting value
depends on the characteristics of the receiver system, but typically ranges between 4 and 16 KB. To
overcome this issue, you can use a subsequent Content Modifier step to delete all headers that are not
supposed to be part of the outbound message.
● Exchange property
For as long as a message is being processed, a data container (referred to as Exchange) is available. This
container is used to store additional data besides the message that is to be processed. An Exchange can be
seen as an abstraction of a message exchange process as it is executed by the Camel framework. An
Exchange is identified uniquely by an Exchange ID. In the Properties area of the Exchange, additional data
can be stored temporarily during message processing. This data is available for the runtime during the
whole duration of the message exchange.
When you use an HTTP-based receiver adapter, Exchange properties are not converted to an HTTP header
for transfer to the receiver.
You can use the Content Modifier to modify the content of the message header and the Exchange property (as
well as of the message body) at one or more steps during message processing.
You can use the message header and the Exchange property to configure various sophisticated ways of
controlling message processing.
One option is to use dynamic parameters:
When configuring an integration flow using the modeling user interface, you can define placeholders for
attributes of certain adapters or step types. The value that is actually used for message processing is set
dynamically based on the content of the message. You can use a certain message header or Exchange property
to dynamically set a specific integration flow property.
Another option to derive such data from a message at runtime is to access a certain element in the message
payload.
The following headers and Exchange properties are supported by the integration framework.
 Note
A subset of these parameters is provided by the associated Open Source components, such as Apache
Camel.
Headers Relevant for Signing with XML Digital Signature
● CamelXmlSignatureTransformMethods
Specifies transformation methods in a comma-separated list.

You can use this header to specify transformation methods in a comma-separated list. This header will
overwrite the value of the option Transform Method for Payload.
 Example
 Sample Code
Example of this use case: The XML signature verifier of the receiving system expects an XML signature
as shown in the following code snippet.
The signature is a detached signature, because the signature element is a sibling of the signed element
B. However, the receiving system requires the enveloped-signature transform method to be specified in
the Transforms list. To ensure this, you have to configure a detached signature in the XML Signer step,
then add a Content Modifier step before the XML Signer step, where you specify the header
"CamelXmlSignatureTransformMethods" with the constant value “http://www.w3.org/2000/09/
xmldsig#enveloped-signature,http://www.w3.org/TR/2001/REC-xml-c14n-20010315".
<?xml version="1.0" encoding="UTF-8" ?>

<root>
<B ID="IDforB">
...
</B>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
Id="_6bf13099-0568-4d76-8649-faf5dcb313c0">
<ds:SignedInfo>
...
<ds:Reference URI="#IDforB">
<ds:Transforms>
<ds:Transform Algorithm="http://www.w3.org/
2000/09/xmldsig#enveloped-signature" />
<ds:Transform Algorithm="http://www.w3.org/TR/
2001/REC-xml-c14n-20010315" />
</ds:Transforms>
...
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>aUDFmiG71</ds:SignatureValue>
</ds:Signature>
<root>
Headers Relevant for Message Signing with XML Advanced Electronic Signature
● CamelXmlSignatureXAdESQualifyingPropertiesId
Specifies the Id attribute value of the QualifyingProperties element.
● CamelXmlSignatureXAdESSignedDataObjectPropertiesId
Specifies the Id attribute value of the SignedDataObjectProperties element.
● CamelXmlSignatureXAdESSignedSignaturePropertiesId
Specifies the Id attribute value of the SignedSignatureProperties element.
● CamelXmlSignatureXAdESDataObjectFormatEncoding
Specifies the value of the Encoding element of the DataObjectFormat element.
● CamelXmlSignatureXAdESNamespace
Overwrites the namespace parameter value.
● CamelXmlSignatureXAdESPrefix
Overwrites the prefix parameter value.
Headers Relevant for Message Splitting

● CamelSplitIndex
Provides a counter for split items that increases for each Exchange that is split (starts from 0).
● CamelSplitSize
Provides the total number of split items (if you are using stream-based splitting, this header is only
provided for the last item, in other words, for the completed Exchange).
● CamelSplitComplete
Indicates whether an Exchange is the last split.
Headers Relevant for Content Encoding
● CamelCharsetName
Specifies the character encoding to be applied for message processing.
Is relevant for content encoding steps.
Headers Relevant for the HTTP and HTTPS Adapter
● CamelHttpUri
Overrides the existing URI set directly in the endpoint.
This header can be used to dynamically change the URI to be called.
● CamelHttpUrl
Refers to the complete URL called, without query parameters.
For example, CamelHttpUrl=https://test.bsn.neo.ondemand.com/http/hello.
● CamelHttpQuery
Refers to the query string that is contained in the request URL.
In the context of a receiver adapter, this header can be used to dynamically change the URI to be called.
For example, CamelHttpQuery=abcd=1234.
● CamelHttpMethod
Refers to the incoming method names used to make the request. These methods are GET, POST, PUT,
DELETE, and so on.
● CamelServletContextPath
Refers to the path specified in the address field of the channel.
For example, if the address in the channel is /abcd/1234, then CamelServletContextPath is /abcd/1234.
● CamelHttpResponseCode
This header can be used to manually set the HTTP response code.
● Content-Type
HTTP content type that fits to the body of the request.
The content type is composed of two parts: a type and a subtype.For example, image/jpeg (where image
is the type and jpeg is the subtype).
Examples:
○ text/plain for unformatted text
○ text/html for text formatted with HTML syntax
○ image/jpeg for a jpeg image file
○ application/json for data in JSON format to be processed by an application that requires this
format
More information on the available types: https://www.w3.org/Protocols/rfc1341/4_Content-Type.html
The list of available content types is maintained by the Internet Assigned Numbers Authority (IANA). For
more information, see http://www.iana.org/assignments/media-types/media-types.xhtml .

 Note
If transferring text/* content types, you can also specify the character encoding in the HTTP header
using the charset parameter.
Here is an example of such a header:
Content-Type: text/html; charset=utf-8
The default character encoding that will be applied for text/* content types depends on the HTTP
version: us-ascii for HTTP 1.0 and iso-8859-1 for HTTP 1.1.
Text data in string format is converted using UTF-8 by default during message processing. If you want
to override this behavior, you can use the Content Modifier step and specify the CamelCharsetName
Exchange property. To avoid encoding issues when using this feature together with the HTTP adapter,
consider the following example configuration:
If you use a Content Modifier step and you want to send iso-8859-1-encoded data to a receiver, make
sure that you specify the CamelCharsetName Exchange property (either header or property) as
iso-8859-1. For the Content-Type HTTP header, use text/plain; charset=iso-8859-1.
● Content-Encoding
HTTP content encoding that indicates the encoding used during message transport (for example, gzip for
GZIP file compression).
This information is used by the receiver to retrieve the media type that is referenced by the content-type
header.
If this header is not specified, the default value identity (no compression) is used.
More information: https://tools.ietf.org/html/rfc2616 (section 14.11)
more information, see:http://www.iana.org/assignments/http-parameters/http-
parameters.xhtml#content-coding .
Headers Relevant for the SFTP Adapter
● CamelFileName
Overrides the existing file and directory name that is set directly in the endpoint.
This header can be used to dynamically change the name of the file and directory to be called.
Headers Relevant for the Mail Adapter
 Note
The mail adapter supports all possible headers that a mail server or mail client can set. Which headers are
set or not set depends on the mail server and the mail client. The headers listed in the table below are
examples of commonly used headers.
● Subject
Specifies the subject of the e-mail message.
● To
Specifies the e-mail address that the message is sent to.
● Cc
Specifies the additional e-mail address that the message is sent to.
● From
Specifies the e-mail address that the message comes from.

● Date
Specifies the date and time when the e-mail was sent.
● Content-Type
Specifies the format of the e-mail (html or plaintext)
● Message-ID
Specifies the ID that the mail system assigned to the e-mail when it was first created.
● Reply-to
Specifies the message ID of the message that this e-mail is a reply to.
● Sender
Specifies the actual sender (acting on behalf of the e-mail address stated in the From header).
● Archived-At
Specifies a link to the archived form of an e-mail.
Headers Relevant for the Aggregator Step
● CamelAggregatedCompletedBy
This header is relevant for use cases with message aggregation.
The header attribute can only have one of the following values:
○ timeout
Processing of the aggregate has been stopped because the configured Completion Timeout has been
reached.
○ predicate
Processing of the aggregate has finished because the Completion Condition has been met.
Headers Relevant for JMS Messages
● JMSTimestamp
Specifies the time when a JMS message was created.
Headers Relevant for the SOAP (SOAP 1.x), SOAP (SAP RM), and IDoc Adapter
● SOAPAction Header
This header is part of the Web service specification.
● SapAuthenticatedUserName
Contains the user name of the client that calls the integration flow.
If the sender channel is configured to use client certificate authentication, no such header is set (as it is not
available in this case).
● SapIDocType <XML Response>
The adapter parses the XML Response and generates the SapIdocType header from it.
An example header would be:
SapIDocType WPDTAX01
.
● SapIDocType <XML Response>

Additional Message Header
You can specify one of the following headers (under Message Header in the Name field):
● SAP_ApplicationID
When you monitor the messages at runtime, you can search for all messages whose defined
SAP_ApplicationID has a specific value (displayed as the MessageID attribute in the Message
Monitoring editor).
As Type, select the XPath expression that points to the message element that is to be used as the
application ID.
● SAP_Sender
● SAP_Receiver
● SAP_MessageType
You can use this property to categorize messages.
● SAP_MessageProcessingLogID
You can use this property to read the ID of the message processing log (no write access supported).
If you have specified SAP_Sender or SAP_Receiver, the corresponding values are displayed in the message
processing log. If you change the SAP_Receiver value during message processing, all values are added to the
receiver field in the message processing log as a comma-separated list. If you don't want this behavior, you can
specify the exchange property SAP_ReceiverOverwrite (see below).
Exchange Properties
You can specify one of the following Exchange properties (under Exchange Property in the Name field):
● SAP_CorrelateMPLs
You can use this property to specify whether message processing logs (MPLs) are to be correlated with
each other using a correlation ID.
By default, MPL correlation is switched on. To specify this property, select Constant as Type and enter
True or False as Value.
● SAP_ReceiverOverwrite
Headers that are added to a message using the SAP_Receiver header element during message
processing are appended to the message processing log (MPL).
This behavior is helpful in scenarios like,the multicast pattern, for example, where a message is sent to
several receivers and all receivers are to be collected in the MPL (not just the last added header).
By setting the SAP_ReceiverOverwrite exchange property to true, you can change this behavior in
such a way that only the last added header is shown in the MPL.
 Note
Example configuration:
Name: SAP_ReceiverOverwrite
Type: Constant
Value: True

● SAP_ErrorModelStepID
You can use this property to set a Model Step ID for an integration flow step. This identifier is required to
relate to an integration flow step in error handling.
● SAPJMSRetries
Contains the number of retries of a JMS message.
You can use this property to specify that the behavior of the integration flow changes depending on the
number of retries that are actually performed. For example, you can configure a scenario where a mail is
sent to an administrator with the message as an attachment and the integration flow is terminated
successfully after a specified number of retries.
● SAPJMSAlerttime
Specifies the time when an alert needs to be sent.
● SAPJMSRetryAt
Specifies the time when a JMS message must be retried.
● SAP_MessageProcessingLogCustomStatus
You can use this property to set an at most 40 characters alphanumeric custom status for the current
message processing log. The value is transferred as CustomStatus attribute to the root part of the
message processing log and then stored in the message processing log header table.
Related Information
Dynamic Parameters (Example) [page 14]
2.1.1.1.1 Dynamic Parameters (Example)
You can define placeholders for parameters of certain adapters or step types. The values of these parameters
will then dynamically be set based on the content of the processed message.
For example, parameters From, To, Cc, Bcc, Subject, Mail Body as well as the attachment name, can be
dynamically set at runtime from message headers or content.
To set an attribute to be dynamically filled by a message header attribute, enter a variable in the form $
{header.attr} in the corresponding field for the attribute of the corresponding step or adapter.
At runtime, the value of the header attribute (attr) of the processed message is written into the field for the
corresponding attribute of the outbound email.
Example: Dynamic Attributes for the Mail Adapter
For example, assume that you dynamically define the email Subject of the mail adapter as shown in the figure
below by the variable {header.attr}.
At runtime, a message is received whose header contains a header attribute attr with the value value1. The
mail adapter will then dynamically set the subject of the outbound email with the entry value1.

Note that the mail adapter processes message content either already contained in the inbound mail (from a
sender system) or as modified by content modifier steps on its way between sender and mail adapter.
As shown in the figure, we assume that the inbound message contains a header header1 with value value1.
Let us assume that you like to define the Subject attribute of the mail receiver adapter dynamically via this
header. To do that, specify the Subject field by the following entry:
${header.header1}
As a result, the mail adapter dynamically writes value value1 of header header1 (from inbound message) into
the subject of the outbound email.
Related Information
Parameters That Support Dynamic Configuration [page 854]
2.1.2 Understanding the Integration Content Types
SAP Cloud Platform Integration provides features on Eclipse to develop and configure integration content.
The feature, called the Integration Designer, provides options to develop integration flows in your local Eclipse
workspace, which implies no network connection is required during development. Each integration flow is
associated with a project and can refer to other entities, such as message mappings, operation mappings, and
WSDL definitions, that are available within the same project.
The integration flow can also refer to an entity, such as a value mapping, that is not available within its project.
You create a separate value mapping project such that the reference takes place across the projects within the
workspace.
The integration flow along with other referenced entities form the integration content. Once you complete the
development of integration content, you deploy the integration flow project as well as the referenced value
mapping to the runtime.
 Note
Another feature, called the Integration Operation Monitoring, provides options to monitor the deployed
integration projects in runtime.
Types of Integration Projects
The sections below introduce you to different project types that the tooling provides based on the entities.

Integration Flow Project Type
The Integration Flow project type contains packages for creating integration content, where each package
consists of a particular entity.
Integration Flow Project Structure
Elements in Project Structure Description
src.main.resources.mapping Package for mappings to be used in scenario
src.main.resources.scenarioflows.integrationflow Package for BPMN integration flow
src.main.resources.wsdl Package for interfaces like IDOC , WSDL used in scenario
MANIFEST.MF File contains dependencies to runtime components and inte

gration content metadata
 Note
Additional files that are available in the Integration Flow project types are:
Additional Elements in Project Structure Description
src.main.resources Package for parameters.prop and parameters.propdef

files
parameters.prop File contains externalized attributes representing a varia

ble such as a the customer's landscape information.
parameters.propdef File contains metadata such as value type of the parame

terized attribute, its description and whether the attribute
should be configured mandatorily.
Value Mapping Project Type
The Value Mapping project type is used for scenarios that require you to map different representations of an
object to each other. Each value mapping project contains one or more value mapping group that is a set of
values of the object.
Value Mapping Project Structure
Elements in Project Structure Description
MANIFEST.MF File contains dependencies to runtime components
value_mapping.XML File contains value mapping groups that hold the objects and
their corresponding representations
2.1.3 Restrictions
The Integration Designer allows you to model specific patterns which are handled at runtime in an unexpected
way.
The following table lists the restrictions.

Restrictions and Alternative Configuration Settings
Expected Behavior at Run
Modelled Pattern time Actual Behavior at Runtime Alternative Modeling Option
Integration flow step with The same message is proc The messages are delivered Configure only one outgoing
more than one outgoing se essed in parallel after the in to the different receivers in a sequence flow and parallel
quence flows tegration flow step. sequence. processing using a multicast
of messages.
For example, after a Message Hereby, the order in that the
Persistence step the mes messages are delivered is
sage is supposed to be sent randomly generated.
to multiple receivers in paral
In addition to that, the follow
lel.
ing behavior may occur: the
message which results from
the processing in the previ
ous sequence flow is taken
as input for the next se
quence flow.
 Note
As an example, consider
two parallel sequence
flows where the first one
contains an encryption
step and the second one
not. In that case, the re
ceiver of the second se
quence flow also gets an
encrypted message (al
though in the second se
quence flow no encryp
tion step has been con
figured).
Comment on Database Transactions

The following step types include transactional database processing.
If one of the below listed steps is contained in an integration flow, the processing of the message is executed in
one transaction.
● Data Store Operations step

○ Select (in case delete=true)
○ Write
○ Get (in case delete=true)
○ Delete
● Usage of Write variables
● Aggregator step
● Content Enricher
 Caution
Such steps might lead to resource shortages because long running transactions can cause node instability
and impede other processes that are running in transactions.

Some of the above mentioned steps or adapters persist data in the database. In case of an error, the whole
process is rolled back and the original state is being re-established. That means, data from failed processes
remain and, in case message processing fails, customers normally cannot access data about the failed
processing (due to the roll-back).
In case an error is propagated back to the calling component, all data that have been written in the course
of the (failed) transaction are being removed (in other words: not persisted in the database). For the calling
component, an error implies, therefore, to restart the integration flow.
Transactional processing is also to be considered in scenarios that contain asynchronous decoupling. Let’s
assume integration flow A contains a Data Store Operation step. Integration flow B contains a Select
operation on the Data Store and runs into an error. In that case, that data is preserved that has been written
to the database by integration flow A. This behavior makes sense in particular when you consider the case
that integration flow B changes or deletes the data that has been stored by integration flow A. In case
integration flow B fails, the original data from integration flow A can be retrieved.
Additional Restrictions
Usage of an Aggregator step in a Local Integration Process or Exception Subprocess is not supported.
2.2 Installing and Configuring the Tool
You install the features of SAP Cloud Platform Integration on the Eclipse integrated development environment
(IDE) to access the Integration Designer functions.
2.2.1 Opening the Integration Designer
You open the Integration Designer as perspective in Eclipse.
Context
Procedure
1. Start Eclipse.
2. In the main menu, choose Windows Open Perspective Other...

3. In the Open Perspective dialog, select Integration Designer.
2.2.2 Configuring the SAP Cloud Platform Integration

Preferences
You can make specific settings for SAP Cloud Platform Integration in the Eclipse Preferences.
Context
You perform the tasks below to configure the tool settings with attributes you are likely to need when working
with the Eclipse IDE.
You can find the specific settings for SAP Cloud Platform Integration under Window Preferences SAP
Cloud Platform Integration .
Related Information
Operations Server [page 19]

Personalize [page 20]
Repository Connection [page 22]
Testing Configuration [page 22]
2.2.2.1 Operations Server
You need to specify the connection from Eclipse to the tenant management node in order to perform tasks
such as deploying integration flows on the tenant.
The tenant management node contains the operations subsystem that is responsible for tasks such as
deploying integration content or selecting monitoring data from the database.
Operations Server Settings
Property Description
URL Tenant management node URL (also referred to as manage

ment URL)
Enter the URL that was provided during tenant provisioning.
User User and password for this connection

Password
Choose Test Connection to test whether the specified URL and user/password enable you to connect to the
tenant management node.
If the URL and user/password are correct but you still get the error message Sending request to server
failed. Reason: Error during processing request on client, check the proxy settings in Eclipse
(under Window Preferences General Network Connections ).
2.2.2.2 Personalize
You can specify personal settings that control how to deal with integration flow templates and how to handle
integration project/integration flow creation.
Personal Settings
Store integration flow templates at Location where to store integration flow templates on your
local computer
Always create integration flow for new integration project If this checkbox is selected (which is the default setting), an
integration flow is always created for a new integration
project.
When you choose to create a new integration project ( File
Integration Project New ), a wizard opens. On the

first page of the wizard, you enter the project name. When
you click Finish (and you have selected the Always create
integration flow for new integration project checkbox in the
Preferences), an integration flow is created for the project
(with the same name as the project).
If you have deselected this checkbox, you have to explicitly

specify an integration flow name (on the next page of the
wizard) and finish the wizard in order to trigger the creation
of an integration flow.

2.2.2.3 Working with Product Profiles
Product profile is a collection of capabilities such as success factor adapter, splitter or datastore elements,
available for a particular product. You can consume these capabilities at the time of designing integration flows.
Context
SAP Cloud Platform Integration enables you to design for multiple runtimes at the same time. You should
select specific product profile to develop content for the respective runtime.
 Note
● If a product profile does not support a particular capability then the checks report errors for
unsupported components in the integration flow.
Procedure
1. To assign product profile at project level, execute the following substeps:

a. Open an integration project, go to Properties tab.
b. From the Product Profile drop down list, select the required profile.
2. To assign product profile at workspace level, execute the following substeps:
a. In Eclipse, navigate to Windows -> Preferences-> SAP Cloud Platform Integration-> Product Profiles.
b. Select the required profile.
 Note
○ If no product profile is selected, by default it is SAP Cloud Platform Integration at the project level
configuration. Also, in that case the system applies workspace level product profile for the
integration flow.
○ If you want to import or export the zip file format of product profile, then you can use Import or
Export option.
○ If you update the tooling, cmd folder is placed inside workspace directory and old profiles cached
in old cmd location are lost. You can manually copy old profiles to the new cmd location and restart
eclipse.
○ You can reload component metadata in the following 3 ways:
○ You can reopen eclipse tool.
○ You can reconnect to server.
○ You can use icon (on eclipse toolbar) to manually download it.

Related Information
Product Profiles [page 407]
2.2.2.4 Repository Connection
If you need to import interfaces or mappings from an on-premise repository, such as the Enterprise Services
Repository, you have to set the connection details to establish the connection with the repository.
Connection to the Enterprise Services Repository is supported for both the Advanced Adapter Engine
(AEX) and Dual Stack.
Repository Connection Settings
URL URL of the on-premise repository in the format

http(s)://<host>:<port>
User User and password for this connection
Password
Choose Test Connection to test whether the specified URL and user/password enable you to connect to the
repository.
2.2.2.5 Testing Configuration
You can specify settings that control how integration tests are executed.
2.2.3 Uninstalling a Feature
Context
You use this task only if you need to uninstall a feature of an installed software plugin.

Procedure
1. From the main menu, choose Help About Eclipse SDK .

2. In the About Eclipse SDK dialog, choose Installation Details.
3. In the Eclipse SDK Installation Details wizard, select the required feature to be uninstalled.
4. Choose Uninstall....
5. In the Uninstall dialog, review the plugin you have selected and choose Finish.
6. In the Software Update dialog, choose Restart Now.
2.3 Developing Integration Flows and Projects
2.3.1 Creating Integration Project for an Integration Flow
Context
An integration flow is a graphical representation of how the integration content can be configured to enable the
flow of messages between two or more participants using SAP Cloud Platform Integration, and thus, ensure
successful communication.
You perform this task to create a BPMN 2.0-based integration flow model in your integration project under the
src.main.resources.scenarioflows.integrationflow package. You can create an integration flow by using the
built-in patterns, templates provided by SAP, or user-defined templates.
 Note
You can use the templates provided by SAP in the New Integration Flow wizard page to help you create and
modify integration flows based on certain scenarios. These templates are based on some of the SAP
supported scenarios.
 Restriction
In this release, SAP supports only limited number of possible integration scenarios.

Procedure
1. In the main menu, choose Window Open Perspective Integration Designer to open the
perspective.
2. In the main menu, choose File New Integration Project… to create a new integration project.
3. In the New Integration Project wizard, enter a project name.
 Note
○ By default, Node Type is set to IFLMAP, which indicates that the integration flow is deployed to that
node in the runtime environment.
○ Choose product profile for the integration project from Product Profile field. The integration flow
templates used during creation adheres to the latest version of a component available in product
profile.
4. If you want to add the project to the working set at this point, select the option Add project to working set.
 Note
If you do not choose to add the project to the working set in this step, you can add it later. For more
information about working sets, see Creating a Working Set of Projects [page 25].
5. If you want to create an integration flow of a specific pattern for the new integration project, choose Next.
 Note
You can also create an integration project together with a point-to-point integration flow. To enable this
option, choose Window Preferences SAP Cloud Platform Integration Integration Flow
Preferences page, and select the Auto-create integration flow on 'Finish' during integration project
creation option.
6. In the New Integration Flow page, enter a name for the integration flow.
7. If you want to create an integration flow using the built-in patterns, select the Enterprise Integration
Patterns category and choose the required pattern.
8. If you want to create an integration flow using SAP templates, select the SAP Defined Template category
and choose the required template.
9. If you want to create an integration flow using templates specific to your scenario, select the User Defined
Template category and choose the required template.
 Note
You can find the templates in the User Defined Template category only if you have saved an integration
flow as a template. For more information, see Saving Integration Flow as a Template [page 29].
10. Choose Finish.

A new project with <integration flow>.iflw is available in the Project Explorer view.
11. If you want to provide a description for the integration project, follow the steps below:
a. In the Project Explorer, select the integration project and choose the Properties view.
b. In the Properties view, select the Project Configuration tab.
c. In the Project Configuration tab page, provide basic details about the integration project, and enter the
bundle name and bundle ID.

 Note
○ The bundle name and bundle ID that you enter get updated in the MANIFEST.MF file.
○ The bundle name and the integration project name are two different attributes.
○ The Node Type shows the runtime node type on which the integration flow is deployed.
○ The description field allows you to enter brief information about the integration project to help
other users understand the use of the project.
12. Click the graphical area, and in the Properties view, select the Integration Flow tab page.
13. Enter a description about the integration flow that provides information to other users who will view or
work with the integration flow.
14. Save the changes.
2.3.2 (Optional) Creating a Working Set of Projects
Context
You perform this task to group projects using the Working Sets feature provided by Eclipse.
For example, you can create a Working Set for grouping projects based on customer or you can create each
Working Set for specific integration scenarios.
 Note
The actions available in the context menu of the projects that are added to the Working Set remain as
before.
Procedure
1. In the Project Explorer view of the Integration Designer perspective, select the dropdown icon from the
toolbar of the view.
2. Choose Select Working Set…
3. In the Select Working Set dialog, choose New….
4. In the New Working Set dialog, select Resource and choose Next.
5. Enter a name for the working set.
6. Select a resource from the Working set contents section.
7. Choose Finish.
8. If you want to edit the working set, select the dropdown icon and choose Edit Active Working Set.
9. Select the dropdown icon in the toolbar of the Project Explorer and choose Top Level Elements
Working Sets to display the Working Set and its content in the Project Explorer.

10. Select Top Level Elements Projects to display only the projects belonging to the existing working
sets, .
 Note
If you want to go back to the default Project Explorer view that displays all the projects irrespective of
the Working Sets, select the dropdown icon in the toolbar of the Project Explorer and choose Deselect
Working Set.
2.3.3 Importing SAP NetWeaver PI Objects from On-Premise

Repository
Context
You perform this task to import interfaces and mappings from an On-Premise repository, such as the ES
Repository, into the integration project. In case of mappings, you can import message mappings (.mmap) and
operation mappings (.opmap).
 Restriction
See the table below to know about the list of unsupported functionalities of the mappings being imported:
Unsupported functionalities of imported mappings

Type of Mappings Limitations
Message Mapping User Defined Functions with Channel type parameter
RFC and JDBC lookups used in Mappings
Parameters declared through Parameter section of mapping edi

tor (in ES Repository Builder )
Used Imported Archives
Used Function Libraries
Containing schema from .xml or .zip files
Operation Mapping Operations (source or target) with cardinality '0..unbonded' are

not supported
Operation mappings with cardinality 0..1 are not supported
Operation mapping containing multiple operations are not sup

ported
Since parameters are not supported in Message Mapping, so op

eration mappings with binding are also not supported
Operation Mappings with Java Mappings (Imported Archives,

Java programs) and external programs are not supported

Type of Mappings Limitations
Operation Mappings, with Do Not Resolve XOP Includes, Read

Attachments are not supported
Only synchronous operation mappings with at least one map

ping program present- either request, response or fault, is sup
ported.
If the WSDL is already present, WSDLs are not overwritten
Procedure
1. In the Project Explorer, right-click on an integration project and from the context menu choose Import PI
Object.
2. In the Import PI Object dialog, select ES Repository below the object type you want to import.
For example, if you want to import operation mappings, select ES Repository below Operation Mapping
object type.
3. Choose Next.
4. In the Import Mappings from ES Repository dialog, select one or more objects and choose Finish.
Results
The imported objects are placed under their respective src.main.resources.<object> folder. For
example, check the imported mapping under src.main.resources.mapping and imported interface under
src.main.resources.wsdl.
WSDLs/XSDs corresponding to Message Types and Fault Message Types are placed under
src.main.resources.mapping folder, other interfaces get placed under src.main.resources.wsdl.
The imported operation mapping has the following features:
● If operation mapping contains message mapping, then the message mapping is downloaded as a jar under
src.main.resources.mapping package.
● If the operation mapping contains XSLTs, then the files are downloaded as .xsl under
src.main.resources.mapping.
● Imported source or target WSDLs are not supported in integration flows.

2.3.4 Modifying an Integration Flow Model
Context
You perform this task if you want to modify the existing integration flow model. For example, if the templates
provided by SAP do not exactly match your requirement, you can modify the integration flow created from the
templates while adhering to SAP's modeling constraints.
To add integration flow elements, you can drag the notations for systems, connections, mappings, routers, and
so on, from the palette and drop it at the required location of the integration flow model in the graphical editor.
Alternatively, you can add elements, such as mapping and split, to the integration flow model using the context
menu options available on the connections of the model.
 Note
The integration flow should match the SAP supported scenarios to avoid deployment failure.
 Example
Consider an example which requires you to model an integration flow with multiple pools. The scenario with
multiple pool may involve any of the following:
● Hosting same endpoint with different connectors, such as SFTP and SOAP connector
● Polling content from different servers
● Grouping similar integration logic that uses different interfaces
The list of elements that you require to model a multiple pool integration flow are:
1. One Sender element

2. N Receiver elements
3. N Integration Process pools for each incoming message from the Sender to a Receiver
4. N Message Flows from the Sender to the Start Message element in the Integration Process pool. This
indicates N incoming message.
5. N Message Flows from each End Message element in the Integration Process pool to the corresponding
Receivers. This indicates N outgoing message flows.
6. Finally, Sequence Flows to connect the Start Message and End Message within each pools. This
completes the integration flow modeling.
Procedure
1. Open the <integration flow>.iflw in the Model Configuration editor.

2. To modify the graphical diagram using the notations in the Palette, follow the substeps below:
a. If the Palette pane is hidden in the Model Configuration editor, choose Show Palette arrow at the right
edge of the editor.

b. Choose the required BPMN notation to modify the integration flow model.
3. To modify the graphical diagram using the context menu options, follow the substeps below:
a. In the Model Configuration editor, right-click on the connections within the pool.
b. From the context menu, choose the necessary action to add an element. For example, Add Routing
adds an Router notation to your graphical diagram that can be used either as a receiver router or an
interface router.
c. Save the changes.
2.3.5 Saving Integration Flow as a Template
Prerequisites
You have specified the location path to store the user-defined templates at Windows Preferences SAP
Cloud Platform Integration Personalize .
Context
You perform this task to save an integration flow as a template. The integration flow saved as template retain
the attribute values so that you can reuse the template for similar configuration scenarios.
Procedure
1. In the Project Explorer view, open the <integration flow>.iflw from your project.
2. From the main menu, choose File Save As… .

3. In the Save As Integration Flow Template dialog, enter a name for the template.
4. If you want to retain the externalized parameters in the template then select Retain the externalized
parameter(s) option.
 Note
If the integration flow contains externalized parameters and you do not select this option, the
integration flow gets saved with the most recent values you have assigned to the externalized
parameters.
5. Choose OK.

Results
You can find the new template in the location you have mentioned in the Preferences page. When you create the
integration flow using the template, you can find the saved configurations.
2.3.6 Using Custom Functions in Message Mapping
Prerequisites
Make sure you have created a valid Integration project with Message Mapping associated scripts.
Context
In Message Mapping, you can create your own custom functions by using groovy scripts and use them as
required. You can use custom functions from the function palette for modeling the mapping expressions.
Procedure
1. In the Project explorer view, select src.main.resources.mapping package.
2. In the context menu of src.main.resources.mapping, choose New Other .
The New dialog box appears.
3. Choose Message Mapping Next .
The New Message Mapping dialog box appears.

4. In the General Details section, enter the message mapping name in the Name field.
5. In the Location Details section, select the project name using Browse…
The path of the selected project gets added to the Path field, and the selected message mapping page
opens.
6. In the Signature section of the message mapping, select the Source Element (.xsd) and Target Element
(.xsd) by choosing Add…
7. In the Properties section, double-click the Definition tab to see the message mapping.
The Standard Functions and Custom Functions appear on the function palette of the Properties section.
8. Choose Custom Functions.

 Note
In the Properties section, if you do not find any groovy scripts under Custom Functions in the function
palette, then can add an existing groovy script or create a new groovy script.
9. In the context menu of Custom Functions, choose Add to use and existing groovy script file.
The Add Script dialog box appears.
a. Select a groovy script (.gsh) file, and choose OK.
The selected groovy script along with all the functions that fulfill the message mapping requirements
appear under Custom Functions in the functions palette.
10. In the context menu of Custom Functions, choose Create to create a new groovy script file.
The New Mapping Script dialog box appears.
a. Enter or select the parent folder for the new groovy script file.
b. Enter the name of the new groovy script file in the File name field.
c. Choose Finish.
The new groovy script file appears under Custom Functions in the function palette. You can expand the
new groovy script to see all the functions under it.
In the function palette, you can select any groovy script under Custom functions and you can use it and
customize it according to your requirements.
11. If you want to add a function to the Expression editor, select a function under the groovy script in the
function palette.
12. Drag and drop the function from the groovy script to the text area of the expression editor.
13. You can define your mapping logic by using your custom functions.
14. Choose File Save .
 Note
○ You can validate your mapping and check for errors by viewing the Problems tab, or Console tab, or
Error log tab. If your mapping has any errors, then they are displayed with error markers .
○ In the function palette, if you have used a function from one of your scripts under Custom
Functions, and if that script is removed is from the functions palette, then an error marker is
displayed.
○ You can access the Message Processing logs using
messageLogFactory.getMessageLog(context);. For access specific logs, please refer
Javadocs.
○ When you launch Eclipse, if you do not see your local workspace, choose File Switch
workspace Other... and select the required workspace.

2.3.6.1 Guidelines for Creating Mapping Scripts using
Custom Functions
You can create your own custom functions by using mapping scripts and use them as required. You can use
custom functions from the function palette for modeling the mapping expressions.
The execution mode for functions are supported by two types:
● Single value
● All values of context
Guidelines for Creating Mapping Script for Single Value Type of Execution
If you want to add a mapping script to a Message Mapping function palette, ensure that the following
conditions are fulfilled:
● Make sure that each function has at least one argument, and also make sure that their type is also declared
along with it.
● The supported types for mapping script are int, float, string, or boolean.
● Make sure that the function’s return type is specified and that it can only be a String.
● Functions which you declare as private cannot be seen in the Message Mapping function palette, but it can
be used in other functions internally.
● You can only use the functions of the JAR files supported by the Integration project/package that you are
working on.
 Example
import com.sap.it.api.mapping.*
def String extParam(String P1,String P2,MappingContext context) {
String value1 =
context.getHeader(P1);
String value2 =
context.getProperty(P2);
return value1+value2;
}
Guidelines for Creating Mapping Script for All Values of Context Type of
Execution
For all values of context, ensure that the following conditions are fulfilled:
● Make sure that Method does not return a value

● Method has an argument called Output, to which you can add values.
● Make sure that all the variables except Output and Mapping Context is of type array.

 Example
import com.sap.it.api.mapping.*
def void extParam(String[] P1,String[] P2, Output output, MappingContext
context) {
String value1 =
context.getHeader(P1);
String value2 =
context.getProperty(P2);
output.addValue(value1);
output.addValue(value2);
}
2.4 Developing Value Mappings
Context
Procedure
2.4.1 Creating a Value Mapping Project
Context
You use this task to create a value mapping definition that represent multiple values of an object. For example,
a product in Company A is referred by the first three letters as 'IDE' whereas in Company B it is referred by
product code as ''0100IDE". When Company A sends message to Comapny B, it needs to take care of the
difference in the representations of the same product. So Company A defines an integration flow with a
Mapping element and this Mapping element contains reference to the value mapping definition. You create
such value mapping groups in a Value Mapping project type.
 Note
● Value Mapping Project does not support importing integration content.

Procedure
1. In the main menu, choose File New Project… .
2. In the New Project wizard, select SAP Cloud Platform Integration Integration Project .
3. Choose Next.
4. Enter a project name and select the required Project Type as Value Mapping.
5. Choose Finish.
A new project is available in the Project Explorer view. By default, the new value mapping project is
configured with IFLMAP runtime node type.
2.4.2 Editing the Value Mapping Project
Context
You use this task to define value mapping groups in the value_mapping.xml file that is available under the Value
Mapping project type. You enter the group IDs for each set of agency, schema and a value of the object that
together identify a specific representation of the object.
Procedure
1. Open the value_mapping.xml in the editor and choose the Source tab page editor.
2. Enter the group ID, agency, schema and value as shown in the example below, and save the changes.
<?xml version="1.0" encoding="UTF-8"?>

<vm>
<group id="Vegetable">
<entry>
<agency>UK</agency>
<schema>Food Items</schema>
<value>Aubergine</value>
</entry>
<entry>
<agency>US</agency>
<value>Eggplant</value>
</entry>
</group>
<group id="Herb">
<entry>
<agency>UK</agency>
<value>Coriander</value>
</entry>
<entry>
<agency>US</agency>

<value>Cilantro</value>
</entry>
</group>
</vm>
 Tip
If you want to edit the values, you can switch to the Design tab page editor.
2.4.3 Exporting and Importing Value Mapping Groups
Context
You use this task to either import a .csv file containing value mapping groups into the Value Mapping project
type within your workspace or export the content of value_mapping.xml from your workspace and store it as
a .csv file in your file system. The format of the valid .csv file containing value mapping groups is shown in the
image below:
This task shows the steps for a simple scenario that requires you to export value mappings from your
workspace, and import the same value mappings into a workspace located in another system.

Procedure
1. Export the value mapping groups into your local file system
a. In the Project Explorer, select the value mapping project and choose Export Value Mappings.
b. In the Export Value Mapping Groups wizard, select the required value mapping groups and choose
Next.
c. In the Export groups into a file page, enter a name for the .csv file and browse for a location to store the
file.
d. Choose Finish.
The .csv file containing the exported value mapping groups is available at the selected file location.
 Example
The image below shows an example of a vale mapping group exported into a .csv file.
2. Import the value mapping groups

a. In the Project Explorer, select the value mapping project that you want to import the value mappings to.
b. Choose Import Value Mappings.
c. In the Select a CSV File page, browse for the .csv file.
d. Choose Finish.
 Note
You cannot import value mappings that have been exported from Eclipse. If you do so, then the
existing version of the value mapping files changes.
The .csv file is imported as value_mapping.xml file, and is available under the value mapping project.

 Example
The screenshot below shows how the content of the .csv file (as shown in the previous screenshot)
gets imported as the value_mapping.xml.
2.4.4 Referencing Value Mappings from a Message Mapping
Prerequisites
● You have imported message mapping (.mmap) from an On-Premise repository into the
src.main.resources.mapping folder of the integration project in your workspace.
● You have placed the required source and target WSDLs into the src.main.resources.wsdl folder of the
integration project in your workspace.
● You have added value_mapping.xml under the value mapping project.
Context
You use this procedure to configure the message mapping definition with references to a value mapping. The
value mapping referencing is required when a node value of a message needs to be converted to another
representation. The runtime can evaluate the reference only if you deploy the integration flow project
containing the message mapping, and the associated value mapping project on the same tenant.

Procedure
1. In the Project Explorer view, expand the integration flow project.

2. Under src.main.resources.mapping folder, double-click the <message map>.mmap to open it in the
message mapping editor.
3. In the Message Mapping Overview, under the Signature category, provide the source and target WSDLs.
4. Choose the Definition editor tab page to view the message mapping tree structure.
5. Connect a source node item with one or more target node item to define the mapping.
6. Double-click the function icon on the connection, denoted as fx, to open the mapping relation between the
source and target elements.
For example, see the screenshot below:
7. In the Expression tab page of the Properties view, expand the Function folder.
8. Select the valuemap option under the Conversion package and drop it within the Expression tab page.
9. Connect the required node and the valuemapping function.

10. Double-click the value mapping function and provide details for the value mapping parameters.
2.4.5 Checking the Value Mapping Consistency
Context
You can execute a consistency check to validate if the content of the project is adhering to the required
definition of a value mapping.
The consistency check is executed on the value_mapping.xml file. The inconsistencies can be mainly due to
invalid content entered in the value_mapping.xml such as the value for an agency-schema pair is repeated ,
incorrect tags or missing tags.
Procedure
1. Right-click on the project and choose Execute Checks.

2. Open the Properties view, and view the result of the check.

2.5 Configuring an Integration Flow
Context
You perform this task to configure an integration flow to represent a specific scenario.
You configure the integration flow by adding elements to the graphical model and assigning values to the
elements relevant to the scenario. The basic integration flow requires you to configure the sender and receiver
channels to enable a point-to-point process flow from the sender to a receiver.
The figure below helps you understand how a scenario is configured using an integration flow and is followed by
an explanation:
The scenario involves communication of System A with System P and System Q, where System A sends
messages to System P and System Q.
System A and System P have different communication protocols, whereas, System Q requires additional field
information in the message format sent by System A. In such a case, you do the following configurations in the
integration flow:
● Create an integration flow with a router branching out to two receivers.

● Configure conditions to route messages to the correct receiver.
● Place a mapping component in the communication between System A and System Q

After configuration, the resulting integration flow should be similar to the example shown below:
 Note
You can use an Error End event to throw the exception to default exception handlers in integration process.
2.5.1 Assigning the Sender and Receiver Participants
Context
You perform this task to assign the sender participant and receiver participant to the integration flow. To allow
the sender participant to connect to the tenant, you have to provide either the client certificates or
authenticate using the SDN username and password.
Procedure
1. Assign the Sender Participant

a. In the Model Configuration editor tab page, select the sender.
b. In the Properties page, enter a name for the sender system that may represent a single participant or a
group of logically related participants in a communication.
c. Specify the Authentication Mode.
You have the following options to authenticate the sender.
○ Role-based Authentication
Select this options if you like to configure one of the following use cases:
○ Basic authentication
○ Client certificate authentication with certificate-to-user mapping
○ Client Certificate Authentication

Select this option if you like to configure the use case that the permissions of the sender are to be
checked on the tenant by evaluating the distinguished name (DN) of the client certificate (sent by
the sender).
Choose Add… to browse and add an authorized client certificate or enter the Subject DN and
Issuer DN manually.
d. Save the changes.
2. Assign the Receiver Participant
a. In the Model Configuration editor page, select the receiver.
b. In the Properties page, enter a name for the receiver system.
c. Save the changes.
2.5.2 Defining Channels
Prerequisites
● You have configured connections to an On-Premise repository if you have to obtain interface WSDL from
the repository into this project.
 Note
You can import service interfaces from ES Repository with server version 7.1 onwards. The imported
service interface WSDLs get added to src.main.resources.wsdl.
For more information on setting the connections to the repository, see Setting the Connections to On-
Premise Repository under Configuring the Tool Settings [page 19].
● If you want to use a WSDL available in your local file system, you have copied the file under
src.main.resources.wsdl in your project.
Context
You perform this task to enable communication between the sender and receiver participants by defining
connectors for the sender and receiver channels of the integration flow.
Procedure
1. In the Model Configuration editor page, select the sender or receiver channel (dotted lines at sender and
receiver side).
2. To configure the channel with a saved configuration that is available as a template, choose Load Channel
Template from the context menu of the channel.

3. To specify new configurations, follow the instructions mentioned in the adjacent topic for the required
connector.
 Tip
If you want to reuse the connector configurations for channels that are within or across integration
flows, then select the Copy and Paste option from the context menu of the channel.
4. To save the configurations of the channel as a template, choose Save as Template from the context menu
of the channel.
 Note
When you save the configuration of the channel as a template:

○ The tool stores the template in the workspace as <ElementTemplateName>.fst.
○ The tool saves the parameter key of the externalized parameters and not the values.
2.5.2.1 Configuring a Channel with Mail Adapter
The receiver mail adapter allows you to send encrypted messages by e-mail. The sender mail adapter can
download e-mails and access the e-mail body content as well as attachments.
Context
You configure the mail adapter either as a receiver adapter or as a sender adapter.
You can use the receiver mail adapter to send encrypted messages by e-mail.
You can use the sender mail adapter to do the following:
● Download e-mails from mailboxes using IMAP or POP3 protocol

● Access the content of the e-mail body
● Access e-mail attachments
 Note
The mailbox settings for downloading e-mails can interfere with the settings in the sender mail adapter.
For example: When using POP3 protocol, the post-processing setting Delete/Remove might not work
properly. In this case, try to configure the correct behavior in the mailbox.
 Note
To access the mail attributes (Subject, From, or To), you have to set them manually as Allowed Headers on
the Runtime Configuration tab. This adds them to a whitelist.
 Note
To access an attachment, you have to use Groovy script or JavaScript.

For more information about how to access attachments, see the documentation for the Script step.
 Note
It is not possible to authenticate the sender of an e-mail
Unlike with other adapters, if you are using the sender mail adapter, the Cloud Integration system cannot
authenticate the sender of an e-mail.
Therefore, if someone is sending you malware, for example, it is not possible to identify and block this
sender in the Cloud Integration system.
To minimize this danger, you can use the authentication mechanism of your mailbox. Bear in mind,
however, that this mechanism might not be sufficient to protect against such attacks.
There are three possible threats when processing e-mail content:
● Danger to a receiver system when forwarding e-mail content

E-mails can contain malware, such as viruses or Trojan horses.
These will not affect the Cloud Integration system, but they can cause damage to a receiver system if it
doesn't have sufficient protection strategies.
● Danger to the Cloud Integration system
E-mail content can be designed to affect the processing runtime of a system.
Processing this content overloads the system and prevents requests from being fulfilled (denial of
service).
The Cloud Integration system is then unavailable until the problem is fixed.
● Reliability of data
Sending e-mails is anonymous. It is not possible to verify whether the sender of an e-mail really is who
they claim to be.
Even if your mailbox has an authentication mechanism, this mechanism might not be sufficient.
Therefore, data contained in an e-mail (for example, the amount of an order), is not reliable without
further verification.
 Caution
If you select Run Once option in the Scheduler, you see messages triggered from all the integration flows
with this setting after a software update. After the latest software is installed on a cluster, it is restarted.
You see messages from these integration flows with Run Once setting.
 Restriction
An integration flow you deploy in SAP Cloud Platform Integration deploys in multiple IFLMAP worker nodes.
Polling is triggered from only one of the worker nodes. The message monitoring currently displays the
process status from the worker nodes where the Scheduler is not started. This results in the message
monitor displaying messages with less than a few milliseconds, where the schedule was not triggered.
These entries contain firenow=true in the log. You can ignore these entries.

Procedure
1. In the Model Configuration editor, double-click the receiver channel.

2. In the Adapter Type section of the General tab page, select Mail from the Adapter Type dropdown.
3. If you configure a sender adapter, you can specify the following attributes in the Connection, Processing
and Scheduler tab pages.
Connection
Parameter Description
Address Specifies the host name or address of the IMAP server, for
example, mail.domain.com.
Use one of the following open ports for external mail serv
ers:
○ 143 for IMAP+STARTTLS

○ 993 for IMAPS
○ 110 for POP3+STARTTLS
○ 995 for POP3S
Proxy Type The type of proxy that you are using to connect to the tar
get system.
Select None if you are connecting directly to the email

server.
Select On-Premise if you are connecting to on-premise

system.
For more information, see .
Timeout (in ms) Specifies the network timeout for the connection attempt
to the server. The default value is 30000.
Location ID (only if On-Premise is selected for Proxy Type) To connect to an SAP Cloud Connector instance associ
ated with your account, enter the location ID that you de
fined for this instance in the destination configuration on
the cloud side, or enter ${header.headername} to
dynamically read the value from a header.

Protection Specifies the method to use to establish an encrypted (se

cure) connection.
There are the following options:
○ Off
No encryption is initiated by the client.
○ POP3S (only when transport protocol POP3 has been
selected when creating the channel)
The TCP connection to the server is encrypted. The S
(in POP3S) stands for secure; in technical terms, TLS
encryption is applied in that case.
○ IMAPS (only when transport protocol IMAP4 has
been selected when creating the channel)
(in IMAPS) stands for secure; in technical terms, TLS
○ STARTTTLS Mandatory
If the server supports STARTTLS, the client initiates
encryption using TLS. If the server does not support
this option, the connection stops with an error.
○ STARTTTLS Optional
If the server supports STARTTLS, the client initiates
encryption using TLS. If the server does not support
this option, client and server remain connected but
communicate without encryption.
Using STARTTLS, an existing connection without encryp

tion can be changed to an encrypted one using TLS (with
out the need to establish a new connection).
Authentication Specifies which mechanism is used to protect user name

and password combination.
○ Plain User Name/Password

The user name and password are sent in plain
text.You should only use this option together with SSL
or TLS, as otherwise an attacker could obtain the
password.
○ Encrypted User/Password
The user name and password are hashed before be
ing sent to the server. This authentication mechanism
(CRAM-MD5 and DIGEST-MD5) is secure even with
out encryption.
Credential Name Specifies the name of the User Credentials artifact that
contains user name and password (used to authenticate
at the email account).

Processing
Folder Specify the IMAP folder containing the mails to be read.
(only if as Transport Protocol the option IMAP4 has been

selected)
Selection Specify which mails will be processed (all mails or only un
read ones).
(only if as Transport Protocol the option IMAP4 has been
selected)
Max. Messages per Poll Defines the maximal number of messages that will be read
from the email server in one polling step.
Post-Processing Specify how to handle processed mails on the server.
 Note
If Post-Processing is set to Mark as Read and the poll
strategy is set to poll for all mails (Selection: All), then
already processed mails will be processed again at ev
ery polling interval.
If you want to use this parameter setting, make sure

that your polling interval is sufficiently large, other
wise your process might become inefficient.
Remove Attachments Select this options if attachments should be removed

from the mail prior to polling.
Scheduler
Scheduler Option Field Description
Schedule on Day On Date Specify the date on which you want

the operation to be executed.
(mails are to be polled at a specific
day)
On Time Specify the time at which you want
Every Specify the interval at which you want

Time Zone Select the time zone that you want the
scheduler to use as a reference for the
date and time settings.

Schedule to Recur Daily Specify that the messages are to be

polled daily (either at a specific time
(mails are to be polled periodically)
as defined next to the checkbox On
Time or in a specific time interval as
defined next to the checkbox Every).
Weekly Specify that the messages are to be

polled weekly. Select the checkboxes
to indicate the days of the week on
which you want the operation to be
executed. Also specify the time
(checkbox On Time) or interval
(checkbox Every) for the schedule to
recur.
Monthly Specify that the messages are to be

polled monthly. Select the day of the
month on which you want the opera
tion to be executed. Also specify the
time (checkbox On Time) or interval
(checkbox Every) for the schedule to
recur.


The Run Once option has been removed in the newest version of the adapter. Default values for the interval
under Schedule on Day and Schedule to Recur have been changed so that the scheduler runs every 10
seconds between 00:00 and 24:00.
4. If you configure a receiver adapter, you can specify the following settings in the Connection and Security
tab pages.

Connection
Address Specifies the host name and (optionally) a port number of the SMTP server.
An external mail server can be used.
Use one of the following open ports for external mail servers:
○ 25 and 587 for SMTP+STARTTLS

○ 465 for SMTPS
If you are using GMail Server, make sure that you allow insecure applications (GMail
considers only communication based on OAuth2 as secure) when configuring the
server. You can use port 25 for connections to GMail server.
Timeout (in ms) Specifies the network timeout for the connection attempt to the server.
This is only used for Transmission Control Protocol (TCP), there is no timeout for
SMTP commands.
The default value is 30000. The timeout should be more than 0, but less than five mi
nutes.
Proxy Type The type of proxy that you are using to connect to the target system.
Select Internet if you are connecting to a cloud system.
Select On-Premise if you are connecting to on-premise system.
Location ID (only if On-Premise To connect to a cloud connector instance associated with your account, enter the lo
is selected for Proxy Type) cation ID that you defined for this instance in the destination configuration on the
cloud side, or enter ${header.headername} to dynamically read the value from a
header.
Protection Defines whether encryption is used. The possible values are:

○ STARTTLS Mandatory
If the server supports STARTTLS, the client initiates encryption using TLS. If the
server does not support this option, the connection fails.
○ STARTTLS Optional
If the server supports the STARTTLS command, the connection is upgraded to
Transport Layer Security encryption. This works with the normal port 25.
server does not support this option, client and server remain connected but com
municate without encryption.
○ SMTPS
The TCP connection to the server is encrypted using SSL/TLS. This usually re
quires an SSL proxy on the server side and access to the port it runs on.
○ Off
No encryption is initiated, whether the server requests it or not.
Using STARTTLS, an existing connection without encryption can be changed to an en

crypted one using TLS (without the need to establish a new connection).

Authentication Specifies which mechanism is used to authenticate against the server with a user
name and password combination. Possible values are:
○ None
No authentication is attempted. No credential can be chosen.
○ Plain User Name/Password
The user name and password are sent in plain text. You should only use this op
tion together with SSL or TLS, as otherwise an attacker could obtain the pass
word.
○ Encrypted User/Password
The user name and password are hashed before being sent to the server. This au
thentication mechanism (CRAM-MD5 and DIGEST-MD5) is secure even without
encryption.
Credential Name Specifies the name of a deployed credential to use for authentication.
From E-mail address that the message comes from.
To E-mail address that the message is sent to.
If you want to configure multiple mail receivers, use a comma (,) to separate the ad
dresses.
Example: name1@example.com, name2@example.com,

name3@example.com
Cc Additional e-mail addresses that the e-mail is to be sent to.
These addresses are visible to the receiver.
dresses.

name3@example.com
Bcc Additional e-mail addresses that the e-mail is to be sent to.
These addresses are not visible to the receiver.
dresses.

name3@example.com
Subject Subject of the e-mail message.
Mail Body Specifies the text of an e-mail message.
Body MIME Type Specifies the type of the message body. This type determines how the message is dis
played by different user agents.

Body Encoding Specifies the character encoding (character set) of the message body. The content of
the input message will be converted to this encoding, and any character that is not
available will be replaced with a question mark ('?'). To ensure that data is passed un
modified, select a Unicode encoding, for example, UTF-8.
Name (under Attachments) Specifies the file name of the attachment.
MIME Type (under The Multipurpose Internet Mail Extensions (MIME) type specifies the data format of
Attachments) the e-mail.
You can select from the following MIME types:
○ Text/Plain
○ Text/CSV
○ Text/HTML
○ Application/XML
○ Application/JSON
○ Application/Octet-Stream
Source Specifies the source of the data. This can be either Body, meaning the body of the in
put message, or Header, meaning a header of the input message.
Header Name If the source is Header, this parameter specifies the name of the header that is at
tached.
Add Message Attachments Select this option to add all attachments contained in the message exchange to the e-
mail.
Security
Encryption Type This parameter configures an encryption scheme used for

sending e-mails. The message body and attachments are
encrypted with the selected scheme and can only be de
crypted by the intended recipients.
Content Encryption Algorithm Specifies the symmetric (block) cipher. DESede should
only be chosen if the destination system or mail client
does not support AES.
Secret Key Length Specifies the key size of the previously chosen symmetric
cipher. To increase the security, choose the maximum key
size supported by the destination.
Receiver Public Key Alias Specifies an alias for the public key that is to be used to
encrypt the message. This key has to be part of the tenant
keystore.

 Note
The parameters From, To, Cc, Bcc, Subject, Mail Body as well as the attachment name, can be
For more information about Camel Simple Expressions, see the following: http://camel.apache.org/
simple.html
Related Information

Headers and Exchange Properties [page 7]
Define Script [page 785]
2.5.2.2 Configuring a Channel with IDoc (IDoc SOAP)

Adapter
Context
The IDoc with SOAP message protocol is used when a system needs to exchange IDoc messages with another
system that accepts data over SOAP protocol.
Supported Header (Sender Adapter):
Supported Header (Receiver Adapter):
Procedure
1. If you are configuring the sender channel, ensure the sender authorization certificate is specified by
following the steps:
a. In the Model Configuration editor, select the sender.

b. In the Properties view, check if the certificate is available in the Sender Authorization table, or add a
certificate.
2. In the Model Configuration editor, double-click the sender or receiver channel.
3. Choose the General tab page and enter the details listed below.
4. In the Adapter Type field, browse and select the IDoc adapter and Message Protocol as IDoc SOAP.
5. Choose the Adapter Specific tab page and enter the details as shown in the table below:
Parameters and Values of Sender IDoc (IDoc SOAP) Adapter (Connection Details)
Parameters Description
Address Relative endpoint address on which ESB Bus listens to the incoming requests, for ex
ample, /HCM/GetEmployeeDetails.
URL to WSDL You can download the WSDL by using the Integration Operations user interface (in the
Properties view, Services tab, under the integration flow-specific endpoint). For newly
deployed integration flows, the WSDL that is generated by the download corresponds
to the endpoint configuration in the integration flow.
 Note
As of now this parameter is no longer available.

Authorization Specifies the authorization option for the sender.
You can select one of the following options:

 Note
○ Client Certificate: Sender authorization is checked on the tenant by evaluating
In the following cases cer
the subject/issuer distinguished name (DN) of the certificate (sent together with
tain features might not be
the inbound request). You can use this option together with the following authen
available for your current
tication option: Client-certificate authentication (without certificate-to-user map
integration flow:
ping).
○ A feature for a partic
○ User Role: Sender authorization is checked based on roles defined on the tenant
ular adapter or step
for the user associated with the inbound request. You can use this option to
was released after
gether with the following authentication options:
you created the cor
○ Basic authentication (using the credentials of the user)
responding shape in
The authorizations for the user are checked based on user-to-role assign
your integration flow.
ments defined on the tenant.
○ You are using a prod
○ Client-certificate authentication and certificate-to-user mapping
uct profile other than
The authorizations for the user derived from the certificate-to-user mapping
the one expected.
are checked based on user-to-role assignments defined on the tenant.
More information: Adapter
Depending on your choice, you can also specify one of the following properties:
and Integration Flow Step
Versions [page 406] ○ Client Certificate Authorization
Allows you to select one or more client certificates (based on which the inbound
authorization is checked).
Choose Add to add a new certificate for inbound authorization for the selected
adapter. You can then select a certificate stored locally on your computer. You
can also delete certificates from the list.
For each certificate, the following attributes are displayed: Subject DN (informa
tion used to authorize the sender) and Issuer DN (information about the certifi-
cate authority that issues the certificate).
○ User Role
Allows you to select a role based on which the inbound authorization is checked.
Choose Select to get a list of all available roles.
The role ESBMessaging.send is provided by default. It is a predefined role pro
vided by SAP which authorizes a sender system to process messages on a ten
ant. However, using SAP Cloud Platform Cockpit, you can also define custom
roles for the runtime node as well. When choosing Select, a selection of all cus
tom roles defined that way is offered.
 Note
Note the following:
○ You can also type in a role name. This has the same result as selecting
the role from the value help: If the inbound request is authenticated, de
pends on the correct user-to-role assignment defined in SAP Cloud
Platform Cockpit.
○ When you externalize the User Role, in the integration flow configuration
the value help for roles is offered as well.

○ If you have selected a product profile for SAP Process Orchestation, the
value help will only show the default role ESBMessaging.send.
Parameters and Values for Sender Adapter/Authorization
Section Parameter Description
Connection Authorization Specifies the authorization option for the sender.
○ Client Certificate
 Note
Sender authorization is checked on the tenant by evaluating the sub
In the following ject/issuer distinguished name (DN) of the certificate (sent together
cases certain fea with the inbound request).
tures might not be You can use this option together with the following authentication op
available for your tion: Client-certificate authentication (without certificate-to-user map
current integra ping).
tion flow: ○ User Role
○ A feature for Sender authorization is checked based on roles defined on the tenant
a particular for the user associated with the inbound request.
adapter or You can use this option together with the following authentication op
step was re tions:
leased after ○ Basic authentication (using the credentials of the user)
you created The authorizations for the user are checked based on user-to-role
the corre assignments defined on the tenant.
sponding ○ Client-certificate authentication and certificate-to-user mapping
shape in your The authorizations for the user derived from the certificate-to-
integration user mapping are checked based on user-to-role assignments de
flow. fined on the tenant.
○ You are using
a product
profile other
than the one
expected.
More information:
Adapter and Inte
gration Flow Step
Versions [page
406]
Client Certificate Allows you to select one or more client certificates (based on which the in
Authorization bound authorization is checked).
(only if you have se Choose Add to add a new certificate for inbound authorization for the se
lected Client
lected adapter. You can then select a certificate stored locally on your com
Certificate as
puter. You can also delete certificates from the list.
Authorization)

User Role Allows you to select a role based on which the inbound authorization is
checked.
The role ESBMessaging.send is provided in any case by default. It is a pre

defined role provided by SAP which authorizes a sender system to process
messages on a tenant.
However, you have the option to define custom roles for the runtime node
as well. When choosing Select, a selection of all custom roles defined that
way is offered.
Conditions
Maximum Message Size This parameter allows you to configure a maximum size
for inbound messages (smallest value for a size limit is 1
MB). All inbound messages that exceed the specified size
(per integration flow and on the runtime node where the
integration flow is deployed) are blocked.
To configure the maximum message size, you can specify

the following parameters:
○ Body Size
○ Attachment Size
If a message is rejected because it exceeds the configured

limit, the sender receives an error message.

Parameters and Values of Receiver IDoc (IDoc SOAP) Adapter (Connection Details)
Address Endpoint address on which the ESB Bus posts the outgo
ing message, for example http://<host>:<port>/payment.
You can dynamically configure the address field of the IDoc

SOAP Adapter.
When you specify the address field of the adapter as $

{header.a} or ${property.a}, at runtime the value of header
a or exchange property (as contained in the incoming
message) will be written into the Camel header CamelDes
tinationOverrideUrl and will be used in runtime to send the
message to.
Also in case the CamelDestinationOverrideUrl header has

been set by another process step (for example, a Content
Modifier), its value will be overwritten.
The endpoint URL that is actually used at runtime is dis

played in the message processing log (MPL) in the mes
sage monitoring application (MPL property
RealDestinationUrl). Note that you can manually
configure the endpoint URL using the Address attribute of
the adapter. However, there are several ways to dynami
cally override the value of this attribute (for example, by
using the Camel header CamelHttpUri).

get system:
○ Select Internet if you are connecting to a cloud sys
tem.
○ Select On-Premise if you are connecting to an on-
premise system.
 Note
If you select the On-Premise option, the following
restrictions apply to other parameter values:
○ Do not use an HTTPS address for Address,
as it leads to errors when performing consis
tency checks or during deployment.
○ Do not use Certificate-Based Authentication
as the Authentication Type, as it leads to er
rors when performing consistency checks or
during deployment
 Note
If you select the On-Premise option and use the
SAP Cloud Connector to connect to your on-
premise system, the Address field of the adapter
refers a virtual address which has to be config-
ured in the SAP Cloud Connector settings.
Location ID only in case On-Premise is selected for Proxy To connect to a cloud connector instance associated with
Type. your account, enter the location ID that you defined for
this instance in the destination configuration on the cloud
side. You can also enter ${header.headername} or ${prop
erty.propertyname} to dynamically read the value from a
header or a property.
URL to WSDL URL to the WSDL defining the WS provider endpoint (of
the receiver). You can provide the WSDL by:
○ Directly entering /wsdl/<interfacename>.wsdl where
the WSDL is available in src.main.resources.wsdl.
○ Selecting a source to browse for a WSDL, either from
an On-Premise ES Repository or your local work
space.
 Note

IDoc Content Type Application/x-sap.doc

○ Allows only single IDoc record for each request
○ Enables Exactly-Once processing
○ Enables message sequencing
Text/XML
○ Allows multiple IDoc records for each request
Request Timeout Specifies the time (in milliseconds) that the client will wait
for a response before the connection is being interrupted.
The default value is 60000 milliseconds (1 minute).
Compress Message Enables the WS endpoint to send compressed request

messages to the WS Provider and to indicate the WS Pro
vider that it can handle compressed response messages.
Allow Chunking Used for enabling HTTP chunking of data while sending
messages.
Clean up Request Headers Select this option to clean up the adapter specific- head
ers after the receiver call.

Connect using Basic Authentication Select this option to allow the ESB to connect to the re
ceiver system using the deployed basic authentication cre
dentials. When you select this option, you need to provide
the credential name.
Credential Name: Enter the credential name of the user

name-password pair specified during the deployment of
basic authentication credentials on the cluster.
 Note
You can externalize all attributes related to the config-
uration of the authentication option. This includes the
attributes with which you specify the authentication
option as such (if you either intend to use basic au
thentication , certificate-based authentication or no
authentication), as well as all attributes with which
you specify further security artifacts that are required
for any configurable authentication option (Private
Key Alias or Credential Name).
Apply one of the following two recommendations

when externalizing such attributes.
○ Externalize all attributes related to the configura-

tion of all options (for example, Authentication
Option, Credential Name and Private Key Alias).
○ Externalize only one of the following attributes:
Private Key Alias or Credential Name.
Avoid incomplete externalization such that, for ex

ample, you externalize only the attribute for the
Authentication Option but not the related Credential
Name. In such cases, the integration flow configura-
tion (based on the externalized parameters) cannot
work properly.
The reason for this is the following: When you have ex
ternalized the Authentication Option attribute and only
the Private Key Alias (but no Credential Name), in the
integration flow configuration dialog all authentication
options (Basic, Certificate-Based and None) are se
lectable in a drop-down list. However, when you now
select Basic Authentication from the drop-down list,
no Credential Name can be configured.

Private Key Alias Allows you to enter the private key alias name that gets the
private key from the keystore and authenticates you to the
receiver in an HTTPs communication.
If you have selected the option of Connect using Basic

Authentication, this field is not visible.
You can dynamically configure the Private Key Alias prop

erty by specifying either a header or a property name in
one of the following ways:
$ {header.headername} or $ {property.propertyname}
Please be aware that in some cases this feature can have a

negative impact on performance.

Authentication You can select one of the following authentication meth

ods:
○ Basic
The tenant authenticates itself against the receiver
using user credentials (user name and password).
It is a prerequisite that user credentials are specified
in a Basic Authentication artifact and deployed on the
related tenant.
using a client certificate.
It is a prerequisite that the required key pair is instal
led and added to a keystore. This keystore has to be
deployed on the related tenant. The receiver side has
to be configured appropriately.
○ None
○ Principal Propagation
The tenant authenticates itself against the receiver by
forwarding the principal of the inbound user to the
cloud connector, and from there to the back end of
the relevant on-premise system
 Note
This authentication method can only be used
with the following sender adapters: HTTP, SOAP,
IDoc.
 Note
Please note that the token for principal prop
agation expires after 30 minutes.
If it takes longer than 30 minutes to process

the data between the sender and receiver
channel, the token for principal propagation
expires, which leads to errors in message
processing.
The AS2 adapter also supports this option.
 Note
In the following cases certain features might not
be available for your current integration flow:
○ A feature for a particular adapter or step was
released after you created the corresponding
shape in your integration flow.

○ You are using a product profile other than the

one expected.
More information: Adapter and Integration Flow

Step Versions [page 406]
You can dynamically configure the Credential Name field of

the adapter, by using a Simple Expression (see http://
camel.apache.org/simple.html . For example, you can
dynamically define the Credential Name of the receiver
adapter by referencing a message header $
{header.MyCredentialName} or a message prop
erty ${exchangeProperty.MyCredentialName}.
Results
In the Model Configuration editor, when you place the cursor on the sender or receiver message flows, you can
see the SOAP Address and WSDL information.
2.5.2.3 Configuring a Channel with SOAP (SAP RM)

Adapter
Prerequisites
Context
You perform this task to configure a sender or receiver channel with the SOAP communication protocol, with
SAP RM as the message protocol. SAP RM is a simplified communication protocol for asynchronous Web
service communication that does not require the use of Web Service Reliable Messaging (WS-RM) standards. It
offers a proprietary extension to ensure reliability on the ABAP back-end side of both Web service consumers
and providers. For more information, see http://wiki.scn.sap.com/wiki/display/ABAPConn/Plain+SOAP
You have the option to set SOAP headers using Groovy script (for example, using the Script step).

Procedure
1. Choose the General tab page and enter the details below.
2. In the Adapter Type field, browse and select the SOAP adapter, and SAP RM as the Message Protocol.
3. Choose the Adapter Specific tab page and enter the details as shown in the table below:
 Note
Note regarding WSDL import:
Parameters and Values of Sender SOAP (SAP RM) Adapter - Connection Details
Address Relative endpoint address at which the ESB listens to the incoming requests, for
example, /HCM/GetEmployeeDetails.
URL to WSDL URL to the WSDL defining the WS provider endpoint (of the receiver). You can
specify the WSDL by selecting a source to browse for a WSDL either from an On-
Premise ES Repository or your local workspace.
In the Resources view you can upload an individual WSDL file or an archive file
(file ending with .zip) that contains multiple WSDLs or XSDs or both resources.
For example, you can upload a WSDL which contains an imported XSD referred
by an xsd:import statement. That means, when you like to upload a WSDL
and dependent resources, you need to add the parent file along with its depend
encies in a single archive (.zip file).
You can download the WSDL by using the Integration Operations user interface
(in the Properties view, Services tab, under the integration flow-specific end
point). For newly deployed integration flows, the WSDL that is generated by the
download corresponds to the endpoint configuration in the integration flow.
The WSDL download does not work for WSDLs with external references because
these WSDLs cannot be parsed.

Processing Settings This feature corresponds to an older version of this adapter. The reason why it is
shown can be that you either have selected a certain product profile other than
SAP Cloud Platform Integration or (in case you have selected SAP Cloud Plat
form Integration product profile) that you continue editing an integration flow
which exists already for a certain time. If you still like to use this feature, you have
the following options:
○ Standard: Message is executed with WS standard processing mechanism.

Errors are not returned to the consumer.
○ Robust: WSDL provider invokes service synchronously and the processing
errors are returned to the consumer.
When you use the up-to-date adapter version, the processing setting Robust is
implicit activated.


 Note
○ Client Certificate: Sender authorization is checked on the tenant by evaluat
In the following cases certain
ing the subject/issuer distinguished name (DN) of the certificate (sent to
features might not be available
gether with the inbound request). You can use this option together with the
for your current integration
following authentication option: Client-certificate authentication (without
flow:
certificate-to-user mapping).
○ A feature for a particular
○ User Role: Sender authorization is checked based on roles defined on the
adapter or step was re
tenant for the user associated with the inbound request. You can use this op
leased after you created
tion together with the following authentication options:
the corresponding shape
in your integration flow.
The authorizations for the user are checked based on user-to-role as
○ You are using a product
signments defined on the tenant.
profile other than the one
expected.
The authorizations for the user derived from the certificate-to-user
More information: Adapter and mapping are checked based on user-to-role assignments defined on the
Integration Flow Step Versions tenant.
[page 406]
○ Client Certificate Authorization

Allows you to select one or more client certificates (based on which the in
bound authorization is checked).
Choose Add to add a new certificate for inbound authorization for the se
For each certificate, the following attributes are displayed: Subject DN (infor
mation used to authorize the sender) and Issuer DN (information about the
certificate authority that issues the certificate).
○ User Role
Allows you to select a role based on which the inbound authorization is
checked.
The role ESBMessaging.send is provided by default. It is a predefined role
provided by SAP which authorizes a sender system to process messages on
a tenant. However, using SAP Cloud Platform Cockpit, you can also define
custom roles for the runtime node as well. When choosing Select, a selection
of all custom roles defined that way is offered.
 Note
Note the following:
○ You can also type in a role name. This has the same result as select
ing the role from the value help: If the inbound request is authenti
cated, depends on the correct user-to-role assignment defined in
SAP Cloud Platform Cockpit.

○ When you externalize the User Role, in the integration flow configu-
ration the value help for roles is offered as well.
○ If you have selected a product profile for SAP Process Orchestation,
the value help will only show the default role ESBMessaging.send.
 Note
step was re tions:
○ You are using
a product
profile other
than the one
expected.
More information:
Adapter and Inte
gration Flow Step
Versions [page
406]
lected Client
Certificate as
Authorization)

checked.

way is offered.
 Note
For Exactly-Once handling, the sender SOAP (SAP RM) adapter save the protocol-specific message ID
in the header SapMessageIdEx. If this header is set, SOAP (SAP RM) receiver use the content of this
header as the message ID for outbound communication. Usually, this is the desired behavior and
enables the receiver to identify any duplicates. However, if the sender system is also the receiver
system, or several variants of the message are sent to the same system (for example, in an external call
or multicast), the receiver system will incorrectly identify these messages as duplicates. In this case,
the header SapMessageIdEx must be deleted (for example, using a script) or overwritten with a new
generated message ID. This deactivates Exactly-Once processing (that is, duplicates are no longer
recognized by the protocol).
If you want to set SOAP headers via the Camel header, the following table shows which Camel header
corresponds to which SOAP header.
Which Camel header corresponds to which SOAP header
SOAP (SAP RM) Header Camel Header
MessageId SapMessageIdEx und SapMessageId
QualityOfService SapPlainSoapQoS
ExactlyOnce ExactlyOnce
ExactlyOnceInOrder ExactlyOnceInOrder
QueueId SapPlainSoapQueueId

Conditions

○ Body Size
○ Attachment Size

 Note
Parameters and Values of Receiver SOAP (SAP RM) Adapter - Connection Details
Address Endpoint address at which the ESB posts the outgoing message, for example http://
<host>:<port>/payment.
You can dynamically configure the address field of the SOAP (SAP RM) Adapter.
When you specify the address field of the adapter as ${header.a} or ${property.a}, at
runtime the value of header a or exchange property (as contained in the incoming mes
sage) will be written into the Camel header CamelDestinationOverrideUrl and will be
used in runtime to send the message to.
Also in case the CamelDestinationOverrideUrl header has been set by another process
step (for example, a Content Modifier), its value will be overwritten.
The endpoint URL that is actually used at runtime is displayed in the message process
ing log (MPL) in the message monitoring application (MPL property
RealDestinationUrl). Note that you can manually configure the endpoint URL
using the Address attribute of the adapter. However, there are several ways to dynami
cally override the value of this attribute (for example, by using the Camel header
CamelHttpUri).

Location ID only in case On- To connect to a cloud connector instance associated with your account, enter the loca
Premise is selected for Proxy tion ID that you defined for this instance in the destination configuration on the cloud
Type. side. You can also enter ${header.headername} or ${property.propertyname} to dy
namically read the value from a header or a property.
URL to WSDL URL to the WSDL defining the WS provider endpoint (of the receiver). You can specify
the WSDL by selecting a source to browse for a WSDL either from an On-Premise ES
Repository or your local workspace.
In the Resources view you can upload an individual WSDL file or an archive file (file end
ing with .zip) that contains multiple WSDLs or XSDs or both resources. For example,
you can upload a WSDL which contains an imported XSD referred by an xsd:import
statement. That means, when you like to upload a WSDL and dependent resources,
you need to add the parent file along with its dependencies in a single archive (.zip
file).
Service Name of the selected service contained in the referenced WSDL.
Endpoint Name of the selected port of a selected service (that you provide in the Service Name
field) contained in the referenced WSDL.
 Note
Using the same port names across receivers is not supported. To use the same
port names, you need to create a copy of the WSDL and use it.
Operation Name Name of the operation of the selected service (that you provide in the Service Name
Private Key Alias Allows you to enter the private key alias name that gets the private key from the key
store and authenticates you to the receiver in an HTTPS communication.
 Note
If you have selected the Connect using Basic Authentication option, this field is not
visible.
You can dynamically configure the Private Key Alias property by specifying either a
header or a property name in one of the following ways:
Please be aware that in some cases this feature can have a negative impact on per
formance.
Compress Message Enables the WS endpoint to send compressed request messages to the WS provider
and to indicate to the WS provider that it can handle compressed response messages.
Allow Chunking Used for enabling HTTP chunking of data while sending messages.
Clean Up Request Headers Select this option to clean up the adapter specific-headers after the receiver call.

Request Timeout Specifies the time (in milliseconds) that the client will wait for a response before the
connection is interrupted.
Note that the timeout setting has no influence on the Transmission Control Protocol
(TCP) timeout when the receiver or any additional component interconnected between
the Cloud Integration tenant and the receiver have a lower timeout. For example, con
sider that you have configured a receiver channel timeout of 10 minutes and there is
another component involved with a timeout of 5 minutes. In case, nothing is transfer
red for a certain time, the connection will be closed after the 5th minute. In HTTP com
munication spanning multiple components (for example, from a sender, through the
load balancer, to a Cloud Integration tenant, and from there to a receiver) the actual
timeout period is influenced by each of the timeout settings of the individual compo
nents that are interconnected between sender and receiver (precisely spoken, of those
components that can control the TCP session). The component or device with the low
est number set for the idle session timeout will determine the timer that will be used.

Authentication You can select one of the following authentication methods:
○ Basic
The tenant authenticates itself against the receiver using user credentials (user
name and password).
It is a prerequisite that user credentials are specified in a Basic Authentication ar
tifact and deployed on the related tenant.
The tenant authenticates itself against the receiver using a client certificate.
It is a prerequisite that the required key pair is installed and added to a keystore.
This keystore has to be deployed on the related tenant. The receiver side has to be
configured appropriately.
○ None
The tenant authenticates itself against the receiver by forwarding the principal of
the inbound user to the cloud connector, and from there to the back end of the rel
evant on-premise system
 Note
This authentication method can only be used with the following sender adapt
ers: HTTP, AS2, SOAP, IDOC
 Note
Please note that the token for principal propagation expires after 30 minutes.
If it takes longer than 30 minutes to process the data between the sender and
receiver channel, the token for principal propagation expires, which leads to
errors in message processing.
 Note
In the following cases certain features might not be available for your current
integration flow:
○ A feature for a particular adapter or step was released after you created
the corresponding shape in your integration flow.
○ You are using a product profile other than the one expected.
More information: Adapter and Integration Flow Step Versions [page 406]
You can dynamically configure the Credential Name field of the adapter, by using a Sim
ple Expression (see http://camel.apache.org/simple.html . For example, you can dy
namically define the Credential Name of the receiver adapter by referencing a message
header ${header.MyCredentialName} or a message property $
{exchangeProperty.MyCredentialName}.
4. Save the configurations in both the sender and receiver channel editors.

Results
In the Model Configuration editor, when you place the cursor on the sender or receiver message flows, you can
see the SOAP Address and WSDL information.
Related Information
https://wiki.scn.sap.com/wiki/display/ABAPConn/Plain+SOAP?original_fqdn=wiki.sdn.sap.com
2.5.2.4 Configuring a Channel with SOAP (SOAP 1.x)

Adapter
Prerequisites
Since the adapter implements web services security, you have ensured that the related certificates are
deployed in the truststore.
Context
SOAP (SOAP 1.x) allows you to deploy web services that support SOAP 1.1 and SOAP 1.2. SOAP 1.x provides you
a framework for binding SOAP to underlying protocols. The binding specification in the WSDL defines the
message format and protocol details for a web service.

Procedure
1. If you are configuring the sender channel, ensure the sender authorization certificate is specified by
following the steps below:
a. In the Model Configuration editor, select the sender.
b. In the Properties view, check if the certificate is available in the Sender Authorization table, else add a
certificate.
2. In the Model Configuration editor, double-click the sender or receiver channel.
3. In the Adapter Type section of the General tab page, select SOAP from the Adapter Type dropdown and
select SOAP 1.x as the message protocol.
4. Choose the Adapter-Specific tab page and enter the details as shown in the table below. The attributes
depend on whether you configure a sender or a receiver channel::
 Note
Connection
Address Relative endpoint address on which the integration runtime expects incoming re
quests, for example, "/HCM/GetEmployeeDetails".
Service Definition Specifies the source of the service definition.
You can select the following options:

○ Manual: You configure the service behavior manually by the parameters shown
below.
○ WSDL: The service behavior is defined via WSDL configuration.
Use WS-Addressing Select this option to accept addressing information from message information head
ers during runtime.
(only if Service Definition:
Manual is selected)

Message Exchange Pattern Specifies the kind of messages that are processed by the adapter.
○ Request-Reply: The adapter processes both request and response.
(only if Service
Definition:Manual is selected
 Tip
When using this option, the response code can accidently be overwritten by
a called receiver. For example, when your integration flow contains an SOAP
sender adapter (with a Request-Reply pattern) and an HTTP receiver
adapter, and the HTTP receiver returns an HTTP response code 202 (as it
has accepted the call), the SOAP sender adapter returns in the reply also
HTTP response code 202 instead of 200 (OK). To overcome this situation,
you have to remove the header CamelHttpResponseCode before the
message reply is sent back to the sender.
○ One-Way
(only if as Service Definition
the option WSDL is selected)
In the Resources view you can upload an individual WSDL file or an archive file (file
ending with .zip) that contains multiple WSDLs or XSDs or both resources. For ex
ample, you can upload a WSDL which contains an imported XSD referred by an
xsd:import statement. That means, when you like to upload a WSDL and depend
ent resources, you need to add the parent file along with its dependencies in a single
archive (.zip file).
 Note
○ 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: <namespace>:<service_name>
Example: p1:MyService
○ Do not use WSDLs with blanks.
We recommend that you don't use blanks in WSDL names or directories, as
this can lead to runtime issues.
You can download the WSDL by using the Integration Operations user interface (in the
For more information on how to work with WSDL resources, refer to the following blog:
Cloud Integration – Usage of WSDLs in the SOAP Adapter
Service Name of the selected service contained in the referenced WSDL

field) contained in the referenced WSDL
(only if Service Definition: The
adapter only: WSDL is se
lected)
Processing Settings ○ WS Standard: Message is executed with WS standard processing mechanism. Er
rors are not returned to the consumer.
(only if one of the following op ○ Robust: WSDL provider invokes service synchronously and the processing errors
tions is selected: are returned to the consumer.
○ Service Definition: WSDL
○ Service Definition: Manual
andMessage Exchange
Pattern: One-Way


ping).

○ User Role
 Note
Note the following:
Platform Cockpit.

WS-Security
WS-Security Configuration Specifies the way how WS-Security settings are to be configured.
○ Via Manual Configuration in Channel
The security settings are manually to be configured (see below listed attributes).
○ None
No WS-Security is applied for message exchange.
If you select this option, no further WS-Security-relevant settings can be applied.
WS-Security Type Specifies the combination of message protection methods that are to be applied.
○ Verify Message and Sign Response (default)
A signed payload is expected by the tenant, and the signature has to be verified.
○ Verify and Decrypt Message and Sign and Encrypt Response
A signed and encrypted payload is expected by the tenant. The signature has to
be verified and the payload has to be decrypted.
Private Key Alias for Response Specify an alias for the private key that is to be used to sign the response message.
Signing
You can also enter ${header.headername} or ${property.propertyname} to read the
name dynamically from a header or exchange property.
The tenant private key is used to sign the response message (that is sent to the WS
consumer). The tenant private key has to be part of the tenant keystore.
Public Key Alias for Response Specify an alias for the public key that is to be used to encrypt the response mes
Encryption sage..
(only in case Verify and The sender (WS consumer) public key is used to sign the response message (that is
Decrypt Message is selected sent to the WS consumer). This key has to be part of the tenant keystore.
for WS-Security Type)
Save Incoming Signed Select this option if the incoming signed (and encrypted) message is to be stored.
Message
Signature Algorithm Specify a signature algorithm to be applied when signing the response message.
Possible values:
○ SHA1 (default value)

○ SHA256
○ SHA512
Signing Order only in case Via Defines the order in which signing and encryption must be applied. There are the fol
Manuel Configuration in lowing options:
Channel is selected for WS- ○ Sign Before Encryption (default)
Security Configuration. ○ Encrypt before Signing

Check Time Stamp Select this option, if the sender (WS consumer) sends a time stamp along with the
message.
In case a request-response pattern is configured, a time stamp is added to the re

sponse message.
Sender is Basic Security Profile As default setting, select this option.

Compliant
This option should be selected in case the sender system supports a dedicated secur
ity level which is described by the Basic Security Profile (as assumed to be the case
for most systems). Only in case the sender system does not support this security pro
file, deselect this option.
Algorithm Suite Assertion Specifies which algorithms are to be used by the WS consumer.
Initiator Token ○ Include Strategy

Preset value Always to Recipient ensures that the WS consumer sends the certifi-
cate along with the message.
○ X509 Token Assertion
Defines the format of the certificate being sent by the WS consumer along with
the message.
Recipient Token Include Strategy
Value Always to Initiator adds the certificate to the response message.

 Note
step was re tions:
○ You are using
a product
profile other
than the one
expected.
More information:
Adapter and Inte
gration Flow Step
Versions [page
406]
lected Client
Certificate as
Authorization)

checked.

way is offered.
Conditions

○ Body Size
○ Attachment Size


 Note
Connection
Address Endpoint address on which the ESB Bus posts the outgoing message, for example
http://<host>:<port>/payment.
You can dynamically configure the address field of the SOAP (SOAP 1.x) Adapter.
runtime the value of header a or exchange property (as contained in the incoming
message) will be written into the Camel header CamelDestinationOverrideUrl and will
be used in runtime to send the message to.
The endpoint URL that is actually used at runtime is displayed in the message proc
essing log (MPL) in the message monitoring application (MPL property
CamelDestinationOverrideUrl).
Proxy Type The type of proxy that you are using to connect to the target system:
○ Select Internet if you are connecting to a cloud system.
○ Select On-Premise if you are connecting to an on-premise system.
 Note
If you select the On-Premise option, the following restrictions apply to other
parameter values:
○ Do not use an HTTPS address for Address, as it leads to errors when per
forming consistency checks or during deployment.
○ Do not use Certificate-Based Authentication as the Authentication Type,
as it leads to errors when performing consistency checks or during de
ployment
 Note
If you select the On-Premise option and use the SAP Cloud Connector to con
nect to your on-premise system, the Address field of the adapter refers a vir
tual address which has to be configured in the SAP Cloud Connector settings.
Location ID only in case On- To connect to a cloud connector instance associated with your account, enter the lo
Premise is selected for Proxy cation ID that you defined for this instance in the destination configuration on the
Type. cloud side. You can also enter ${header.headername} or ${property.propertyname} to
dynamically read the value from a header or a property.

In the Resources view you can upload an individual WSDL file or an archive file (file
ending with .zip) that contains multiple WSDLs or XSDs or both resources. For ex
ample, you can upload a WSDL which contains an imported XSD referred by an
xsd:import statement. That means, when you like to upload a WSDL and depend
ent resources, you need to add the parent file along with its dependencies in a single
archive (.zip file).
 Note
○ If you specify a WSDL, you also have to specify the name of the selected serv
ice and the name of the port selected for this service. These fields must have
a namespace prefix.
○ Do not use WSDLs with blanks:
It is not recommended to use blanks in WSDL names or directories. This
could lead to runtime issues.
Service Name Name of the selected service contained in the referenced WSDL
Port Name Name of the selected port of a selected service (that you provide in the Service Name
field) contained in the referenced WSDL .
Same port names across receivers is not supported. To use the same port names, you
need to create a copy of the WSDL and use it.
Operation Name Name of the operation of selected service (that you provide in the Service Name field)
contained in the referenced WSDL.
Connect Without Client This feature corresponds to the Authentication setting None and is shown when you
Authentication use an older version of this adapter. The reason why it is shown can be that you either
have selected a certain product profile other than SAP Cloud Platform Integration or
(in case you have selected SAP Cloud Platform Integration product profile) that you
continue editing an integration flow which exists already for a certain time.
Select this option to connect the tenant anonymously to the receiver system.
Select this option if your server allows connections without authentication at the
transport level.

Connect Using Basic This feature corresponds to Authentication setting Basic and is shown when you use
Authentication an older version of this adapter. The reason why it is shown can be that you either have
selected a certain product profile other than SAP Cloud Platform Integration or (in
case you have selected SAP Cloud Platform Integration product profile) that you con
tinue editing an integration flow which exists already for a certain time.
Select this option to allow the tenant to connect to the receiver system using the de
ployed basic authentication credentials.
Credential Name: Enter the credential name of the username-password pair specified
during the deployment of basic authentication credentials on the cluster.

○ Basic
name and password).
When you have selected Basic authentication option, you can enter a Credential
Name.
This keystore has to be deployed on the related tenant. The receiver side has to
be configured appropriately.
○ None
the inbound user to the cloud connector, and from there to the back end of the
relevant on-premise system
 Note
This authentication method can only be used with the following sender
adapters: HTTP, SOAP, IDoc.
 Note
You can dynamically configure the Credential Name field of the adapter, by using a
Simple Expression (see http://camel.apache.org/simple.html . For example, you
can dynamically define the Credential Name of the receiver adapter by referencing a
message header ${header.MyCredentialName} or a message property $

If you have selected the option of Connect using Basic Authentication, this field is not
visible.
formance.
 Note
You can externalize all attributes related to the configuration of the authentication
option. This includes the attributes with which you specify the authentication op
tion as such (if you either intend to use basic authentication , certificate-based au
thentication or no authentication), as well as all attributes with which you specify
further security artifacts that are required for any configurable authentication op
tion (Private Key Alias or Credential Name).
Apply one of the following two recommendations when externalizing such attrib
utes.
○ Externalize all attributes related to the configuration of all options (for exam
ple, Authentication Option, Credential Name and Private Key Alias).
○ Externalize only one of the following attributes: Private Key Alias or Credential
Name.
Avoid incomplete externalization such that, for example, you externalize only the
attribute for the Authentication Option but not the related Credential Name. In
such cases, the integration flow configuration (based on the externalized parame
ters) cannot work properly.
The reason for this is the following: When you have externalized the Authentication
Option attribute and only the Private Key Alias (but no Credential Name), in the in
tegration flow configuration dialog all authentication options (Basic, Certificate-
Based and None) are selectable in a drop-down list. However, when you now select
Basic Authentication from the drop-down list, no Credential Name can be config-
ured.

Timeout (in ms) Specifies the time (in milliseconds) that the client will wait for a response before the
connection is being interrupted.
(TCP) timeout when the receiver or any additional component interconnected be
tween the Cloud Integration tenant and the receiver have a lower timeout. For exam
ple, consider that you have configured a receiver channel timeout of 10 minutes and
there is another component involved with a timeout of 5 minutes. In case, nothing is
transferred for a certain time, the connection will be closed after the 5th minute. In
HTTP communication spanning multiple components (for example, from a sender,
through the load balancer, to a Cloud Integration tenant, and from there to a receiver)
the actual timeout period is influenced by each of the timeout settings of the individual
components that are interconnected between sender and receiver (precisely spoken,
of those components that can control the TCP session). The component or device
with the lowest number set for the idle session timeout will determine the timer that
will be used.
Compress Message Enables the WS endpoint to send compressed request messages to the WS Provider
and to indicate the WS Provider that it can handle compressed response messages.
Clean Up Request Headers Select this option to clean up the adapter-specific headers after the receiver call.
WS-Security
○ Via Manual Configuration in Channel
○ Based on Policies in WSDL
The security settings are specified as part of the receiver endpoint (within the
endpoint WSDL) in elements as defined by the WS-Policy standard.
○ None

Username Token Specifies the way how Username Token is to be configured. Select this option to au
thenticate at message level based on a user ID and a password (transported within a
SOAP message).
When as WS-Security Configuration you have selected Via Manual Configuration in

Channel, you have the following options:
○ Plain Text Password

The Password is transferred in plain text (https encrypted).
○ Hashed Password
Cryptographic hash function is applied for password.
○ None
No User Name Token is applied.
If you have selected the option Plain Text Password or Hashed Password, enter the cre
dential name, that is, the alias that was assigned to the authorized user and password
during tenant deployment.
 Note
It depends on additional adapter settings how the token is treated during runtime
(in particular, with regard to whether the token will be encrypted or not).
When the security settings are defined by the endpoint WSDL (when for WS-
Security Configuration you have selected Based on Policies in WSDL), the token is
treated according to what is defined within the WSDL.
When the security settings are defined manually (when for WS-Security
Configuration you have selected Via Manual Configuration in Channel), it depends
on the selected WS-Security Type how the token is treated:
○ Sign Message selected: The token is not encrypted.

○ Sign and Encrypt Message selected: The token is encrypted.
Credential Name Alias that was assigned to the authorized user and password during tenant deploy
ment
(only configurable when for
WS-Security Configuration the
option Based on Policies in
WSDL is selected)
WS-Security Type Specifies the combination of message protection methods that are to be applied.
○ Sign Message
Tenant signs the payload.
option Via Manual
○ Sign and Encrypt Message
Configuration in Channel is se
Tenant signs and encrypts the payload
lected)
○ None
No WS-Security Type is applied.

Private Key Alias for Signing Specify an alias for the tenant private key that is to be used to sign the message.
You can also enter ${header.headername} or ${property.propertyname} to read the

name dynamically from a header or exchange property.
The tenant private key is used to sign the request message (that is sent to the WS pro
vider (receiver)). The tenant private key has to be part of the tenant keystore.
Public Key Alias for Encryption Specify an alias for the public key that is to be used to encrypt the message.
(only configurable when for The receiver (WS provider) public key is used to encrypt the request message (that is
WS-Security Type the option sent to the receiver). This key has to be part of the tenant keystore.
Sign and Encrypt Message is
selected)
Signature Algorithm Specify a signature algorithm to be applied when signing the request message.
Possible values:
○ SHA1 (default value)

○ SHA256
○ SHA512
Set Time Stamp Select this option to send a time stamp along with the message.
In case a request-response pattern is configured, a time stamp is expected in the re

sponse message.
Receiver is Basic Security Leave this option selected if the receiver system complies with the basic security pro
Profile Compliant file (as assumed to be the case for most systems). Deselect this option if the receiver
system does not support this security profile.
Layout ○ Strict
Items are added to the security header following numbered layout rules according
to a general principle of 'declare before use'.
○ Lax
option Via Manual
Items are added to the security header in any order that conforms to WSS: SOAP
Message Security
lected)
Algorithm Suite Assertion Specifies which algorithms are used by the WS consumer

option Via Manual
lected)
Initiator Token These entries define policies for the WS consumer.

○ Include Strategy
Value Always to Recipient ensures that the WS consumer sends the certificate
along with the message.
option Via Manual
Defines the format of the certificate being sent by the WS consumer along with
lected)
the message.

Recipient Token These entries define policies for the WS consumer.

○ Include Strategy
option Via Manual
Configuration in Channel is se Defines the format of the certificate being sent by the WS consumer along with the
lected) message.
5. Save the configurations.

In the Model Configuration editor, when you place the cursor on the sender or receiver message flows, you
can see the SOAP Address and WSDL information.
Related Information
WS-Security Configuration for the Sender SOAP 1.x Adapter [page 90]
WS-Security Configuration for the Receiver SOAP 1.x Adapter [page 91]
https://blogs.sap.com/2018/01/25/cloud-integration-soap-adapter-web-service-security/
https://blogs.sap.com/2018/01/24/cloud-integration-wss-between-cloud-integration-and-sap-po-soap-
adapter/
2.5.2.4.1 WS-Security Configuration for the Sender SOAP

1.x Adapter
You use a sender channel to configure how inbound messages are to be treated at the tenant’s side of the
communication.
With regard to WS-Security in a sender channel, you specify the following:
● How the tenant verifies the payload of an incoming message (signed by the sender)
● How the tenant decrypts the payload of an incoming message (encrypted by the sender)

The following figure illustrates the setup of components:
The sender SOAP 1.x adapter allows the following combination of message-level security options:
● Verifying a payload
● Verifying and decrypting a payload
For a detailed description of the SOAP adapter WS-Security parameters, check out Configure SOAP (SOAP 1.x)
Sender Adapter [page 519] (under WS-Security).
2.5.2.4.2 WS-Security Configuration for the Receiver SOAP

1.x Adapter
With a receiver channel you configure the outbound communication at the tenant’s side of the communication.
With regard to WS-Security in a sender channel you specify the following:
● How the tenant signs the payload of a message (to be verified by the receiver)
● How the tenant encrypts the payload of a message (to be decrypted by the receiver)
The following figure illustrates the setup of components.

The receiver SOAP 1.x adapter allows to configure the following combinations of message security methods:
● Signing a payload
● Signing and encrypting a payload
Configuration Options for WS-Security
Signing and encryption (and verifying and decryption) is based on a specific set up of keys as illustrated in the
figures. Moreover, for the message exchange, specific communication rules apply as been agreed between the
administrators of the Web service client and Web service provider (for example, if certificates are to be sent
with the message).
There are two options how these security and communication settings can be specified:
● Based on Policies in WSDL

Using this option, the security settings are specified as part of the receiver endpoint (within the endpoint
WSDL) in elements as defined by the WS-Policy standard.
That way you can specify, for example, within the WSDL that certificates for message level security are sent
with the message.
For more information on the WS-Policy standard, see: http://docs.oasis-open.org/ws-sx/ws-
securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.html .
● Manual Configuration in Channel
Using this option, you specify the required settings in the channel.
The naming of the available attributes corresponds to the terminology used in the WS-Policy specification.
If you use manual configuration, a sub set of the options as defined by the standard is supported. For more
information on the standard, see http://www.w3.org/TR/ws-policy/ and http://docs.oasis-open.org/ws-
sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.pdf .
Receiver Adapter [page 531] (under WS-Security).

2.5.2.5 Configuring a Channel with AS2 Adapter
Prerequisites
You (tenant admin) can provision message broker to AS2 adapter scenarios only if you have Enterprise Edition
license.
 Note
You have to set up a cluster for the usage of message broker. For more details refer .
 Caution
Do not use this adapter type together with Data Store Operations steps, Aggregator steps, or global
variables, as this can cause issues related to transactional behavior.
Context
You use this procedure to configure a sender and receiver channel of an integration flow with the AS2 adapter.
You can use this adapter and exchange business-specific documents with your partner through AS2 protocol.
You can use this adapter to encrypt/decrypt, compress/decompress and sign/verify the documents.
 Restriction
Procedure
1. Double-click the channel that you want to configure on the Model Configuration tab page.
2. Select the General tab page.
3. Choose Browse in the Adapter Type screen area.
4. Select AS2 in the Choose Adapter window and choose OK.
5. If you configure the sender channel, choose AS2 or AS2 MDN under Message Protocol field else for receiver
channel choose AS2.

 Note
○ If you are configuring the sender channel to receive AS2 message then you can choose AS2
message protocol.
○ If you are configuring the sender channel to receive asynchronous AS2 MDN, then you can choose
AS2 MDN message protocol.
○ If you want to call as2 sender channel, then for as2 sender channel the pattern should be http://
<host>:<port>/as2/as2 and for as2 mdn sender channel the pattern should be http://
<host>:<port>/as2/mdn .
○ To analyze a troubleshooting scenario better, it is recommended to mention the name of the AS2
sender channel. Because a part of the JMS queue name contains the AS2 sender channel name.
6. Choose the Processing tab under Adapter-Specific tab page and enter the details.
Fields Description
Message ID Left Part Specify left side of AS2 message ID. Regular expression or
'.*' is allowed.
Message ID Right Part Specify right side of AS2 message ID. Regular expression
or '.*' is allowed.
Partner AS2 ID Specify partner's AS2 ID. Regular expression or '.*' is al
lowed.
Own AS2 ID Specify own AS2 ID. Regular expression or '.*' is allowed.
Message Subject Specify AS2 message subject. Regular expression or '.*' is

allowed.
Number of Concurrent Processes The number provided determines the processes that are
running in parallel for each worker node and it must be
less than 99. The value depends on the number of worker
nodes, the number of queues on the tenant, and the in
coming load.
Authorization Specify the autorization type to be User Role or Client

Certificate. By default, the authorization type is Role
Based.
For more details, please refer to .
For more details, please refer to .
AS2 Sender Adapter with Role Based Authentication only,

support Certificate to User Mapping and hence call from
AS2 partner should be sent using Client Certificate Au
thentication.
User Role (For sender only) Provide a role as defined in the tenant system, to check in
bound sender authorization.

Fields Description
If a role is not defined, then default role

ESBMessaging.send is used. It authorizes the sender
system to process messages on a tenant.
File name (For receiver only) Specify AS2 filename. If no filename is specified, default
filename will be set to <Own AS2 ID>_File. Use of simple
expression, ${header.<header-name>} or ${prop
erty.<property-name>}, is allowed.
Own E-mail address (For receiver only) Specify own email ID. Use of simple expression, $
{header.<header-name>} or ${property.<property-
name>}, is allowed.
Content Type (For receiver only) Specify content type of the outgoing message. For e.g. ap
plication/edi-x12. Use of simple expression, $
name>}, is allowed.
You can also set value of this attribute dynamically using

header AS2_outbound_content_type.
 Note
If header value is set, it takes precedence over actual
value configured in the channel.
Custom Headers Pattern (For receiver only) Specify regular expression to pick message headers and
add them as AS2 custom headers.
For example, if you want to pick all EDI headers starting

with the name EDI, then you can specify the expression as
EDI.*
Content Transfer Encoding (For receiver only) Specify AS2 message encoding type.
 Note
○ You should ensure that the combination of Message ID Left Part, Message ID Right Part, Partner
AS2 ID, Own AS2 ID and Message Subject parameters, is unique across all AS2 sender channels.
○ If you use regular expression for the above mentioned AS2 sender parameters, then you must
ensure that the regular expression configuration is unique across the endpoints.
○ The runtime identifies relevant channel and integration flow for the incoming AS2 sender message,
based on the above mentioned parameters.
○ AS2 adapter now supports Camel Attachments that contains headers. From the message payload,
the AS2 adapter preserves and reads the corresponding header values that are part of the
attachment.
7. Choose the Security tab under Adapter-Specific tab page and enter the details.

Field Description
Message Security Ensures that the message is compressed or encoded.
Decrypt Message (For sender only) Ensures that the message is decrypted.

header AS2_inbound_decrypt_message .
The valid values are:

○ true
○ false
 Note
Private Key Alias (For sender only) If you select Decrypt Message, then this field is enabled.
Specify private key alias to Decrypt AS2 Message.
Verify Signature (For sender only) Ensures that the signature is verified.

header AS2_inbound_verify_signature.
Public Key Alias (For sender only) If you select Verify Signature of Message, then this field is
enabled. Specify public key alias to verify signature of AS2
Message.
Compress Message (For receiver only) Ensures that the outgoing message is compressed.

header AS2_outbound_compress_message .

○ true
○ false
 Note
Sign Message (For receiver only) Ensures that the outgoing AS2 Message is signed.

header AS2_outbound_sign_message .

○ true
○ false
 Note

Field Description
Algorithm (For receiver only) If you select Sign Message, then this field is enabled. Se
lect AS2 Message signing algorithm.

header AS2_outbound_signing_algorithm.

○ SHA1
○ SHA224
○ SHA256
○ SHA384
○ SHA512
○ MD5
 Note
Private Key Alias (For receiver only) If you select Sign Message, then this field is enabled.
Specify private key alias to Sign AS2 Message. Use of sim
ple expression, ${header.<header-name>} or ${prop
erty.<property-name>}, is allowed.
Encrypt Message (For receiver only) Ensures that the message is encrypted.

header AS2_outbound_encrypt_message .

○ true
○ false
 Note
Algorithm (For receiver only) If you select Encrypt Message, then this field is enabled.
Select AS2 Message encryption algorithm.

header AS2_outbound_encryption_algorithm.

○ 3DES
○ AES128
○ AES192
○ AES256
○ RC2

Field Description
 Note
Public Key Alias (For receiver only) If you select Encrypt Message, then this field is enabled.
Specify public key alias to encrypt AS2 Message. Use of
simple expression, ${header.<header-name>} or ${prop
erty.<property-name>}, is allowed. The header or property
can conatin public key alias or X509 certificate.
Key Length (For receiver only) If you select Encrypt Message and choose RC2 for Algo
rithm field then this field is enabled. Specify public key
length.

header
AS2_outbound_encryption_key_length.
 Note
8. Choose the MDN tab under Adapter-Specific tab page and enter the details.
Fields Description
Private Key Alias for Signature (For sender only) Specify private key alias to sign the MDN on partner's re
quest.
Signature Encoding (For sender only) Select MDN signature encoding type.
Authentication for Asynchronous MDN (For sender Select authentication type for asynchronous MDN.
only)
Timeout (For sender only) Specify the time in milliseconds during which client has to
accept asynchronous MDN, before the timeout occurs.
Enter the value '0' if you want the client to wait indefinitely.
Number of Concurrent Processes (For Sender Only) The number provided determines the processes that are
running in parallel for each worker node and it must be
less than 99. The value depends on the number of worker
nodes, the number of queues on the tenant, and the in
coming load.
Type (For receiver only) Enable this option to request partner to send Message In
tegrity Check(MIC) in AS2 MDN.

header AS2_outbound_mdn_type.

Fields Description
 Note
Target URL (For receiver only) If you choose asynchronous MDN type, then this field is
enabled. Specify URL on which AS2 MDN will be received
from partner. Use of simple expression, $
name>}, is allowed.
 Note
If the recipient url belongs to AS2 adapter of SAP

Cloud Platform Integration, then for AS2 mdn sender
channel the pattern should be http://
Request Signing (For receiver only) If you choose asynchronous or synchronous MDN type,
then this field is enabled. You can enable this option to re
quest partner to sign AS2 MDN.

header AS2_outbound_mdn_request_signing.
Algorithm (For receiver only) If you enable Request Signing option, then this field is ena
bled.

header
AS2_outbound_mdn_signing_algorithm.
 Note
Verify Signature (For receiver only) If you choose synchronous MDN type, then this field is en
abled. You can enable this option to verify signature of
AS2 MDN.
Public Key Alias (For receiver only) If you select Verify Signature, then this field is enabled.
Specify public key alias to verify MDN signature. Use of
simple expression, ${header.<header-name>} or ${prop
erty.<property-name>}, is allowed. The header or property
can conatin public key alias or X509 certificate.

Fields Description
Request MIC (For receiver only) If you want to requst for integrity check then you can ena
ble this option.

header AS2_outbound_mdn_request_mic
Verify MIC (For receiver only) If you choose synchronous MDN type, then this field is en
abled. You can enable this option to verify MIC of AS2
MDN.
If you enable request MIC option the you can also enable
this option if you wnat to verify integrity of the message.

header AS2_outbound_mdn_verify_mic.
 Note
○ You can configure AS2 receiver channel for Request-Reply integration flow element. If you request
for synchronous MDN, then the adapter sets received MDN response as message payload.
○ If you request for synchronous MDN in receiver channel, you may receive positive or negative MDN.
In both the cases, status of message in Message Monitoring tab is COMPLETED. You can process
the MDN message on your own and take the required action for positive or negative MDN, post AS2
call for synchronous MDN.
○ In MDN message, positive MDN is represented as shown below:
 Sample Code

<MDNDeliveryReport>
................
<MDNDispositionNotification>
...............
<Disposition>
<DispositionMode ActionMode="automatic-action" SendingMode="MDN-
sent-automatically"/>
<DispositionType>processed</DispositionType>
</Disposition>
<ReceivedContentMIC mic="9I2W0DSFpQOVRH75/1sLGpWAgtc="
alg="sha1"></ReceivedContentMIC>
</MDNDispositionNotification>
</MDNDeliveryReport>
○ In MDN message, negative MDN is represented as shown below:
 Sample Code

<MDNDeliveryReport>
................
................
<Disposition>

<DispositionModifier>error</DispositionModifier></Disposition>
<Error>insufficient-message-security</Error>
</Disposition>
<ReceivedContentMIC mic="9I2W0DSFpQOVRH75/1sLGpWAgtc="
alg="sha1"></ReceivedContentMIC>
○ If MDN signature validation fails or incorrect message integrity check (MIC) is received, then in that
case, status of message is FAILED.
9. Choose the Retry and enter the retry handling details.
Retry Interval (in min) Enter a value for the amount of time to wait before retry
ing message delivery.
Exponential Backoff Enter a value to double the retry interval after each unsuc
cessful retry.
Maximum Retry Interval (in min) Enter a value for the maximum amount of time to wait be
fore retrying message delivery.
Dead-Letter Queue Select this option to place the message in the dead-letter
queue if it cannot be processed after two retries.
In such cases, a lock entry is created which you can view

and release in the Message Monitoring application under
Managing Locks.
10. Choose the Connection tab under Adapter-Specific tab page for AS2 receiver channel and enter the details.
Fields Description
Recipient URL (For reciever only) Specify partner's AS2 URL. Use of simple expression, $
name>}, is allowed.
 Note
If the recipient url belongs to as2 adapter of SAP

Cloud Platform Integration, then for as2 sender chan
nel the pattern should be http://
<host>:<port>/as2/as2 and for as2 mdn
sender channel the pattern should be http://

Fields Description
URL Paramters Pattern (For receiver only) Specify regular expression to pick message headers and
add them as AS2 URL parameters.
For example, if you want to pick all EDI headers starting

with the name EDI, then you can specify the expression as
EDI.*
Authentication Type (For receiver only) Specify the authetication type for invoking recipient URL.
Credential Name (For receiver only) If you select basic authetication, then this field is enabled.
Private Key Alias (For receiver only) If you select client certificate authetication, then this field
is enabled.
Timeout (in ms) (For receiver only) Specify the time in milliseconds during which client has to
accept AS2 message, before the timeout occurs.
11. Save the configuration of the channel editors.
 Note
○ AS2 sender passes the following headers to the integration flow for message processing:
○ AS2PartnerID
○ AS2OwnID
○ AS2MessageSubject
○ AS2Filename
○ AS2MessageID
○ AS2PartnerEmail
○ AS2MessageContentType
○ AS2 MDN sender passes the following headers to the integration flow for message processing:
○ AS2PartnerID
○ AS2OwnID
○ AS2MessageID
○ AS2OriginalMessageID
○ You can configure AS2 sender to retry messages, if any error occurs during integration flow
processing.
○ You can use the parameterRetry Interval (in m) to enter a value for the amount of time to wait
before retrying message delivery.
The AS2 sender adapter writes messages into a JMS queue prior to further processing it. The
retry handling (in case a Retry Interval (in m) is configured) is analog to as described for the
JMS adapter (see Related Link below).
○ You can use the parameterExponential Backoff to double the retry interval after each
unsuccessful retry.
○ You can use the parameter Maximum Retry Interval (in m) to set an upper limit on the value to
avoid an endless increase of the retry interval. The default value is 60 minutes.

○ Based on different AS2 adapter scenarios, use the following attributes to refer the values that are
associated with MPL:
○ AS2 receiver adapter attributes:
○ AdapterId
○ adapterMessageId
○ SAP_MplCorrelationId
○ ReceiverAS2Name
○ MessageDirection
○ MDNType
○ MPL ID
○ MDNRequested
○ SenderAS2Name
○ AS2MessageID
For example:
{AdapterId=AS2 Receiver,
adapterMessageId=<c31b34955-d799-4219-9f1c-5dd3a044e4@HCIAS2>,
SAP_MplCorrelationId=AFgsEou7oJYm7AqQHsV2lM2T6iTT,
ReceiverAS2Name=ASCDSSCSAS2,
MessageDirection=Outbound,
MDNType=Receiving,
MPL ID=AFgsEosepT9fR54od_XHp6yWu6Gs,
MDNRequested=Asynchronous,
SenderAS2Name=HCIAS2,
AS2MessageID=<c31b5955-d799-4219-9f1c-5dde63a044e4@HCIAS2>}
○ AS2 MDN sender adapter attributes:

○ AdapterId
○ MDNStatus
○ Message Id
○ ErrorDescription
For example:
{AdapterId=AS2 MDN Sender,

adapterMessageId=<qwesdt_123sourcewe_AS2-1479283341389-0@endionAS2_HC
IAS2>,
MDNStatus=error,
Message Id=<c31b53255-d799-4219-9f1c-5e63a044e4@HCIAS2>,
ErrorDescription=insufficient-message-security}
○ AS2 sender adapter attributes:

○ AdapterId
○ ReceiverAS2Name
○ MDNType
○ MDNStatus
○ MPL ID

○ MDNRequested
○ SenderAS2Name
○ AS2MessageID
For example:
{AdapterId=AS2 Sender,
adapterMessageId=<define _AS2-147665710-6@endionAS2_HCIAS2>,
ReceiverAS2Name=HCIAS2,
MessageDirection=Inbound,
MDNType=Sending,
MDNStatus=Success,
MPL ID=AFgsPspcD-eYhvHFdfOZYKydBmzw,
MDNRequested=Synchronous,
SenderAS2Name=endionAS2,
AS2MessageID=<define _AS2-147665710-6@endionAS2_HCIAS2>}

○ AdapterId
○ ReceiverAS2Name
○ MDNType
○ MDNStatus
○ MPL ID
○ MDNRequested
○ SenderAS2Name
○ AS2MessageID
For example:
adapterMessageId=<define_AS2-14798922282-7@gibsonAS2_HCIAS2>,
MDNType=Sending,
MDNStatus=Success,
MPL ID=AFgsQ0_3KdRx-UiOjcwGruy6Xw4V,
SenderAS2Name= gibsonAS2,
AS2MessageID=<define _AS2-14798922282-7@ gibsonAS2_HCIAS2>}
Related Information
Configuring a Channel with JMS Adapter [page 176]

2.5.2.6 Configuring a Channel with HTTP Receiver Adapter
The HTTP adapter allows you to configure an outbound HTTP connection from SAP Cloud Platform Integration
to a receiver.
Prerequisites
If you like to send strings with the HTTP receiver adapter which contain non-ASCII characters (for example,
German umlaut or cyrillic characters), make sure that you do the following (using a Content Modifier):
Use the Content-Type header to specify the media type that the receiver can expect (for example, text/
plain for unformatted text).
Set the value of the CamelCharsetName property or header to the desired character set (for example, UTF-8).
 Note
If you don't specify the character set in the proposed way, the HTTP adapter sends ASCII strings. This will
lead to errors when your data contains non-ASCII characters.
Context
The HTTP adapter supports only HTTP 1.1. This means that the target system must support chunked transfer
encoding and may not rely on the existence of the HTTP Content-Length header.
You can configure a channel with the HTTP adapter type for outbound calls (from the tenant toIf you want to
dynamically override the configuration of the adapter, you can set the following headers before calling the
HTTP adapter:
● CamelHttpUri
● CamelHttpQuery
● Content-Type
The content type is composed of two parts: a type and a subtype.For example, image/jpeg (where image
is the type and jpeg is the subtype).
Examples:
format

more information, see http://www.iana.org/assignments/media-types/media-types.xhtml .
 Note
If transferring text/* content types, you can also specify the character encoding in the HTTP header
using the charset parameter.
Text data in string format is converted using UTF-8 by default during message processing. If you want
to override this behavior, you can use the Content Modifier step and specify the CamelCharsetName
Exchange property. To avoid encoding issues when using this feature together with the HTTP adapter,
If you use a Content Modifier step and you want to send iso-8859-1-encoded data to a receiver, make
sure that you specify the CamelCharsetName Exchange property (either header or property) as
iso-8859-1. For the Content-Type HTTP header, use text/plain; charset=iso-8859-1.
HTTP content encoding that indicates the encoding used during message transport (for example, gzip for
GZIP file compression).
This information is used by the receiver to retrieve the media type that is referenced by the content-type
header.
more information, see:http://www.iana.org/assignments/http-parameters/http-
Procedure
 Note
1. Choose the General tab page.

2. Select HTTP from the Adapter Type dropdown list.You can configure a channel with the HTTP adapter type
for outbound calls (from the tenant to a receiver system).
3. Choose the Adapter Specific tab page and enter the values for the available parameters. The table below
gives a description of the fields and the possible values you can enter:

Field Name and Description for HTTP Adapter
Field Description
Address URL of the target system that you are connecting to, for
example, https://mysystem.com
Note that the authentication method Client

Certificate requires the HTTPS protocol. For Basic
authentication it is strongly recommended that you
use the HTTPS protocol.
If you have selected one of these authentication methods,

you therefore have to enter an https URL.
You can also specify HTTP parameters in the URL. How

ever, if you select the HTTP method POST, parameters are
usually sent in the body. You therefore get a warning mes
sage if you configure this parameter-value combination.
The following URL parameters are currently not allowed

for technical reasons:
○ throwExceptionOnFailure
○ bridgeEndpoint
○ transferException
○ client
○ clientConfig
○ binding
○ sslContextParameters
○ bufferSize
You can dynamically configure the Address field of the

HTTP adapter.
When you specify the Address field of the HTTP adapter

as ${header.a}, at runtime the value of header a (as
contained in the incoming message) will be written into
the Camel header CamelHttpUri.
Also in case the CamelHttpUri header has been set by

another process step (for example, a Content Modifier),
its value will be overwritten.


Field Description
Query Query string that you want to send with the HTTP request
Query strings must not be entered in the Address field.
This parameter can be externalized.
You can dynamically configure the Query field of the HTTP

adapter.
When you specify the Query field of the HTTP adapter as

${header.a}, at runtime the value of header a (as con
tained in the incoming message) will be written into the
Camel header CamelHttpQuery.
 Note
If you want to send parameters in the query string of
the HTTP adapter, these parameters must be coded
in a URL-compatible way. Individual parameter-value
pairs must be separated with an ”&” and there must
be an “=” between the name of a parameter and its
value.
Example 1)
parameter1=123, parameter2=abc
You must specify the following in the query field: pa

rameter1=123&parameter2=abc
Example 2)
Manufacturer = Mars Inc. Product = M&M
You must specify the following in the query field: Man

ufacturer =Mars+Inc.&Product=M%26M

Field Description
get system:
tem.
premise system.
 Note
during deployment
 Note

Field Description
Method Action that the HTTP request should perform
○ POST
Requests that the receiver accepts the data enclosed
in the request body.
○ Delete
Requests that the origin server delete the resource
identified by the Request-URl
○ Dynamic
The method is determined dynamically by reading a
value from a message header or property such as $
{header.abc} or ${property.abc} during runtime.
○ GET
Sends a GET request to the receiver.
○ HEAD
Sends a HEAD request which is similar to a GET re
quest but does not return a message body.
○ PUT
Updates or creates the enclosed data on the receiver
side.
○ TRACE
Sends a TRACE request to the receiver that sends
back the message to the caller.
Send Body Select this checkbox if you want to send the body of the
message with the request. For methods GET, DELETE, and
This field is enabled only if you select for Method the op
HEAD, the body is not sent by default because some HTTP
tion GET, DELETE, HEAD or "Dynamic".
servers do not support this function.
Expression The expression field allows you to enter a simple expres

sion that specifies the HTTP method for the HTTP call .
For example, you can define that the method is deter
tion Dynamic.
mined dynamically by reading a value from a message
header or property such as ${header.abc} or ${prop
erty.abc}. If the header or property does not exist or its
value is empty, the POST method is used by default.

Field Description
Authentication Defines how the tenant (as the HTTP client) will authenti
cate itself against the receiver.
You can select one of the following authentication meth

ods:
○ None
○ Basic
related tenant.
 Note

○ Externalize all attributes related to the configu-

ration of all options (for example, Authentication

work properly.

Field Description
ternalized the Authentication Option attribute and
only the Private Key Alias (but no Credential Name), in
the integration flow configuration dialog all authenti
cation options (Basic, Certificate-Based and None)
are selectable in a drop-down list. However, when you
now select Basic Authentication from the drop-down
list, no Credential Name can be configured.
 Note
IDOC
 Note
Please note that the token for principal propaga
tion expires after 30 minutes.
If it takes longer than 30 minutes to process the

data between the sender and receiver channel,
the token for principal propagation expires, which
leads to errors in message processing.
For special use cases, this authentication method can

also be used with the AS2 adapter.
 Note
released after you created the correspond
ing shape in your integration flow.
○ You are using a product profile other than
the one expected.


Field Description
Credential Name Identifies the User Credential artifact that contains the
credentials (user name and password).
 Note
You can dynamically configure the Credential Name prop
This field is enabled only if you select for erty by specifying either a header or a parameter name in
Authentication the option Basic. one of the following ways: ${header.headername}
or ${parameter.parametername}. As an example,
you can use a Script step before the adapter where you
look-up the User Credentials and enter the base64-en
coded values for user and password into the header
Authorization. The HTTP adapter will then use this
header in the HTTP request.
Although you can configure this feature, it is not sup

ported when using the corresponding integration content
with the SAP Process Orchestration (SAP PO) runtime in
releases lower than SAP PO 7.5 SP5.
Private Key Alias Enter the private key alias that enables the system to fetch
the private key from keystore for authentication.
 Note
 Restriction
This option is enabled only if you select client certifi-
The values true and false are not supported for
cate authentication.
this field.

Field Description
Timeout (in ms) Maximum time that the tenant waits for a response before
terminating message processing
Note that the timeout setting has no influence on the

Transmission Control Protocol (TCP) timeout when the re
ceiver or any additional component interconnected be
tween the Cloud Integration tenant and the receiver have a
lower timeout. For example, consider that you have config-
ured a receiver channel timeout of 10 minutes and there is
another component involved with a timeout of 5 minutes.
In case, nothing is transferred for a certain time, the con
nection will be closed after the 5th minute. In HTTP com
munication spanning multiple components (for example,
from a sender, through the load balancer, to a Cloud Inte
gration tenant, and from there to a receiver) the actual
timeout period is influenced by each of the timeout set
tings of the individual components that are intercon
nected between sender and receiver (precisely spoken, of
those components that can control the TCP session). The
component or device with the lowest number set for the
idle session timeout will determine the timer that will be
used.
4. Save the configuration in the receiver channel editor.
Related Information

Script Example for Exception Handling in HTTP Receiver [page 259]

2.5.2.7 Configuring a Channel with HTTPS Sender Adapter
The HTTPS sender adapter allows you to accept incoming http request on a specific address.
Context
Supported Header:
Supported Header:
The following HTTP request headers for the sample HTTP endpoint https://
test.bsn.neo.ondemand.com/http/hello?abcd=1234 are added to exchange headers for further
processing in integration flow:
● CamelHttpUrl
● CamelHttpQuery
● CamelHttpMethod
DELETE, and so on.
Procedure
1. Double-click the sender channel that you want to configure on the Model Configuration tab page.
2. Choose the General tab page.
3. Select HTTPS from the Adapter Type dropdown list.
4. Choose the Adapter Specific tab page.
5. Choose the Connection tab page and specify the following attributes.

Parameters of the HTTPS Sender Adapter
Address Enter the URL of the HTTP system to connect to.
 Note
○ Use the following pattern: http://
<host>:<port>/http . This should be ap
pended by the unique address apecified in the
channel.
○ The field value supports these characters ~, -, . ,
$ and * .
○ The Address field should start with '/ ' and can
contain alphanumeric values, '_' and '/ '. For ex
ample a valid address is /test/123.
○ In the example mentioned above, you can use ~
only for the address part which succeeds /test/
○ You can use $ only at the beginning of the ad
dress after /.
○ You can use* only at the extreme end of the ad
dress and no characters are allowed after *. A *
can only be preceded with /.
○ You cannot begin address with., - or ~ . Alphanu
meric value or _ must succeed these characters.
○ If you are using /*, it implies that uri containing
the prefix preceding the /* is supported. For ex
ample. if the address is /Customer/* then uris
supported are http://<host>:<port>/http/
Customer/<Any-url>.
○ Uris are case insensitive. So, http://
<host>:<port>/http/test and http://
<host>:<port>/http/Test is treated as same.

○ Client Certificate: Sender authorization is checked on

the tenant by evaluating the subject/issuer distin
guished name (DN) of the certificate (sent together
with the inbound request). You can use this option to
gether with the following authentication option: Cli
ent-certificate authentication (without certificate-to-
user mapping).
○ User Role: Sender authorization is checked based on
roles defined on the tenant for the user associated
with the inbound request. You can use this option to
○ Basic authentication (using the credentials of the
user)
The authorizations for the user are checked
based on user-to-role assignments defined on
the tenant.
○ Client-certificate authentication and certificate-
to-user mapping
The authorizations for the user derived from the
certificate-to-user mapping are checked based
on user-to-role assignments defined on the ten
ant.
Depending on your choice, you can also specify one of the

following properties:

Allows you to select one or more client certificates
(based on which the inbound authorization is
checked).
Choose Add to add a new certificate for inbound au
thorization for the selected adapter. You can then se
lect a certificate stored locally on your computer. You
For each certificate, the following attributes are dis
played: Subject DN (information used to authorize
the sender) and Issuer DN (information about the cer
tificate authority that issues the certificate).
○ User Role
Allows you to enter a role based on which the inbound
authorization is checked.
The role ESBMessaging.send is provided by default. It
is a predefined role provided by SAP which authorizes
a sender system to process messages on a tenant.

CSRF Protected This option prevents Cross-Site Request Forgery (CSRF),

which is a malicious online attack. Such attacks exposes
user content without their authorization.
 Note
Include X-CSRF-Token in the HTTP header field for all
modifying requests and these requests are validated
during runtime. If the validation fails then the server
returns “HTTP 403 Forbidden” status code.
6. Save the configuration in the sender channel editor.
 Note
○ Additional incoming request headers and URL parameters can be added to exchange headers for
further processing in integration flow. You must define these headers and paramters in Allowed
Headers list at integration flow level.
○ Once the integration flow processing completes, the HTTPS sender adapter returns header and
body to end user and sets the response code. You can use Content Modifier element to send back
specific http response and customize the response.
○ The sample integration flow is as shown below:
○ Only Basic Authentication is supported for the http calls and the ESBMessaging.Send role must be
assigned to the user.
○ Address URLs for http endpoints across integration flow must be unique. If it is not unique then the
integration flow does not start.
○ Adapter returns the following HTTP response code:
○ 200 - Processing is successful
○ 503 - Service is not available
○ 500 - Exception during integration flow processing
Also, you can set the header CamelHttpResponseCode to customize the response code.
○ You can invoke the HTTP endpoints using the syntax <Base URI>/http/<Value of address field>.
You can get Base URI value from Services tab in Properties view of a worker node.
Atleast one integration flow with SOAP endpoint must be deployed to view details in Services tab.
○ You should useScript element to customise which headers can be sent in response to the HTTP
call. It is a recommendation that you must remove internal headers and sent back only required
headers.
○ If an exception occurs during the HTTPS call, it is thrown back with a message and MPL ID
explaining the exception, rather than displaying the stack trace.

2.5.2.8 Configuring a Channel with SFTP Adapter
The SFTP adapter uses the SSH protocol to transfer files.
Context
Unlike the standard FTP, the SFTP adapter uses a certificate and keystore to authenticate the file transfer. The
SFTP connector achieves secure transfer by encrypting sensitive information before transmitting it on the
network.
 Note
The clock icon on a message flow indicates polling of messages at regular intervals.
If you want to dynamically override the configuration of the adapter, you can set the following header before
calling the SFTP adapter:
● CamelFileName
The following examples show the header CamelFileName, read via XPath from the payload, or set using an
expression:
Example of Header
Name Type Data Type Value
CamelFileName xpath java.lang.String /p:<XYZ>MessageBulk/

<XYZ>Message/FileName/
text()
CamelFileName expression java.lang.String <myapplication>/

template/out/output$
{date:now:yyyyMMddHHmm
 Note
ss}.xml
Be aware of the following
behavior if you have con
figured the file name dy
namically: If you have se
lected the Append
Timestamp option, the
timestamp overrides the
file name defined dy
namically via the header
(CamelFileName).
SAP Cloud Platform Integration for processes currently supports the following ciphers for SSH (SFTP)
communication: blowfish-cbc,3des-cbc,aes128-cbc,aes192-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr,
3des-ctr,arcfour,arcfour128,arcfour256.

 Caution
The ciphers listed above can change in the future. New ciphers can be added and existing ones can be
removed in case of security weaknesses. In such cases, you will have to change the ciphers on the SFTP
server and reconfigure the integration flows that contain SFTP adapter. SAP will inform customers, if
necessary.
 Caution
You see messages from these integration flows with Run Once setting.
Related Information
Configuring a Channel with SFTP Sender Adapter [page 120]

Configuring a Channel with SFTP Receiver Adapter [page 131]
2.5.2.8.1 Configuring a Channel with SFTP Sender Adapter
You can use the SFTP sender adapter to transfer files from an SFTP server to the tenant using the SSH
protocol.
Context
How the Sender SFTP Adapter Works

If you have configured a sender SFTP adapter, message processing is performed as follows at runtime: The
tenant sends a request to an SFTP server (think of this as the sender system), but the data flow is in the
opposite direction, from the SFTP server to the tenant. In other words, the tenant reads files from the SFTP
server (a process that is also referred to as polling).
SFTP Sender Adapter: Tenant reads files from SFTP server
 Restriction

Procedure
1. Select the integration flow you want to configure and choose Edit.
2. Choose the communication channel you want to configure.
To configure a sender channel, click on a connection between a sender and the Integration Process
component.
3. In General tab page, provide channel name and description in the relevant fields if required.
4. Choose Adapter Specific tab page and provide values in fields based on description in table.
On the Source tab of the sender channel, specify the following attributes.
Field Description
Directory Use the relative path to read the file from a directory, for example, <dir>/<subdir>.

Field Description
File Name Name of the file to be read.
 Note
If you do not enter a file name and the parameter remains blank, all the files in
the specified directory are read.
 Note
Usage of file name pattern:
Expressions, such as ab*, a.*, *a*, ?b, and so on, are supported.
The expression * replaces no character or an arbitrary number of characters.
The expression ? replaces exactly one arbitrary character.
Examples:
If you specify file*.txt as the File Name, the following files are polled by
the adapter: file1.txt, file2.txt, as well as file.txt and
file1234.txt, and so on.
If you specify file?.txt as the File Name, the following files are polled by
the adapter: file1.txt, file2.txt, and so on, but not the files
file.txt or file1234.txt.
Although you can configure this feature, it is not supported when using the cor
responding integration content with the SAP Process Orchestration (SAP PO)
runtime in releases lower than SAP PO 7.5 SP5.
 Caution
Files with file names longer than 100 characters will be processed with the fol
lowing limitations:
○ If two files with names longer than 100 characters are available for proc
essing, only one of these files will be processed at a time. This means that
both files will be processed, but not in parallel. This is also the case if two
runtime nodes are available. If the node fails multiple times while process
ing a file with a file name longer than 100 characters, none of the files
sharing the first 100 characters with that file can be executed without
manual intervention from the administrator.
○ The option Keep File and Mark as Processed in Idempotent Repository (for
sender channels under Processing) will not work for these files.
Address Host name or IP address of the SFTP server and an optional port, for example,
wdfd00213123:22.

Field Description
Select None if you are connecting directly to the SFTP server.
For more information on how to use the On-Premise option to connect to an on-
premise SFTP server, check out the SAP Community blog Cloud Integration – How
to Connect to an On-Premise sftp server via Cloud Connector .
Location ID To connect to an SAP Cloud Connector instance associated with your account, en
(only if On-Premise is selected for ter the location ID that you defined for this instance in the destination configuration
Proxy Type on the cloud side.
Authentication Authentication option for the connection to the SFTP server.
You have the following options:
○ User Name/Password
SFTP server authenticates the calling component based on the user name and
password. To make this configuration setting work, you need to define the user
name and password in a User Credential artifact and deploy the artifact on the
tenant.
○ Public Key
SFTP server authenticates the calling component based on a public key.
Credential Name Name of the User Credential artifact that contains the user name and password.
(Only available if you have se

lected User Name/Password for
Authentication)
User Name ID of the user performing the file transfer.
(Only available if you have se Make sure that the user name contains no other characters than A-z, 0-9, _ (un
lected Public Key for derscore), - (hyphen), / (slash), ? (question mark), @ (at), ! (exclamation mark),
Authentication) $ (dollar sign ), ' (apostrophe), (, ) (brackets), * (asterisk), + (plus sign), ,
(comma), ; (semicolon), = (equality sign), . (dot), or ~ (tilde). Otherwise, an at
tempt for anonymous login is made which results in an error.
Timeout (in ms) Maximum time to wait for the SFTP server to be contacted while establishing con
nection or performing a read operation.
Default value: 10000 ms
The timeout should be more than 0, but less than five minutes.
Maximum Reconnect Attempts Maximum number of attempts allowed to reconnect to the SFTP server.
Default value: 3
Use 0 to disable this behavior.

Field Description
Reconnect Delay (in ms) How long the system waits before attempting to reconnect to the SFTP server.
Default Value: 1000ms
Automatically Disconnect Disconnect from the SFTP server after each message processing.
The following figure illustrates how the properties configured for Authentication are used.
When as Authentication the option User Name/Password is chosen, user name and password are
determined by a User Credentials artifact (which is specified in the SFTP adapter). On the SFTP server, the
user is authenticated by the password.
When as Authentication the option Public Key is chosen, the user is specified in the SFTP adapter. On the
SFTP server, the user is authenticated by the public key associated with the user.
5. Choose Processing tab page.

Fields and Descriptions for SFTP Adapter Sender Channel
Field Description
Read Lock Strategy Prevents files that are in the process of being written from
being read from the SFTP server. The endpoint waits until
it has an exclusive read lock on a file before reading it.
Select one of the following options based on the capabili

ties of the SFTP server:
○ None: Does not use a read lock, which means that the
endpoint can immediately read the file. None is the
simplest option if the SFTP server guarantees that a
file only becomes visible on the server once it is com
pletely written.
○ Rename: Renames the file before reading. The Re
name option allows clients to rename files on the
SFTP server.
○ Content Change: Monitors changes in the file length/
modification timestamp to determine if the write op
eration on the file is complete and the file is ready to
be read. The Content Change option waits for at least
one second until there are no more file changes.
Therefore, if you select this option, files cannot be
read as quickly as with the other two options.
○ Done File Expected : Uses a specific file to signal that
the file to be processed is ready for consumption.
If you have selected this option, enter the name of the
done file. The done file signals that the file to be proc
essed is ready for consumption. This file must be in
the same folder as the file to be processed. Place
holders are allowed. Default: ${file:name}.done.
Sorting Select the type of sorting to use to poll files from the SFTP
server:
○ None: The sorting is specified by the STFP server

○ File Name: Files are polled sorted by file name
○ File Size: Files are polled sorted by file size
○ Time Stamp: Files are polled sorted by the modifica-
tion time stamp of the file
Sorting Order Select whether to sort in ascending or descending order.

Field Description
Lock Timeout (in min) Specify how long to wait before trying to process the file
again in the event of a cluster outage. If it takes a very long
time to process the scenario, you may need to increase
the timeout to avoid parallel processing of the same file.
This value should be higher than the processing time re
quired for the number of messages specified in Max.
Messages per Poll.
Default: 15
Change Directories Stepwise Select this option to change directory levels one at a time.
Include Subdirectories Selecting this option allows you to look for files in all the
subdirectories of the directory.

Field Description
Post-Processing Allows you to specify how files are to be handled after

processing.
Note that only successfully processed messages can be

post-processed. If message processing fails, the Post-
Processing settings are not effective.
You can select one of the following options from the drop
down list:
○ Delete File: The file is deleted after it has been read.

If you have also selected Done File Expected as Read
Lock Strategy, the file to be processed as well as the
done file will be deleted.
○ Keep File and Mark as Processed in Idempotent
Repository: Enables an idempotent repository to pre
vent a file from being consumed twice. Select this op
tion for SFTP servers that do not allow deletion or
moving of files, but the files are to be read only once.
Lock Strategy, an entry will be created in the idempo
tent repository; the done file will not be deleted.
○ Keep File and Process Again: The file is kept on the
SFTP server and file processing is repeated. You can
use this option for testing purposes, for example.
○ Move File: The file is moved to another directory.
If you select this option, you need to specify the tar
get directory.
Make sure that you specify a relative file path for the
target directory. Note that the specified file path is
defined relative to the directory specified with the
Directory parameter.
 Note
If you specify an absolute file path, it may occur
that the file cannot be stored correctly at run
time.
You can also specify the target directory dynamically,

for example, using the timestamp of the message.
The following example uses backup folders with time
stamps and replaces the file extension with bak:
backup/${date:now:yyyyMMdd}/$
{file:name.noext}.bak
Lock Strategy, only the file to be processed will be
moved and the done file will be deleted.

Field Description
Idempotent Repository You can select one of the following idempotent repository
options:
(Only available if you have selected Keep File and Mark as
Processed in Idempotent Repository for Post-Processing) ○ In Memory: Keeps the file names in the memory. Files
are read again from the SFTP server when the run
time node is restarted. It is not recommended to use
the In Memory option if multiple runtime nodes are
used. In this case the other nodes would pick the file
and process it because the memory is specific to the
runtime node.
○ Database(default): Stores the file names in a data
base to synchronize between multiple worker nodes
and to prevent the files from being read again when
the runtime node is restarted. File name entries are
deleted by default after 90 days.
 Note
The idempotent repository uses the username,
host name, and file name as key values to identify
files uniquely across integration flows of a tenant.
Retry Threshold for Alerting If the number of attempts to retry polling of a message
from the SFTP server exceeds this threshold value, an
alert is raised. The default value '0' indicates that the alert
is not raised.
 Note
If two or more sender channels are configured with
the SFTP connector, the value for the Alert Threshold
for Retry parameter should be the same.
6. Choose Advanced tab page.
Field Description
Buffer Size Write file content using the specified buffer size.
Default: 128 KB
Flatten File Names Flatten the file path by removing the directory levels so
that only the file names are considered and they are writ
ten under a single directory.

Field Description
Max. Messages per Poll (for sender channel only) Maximum number of messages to gather in each poll.
Consider how long it will take to process this number of
messages, and make sure that you set a higher value for
Lock Timeout (in min).
Default: 20 Example: 1000 can be set as a limit.
 Note
If you are using the sender SFTP adapter in combina
tion with an Aggregator step and you expect a high
message load, consider the following recommenda
tion:
Set the value for Max. Messages per Poll to a small

number larger than 0 (for example, 20). This ensures
proper logging of the message processing status at
runtime.
Prevent Directory Traversal If the file contains any backward path traversals such as
\..\ or /../.. , this carries a potential risk of directory tra
versal. In such a case, message processing is stopped with
an error. The unique message ID is logged in the message
processing log.
 Note
We recommend that you specify the Directory and File
Name fields to avoid any security risks. If you provide
these fields, the header is not considered.
7. Choose Scheduler tab page.
 Note
In the following cases certain features might not be available for your current integration flow:
○ A feature for a particular adapter or step was released after you created the corresponding shape
Scheduler


At Time Specify the time at which you want

Every Specify the interval at which the oper

ation has to be executed.
Schedule to Recur Daily Select the time or interval and time

zone for the schedule to recur.
Weekly Select the checkboxes to indicate the

days of the week on which the opera
tion has to be executed. Also, specify
the time or interval for the schedule to
recur.
Monthly Select the day of the month on which

the operation has to be executed. Also
indicate the time or the interval for the
schedule to recur.
under Schedule on Day and Schedule to Recur have been changed so that the scheduler runs every 10
seconds between 00:00 and 24:00.
8. Save or deploy the configuration.
SFTP polling is supported in the following way: The same file can be polled by multiple endpoints
configured to use the SFTP channel. This means that you can now deploy an integration flow with a
configured SFTP channel on multiple runtime nodes (which might be necessary to meet failover
requirements) without the risk of creating duplicates by polling the same file multiple times. Note that to
enable the new option, integration flows (configured to use SFTP channels) that were developed prior to
the introduction of this feature have to be regenerated.

2.5.2.8.2 Configuring a Channel with SFTP Receiver
Adapter
You can use the SFTP receiver adapter to transfer files the tenant to an SFTP server using the SSH protocol.
Context
How the Receiver SFTP Adapter Works

If you have configured a receiver SFTP adapter, message processing is performed as follows at runtime: The
tenant sends a request to an SFTP server (think of this as the receiver system), and the data flow is in the same
direction, from the tenant to the SFTP server. In other words, the tenant writes files to the SFTP server (from
where the communication partner can read them).
SFTP Receiver Adapter: Tenant writes file to SFTP server
Procedure
To configure a receiver channel, click on a connection between Integration Process component and a
receiver.
On the Target tab of the receiver channel, specify the following attributes.

Field Description
Directory Use the relative path to write the file to a directory, for ex
ample <dir>/<subdir>.
File Name Name of the file to be written.
 Note
If you do not enter a file name and the parameter re
mains blank, the content of the CamelFileName
header is used as file name. If this header is not speci
fied, the Exchange ID is used as file name.
Expressions, such as ab*, a.*, *a*, and so on, are not

supported.

ProducedFile). Note that you can manually configure
the endpoint URL using the File Name attribute of the
SFTP adapter. However, you can dynamically override the
value of this attribute by using the Camel header
CamelFileName.
Append Timestamp and dynamically configuring File

Name (through a Camel simple expression) must not be
used together. The reason is that using the Append
Timestamp option results in generating a simple expres
sion for the date. Both simple expressions result in an in
valid expression that cannot be processed correctly.

Field Description
Append Timestamp Appends a timestamp at the end of the file name.
If the file has an extension (for example, .xml), the time

stamp is appended to the file extension itself. Example: If
the file name is myfile.xml, the Append Timestamp
option (assuming the timestamp is Nov 30, 2015,
10:10:20) generates the following file name:
myfile20151201170800.xml
 Note
Be aware of the following behavior if you have config-
ured the file name dynamically: If you have selected
the Append Timestamp option, the timestamp over
rides the file name defined dynamically via the header
(CamelFileName).

Name (through a Camel simple expression) must not
be used together. The reason is that using the Append
Timestamp option results in generating a simple ex
pression for the date. Both simple expressions result
in an invalid expression that cannot be processed cor
rectly.
 Caution
Note that in case files are processed very quickly, the
Append Timestamp option might not guarantee
unique file names.
Address Host name or IP address of the SFTP server and an op

tional port, for example, wdfd00213123:22.
get system.
Select None if you are connecting directly to the SFTP

server.

system.
For more information on how to use the On-Premise op

tion to connect to an on-premise SFTP server, check out
the SAP Community blog Cloud Integration – How to Con
nect to an On-Premise sftp server via Cloud Connector .

Field Description
Location ID To connect to an SAP Cloud Connector instance associ
(only if On-Premise is selected for Proxy Type ated with your account, enter the location ID that you de
the cloud side.
Authentication Authentication option for the connection to the SFTP

server.
SFTP server authenticates the calling component
based on the user name and password. To make this
configuration setting work, you need to define the
user name and password in a User Credential artifact
and deploy the artifact on the tenant.
○ Public Key
based on a public key.
Credential Name Name of the User Credential artifact that contains the user
name and password.
(Only available if you have selected User Name/Password
for Authentication)
(Only available if you have selected Public Key for Make sure that the user name contains no other charac
Authentication) ters than A-z, 0-9, _ (underscore), - (hyphen), /
(slash), ? (question mark), @ (at), ! (exclamation mark), $
(dollar sign ), ' (apostrophe), (, ) (brackets), * (asterisk),
+ (plus sign), , (comma), ; (semicolon), = (equality
sign), . (dot), or ~ (tilde). Otherwise, an attempt for anon
ymous login is made which results in an error.
Timeout (in ms) Maximum time to wait for the SFTP server to be contacted
while establishing connection or performing a read opera
tion.
The timeout should be more than 0, but less than five mi
nutes.
Maximum Reconnect Attempts Maximum number of attempts allowed to reconnect to the

SFTP server.
Default value: 3

Field Description
Reconnect Delay (in ms) How long the system waits before attempting to recon
nect to the SFTP server.
Automatically Disconnect Disconnect from the SFTP server after each message
processing.
5. Choose Processing tab page.
Parameters and Descriptions for SFTP Adapter Receiver Channel
Field Description
Handling for Existing Files If the file already exists in the target, allow the following:
Override: Replace the existing file content with the new

one.
Append: Add the new file content to the end of the existing
one.
Fail: Do not perform any action and raise a failure.
Ignore: Do not perform any action.
Change Directories Stepwise Changes directory levels one at a time.
Create Directories Automatically creates missing directory levels as provided

in the file's path name.

Field Description
Temporary File Name Allows you to specify a name for a temporary file.
(Only visible when Handling for Existing Files is set to If you override an existing file (on the SFTP server) with a
Override) new one, the following situation can occur: The subse
quent file processor (implemented on the receiver side)
already starts processing the file, even though it is not yet
completely written (by the SFTP adapter) to the SFTP
server. Together with the Override option, you can specify
the name of a temporary file. The SFTP adapter then fin-
ishes writing the file with the temporary file name to the
SFTP server first. After that, the temporary file is renamed
according to the target file name specified in the SFTP
adapter (according to the setting for File Name under
Target). This makes sure that the subsequent processor
only processes a completely written file.
 Caution
Make sure that the name of the temporary file is
unique on the server, otherwise problems can occur
when different clients try to access the SFTP server
using the same temporary file name.
To make sure the name of the temporary file is

unique, you can enter one of the following strings, for
example:
${exchangeId}.tmp (because the Camel Ex

change ID is unique)
${file:name}.tmp (in this case, make sure that

the file name is unique, which anyway is a reasonable
requirement for a scenario including a SFTP file trans
fer)
Use Temporary File For synchronization reasons, the SFTP receiver writes the
data to a temporary file initially. Once the write procedure
is finished, the temp file is renamed to the target file. The
temp file is deleted automatically, irrespective of whether
the write procedure is successful or contains errors.
Enter a temporary file name.
You can either use a static file name such as

large.file.temp or a placeholder such as $(file:name).temp
6. Choose Advanced tab page.

Field Description
Default: 128 KB
 Note
tion:

runtime.
processing log.
 Note

2.5.2.9 Configuring a Channel with OData Adapter
Prerequisites
You have created an integration project and an integration flow.
Context
OData adapter allows you to communicate using OData protocol in either ATOM or JSON format. In the sender
channel, the OData adapter listens for incoming requests in either ATOM or JSON format. In the receiver
channel, the OData adapter sends the OData request in the format you choose (ATOM or JSON) to the OData
service provider.
OData adapters only support synchronous communication. In other words, every request must have a
response.
 Tip
If your input payload contains nodes without data, the output also contains empty strings. If you want to
avoid empty strings in the output, ensure that the input payload does not contain any empty nodes.
Procedure
You use this procedure to configure OData adapter assigned to a communication channel.
1. Double-click the communication channel in the Model Configuration tab page.
2. Choose Browse in the Adapter Type screen area.
3. Choose OData in the Choose Adapter window and choose OK.
4. Choose the Adapter Specific tab page and enter details in fields based on the description given in the
following table.

Field Channel Description
Authorization Sender only Select User Role if you want to authorize a user to send OData
requests based on the ESBMessaging.send
Select Client Certificate if you want to authorize a user to send

OData requests based on a certificate. If you select this option,
you have to choose Add and enter the Subject DN (information
used to authorize the sender) and Issuer DN (information
about the Certificate Authority who issues the certificate).
EDMX Sender only Select the EDMX file that contains the OData service definition.
Operation Sender only Select an operation to perform on the entity.
Entity Set Sender only Enter name of the entity set in the OData model.
Address Receiver only Enter URL of the OData service provider you want to connect
to.
Proxy Type Receiver only The type of proxy that you are using to connect to the target
system:
○ Select Internet if you are connecting to a cloud system.
○ Select On-Premise if you are connecting to an on-premise
system.
 Note
If you select the On-Premise option, the following re
strictions apply to other parameter values:
○ Do not use an HTTPS address for Address, as it
leads to errors when performing consistency
checks or during deployment.
○ Do not use Certificate-Based Authentication as
the Authentication Type, as it leads to errors
when performing consistency checks or during
deployment
 Note
If you select the On-Premise option and use the SAP
Cloud Connector to connect to your on-premise sys
tem, the Address field of the adapter refers a virtual
address which has to be configured in the SAP Cloud
Connector settings.

Field Channel Description
Location ID Receiver only in Enter the Location ID that you have provided in the account
case you choose configuration in the cloud connector
Proxy Type as On-
Premise
Authentication Receiver only Select Basic from the dropdown list if you want to use basic au
thentication to connect to the OData service provider
Select Client Certificate from the dropdown list if you want to

use a certificate for authentication while connecting to the
OData service provider.
 Restriction
You cannot use client certificate for connecting to the
OData service provider while modeling operations using
operations modeler.
Select Principal Propagation from the dropdown list if you want

the tenant to authenticate itself against the receiver by for
warding the principal of the inbound user to the cloud connec
tor. From there, it is forwarded to the back end of the relevant
on-premise system.
Operation Details Receiver only This contains details to the operation including Query (GET),
Update (PUT), Insert (POST), Read (GET), Create (POST) and
Merge (MERGE).
ResourcePath: This is the URI that is appended to the OData

service endpoint when connecting to the service provider.
For more information, see Modeling Operations for OData

Adapter
Query Options Receiver Only Enter any query options that you would like to send to the
OData service.
Custom Query Options Receiver only Enter additional query options other than the ones configured
using operations modeler. For example, sap-client=100 is a
custom query option that you can specify.
Content Type Receiver only Select format of the request payload. You can select Atom or
JSON.
Content Type Encoding Receiver only Select encoding standard used to encode the request payload
content.
Page Size Receiver only Enter total number of records in one page of response from
OData service provider.

 Note
For more information on authentication and authorization types, see and .
5. If you want the system to fetch records in pages of size specified in the Page Size field, select Process in
Batches checkbox.
Process in Batches option is available only for Query (GET) operation.
 Tip
In the Process Call step in which you are calling the Local Integration Process, ensure that you enable
looping and select the Expression Type as Non-XML, Condition Expression as $
{property.<ReceiverName>.<ChannelName>} contains 'true', and Maximum Number of
Iterations as 999.
Important Considerations while Specifying the Condition Expression in Process Call
○ Do not declare the property hasMoreRecords in any of the integration flow steps (For example,
content modifier or script). It is available by default. You can directly use this property while
entering the Condition Expression in Process Call step.
○ Ensure that the receiver system name in the Condition Expression is the SuccessFactors system
that you are connecting to using the receiver channel in the Local Integration Process. Do not enter
the receiver system name from the main integration flow.
○ If you have specified a channel name for the receiver channel in the Local Integration Process,
provide that name in the Condition Expression.
6. Save the configuration.
Modeling Operations for OData Adapter
Prerequisites
You have configured OData adapter assigned to the receiver channel.
Context
You use the Model Operation feature in the OData adapter to model an operation [Query (GET), Update (PUT),
Create (POST), Read (GET) and Merge (MERGE)]. You also select the ResourcePath, the URI using which you
transact with the OData service provider.
 Note
If you are connecting to a system that supports https communication, you must ensure the following:
● Java development kit is installed on your system

● You have referred JDK in the Eclipse configuration file

 Note
For information on referring JDK in Eclipse configuration file, refer to Eclipse documentation.
● You have imported the security certificate of the system you are connecting to your JDK keystore
 Note
For information on importing certificate to JDK keystore, refer to JDK documentation.
Procedure
You use this procedure to model an operation with the OData adapter.
1. Double-click the OData receiver channel of the integration flow in the Model Configuration tab page.
2. Choose the Adapter Specific tab page.
3. Choose Model Operation.
4. If you want to use a local EDMX file to connect to the OData service provider, perform the following
substeps:
 Remember
If you have used client certificate for connecting to the OData service provider, you need to download
the EDMX file from the OData service provider and import it to the src.main.resources.edmx folder. It
enables you to use local EDMX file to connect to the system.
a. Select the Local EDMX File checkbox.

b. Choose Browse.
c. Select an EDMX file in the EDMX Selection window and choose OK.
5. If you want to enter connection details manually, enter values in fields based on the description given in the
table.
Field Description
Address URL of OData service provider you are connecting to
Username Username you are using for authentication
Password Password you are using for authentication
 Note
You cannot use this option if you have selected client certificate as the authentication method while
configuring the channel.
6. Select the entity in Select Entity for an Operation window and choose Next.
7. Choose the Operation from the dropdown list based on the description given in the table.

Operation Description
Query (GET) Used to fetch data from the OData service
Create (POST) Used to insert data to an OData service
Update (PUT) Used to update data to an OData service
 Restriction
This operation is not supported for associated entities
Merge (MERGE) Used to merge data with existing data in OData service
 Restriction
This operation is not supported for associated entities
Read (GET) Used to fetch a unique entity from the OData Service.
Passes the key fields along with the Entity in the URI.
Format: <Entity>(keyfield 1, keyfield x,..)
8. Select the required fields for the operation form the Fields screen area.
 Note
IN the case of Update (PUT) or Insert (POST) operation, this would be the last step. Choose Finish.
9. If you have chosen the operation as Query (GET), enter values in Top and Skip fields based on the
description given in table.
Field Description
Top If you enter a value 'x', the system fetches the top x re
cords form the OData service provider
Skip If you enter a value 'x', the system skips x records from top
and fetches the remaining records from the OData service
provider
10. Choose Next.

11. If you want to add filter conditions to the operation, enter values in fields based on the description given in
table.
Field Description
Filter Field Field that is used in the ‘WHERE’ clause for filtering.
 Note
Field set contains the set of filterable fields returned
from the OData service provider that you can use in
the Filter Condition
Operation Operator to be used in the WHERE condition Example < , >

Field Description
Type Value that the filter filed has to be compared against.
When the Type is Text then specify the exact value
When the Type is XPath specify the entire XPath value. In

case the previous Integration flow step is a content en
richer, the XPath must be specified as a relative path,
starting with double-slash ‘\\’.
When the Type is Property, the system reads value from

the property you have defined in the integration flow ele
ment.
Value Value that the filter filed has to be compared against.
When the Type is Text then specify the exact value
When the Type is XPath specify the entire XPath value. In

case the previous Integration flow step is a content en
richer, the XPath must be specified as a relative path,
starting with double-slash ‘\\’.
Condition ‘AND’ or ‘OR’ condition that needs to be used in the Query

WHERE clause filter condition.
Add The condition will be added to the generated SuccessFac

tors Query
 Note
Multiple conditions can be added if required
Remove Any condition that is already added to the list can be se
lected and removed from the final Query
12. Choose Finish.
Results
Choosing the Finish button generates an XSD and EDMX files.
The XSD is the format in which data is processed in the Cloud Integration esb. You use this xsd file in the
mapping step for data transformation.
The EDMX file contains the OData Entity specification form the provider. This can be used when you model
operation again by choosing ‘Local EDMX’ file.

Defining Mapping for OData Batch Processing
Prerequisites
● You have created an integration project and integration flow

● You have configured the OData adapter receiver channel
● You have modeled PUT or POST operation using the OData adapter
● You have imported the input payload XML format into the eclipse project
Context
When you choose batch processing for PUT and POST operations for the OData adapter, the payload format
that is sent to the OData service must be in the recommended structure. You can use the input XSD that is
generated when you model the operation with a mapping step to transform the payload into the recommended
XSD structure. You can alternatively use XSLT or content modifier to do this.
Procedure
This procedure enables you to transform the input payload XML into the recommended batch processing
structure.
1. Choose File New Other .
2. In the New wizard, choose SAP Cloud Platform Integration Message Mapping and choose Next.
3. In the General Details section of the New Message Mapping window, enter Name and Description.
4. In the Location Details section of the New Message Mapping window, choose Browse and select the project
that you are working in. Choose Ok.
5. In the New Message Mapping window, choose Finish.
6. In the Source Element section, choose Add.
7. In the Select a XSD or WSDL file window, select the input payload format XML and choose OK.
8. In the Target Element section, choose Add.
9. In the Select a XSD or WSDL file window, select the XSD file that was generated when you modeled the
operation and choose OK.
10. Choose the Definition tab page and perform the following substeps to map the elements in the payload
XML to the target XSD.
a. Map the Entity Type element in the left pane to the batchChangeSet on the right pane.
b. Map the fields in the left pane to the appropriate fields on the right pane.
c. Map the batchChangeSet, Entity Set and Entity Type elements on the right pane except the headers to
a constant. The value of the constant can be a dummy example value.
d. Choose the method element and double-click Constant element in the properties view.
e. In the Constant Parameters window, enter the operation (PUT/POST) in the Value field and choose OK.
This is the same operation that you have chosen while modeling the OData operation.

 Note
Refer to 2031746 for more details on the structure of request and response XSD.
Mapping Definition for Reference Insert
When you are performing the Insert (POST) operation, in addition to inserting an entity, you can add a
reference to an associated entity. To do this, you have to map the appropriate field from the payload to the key
field of associated entity in <link> tag.
You can use a mapping step to do this. Consider the following example.

<Categories xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="CategoriesEntityPOST0.xsd">
<Category>
<ID>0</ID>
<Products>
<Product>
<Description>Description</Description>
<Name>Name</Name>
<ID>0</ID>
</Product>
</Products>
<link>
<Products>
<Product>
<ID>0</ID>
</Product>
</Products>
</link>
</Category>
</Categories>
The primary key is <ID>. You need to map the key element to your reference to <ID> for successfully executing
reference insert operation.
2.5.2.10 Configuring a Channel with Ariba Adapter
Prerequisites
● You have created an integration project and an integration flow.

● You have the credentials to log on to the Ariba Network.
● You have a certificate from Ariba or a trusted third party who is a certification authority.
● You have deployed the following artifacts: User Credentials and Keystore.

Context
You use this procedure to configure a sender and receiver channel of an integration flow with the Ariba Network
adapter. These channels enable the SAP and non-SAP cloud applications to send and receive business-specific
documents in cXML format to and from the Ariba Network. Examples of business documents are purchase
orders and invoices.
 Restriction
Procedure
2. On the General tab page, choose Browse in the Adapter Type screen area.
3. Select Ariba in the Choose Adapter window and choose OK.
4. Choose the Adapter-Specific tab page and enter the details as shown in the table below:
Parameters and Values of a Channel for the Ariba Adapter

Connection Details Connectivity URL You need URL to which the cXML re
quests are posted to/polled from or
you need profile URL to connect to
Ariba network.
If you do not have actual end-point

URL, then you need to enter /
getprofile at the end of profile
URL. This in turn sends a profile re
quest to this URL which internally
takes care of sending payload to the
correct URL.

Connection Mode Select one of the options based on the

description given below:
Test - If you select this option, the

Ariba Network will not process the
messages, and treats the messages
as test data.
Production - If you select this option,

the Ariba Network processes the mes
sages.
Default deployment mode is “Produc

tion”.
Account Type Select one of the options based on the

Buyer - If you hold a buyer account on

the Ariba Network.
Supplier - If you hold a supplier ac

count on the Ariba Network.
Request Type (this field is available Select one of the options based on the
only in the sender channel) request types of buyer/supplier that
you want to poll.
Maximum Messages (this field is Enter the number of messages to be

available only in the sender channel) polled from the Ariba Network for the
above-selected Request Type.
The maximum allowed value is 200.
Authentication Domain Select one of the options based on the

Network ID: A unique alphanumeric

value assigned to every organization
registered on Ariba SN; for example,
AN01000000001.
Network User Id: A login name of an

Ariba SN user. These names typically
have the format of an e-mail address;
for example, xyz@abc.com.

Authentication Select one of the options based on the

Shared Key: If you have set the shared

key in your Ariba account.
Client Certificate: If you have config-

ured your certificate from a trusted
certificate authority in the Ariba ac
count.
Credential Name Enter a name. This name is treated as

an alias to the secure store where the
user credentials are deployed. This
value should be set according to the
Authentication selected above. If you
have selected Client CertificateClient,
then enter the alias details in the
Private Key Alias field.
This alias is used to identify the key

store credentials deployed on the SAP
Cloud Platform Integration account.
For User, you can enter Network

User Id or Network ID, depend
ing on the selected option for
Authentication Domain.
For Password, enter the shared key.
Ariba Network ID Enter the ID that is associated with

the Ariba Network. Default value is
AN01000000001.
Processing Details cXML version Default value provided by SAP is

1.2.025. If you are entering the ver
sion, it must be above 1.2.018.
User Agent Enter the user agent details. The con

vention is a textual string representing
the client system that is conducting
the cXML conversation. It must con
sist of the software company name
and the product name.
Language Language that is used for construct

ing the cXML conversation.
The only supported language is EN.
Scheduler (only valid for the sender Run Once Run a data polling process immedi
channel) ately after deploying the project.

On Date Specific date on which the data poll

ing process has to be initiated to fetch
data from the Ariba system.
Daily Run message polling every day to

fetch data from the Ariba system.
Weekly Run the message polling every week

on specified days of the week to fetch
data from the SuccessFactors system.
Monthly on Day Execute the message polling every

month on the specified date to fetch
data from the Ariba server.
 Note
If the specified date is not appli
cable in a particular month, the
data polling is not executed in
that month. For example, if the
30th day is selected, polling will
not be executed in the month of
February, as 30th is not a valid
day for February.
Time The time at which the data polling cy

cle has to be initiated. For example, if
you want the data polling to be started
at 4:10 p.m., enter 16:10. Note that the
time must be entered in 24-hour for
mat.
Every xx minutes between HH hours The connector fetches data from the
and HH hours Ariba system every ‘xx’ minutes be
tween HH hours and HH hours.
 Note
If you want the polling to run for
the entire day, enter 1 and 59.
Time Zone Select the time zone that you want to

use as reference for scheduling the
data polling cycle.
 Note
You can use headers and properties to set values for Ariba Network URL, Credential Name, Private Key
Alias and Ariba Network ID. You can enter values in the following format:
○ ${header.url}
○ ${property.credentialName}

Results
In the Model Configuration editor, right-click and choose Deploy Integration Content to apply the configuration
settings and run the integration flow.
2.5.2.11 Configuring a Channel with Twitter Adapter
Prerequisites
You can only select the Twitter adapter type when you have connected your client (which runs Eclipse) to a
suitable version of a cluster. After connecting to the newest version of the cluster, choose Update client with
latest components from server (see the following figure).
Context
You can use the Twitter receiver adapter to extract information from the Twitter platform (which is the receiver
platform) based on certain criteria such as keywords, user data, for example. As one example, you can use this
feature to send, search for and receive Twitter feeds.
The connection works that way that the tenant logs on to Twitter based on an OAuth authentication mechnism
and searches for information based on criteria as configured in the adapter at design time. OAuth allows the
tenant to access someone else’s resources (of a specific Twitter user) on behalf of the tenant. As illustrated in
the figure, the tenant (through the Twitter receiver adapter) calls the Twitter API to access resources of a
specific Twitter user. Currently, the Twitter adapter can only be used as receiver adapter. For more information
on the Twitter API, go to: https://dev.twitter.com/ .
Procedure

3. Select Twitter in the Choose Adapter window and choose OK.
Attributes of the Twitter Receiver Adapter (Twitter Components)

Field Description
Endpoint To access Twitter content, you can choose among the following general options.
○ Send Tweet
Allows you to send content to a specific user timeline.
○ Search
Allows you to do a search on Twitter content by specifying keywords.
○ Send Direct Message
Allows you to send messages to Twitter (write access, direct message).
User Specifies the Twitter user from which account the information is to be extracted.
(only in case as
Endpoint you
have selected
Send Direct
Message)
Page Size Specifies the maximum number of results (tweets) per page.
Number Of Specifies the number of pages which you want the tenant to consume.
Pages
Attributes of the Twitter Receiver Adapter (Filter Settings)

Field Description
Keywords Specifies the keywords used to filter the results.
(only in case as Use commas to separate different keywords or a valid Twitter Search API query (for more informa
Endpoint you tion, go to https://dev.twitter.com/rest/public/search ).
have selected
Search)
Language Specifies the search language.
(only in case as
Endpoint you
have selected
Search)
Attributes of the Twitter Receiver Adapter (OAuth Settings)

Field Description
Consumer Key An alias by which the consumer (tenant) that requests Twitter resources is identified

Field Description
Consumer An alias by which the shared secret is identified (that is used to to define the token of the consumer
Secret (tenant))
Access Token An alias by which the access token for the Twitter user is identified
In order to make authorized calls to the TwitterAPI, your application must first obtain an OAuth ac
cess token on behalf of a Twitter user
Access Token An alias by which shared secret is identified that is used to define the token of the Twitter user
Secret
The authorization is based on shared secret technology. This method relies on the fact that all parties of a
communication share a piece of data that is known only to the parties involved. Using OAuth in the context
of this adapter, the Consumer (that calls the API of the receiver platform on behalf of a specific user of this
platform) identifies itself using its Consumer Key and Consumer Secret, while the context to the user
itself is defined by an Access Token and an Access Token Secret. These artifacts are to be generated for
the receiver platform app (consumer) and should be configured that way that they will never expire. This
adapter only supports consumer key/secret and access token key/secret artifacts that do not expire.
To finish the configuration of a scenario using this adapter, the generated consumer key/secret and access
token key/secret artifacts are to be deployed as Secure Parameter artifact on the related tenant. To do this,
use the Integration Operations feature, position the cursor on the tenant and chosen Deploy Artifact .... As
artifact type, choose Secure Parameter.
5. Save the configuration of the channel editor.
2.5.2.12 Configuring a Channel with Facebook Adapter
Context
You can use the Facebook receiver adapter to extract information from Facebook (which is the receiver
feature in social marketing activities to do social media data analysis based on Facebook content.
The connection works that way that the tenant logs on to Facebook based on an OAuth authentication
mechanism and searches for information based on criteria as configured in the adapter at design time. OAuth
allows a the tenant to access someone else’s resources (of a specific Facebook user) on behalf of the tenant. As
illustrated in the figure, the tenant (through the Facebook receiver adapter) calls the Facebook API to access
resources of a specific Facebook user. For more information on the Facebook API, go to: https://
developers.facebook.com/ .

Procedure
3. Select Facebook in the Choose Adapter window and choose OK.
Attributes of the Facebook Receiver Adapter (Facebook Components)

Field Description
Endpoint To access Facebook content, you can choose among the following general options.
○ Get Posts
Allows you to fetch specific Facebook posts.
○ Get Post Comments
Allows you to fetch specific Facebook post comments.
○ Get Users
Allows you to fetch details of a specific user.
○ Get Feeds
Allows you to fetch feeds of a specific user or a page.
User/Page ID Specifies the Facebook user from which account the information is to be extracted.
Timeout (ms) Specifies a timeout (in miliseconds) after which the connection to te Facebook platform should be
terminated.
Attributes of the Facebook Receiver Adapter (OAuth Settings)

Field Description
Application ID An alias by which the consumer (tenant) that requests Facebook resources is identified
Application An alias by which the shared secret is identified (that is used to to define the token of the consumer
Secret (tenant))

Field Description
Access Token An alias by which the access token for the Facebook user is identified
In order to make authorized calls to the Facebook API, your application must first obtain an OAuth
access token on behalf of a Facebook user
5. Save the configuration of the channel editor.
2.5.2.13 Configuring a Channel with SuccessFactors Adapter
Prerequisites
To successfully run the Operations Modeler, your Java Virtual Machine (JVM) must contain the security
certificate recommended by the SuccessFactors system. Example: VeriSign Class 3 Public Primary
Certification Authority - G5 security certificate.
 Note
First, you must verify if the JVM contains the security certificate that is used by SuccessFactors system. If
not, then download the certificate from the appropriate security certificate vendor and install it. You can
refer to JVM documentation for verifying and installing the security certificate on to your JVM. Ensure that
the IP addresses of the SAP Cloud Platform Integration runtime worker node and the systems you are using
to connect to the SuccessFactors system are in the list of allowed IP addresses.
Context
The SuccessFactors adapter provides three message protocols for you to communicate with the
SuccessFactors system. They are:

1. SOAP - Configuring SuccessFactors Adapter with SOAP Message Protocol [page 156]
2. OData V2 - Configuring SuccessFactors Adapter with OData V2 Message Protocol [page 166]
 Note
This is available only for the receiver channel.
3. OData V4 - Configuring SuccessFactors Adapter with OData V4 Message Protocol [page 172]
 Note
This is available only for the receiver channel.
4. REST - Configuring SuccessFactors Adapter with REST Message Protocol [page 173]
You can choose the protocol you want based on the scenario you want to execute.
You need to provide the following details in order to communicate with the SuccessFactors system.
● Connection details – Details required to establish a connection with the SuccessFactors system
● Processing details – Information required to process your modeled operation
● Scheduler – Settings that enable you to schedule a data polling cycle at regular intervals
 Note
The scheduler is available only for the sender channel.
 Note
The password for connecting to the SuccessFactors system should be deployed onto the tenant via the
‘Credentials’ deployment wizard available in the Node Explorer.
 Tip
You can use the Insert (POST) operation to insert more than one records in a single operation. These
records must have an edmx association between them.
2.5.2.13.1 Configuring SuccessFactors Adapter with SOAP

Message Protocol
Context
You use this procedure to configure the SuccessFactors adapter with the SOAP message protocol.
 Note
You can now pass filter conditions via header or property while performing an asynchronous or ad-hoc
operation.

 Restriction
Procedure
1. On the Model Configuration tab, double-click the channel that you want to configure.
2. Go to the General tab and choose Browse in the Adapter Type screen area.
3. In the Choose Adapter window, select SuccessFactors and choose OK.
4. Choose SOAP from the dropdown list in the Message Protocol field.
5. Go to the Adapter Specific tab.
6. Provide values in the fields based on the descriptions in the following table.
Field Description
Address URL of the SuccessFactors data center that you want to

connect to.
Address Suffix The system provides a value for this field based on the
protocol you choose. For SOAP, the value is /sfapi/v1/
soap.
Credential Name Credential name that you have used while deploying cre
dentials on the tenant.
Proxy Type Type of proxy you want to use to connect to the Success
Factors system.
If you choose Manual, you should enter values for the

fields Proxy Host and Proxy Port.
Proxy Host is the name of the proxy host you are using.
Proxy Port is the port number that you are using.
Call Type Type of call that the SAP Cloud Platform Integration sys
tem makes to the SuccessFactors system.
Choose Synchronous for normal operations.
Choose Asynchronous for ad hoc operations.
Operation Details Details of the operation that you are performing on the
SuccessFactors system. Choose Model Operation to
launch the operations modeler wizard. For more informa

Field Description
tion, see Configuring SuccessFactors Adapter with SOAP

Message Protocol [page 156]
You can view the following details:
Entity: The entity that you are accessing in the Success

Factors system
Operation: Query/Insert/Update/Upsert
Query: SFQL (SuccessFactors Query Language) query

type that is used to communicate with the SuccessFactors
system
 Note
Query is the only operation available in the sender
channel.
Parameters SFAPI operation parameters that you want to include in

the operation that you have modeled using the operations
modeler wizard.
 Code Syntax
key1=value1&key2=value2
 Note
You can specify the custom parameters in four ways:
<Key>=<value>;<key>=,value>
<header/property variable>=value;<header/property
variable>=value
<header/property variable>;<header/property varia

ble>; here, the variable contains both the key and its
value.
 Example
externalKeyMapping=costCenter;pro
cessinactiveEmployees=true
 Example
$
{property.ECERP_PARAMETERS}=costC

Field Description
enter;$
{header.ECERP_PARAMETERS}=true
 Example
${property.ECERP_PARAMETERS};$
{header.ECERP}, which contains the key-
value pair.
 Example
$
{property.ECERP_PARAMETERS}=proce
ssinactiveEmployees=true;resultOp
tions=allJobChangesPerDay
. Here, you are specifying multiple key-value pairs in

one property parameter.
Page Size In the case of a Query operation, this value indicates the
maximum number of records fetched in one polling cycle
from the SuccessFactors system.
 Caution
If you find that the Query operation stops due to a
timeout, reduce the Page Size and execute the opera
tion again.
In the case of Insert/Update/Upsert operations, this value

indicates the maximum number of records you can send
in a payload.
 Caution
Since the SuccessFactors system supports a maxi
mum page size of 800, you must ensure that the max
imum number of records in the payload for data ma
nipulation operations (Insert, Update, or Upsert) is
less than or equal to the page size specified.
If you need to send a larger payload, use the Splitter

element to split the payload. Also, ensure that the
split payload size is less than or equal to the page size
specified.
The maximum page size supported by SuccessFactors is

800.

Field Description
 Tip
The system assigns a default value of 200 if you do
not provide a value for this field.
Timeout (in min) Maximum time system waits for a response before the
connection ends or is timed out. By default, 5 minutes is
the timeout value if you do not provide input.
7. If you want to process messages in batches while using the SuccessFactors SOAP adapter in the receiver
channel of a Local Integration Process, select Process in Batches.
 Restriction
You cannot use Process in Batches option with Query operation if the Process Call step is used in a
Multicast branch.
 Note
By selecting Process in Batches, you enable the adapter to process messages in batches. The size of a
message batch is defined by the value that you specify in Page Size.
 Tip
{property.SAP_SuccessFactorsHasMoreRecords.<ReceiverName>} contains 'true', and
Maximum Number of Iterations as 999.
○ Do not declare the property SAP_SuccessFactorsHasMoreRecords in any of the integration

flow steps (For example, content modifier or script). It is available by default. You can directly use
this property while entering the Condition Expression in Process Call step.
8. If you are configuring the sender channel, perform the following substeps to configure the scheduler:
a. Go to the Scheduler tab.
b. Enter the scheduler details based on the descriptions given in the table below.

Parameters and Values of SuccessFactors Adapter Scheduler
Field Description
Run Once Run a data polling process immediately after deploying

the project.
On Date Specific date on which the data polling process has to

be initiated to fetch data from the SuccessFactors sys
tem.
Daily Run message polling every day to fetch data from the
SuccessFactors system.
Weekly Run message polling on a specified day every week to

fetch data from the SuccessFactors system.
Monthly on Day Run message polling on a specified date every month to

fetch data from the SuccessFactors server.
 Note
If the specified date is not applicable to a month,
data polling is not executed in that particular
month. For example, if the 30th day of the month is
selected as the polling date, polling will not be exe
cuted in the month of February as February 30 is
not a valid date.
Time The time at which the data polling cycle has to be initi
ated. For example, if you want data polling to start at
4.1PM, enter 16:10. Note that the time must be entered
in 24-hour format.
Every xx minutes between HH hours and HH hours The connector fetches data from the SuccessFactors
system every ‘xx’ minutes between HH hours and HH
hours.
 Note
If you want the polling to run for the entire day, en
ter 1 and 59.
Time Zone Select the time zone that you want to use as the refer
ence for scheduling the data polling cycle.

2.5.2.13.1.1 Modeling Operations for SuccessFactors SOAP
Web Service
Prerequisites
● You have assigned the SuccessFactors adapter to the communication channel.

● You have selected SOAP in the Message Protocol field.
● You have launched the operations modeler wizard by choosing Model Operation on the Adapter Specific
tab.
Context
You need to provide operation details to access and modify records in the SuccessFactors SOAP Web service.
You use the operations modeler wizard to provide these details and also generate the XSD file.
Procedure
1. In the Connect to System window, provide values in the fields based on the descriptions in the table below
and choose Next.
Field Description
Address URL of the SuccessFactors system that you are connect

ing to
Company ID SuccessFactors company ID
User Name Your user name for authentication
Password Relevant password for the specified user name
Proxy Communication Select this checkbox if you want to manually specify the
proxy details
Proxy Host Proxy host name
Proxy Port Proxy port number
2. In the Entity Selection window, select the entity that you want to perform the operation on from the Entity
List. Choose Next.
The wizard fetches the fields for the selected entity.

3. In the Model Operation window, select the Operation from the dropdown list.
4. Select the fields that you want to perform the operation on.
5. If you have selected query for the Operation, choose Next to specify filter conditions.
You can configure the filter conditions to execute delta sync scenarios. For more information, see
Configuring Delta Sync Scenarios [page 164]. Refer to the following table when specifying filter conditions.
Field Description
Filter Field Field that is used in the SuccessFactors API ‘WHERE’

clause for filtering.
 Note
The field set contains the set of filterable fields re
turned from the SuccessFactors API that you can use
in the filter condition.
Operation Operator to be used in the WHERE condition. Example: < ,

>
Type Value that the filter field has to be compared against.
If the type is Text, specify the exact value.
If the type is XPath, specify the entire XPath value. If the

previous integration flow step is a content enricher, the
XPath must be specified as a relative path, starting with a
double-slash ‘\\’.
If the type is Delta Sync, the value is populated with

maxDateFromLastRun.
If the type is Property, the system reads the value from the
property that you have defined in the integration flow ele
ment.
Value Value that the filter field has to be compared against.
If the type is Text, specify the exact value
If the type is XPath, specify the entire XPath value. If the

previous integration flow step is a content enricher, the
XPath must be specified as a relative path, starting with a
double-slash ‘\\’.
If the type is Delta Sync, the value is populated with

maxDateFromLastRun.
Condition ‘AND’ or ‘OR’ condition that needs to be used in the query


Field Description

tors query.
 Note
Multiple conditions can be added if required.
lected and removed from the final SuccessFactors query.
6. Choose Finish.
The Finish button is only activated if you have selected fields of the entity in step 3. When you choose
Finish, the system creates a XML schema file with the selected entities. You can access the schema file in
the src.main.resources.wsdl folder of your project. If there is an existing XML schema file, you have the
option of overwriting the existing file or creating a new file after choosing the Finish option. This file can be
used in the integration flow like a mapping step.
One of the root elements in the XML schema file is the Entity Name. In cases where the Entity Name is in
the format <EntityName>_$XX, only <EntityName> is used as the root element of the XML schema file.
$XX is dropped from the root element name of the XML schema so that you can use the same integration
flow in other SuccessFactors company IDs without changing the mapping.
2.5.2.13.1.1.1 Configuring Delta Sync Scenarios
You can configure the SuccessFactors connector to fetch the modified or delta records instead of fetching all
the records. This optimizes the polling mechanism. This is known as a delta sync configuration.
If you want to add more filter conditions after you have configured the delta sync, use the appropriate
operators and add them. Once the query is executed, the relevant scenarios are executed.
 Note
The following steps guide you through the configuration of the delta sync conditions only. For an end-to-
end procedure for creating and executing operations, see Modeling Operations.
Delta Sync
With this configuration, the system fetches all records from the beginning of time (1/1/19070, by default) in the
first run. Only modified records are fetched in the subsequent runs.
1. In the Configure Filter Condition for Fields window, select a field of type DATETIME for the Filter Field.
Example: lastModified
2. In the Operation field, select >.
3. In the Type field, select Delta Sync. maxDateFromLastRun is automatically populated in the Value field.

 Note
If the payload from the SuccessFactors system has execution_timestamp as one of the fields, that time
stamp is used as the reference date for the subsequent delta sync polling cycles. The date specified in the
Query is ignored.
Modify Query in Existing Delta Sync Configuration
With this configuration, you can modify the query in an existing delta sync configuration. The system will
consider the new query and fetch only modified records in the subsequent polling cycles.
1. In the Model Operation window, add or remove the new fields that you wish to fetch.
2. In the Configure Filter Conditions for Fields window, you can add new filter conditions.
3. You can also modify or remove existing filter conditions in the Configure Filter Conditions for Fields window.
4. Continue with the existing delta sync configuration.
Reset Existing Delta Sync Configuration
You perform these steps only to reset an existing delta sync configuration. After reset, the configuration
enables you to fetch data from the beginning of time (1/1/1970) in the first polling cycle and fetch only
modified records in the subsequent polling cycles.
1. In the channel configuration, enter a new channel name in the Channel Details section. The new name
resets the existing delta sync configuration.
 Caution
Choose a unique channel name. Do not use names that were used in earlier delta sync configurations.
Fetch Records After a Specified Date in the First Run and Fetch Modified
Records in Subsequent Runs
With this configuration, you can specify a date that will be used as a reference to fetch records. The system
fetches the records that have been modified or added after the specified date in the first polling cycle. The
modified records are fetched in the subsequent polling cycles.
1. In the Model Configuration window, select the fields that you want to fetch.
2. In the Configure Filter Condition for Fields window, select a DATETIME type field in theFilter Field window.
Example: lastModified
3. In the Operation field, choose >=.
4. In the Value field, enter the date after which you want the records to be fetched from the system.

5. Choose Add.
6. Select a field of type DATETIME for the Filter Field. Example: lastModified
7. In the Operation field, select >.
8. In the Type field, select Delta Sync. maxDateFromLastRun is automatically populated in the Value field.
9. In the Operators field, choose AND.
2.5.2.13.2 Configuring SuccessFactors Adapter with OData

V2 Message Protocol
Context
You use this procedure to configure the SuccessFactors adapter with the OData V2 message protocol.
 Remember
The OData V2 message protocol is only available if you are using the SuccessFactors adapter in the receiver
channel.
 Restriction
 Tip
Procedure
4. Choose OData V2 from the dropdown list in the Message Protocol field.
6. Provide values in the fields based on the descriptions in the following table.

Field Description
Address URL of the SuccessFactors data center that you would like
to connect to.
protocol you choose. For SOAP, the value is /odata/v2.
Factors system.
You can choose Internet or On-premise.
Operation Details Operation that you have created using the operations
modeler. For more information, see . [page 168]
Content Type Format of the request payload. You can select Atom or
JSON.
Content Type Encoding Encoding standard to be used for encoding content. Cur
rently, UTF-8 is supported.
Page Size This field is only applicable for Query operations. It indi
cates the number of records that the SAP Cloud Platform
Integration system reads from the SuccessFactors system
in one polling cycle when Operation is executed.
If you find that the Operation stops due to a timeout, re

duce the Page Size and execute the operation again.
Timeout (in min) Maximum time system waits for a response before the
connection ends or is timed out. By default, 5 minutes is
the timeout value if you do not provide input.
7. If you want to process messages in batches while using the SuccessFactors ODataV2 adapter in the
receiver channel of a Local Integration Process, select Process in Batches.
 Restriction
You cannot use Process in Batches option with Query operation if the Process Call step is used in a
Multicast branch.
 Note
By selecting Process in Batches, you enable the adapter to process messages in batches. The size of a
message batch is defined by the value that you specify in Page Size.

 Tip
{property.<ReceiverName>.<ChannelName>.hasMoreRecords} contains 'true', and
Maximum Number of Iterations as 999.
○ Do not declare the property hasMoreRecords in any of the integration flow steps (For example,
content modifier or script). It is available by default. You can directly use this property while
entering the Condition Expression in Process Call step.
2.5.2.13.2.1 Modeling Operations for SuccessFactors OData

V2 Web Service
Prerequisites

● You have selected OData V2 in the Message Protocol field.
● You have launched the operations modeler wizard by choosing Model Operation on the Adapter Specific
tab.
Context
You need to provide operation details to access and modify records in the SuccessFactors SOAP Web service.
You use the operations modeler wizard to provide these details and also generate the EDMX file.
Procedure
1. If you want to use a local EDMX file to connect to the system, perform the following substeps:
a. Select the Local EDMX File checkbox.

b. Choose Browse.
c. Select an EDMX file in the EDMX Selection window and choose OK.
2. If you want to specify the connection details manually, make sure that the Local EDMX File checkbox is not
selected and provide values in the fields based on the descriptions in the following table.
Field Description
Address URL of the SuccessFactors system that you are connect

ing to
Company ID SuccessFactors company ID
User Name Your user name for authentication
Password Relevant password for the specified user name
Proxy Communication Select this checkbox if you want to manually specify the
proxy details
Proxy Host Proxy host name
Proxy Port Proxy port number
 Note
If you are connecting to a system that supports HTTPS communication, you must ensure the following:
○ Java Development Kit is installed on your system.
○ You have referenced JDK in the Eclipse configuration file.
 Note
For information about referencing JDK in the Eclipse configuration file, see the Eclipse
documentation.
○ You have imported the security certificate of the system that you are connecting to your JDK
keystore.
 Note
For information about importing certificates to the JDK keystore, see the JDK documentation.
You should see a list of entities.
3. In the Select Entity for an operation window, select the Entity and choose Next.
4. Choose the Sub-Levels from the dropdown list.
 Remember
If you are performing the Insert (POST) operation and the payload contains one level of sub-entities,
choose 1 from the dropdown list.

 Caution
Ensure that you select values for the Sub-Levels field only from the dropdown list.
 Note
The navigation depth is the level up to which you want to view the entity association. For example,
consider that entity B is associated with entity A and entity C is associated with entity B. If you choose
entity A in the Select Entity for an operation window and choose a navigation depth of 1, you can
navigate up to entity B. If you choose a navigation depth of 2, you can navigate up to entity C.
5. Choose the Operation from the dropdown list based on the descriptions in the table below.
Operation Description
Query (GET) Used to fetch data from the OData service.
Update (PUT) Used to update data to an OData service.
Insert (POST) Used to insert data into an OData service.
Read (GET) Used to fetch a unique entity from the OData service.
Passes the key fields along with the entity in the URI (Uni
versal Resource Indicator). Format:<Entity>(Keyfield 1,
Keyfield 2, and so on)
Upsert (UPSERT) Used to perform Update and Insert operations using one
command to the OData service exposed by the Success
Factors system. It checks if the record exists in the table. If
the record is present, it updates the content of the record.
If the record is not present, it will create a new record with
the parameters specified in the payload.
 Restriction
This operation is not supported if you specify JSON as
the request payload type.
6. Select the required fields for the operation from the Fields screen area and choose Next.
 Remember
If you choose a PUT or POST operation, this is the last step. Choose Finish.
7. Enter values in the Top and Skip fields based on the descriptions in the table below. This is only applicable
for Query operations.
Field Description
Top If you enter the value 'x', only the top 'x' values are fetched
from the OData service provider.
Skip If you enter the value 'x', the top 'x' values are ignored and
the remaining records are fetched from the OData service
provider.
8. Select the values based on the descriptions in the table below to add filter conditions to the operation. The
filter step is only available for query (GET) operations.

Field Description
Filter Field Field that is used in the SuccessFactors API ‘WHERE’

clause for filtering.
 Note
The field set contains the set of filterable fields re
turned from the SuccessFactors API that you can use
in the filter condition.
Operation Operator to be used in the WHERE condition. Example: < ,

>
Type Value that the filter field has to be compared against.
If the type is Header, the value is populated from the

header that you have specified.
If the type is Property, the system reads the value from the
property you have defined in the integration flow element.
Value Value that the filter field has to be compared against.
If the type is Header, specify the header that contains .
If the type is Property, specify the property from which the

value has to read.
Condition ‘AND’ or ‘OR’ condition that needs to be used in the query


tors query.
 Note
Multiple conditions can be added if required.
lected and removed from the final SuccessFactors query.
9. Choose Finish.
Results
Choosing Finish generates an XSD and EDMX files.
The SAP Cloud Platform Integration enterprise service bus (ESD) processes data in the XSD format. You use
this XSD file in the mapping step for data transformation.
The EDMX file contains the OData entity specification from the OData service provider. You can use this file in
the subsequent operation modeling steps to connect to the OData service provider.

2.5.2.13.3 Configuring SuccessFactors Adapter with OData
V4 Message Protocol
Context
 Remember
The OData V2 message protocol is only available if you are using the SuccessFactors adapter in the receiver
channel.
 Tip
Procedure
6. Provide values in the fields based on the descriptions in the table below.
Field Description
to connect to.
Factors system.
Operation Operation that you want to perform on the OData V4 serv

ice.

Field Description
Query(GET), Create(POST) and Update (PUT) operations

are currently supported.
Resource Path Provide the resource path of the entity that you want to
access.
Query Options Query options that you want to send to the OData V4 serv
ice with operation details.
For more information on Query Options, refer to steps 7 and 8 in Modeling Operations for SuccessFactors
OData V2 Web Service [page 168].
2.5.2.13.4 Configuring SuccessFactors Adapter with REST

Message Protocol
Context
Procedure
6. Provide values in the fields based on the descriptions in the table below.
Field Description
to connect to.
protocol you choose. For SOAP, the value is /odata/v2.

Field Description
Factors system.
Operation Select the operation you want to perform from the drop
down list.
 Note
Only GET for the sender channel and GET andPOST
for the receiver channel are currently supported.
Entity LMS entity you are accessing.
 Note
You can find the entity name in the relevant API docu
mentation.
Parameters Parameters to be sent to the REST service.
Example: creationDate=1&active=true
 Note
In the case of the GET operation, you can fetch just
the modified records in subsequent runs by using the
condition lastModifiedDate=${deltasync.maxDate
FromLastRun}.
Page Size The number of records that are read from the Success
Factors system in one request.
If you find that the Operation stops due to a timeout, re

duce the Page Size and execute the operation again.
7. If you are configuring the sender channel, perform the following substeps to configure the scheduler:
a. Go to the Scheduler tab.
b. Enter the scheduler details based on the descriptions in the table below.
Parameters and Values of SuccessFactors Adapter Scheduler

Field Description
Run Once Run a data polling process immediately after deploying

the project.

Field Description
On Date Specific date on which the data polling process has to

be initiated to fetch data from the SuccessFactors sys
tem.
Daily Run message polling every day to fetch data from the
SuccessFactors system.
Weekly Run message polling on a specified day every week to

fetch data from the SuccessFactors system.
Monthly on Day Run message polling on a specified date every month to

fetch data from the SuccessFactors server.
 Note
If the specified date is not applicable to a month,
data polling is not executed in that particular
month. For example, if the 30th day of the month is
selected as the polling date, polling will not be exe
cuted in the month of February as February 30 is
not a valid date.
Time The time at which the data polling cycle has to be initi
ated. For example, if you want data polling to start at
4.1PM, enter 16:10. Note that the time must be entered
in 24-hour format.
Every xx minutes between HH hours and HH hours The connector fetches data from the SuccessFactors
system every ‘xx’ minutes between HH hours and HH
hours.
 Note
If you want the polling to run for the entire day, en
ter 1 and 59.
Time Zone Select the time zone that you want to use as the refer
ence for scheduling the data polling cycle.
 Caution
If a cluster is updated with the latest node assembly, it is restarted after the update. If you have
deployed projects on the cluster with scheduler settings, you face the following issues:
○ Run Once settings: If you have selected Run Once in the scheduler, the system deploys the
project after the cluster is updated. This results in the system performing the operation again.
You see copies of the same result after the cluster update.
○ Specific time schedule: If you have configured a specific date in the scheduler and those
projects are deployed again after a cluster update, you might see those projects in an error
state.
To avoid this, you have to undeploy the project after the system has executesd the operation
according to the scheduler settings.

2.5.2.14 Configuring a Channel with JMS Adapter
You configure the JMS adapter to enables asynchronous messaging by using message queues.
Prerequisites
The JMS messaging instance that is used in asynchronous messaging scenarios with the JMS or AS2 adapters
has limited resources. Cloud Platform Integration Enterprise Edition sets a limit on the queues, storage, and
connections that you can use in the messaging instance.
Resource Limits for Cloud Platform Integration Enterprise Edition:
● Maximum number of queues: 28

● Queue capacity: 5GB
There are also technical restrictions on the size of the headers and exchange properties that can be stored in
the JMS queue.
The following size limits apply when saving messages to JMS queues:
● There are no size limits for the payload. The message is split internally when it is put into the queue.
● There are no size limits for attachments. The message and the attachment are split internally when put
into the queue.
● Headers and exchange properties defined in the integration flow before the message is saved to the queue
must not exceed 4 MB in total.
 Note
The JMS Adapter generates message queues during deployment. To avoid errors, you must manually
delete any message queues that are no longer required in the Message Queue Monitor.
 Caution
This adapter type cannot process ZIP files correctly. Therefore, don't use this adapter type together with
Encoder or Decoder process steps that deal with ZIP compression or decompression.
Context
You configure the receiver and sender JMS adapter to enables asynchronous messaging by using message
queues. The JMS incoming message is stored in a permanent persistence and scheduled for processing in a
queue. The processing of messages from the queue is not serialized. The messages are processed
concurrently. The sender does not have to wait while the message is being processed and if needed retried.

 Note
The JMS adapter stores only simple data types, which includes in particular: exchange properties that do
not start with Camel, as well as headers (primitive data types or strings).
 Note
You can use the JMS Receiver Adapter in the Send step to save the message to the JMS queue and to
continue the processing afterwards.
Supported Headers:
● JMSTimestamp
Specifies the time when a JMS message was created.
Procedure
3. Select JMS in the Choose Adapter window and choose OK.
Parameters and Values of Sender JMS Adapter

Section Parameters Description
Processing Details Queue Name Enter the name of the message

queue.
Number of Concurrent Processes Enter the number of concurrent proc

esses for each worker node. The rec
ommended value depends on the
number of worker nodes, the number
of queues on the tenant, and the in
coming load. The value should be as
small as possible (1-5).
Retry Handling Retry Interval (in m)* Enter a value for the amount of time
to wait before retrying message deliv
ery.
Exponential Backoff Enter a value to double the retry inter

val after each unsuccessful retry.
Maximum Retry Interval (in m)* Enter a value for the maximum
amount of time to wait before retrying
message delivery.

Dead-Letter Queue If selected, the message will be taken

out of processing and marked as
Blocked in the queue if it cannot be
processed after two retries.
In certain cases, usage of the JMS

sender adapter can cause a node fail
ure. This can happen, for example, if
the JMS adapter tries repeatedly to
process a failed (large) message. To
avoid such a situation, select this op
tion (switched on by default).
In such cases, a lock entry is created,

which you can view and release in the
Message Monitoring application under
Managing Locks.
For more information, check out the

following blog: Cloud Integration –
Configure Dead Letter Handling in
JMS Adapter .
 Note
For high-load scenarios, or if you
are sure that only small messages
will be processed in your scenario,
you should deselect the checkbox
to improve the performance. But
be aware that there is a risk of an
outage, for example,if you run out
of memory.

JMS Adapter .
Parameters and Values of JMS Receiver Adapter

queue.
Retention Threshold for Alerting (in d) Enter the time period (in days) by
which the messages have to be
fetched. The default value is 2.

Expiration Period (in d)* Enter the number of days after which
the stored messages are deleted (de
fault is 90).
The minimum value for Expiration Pe

riod should be at least twice the value
for Retention Threshold for Alerting.
Encrypt Stored Message Select this option to encrypt the mes

sage in the data store.
Transfer Exchange Properties You can select this option to also

transfer the exchange properties to
the JMS queue.
However, we do not recommend using

this option because headers and ex
change properties are subject to size
restrictions, which can result in prob
lems or errors.
JMS Retry Handling
Note the following behavior, which can be observed in message monitoring if you have configured a Retry
Interval in the adapter:
The following figure shows a straightforward case when JMS queues are configured during message
processing between a sender and a receiver.
In the setup shown, integration flow 1 receives a message from a sender, processes it, and writes the result
to JMS queue 1 (using a JMS receiver adapter), from where it is picked up by integration flow 2 (using a
JMS sender adapter). The latter processes the message and writes it to another queue, JMS queue 2
(using a JMS receiver adapter). From there, integration flow 3 picks up the message (using a JMS sender
adapter), processes it, and sends it to a receiver.
Each integration flow generates a message processing log (MPL1, MPL 2, and MPL3). The following table
summarizes the resulting MPLs in our example:
Involved Message Processing Logs (MPLs)
MPL Description
MPL 1 Shows that message is received from sender and submit

ted to JMS queue queue1

MPL Description
MPL 2 Shows that message is received from JMS queue queue1

and submitted to JMS queue queue2

and submitted to receiver
MPLs for those messages that are reading from and writing into one queue (using the JMS sender,
respectively receiver adapter) are correlated with each other using a correlation ID. You can use the
Message Monitor or the OData API to search for messages that belong to one correlation ID. To get back to
our example, the MPLs are correlated in the following way:
○ MPL1 and MPL2 are correlated by a correlation ID (for example, by correlation ID: ABC)
○ MPL2 and MPL3 are correlated by another correlation ID (for example, by correlation ID: XYZ)
If an error occurs when sending the message to the receiver (for example, the receiver cannot be reached),
the following happens:
During a retry, the message is in status Retry. For each retry, a separate Run is generated and displayed in
the Monitoring application within one MPL (and can be accessed using one MPL ID).
5. Save and deploy the configuration of the channel editor.
Results
Managing Locks for JMS Dead Letter Handling
In certain cases, usage of the JMS sender adapter can cause a node failure. This can happen, for example, if the
JMS adapter tries repeatedly to process a failed (large) message. The classic approach in such cases is to
undeploy the integration flow and reprocess the message. However, if you do this, the content of the original
message is lost.
To avoid such situations, the JMS adapter provides the option Dead-Letter Queue (switched on by default). If
this option is selected, the message is stored in the dead-letter queue if it cannot be processed after two
retries.
To be more specific: The first retry of the message is executed with a delay of 7 minutes. If the message then
still fails, it is stored in the dead-letter queue and manual interaction is required to process the message again.
If you are running scenarios with the JMS sender adapter, the Managing Locks editor helps you deal with
messages that cannot be processed.
After the last retry, a lock entry is written, which can be investigated in the Message Monitoring application
under Managing Locks.
 Note
The lock entry is also visible under Managing Message Queues.

You can identify such lock entries by the following attributes:
Attribute Value
Component JmsDeadLetter
Entry The message ID.
 Note
You can use this value to search for the message under
Managing Message Queues.
Expires at No expiration date is displayed.
When you release the lock, the system starts retrying the message again.
Next Steps
 Note
Note that the following specific exchange properties are available to be used in context of the JMS adapter:
SAPJMSRetries, SAPJMSAlerttime, SAPJMSRetryAt
Refer to more information on the headers and exchange properties.
Related Information
https://blogs.sap.com/2017/07/17/cloud-integration-configure-dead-letter-handling-in-jms-adapter/
Defining a Send Step [page 359]
2.5.2.15 Configuring a Channel with ODC Adapter
Context
The ODC adapter enables you to communicate with systems that expose data through the OData Channel for
SAP NetWeaver Gateway. You must configure a channel with ODC adapter to connect to a service developed
using SAP NetWeaver Gateway. For more information, see OData Channel.

Procedure
2. In the General tab, choose Browse in the Adapter Type screen area.
3. In the Choose Adapter window, select ODC and choose OK.
4. Choose Adapter Specific tab.
5. Provide values in fields based on description in table.
Field Description
Address URL of the SAP NetWeaver Gateway OData Channel that

you are accessing
Client Backend sytem client that you want to connect to
Namespace Namespace of the service
Service Name Name of the service
Version Version of the service
Credential Name Alias that you used while deploying basic authentication
credentials
Operation Select the operation that you want to perform from the
dropdown list.
Resource Path Path to the resource that you want to perform the opera
tion on
6. In the <EDMX> field, choose Select.
You see a prompt to connect to the system.

7. Provide values in fields based on description in table and choose Finish.
Field Description
Address URL of the system that you are connecting to
Client Backend system client that you are connecting to
Username User name for authentication
Password Relevant password for the specified username

8. Save or deploy the integration flow.
2.5.2.16 Configuring a Channel with LDAP Adapter
Prerequisites
You have created an integration project and integration flow.
Context
The LDAP adapter enables you to communicate with systems that expose data through LDAP service.
In case you have input messages in different formats, you need to use a mapping step to create a target
payload that can be recognized by the LDAP adapter. You can use this schema as a template for the target in
mapping step.

<schema xmlns="http://www.w3.org/2001/XMLSchema">
<element name="Schema">
<complexType>
<sequence>
<element name="DistinguishedName" maxOccurs="1" minOccurs="1"
type="string"/>
<element name="ObjectClass" maxOccurs="1" minOccurs="0"
type="string"/>
<element name="Attributes" maxOccurs="1" minOccurs="1">
<complexType>
<sequence>
<element name="cn" type="string" maxOccurs="1"
minOccurs="0"></element>
<element name="sAMAccountName" type="string"
maxOccurs="1" minOccurs="1"></element>
<element name="sn" type="string" maxOccurs="1"
<element name="givenName" type="string"
<element name="displayName" type="string"
<element name="name" type="string" maxOccurs="1"
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
The LDAP adapter is available only in the receiver channel.

 Note
You cannot update multiple records in a single processing cycle. You can only perform a given operation on
one record at a time.
 Remember
You must use SAP Cloud Platform Connector for connecting to an LDAP service using the LDAP adapter.
LDAP adapter supports version 2.9 or higher versions of the cloud connector.
For more information, see SAP Cloud Platform Connector.
Procedure
3. In the Choose Adapter window, select LDAP and choose OK.
4. Choose the Adapter Specific tab.
Field Description
Address Enter the URL of the LDAP directory service that you are
connecting to
Proxy Type Select the proxy type that you want to use. Currently, only
on premise option is supported.
Authentication Select the authentication type that you want to use. Cur
rently, only simple option is supported.
Credential Name Enter the credential name that you have deployed in the
tenant
Operation Select the operation that you want to perform. Currently,

only Insert and Modify operations are supported.
Input Type Select the type of input that you are providing (Applicable
only for Insert operation)

2.5.2.16.1 Specific Use Cases for LDAP Adapter
Using Input Type Java (JNDI) Attributes
The LDAP adapter supports input via JNDI attributes. If you choose this as the input type, you use a script step
to obtain values to attributes that are then passed to the LDAP service.
For example, consider this script being used in a Script step.
importClass(com.sap.gateway.ip.core.customdev.util.Message);
importClass(java.util.HashMap);
importClass(javax.naming.directory.Attribute);
importClass(javax.naming.directory.BasicAttribute);
importClass(javax.naming.directory.BasicAttributes);
importClass(javax.naming.directory.Attributes);
function processData(message) {
var body = message.getBody();
var dn= "cn=Markus,ou=users,dc=testcompany,dc=com";
var givenNameAttr = new BasicAttribute("givenName", "Jack");
var displayNameAttr = new BasicAttribute("displayName", "Reacher");
var telephoneNumberAttr = new BasicAttribute("telephoneNumber",
"100-100-100");
var attributes = new BasicAttributes();
attributes.put(givenNameAttr);
attributes.put(displayNameAttr);
attributes.put(telephoneNumberAttr);
attr =new BasicAttribute("title", "Developer");
attributes.put(attr);
attr =new BasicAttribute("sn", "Brutus");
var resultingMap = new HashMap();
resultingMap.put("dn", dn);
resultingMap.put("attributes", attributes);
message.setBody(resultingMap);
return message;
}
In the script, the values for attributes givenName, displayName and telephoneNumber are declared in the
script before they are passed to the LDAP adapter. Similarly, you can also create a script where these values
are dynamically fetched during runtime.
Adding Attributes to Template Schema
The example schema contains a set of attributes for a given record. In case you want the schema to contain
additional attributes, you can manually edit the schema before using it in the mapping step.
For example, if you want to add a field, telephone number, you can add an element in the schema under the
sequence element.
Here’s how the edited schema will look like:

<complexType>
<sequence>
type="string"/>
type="string"/>
<complexType>
<sequence>
<element name="sAMAccountName" type="string"></
element>
<element name="sn" type="string"></element>
<element name="givenName" type="string"></element>
<element name="displayName" type="string"></element>
<element name="name" type="string"></element>
<element name="telephoneNumber" type="string"></
element>

</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
Add Additional Attributes to the Message after Mapping using Script
Let us consider a scenario where you want to add an attribute to the message (payload) that you are sending to
the LDAP service. For example, you want to add a password attribute. Due to security concerns, you should
encode the password before you add it.
You can achieve this by adding a Script step after the mapping step in the integration flow. Here's an example of
the script that you can use in the Script step:
import com.sap.gateway.ip.core.customdev.util.Message;
import java.util.HashMap;
import javax.xml.bind.DatatypeConverter;
import javax.naming.directory.Attribute;
import javax.naming.directory.Attributes;
import javax.naming.directory.BasicAttribute;
import javax.naming.directory.BasicAttributes;
def Message processData(Message message)
{
Attributes attributes = new BasicAttributes();
String quotedPassword = '"'+"Initial@1"+'"';
byte[] unicodePasswordByteArray = quotedPassword.getBytes("UTF-16LE");
attributes.put(new BasicAttribute("unicodePwd", unicodePasswordByteArray));
message.setHeader("SAP_LDAPAttributes",attributes);
return message;
}

Using Modify Operation to Change DN
You can use the Modify operation to change the DN of an LDAP record. You can do this by adding the tag
<DistinguishedName_Previous> to the input payload with the old DN. Specify the modified DN in
<DistinguishedName> tag and perform the Modify operation.
Here's an example that shows a sample input payload for modiying the DN of an LDAP record:

<Schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DistinguishedName>CN=CMD ABC,CN=Users,DC=dev109,DC=dev-
wdf,DC=sap,DC=corp</DistinguishedName>
<DistinguishedName_Previous>CN=CMD,CN=Users,DC=dev109,DC=dev-
wdf,DC=sap,DC=corp</DistinguishedName_Previous>
<ObjectClass>user</ObjectClass>
<Attributes>
<mail>123@xyz.com</mail>
<telephoneNumber>123456789</telephoneNumber>
</Attributes>
</Schema>
2.5.2.17 Configure a Channel with XI Adapter
Related Information
Configure a Channel with XI Sender Adapter [page 187]

Configure Channel with XI Receiver Adapter [page 193]
2.5.2.17.1 Configure a Channel with XI Sender Adapter
The XI sender adapter allows you to connect a tenant to a local Integration Engine in a sender system.
The adapter supports communication over the XI 3.0 protocol.
 Note
● A feature for a particular adapter or step was released after you created the corresponding shape in
● You are using a product profile other than the one expected.

Consider the following when using the XI adapter.
● Avoid to change the temporary storage location for operative scenarios (or do this very carefully).
Such an action can result in data loss. The reason s that outdated messages (which will not be retried any
more) can still be stored there, also when you have changed the Temporary Storage attribute in the
meantime. When you plan to change this attribute, make sure there are no messages any more in the
originally configured temporaty storage.
● Avoid changing (sender or receiver) participant or channel name in the integration flow.
The name of the configured Temporary Storage is generated based on these names. If you change these
names in the integration flow model and deploy the integration flow again, a temporary storage is
generated with the new name. However, there can still be messages in the old storage. These messages will
not be retried any more after the new storage has been created.
● Apply the right transaction handling.
JMS queues and data stores support different transactional processing. As there are additional
implications of each transactional processing option with other integration flow steps, we urgently
recommend to follow these rules:
○ If as Temporary Storage you select JMS Queue in an XI receiver adapter and the XI adapter is used in a
sequential multicast or splitter pattern, as Transaction Handling you have to select Required for JMS.
If as Temporary Storage you select Data Store in an XI receiver adapter and the XI adapter is used in a
sequential multicast or splitter pattern, as Transaction Handling you have to select Required for JDBC.
For the XI sender adapter no transaction handler is required.
For the XI receiver adapter no transaction handler is required if the XI adapter is not used in a
sequential multicast or in a split scenario.
There is no distributed transaction support. Therefore, you cannot combine JMS and JDBC
transactions. As a consequence, transactional behavior cannot be guaranteed in scenarios using the XI
receiver adapter with JMS storage in multicast scenarios together with flow steps that need a JDBC
transaction handler (like, for example, Data Store or Write Variables).
Note the following limitations.
● The XI adapter does not support acknowledgements.

● When you have selected Exactly Once (as Quality of Service), currently only AtLeastOnce (ALO) is
supported by the XI adapter, no ExactlyOnce (EO) in the strict sense. That means if the sender system
sends the same message multiple times, the XI adapter forwards all these messages to the receiver
(multiple times).
ExactlyOnceInOrder (EOIO) is not supported.
When you have created a sender channel (with XI adapter selected), you can configure the following attributes.

Connections Tab
Parameters and Values of Sender XI Adapter/Connection
Address Address under which a sender system can reach the tenant

● Client Certificate: Sender authorization is checked on the tenant by evaluating the sub
ject/issuer distinguished name (DN) of the certificate (sent together with the inbound
request). You can use this option together with the following authentication option: Cli
ent-certificate authentication (without certificate-to-user mapping).
● User Role: Sender authorization is checked based on roles defined on the tenant for the
user associated with the inbound request. You can use this option together with the fol
lowing authentication options:
The authorizations for the user are checked based on user-to-role assignments de
fined on the tenant.
The authorizations for the user derived from the certificate-to-user mapping are
checked based on user-to-role assignments defined on the tenant.
● Client Certificate Authorization

Allows you to select one or more client certificates (based on which the inbound authori
zation is checked).
Choose Add to add a new certificate for inbound authorization for the selected adapter.
You can then select a certificate stored locally on your computer. You can also delete
certificates from the list.
For each certificate, the following attributes are displayed: Subject DN (information used
to authorize the sender) and Issuer DN (information about the certificate authority that
issues the certificate).
● User Role
The role ESBMessaging.send is provided by default. It is a predefined role provided by
SAP which authorizes a sender system to process messages on a tenant. However, us
ing SAP Cloud Platform Cockpit, you can also define custom roles for the runtime node
as well. When choosing Select, a selection of all custom roles defined that way is offered.
 Note
Note the following:
○ You can also type in a role name. This has the same result as selecting the role
from the value help: If the inbound request is authenticated, depends on the
correct user-to-role assignment defined in SAP Cloud Platform Cockpit.
○ When you externalize the User Role, in the integration flow configuration the
value help for roles is offered as well.
○ If you have selected a product profile for SAP Process Orchestation, the value
help will only show the default role ESBMessaging.send.

Delivery Assurance Tab
Parameters and Values of Sender XI Adapter/Delivery Assurance

Quality of Service Defines how the message (from the sender) is processed by the tenant.
● Best Effort
The message is sent synchronously; this means that the tenant waits for a re
sponse before it continues processing.
No temporaty storage of the message needs to be configured, as message re
quest and response are processed immediately after another.
● At Least Once
The message is sent asynchronously. This means that the tenant does not wait
for a response before continuing processing. It is expected that the receiver
guarantees that the message is processed exactly once.
This option guarantees that the message is processed at least once on the ten
ant. If a message with identical message ID is received multiple times from a
sender,, all of them will be processed.
If you choose this option, the message needs to be temporarily stored on the
tenant (in the storage configured under Temporary Storage). As soon as the
message is store there, the sender receives successfully received status mes
sage. If an error occurs, the message is retried from the temporary storage.
● Exactly Once (Only possible if as Temporary Storage the option Data Store is se
lected)
for a response before continuing processing.
This option guarantees that the message is processed exactly once on the ten
sender, only the first one will be processed. The subsequent messages can be
identified as duplicates (based on the value of the message header
SapMessageIdEx, see below) and will not be processed.
 Note
For Exactly Once handling, the sender XI adapter saves the protocol-spe
cific message ID in the header SapMessageIdEx. If this header is set, XI
receiver uses the content of this header as the message ID for outbound
communication. Usually, this is the desired behavior and enables the re
ceiver to identify any duplicates. However, if the sender system is also the
receiver system, or several variants of the message are sent to the same
system (for example, in an external call or multicast), the receiver system
will incorrectly identify these messages as duplicates. In this case, the
header SapMessageIdEx must be deleted (for example, using a content
modifier) or overwritten with a new generated message ID. This deactivates
Exactly Once processing (that is, duplicates are no longer recognized by the
protocol).

Temporary Storage Temporary storage location for messages that are processed asynchronously. Mes
sages for which processing runs into an error can be retried from the temporary
(only if as Quality of Service the op
storage.
tion Exactly Once is selected)
You can choose among the following storage types:
● Data Store
The message is temporarily stored in the database of the tenant (in case of an
error). In case of successful message processing, the message is immediately
removed from the data store.
You can monitor the content of the data store in the Monitor section of the Web
UI under Manage Stores in the Data Stores tile.
 Note
The data store name is automatically generated and contains the following
parts:
<name of participant connected with XI adapter>_<

XI channel name>
This automatically generated name is subject to a length restriction and

must be no more than 40 characters (including the underscore). If the data
store name exceeds this limit, you must shorten the participant name or
channel name accordingly.
Below the data store name, you find a reference to the associated integra
tion flow in the following form: <integration flow name>/XI
● JMS Queue
The message is stored temporarily in a JMS queue on the configured message
broker.
If possible, use this option as it comes with a better performance.
UI under Manage Stores in the Message Queues tile.
 Note
The name of the JMS queue is automatically generated and contains the
following parts:
XI.<Integration Flow Name>.<Channel Name>.<Guid>
 Note
This option is only available if you have an Enterprise Edition license.

Retry Interval (in min) Enter a value for the amount of time to wait before retrying message delivery.
Exponential Backoff Select this option to double the retry interval after each unsuccessful retry.
Maximum Retry Interval (in min) You can set an upper limit on that value to avoid an endless increase of the retry in
(only configurable when Exponential terval. The default value is 3600 seconds.
Backoff is selected)
Dead-Letter Queue Select this option to place the message in the dead-letter queue if it cannot be proc
essed after three retries caused by an out-of-memory. Processing of the message is
(only if as Temporary Storage the op
stopped then.
tion JMS Queue is selected)
In such cases, a lock entry is created which you can view and release in the Monitor
section of the Web UI under Managing Locks.
Use this option to avoid out-of-memory situations (caused in many cases by large
messages).
For more information, read the SAP Community blog Cloud Integration – Configure
Dead Letter Handling in JMS Adapter .
Encrypt Message during Persistence Select this option in case the messages should be stored in an encrypted way during
(only in case you have selected certain processing steps.
Exactly Once as Quality of Service)
2.5.2.17.2 Configure Channel with XI Receiver Adapter
The XI receiver adapter allows you to connect a tenant to a local Integration Engine in a receiver system.
 Note

● In the current release, you cannot dynamically configure any parameters of the adapter.
● Currently, the adapter is not supported in the Request-Reply and the Send step.
● In the current version, explicit retry configuration using retry headers is not supported.
● When you have selected Exactly Once (as Quality of Service), currently only AtLeastOnce (ALO) is
supported by the XI adapter, no ExactlyOnce (EO) in the strict sense. That means if the sender system
sends the same message multiple times, the XI adapter forwards all these messages to the receiver
(multiple times).
● ExactlyOnceInOrder (EOIO) is not supported by the XI adapter.
When you have created a receiver channel (with XI adapter selected), you can configure the following
attributes.

Connection Tab
Parameters of Receiver XI Adapter/Connection

Address Address under which the local integration engine of the receiver system can be called
The integration engine address is composed in the following way:
https://<host name>:<port>/sap/xi/engine?type=receiver&sap-
client=<client>
 Note
You can find out the constituents (HTTPS port) of the URL by choosing transaction SMICM in the receiver
system and choosing Goto Services .
The endpoint URL that has actually been used at runtime is displayed in the message processing log (MPL) in
the message monitoring application (MPL property RealDestinationUrl).
This parameter can be configured dynamically.
● Select Internet if you are connecting to a cloud system.

● Select On-Premise if you are connecting to an on-premise system.
 Note
If you select the On-Premise option, the following restrictions apply to other parameter values:
○ Do not use an HTTPS address for Address, as it leads to errors when performing consistency
○ Do not use Certificate-Based Authentication as the Authentication Type, as it leads to errors
when performing consistency checks or during deployment
 Note
If you select the On-Premise option and use the SAP Cloud Connector to connect to your on-premise
system, the Address field of the adapter refers a virtual address which has to be configured in the
SAP Cloud Connector settings.
Location ID To connect to an ASP Cloud Connector instance associated with your account, enter the location ID that you
only in case defined for this instance in the destination configuration on the cloud side. You can also enter $
On-Premise {header.headername} or ${property.propertyname} to dynamically read the value from a
is selected header or a property.
for Proxy
Type.

Authenticat Defines the tenant authenticates itself against the receiver.

ion Type
● None
No authentication is configured.
● Basic Authentication
The tenant authenticates itself against the receiver based on user credentials (user and password).
Note that when this authentication option is selected, the required security artifact (User Credentials)
has to be deployed on the tenant.
● Certificate-Based Authentication
The tenant authenticates itself against the receiver based on X.509 certificates.
Note that when this authentication option is selected, the required security artifact (Keystore) has to be
deployed on the tenant.
● Principal Propagation
The tenant authenticates itself against the receiver by forwarding the principal of the inbound user to the
cloud connector, and from there to the back end of the relevant on-premise system. You can only use
principal propagation if you have selectedBest Effort as the Quality of Service.
 Note
This authentication method can only be used with the following sender adapters: HTTP, SOAP, IDoc,
XI sender (and Quality-of-Service Best Effort)
 Note
If it takes longer than 30 minutes to process the data between the sender and receiver channel, the
token for principal propagation expires, which leads to errors in message processing.
For special use cases, this authentication method can also be used with the AS2 adapter.
Credential Name of User Credentials artifact that needs to be deployed separate on the tenant (it contains user name
Name and password for the user to be authenticated).
(Only when This parameter can be configured dynamically.

you have
selected
Basic
Authenticat
ion as
Authenticat
ion Type)

Private Key Optional entry to specify the alias of the private key to be used for authentication. If you leave this field empty,
Alias the system checks at runtime for any valid key pair in the tenant keystore.

you have
selected
Certificate-
Based
Authenticat
ion as
Authenticat
ion Type)
Compress Enables the tenant to send compressed request messages to the receiver (which acts as WS provider) and to
Message indicate to the receiver that it can handle compressed response messages.
Allow Used for enabling chunking of data while sending messages.

Chunking
Clean Up Select this option to clean up the adapter-specific headers after the receiver call.
Request
Headers

XI ● Communication Party
Identifiers Specifies the Communication Party header value of the request message sent to the receiver system.
for Sender A communication party typically represents a larger unit involved in an integration scenario. You usually
use a communication party to address a company.
An XI mes
sage con
● Communication Component
tains spe
Specifies the Communication Component header value of the request message sent to the receiver sys
cific header
tem.
elements
You typically use a communication component to address a business system as the sender or receiver of
that are
messages.
used to ad
dress the
sender or a
receiver of
the mes
sage, such
as commu
nication
party, com
munication
compo
nent, and
service in
terface. For
more infor
mation on
the con
cepts be
hind these
entities,
see the
documen
tation of
SAP Proc
ess Integra
tion at
https://
help.sap.co
m/viewer/
product/
SAP_NET
WEA
VER_PI/
ALL/.

Identifiers Specifies the Communication Party header value of the response message received from the receiver
for Receiver system.
A communication party typically represents a larger unit involved in an integration scenario. You usually
An XI mes
sage con
tains spe
cific header
Specifies the Communication Component header value of the response message received from the re
elements
ceiver system.
that are
used to ad
messages.
dress the
sender or a
receiver of
 Note
the mes
sage, such To get this information, go to the receiver system and choose transaction SLDCHECK. In section
as commu LCR_GET_OWN_BUSINESS_SYSTEM, you find the business system ID (which typically has the form
nication <SID>_<client>).
party, com
● Service Interface and Service Interface Namespace
munication
These attributes specify the service interface that determines the data structure of the response mes
compo
sage received from the receiver system.
nent, and
The receiver interface is described according to how interfaces are defined in the Enterprise Services Re
service in
pository, that means, with a name and a namespace.
terface. For
more infor
mation on
the con
cepts be
hind these
entities,
see the
documen
tation of
SAP Proc
ess Integra
tion at
https://
help.sap.co
m/viewer/
product/
SAP_NET
WEA
VER_PI/
ALL/.

Parameters of Receiver XI Adapter/Delivery Assurance

XI Message Select this option to specify how the XI Message ID shall be defined.
ID
You can choose among the following options:
Determinati
on ● Generate (default)
Generates a new XI message ID.
● Reuse
Take over the message ID passed with the header SAPMessageIdEx. If the header is not available in
runtime, a new message ID is generated
● Map
Maps a source message ID to the new XI message ID.
For more information on how to use this option in an end-to-end scenario, check out the SAP Community
blog Cloud Integration – Configuring ID Mapping in XI Receiver Adapter
Source for To map the source message ID to the XI message ID enter:

XI Message
${header.headername} or ${property.propertyname}
ID (only in
case you
 Note
selected
Map as XI If no header or property is available at runtime, a new message ID is generated.
Message ID
Determinati
on)
Quality of Defines how the message (from the tenant) is expected to be processed by the receiver.
Service
● Best Effort
The message is sent synchronously; this means that the tenant waits for a response before it continues
processing.
No temporary storage of the message needs to be configured, as message request and response are
processed immediately after another.
● Exactly Once
The message is sent asynchronously. This means that the tenant does not wait for a response before
continuing processing. It is expected that the receiver guarantees that the message is processed exactly
once.
If you choose this option, the message needs to be temporarily stored on the tenant (in the storage con
figured under Temporary Storage). As soon as the message is store there, the sender receives success
fully received status message. If an error occurs, the message is retried from the temporary storage.

Temporary Temporary storage location for messages that are processed asynchronously. Messages for which processing
Storage runs into an error can be retried from the temporary storage.
(only if as You can choose among the following storage types:

Quality of
● Data Store
Service the
The message is temporarily stored in the database of the tenant (in case of an error). In case of success
option
ful message processing, the message is immediately removed from the data store.
Exactly
You can monitor the content of the data store in the Monitor section of the Web UI under Manage Stores
Once is se
in the Data Stores tile.
lected)
 Note
The data store name is automatically generated and contains the following parts:
<name of participant connected with XI adapter>_< XI channel name>
This automatically generated name is subject to a length restriction and must be no more than 40
characters (including the underscore). If the data store name exceeds this limit, you must shorten
the participant name or channel name accordingly.
Below the data store name, you find a reference to the associated integration flow in the following
form: <integration flow name>/XI
● JMS Queue
The message is stored temporarily in a JMS queue on the configured message broker.
in the Message Queues tile.
 Note
The name of the JMS queue is automatically generated and contains the following parts:
 Note
Retry Enter a value for the amount of time to wait before retrying message delivery (in case of an error).
Interval (in
min)
Exponential Select this option to double the retry interval after each unsuccessful retry.
Backoff

Maximum You can set an upper limit on that value to avoid an endless increase of the retry interval. The default value is
Retry
3600 seconds.
Interval (in
min)
(only con
figurable
when
Exponential
Backoff is
selected)
Dead-Letter Select this option to place the message in the dead-letter queue if it cannot be processed after three retries
Queue caused by an out-of-memory. Processing of the message is stopped then.
(only if as In such cases, a lock entry is created which you can view and release in the Monitor section of the Web UI
Temporary under Managing Locks.
Storage the
Use this option to avoid out-of-memory situations (caused in many cases by large messages).
option JMS
Queue is For more information, read the SAP Community blog Cloud Integration – Configure Dead Letter Handling in
selected) JMS Adapter .
Encrypt Select this option in case the messages should be stored in an encrypted way during certain processing
Message steps. It is recommended to choose this option if the message can contain sensitive data. Note that this set
during ting might decrease performance of the integration scenario.
Persistence
(only in
case you
have se
lected
Exactly
Once as
Quality of
Service)
2.5.2.18 Configuring a Channel with RFC Receiver Adapter

You can use Remote Function Call (RFC) to integrate on-premise ABAP systems with the systems hosted on
the cloud using the Cloud connector.
Prerequisites
Ensure that following prerequisites are met:
● You have defined the RFC destination in the SAP Cloud connector for your application. To create
destinations you need to either have administrator or developer role in SAP Cloud Platform cockpit.

 Note
For more information on how to create RFC destinations in the Cloud connector, see Creating an RFC
Destination [page 680] .
● You have opened the integration flow in the editor for editing purposes.
● SAP Netweaver ABAP system is up and running.
● You have generated the remote function module XSD file. For more information on how to generate XSD
file, see Generating XSD/WSDL for Function Modules Using ESR (Process Integration) [page 680].
Context
RFC executes the function call using synchronous communication, which means that both systems must be
available at the time the call is made. When the call is made for the function module using the RFC interface,
the calling program must specify the parameters of the connection in the form of an RFC destination. RFC
destinations provide the configuration needed to communicate with an on-premise ABAP system through an
RFC interface.
The RFC destination configuration settings are used by the SAP JAVA Connector (SAP JCo) to establish and
manage the connection.
 Remember
● The RFC adapter supports SAP NetWeaver 7.31 and higher.

● From RFC adapter version 1.2.0, function modules that contains "/" in their names are also supported.
For these function modules you need to replace "/" with "_-" (underscore and hyphen) in the input
XML.
● The date provided in the input XML must be of format "YYYY-MM-DD".
● If the parameters of the ABAP function are changed, the integration flow containing the RFC adapter
must be redeployed for the new parameters to be reflected in the output XML. However, this doesn't
hold good in case the RFC adapter is configured with dynamic destination. For the changed parameters
to be reflected in the output, the integration flow must be redeployed with the static destination only.
Parameter and Value of the RFC Receiver Adapter
Field Description
Destination RFC destination configured in SAP Cloud Platform for your

application.

Field Description
Send Confirm Transaction (Applicable to BAPI functions) By default this option is disa
bled. You can enable this option if you want to support BAPI
functions that require BAPI_TRANSACTION_COMMIT to be
invoked implicitly by the RFC receiver adapter.
 Note
Ensure the following ABAP functions are whitelisted in
Cloud connector before using this option:
● BAPI_TRANSACTION_COMMIT
● BAPI_TRANSACTION_ROLLBACK
 Caution
If you enable this option for non-BAPI functions,
BAPI_TRANSACTION_COMMIT can still be invoked,
which is redundant and hence may impact RFC function
execution time.
 Note
You can create dynamic destinations by using regular expressions (header, property) in the Content
Modifier. To do that, you need to first select the Content Modifier in the integration flow. Then go to Message
Header and assign corresponding value to the header name as the destination name. Select your RFC
adapter and assign dynamic destination by using the expression: ${header/property.<header/property
name>}. For example ${header.abc} or ${property.abc} where abc is the value of the header or property.
Procedure
1. In the Model Configuration editor, double-click the channel that you want to configure.
2. Go to General tab. Select RFC from the Adapter Type dropdown.
3. Go to the Adapter Specific tab and enter the value for the field shown in the table below:
Field Description

application.

Field Description
Send Confirm Transaction (Applicable to BAPI functions) By default this option is dis
abled. You can enable this option if you want to support
BAPI functions that require BAPI_TRANSACTION_COM
MIT to be invoked implicitly by the RFC receiver adapter.
 Note
○ BAPI_TRANSACTION_COMMIT
○ BAPI_TRANSACTION_ROLLBACK
 Caution
which is redundant and hence may impact RFC func
tion execution time.
 Note
Modifier. To do that, you need to first select the Content Modifier in the integration flow. Then go to
Message Header and assign corresponding value to the header name as the destination name. Select
your RFC adapter and assign dynamic destination by using the expression: ${header/
property.<header/property name>}. For example ${header.abc} or ${property.abc} where abc is the
value of the header or property.
2.5.2.19 Configuring a Channel with ProcessDirect Adapter

Use ProcessDirect adapter (sender and receiver) to establish fast and direct communication between
integration flows by reducing latency and network overhead provided both of them are available within a same
tenant.
Prerequisites
● Deployment of the ProcessDirect adapter must support N:1 cardinality, where N (producer) → 1
(consumer).
 Caution
Multiple producers can connect to a single consumer, but the reverse is not possible. The cardinality
restriction is also valid across integration projects. If two consumers with the same endpoint are
deployed, then the start of the second consumer fails.

● The Address mentioned in ProcessDirect configuration settings must match for producer and consumer
integration flows at any given point.
Context
ProcessDirect Receiver Adapter: If the ProcessDirect adapter is used to send data to other integration flows,
the integration flow is considered as a producer integration flow. In this case, the integration flow has a receiver
ProcessDirect adapter.
ProcessDirect Sender adapter: If the ProcessDirect adapter is used to consume data from other integration
flows, the integration flow is considered as a consumer integration flow. In this case, the integration flow has a
sender ProcessDirect adapter.
The ProcessDirect adapter supports the following features:
● Decompose large integration flows: You can split a large integration flow into smaller integration flows
and maintain the in-process exchange without network latency.
● Customize the standard content: SAP Cloud Platform Integration enables integration developers to
customize their integration flows without modifying them entirely. The platform provides plugin
touchpoints where integration developers can add custom content. This custom content is currently
connected using HTTP or SOAP adapters. You can also use the ProcessDirect adapter to connect the
plugin touchpoints at a lower network latency.
● Allow multiple integration developers to work on the same integration flow: In some scenarios,
integration flows can be large (100 steps or more), and if they are owned or developed by just one
integration developer this can lead to an overreliance on one person. The ProcessDirect adapter helps you
to split a large integration flow into smaller parts that can be owned and managed by multiple integration
developers independently. This allows several people to work on different parts of the same integration
flow simultaneously.
● Reuse of integration flows by multiple integration processes spanning multiple integration projects:
Enables the reuse of integration flows such as error handling, logging, extension mapping, and retry
handling across different integration projects and Camel context. Integration developers therefore only
need to define repetitive logic flows once and can then call them from any integration flow using the
● Dynamic endpoint: Enables the producer integration flow to route the message dynamically to different
consumer integration flow endpoints. The producer integration flow look ups the address in the headers,
body, or property of the exchange and the corresponding value is then resolved to the endpoint to which
the exchange is to be routed.
● Multiple MPLs: MPL logs are interlinked using correlation IDs.
● Transaction processing: Transactions are supported on integration flows using the ProcessDirect adapter.
However, the scope of the transaction is isolated and restricted to a single integration flow.
● Header propagation: Header propagation is not supported across producer and consumer integration
flows unless configured in <Allowed Header(s)> in the integration flow's runtime configuration.
● Property propagation: Property propagation is not supported across producer and consumer integration
flows, except for SAP_SAPPASSPORT property. This property is for internal use only and users are not
allowed to modify it.
 Tip
ProcessDirect adapter improves network latency, as message propagation across integration flows do not
involve load balancer. For this reason, we recommend that you consider memory utilization as a parameter

in scenarios involving heavy payloads and alternatively use HTTP adapter in such scenarios because, the
behavior will be the same.
 Restriction
Cyclic loop deployment of integration flows must be avoided.
Procedure
1. In the Model Configuration editor, double-click the channel that you want to configure.
2. Go to General tab. Select ProcessDirect from the Adapter Type dropdown.
3. Go to the Adapter Specific tab and enter the value for the field shown in the table below:
Parameters of the ProcessDirect Adapter
Address URL of the target system that you are connecting to. For
example, /localiprequiresnew.
 Note
It may or may not start with "/". It can contain alpha
numeric characters and special characters such as
underscore "_" or hyphen "-". You can also use simple
expressions, for example, ${header.address}.
 Remember
○ If the consumer has an <Escalated End Event> in the <Exception Sub-Process>, then in
case of exception in the consumer, the MPL status for the producer varies based on the following
cases:
○ If the producer integration flow starts with <Timer>, the MPL status for the consumer will be
Escalated and for Producer, it will be Completed.
○ If the producer integration flow starts with <HTTP> Sender, the MPL status for the consumer
will be Escalated and for producer, it will be Failed.
○ The combination of <Iterating Splitter> and <Aggregator> in the producer integration
flow might generate an extra MPL (Aggregator MPL) due to the default behavior of Aggregator.
○ The <Send> component is incompatible with the ProcessDirect adapter as the adapter supports
asynchronous mode for message exchange and it expects a response.
To learn more about the adapter, see blog on ProcessDirect Adapter in SAP Community .

2.5.3 Defining Message Transformers
Context
Procedure
2.5.3.1 Assigning Mapping
Prerequisites
● You have configured the connections to an On-Premise repository if you have to import mapping from that
repository into the workspace.
 Note
For more information on setting the connections to the repository, see the task 'Setting the
Connections to the External Repository' in Configuring the Tool Settings [page 19]. You can import
message mappings (.mmap) from ES Repository with server version 7.1 onwards, and operation
mapping from ES Repository with server version 7.3 EHP1 SP3 .
● You have imported the mappings to your local workspace from the On-Premise repository.
 Note
For more information about how to import mappings from the ES Repository, see Importing SAP
NetWeaver PI Objects from On-Premise Repository [page 26].
Context
You perform this task to assign a mapping that is available in your local workspace.
Your local workspace can contain mappings that are already imported from an external repository, such as the
ES Repository, or you have obtained them from some other integration project.

 Caution
You have to be cautious in distributing the mappings imported from ES Repository if they contain any
sensitive data. Although you securely import mappings from the repository by providing the user
credentials, copying the imported mappings from one Integration Project to another does not require any
authorization.
In an integration flow project, the src.main.resources.mapping package can contain message mapping
(.mmap), operation mapping (.opmap), XSL mapping and XSLT mapping.
Procedure
1. To add a mapping element to an integration flow model, perform the steps below:
a. In the Model Configuration editor, select the sequence flow within the pool.
b. From the context menu of the sequence flow, choose Add Message Transformers and then select
Mapping.
2. Select the mapping in the integration flow.
3. From the context menu, you can choose one of the mapping options: Assign Mapping, New Message
Mapping, Switch to XSLT Mapping or Switch to Operation Mapping
4. Open the Properties view.
5. If you want to assign mapping then execute the following substeps:
a. To select a mapping for the integration flow, choose Browse….
 Note
You can assign an operation mapping only if the sender and receiver channel is configured with
SOAP adapters.
b. In the Choose Mapping dialog, choose the dropdown icon and select Local to obtain the mapping.
 Note
Local option shows mapping of different types, such as message mapping (.mmap), operation
mapping (.opmap), XSL mapping and XSLT mapping, available within the current project.
c. Select a mapping.
d. Choose OK.
6.  Note
XSLT Mapping version 1.1 supports functions to set header, exchange properties.
It allows you also to access the partner directory.
You can set header and property as shown in the example below.
 Sample Code

<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

xmlns:hci="http://sap.com/it/"
exclude-result-prefixes="hci">
<xsl:param name="exchange"/>
<xsl:output method="xml" encoding="UTF-8" indent="no" />
<xsl:template match="/">
<xsl:value-of select="hci:setHeader($exchange, 'myname',
'myvalue')"/>
<xsl:value-of select="hci:setProperty($exchange, 'myname',
'myvalue')"/>
<Test1/>
</xsl:template>
</xsl:stylesheet>
Here the header/property name is myname and value is myvalue.
Execute the following substeps for XSLT mapping version 1.1:

a. From the context menu, choose Switch to XSLT Mapping.
b. In the Properties view, select either Integration Flow or Header as source for the mapping.
c. If you select header as source, then enter name for the header in the Header Name field.
 Note
To assign xslt mapping for partner directory, the valid format for value of header name is
pd:<Partner ID>:<Parameter ID>:<Parameter Type>, where the parameter type is either
binary or string. For example, the correct header name is pd:SenderABC:SenderXSD:Binary.
You can
To access access headers via the xsl:param element
For example, when you like to access the header myHeader, you need the following expression:
<xsl:param name="myHeader"/>
d. Choose OK.
 Note
○ To view or modify the definition of message mapping in the mapping editor, click Name in the
Properties view. If you have assigned an operation mapping, the navigation to the mapping editor is
not supported.
○ For XSLT mapping, you can select the output format of the message to be either string or bytes
from the Output Format field.
 Restriction
Message mapping does not work if the integration flow project contains whitespaces.
Related Information
Avoiding Encoding Issues [page 775]

2.5.3.2 Defining Content Modifier
Context
You can also use content modifier to define local properties for storing additional data during message
processing. These properties can be further used in connectors and conditions.
Example
In SFTP Connector, the user can specify the receiver file name as - File_${property.count}.txt.
In Router, the user can define the condition as ${property.count} = '5'.
Procedure
2. If you want to add a content modifier in the integration flow, choose Add Message Transformers
Content Modifier from the context menu of a connection within the pool.
3. Select the added content modifier in the integration flow model to configure it.
4. To configure the content modifier with a saved configuration that is available as a template, choose Load
Element Template from the context menu of the Content Modifier element.
5. In the Properties view, select the Header tab.
6. In the Action column you can either Create additional headers, set values for existing headers of messages
(by using constants, another header, an XPath, a property, an external parameter, or by forming an
expression).
a. To enter an XPath, select xpath in the Type column and browse for an XPath from the lookup in the
Value column.
 Note
○ The Data Type column is mainly used for the XPath type. The data type can belong to any Java
class. An example of a data type for an XPath is java.lang.String.
○ 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.
Note that data written into the message header at a certain processing step (for example, in a Content
Modifier or Script step) will also be part of the outbound message addressed to a receiver system.
Because of this, it is important to consider the following restriction regarding the header size if you use
an HTTP-based receiver adapter:
If the message header exceeds 8 KB, it might lead to situations that the receiver cannot accept the
inbound call. (Relevant for all http-based receiver adapters)
b. To enter a header, select header in the Type column, and browse for a header from the lookup in the
Value column.

 Note
○ This lookup dialog shows you a list of headers that you have specified:
○ In the Header tab page of Content Modifier flow steps
○ In the Allowed Headers field of the Runtime Configuration tab page
c. To enter a property, select property in the Type column and define a value based on the selected value
type.
d. To enter an external parameter, select external parameter in the Type column and define the parameter
key. For more information, see Externalizing Parameters of Integration Flow [page 375].
 Note
Defining multiple parameters in the same field or column is not supported for tables.
7. If you are using version 1.2 then you can specify name or expression of the header/property to Delete an
existing header/property through the Action column, by executing the following substeps.
a. If you click on the icon in Name field, then Specify Header or Expression dialog appears.
b. If you want to delete header using header name then enter the required name in Header field.
c. If you want to delete headers using expression then enter the required name or expression in
Expression field.
○ In Include field you can enter name or expression of the header you want to delete. For example, if
you enter 'test*', then all headers starting with test are deleted.
○ In Exclude field you can enter name or expression of the header you do not want to delete. For
example, if you enter 'test*', then all headers starting with test are not deleted.
8. In the same way as for headers, in Action column, the user can either Create additional properties, set
values for existing properties of messages (by using constants, another header, an XPath, a property, an
external parameter, or by forming an expression) or Delete properties as explained above, by selecting the
Property tab in the Properties view.
 Note
○ Special characters like {}, [] are not allowed in header name, for a header of type Constant.
○ Header values can be lost following the external system call, whereas properties will be available
for complete message execution.
○ During outbound communication, headers will be handed over to all message receivers and
integration flow steps, whereas properties will remain within the integration flow and will not be
handed over to receivers.
○ You must specify name of the property you want to delete.

10. To save the configuration of the modifier as a template, choose Save as Template from the context menu of
the Content Modifier element.
 Note
○ When you save the configuration of the Content Modifier element as a template, the tool stores the
template in the workspace as <ElementTemplateName>.fst.
○ If you add a content modifier without header, body and property then you cannot trace the
element.

 Example
Suppose the incoming message has the following information:
<order>
<book>
<BookID>A1000</BookID>
<Count>5<Count>
</book>
</order>
In the Body tab of the Content Modifier, you specify the content expected in the outgoing message. Keep a
placeholder for the header information to modify the content as shown below:
<invoice>
<vendor>${header.vendor}</vendor>
${in.body}
<deliverydate>${header.date}</delivery>
</invoice>
In the Header tab of the Content Modifier, enter the following:
Name Type Value
vendor constant ABC Corp
delivery date constant 25062013
The output message would look like this:
<invoice>
<vendor>ABC Corp</vendor>
<order>
<book>
<Count>5<Count>
</book>
</order>
<deliverydate>25062013</deliverydate>
</invoice>
Related Information
Content Modifier Basics [page 214]

Specifying Runtime Configuration [page 368]

2.5.3.2.1 Content Modifier Basics
An integration flow is a BPMN (Business Process Model and Notation)-like model that allows you to specify
how a message is to be processed on a tenant.
To interpret an integration flow model at runtime, it is transformed into an XML structure that is compatible
with Apache Camel (http://camel.apache.org ), an Open Source integration framework for Java that
supports the mediation and routing of messages of any format.
The only prerequisite for a message that is to be processed by the Camel framework is that it comprises the
following elements:
● Headers
Contain information related to the message, for example, information for addressing the message sender.
● Attachments
Contain optional data that is to be attached to the message.
● Body
Contains the payload (usually with the business-related data) to be transferred in the message.
seen as an abstraction of a message exchange process as it is executed by the Camel framework. An Exchange
is identified uniquely by an Exchange ID. In the Properties area of the Exchange, additional data can be stored
temporarily during message processing. This data is available for the runtime during the whole duration of the
message exchange.
You can use the Content Modifier step to modify a message by adding additional data to it.
More precisely, this step type allows you to modify the content of the following three data containers during
message processing:
● Message Header
You can add headers to the message, and edit and delete headers.
● Message Body
You can modify the message body part.
● Exchange Property
You can write data to the message exchange, and edit and delete the properties.
For example, you can retrieve the value of a particular element of the payload of an inbound message and write
this value to the header of the message (to make it available for subsequent processing steps).
You need to specify additional parameters in the Content Modifier step to tell the integration runtime how
exactly to access the data from the incoming message (which is to be written to one of the three data
containers above).
Here's a simple example to show how this works: Let's say you want to write the value of the element
CustomerNumber from an inbound XML message to the message header, to make it available for subsequent
process steps.
In this case, you could configure the Content Modifier as follows:
On the Message Header tab of the Content Modifier, add a new entry. Specify XPath as the Type (because you
want to address the CustomerNumber element in an incoming XML message). For Value, enter the exact XPath
expression that is to be used to address this element (for example, /Order/Customer/CustomerNumber). In an
additional field, you now need to specify the data format expected for the content of the CustomerNumber

element. To express that this is a String element, you need to specify a valid Java data type, which is
java.lang.string in this case. For Name, enter the desired name of the message header (which should
contain the CustomerNumber value), for example, CustomerNo.
Example
The following example shows how to modify both the header and body data container of a message using the
Content Modifier step.
Suppose that the incoming message has the following information:
<order>
<book>
<Count>5</Count>
</book>
</order>
On the Header tab of the Content Modifier, enter the following to write constant values to the message header:
Name Type Value
On the Body tab, keep placeholders for the header information specified in the first Content Modifier step ($
{header.vendor} and ${header.date}) to modify the content as shown below. Additionally, use a
placeholder ${in.body} for the incoming message.
<invoice>
${in.body}
<deliverydate>${header.delivery date}</delivery>
</invoice>
<invoice>
<order>
<book>
<Count>5</Count>
</book>
</order>
</invoice>

2.5.3.3 Defining Encoders
You use this task to encode messages using an encoding scheme to secure any sensitive message content
during transfer over the network.
Procedure
2. If you did not select the encoder pattern when creating the integration flow, choose Add Message
Transformers Encoder from the context menu of a connection within the pool.
3. Select the encoder in the integration flow model to configure it.
4. In the Properties view, select the encoding scheme from the dropdown list. You can select one of the
following encoding schemes:
○ Base64 Encode
Encodes the message content using base64.
○ GZIP Compress: Compresses the message content using GNU zip (GZIP).
○ ZIP Compress: Compresses the message content using zip (only zip archives with a single entry
supported).
○ MIME Multipart Encode: Transforms the message content into a MIME multipart message.
If you want to send a message with attachments, but the protocol (for example, HTTP or SFTP) does
not support attachments, you can send the message as a MIME multipart instead.
 Example
A message with the header Content-Type "text/plain" is sent to a MIME multipart encoder. The add
multipart headers inline functionality is activated.
 Sample Code
from("...").marshal().mimeMultipart("related", true, true, "(included|

x-.*)", true);
The resulting message body will be:
 Sample Code
Message Body
Message-ID: <...>
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_0_1134128170.1447659361365"
------=_Part_0_1134128170.1447659361365
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Body text
------=_Part_0_1134128170.1447659361365
Content-Type: application/binary
Content-Transfer-Encoding: binary

Content-Disposition: attachment; filename="Attachment File Name"
[binary content]
------=_Part_0_1134128170.1447659361365
Consider the input XML payload structure to the encoder:
<message>
Input for encoder
</message>
If you select Base64 Encode, the output message would look like this:
PG1lc3NhZ2U+DQoJSW5wdXQgZm9yIGVuY29kZXINCjwvbWVzc2FnZT4NCg==
Related Information
MIME Multipart Messages [page 217]
2.5.3.3.1 MIME Multipart Messages
A Multipurpose Internet Mail Extensions (MIME) multipart message allows you to combine different kinds of
content in one message (for example, plain text and attachments).
To mention a use case, if you want to send a message with attachments, but the protocol (for example, HTTP or
SFTP) does not support attachments, you can send the message as a MIME multipart instead.
With a multipart subtype you can specify how the different content types are combined as MIME multipart
message. The property Multipart Subtype in the Encoder step allows you to specify the Content-Type property
of the MIME message. For more information on the different options for Multipart Subtype, refer to the general
definition of the Multipart Content-Type.
An input message for the MIME Multipart Encoder step doesn’t have to be composed in a specific way.
An inbound message for a MIME Multipart Decoder step has to be a MIME multipart message. Hereby, the
multipart headers can either be stored as Camel headers or as part of the message body.
Usage of Dynamic Headers
You have the option to dynamically (based on the content of the processed message) add custom headers to a
MIME multipart message. Do enable this option, you have to activate Add Multipart Header Inline. In that case,
the option Include Headers is displayed.

You can now enter regular expressions for the headers which are to be added dynamically. With such regular
expressions (regex), you can define placeholders for the custom headers:
 Tip
Example:
When you enter for Include Headers the string (x-.*|myAdditionalHeader), all headers that start with
x- and the header myAdditionalHeader are added dynamically.
MIME Multipart Encoder
The following table summarizes how the Encoder step transforms the message depending on whether you
select or deselect the option Add Multipart Header Inline.
Encoder: Add Multipart Header Inline Option
Add Multipart Header Inline Description
Selected The Encoder transforms the inbound message into a new message where the message
body (of the resulting message) is a MIME multipart message with headers.
Body and attachments (if available) of the inbound message will be added as separate
parts of the multipart message. The attachments are removed from the resulting message.
Note that the message will also always be transformed into a MIME multipart message, re
gardless whether it contains attachments or not.
Deselected The following cases can occur:
● The inbound message has attachments: Encoder transforms message body and at
tachments of the inbound message into a MIME multipart message. The headers of
the multipart message will be added as Camel headers. The message body will be re
placed by the rest of the message.
● The inbound message has no attachments: Encoder does not change the inbound
message.
The following figures illustrate how the property Add Multipart Header Inline influences the processing of the
message.
Add Multipart Header Inline selected

Add Multipart Header Inline deselected
MIME Multipart Decoder
The following table summarizes how the Decoder step transforms the message depending on whether you
select or deselect the option Multipart Headers Inline.
Decoder: Multipart Headers Inline Option
Multipart Headers Inline Description
Selected The Decoder transforms the first part of the multipart message into the message body of
the resulting message and the following parts (if available) will be transformed into attach
ments of the resulting message.
In case the inbound message is, other than expected, no MIME multipart message with in
line headers, the complete message body is interpreted as a preamble of the MIME multi
part, and the resulting message is empty.
● The inbound message either doesn’t contain the multipart header as Camel header or
the Content-Type is no multipart, the Decoder step doesn’t change the inbound mes
sage.
● In all other cases, the header of the inbound message will be used as header of the
multipart message (and deleted). The message body of the resulting message will be
built up out of those parts which are contained in the message body (and, if available,
out of the attachments).
2.5.3.4 Defining Decoders
You use this task to decode the message received over the network to retrieve original data.
Procedure
2. If you want to add a decoder in the integration flow, choose Add Message Transformers Decoder
from the context menu of a connection within the pool.
3. Select the newly added decoder in the integration flow model to configure it.

4. In the Properties view, select the decoding scheme from the dropdown list. You can select one of the
following decoding schemes:
○ Base64 Decode: Decodes base64-encoded message content.

○ GZIP Decompress: Decompresses the message content using GNU zip (GZIP).
○ ZIP Decompress: Decompresses the message content using zip.
○ MIME Multipart Decode: Transforms a MIME multipart message into a message with attachments.
If the multipart headers are part of the message body, select Multipart Headers Inline.
 Note
If this option is not selected and the content type camel-header is not set to a multipart type, no
decoding takes place.
If this option is selected and the body of the message is not a MIME multipart (with MIME headers
in the body), the message is handled as a MIME comment and the body is empty afterwards.
 Example
Let us suppose that an input message to the decoder is a message encoded in Base64 that looks like this:
The output message of the decoder would be as follows:
<message>
Input for encoder
</message>
2.5.3.5 Defining Content Filter
Context
You use this task if you want to filter information by extracting a specific node from the incoming message.
Procedure
1. Open the <integration flow>.iflw in the Model Configuration editor
2. If you want to add content filter in the integration flow, choose Add Message Transformers Content
Filter from the context menu of a connection within the pool.
3. Select the added content filter in the integration flow model to configure it.

4. In the Properties view, enter an Xpath to extract a specific message part from the body. For example, in the
Xpath Expression field, enter /ns0:MessageBulk/Message/MessageContent/text() .
 Tip
To quickly specify the Xpath in the content filter, select Define Content Filter from the context menu of
the element.
5. In the Properties view, select a particular value for the output, from the Value Typedropdown menu.
Value Type Description
String The output is of type string.
Integer The output is of type integer.
Boolean The output is of type boolean.
Node The output is of type node.
Nodelist The output is collection of nodes.
 Example
Consider an XML payload structure-
<Message>
<orders>
<order>
<clientId>I0001</clientId>
<count>100</count>
</order>
<order>
<count>10</count>
</order>
</orders>
</Message>
If you enter an Xpath- /Message/orders/order/count/text(). The output of the Content Filter would
be- 10010
Related Information

2.5.3.6 Define Message Digest
This integration flow step is used to calculate a digest of the payload or parts of it and store the result in a
message header.
Context
In detail, the Message Digest integration flow step transforms a message into a canonical XML document. From
this document, a digest (hash value) is calculated and written to the message header.
 Note
Canonicalization transforms an XML document into a form (the canonic form) that makes it possible to
compare it with other XML documents. With the Message Digest integration flow step, you can apply
canonicalization to a message (or to parts of a message), calculate a digest out of the transformed
message, and add the digest to the message header.
In simple terms, canonicalization skips non-significant elements from an XML document. To give some
examples, the following changes are applied during the canonicalization of an XML document: Unification
of quotation marks and blanks, or encoding of empty elements as start/end pairs.
The original message remains unchanged.
You also have the option to define a filter to apply canonicalization only to a sub-set of the message.
Procedure
1. Open the integration flow in the Model Configuration editor.

2. Select the Message Digest step and add it to the integration flow.
3. Specify the following attributes for the step.
Option Description
Filter (XPath) If you only want to transform part of the message, enter an XPath expression to specify the part (op
tional attribute).
You can also define a prefix namespace mapping.
Canonicaliza You can choose between the following methods.

tion Method ○ Canonical XML Version 1.0
More information: http://www.w3.org/TR/2001/REC-xml-c14n-20010315
○ Canonical XML with Comments Version 1.0
More information: http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments
○ Exclusive XML Canonicalization Version 1.0
More information: http://www.w3.org/2001/10/xml-exc-c14n
○ Exclusive XML Canonicalization with Comments Version 1.0

Option Description
More information: http://www.w3.org/2001/10/xml-exc-c14n#WithComments
This is an optional attribute.
Digest Algo Select the hash algorithm to be used to calculate the digest.
rithm
You can choose between the following hash algorithms:
○ SHA-1
○ SHA-256
○ SHA-384
○ SHA-512
○ MD5
This is a mandatory attribute.
Target Enter the name of the target header element which is to contain the hash value (digest).
Header Name
2.5.3.7 Defining Converter
Context
The converter element enables you to transform an input message in one format to another. You can also
specify some conditions that are used as reference to transform the message.
The CSV to XML converter transforms a message in CSV format to XML format. Conversely, the XML to CSV
converter transforms a message in XML format to CSV format.
 Restriction
You cannot use XML to CSV converter to convert complex XML files to CSV format.
Procedure
You use this procedure to define a converter element in an integration process.

2. Access the palette and choose Message Transformers.
3. Drag from palette to the integration process and define the message path.

 Note
Alternatively, you can also add the converter from context menu. Choose Message Transformers
Converter
4. If you want to use CSV to XML Converter, perform the following substeps.
a. Select the Converter element and access Properties tab page.
b. Provide values in fields based on description in table.
Field Description
Name Provide a name for the converter step. This field is op
tional.
XML Schema Choose Browse and select the file path to the XML
schema file that is used as the basis for message trans
formation. The XML file schema format is used as the
basis for creation of the payload. This file has to be in
the package source.main.resources.xsd
Path to Target Element in XSD XPath in the XML Schema File where the content from
CSV has to be placed.
Record Marker in CSV The corresponding record in the CSV file that has to be
considered for conversion. This entry is the first text in
every new record of the CSV.
 Note
If this value is not specified then all the records
would be considered for conversion.
c. In the Field Separator in CSV field, choose the character that you want to use as the field separator in
CSV file from the dropdown list.
 Note
If you want to use a field separator that is not available in the dropdown list, manually enter the
character in Field Separator in CSV field.
d. If you want to exclude headers in the first line of CSV file for conversion, select Exclude First Line
Header checkbox.
e. Save changes.
5. If you want to use XML to CSV Converter, right-click on the CSV to XML Converter and choose Switch to
XML to CSV Converter. Perform the following substeps:
a. In the context menu of Converter, choose Switch to XML to CSV Converter.
b. Access the Properties tab page.
c. In the Path to Source Element field, enter the path of the source element in XML file.
d. In the Field Separator in CSV field, select the field separator from the dropdown list.

 Note
If you want to use a field separator that is not available in the dropdown list, manually enter the
character in Field Separator in CSV field.
e. If you want to use the field names in the XML file as headers in CSV file, select the Field Names as
Headers in CSV checkbox.
f. If you want to include the parent element of the XML file in the CSV file, in the Advanced tab page
select Include Parent Element checkbox.
g. If you want to include the attribute values of the XML file in the CSV file, in the Advanced tab page
select Include Attribute Values checkbox.
h. Save changes.
 Example
Consider a CSV file that is in the following format:
COMPETENCY,
Role Specific,
Computer Skills,
"Skilled in the use of computers, adapts to new technology, keeps abreast of
changes, learns new programs quickly, uses computers to improve productivity."
Consider the Schema XML File in the following format:

<CompetencyList>
<Competency>
<id></id>
<name></name>
<description></description>
</Competency>
</CompetencyList>
Value for the field XPath of Record Identifier in XSD is given as CompetencyList\Competency.
After it is processed by the CSV to XML converter, the XML output appears in the following format:

<CompetencyList>
<Competency>
<id>Role Specific</id>
<name>Computer Skills</name>
<description>Skilled in the use of computers, adapts to new technology, keeps
abreast of changes, learns new programs quickly, uses computers to improve
productivity.</description>
</Competency>
</CompetencyList>

2.5.3.7.1 Defining the JSON-to-XML Converter
The JSON-to-XML converter enables you to transform messages in JSON format to XML format.
Procedure

3. Drag Converter from the palette to the integration process.
4. From the context menu, choose Switch to JSON to XML Converter.
5. On the properties tab page, define the conversion parameters, see table below:
Option Description
Name Enter the name of the converter.
JSON Prefix (only if the option Use Namespace Mapping Enter the mapping of the JSON prefix to the XML name
is selected) space. The JSON namespace/prefix must begin with a let
ter and can contain aA-zZ and 0-9.
JSON Prefix Separator Enter the JSON prefix separator to be used to separate
the JSON prefix from the local part. The value used must
not be used in the JSON prefix or local name.
The following characters are allowed: colon(:), comma(,),

dot(.), pipe(|), semicolon(;), and space.
2.5.3.7.1.1 Conversion Rules for JSON to XML Conversion
To ensure a successful conversion of you data, you should make yourself familiar with the conversion rules.
The conversion from JSON format to XML format follows the following rules:
● The value of a complex element (having attributes for example) is represented by a separate member
"$":"value".
● An element with multiple child elements of the same name is represented by an array. This also holds if
between the children with the same name other children with another name reside.
Example: <root><childA>A1</childA><childB>B</childB><childA>A2</childA></root> is
transformed in the non-streaming case to {"root":{"childA":["A1","A2"],"childB":"B"}},
which means that the order of the children is not preserved.
In the streaming case, the result is: {"root":{"childA":["A1"],"childB":"B","childA":
["A2"]"}}, which means that a non-valid JSON document is created because the member "childA"
appears twice.
● An element with no characters or child elements is represented by "element" : ""

● An attribute is represented as JSON member whose name is the concatenation of '@' , the JSON prefix
corresponding to the XML namespace, JSON delimiter, and the attribute name. If the attribute has no
namespace, no prefix and JSON delimiter are added to the JSON name.
● An element is represented as JSON member whose name is the concatenation of JSON prefix
corresponding to the XML namespace, JSON delimiter, and the element name. If the element has no
namespace, no prefix and JSON delimiter is added to the JSON name.
● A member with JSON null value is transformed to empty element; example: "C":null is converted to
<C/>.
● Conversion of "@attr":null to XML is not supported (you get a NullPointerException, since cluster
version 1.21 you get a JsonXmlException).
● The result XML document is encoded in UTF-8 and gets the XML header "<?xml version='1.0'
encoding='UTF-8'?>".
● The content of the XML-Namespace-to-JSON-Prefix map is transformed to namespace prefix declarations
on the root element.
● If for a JSON prefix no XML Namespace is defined, then the full member name with the prefix and JSON
delimiter is set as element name: "p.A" leads to <p.A>.
Related Information
Define JSON to XML Converter [page 737]

Conversion Rules for XML to JSON Conversion [page 231]
2.5.3.7.1.2 Limitations for JSON to XML Conversion

To ensure a successful conversion frrm JSON to XML format you have to know the limitations for this
conversion.
The JSON to XML conversion has the following limitations:
● The XML element and attribute names must not contain any delimiter characters, because the delimiter is
used in JSON to separate the prefix from the element name.
● Elements with mixed content are not supported.
● Conversion of "@attr":null to XML is not supported. You get a NullPointerException; as of cluster version
1.21 you get a JsonXmlException.
● JSON member names must not contain in their local or prefix part any characters that are not allowed for
XML element/attribute names (for example, space or column (':') are not allowed). XML element/attribute
names are of type NCName (see http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName
).
● JSON texts that start with an array (for example, [{"a":{"b":"bvalue"}}] ) are not supported. The
JSON text must start with a JSON object such as {{"a":{"b":"bvalue"}}}. A
javax.xml.stream.XMLStreamException is thrown. As of cluster version 1.21, a JsonXmlException is thrown.
● The root JSON object must contain exactly one member. If the root JSON object contains more than one
member (for example, {"a":"avalue","b":"bvalue"}), a javax.xml.stream.XMLStreamException is
thrown. If the root JSON object is empty ({}), a javax.xml.stream.XMLStreamException is thrown. As of
cluster version 1.21, a JsonXmlException or IllegalStateException (for {}) is thrown.

 Tip
If you need to convert a JSON file that doesn't fulfil this requirement, you can do the following:
Add a content modifier before the JSON to XML converter that changes the message body. In the entry
field in tab Message Body, enter:
{"root": ${in.body}}
● If no XML namespace is defined for a JSON prefix, the full member name with the prefix and JSON
delimiter is set as the element name: "p:A" -> <p:A>.
Related Information

Conversion Rules for JSON to XML Conversion [page 738]
Limitations for XML-to-JSON Conversion [page 232]
2.5.3.7.1.3 Example: Transformations from JSON format to

XML format with and without Namespace
Mapping
Whether you select the option Use Namespace Mapping or not, leads to different transformation results.
Using Namespace Mapping
For this example we look at the following JSON document:
{"abc:A":{"xyz:B":{"@xyz:attr1":"1","@attr2":"2","$":"valueB"},"C":
["valueC1","valueC2"],"D":"","E":"valueE"}}
For the transformation of this document we choose the following settings:
● The character ':' is used as the JSON prefix separator.

● The option Use Namespace Mapping is selected.
● The JSON-prefix-to-XML-namespace mapping is as follows:
JSON Prefix XML Namespace
abc http://com.sap/abc
xyz http://com.sap/xyz
We get the following XML document:

<?xml version='1.0' encoding='UTF-8'?>
<abc:A xmlns:abc="http://com.sap/abc" xmlns:xyz="http://
com.sap/xyz"><xyz:B xyz:attr1="1" attr2="2">valueB</xyz:B><C>valueC1</
C><C>valueC2</C><D/><E>valueE<E></abc:A>
No Namespace Mapping
{"abc.A":{"xyz.B":{"@xyz.attr1":"1","@attr2":"2","$":"valueB"},"C":

● The option Use Namespace Mapping is not selected.
We get the followingXML document:
<?xml version='1.0' encoding='UTF-8'?><A><B attr1="1" attr2="2">valueB</

B><C>valueC1</C><C>valueC2</C><D/><E>valueE<E></A>
2.5.3.7.2 Defining the XML-to-JSON Converter
The XML-to-JSON converter enables you to transform messages in XML format to JSON format.
Procedure
You use this procedure to define a converter element in an integration process.

3. Drag Converter from the palette to the integration process.
4. From the context menu, choose Switch to XML to JSON Converter.
5. On the XML to JSON Converter properties tab page, define the parameters to convert the XML data format
to JSON data format.
Option Description

Option Description
JSON Output Encoding Enter the JSON output encoding. The default value is from
header or property.
If you select from header or property, the converter tries to

read the encoding from the message header or exchange
property CamelCharsetName. If there is no value de
fined, UTF-8 is used.
XML Namespace (only if the option Namespace Mapping If you select from header or property, the converter tries
is selected) to read the encoding from the message header or ex
change property CamelCharsetName. If there is no value
defined, UTF-8 is used.
JSON Prefix Separator (only if the option Namespace Enter the JSON prefix separator to be used to separate
Mapping is selected) the JSON prefix from the local part. The value used must

Suppress JSON Root Element Choose this option to create the JSON message without
the root element tag.
6. Specify whether to enable Streaming or not.
You can specify whether the whole XML document or only specified XML elements are to be presented by
JSON arrays.
All All elements are presented as JSON arrays.

Specific Ones Only the specified elements will be represented as JSON
arrays, the others as JSON objects.
 Note
A JSON object is an unordered set of name/value
pairs that begins with { and ends with }. Each name
is followed by : and the name/value pairs are sepa
rated by ,.
A JSON array is an ordered collection of values. An ar

ray begins with [ and ends with ]. Values are sepa
rated by ,.
Enter the absolute paths to the XML elements to be con

verted to JSON arrays. Specify all elements with a multi
plicity larger than one. Otherwise, it cannot be ensured
that streaming will result in a valid JSON document.
Familiarize yourself with streaming in the XML-to-JSON

converter, as documented in a separate topic.
Related Information

How Streaming in the XML-to-JSON Converter Works [page 233]
2.5.3.7.2.1 Conversion Rules for XML to JSON Conversion
To ensure a successful conversion from XML format to JSON format, you should make yourself familiar with
the conversion rules.
The conversion from XML format to JSON format follows the following rules:

appears twice.
"$":"value".
● Elements with mixed content (for example. <A>mixed1_value<B>valueB</B>mixed2_value</A>) are
not supported. Currently you get wrong results for XML to JSON: {"A":
{"B":"valueB","$":"mixed1_valuemixed2_value"}} in the non-streaming case or
{"A":"$":mixed1_value","B":"valueB","$":"mixed2_value"}} in the streaming case.
● All element/attribute values are transformed to JSON string.
● No namespace declaration is written into the JSON document.
● Tabs, spaces, new lines between elements and attributes are ignored. However, a white space value of an
element with simple type is represented in JSON; example <A> </A> is represented by "A":" ".
● If you have an element with namespace but without XML prefix whose namespace is not contained in the
XML-namespace-to-Json-prefix map, then you get an exception: <A xmlns="http://test"/> leads to
IllegalStateException Invalid JSON namespace: http://test.
This is not the case if you choose the streaming option. With streaming the namespace is just ignored: <A
xmlns="http://test"/>v</A> leads to {"A":"v"}.
● If you have an element with namespace and XML prefix whose namespace is not contained in the XML-
namespace-to-Json-prefix map then the XML prefix is used as JSON prefix <ns:A xmlns:ns:="http://
test"/> leads to "ns.A":"" (if JSON delimiter is '.').
Related Information
Define XML to JSON Converter [page 741]

Example: Transformation to a JSON Message without Root Element Tag [page 236]
2.5.3.7.2.2 Limitations for XML-to-JSON Conversion
To ensure a successful conversion form XML to JSON format you have to know the limitations for this
conversion.
The XML to JSON conversion has the following limitations:
● XML comments () are not represented in the JSON document; they are ignored.

● DTD declarations are not represented in the JSON document; they are ignored.
● XML processing instructions are not represented in the JSON document; they are ignored.
● No conversion to JSON primitive types for XML to JSON. All XML element/attribute values are transformed
to a JSON string.
● Entity references (except the predefined entity references & < > " ') are not
represented in the JSON document; they are ignored.
● If a sibling with another name resides between XML sibling nodes with the same name, then the order of
the siblings is not kept in JSON in the non-streaming case, because siblings with the same name are
represented by one array. Example: <root><childA>A1</childA><childB>B</
childB><childA>A2</childA></root> leads to {"root":{"childA":
["A1","A2"],"childB":"B"}}.
In the streaming case this leads to an invalid JSON document: {"root":{"childA":
["A1"],"childB":"B","childA":["A2"]}.
● If you have an element with a namespace but no XML prefix whose namespace is not contained in the XML-
namespace-to-JSON-prefix map, you get an exception: <A xmlns="http://test"/> -> IllegalStateException
Invalid JSON namespace: http://test.
If you choose the streaming option, the namespace is ignored: <A xmlns="http://test"/>v</A> leads
to {"A":"v"}.
Related Information

2.5.3.7.2.3 How Streaming in the XML-to-JSON Converter

Works
During streaming the XML document is processed in parts or segments:
The individual tags of an XML document are processed consecutively,irrespective of where in the overall
structure the tag occurs and how often (multiplicity). This means that during the streaming process the
converter cannot know if an element occurs in the structure more than once. In other words, during the
streaming process the object model that reflects the overall structure of the XML document (and, therefore,
also all information that can only be derived from the object model, like the multiplicity of elements) is not in
place. This is different to the non-streaming case, where the converter can calculate the multiplicity of the XML
elements from the object model of the complete XML document. The multiplicity is needed to create a correct
JSON document. Elements whose multiplicity is greater than one must be transformed to a JSON member
with an array. For example, you may think that for the XML document <root><B>b1</B><B>b2</B></root>,
you create the JSON document {“root”:{“B”:”b1”,”B”:”b2”}}. However, this JSON document is invalid,
because the member name “B” occurs twice on the same hierarchy level.

To ensure nevertheless a conversion that creates correct JSON documents during streaming, you need to
either manually provide the information about which XML elements are multiple in advance, or decide that
every XML element is converted to a JSON array (when configuring the converter in the Integration Designer).
To illustrate this behavior, let’s consider how the following simple XML structure has to be converted to JSON:
<root>
<A>a</A>
<B>b1</B>
<B>b2</B>
<C>c</C>
</root>
Note that the element root/B occurs twice (multiplicity = 2).
Without streaming, the converter would produce the following JSON structure:
{"root":{"A":"a","B":["b1","b2"],"C":"c"}}
As expected, the XML element root/B would transform into a JSON member with an array as value, where the
array has two values (b1 and b2) – according to the multiplicity of root/B. Note that a JSON array is indicated
by the following type of brackets: [ … ].
With streaming with all elements to JSON arrays, the converter would produce the following JSON structure:
{"root":[{"A":["a"],"B":["b1","b2"],"C":["c"]}]}
All XML elements are transformed into members with a JSON array as value.
With streaming and specific elements as arrays (where root/A and root/B are specified), the converter would
produce the following JSON structure:
{"root":{"A":["a"],"B":["b1","b2"],"C":"c"}}
An array is produced only for the XML elements root/A and root/B, but not for root/C.
With streaming and specific elements as arrays (where only root/A is specified), the converter would produce
the following invalid JSON structure:
{"root":{"A":["a"],"B":"b1",”B”:"b2","C":"c"}}

2.5.3.7.2.4 Example: Transformations from XML format to
JSON format with and without Namespace
Mapping
 Example
For this example we look at the following XML document:

<n1:A xmlns:n1="http://com.sap/abc" xmlns:n2="http://
com.sap/xyz">
<n2:B n2:attr1="1" attr2="2">valueB</n2:B>
<C>valueC1</C>
<C>valueC2</C>
<D/>
<E>valueE<E>
</n1:A>

● The XML-namespace-to-JSON-prefix mapping is as follows:
XML Namespace JSON Prefix
http://com.sap/abc abc
http://com.sap/xyz xyz
We get the following JSON document:
 Note
Line breaks and spaces between the elements are ignored.

 Example

<abc:A xmlns:abc="http://com.sap/abc"
xmlns:xyz="http://com.sap/xyz"><xyz:B xyz:attr1="1" attr2="2">valueB</
xyz:B><C>valueC1</C><C>valueC2</C><D/><E>valueE</E></abc:A>
For the transformation we choose the following settings:

We get the following JSON Document:
{"A":{"B":{"@attr1":"1","@attr2":"2","$":"valueB"},"C":
2.5.3.7.2.5 Example: Transformation to a JSON Message

without Root Element Tag
Examples and Special Cases of JSON Message without Root Element Tag
The following examples apply to XML-to-JSON conversion:
 Example
The following example shows the transformation from XML to JSON (option Suppress JSON Root Element
is selected).
Input XML Message
<root>
<A>a</A>
<B>b</B>
<C>c</C>
<D>d</D>
</root>
Output JSON Message
{
"A": "a",
"B": "b",
"C": "c",
"D": "d"
}
Special Cases

Input XML Message: Root Element with Simple Value
<root>v</root>
Output JSON Message
"v"
Input XML Message: Root Element with no Value
<root></root>
Output JSON Message
""
Input XML Message: Root Element with Simple Value (options Suppress JSON Root Element, Steaming All
are selected)
<root><A>a<A><B><C>c</C></B></root>
Output JSON Message
{"A":["a"],"B":[{"C":["c"]}]}
with dropRootElement=false
{"root":{["A":["a"],"B":[{"C":["c"]}]]}}
2.5.3.7.3 Defining EDI to XML Converter
The EDI to XML converter enables you to transform messages in EDI format to XML format. You can convert
EDIFACT and ASC-X12 format into XML format.
Context
 Note
Contact the SAP Cloud Platform Integration Team to obtain EDI related XSD files.

Procedure
2. Choose Add Message Transformers Converter from the context menu of a connection within the
pool.
3. Choose Switch to EDI to XML Converter, from the context menu,.
4. On the EDI to XML Converter properties tab page, define the following parameters to convert the EDI data
format to XML data format.
Field Description
Source Encoding Select encoding format for the incoming payload.
EDI Schema Definition Select the source of schema definition.

Field Description
Schemas If you select Integration Flow as EDI Schema

Definition, then you can see the table Schemas, in
Properties view. Select the valid schemas against which
the conversion will take place.
 Note
○ You can add XSD files to the integration flow. For
more details, please refer to the topic Validating
Message Payload against XML Schema, in de
veloper's guide.
○ The file name of the xml schema for EDIFACT
should have the following format:
UN-EDIFACT_ORDERS_D96A.xsd
The file name comprises of following three parts
separated by '_':
○ First part "UN-EDIFACT" refers to the EDI
standard with organization name. This value
is fixed and cannot be customised.
○ Second part "ORDERS" refers to the mes
sage type.
○ Third part "D96A" refers to the version .
○ The file name of the xml schema for ASC-X12
ASC-X12_810_004010.xsd
separated by '_':
○ First part "ASC-X12" refers to the ASC-X12
○ Second part "810" refers to the message
type.
○ Third part "004010" refers to the version .
○ The above mentioned values should match with
schema content.

Field Description
HeaderName If you select Header as EDI Schema Definition, then you

can see the field HeaderName, in Properties view. Enter a
valid header name for the field.
 Note
This header name is fetched from camel header. The
header is added in script element. This script element
is added before converter element. You can add value
for this header in the script element.
For example, you can add the value, /xsd/UN-

EDIFACT_ORDERS_D96A.xsd for EDIFACT.
For example, you can add the value, /xsd/ASC-

X12_810_004010.xsd for ASC-X12.
 Note
○ Any EDIFACT message is an interchange. An interchange can have multiple groups. And each
group consists of message types. For EDIFACT message, the EDI elements in SAP Cloud Platform
Integration support only 1 message type per interchange but does not support any group segment
(GS) per interchange segment.
○ Any ASC-X12 message is an interchange. An interchange can have multiple groups. And each
group consists of transaction sets. For ASC-X12 message, the EDI elements in SAP Cloud Platform
Integration support only 1 group segment (GS) per interchange segment and only 1 transaction set
(ST) per group segment.
○ SAP Cloud Platform Integration does not support repetition characters. Repetition character is a
single character which separates the instances of a repeating data element. For example, ^ (caret
sign) is a repetition character.
 Note
EDI_Document_Number header contains document number for the incoming EDI file.
 Example
● The following example shows the transformation from EDI to XML format of EDIFACT message.
Input sample EDIFACT EDI Message
UNA:+.? '
UNB+UNOC:3+SENDERABC:14:XXXX+ReceiverXYZ:14:YYYYY+150831:1530+1+HELLO WORLD
++A+++1'
UNH+1+ORDERS:D:96A:UN++2'
BGM+220+MY_ID+9+NA'
DTM+137:201507311500:203'
DTM+2:201508010930:203'
CNT+16:10'
UNT+5+1'
UNZ+1+1'

Output sample EDIFACT XML Message
<?xml version="1.0" encoding="UTF-8"?><Interchange>

<S_UNA>:+.? '</S_UNA>
<S_UNB>
<C_S001>
<D_0001>UNOC</D_0001>
<D_0002>3</D_0002>
</C_S001>
<C_S002>
<D_0004>SENDERABC</D_0004>
<D_0007>14</D_0007>
<D_0008>XXXX</D_0008>
</C_S002>
<C_S003>
<D_0010>ReceiverXYZ</D_0010>
<D_0007>14</D_0007>
<D_0014>YYYYY</D_0014>
</C_S003>
<C_S004>
<D_0017>150831</D_0017>
<D_0019>1530</D_0019>
</C_S004>
<D_0020>1</D_0020>
<C_S005>
<D_0022>HELLO WORLD</D_0022>
</C_S005>
<D_0029>A</D_0029>
<D_0035>1</D_0035>
</S_UNB>
<M_ORDERS>
<S_UNH>
<D_0062>1</D_0062>
<C_S009>
<D_0065>ORDERS</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
</C_S009>
<C_S010>
<D_0070>2</D_0070>
</C_S010>
</S_UNH>
<S_BGM>
<C_C002>
<D_1001>220</D_1001>
</C_C002>
<D_1004>MY_ID</D_1004>
<D_1225>9</D_1225>
<D_4343>NA</D_4343>
</S_BGM>
<S_DTM>
<C_C507>
<D_2005>137</D_2005>
<D_2380>201507311500</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_DTM>
<C_C507>
<D_2005>2</D_2005>
<D_2380>201508010930</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_CNT>
<C_C270>
<D_6069>16</D_6069>

<D_6066>10</D_6066>
</C_C270>
</S_CNT>
<S_UNT>
<D_0074>5</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</M_ORDERS>
<S_UNZ>
<D_0036>1</D_0036>
<D_0020>1</D_0020>
</S_UNZ>
</Interchange>
● The following example shows the transformation from EDI to XML format of ASC-X12 message.
Input sample ASC-X12 EDI Message
 Sample Code
ISA*00* *00* *01*784849291 *01*315029991

*051007*0928*/*4010 *000000001*0*P*^~
GS*PO*784849291*315029991*20051007*0928*1*U*004010~
ST*850*10001~
BEG*00*NE*228914**20051006~
CUR*BY*EUR*0100~
N1*SF*BEHR SERVICE GMBH*92*1939~
N1*ST*BEHR SERVICE AMERICA*92*1939~
PO1*10000*17*EA*91.8074*EA*BP*2112910003*PD*Radiator~
LIN**MF*2109308~
SCH*17*EA***002*20060401~
CTT*1~
SE*10*10001~
GE*1*1~
IEA*1*000000001~
Output sample ASC-X12 XML Message
<?xml version="1.0" encoding="UTF-8"?><ns0:Interchange

xmlns:ns0="urn:sap.com:typesystem:b2b:116:asc-x12:850:004010">
<S_ISA>
<D_I01>00</D_I01>
<D_I02> </D_I02>
<D_I03>00</D_I03>
<D_I04> </D_I04>
<D_I05_1>01</D_I05_1>
<D_I06>784849291 </D_I06>
<D_I05_2>01</D_I05_2>
<D_I07>315029991 </D_I07>
<D_I08>051007</D_I08>
<D_I09>0928</D_I09>
<D_I10>/</D_I10>
<D_I11>4010 </D_I11>
<D_I12>000000001</D_I12>
<D_I13>0</D_I13>
<D_I14>P</D_I14>
<D_I15>^</D_I15>
</S_ISA>
<S_GS>
<D_479>PO</D_479>
<D_142>784849291</D_142>
<D_124>315029991</D_124>
<D_373>20051007</D_373>
<D_337>0928</D_337>
<D_28>1</D_28>
<D_455>U</D_455>
<D_480>004010</D_480>

</S_GS>
<M_850>
<S_ST>
<D_143>850</D_143>
<D_329>10001</D_329>
</S_ST>
<S_BEG>
<D_353>00</D_353>
<D_92>NE</D_92>
<D_324>228914</D_324>
<D_373>20051006</D_373>
</S_BEG>
<S_CUR>
<D_98_1>BY</D_98_1>
<D_100_1>EUR</D_100_1>
<D_280>0100</D_280>
</S_CUR>
<G_N1>
<S_N1>
<D_98_1>SF</D_98_1>
<D_93>BEHR SERVICE GMBH</D_93>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_N1>
<S_N1>
<D_98_1>ST</D_98_1>
<D_93>BEHR SERVICE AMERICA</D_93>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_PO1>
<S_PO1>
<D_350>10000</D_350>
<D_330>17</D_330>
<D_355>EA</D_355>
<D_212>91.8074</D_212>
<D_639>EA</D_639>
<D_235_1>BP</D_235_1>
<D_234_1>2112910003</D_234_1>
<D_235_2>PD</D_235_2>
<D_234_2>Radiator</D_234_2>
</S_PO1>
<S_LIN>
<D_235_1>MF</D_235_1>
<D_234_1>2109308</D_234_1>
</S_LIN>
<G_SCH>
<S_SCH>
<D_380>17</D_380>
<D_355>EA</D_355>
<D_374_1>002</D_374_1>
<D_373_1>20060401</D_373_1>
</S_SCH>
</G_SCH>
</G_PO1>
<G_CTT>
<S_CTT>
<D_354>1</D_354>
</S_CTT>
</G_CTT>
<S_SE>
<D_96>10</D_96>
<D_329>10001</D_329>
</S_SE>
</M_850>

<S_GE>
<D_97>1</D_97>
<D_28>1</D_28>
</S_GE>
<S_IEA>
<D_I16>1</D_I16>
<D_I12>000000001</D_I12>
</S_IEA>
</ns0:Interchange>
2.5.3.7.4 Defining XML to EDI Converter
The XML to EDI converter transforms a message in XML format to EDI format. You can convert EDIFACT and
ASC-X12 format into XML format.
Context
 Note
Contact the SAP Cloud Platform Integration Team to obtain EDI related XSD files.
Procedure
2. Choose Add Message Transformers Converter from the context menu of a connection within the
pool.
3. Choose Switch to XML to EDI Converter, from the context menu,.
4. Provide values in fields based on description in table:
Tab Field Description
General Name Enter a name for the flow step.
EDIFACT Source Encoding Select encoding format for the incom

ing payload.
EDI Schema Definition Select the source of schema defini-

tion.

Schemas If you select Integration Flow as EDI

Schema Definition, then you can see
the table Schemas, in Properties view.
Select the valid schemas against
which the conversion will take place.
 Note
○ You can add XSD files to the
integration flow. For more de
tails, please refer to the topic
Validating Message Payload
against XML Schema.
○ The file name of the xml
schema for ASC-X12 should
have the format, ASC-
X12_810_004010.xsd. It con
tains three parts separated
by _:
○ First part ASC-X12 refers
to the ASC-X12 standard
with organization name.
This value is fixed and
cannot be customised.
○ Second part 810 refers
to the message type.
○ Third part 004010 refers
to the version.
○ The aforementioned values
should match with the
schema content.

HeaderName If you select Header as EDI Schema

Definition, then you can see the field
HeaderName, in Properties view. Enter
a valid header name for the field.
 Note
This header name is fetched from
Camel header. The header is
added in script element. This
script element is added before
the converter element. You can
add value for this header in the
script element.
For example, you can add the

value, /xsd/UN-
EDIFACT_ORDERS_D96A.xs
d.
Use Custom Separators Select this option if you want to spec

ify which separators are to be used in
the converted message. You can se
lect the characters available in the
dropdown list for each separator.
 Note
You can also manually specify the
custom separator.
○ Enter the hexadecimal value

for the separator you want to
use in the respective field.
For example, enter #x2b to
use + as the separator.
○ Enter the header value to
fetch the sepatator from
header. For example, $
{header.HEADER_NAME
}
X12 Source Encoding Select encoding format for the incom

ing payload.

EDI Schema Definition If you select Integration Flow as EDI

 Note
against XML Schema, in de
veloper's guide.
X12_810_004010.xsd. It con
by _:
to the version.
schema content.
○ During runtime only XSD’s
from Integration Content Ad
visor (ICA) are supported.

Header Name If you select Header as EDI Schema

 Note
camel header. The header is
converter element. You can add
value for this header in the script
element.

value, /xsd/ASC-
X12_810_004010.xsd.

 Note
custom separator.

{header.HEADER_NAME
}
 Note

○ SAP Cloud Platform Integration generates EDI file which uses the following separators for EDIFACT
message:
○ Data Element separator +
○ Component Data Element separator :
○ Segment separator ‘
○ SAP Cloud Platform Integration generates EDI file which uses the following separators for ASC-X12
message:
○ Data Element separator *
○ Segment separator ~
 Note
EDI_Document_Number header contains document number for the incoming EDI file.
 Example
● The following example shows the transformation from XML to EDI format of EDIFACT message.
Input sample EDIFACT XML Message

<S_UNA>:+.? '</S_UNA>
<S_UNB>
<C_S001>
<D_0001>UNOC</D_0001>
<D_0002>3</D_0002>
</C_S001>
<C_S002>
<D_0007>14</D_0007>
<D_0008>XXXX</D_0008>
</C_S002>
<C_S003>
<D_0007>14</D_0007>
<D_0014>YYYYY</D_0014>
</C_S003>
<C_S004>
<D_0017>150831</D_0017>
<D_0019>1530</D_0019>
</C_S004>
<D_0020>1</D_0020>
<C_S005>
</C_S005>
<D_0029>A</D_0029>
<D_0035>1</D_0035>
</S_UNB>
<M_ORDERS>
<S_UNH>
<D_0062>1</D_0062>

<C_S009>
<D_0065>ORDERS</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
</C_S009>
<C_S010>
<D_0070>2</D_0070>
</C_S010>
</S_UNH>
<S_BGM>
<C_C002>
<D_1001>220</D_1001>
</C_C002>
<D_1004>MY_ID</D_1004>
<D_1225>9</D_1225>
<D_4343>NA</D_4343>
</S_BGM>
<S_DTM>
<C_C507>
<D_2005>137</D_2005>
<D_2380>201507311500</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_DTM>
<C_C507>
<D_2005>2</D_2005>
<D_2380>201508010930</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_CNT>
<C_C270>
<D_6069>16</D_6069>
<D_6066>10</D_6066>
</C_C270>
</S_CNT>
<S_UNT>
<D_0074>5</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</M_ORDERS>
<S_UNZ>
<D_0036>1</D_0036>
<D_0020>1</D_0020>
</S_UNZ>
</Interchange>
Output sample EDIFACT EDI Message
UNA:+.? '
++A+++1'
BGM+220+MY_ID+9+NA'
DTM+137:201507311500:203'
DTM+2:201508010930:203'
CNT+16:10'
UNT+5+1'
UNZ+1+1'
● The following example shows the transformation from XML to EDI format of ASC-X12 message.
Input sample ASC-X12 XML Message


<S_ISA>
<D_I01>00</D_I01>
<D_I02> </D_I02>
<D_I03>00</D_I03>
<D_I04> </D_I04>
<D_I05_1>01</D_I05_1>
<D_I06>784849291 </D_I06>
<D_I05_2>01</D_I05_2>
<D_I07>315029991 </D_I07>
<D_I08>051007</D_I08>
<D_I09>0928</D_I09>
<D_I10>/</D_I10>
<D_I11>4010 </D_I11>
<D_I12>000000001</D_I12>
<D_I13>0</D_I13>
<D_I14>P</D_I14>
<D_I15>^</D_I15>
</S_ISA>
<S_GS>
<D_479>PO</D_479>
<D_142>784849291</D_142>
<D_124>315029991</D_124>
<D_373>20051007</D_373>
<D_337>0928</D_337>
<D_28>1</D_28>
<D_455>U</D_455>
<D_480>004010</D_480>
</S_GS>
<M_850>
<S_ST>
<D_143>850</D_143>
<D_329>10001</D_329>
</S_ST>
<S_BEG>
<D_353>00</D_353>
<D_92>NE</D_92>
<D_324>228914</D_324>
<D_373>20051006</D_373>
</S_BEG>
<S_CUR>
<D_98_1>BY</D_98_1>
<D_100_1>EUR</D_100_1>
<D_280>0100</D_280>
</S_CUR>
<G_N1>
<S_N1>
<D_98_1>SF</D_98_1>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_N1>
<S_N1>
<D_98_1>ST</D_98_1>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_PO1>
<S_PO1>
<D_350>10000</D_350>
<D_330>17</D_330>
<D_355>EA</D_355>
<D_212>91.8074</D_212>
<D_639>EA</D_639>
<D_235_1>BP</D_235_1>

<D_234_1>2112910003</D_234_1>
<D_235_2>PD</D_235_2>
<D_234_2>Radiator</D_234_2>
</S_PO1>
<S_LIN>
<D_235_1>MF</D_235_1>
<D_234_1>2109308</D_234_1>
</S_LIN>
<G_SCH>
<S_SCH>
<D_380>17</D_380>
<D_355>EA</D_355>
<D_374_1>002</D_374_1>
<D_373_1>20060401</D_373_1>
</S_SCH>
</G_SCH>
</G_PO1>
<G_CTT>
<S_CTT>
<D_354>1</D_354>
</S_CTT>
</G_CTT>
<S_SE>
<D_96>10</D_96>
<D_329>10001</D_329>
</S_SE>
</M_850>
<S_GE>
<D_97>1</D_97>
<D_28>1</D_28>
</S_GE>
<S_IEA>
<D_I16>1</D_I16>
<D_I12>000000001</D_I12>
</S_IEA>
</ns0:Interchange>
Output sample ASC-X12 EDI Message
ISA*00* *00* *01*784849291 *01*315029991

*051007*0928*/*4010 *000000001*0*P*^~
GS*PO*784849291*315029991*20051007*0928*1*U*004010~
ST*850*10001~
BEG*00*NE*228914**20051006~
CUR*BY*EUR*0100~
LIN**MF*2109308~
SCH*17*EA***002*20060401~
CTT*1~
SE*10*10001~
GE*1*1~
IEA*1*000000001~

2.5.3.8 Defining Script
Context
You use this task to execute custom Java script or Groovy script for message processing. SAP Cloud Platform
Integration provides a Java API to support this use case.
 Note
Modifier or Script step) will also be part of the outbound message addressed to a receiver system. Because
of this, it is important to consider the following restriction regarding the header size if you use an HTTP-
based receiver adapter:
If the message header exceeds 8 KB, it might lead to situations that the receiver cannot accept the inbound
call (relevant for all http-based receiver adapters).
 Note
The Java standard libraries of Java 7 can be used.
Cloud Integration supports the XML Document Object Model (DOM) to process XML documents.
 Note
Any application that parses XML data is prone to the risk of XML External Entity (XXE) Processing attacks.
More information: https://www.owasp.org/index.php/XML_External_Entity_%28XXE%29_Processing
To overcome this issue, you should take the following measures to protect integration flows that contain
Script steps (using Groovy script or Java Script) against XXE Processing attacks:
● Do not use XML parsing (for example, DocumentBuilderFactory) at all or

● Switch off the processing of external entities as described at https://www.owasp.org/index.php/
XML_External_Entity_%28XXE%29_Prevention_Cheat_Sheet#Java .
Procedure

2. Add script in the integration flow, choose Add Message Transformers>Script from the context menu of a
connection within the pool.
3. Select the added script in the integration flow model to configure it.
4. If you already have an existing java script or groovy script, copy it to the folder src.main.resources.script. To
assign this script, choose Assign Script from the context menu of the Script element.

5. To create a new java script or groovy script, choose New Script from the context menu of the Script
element.
6. In the Properties view, specify the script step name in Name.
7. In the Properties view, specify a custom function that will take the “message” object as the argument in
Script Function.
In the script you require Script Function, which will be executed at runtime. The function definition is as
follows:
import com.sap.gateway.ip.core.customdev.util.Message
def Message processData(Message message) {
def body = message.getBody()
//modify body
message.setBody(body + "enhancements")
//modify headers
def map = message.getHeaders()
def value = map.get("oldHeader");
message.setHeader("oldHeader", value + "modified")
message.setHeader("newHeader", "headerValue")
//modify properties
map = message.getProperties()
value = map.get("oldProperty")
message.setProperty("oldProperty", value + "modified")
message.setProperty("newProperty", "script")
return message
}
8. Add or modify Header, Body, and Property by using the interfaces below on the "message" object.
1. You can use the following interfaces for Header:
○ public java.util.Map<java.lang.String,java.lang.Object> getHeaders()
○ public void setHeaders(java.util.Map<java.lang.String,java.lang.Object> exchangeHeaders)
○ public void setHeader(java.lang.String name, java.lang.Object value)
2. You can use the following interfaces for Body:
○ public java.lang.Object getBody()
○ public void setBody(java.lang.Object exchangeBody)
○ public java.lang.Object getBody(java.lang.String fullyQualifiedClassName)
 Note
SAP Cloud Platform Integration framework supports conversion of payload into the following
formats:
○ String
○ InputStream
○ byte[]
To convert the payload into String or InputStream use the following fullyQualifiedClassName:
○ java.lang.String
○ java.io.InputStream
To convert the payload into byte[] use the following:
○ For groovy script - def body = message.getBody(java.lang.String) as byte[]
○ For java script - var body = [message.getBody()]
3. You can use the following interfaces for Property:

○ public java.util.Map<java.lang.String,java.lang.Object> getProperties()
○ public void setProperties(java.util.Map<java.lang.String,java.lang.Object> exchangeProperties)
○ public void setProperty(java.lang.String name, java.lang.Object value)
4. You can use the following interfaces for Attachment:
○ public java.util.Map<java.lang.String,javax.activation.DataHandler> getAttachments()
○ public void setAttachments(Map<java.lang.String, javax.activation.DataHandler>)
 Note
○ 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. Please refer to https://
tools.hana.ondemand.com/#cloudintegration to download the file.
○ You should not add or modify a Property name starting with sap.
○ If no Script Function is specified in the script flow step, the Script Function name will be
processData by default.
 Caution
When converting parts of the message object like the body or even headers or properties into a string
(as string) or into a byte array (as byte[]) please consider copies of the existing data is created which
requires extra memory. This resource consumption may even exceed the memory size of the original
object if string conversion is executed.
Example:
def body = message.getBody(java.lang.String) as String;
Depending on the size of the object byte[] or string conversion can endanger worker node of OOM
failure. Please consciously decide which part of the message object should be converted.
9. If you want to access the security artifacts such as secure store and keystore that are deployed using the
deployment wizard, refer the table below:

Artifact Type Sample Groovy Script
Secure Store Import packages
import com.sap.it.api.ITApiFactory;
import com.sap.it.api.securestore.SecureStoreService;
import com.sap.it.api.securestore.UserCredential;
import
com.sap.it.api.securestore.exception.SecureStoreException;
 Sample Code
def service =
ITApiFactory.getApi(SecureStoreService.class, null);
if( service != null)

{
//Get UserCredential containing user credential
details deployed on the node with the given alias.
def credential =
service.getUserCredential(aliasname);
}
Keystore Import packages
import com.sap.it.api.keystore.KeystoreService;
import com.sap.it.api.keystore.exception.KeystoreException;
 Sample Code
def service = ITApiFactory.getApi(KeystoreService.class,

null);

{
//Get all trust manager implementation instances
using the service for the default trust store
def trustmanager = service.getTrustManagers();
//Get all KeyManager implementation instances using
the service
def keymanagers = service.getKeyManagers(alias);

……………………………
}
10. If you want to access artificats like value mapping, number ranges refer to the table below:
Artifact Sample Script
Value Mapping Import packages

Artifact Sample Script
import
com.sap.it.api.keystore.KeystoreService
;
import
com.sap.it.api.keystore.exception.Keyst
oreException;
 Sample Code
def service =
ITApiFactory.getApi(KeystoreServic
e.class, null);

{
//Get all trust manager
implementation instances using
the service for the default trust
store
def trustmanager =
service.getTrustManagers();
//Get all KeyManager
implementation instances using
the service
def keymanagers =
service.getKeyManagers(alias);
……………………………
}
 Note
○ The script should be saved in the src.main.resources.script folder.

○ In the Properties view, you can also choose Browse to select java scripts or groovy scripts for
custom processing.
○ You can also store external jar(s) in src.main.resources.lib. You can then invoke functions from
these external jar(s) in the script.
Next Steps
There are the following additional Java interfaces for the message processing log (MPL) which you can address
with the script step (either in Groovy Script or JavaScript):
● MessageLogFactory
Provides access to the message processing log.

● MessageLog
Supports writing properties and adding attachments to the message processing log.
The interface MessageLogFactory can be used through the variable messageLogFactory in order to
retrieve an instance of MessageLog.
You can use the following methods in an instance of MessageLog in order to set a property of a given type in
the message processing log:
● void setStringProperty(String name, String value)

● void setIntegerProperty(String name, Integer value)
● void setLongProperty(String name, Long value)
● void setBooleanProperty(String name, Boolean value)
● void setFloatProperty(String name, Float value)
● void setDoubleProperty(String name, Double value)
● void setDateProperty(String name, Date value)
You can use the following method in an instance of MessageLog in order to add string to an attachment using
message processing log:
● void addAttachmentAsString(String name, String text, String mediaType)
You can use the following method in an instance of MessageLog in order to add, set, get, remove headers to/
from an attachment using message processing log:
● void addAttachmentHeader(String headerName, String headerValue,AttachmentWrapper

attachment)
● void setAttachmentHeader(String headerName, String headerValue,AttachmentWrapper
attachment)
● getAttachmentHeader(String headerName,AttachmentWrapper attachment)
● void removeAttachmentHeader(String headerName, AttachmentWrapper attachment);
You can use the following method in an instance of MessageLog in order to add, set attachment objects as a
map using message processing log:
● Map<String, AttachmentWrapper> getAttachmentWrapperObjects()

● void setAttachmentWrapperObjects(Map<String, AttachmentWrapper>
attachmentObjects)
● void addAttachmentObject(String id, AttachmentWrapper content)
Use method addAttachmentAsString to add a longer, structured document to the message processing log
(MPL). Use method setStringProperty only for short strings (containing one or a few words).
If the value "null" is specified for the parameter mediaType, then the value "text/plain" is assumed as
media type.”
As an example, the following code lines allow you to set a string property:
Groovy:
def messageLog = messageLogFactory.getMessageLog(message)

messageLog.setStringProperty("Greeting", "Hello World!")

JavaScript:
var messageLog = messageLogFactory.getMessageLog(message)

 Caution
Note that the properties provided by the script step are displayed in alphabetical order in the resulting
message processing log (MPL). That means that the sequence of properties in the MPL does not
necessarily reflect the sequence applied in the script.
Related Information
2.5.3.8.1 Script Example for Exception Handling in HTTP

Receiver
Script example to identify any exceptions that arise when sending messages using the HTTP receiver.
You can use Groovy programming language (Groovy script) to identify any exceptions that arise when sending
messages using the HTTP receiver.
The Groovy script provides examples how to do following:
● Save the value of http response as a message attachment
● Copy the value of the http error to a ‘http.ResponseBody’ property
● Copy the value of the http error to the message body
● Copy http error text and error code to properties
1. Copy the following script to the script flow step.
 Sample Code
// get a map of iflow properties

def map = message.getProperties();
// get an exception java class instance

def ex = map.get("CamelExceptionCaught");
if (ex!=null) {
// an http adapter throws an instance of

org.apache.camel.component.ahc.AhcOperationFailedException
if
(ex.getClass().getCanonicalName().equals("org.apache.camel.component.ahc.Ah
cOperationFailedException")) {

// save the http error
response as a message attachment
def messageLog =
messageLogFactory.getMessageLog(message);
messageLog.addAttachmentAsString("http.ResponseBody",
ex.getResponseBody(), "text/plain");
// copy the http error
response to an iflow's property
message.setProperty("http.ResponseBody",ex.getResponseBody());
response to the message body
message.setBody(ex.getResponseBody());
// copy the value of http
error code (i.e. 500) to a property
message.setProperty("http.StatusCode",ex.getStatusCode());
error text (i.e. "Internal Server Error") to a property
message.setProperty("http.StatusText",ex.getStatusText());
}
}
return message;
}
2. Call the script flow step in an exception subprocess.
2.5.4 Defining Message Persistence
Context
Procedure

2.5.4.1 Defining Data Store Operations
You can use the transient data store to temporarily store messages.
Context
The transient data store (data store for sakes of simplicity) supports four types of operations:
Data Store Operations
Operation Used to ...
Write Store the messages temporarily in the data store.
If you use a Write operation, you can store the messages in the data store by configuring the data store
name and a unique Entry ID.
Delete Trigger the deletion of messages in the data store.
Select Fetch messages in bulk from the data store.
You can also specify the number of messages you fetch in each poll.
If you use Select operation, you can transfer only overwritten data fetched from the data store.
Get Fetch a specific message from the data store.
 Note
A data store operations step has to be triggered explicitly, for example, by a Timer event.
Next Steps
You can display the content of the data store in the Data Store Viewer of the Integration Operations feature.
 Note
● In the case of Select operations, you can select multiple messages. The content of the selected
messages will appear in the following format:
<messages>
<message id=”<Entry ID>”>
<Content of selected message>
</message>
………..
……….
……….
</message>

………..
……….
……….
</message>
</messages>
Related Information
Defining Data Store Select Operations [page 262]

Defining Data Store Write Operations [page 264]
Defining Data Store Get Operations [page 266]
Defining Data Store Delete Operations [page 267]
2.5.4.1.1 Defining Data Store Select Operations
You can perform a select operation on the transient data store.
Context
Procedure

2. If you want to add a Data Store Operations step to the integration flow, choose Add Message Persistence-
>Data Store Operations from the context menu of a connection within the pool.
 Note
Adding data store operations enables Write operations by default. Click the Switch to option to choose
the Select operation.
3. Enter the attributes of the step.
 Note
When retrieving a message body from a data store operation, only XML is supported.

Attribute Description
Data Store Name Specifies the name of the data store (no white spaces).
You can dynamically define the data store name based on a header or exchange
property. Use the format ${header.headername} to dynamically read the
name from a header, or ${property.propertyname} to read it from an
exchange property.
The maximum length allowed for the data store name is 40 characters. If you enter
a longer string, a validation error is raised. Note that this length restriction applies
to the value that is used for this parameter at runtime. Therefore, if you configure
this parameter dynamically, make sure that the expected header or property value
does not exceed this length restriction. Otherwise, a runtime error will be raised.
Visibility Defines whether the data store is shared by all integration flows (deployed on the
tenant) or only by one specific integration flow.
○ Global: Data store is shared across all integration flows deployed on the
tenant.
○ Integration Flow: Data store is used by one integration flow.
Number of Polled Messages Specifies the maximum number of messages to be fetched from the data store
within one poll (default is 1).
If the number of messages fetched per poll is specified in the header

SapDataStoreMaxResults, the header takes the precedence.
You can also configure this property in such a way that the number of fetched
messages per poll is dynamically evaluated at runtime based on the incoming
message. To do this, you can enter the following kind of expressions:
○ ${header.headername} to dynamically retrieve the number of fetched

messages per poll from the message header
○ ${xpath.<xpath>} to dynamically retrieve the number of fetched
messages per poll from an element in the message indicated by an xPath
expression
Delete on Completion Select this option to delete a message from the data store after having
successfully processed the message.
Results
There is no in-order processing of data store entries. In other words, the sequence of data store entries
selected with a Select operation is random and non-deterministic. If you have restricted the number of
entries to be fetched (with the Number of Polled Messages attribute), the selection of retrieved entries is also
random.

Related Information
2.5.4.1.2 Defining Data Store Write Operations
Context
Procedure

 Note
Adding data store operations enables Write operations by default.
The data store write operation stores the payload only, not the headers.
Headers are only stored if they are primitive data types, serializable standard data types (such as
strings), or lists/sets of these entities. Any other data types do remain part of the processed message,
but are not considered during a data store operation and so cannot be retrieved from the data store in
subsequent steps.
exchange property.

tenant.
Entry ID Specify an entry ID that will be stored together with the message content.
Details for the entry ID are read from the incoming message. You can enter the
following kinds of expressions:
○ ${header.headername} to dynamically generate the entry ID from the

message header
○ ${property.propertyname} to dynamically generate the entry ID from
the exchange property of the message
○ ${xpath.<xpath>} to dynamically generate the entry ID from an element
in the message indicated by an xPath expression
In the case of Write operations, if the Entry ID is not defined, the data store
component generates an entry ID and sets the SapDataStoreId header with
the generated value.
In the case of Delete and Get operations, you can explicitly define an Entry ID or
pass the header SapDataStoreId.
Retention Threshold for Alerting Time period (in days) within which the messages have to be fetched before an alert
in (d) is raised.
Expiration Period in (d) Number of days after which the stored messages are deleted (default is 90 days,
maximum possible value is 180 days).
The minimum value of Expiration Period should be at least twice that of Retention
Threshold for Alerting.
Encrypt Stored Message Select this option to encrypt the message in the data store.
Overwrite Existing Message Select this option to overwrite an existing message in the data store.
Trying to overwrite an existing entry without having this option selected will result
in a DuplicateEntryException.
Related Information

2.5.4.1.3 Defining Data Store Get Operations
n perform a select operation on the transient data store.
Context
Procedure

 Note
the Get operation.
exchange property.
tenant.


message header
Throw Exception on Missing You have the option to throw an exception if the entry with the specified Entry ID
Entry does not exist in the datastore.
This checkbox is selected by default.
 Remember
If you disable this option, the header SAP_DatastoreEntryFound is set
to false and no exception is thrown, even if the Entry ID does not exist.
Related Information
2.5.4.1.4 Defining Data Store Delete Operations
Context

Procedure

 Note
the Delete operation.
exchange property.
tenant.

message header

Related Information
2.5.4.2 Defining Write Variables
You use write variables to specify values for variables and support message flow execution.
Procedure
2. To add write variables in the integration flow, choose Add Message Persistence Write Variables from
the context menu of a connection within the pool.
3. Select the Write Variables tab in the Properties view.
4. Choose Add.
5. Specify a name for the variable and perform the following substeps to assign values to the variable.
a. To assign a value using an XPath, select xpath in the Type column and enter the XPath expression in the
Value column.
b. 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.
 Note
○ The value for name of the variable must be constant and should not be a reference to some
other value. For example, a valid value is Variable1 and not ${header.source}.
○ The Data Type column is applicable for the xpath and expression types. The data type can be
any Java class. An example of a data type for an XPath is java.lang.String.
c. To assign a value using a header, select header in the Type column and enter the header in the Value
column.
d. To assign an external parameter, select external parameter in the Type column and define a parameter
key.
 Note
Defining multiple parameters in the same field or column is not supported for tables.
e. To assign a property, select property in the Type column.


 Note
○ If you want the variable to be used in multiple integration flows, select the global scope checkbox.
○ By default, stored variables are deleted 400 days after the last update; the system raises an alert 2
days before the variables expire.
○ The default data store name for variables is ‘sap_global_store’. You should not use this value as the
data store name for data store operations.
○ Variables should not have same name as header id in integration flow.
○ Properties are local variables.
○ Variables cannot be downloaded using data store viewer.
2.5.4.3 Configuring Message Storage at a Process Step
Context
You use this task to configure a process step to store a message payload so that you can access the stored
message and analyze it at a later point in time.
In the integration flow, you mark a process step for persistence by specifying a unique step ID, which can be a
descriptive name or a step number. For example, a step ID configured after a mapping step could be
MessageStoredAfterMapping.
At runtime, the runtime node of the cluster stores information, such as GUID, MPL GUID, tenant ID, timestamp,
or payload, for the messages at the process steps that have been marked for persistence.
The message storage feature is useful for the following cases
● Auditing: The SaaS Admin can use this feature to analyze messages that have been processed.
 Note
Messages can be stored in the runtime node for 90 days, after which the messages are automatically
deleted.
● Providing access to data owned by the customer : Since messages are processed on behalf of the
customer, you might need to access the customer-owned data after the messages have been processed to
provide it to the customer.
Procedure
1. Open the <integration flow>.iflw on the Model Configuration editor page.

2. Determine if you want to store the message payload before or after a process step.
For example, you can store the message payload before and after a mapping step, so you add Persist
Message at the two points.

3. In the Model Configuration editor, right-click the connection at the determined point within the pool and
choose the Add Persist Message option.
4. In the Model Configuration editor, select the Persist Message element.
5. In the Properties view, retain the auto-generated step ID for the process step, or edit it if required.
6. If you want to encrypt the message payload that is stored at the step ID, choose Encrypt the stored
message payload.
2.5.5 Validating Message Payload against XML Schema
The XML validator validates the message payload in XML format against the configured XML schema.
Prerequisites
You have the XML schema (XSD files) added in the .src.main.resources.xsd location of your integration flow
project. If you do not thave the specified location in your project, you need to create one first and then add the
XSD files.
Context
You use this procedure to assign XML schema (XSD files) to validate the message payload in a process step.
The validator checks the message payload against configured XML schema, and report discrepencies in
message payload. If the validation fails, the SAP Cloud Platform Integration system stops the whole message
processing by default.
Procedure

2. To add a XML Validator step to the integration flow, choose Message Validator->Validator from the context
menu of a connection within the pool.
3. Select the XML Validator tab in the Properties view.
4. In the Name field, enter an appropriate validator flow step name.

5. In the XML Schema field, select Browse.
6. Choose an XSD file that you want to use to validate the format.
 Note
○ You can have references to other XSDs within the same project. XSDs residing outside the projects
cannot be referred.

○ You can enter a value less than 5000 for attribute maxOccurs, in input xsd. You can also enter
unbounded, if you do not want to check for max occurrence but would like to support any number
of nodes.
○ If there are any validation errors in the payload, the details of the error is visible in MPL
attachment. The link for the attachment is available in MPL log.
○ Use ${header.XmlValidationResult to get more details on validation excecptions.
7. If you want to continue the processing even if the system encounters error while validating, then select the
check box Prevent Exception on Failure.
 Note
If an exception occurs, then the error payload is added to SAP_XmlValidationResult header.
2.5.6 Defining Message Routing
Context
Procedure
2.5.6.1 Defining Router
Prerequisites
You have selected the Content-Based Router (Multiple Interfaces/Multiple Receivers) pattern or you have added
the router element to the integration flow model from the palette.

Context
You perform this task when you have to specify conditions based on which the messages are routed to a
receiver or an interface during runtime. If the message contains XML payload, you form expressions using the
Xpath-supported operators. If the message contains Non-XML payload, you form expressions using the
operators shown in the table below:
Usage of Operators in Non-XML Conditions

Operator Example
= ${header.SenderId} = '1'
!= ${header.SenderId} != '1'
> ${header.SenderId} > '1'
>= ${header.SenderId} >= '1'
< ${header.SenderId} < '1'
<= ${header.SenderId} <= '1'
and ${header.SenderId}= '1' and ${header.ReceiverId} = '2'
or ${header.SenderId}= '1' or ${header.ReceiverId}= '2'
contains ${header.SenderId} contains '1'
not contains ${header.SenderId} not contains '1'
in ${header.SenderId} in '1,2'
not in ${header.SenderId} not in '1,2'
regex ${header.SenderId} regex '1.*'
not regex ${header.SenderId} not regex '1.*'
 Example
A condition with expression ${header.SenderId} regex '1.*' routes all the messages having Sender
ID starting with 1.
 Note
● You can define a condition based on property or exception that may occur.
● If condition ${property.SenderId} = '1' is true, then router routes the message to a particular
sender having Sender ID as 1.
● If condition ${exception.message}contains 'java.lang.Exception' is true, then router
routes the message to a particular receiver else it routes to other receiver.
Procedure

2. If you want to add a router at any point in the integration flow, follow the steps below:
a. Right-click a connection within the pool and choose Add Routing.
b. Right-click the added Router notation and choose the relevant option, either Add Receiver or Add
Interface.
3. In the Model Configuration editor, select one of the routing branches splitting from the router.
4. On the Route tab of the Properties view, enter a descriptive name for the routing branch.
5. From the Expression Type dropdown, select the type of expression used to formulate the routing condition.
a. Select XML to form an expression using Xpath.
b. Select Non-XML to form an expression using message header, property or exception.
6. In the Condition field, formulate a valid XML or non-XML condition that routes the message to its
associated receiver.
 Recommendation
We recommend you to ensure that the routing branches of a router are configured with the same type
of condition, either XML or non-XML, and not a combination of both. At runtime, the specified
conditions are executed in the same order as displayed in the Properties view of the Router. If the
conditions are a combination of both non-XML and XML type, the evaluation fails.
 Tip
To quickly configure routing conditions, select Define Condition from the context menu of the routing
branch.
7. If you want to set the selected route as the default, such that, its associated receiver handles the error
situation if no receiver is found, select the Default Route option.
 Note
Only the route that was recently selected as Default Route is considered as the default route.
 Tip
To quickly set a route as a default route from the Model Configuration editor tab page, select Set as
Default Route from the context menu of routing branch.
8. In the Model Configuration editor, select the Router notation.

9. In the Properties view, under Routing Behavior, select Raise Alert or Throw Exception to set the behavior if
no receiver is found.
 Note
To configure an alert, see the Alert Configuration section in the Operations Guide.
10. To model the integration flow when no receiver is found, follow the steps below:
a. From the Palette select the Terminate End notation and drop it inside the pool in the Model
Configuration.
b. Place the cursor on the Router to select the connection from the hover menu and drag the connection
to the Terminate End notation.

 Note
If you do not add the Terminate End notation in your integration flow model, the Raise Alert or
Throw Exception option does not apply.
11. Select the Router notation and, in the Properties view, check the overview of all the routes and their
conditions that you have defined for the scenario.
2.5.6.2 Defining Splitter
A splitter step decomposes a composite message into a series of individual messages and sends them to a
receiver.
Prerequisites
You have selected the Splitter step or you have explicitly added the splitter step to the integration flow model.
Context
You perform this task if you need to break down a composite message into a series of individual messages and
send them to a receiver. You split the composite message based on the message type, for example, IDoc or
PKCS#7/CMS Signature-Content, or the manner in which the message is to be split, for example, general or
iterative splitter.
Procedure

2. If you want to add a splitter to the integration flow, choose Add Splitter from the context menu of the
3. In the Model Configuration editor, select the splitter element.
4. In the Properties view, select a Splitter Type.
Splitter Types
Splitter Type Description
IDoc Is used to split a composite IDoc messages into a series of

individual IDoc messages with the enveloping elements of
the composite IDoc message.

Splitter Type Description
PKCS#7/CMS Signature-Content Is used when an agent sends a PKCS7 Signed Data mes
sage that contains a signature and content. This splitter
type breaks down the signature and content into separate
files.
General Is used to split a composite message comprising of N

messages into N individual messages each containing one
message with the enveloping elements of the composite
message.
 Note
A possible use case for this splitter type is where a
message obtained from a sender contains multiple
account statements and needs to be split into sepa
rate individual messages, each containing the account
statement for one specific account owner.
Typically, the target message also needs to contain

enveloping information such as the bank name or
other attributes to make the account statement com
plete. In this case, it would make sense to choose the
general splitter pattern.
Iterating Is used to split a composite message into a series of mes

sages without copying the enveloping elements of the
composite message.
 Note
A possible use case for this splitter type is where a
message obtained from a sender contains multiple or
ders from different customers and needs to be split
into individual messages. Each resulting message
should contain the order of one customer only and is
to be routed to this customer. In this case it might
make more sense for the resulting split messages to
contain only data that is related to the corresponding
customer, without any of the additional information
that is contained in enveloping elements.
5. Specify the properties of the splitter.

 Example
Consider the following XML payload structure as input for the Splitter step:
<orders>
<order>

<count>100</count>
</order>
<order>
<count>10</count>
</order>
</orders>
If you use Token as Expression Type and enter the order as Token, the XML payload is split into two output
files.
Output1.xml contains the following:
<order>
<count>100</count>
</order>
Output2.xml contains the following:
<order>
<count>10</count>
</order>
Using XPath as Expression Type, you can achieve the same behavior by entering one of the following two
expressions (as XPath)::
● /orders/order (absolute expression for the element <order>))

● //order (relative expression for the element <order>)
Next Steps
When a message is split (as configured in a Splitter step of an integration flow), the Camel headers listed below
are generated every time the runtime finishes splitting an Exchange. You have several options for accessing
these Camel headers at runtime. For example, suppose that you are configuring an integration flow with a
Splitter step before an SFTP receiver adapter. If you enter the string split_${exchangeId}_Index$
{header.CamelSplitIndex} for File Name, the file name of the generated file on the SFTP server contains
the Camel header CamelSplitIndex (in other words, the information on the number of split Exchanges
induced by the Splitter step).
● CamelSplitIndex
● CamelSplitSize
 Note
You can use the Gather step after Splitter in an integration flow if you have configured the Splitter Type as
General or Iterating.

 Restriction
● You cannot use Splitter after Multicast.

● You cannot use two consecutive Splitter elements ending in Gather.
● You cannot use PKCS#7/CMS Splitter within a Subprocess.
Related Information
Defining a General Splitter [page 278]

Defining an Iterating Splitter [page 283]
Defining a PKCS#7/CMS Signature-Content Splitter [page 303]
General and Iterating Splitter [page 304]
2.5.6.2.1 Defining a General Splitter
A general splitter is used to split a composite message comprising of N messages into N individual messages
each containing one message with the enveloping elements of the composite message.
Context
A possible use case for this splitter type is where a message obtained from a sender contains multiple account
statements and needs to be split into separate individual messages, each containing the account statement for
one specific account owner.
Typically, the target message also needs to contain enveloping information such as the bank name or other
attributes to make the account statement complete. In this case, it would make sense to choose the general
splitter pattern.
Procedure

4. In the Properties view, select General as Splitter Type.
5. Specify the attributes.

Field Description
Expression Type Specify the expression type you want to use to define the
split point (the element in the message structure below
 Note which the message is to be split).
In the following cases certain features might not be

 Note
available for your current integration flow:
○ A feature for a particular adapter or step was re The defined Stop on Exception handling takes priority
leased after you created the corresponding over the end event defined in an exception subpro
shape in your integration flow. cess with respect to continuing with the next split. It
○ You are using a product profile other than the one means that the next split is only executed if Stop on
expected. Exception is not set.
More information: Adapter and Integration Flow Step If Stop on Exception is set, the next split is not exe
Versions [page 406] cuted, irrespective of the end event used in an excep
tion subprocess.
The following options are available:
○ XPath
The splitter argument is specified by an XPath ex
pression.
○ Line Break
If the input message is a non-XML file, it is split ac
cording to the line breaks in the input message.
Empty lines in input messages will be ignored and no
empty messages are created.

Field Description
XPath Expression XPath to the split term
(Enabled only if you select XPath in the Expression Type You can specify the absolute or relative path.
field)
 Note
Note that only the following types of XPath expres
sions are supported:
○ Absolute XPath expressions, for exam

ple, /A/B/C/D
○ Relative XPath expressions, for example, //D
The following characters are not supported in an

XPath expression:
○ |
○ +
○ *
○ >
○ <
○ >=
○ <=
○ [
○ ]
○ @
 Note
When addressing elements with namespaces in the
Splitter step, you have to specify them in a specific
way in the XPath expression, and the namespace dec
laration in the incoming message must follow a cer
tain convention:
Assume that the incoming message contains an ele

ment root with a namespace, for example:
<root xmlns:n0=“http://
myspace.com“></root>
To address this element in the Splitter step, you need

to enter the following XPath expression: /n0:root.
Using XPath expression /root will lead to an error in

that case.
 Caution
You cannot split by values of message elements.

Field Description
Consider the following inbound message:
<customerList>
<customers>
<customerNumber>0001</
customerNumber>
<customerName>Paul Smith</
customerName>
</customers>
<customers>
customerNumber>
<customerName>Seena
Kumar</customerName>
</customers>
</customerList>
In that case, using the following XPath expression will

not be supported to split the message at the
customerNumber node with the value 0001:
/customerList/customers/
customerNumber=0001
 Note
Note the following behavior if the specified XPath ex
pression does not match the inbound payload: If no
split point is found for the specified XPath, no out
bound payload will be generated from the Splitter
step and the integration flow will be ended with status
Completed.
Grouping The size of the groups into which the composite message
is to be split.
For example, if a message has 10 nodes and grouping is

defined as 2, the message is split into 5 messages with 2
nodes each.
Streaming Select this option if you want to stream the process of

splitting a large composite message.
If you activate streaming, the system already starts proc

essing parts (chunks) of the composite message before
the message is fully transferred to the memory (of the
runtime node).
If you deactivate this option, the message is transferred

fully to the memory before it is split and processed fur
ther. Deactivating streaming is more memory-intensive
than activating it.

Field Description
Parallel Processing Select this checkbox if you want to enable (parallel) proc
essing of all the split messages at once.
Number of Concurrent Processes If you have selected Parallel Processing, the split mes
sages are processed concurrently in threads. Define how
(Enabled only if Parallel Processing is selected)
many concurrent processes to use in the splitter. The de
fault is 10. The maximum value allowed is 50.
Timeout (in s) Maximum time in seconds that the system will wait for
processing to complete before it is aborted. The default
value is 300 seconds.
 Caution
Note that after the specified timeout the splitter proc
essing stops without exception.
This behavior can lead to unexpected results (even

data loss) if not all message splits are processed
within the timeout period.
Stop On Exception Select this option to stop message processing if an excep

tion occurs.
 Note
If Stop on Exception is set, the exception subprocess
has no effect on the exception. The processing is
stopped, and the message is set to Failed.
Related Information

https://blogs.sap.com/2018/01/16/stop-on-exception-for-iteratinggeneral-splitter/

2.5.6.2.2 Defining an Iterating Splitter
An iterating splitter is used to split a composite message into a series of messages without copying the
enveloping elements of the composite message.
Context
A possible use case for this splitter type is where a message obtained from a sender contains multiple orders
from different customers and needs to be split into individual messages. Each resulting message should
contain the order of one customer only and is to be routed to this customer. In this case it might make more
sense for the resulting split messages to contain only data that is related to the corresponding customer,
without any of the additional information that is contained in enveloping elements.
Procedure

4. In the Properties view, select Iterating as Splitter Type.

Field Description
which the message is to be split).
 Note
The defined Stop on Exception handling takes priority
over the end event defined in an exception subpro
cess with respect to continuing with the next split. It
means that the next split is only executed if Stop on
Exception is not set.
If Stop on Exception is set, the next split is not exe

cuted, irrespective of the end event used in an excep
tion subprocess.
○ XPath
pression.
○ Token
The splitter argument is specified by a keyword.
○ Line Break
Token (Enabled only if you select Token in the Expression The keyword or token to be used as a reference for split
Type field) ting the composite message

Field Description
XPath XPath to the split term
field)
 Note

ple, /A/B/C/D

XPath expression:
○ |
○ +
○ *
○ >
○ <
○ >=
○ <=
○ [
○ ]
○ @
 Note
tain convention:



that case.
 Caution

Field Description
<customerList>
<customers>
customerNumber>
customerName>
</customers>
<customers>
customerNumber>
<customerName>Seena
</customers>
</customerList>

customerNumber=0001
is to be split.

nodes each.


runtime node).

than activating it.
Parallel Processing Select this checkbox if you want to enable processing of all
the split messages at once.

Field Description
 Caution


tion occurs.
 Note
If Stop on Exception is set, the exception sub-process
stopped, and message is set to Failed.
Related Information

https://blogs.sap.com/2018/01/26/grouping-option-of-iteratinggeneral-splitter/
2.5.6.2.3 Defining EDI Splitter
Context
You use the EDI splitter to split inbound bulk EDI messages, and during processing you can configure the
splitter to validate and acknowledge the inbound messages. If you choose to acknowledge the EDI message,
then the splitter transmits a functional acknowledgement after processing the bulk EDI message. A bulk EDI
message can contain one or more EDI formats, such as EDIFACT, EANCOM, and ASC-X12. You can configure
the EDI splitter to process different EDI formats depending on the business requirements of the trading
partners.

Consider a use case where a bulk EDI message received from a sender contains more than one business
document in EDIFACT format. According to the requirement, the bulk EDI message needs to be split at
message level and routed to specific partners as shown in the figure below. After splitting, the EDI splitter
validates the document and creates a functional acknowledgement that can be routed and transmitted to the
sender. In the next process, the individual EDI messages are converted and extracted. Then the process routes
individual messages to specific business partners.
Procedure

2. From the Message Routing context menu, drag and drop the splitter element into the integration flow.
3. Right click on the Splitter, and choose Switch to EDI Splitter.
4. In the Properties view, provide values in the fields based on the descriptions in the table.

Field Description
Name Define a relevant name for the EDI splitter or

use the default name.
Parallel Processing This mode creates multiple processes for

each split message, and individual EDI mes
sages are processed simultaneously.
Timeout (in sec) Set the time limit in seconds for the EDI split
ter to process individual split messages. If
there are any processes still pending once the
time has lapsed, the splitter terminates the
processes and updates the MPL status.
EDIFACT
Source Encoding Use the appropriate encoding format of the in

bound EDIFACT interchange. The following en
coding formats are available in the EDI split
ter:
○ UTF-8
○ ISO-8859-1
You can also set this field using the header

EDISPLITTER_EDIFACT_SOURCE_ENCO
DING. The values for the headers can be one
of the following:
○ UTF-8
○ ISO-8859-1
Validate Message This mode initiates the validation of the split

EDI messages.

EDISPLITTER_EDIFACT_VALIDATE_ME
SSAGE. The values for the headers can be one
of the following:
○ true
○ false

Field Description
Validate The EDI splitter performs validation of either

Envelope or Envelope and Message for the EDI
content.

EDISPLITTER_EDIFACT_VALIDATION_
METHOD. The values for the headers can be
one of the following:
○ envelop
○ envelopAndMessage
Transaction Mode This feature is available only in Envelope and

Message validation mode. The following two
options are available:
○ Interchange: Allows the splitter to validate
the entire EDI interchange as a single en
tity.
○ Message: Allows the splitter to validate
the entire EDI interchange as independ
ent individual entities.
 Example
Consider a scenario where you receive a
bulk EDI message containing five pur
chase orders. In Interchange mode, if a
single EDI message fails, the entire inter
change is rejected. However, in Message
mode, if a single EDI message fails, only
the invalid message is rejected and the
valid messages are dispatched for further
processing.

EDISPLITTER_EDIFACT_TRANSACTION
_MODE. The values for the headers can be one
of the following:
○ interchange
○ message

Field Description
EDI Schema Definition Validates an EDI interchange against the XSD

schema for conversion. Deploy the schema by
selecting it from an integration flow or by de
fining the location of the schema.
Follow the steps here to add an *.xsd file to

the integration flow:
1. In the EDI Schema Definition, select
Integration Flow.
2. Choose Add from the Schemas table.
3. Select a row from the table, and choose
to add an XML Schema file from

the XSD folder found in the integration
project.
 Note
If you wish to remove an XSD file
from the project, then select the rele
vant XSD file and choose Remove.

EDISPLITTER_EDIFACT_SCHEMA_SOUR
CE. The values for the headers can be one of
the following:
○ Header
○ IntegrationProject
Process Invalid Messages If you select this option, then all the invalid
split messages are routed through new route
where the condition is defined as
EDI_MESSAGE_STATUS=failure.
In the acknowledgement header, if you find

EDI_INTERCHANGE_STATUS=failure
it notifies you that an error has occurred while
processing the interchange.

Field Description

HeaderName, in Properties view. Enter a valid
header name for the field.
 Note
This header name is fetched from camel
header. The header is added in script ele
ment. This script element is added before
converter element. You can add value for
this header in the script element.

value, /xsd/UN-
EDIFACT_ORDERS_D96A.xsd for ED
IFACT.

value, /xsd/ASC-
X12_810_004010.xsd for ASC-X12.

Field Description
Create Acknowledgement The following options are available to process

the functional acknowledgement:
○ Not Required: Does not transmit the func
tional acknowledgement.
○ Check EDI Envelop: Allows the splitter to
check the request for a functional ac
knowledgement in the UNB segment of
an EDI interchange.
○ Required: The splitter creates and trans
mits a functional acknowledgement.

EDISPLITTER_EDIFACT_CREATE_ACK.
The values for the headers can be one of the
following:
○ required
○ notRequired
○ checkEDIEnvelop
 Note
In case of rules violation, you see the ac
knoedgement in a specific format. Here's
how the acknowledge is formatted:
AK4 is represented only for the first ele

ment of the conditional rule. For example,
AK4*2*358*2.
If there are two or more violations for a

single element, the same AK4 segment is
repeated for each violation. For example,
AK4*2*358*2 AK4*2*358*2
If there is an exclusive violation, AK4 is

represented for only the first element. For
example, AK4*2*358*10.

Field Description
Interchange Number The splitter uses the interchange number of

an EDI message in the functional acknowledg
ment. It allows the splitter to read the inter
change number either from the EDI message
or from an assigned set of number ranges.

EDISPLITTER_EDIFACT_INTERCHANGE
_NUMBER. The values for the headers can be
○ useFromEDIMessage
○ numberRange
Number range Define the number range assigned to an inter

change number in the functional acknowl
edgement.

EDISPLITTER_EDIFACT_NUMBER_RANG
E. The value for the header should be the
number range artifact name.
CONTRL Message Version Determine the appropriate EDIFACT CONTRL

message version to be transmitted to the
trading partner.

EDISPLITTER_EDIFACT_CONTRL_MSG_
VERSION. The values for the headers can be
○ defaultVersion
Include UNA Segment The trading partner uses the UNA segment in
the CONTRL message to define special char
acters, such as separators and indicators.
This option enables the splitter to include spe
cial characters in the CONTRL message. If not
selected, the UNA segment is not included in
the CONTRL message.

EDISPLITTER_EDIFACT_INCLUDE_UNA
. The values for the headers can be one of the
following:
○ true
○ false

Field Description
X12

bound X12 interchange. The following encod
ing formats are available in the EDI splitter:
○ UTF-8
○ ISO-8859-1

EDISPLITTER_X12_SOURCE_ENCODING
following:
○ UTF-8
○ ISO-8859-1
Validate Message The EDI splitter performs validation on incom

ing ASC X12 message against the XSD
scheme, and has the following options availa
ble during validation:
○ No Validation: Validation is not performed
on the incoming payload.
○ Standard Validation : Validates the incom
ing payload for the structural violations
defined in XSD schema.

EDISPLITTER_X12_VALIDATE_MESSAG
E_OPTION. The values for the headers can
be one of the following:
○ none
○ basic
Transaction Mode The splitter has two modes for validating a

transaction:
tity.

EDISPLITTER_X12_TRANSACTION_MOD
E. The values for the headers can be one of
the following:
○ interchange
○ message

Field Description


Integration Flow.
3. Select a row from the table, and choose
to add an XML Schema file from

the XSD folder found in the integration
project.
 Note
If you wish to remove an XSD file
from the project, then select the rele
vant XSD file and choose Remove.

EDISPLITTER_X12_SCHEMA_SOURCE.
following:
○ Header

Field Description

 Note

value, /xsd/UN-
IFACT.

value, /xsd/ASC-
X12_810_004010.xsd for ASC-X12.
Create Acknowledgement The following options are available for proc

essing a functional acknowledgement:
an EDI interchange.

EDISPLITTER_X12_CREATE_ACK. The
values for the headers can be one of the fol
lowing:
○ required
○ notRequired
○ checkEDIEnvelop

Field Description


EDISPLITTER_X12_INTERCHANGE_NUM
BER. The values for the headers can be one of
the following:
○ numberRange
Number Range Define the number range assigned to an inter

edgement.

EDISPLITTER_X12_NUMBER_RANGE.
The value for the header should be the num
ber range artifact name.
Exclude AK3 and AK4 Notifies the splitter to exclude the AK3 and
AK4 segments from the functional acknowl
edgement message. However, it retains the
details of the AK1, AK2, AK5, and AK9 seg
ments in the functional acknowledgement.

EDISPLITTER_X12_EXCLUDE_AK3_AK4
following:
○ true
○ false
Error Codes for EDI Splitter
The error codes for UN-EDIFACT interchange and message levels are given below:
Interchange Level
Error Code Error Text NotifiesThat...
2 Syntax version and/or level is not supported by the recipi

ent.

 Note
If you select Interchange transaction mode, the splitter treats the entire EDI interchange as a single
entity, and includes interchange errors in the acknowledgement.
Interchange and Message Level
18 An error has been identified, but the nature of the error is

not reported.
28 The control reference in UNB, UNG, or UNH does not

match the one in UNZ, UNE, or UNT respectively.
29 The number of groups, messages, or segments does not

match the number given in the UNZ, UNE, or UNT seg
ment.
30 Groups have been mixed with messages/packages out

side of groups in the interchange.
Message Level
Error Code Error Text Notifies That...
12 The value of a stand-alone data element, composite data

element, or component data element does not conform to
the relevant specifications for the value.
13 Mandatory (or otherwise required) service or user seg

ment, data element, composite data element, or compo
nent data element is missing.
16 The identified segment contains too many data elements

or the identified composite data element contains too
many component data elements.
31 Different message types are contained in a functional

group.
35 A segment was repeated too many times.
36 A segment group is repeated to many times.
37 One or more numeric characters were used in an alpha

betic (component) data element or one or more alpha
betic characters were used in a numeric (component)
data element.
38 A decimal sign is not preceded by one or more digits.

39 The length of the data element received exceeds the maxi

mum length specified in the data element description.
40 The length of the data element received is shorter than

the minimum length specified in the data element descrip
tion.
The error codes for ASC-X12 are given below:
AK3 Segment Level Error Codes
Error Codes Error Text Notifies That...
3 Mandatory segment is missing.
4 Maximum number of loops exceeded.
5 Segment exceeds maximum use.
6 Segment is not defined in transaction set.
7 Segment is not in proper sequence.
AK4 Data Element Level Error Codes
1 Mandatory data element is missing.
3 Too many data elements.
4 Data element is too short.
5 Data element is too long.
6 Invalid character in data element.
7 Invalid code value.
8 Invalid date.
AK5 Transaction Set Level Error Codes
3 Transaction set control number in header and trailer do

not match.
4 Number of included segments does not match actual

count.

AK9 Functional Group Level Error Codes
4 Group control number in the functional group header and

trailer do not match.
5 Number of included transaction sets does not match ac

tual count.
 Example
EANCOM Document Standard
The following segments are part of message payload of EANCOM, and the table below mentions the
headers and values for the given payload.
UNB+UNOC:3+4006501000002:14+5790000016839:14+100818:0028+0650+++++XXXXX'
UNH+1+INVOIC:D:96A:EN:EAN008'
Value for EANCOM Document Standard
Header Name Value
SAP_EDI_Payload_Format XML or Flat-File
SAP_EDI_Document_Standard EANCOM
SAP_EDI_Sender_ID 4006501000002
SAP_EDI_Sender_ID_Qualifier 14
SAP_EDI_Receiver_ID 5790000016839
SAP_EDI_Receiver_ID_Qualifier 14
SAP_EDI_Interchange_Control_Number 0650
SAP_EDI_Message_Type INVOIC
SAP_EDI_Message_Version D
SAP_EDI_Message_Release 96A
SAP_EDI_Message_Controlling_Agency EN
SAP_EDI_Message_Association_Assign_Code EAN008
EDIFACT Document Standard
The element creates camel headers and populates it with respective extracted values. For example, if
following segments are part of message payload of EDIFACT, then respective headers and values for the
same are given in the table below.
UNB+UNOC:3+4006501000002:14+5790000016839:14+100818:0028+0650+++++XXXXX'

UNH+1+INVOIC:D:96A:UN'
Value for EDIFACT Document Standard
Header Name Value
SAP_EDI_Document_Standard UN-EDIFACT
SAP_EDI_Message_Controlling_Agency UN
ASC-X12 Document Standard
If following segments are part of message payload of ASC-X12 , then respective headers and values for the
ISA*00* *00* *ZZ*WWRESNDR *ZZ*WWRERCVR *020709*0816*U*00401*000046668*0*P*:~
GS*IN*GSRESNDR*GSRERCVR*20030709*0816*12345*X*004010~
810*0001~
Value for ASC-X12 Document Standard
Header Name Value
SAP_EDI_Document_Standard ASC-X12
SAP_EDI_Sender_ID WWRESNDR
SAP_EDI_Sender_ID_Qualifier ZZ
SAP_EDI_Receiver_ID WWRERCVR
SAP_EDI_Receiver_ID_Qualifier ZZ

Header Name Value
SAP_EDI_Message_Type 810
SAP_EDI_Message_Version 004010
SAP_EDI_GS_Sender_ID GSRESNDR
SAP_EDI_Receiver_ID GSRERCVR
SAP_EDI_GS_Control_Number 12345
SAP_GS_Functional_Id_Code IN
SAP_GS_Responsible_Agency_Code X
SAP_ISA_Acknowledgment_Requested 0
SAP_ISA_Auth_Information_Qualifier 00
SAP_ISA_Control_Standards_Identifier
SAP_ ISA_Security_Information_Qualifier 00
SAP_ISA_Usage_Indicator P
SAP_ISA_Version_Number 004010
SAP_MessageProcessingLogID
SAP_ST_Control_Number
2.5.6.2.4 Defining a PKCS#7/CMS Signature-Content

Splitter
The PKCS#7/CMS Signature-Content splitter is used when an agent sends a PKCS7 Signed Data message that
contains a signature and content. This splitter type breaks down the signature and content into separate files.
Context

Procedure

4. In the Properties view, select PKCS#7/CMS Signature-Content as Splitter Type.
Field Description
Payload File Name Name of the file that should contain the payload after the
splitting step
Signature File Name Name of the file (extension .sig) that should contain the
signature after the splitting step
Wrap by Content Info Select this option if you want to wrap PKCS#7 signed data
containing the signature into PKCS#7 content.
PayloadFirst Select this option if you want the payload to be the first
message returned.
BASE64 Payload Select this option if you want to encode the payload with
the base64 encoding scheme after splitting.
BASE64 Signature Select this option if you want to encode the signature us
ing the base64 encoding scheme after splitting.
Related Information
Signing the Message Content with PKCS#7/CMS Signer [page 319]
2.5.6.2.5 General and Iterating Splitter

The two splitter types General Splitter and Iterative Splitter behave differently in their handling of the
enveloping elements of the input message.
The General Splitter splits a composite message comprising N messages into N individual messages, each
containing one message with the enveloping elements of the composite message. We use the term enveloping
elements to refer to the elements above and including the split point.
The Iterative Splitter splits a composite message into a series of messages without copying the enveloping
elements of the composite message.

The following figures illustrate the behavior of both splitter types. In both cases an input message comprising
four items is split into individual messages.
General Splitter

Iterative Splitter
If you expect a non-XML file as the input message and, as a result, selectLine Break in the Expression Type field,
General Splitter and Iterative Splitter process the message differently, as shown for the following example.
Let's assume the input message has the following content:
 Sample Code
"Customer Number", "No of Ordered Articles", "Price"

"0001", "100", "1000 EUR"
"0009", "1", "10000 EUR"
"0011", "20", "999 EUR"
The General Splitter would transform this into the following messages:

"0001", "100", "1000 EUR"

"0009", "1", "10000 EUR"

"0011", "20", "999 EUR"

The Iterative Splitter would transform this into the following messages:
"0001", "100", "1000 EUR"
"0009", "1", "10000 EUR"
"0011", "20", "999 EUR"
Example for General Splitter (XML Message)
Assume you expect an XML message and like to address elements with a Expression Type XPath. This is an
example for an input message representing items ordered by a certain customer.
<customer xmlns="http://myCustomer.com">
<customerNumber>0001</customerNumber>
<customerName>Paul Smith</customerName>
<order id="100">
<items>
<item>Shirt</item>
<item>Shoe</item>
</items>
</order>
<order id="101">
<items>
<item>Shoe</item>
<item>Car</item>
<item>Watch</item>
</items>
</order>
</customer>
To split this message, you need to define a namespace mapping (of a prefix and a namespace) for the
integration flow (under Runtime Configuration), for example: xmlns:n1=http://myCustomer.com.
When configuring the General Splitter and like to address the message element with an XPath expression,
make sure that you refer to the namespace prefix.
Use the following XPath expression:
/n1:customer/n1:order
 Note
Namespaces are inherited from parent to child element. This is why you need to indicate the namespace
explicitly in the XPath expression.
Then the message is split with the General Splitter into the following two chunks:
<order id="100">
<items>
<item>Shirt</item>
<item>Shoe</item>
</items>

</order>
</customer>
<order id="101">
<items>
<item>Shoe</item>
<item>Car</item>
<item>Watch</item>
</items>
</order>
</customer>
Example for Iterative Splitter (XML Message)
This is an example for an input message representing orders from different customers.
<customerList xmlns=”http://myCustomer.com”>
<customers>
</customers>
<customers>
<customerName>Seena Kumar</customerName>
</customers>
</customerList>
/n2:customerList/n2:customers
Then the message is split with the Iterative Splitter into the following two chunks:
<customers>
</customers>
<customers>
</customers>

2.5.6.3 Defining an Aggregator
You can use the Aggregator step to combine multiple incoming messages into a single message.
Prerequisites
 Caution
Context
 Note
When you use the Aggregator step in combination with a polling SFTP sender adapter and you expect a
high message load, please consider the following recommendation:
For the involved in SFTP sender adapter set the value for Maximum Messages per Poll to a small number
which is larger than 0 (for example, 20) (under Advanced Parameters). That way, you ensure a proper
message processing status logging at runtime.
Procedure
1. Open the related integration flow and select an Aggregator step (in the palette under Message Routing).
2. Open the Properties view for the step.
3. Specify which incoming messages belong together and are to be aggregated. To do that, open Correlation
tab and enter an XPath expression that identifies an element based on which the incoming messages
should be correlated (in the field Correlation Expression (XPath)).
This attribute determines the messages which are to be aggregated in the following way: messages with
the same value for the message element defined by the XPATH expression are being stored in the same
aggregate.
4. Open the Aggregation Strategy tab and specify the following attributes:

Incoming Format Content type of the incoming message
Currently, only XML (Same Format) can be selected.
It is important that the incoming messages have the same

format.
Aggregation Algorithm Specifies how the correlated messages should be treated.
○ Combine in Sequence
Aggregated message contains all correlated incoming
messages, and the original messages are put into a
sequence.
○ Combine
messages.
The Aggregator step generates an SAP Process Integra

tion multi mapping as specific format. This is important
to know because the integration developer typically has to
create a mapping from the generated format to the mes
sage structure required by the receiver.
Message Sequence Expression (XPath) Enter an XPath expression for that message element
based on which a sequence is being defined.
(only if for Aggregation Algorithm the option Combine in
Sequence has been selected) You can use only numbers to define a sequence. Each se
quence starts with 1.
Last Message Condition (XPath) Define the condition (XPATH = value) to identify the
last message of an aggregate.
You have the option to use an Router step after the

Aggregator in order to evaluate the Camel $
{header.CamelAggregatedCompletedBy} at
tribute, and, based on the value, decide how to continue.
Note that the header attribute can only have one of the
following values:
○ timeout
Processing of the aggregate has been finished be
cause the configured Completion Timeout has been
reached.
○ predicate
cause the Completion Condition has been fulfilled.

Completion Timeout Defines the maximum time between two messages before
aggregation is being stopped (period of inactivity).

following values:
○ timeout
reached.
○ predicate
Data Store Name Enter the name of the transient data store where the ag
gregated message is to be stored. The name should begin
with a letter and use characters (aA-zZ, 0-9, - _ . ~ ).
Note that only local data stores (that apply only to the in
tegration flow) can be used. Global data stores cannot be
used for this purpose.
 Note
The Integration Operations feature provides a Data
Store Viewer that allows you to monitor your transient
data stores.
Results
The Aggregator step creates a message in the multi-mapping format with just one message instance:

<sm:Messages xmlns:sm="http://sap.com/xi/XI/SplitAndMerge">
<Message1>
...
</Message1>
</sm:Messages>

Next Steps
The following header is supported by this step:
○ timeout
reached.
○ predicate
Related Information
Multi-Mappings [page 382]
2.5.6.4 Defining Multicast of Messages
Prerequisites
● You have created an integration project and integration flow.

● You have opened the Integration Designer perspective.
Context
Multicast enables you to send the same message to more than one receiver. This allows you to perform
multiple operations on the same message in a single integration flow. Without multicast, you require separate
integration processes to perform different operations on the same incoming message.
There are two types of multicast that you can choose:
1. Parallel multicast
2. Sequential multicast
Parallel multicast initiates message transfer to all the receiver nodes in parallel.
Sequential multicast provides an option to define the sequence in which the message transfer is initiated to the
receiver nodes.
If you want to aggregate the message that is sent to more than one receiver node, you can use the join and
gather elements.

 Restriction
1. You cannot use Process in Batches option in SuccessFactors adapter with SOAP message protocol
within a multicast branch. For more information, see Configuring SuccessFactors Adapter with SOAP
Message Protocol [page 156].
2. You cannot use Splitter within a Multicast branch.
3. If you are using SFTP receiver with parallel multicast, the message might be corrupted in one or more
of the Multicast branches. The message is corrupted in the branches where the SFTP receiver does not
write the complete data in its respective SFTP files.
You can overcome this limitation in two ways:
1. Add a content modifier before the SFTP receiver. In the content modifier, specify the Body as $
{bodyAs(byte[])}.
2. You can switch from parallel multicast to sequential multicast.
 Remember
You cannot use Exception Subprocess with Multicast as Exception Subprocess is not executed in case of an
exception within the Multicast branches.
If you want to enable the execution of Exception Subprocess when an exception occurs in one of the
Multicast branches, ensure that you use version 1.1 of both Multicast and Integration Process.
Procedure
You use this procedure to add a multicast and join elements to your integration flow.
1. In the Model Configuration editor, access the palette.
2. If you want to add a multicast or join element, perform the following substeps.
a. Choose Message Routing.
b. If you want to add parallel multicast, drag the element from palette to the integration
flow.
c. If you want to add sequential multicast, drag the element from the palette to the
integration flow.
3. If you want to combine the messages, see Defining Join and Gather [page 314].
4. Add the necessary elements based on your scenario to complete the integration flow.

2.5.6.5 Defining Join and Gather
Context
The Join element enables you to bring together the messages from different routes before combining them into
a single message. You use this in combination with the Gather element. Join only brings together the messages
from different routes without affecting the content of messages.
The Gather step enables you to merge messages from more than one route in an integration process. You
define conditions based on the type of messages that you are gathering using the Gather step. You can choose
to gather:
1. XML messages of different format

2. XML messages of the same format
3. Plain text messages
Based on this, you choose the strategy to combine the two messages.
● For XML messages of the same format, you can combine without any conditions (multimapping format) or
specify the XPath to the node at which the messages have to be combined.
● For XML messages of different formats, you can only combine the messages
● For plain text messages, you can only specify concatenation as the combine strategy
● Specify valid xpath expression that includes namespace prefixes if incoming payload contains namespace
declarations, including default namespace declarations.
 Remember
● If you want to combine messages that are transmitted to more than one route by Multicast, you need to
use Join before using Gather.
● If you want to combine messages that are split using Splitter, you use only Gather.
If your incoming payload contains namespace declarations including default namespace, ensure that you
specify xpath with namespace prefixes. Also ensure that the namespace prefix mapping is defined in the
runtime configuration. If the xpath you have defined does not exist in any of the branches of the incoming XML,
the scenario fails with an exception.
Consider the following XML:
 Sample Code
<root xmlns="http:defaultnamespace.com">
<f:table xmlns:f="http://www.w3schools.com/furniture">
<f:name>African Coffee Table</f:name>
<f:width>80</f:width>
<f:length>120</f:length>
</f:table>
<table>
<name>African Coffee Table</name>
<width>80</width>
<length>120</length>
</table>
</root>

f and d are the prefixes defined in the Namespace Mapping field of Runtime Configuration and mapped to the
namespaces http://www.w3schools.com/furniture and http:defaultnamespace.com respectively. Examples
of valid xpaths for the above XML are:
● //f:table
● /d:root/f:table
● /d:root/d:table
Procedure
You use this procedure to combine messages using Gather in an integration process.
1. Open the integration flow in Model Configuration editor.
2. In the palette of the Model Configuration editor, choose Message Routing.
3. To add Join, drag from the palette to the integration process.
4. Connect all the messages that you want to merge to the element.
5. To add Gather, drag from the palette to the integration process.

6. In the Properties tab page, select value in Incoming Format field based on description in table.
Value Description
XML (Same Format) If messages from different routes are of the same format
XML (Different Format) If messages from different routes are of the different for
mat
Plain Text If messages from different routes are of the plain text for
mat
7. Select value for Aggregation Algorithm field based on description given in table.

Aggregation Algo
Incoming Format rithm Description Additional Fields Description
XML (Same Format) Combine Combine the incoming NA NA

messages without any
conditions. The mes
sages are combined in
Multimapping format.
 Note
In case you are us
ing the mapping
step to map the
output of this
strategy you can
have the source
XSD in the LHS
and specify the
Occurrence as
0..Unbounded.
Combine at XPath Combine the incoming Combine from Source XPath of the node that
messages at the speci (XPath) you are using as refer
fied XPath ence in the source
message to retrieve
the information.
Combine at Target Path to node which

(Path) would act as the root
for combined message
XML (Different For Combine Combine the incoming NA NA

mat) messages without any
conditions in multi
mapping format.
 Note
In case you are us
ing the mapping
step to map the
output of this
strategy you can
add the XSD’s
from the different
multicast
branches one after
another in LHS.
The sequence of
the messages is
important and so
this strategy
makes sense only
with the sequential
multicast.

Aggregation Algo
Incoming Format rithm Description Additional Fields Description
Plain Text Concatenate Concatenate the infor NA NA

mation from the differ-
ent sources one after
another
8. Save changes.
This flow element does not work directly with Router. It is recommended to model the flow using Local
Integration Process.
2.5.7 Defining Security Elements
Message-level security features allow you to digitally encrypt/decrypt or sign/verify a message (or both). The
following standards and algorithms are supported.
Context
Ensuring security is important, during message exchange, to preserve the integrity of messages. A sender
participant uses signatures to ensure authenticity of the sender, and encryption to prevent non-repudiation of
messages during the message exchange.
Procedure
Related Information
Signing the Message Content with PKCS#7/CMS Signer [page 319]

Signing the Message Content with an XML Digital Signature [page 321]
Verifying the PKCS#7/CMS Signature [page 336]
Verifying the XML Digital Signature [page 338]
Encrypting and Signing the Message Content with PKCS#7/CMS [page 343]
Encrypting and Signing the Message Content with OpenPGP [page 346]
Decrypting and Verifying the Message Content with OpenPGP [page 348]
Signing the Message Content with Simple Signer [page 318]

2.5.7.1 Signing the Message Content with Simple Signer
Simple Signer makes it easy to sign messages to ensure authenticity and data integrity when sending a
message to participants on the cloud.
Context
You work with the Simple Signer to make the identity of the sender known to the receiver(s) and thus ensure
the authenticity of the messages. This task guarantees the identity of the sender by signing the messages with
a private key using a signature algorithm.
In the integration flow model, you configure the Simple Signer by providing a private key alias. The signer uses
the alias name to get the private key of type DSA or RSA from the keystore. You also specify the signature
algorithm for the key type, which is a combination of digest and encryption algorithms, for example,
SHA512/RSA or SHA/DSA. The Simple Signer uses the algorithm to generate the corresponding signature.
Procedure
1. In the Model Configuration editor, select the Signer element and, from the context menu, select the Switch
to Simple Signer option.
2. To configure the signer with a saved configuration that is available as a template, choose Load Element
Template from the context menu of the Signer element.
3. On the Simple Signer tab page, enter the parameters to create a signature for the incoming message.
Option Description
Name Enter a name for the signer. It must consist of alphanumeric ASCII characters or underscores and
start with a letter. The minimum length is 3, the maximum length is 30.
Private Key Alias Enter an alias to select the private key from the keystore.
You can also specify that the alias is read dynamically from a message header; for example, if you
specify ${header.abc} then the alias value is read from the header with the name "abc“.
Signature Select a signature algorithm for the RSA or DSA private key type.
Algorithm
Signature Header Enter the name of the message header where the signature value in Base64 format is stored.
Name

5. To save the configuration of the signer as a template, choose Save as Template from the context menu of
the Signer element.
 Note
When you save the configuration of the Signer element as a template, the tool stores the template in
the workspace as <ElementTemplate>.fst.

2.5.7.2 Signing the Message Content with PKCS#7/CMS
Signer
Context
You work with the PKCS#7/CMS signer to make your identity known to the participants and thus ensure the
authenticity of the messages you are sending on the cloud. This task guarantees your identity by signing the
messages with one or more private keys using a signature algorithm.
Working with PKCS#7/CMS Signer
In the integration flow model, you configure the PKCS#7/CMS signer by providing one or more private key
aliases. The signer uses the alias name to get the private keys of type DSA or RSA from the keystore. You also
specify the signature algorithm for each key type, which is a combination of digest and encryption algorithms,
for example, SHA512/RSA or SHA/DSA. The PKCS#7/CMS signer uses the algorithm to generate
corresponding signatures. The data generated by the signer is known as the Signed Data.
Procedure
2. Right-click a connection within the pool and choose Add Security Element Message Signer .
3. In the Model Configuration editor, select the Signer element.
 Note
By default, the Signer is of type PKCS#7/CMS. If you want to work with XML Digital Signature or Simple
Signature, choose the relevant option from the context menu.
5. In the Properties view, enter the details to sign the incoming message with one or more signatures.
Parameters and Values of PKCS#7/CMS Signer
Name Name for the signer step
Block Size (in bytes) Enter the size of the data that is to be encoded.
If you enter a value equal to or less than 0, the whole data

is encoded.

Include Content in Signed Data You can choose to include the original content that is to be
signed in the SignedData element. This SignedData ele
ment is written to the message body. Otherwise, you can
choose to include the signed data in the
SapCmsSignedData header and only keep the original
content in the message body.
Encode Signed Data with Base64 You can also Base64-encode the signed data in either the
message body or the message header, to further protect it
during message exchange.
 Note
When you Base64-encode the signed data, you en
code either the message header or body, depending
on where the signed data is placed. When verifying
the message, make sure you specify which part of the
message (header or body) was Base64-encoded.
Signer Parameters For each private key alias, define the following parameters:
○ Private Key Alias

Enter an alias for selecting a private key from the key
store. You can enter ${header.headername} or
${property.propertyname} to read the name
dynamically from a header or exchange property.
○ Signature Algorithm
Specify the signature (digest) algorithm.
○ Include Certificates
If you activate this option (value true), the certifi-
cate chain corresponding to the private key will be
added to the SignedData element.
○ Include Signing Time
If you activate this option (value true), the signing
time for the signed attributes will be added to the
SignedData element.

7. To save the configurations of the signer as a template, choose Save as Template from the context menu of
the Signer element.
 Note

2.5.7.3 Signing the Message Content with an XML Digital
Signature
You sign with an XML digital signature to ensure authenticity and data integrity while sending an XML resource
to the participants on the cloud.
Context
Procedure
to XML Digital Signer option.
3. On the XML Digital Signer tab page, enter the parameters to create an XML digital signature for the
incoming message.
Private Key Alias Enter an alias for selecting a private key from keystore.
You can also enter ${header.headername} or ${prop
erty.propertyname} to read the name dynamically from a
header or exchange property.
Signature Algorithm Signature algorithm for the RSA or DSA private key type
Using the private key, the sender encrypts the digest.
Digest Algorithm Digest algorithm that is used to calculate a digest from the
canonicalized XML document
Note that if the digest algorithm is not specified, the digest

algorithm of the signature algorithm is used by default.

Signature Type ○ Enveloping XML Signature

The input message body is signed and embedded in
the signature. This means that the message body is
wrapped by the Object element, where Object is
a child element of the Signature element.
○ Enveloped XML Signature
The digital signature is embedded in the XML mes
sage to be signed. This means that the XML message
contains the Signature element as one of its child
elements.
○ Detached XML Signature
The digital signature is a sibling of the signed ele
ment. There can be several XML signatures in one
XML document.
XML Schema file path (only if the option Detached XML Choose Browse and select the file path to the XML
Signatures is selected) schema file that is used to validate the incoming XML
document. This file has to be in the package
source.main.resources.xsd
Signatures for Elements (only if the option Detached XML Choose Add to enter the XPath to the attribute of type ID,
Signatures is selected) in order to identify the element to be signed. Example: /
nsx:Document/SubDocument/@Id
Namespaces prefixes must be defined in the namespaces

mapping of the runtime configuration.
Parent Node (only if the option Enveloped XML Signature is Specify how the parent element of the Signature element
selected for the attribute Signature Type) is to be specified. You have the following options:
○ Specified by Name and Namespace (using local name

and namespace)
○ Specified by XPath expression (using an XML Path
Language (XPath))
Parent Node Name (only if the option Enveloped XML A local name of the parent element of the Signature ele
Signature is selected for the attribute Signature Type and ment
Specified by Name and Namespace is selected for Parent
This attribute is only relevant for Enveloped XML Signa
Node)
ture case. The Signature element is added at the end of
the children of the parent.
Parent Node Namespace (only if the option Enveloped Namespace of the parent element of the Signature ele
XML Signature is selected for the attribute Signature Type ment
and Specified by Name and Namespace is selected for
Parent Node)
ture case. In the Enveloped XML Signature case, a null
value is also allowed to support no namespaces. An empty
value is not allowed.

XPath Expression (only if the option Enveloped XML Enter an XPath expression for the parent node to be speci
Signature is selected for the attribute Signature Type and fied.
Specified by XPath expression is selected for Parent Node)
ture case.
Key Info Content Specifies which signing key information will be included in
the KeyInfo element of the XML signature. You can select a
combination of the following attribute values:
○ X.509 Certificate Chain

X509Certificate elements representing the certificate
chain of the signer key
 Note
The KeyInfo element might not contain the whole
certificate chain, but only the certificate chain
that is assigned to the key pair entry.
○ X.509 Certificate
X509Certificate element containing the X.509 certifi-
cate of the signer key
○ Issuer Distinguished Name and Serial Number
X509IssuerSerial element containing the issuer dis
tinguished name and the serial number of the X.509
certificate of the signer key
○ Key Value
Key Value element containing the modulus and expo
nent of the public key
 Note
You can use any combination of these four attrib
ute values.
Sign Key Info With this attribute you can specify a reference to the Key
Info element.
For more information about the various attributes, see the following:
http://www.w3.org/TR/xmldsig-core/
4. On the Advanced tab page, under Transformation, specify the following parameters.
Canonicalization Method for SignedInfo Specify the canonicalization method to be used to trans
form the SignedInfo element that contains the digest
(from the canonicalized XML document).

Transform Method for Payload Specify the transform method to be used to transform the
inbound message body before it is signed.
○ CamelXmlSignatureTransformMethods
 Example
 Sample Code
Example of this use case: The XML signature verifier of the receiving system expects an XML
signature as shown in the following code snippet.
The signature is a detached signature, because the signature element is a sibling of the signed
element B. However, the receiving system requires the enveloped-signature transform method to
be specified in the Transforms list. To ensure this, you have to configure a detached signature in the
XML Signer step, then add a Content Modifier step before the XML Signer step, where you specify
the header "CamelXmlSignatureTransformMethods" with the constant value “http://www.w3.org/
2000/09/xmldsig#enveloped-signature,http://www.w3.org/TR/2001/REC-xml-c14n-20010315".

<root>
<B ID="IDforB">
...
</B>
Id="_6bf13099-0568-4d76-8649-faf5dcb313c0">
<ds:SignedInfo>
...
<ds:Transforms>
<ds:Transform Algorithm="http://
www.w3.org/TR/2001/REC-xml-c14n-20010315" />
</ds:Transforms>
...
</ds:Reference>
</ds:SignedInfo>
</ds:Signature>
<root>
For more information about the various methods, see the following:
http://www.w3.org/2000/09/xmldsig#enveloped-signature,http://www.w3.org/TR/2001/REC-xml-
c14n-20010315
http://www.w3.org/2000/09/xmldsig#enveloped-signature
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments

http://www.w3.org/2001/10/xml-exc-c14n#
http://www.w3.org/2001/10/xml-exc-c14n#WithComments
5. On the Advanced tab page, under XML Document Parameters, specify the following parameters.
Reference Type Enter the value of the type attribute of the content refer
ence.
If you enter null or empty, no reference type is created.
More information: http://www.w3.org/2000/09/

xmldsig#Object
Namespace Prefix Enter a prefix for the XML signature namespace.
Default value is ds.
Signature Id Specifies the value of the Id attribute of the Signature ele

ment.
If you specify no value, no Id attribute is added to the Sig

nature element.
Output Encoding Select an encoding scheme for the output XML document.
The encoded output document will be written into the

message header. If no encoding scheme is specified, the
output will be UTF-8-encoded.
Exclude XML Declaration Specify whether the XML declaration header shall be
omitted in the output XML message.
Disallow DOCTYPE Declaration Specify whether DTD DOCTYPE declarations shall be dis
allowed in the incoming XML message.

7. To save the configurations of the signer as a template, choose Save as Template from the context menu of
the Signer element.
 Note
Related Information
XML Digital Signature [page 326]

2.5.7.3.1 XML Digital Signature
The following types of XML digital signatures are supported:
● Enveloping XML Signature: The input message body is signed and embedded within the signature. This
means that the message body is wrapped by the Object element, where Object is a child element of the
Signature element.
 Example
A template of the enveloping signature is shown below and describes the structure supported by XML
signature implementation. ("?" denotes zero or one occurrence; the brackets [] denote variables whose
values can vary.)
<Signature>
<SignedInfo>
<CanonicalizationMethod>
<SignatureMethod>
<Reference URI="#[generated object_id]"
type="[optional_type_value]">
<Transform Algorithm="canonicalization method">
<DigestMethod>
<DigestValue>
</Reference>
(<Reference URI="#[generated keyinfo_id]">
<Transform Algorithm="http://www.w3.org/TR/2001/REC-xml-
c14n-20010315"/>
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfo Id="[generated keyinfo_id]">)?
<--!The Id attribute is only added if there exists a reference-->
<Object Id="[generated object_id]"/>
</Signature>
● Enveloped XML Signature: The digital signature is embedded in the XML message to be signed. This
means that the XML message contains the Signature element as one of its child elements. The Signature
element contains information such as:
○ Algorithms to be used to obtain the digest value
○ Reference with empty URI, which means the entire XML resource
○ Optional reference to the KeyInfo element (attribute Also Sign Key Info)
 Example
A template of the enveloped signature is shown below and describes the structure supported by XML
values can vary):
<[parent element]>
...
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference URI="" type="[optional_type_value]">

<Transform Algorithm="http://www.w3.org/2000/09/
xmldsig#enveloped-signature"/>
<Transform Algorithm=[canonicalization method]/>
<DigestMethod>
<DigestValue>
</Reference>
(<Reference URI="#[generated keyinfo_Id]">
c14n-20010315"/>
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
</Signature>
</[parent element]>
● Detached XML Signature: The digital signature is a sibling of the signed element. There can be several
XML signatures in one XML document.
You can sign several elements of the message body. The elements to be signed must have an attribute of
type ID. The ID type of the attribute must be defined in the XML schema that is specified during the
configuration.
Additionally, you specify a list of XPath expressions pointing to attributes of type ID. These attributes
determine the elements to be signed. For each element, a signature is created as a sibling of the element.
The elements are signed with the same private key. Elements with a higher hierarchy level are signed first.
This can result in nested signatures.
 Example
A template of the detached signature is shown below and describes the structure supported by XML
values can vary):
 Sample Code
(<[signed element] Id="[id_value]">


...
</[signed element]>
<other sibling/>* 
<Signature>

<SignedInfo>
<SignatureMethod>
<Reference URI="#[id_value]" type="[optional_type_value]">

<DigestMethod>
<DigestValue>
</Reference>
(<Reference URI="#[generated_keyinfo_Id]">
c14n-20010315"/>
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>

<SignatureValue>
(<KeyInfo Id="[generated_keyinfo_id]">)?

</Signature>)+
Note that the following elements are generated and cannot be configured with the Integration Designer:
● Key Info ID
● Object ID
The sender canonicalizes the XML resource to be signed, based on the specified transform algorithm. Using a
digest algorithm on the canonicalized XML resource, a digest value is obtained. This digest value is included
within the 'Reference' element of the 'SignedInfo' block. Then, a digest algorithm, as specified in the signature
algorithm, is used on the canonicalized SignedInfo. The obtained digest value is encrypted using the sender's
private key.
 Note
Canonicalization transforms the XML document to a standardized format, for example, canonicalization
removes white spaces within tags, uses particular character encoding, sorts namespace references and
eliminates redundant ones, removes XML and DOCTYPE declarations, and transforms relative URIs into
absolute URIs. The representation of the XML data is used to determine if two XML documents are
identical. Even a slight variation in white spaces results in a different digest for an XML document.
2.5.7.4 Signing the Message Content with XML Advanced

Electronic Signature
XML Advanced Electronic Signature (XAdES) allows you to create digital signatures based on XML Digital
Signature that include additional qualifying properties.
Context
The additional properties allow you to create signatures that are compliant with the European Directive (http://
eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2000:013:0012:0020:EN:PDF ).
XAdES is an industry standard based on XML Signature and issued by the European Telecommunications
Standards Institute (ETSI). It allows you to enhance the digital signature with additional data, for example,
timestamps to provide evidence that the signature key was valid at the time the signature was created.
The following XAdES forms are supported:

XAdES Forms
Form Allows you to ...
XAdES-BES (XAdES-BES (1) and XAdES- Create an electronic signature based on XML Digital Signature that includes ad
BES (2))
ditional properties to further qualify the signature.
(XAdES Basic Electronic Signature)
XAdES-EPES Create an electronic signature based on XML Digital Signature that unambigu
(XAdES Explicit Policy based Electronic ously refers to a signature policy agreed between signer and verifier. An elec
Signature) tronic signature built in this way enforces the usage of the signature policy for
signature validation and thus increases the security level of the usage of the digi
tal signature.
 Note
There are additional XAdES forms defined by the specification. SAP currently only supports XAdES-BES
and XAdES-EPES.
For more information, see http://uri.etsi.org/01903/v1.3.2/ts_101903v010302p.pdf .
Procedure
Related Information
Signing the Message Content with XAdES-BES (1) [page 330]

Signing the Message Content with XAdES-BES (2) [page 333]
Signing the Message Content with XAdES-EPES [page 334]
Message Headers [page 336]
Limitations [page 329]
2.5.7.4.1 Limitations
SAP currently only supports XAdES-BES and XAdES-EPES. There are a number of additional limitations.
● No support for the QualifyingPropertiesReference element (see section 6.3.2 of the XAdES
specification at http://uri.etsi.org/01903/v1.3.2/ts_101903v010302p.pdf ).
● No support for signature forms XAdES-T and XAdES-C.
● No support for the Transforms element contained in the SignaturePolicyId element contained in the
SignaturePolicyIdentifier element.

● No support of the CounterSignature element; this implies that there is no support for the
UnsignedProperties element.
● At most one DataObjectFormat element is supported.
More than one DataObjectFormat element does not make any sense in the use cases supported by the
Signer step, because only one signed data object is expected (the incoming message body to the XML
signer).
● At most one CommitmentTypeIndication element is supported.
More than one CommitmentTypeIndicationelement does not make any sense in the use cases
supported by the Signer step, because only one signed data object is expected (the incoming message
body to the XML signer).
● A CommitmentTypeIndication element always contains the AllSignedDataObjects element.
The ObjectReference element within a CommitmentTypeIndication element is not supported.
● No support of the AllDataObjectsTimeStamp element (it requires a time authority).
● No support of the IndividualDataObjectsTimeStamp element (it requires a time authority).
2.5.7.4.2 Signing the Message Content with XAdES-BES (1)
This option allows you to add timestamps (for the signing time), a reference to the signer's key certificate, and
other information that further qualifies the signature.
Context
Procedure
to XAdES-BES (1) option.
2. Add the signing time and the certificate to the signature.
Option Description
Time Select this option if you want to add the signing time to the signature.
This measure helps to provide evidence that the signature key was valid at the time the signa
ture was created.
Certificate Specify whether the certificate of the signing key is to be added to the signature.

○ None
Add no certificate.

Option Description
○ Certificate Only
Add digest value, issuer, and serial number of the signing certificate.
○ Certificate Chain
Add digest value, issuer, and serial number of the certificates of the certificate chain.
Digest Algorithm Specify a digest algorithm that is to be used to calculate a digest value from the certificate.
(only when either
Certificate This measure helps to control whether the certificate that is used to verify the message content
Only or corresponds to the one that has been used to sign the message content.
Certificate
Chain is selected SHA256 is proposed as the default.
for Certificate)
Certificate URI Specify a reference to the certificate.
If as Certificate you have selected Certificate Only, only one URI is allowed.
If as Certificate you have selected Certificate Chain, you can add for each certificate in
the certificate chain an URI. The URI must be added at the position where the corresponding
certificate in the chain is located. At the position 0 the signing certificate URI must be placed. If
for a certain certificate in the chain no URI is available, enter an empty string at the correspond
ing place in the URI list.
Adding the signer's key certificate and its digest value to the signed document makes sure that the signed
document contains an unambiguous reference to the signer's certificate.
3. Specify the signer role.

These properties allow you to specify the role of the signer in order to make clear the signer's position in
the company or organization. Doing this helps provide evidence to the verifier that the signer is empowered
by the organization to perform the signing task.
Option Description
Claimed Roles Specify the claimed roles of the signer.

(optional)
To specify a claimed role, choose Add and enter a text or an XML fragment with the root element
ClaimedRole.
Certified Roles Specify the roles of the signer which are certified by an attribute certificate.
(optional)
An attribute certificate associates the identifier of a certificate to some attributes of its owner, in this
case, to a role
The specified attribute certificates must be base-64 encoded.
To specify a certified role, choose Add and specify the following attributes:
○ Encoding
Select the encoding scheme.
An empty string indicates that the Encoding attribute is not specified. In this case, it is assumed
that the PKI data is ASN.1 data encoded in DER.
○ ID (optional)
4. Under Data Object Format, specify the format of the signed data.

Option Description
Description (optional) Provide an informal text to describe the format of the signed data.
MIME Type (optional) Specify the Internet Media Type (MIME type) that determines the data object format.
You need to enter the MIME type manually.
Example: text/xml
This information can help to parse the signed document correctly.
5. Specify the Identifier of the data object format.
Option Description
Name Specify an identifier to indicate the format of a signed data.
You can specify the identifier by one of the following options:

○ By means of a Uniform Resource Identifier (URI) (preferred option when deal
ing with XML documents)
In this case, the Name of the identifier consists of the identifying URI. In this
case, the property Qualifier must not be specified (empty string).
○ By means Object Identifier (OID) when using ASN.1 (Abstract Syntax Notation
One)
To support an OID, the content of Identifier consists of an OID, either encoded
as Uniform Resource Name (URN) or as Uniform Resource Identifier (URI). The
optional Qualifier attribute can be used to provide a hint about the applied en
coding (values OIDAsURN or OIDAsURI).
Qualifier (only relevant if an Further qualify how the identifier is defined in case Abstract Syntax Notation One
Identifier Name has been (ASN 1) is used.
specified)
You can select one of the following values:
○ empty string
○ OIDAsURI – uses Uniform Resource Name.
○ OIDAsURN – uses Uniform Resource Name.
Description (only relevant if an Provide a reference to further documentation of the identifier.
Identifier Name has been
specified)
Documentation Reference (only

relevant if an Identifier Name
has been specified)

2.5.7.4.3 Signing the Message Content with XAdES-BES (2)
This option allows you to add further contextual information to the signature, like, for example, the place where
the signature has been created, or the type of commitment assured by the signer when creating the signature.
Context
Procedure
to XAdES-BES (2) option.
2. Under Production Place enter information on the purported place where the signer claims to have
produced the signature (City, State/Province, Postal Code, and Country Name).
3. Specify the commitment to be undertaken by the signer (for example, proof of origin, proof of receipt,
proof of creation).
Option Description
Commitment Specify the commitment. You can select one of the following values:
○ Proof of origin
Indicates that the signer recognizes to have created, approved and sent the signed data ob
ject.
The URI for this commitment is: http://uri.etsi.org/01903/v1.2.2#ProofOfOrigin .
○ Proof of receipt
Indicates that signer recognizes to have received the content of the signed data object.
The URI for this commitment is: http://uri.etsi.org/01903/v1.2.2#ProofOfReceipt .
○ Proof of delivery
Indicates that the trusted service provider (TSP) providing that indication has delivered a
signed data object in a local store accessible to the recipient of the signed data object.
The URI for this commitment is: http://uri.etsi.org/01903/v1.2.2#ProofOfDelivery .
○ Proof of sender
Indicates that the entity providing that indication has sent the signed data object (but not
necessarily created it).
The URI for this commitment is: http://uri.etsi.org/01903/v1.2.2#ProofOfSender .
○ Proof of approval
Indicates that the signer has approved the content of the signed data object.
The URI for this commitment is: http://uri.etsi.org/01903/v1.2.2#ProofOfApproval .
○ Proof of creation
Indicates that the signer has created the signed data object (but not necessarily approved,
nor sent it).
The URI for this commitment is: http://uri.etsi.org/01903/v1.2.2#ProofOfCreation .

Option Description
Description Enter a free text description of the commitment.
Documentation Enter references (URIs) to one or more documents where the commitment is described.
Reference
Commitment Enter additional qualifying information on the commitment made by the signer.
Qualifier
Enter a text or an XML fragment with the root element CommitmentTypeQualifier.
Adding these properties helps to avoid legal disputes as the commitment undertaken by the signer can be
compared with the commitment made in the context of an applied signature policy.
4. Under XML Document Parameters, select the namespace of the XAdES version and enter a namespace
prefix.
2.5.7.4.4 Signing the Message Content with XAdES-EPES
This option allows you to create a digital signature based on XML Digital Signature that unambiguously refers
to a signature policy agreed between signer and verifier. An electronic signature created this way enforces the
usage of the signature policy for signature validation and thus increases the security level of the digital
signature.
Context
A signature policy is a set of rules for the creation and validation of a digital signature.
Procedure
to XAdES-EPES option.
2. Specify the properties of the signature.
Option Description
Signature Policy Specify whether a signature policy is to be added, and, if yes, in which form this should
be done.
○ None
○ Implied
The signature policy can be unambiguously derived from the semantics of the type
of data object(s) being signed, and some other information.
Using this option, the SignaturePolicyImplied element will be part of the signature.

Option Description
○ Explicit ID
The signature contains an identifier of a signature policy together with a hash value
of the signature policy that allows verification that the policy selected by the signer
is the one being used by the verifier.
Identifier (only if the value Specify an identifier that uniquely identifies a specific version of the signature policy.
Explicit ID has been
selected for Signature You can specify the identifier by one of the following options:
Policy) ○ By means of a Uniform Resource Identifier (URI) (preferred option when dealing
with XML documents)
In this case, the Name of the Identifier consists of the identifying URI. In this case,
the property Qualifier must not be specified (empty string).
○ By means of an Object Identifier when using ASN.1 (Abstract Syntax Notation One)
To support an OID, the content of Identifier consists of an OID, either encoded as a
Uniform Resource Name (URN) or as a Uniform Resource Identifier (URI). The op
tional Qualifier attribute can be used to provide information about the applied en
coding (values OIDAsURN or OIDAsURI).
Identifier Qualifier (only if Qualify how the identifier is defined in case Abstract Syntax Notation One (ASN 1) is
the value Explicit ID used.
has been selected for
Signature Policy) You can select one of the following values:
○ Empty string
○ OIDAsURI – uses Uniform Resource Name.
○ OIDAsURN – uses Uniform Resource Name.
Description (only if the Enter a description of the signature policy.
value Explicit ID has
been selected for
Signature Policy)
Documentation Reference Provide a reference to further documentation of the signature policy.

(only if the value
Explicit ID has been
selected for Signature
Policy)
Digest Algorithm (only if Specify the digest algorithm used to calculate the digest value of the signature policy
the value Explicit ID document.
has been selected for
Signature Policy) As default, SHA256 is used.
Digest Value (only if the Specify the digest value of the signature policy document (base 64-encoded).
value Explicit ID has
been selected for You can either enter the digest value manually or calculate it.
Signature Policy)
To calculate the digest value, you have the following options:
○ Calculate from Identifier
Calculates the digest value from the value of the Identifier provided above. Note that
the Identifier must be a valid URL and start with http:// or https://.
○ Browse to local File
Calculates the digest value from the content of a file.
Policy Qualifier (only if the Enter additional information qualifying the signature policy. To do this, enter text or an
value Explicit ID has XML fragment with the root element SigPolicyQualifier.
been selected for
Signature Policy)

2.5.7.4.5 Message Headers
For certain message headers you can define specific elements in the XAdES form.
● CamelXmlSignatureXAdESQualifyingPropertiesId
Specifies the Id attribute value of the QualifyingProperties element.
● CamelXmlSignatureXAdESSignedDataObjectPropertiesId
Specifies the Id attribute value of the SignedDataObjectProperties element.
● CamelXmlSignatureXAdESSignedSignaturePropertiesId
Specifies the Id attribute value of the SignedSignatureProperties element.
● CamelXmlSignatureXAdESDataObjectFormatEncoding
Specifies the value of the Encoding element of the DataObjectFormat element.
● CamelXmlSignatureXAdESNamespace
Overwrites the namespace parameter value.
● CamelXmlSignatureXAdESPrefix
Overwrites the prefix parameter value.
2.5.7.5 Verifying the PKCS#7/CMS Signature
You perform this task to ensure that the signed message received over the cloud is authentic.
Context
In the integration flow model, you configure the Verifier by providing information about the public key alias, and
whether the message header or body is Base64-encoded, depending on where the Signed Data is placed. For
example, consider the following two cases:
● If the Signed Data contains the original content, then in the Signature Verifier you provide the Signed Data
in the message body.
● If the Signed Data does not contain the original content, then in the Signature Verifier you provide the
Signed Data in the header SapCmsSignedData and the original content in the message body.
The Verifier uses the public key alias to obtain the public keys of type DSA or RSA that are used to decrypt the
message digest. In this way the authenticity of the participant who signed the message is verified. If the
verification is not successful, the Signature Verifier informs the user by raising an exception.
Under Public Key Alias you can enter one or multiple public key aliases for the Verifier.
 Note
In general, an alias is a reference to an entry in a keystore. A keystore can contain multiple public keys. You
can use a public key alias to refer to and select a specific public key from a keystore.
You can use this attribute to support the following use cases:
● Management of the certificate lifecycle. Certificates have a certain validity period. Using the Public Key
Alias attribute in the Verifier step, you can enter both an alias of an existing certificate (which will expire

within a certain time period) and an alias for a new certificate (which does not necessarily have to exist
already in the keystore). In this way, the Verifier is configured to verify messages signed by either the old or
the new certificate. As soon as the new certificate has been installed and imported into the keystore, the
Verifier refers to the new certificate. In this way, certificates can be renewed without any downtime.
● You can use different aliases to support different signing senders with the same Verifier step. Using the
Public Key Alias attribute, you can specify a list of signing senders.
 Note
Exceptions that occur during runtime are displayed in the Message Processing Log view of the Operations
Integration perspective.
Procedure
2. Right-click a connection within the pool and choose Add Security Element Signature Verifier .
3. In the Model Configuration editor, select Verifier.
 Note
By default, the Verifier is of type PKCS#7/CMS. If you want to work with XML Signature Verifier, then
choose the Switch to XML Signature Verifier option from the context menu.
4. In the Properties view, enter the details to verify the signatures of the incoming message.
Parameters and Values of PKCS#7/CMS Signature Verifier
Name Name for the Verifier step
Header is Base64 Encoded Select this option to verify if the Signed Data encoded in
Base64 is included in the header
Body is Base64 Encoded Select this option to verify if the Signed Data encoded in
Base64 is included in the message body
Public Key Alias Enter an alias name to select a public key and correspond
ing certificate from the keystore

2.5.7.6 Verifying the XML Digital Signature
Context
The XML Signature Verifier validates the XML signature contained in the incoming message body and returns
the content which was signed in the outgoing message body.
 Note
For enveloping and enveloped XML signatures the incoming message body must contain only one XML
signature.
The Verifier supports enveloping and enveloped XML signatures and detached XML signatures. In the
enveloping XML signature case, one reference whose URI references the only allowed 'Object' element via ID,
and an optional reference to the optional KeyInfo element via ID is supported
Working of XML Signature Verifier
In the validation process, a public key is required and it is fetched from the worker node keystore. On receiving
the XML message, the Verifier canonicalizes the data identified by the 'Reference' element and then digests it
to give a digest value. The digest value is compared against the digest value available under the 'Reference'
element of the incoming message. This helps to ensure that the target elements were not tampered with.
Then, the digest value of the canonicalized 'SignedInfo' is calculated. The resulting bytes are verified with the
signature on the 'SignedInfo' element, using the sender's public key. If both the signature on the 'SignedInfo'
element and each of the 'Reference' digest values verify correctly, then the XML signature is valid.
 Note
XML Signature Verifier supports both enveloping and enveloped signatures
Procedure
1. In the Model Configuration editor, select Verifier element and from the context menu, select Switch to XML
Signature Verifier option.
2. In the XML Signature Verifier tab page, enter the parameters to verify XML digital signature for the
incoming message.
Parameters and Values of XML Signature Verifier

Expected Signature Type Select the expected Signature type:
○ Enveloping or Enveloped XML Signature: If the sig

nature is contained within the content or the signa
ture contains the signed data.
Verifying Enveloping Signature: If the incoming
message has enveloping signature
○ an optional 'Reference' to the optional 'KeyInfo'
element via ID is supported
○ 'References' can have one optional transform
whose algorithm must be a canonicalization
method
So it implies, an enveloping XML signature with only
the following structure is supported ("?" denotes zero
or one occurrence, the brackets [] denotes variables
whose values can vary).
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference
URI="#[object_id]">
(<Transform
Algorithm=[canonicalization
method]/>)?
<DigestMethod>
<DigestValue>
</Reference>
(<Reference
URI="#[keyinfo_id]">
(<Transform
method]/>)?
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfo
(Id="[keyinfo_id]")?>)?
<Object Id="[object_id]"/>
</Signature>
Verifying Enveloped Signature: If the incoming mes

sage has enveloped signature
○ One reference with empty URI and an optional
reference to the KeyInfo element via its ID is al
lowed
○ An additional transform containing a canonicali
zation method is supported, beside the trans

form with algorithm "http://www.w3.org/

2000/09/xmldsig#enveloped-signature".
So it implies, an enveloped XML signature with only
<[parent]>
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference URI="">
<Transform
Algorithm="http://www.w3.org/
2000/09/xmldsig#enveloped-
signature"/>
(<Transform
Algorithm="[canonicalization
method]"/>)?
<DigestMethod>
<DigestValue>
</Reference>
(<Reference
(<Transform
method]"/>)?
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfo
</Signature>
</[parent]>
○ Detached XML Signatures: If the signature is con

tained within the content or the signature contains
the signed data.
Verifying Detached Signature If the incoming mes
sage has detached signature:
○ Signature element must be a sibling of the
signed element
○ Signed element must have an attribute of type ID
○ Signature references signed element via the ID
value
So it implies, a detached XML signature with only the
following structure is supported ("?" denotes zero or

one occurrence, the brackets [] denotes variables

(<[signed element]
Id="[id_value]">

...
</[signed element]>
<other sibling/>* 
<Signature>
<SignedInfo>
<SignatureMethod>
<ReferenceURI="#[id_value]"type="
[optional_type_value]">

<TransformAlgorithm=[canonicaliza
tion method]/>
<DigestMethod>
<DigestValue>
</Reference>
(<ReferenceURI="#[generated_keyin
fo_Id]">
<TransformAlgorithm="http://
www.w3.org/TR/2001/REC-xml-
c14n-20010315" />
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfoId="[generated_keyinfo_i
d]">)?
<Signature>)+

Check for Key Info Element Select this option to check that the XML Signature con
tains a Key Info element
The KeyInfo element has to contain either the certificate

chain, the certificate, the Issuer Distinguished Name and
Serial Number, or the Key Value element (or combinations
of these attributes).
 Note
In case multiple public key aliases are specified (using
the Public Key Alias attribute), this option is manda
tory (to make sure that from the KeyInfo the public
key can be derived).
Disallow DOCTYPE Declaration Select this option to disallow DTD DOCTYPE declaration in
the incoming XML message

ing certificate
Using the Public Key Alias, you can enter one or multiple
public key aliases for the Verifier.
 Note
In general, an alias is a reference to an entry in a key
store. A keystore can contain multiple public keys. You
can use a public key alias to refer to and select a spe
cific public key from a keystore.
You can use this attribute to support the following use

cases:
○ Management of the certificate lifecycle: Certificates

have a certain validity period. Using the Public Key
Alias attribute in the Verifier step, you can enter both
an alias of an existing certificate (which will expire
within a certain time period) and an alias for a new
certificate (which not necessarily has to exist already
in the keystore). That way, the Verifier is configured to
verify messages signed by either the old or the new
certificate. As soon as the new certificate has been in
stalled and imported into the keystore, the Verifier re
fers to the new certificate. That way, certificates can
be renewed without any downtime.
○ You can use different aliases to support different sign
ing senders with the same Verifier step. Using the
Public Key Alias attribute, you can specify a list sign
ing senders.
2.5.7.7 Encrypting and Signing the Message Content with

PKCS#7/CMS
Context
You perform this task to protect the message content from being altered while it is being sent to other
participants on the cloud, by encrypting the content. In the integration flow model, you configure the Encryptor
by providing information on the public key alias, content encryption algorithm, and secret key length. The

encryptor uses one or more receiver public key aliases to find the public key in the keystore. The encryption
process uses a symmetric key of specified length for content encryption. The symmetric key is encrypted by
the public recipient key with the cipher. The encryption is determined by the type of Content Encryption
Algorithm that you select. The encrypted content and the receiver information containing the symmetric
encryption key are placed in the message body.
In addition to encrypting the message content, you can also sign the content to make your identity known to
the participants and thus ensure the authenticity of the messages you are sending. This task guarantees your
identity by signing the messages with one or more private keys using a signature algorithm.
Procedure
2. Right-click a connection within the pool and choose Add Security Element Content Encryptor .
3. In the Model Configuration editor, select Encryptor.
4. To configure the encryptor with a saved configuration that is available as a template, choose Load Element
Template from the context menu of the Encryptor element.
5. In the Properties view, specify the general settings for encryption.
Name Enter a name for the signer. It must consist of alphanu

meric ASCII characters or underscores and start with a
letter. The minimum length is 3, the maximum length is
30.

is encoded.
Encode Body with Base64 Select this option if the message body will be base64-en
coded.
Signatures Select one of the following options:
○ Enveloped Data Only

Select this option if you want to apply encryption
only.
○ Signed and Enveloped Data
Select this option if you want to apply both encryp
tion and signing.
6. Specify the settings for the encryption process (under Encryption).
Content Encryption Algorithm Specify the algorithm that is to be used to encrypt the
payload.

Secret Key Length Specify the key length.
The offered key lengths depend on the chosen encryption

algorithm.
Receiver Public Key Alias Specify one or more aliases.
Enter an alias to select the public key from the keystore.

You can enter ${header.headername} or $
{property.propertyname} to read the name dy
namically from a header or exchange property.
7. Specify the settings for the signing process under Signature (only if you selected Signed and Enveloped
Data for Signatures in PKCS7 Message).
For each private key alias (specified under Signer Parameters), you define the following parameters:

added to the SignedAndEnvelopedData element.

9. To save the configuration of the encryptor as a template, choose Save as Template from the context menu
of the Encryptor element.
 Note
When you save the configuration of the Encryptor element as a template, the tool stores the template
in the workspace as <ElementTemplateName>.fst.

2.5.7.8 Encrypting and Signing the Message Content with
OpenPGP
You have the option to encrypt the message content using Open Pretty Good Privacy (OpenPGP).
Context
You have the following options to protect communication at message level based on the OpenPGP standard:
● You can encrypt a payload.

● You can sign and encrypt a payload.
Procedure
2. Right-click a connection within the pool and choose Add Security Element Content Encryptor .
3. In the Model Configuration editor, position the cursor on the Content Encryptor step and in the context
menu select Switch to PGP.
5. Specify whether or not to sign the payload (in addition to applying payload encryption). To do this, select
one of the following options for Signatures in PGP Message:
Option Description
Include Signature Select this option if you want to apply both encryption and signing.
No Signature Select this option if you want to apply encryption only.
6. Under Encryption, specify the following parameters for message encryption:
Field Description
Content Encryption Algorithm In the dropdown list, select the algorithm you want to use
to encrypt the payload.
Secret Key Length Enter the secret key length.
 Note
The length of the secret key depends on the encryp
tion algorithm that you choose.
Compression Algorithm Select the algorithm you want to use to compress the pay
load.

Field Description
Armored Select if you want the output to be radix 64 (base64) en

coded with additional header.
Integrity protected Data Packet Select if you want to create an Encrypted Integrity Pro
tected Data Packet. This is a specific format where an ad
ditional hash value is calculated (using SHA-1 algorithm)
and added to the message.
This increases the message security level.
Encryption User ID of Key(s) from Public Keyring You can specify the encryption key user IDs (or parts of
them). Based on this, system look for the public key in
PGP public keyring.
You can specify multiple user IDs.
7. Under Signature, specify the following parameters for message signing (only if you have selected Include
Signature for Signatures in PGP Message):
Option Description
Digest Algorithm Specify the digest algorithm (or hash algorithm) that is to be applied.
The sender calculates a digest (or hash value) from the message content using a digest algo
rithm. To finalize the payload signing step, this digest is encrypted by the sender using a private
key.
Signer Key User ID Specify the signer key user ID parts.

Parts of Keys from
the Secret Keyring Based on the signer key user ID parts, the private key (for message signing) is looked up in the
PGP secret keyring.
Next Steps
You can provide a file name with the PGP message in the Literal Packet, according to the specification at
https://tools.ietf.org/html/rfc4880 , chapter 5.9 Literal Data Packet (Tag 11).
By default, this file name is set to an empty string.
A file name that differs from an empty string can be specified by the header CamelFileName.
 Note
The SFTP adapter sets the header CamelFileName automatically.

2.5.7.9 Decrypting and Verifying the Message Content with
OpenPGP
You have the option to decrypt the message content using Open Pretty Good Privacy (OpenPGP).
Context
Procedure
2. Right-click on a connection within the pool and choose Add Security Element Content Decryptor .
3. In the Model Configuration editor, position the cursor on the Content Decryptor step and in the context
menu select Switch to PGP.
5. Specify the following parameters for message decryption:.
Option Description
Name Name of the selected PGP Decryptor element. The default name is PGP Decryptor.
If you add a second PGP Decryptor to the integration flow, you have to change the name because the
Decryptor name must be unique.
Signatures Specify the expected payload content type which is to be decrypted. You have the following options:
in PGP Mes ○ No Signatures Expected
sage When you select this option, the decryptor expects an inbound message that doesn't contain a sig
nature.
 Note
If you select this option, inbound messages that contain a signature cannot be processed.
○ Signatures Optional
When you select this option, the decryptor can process messages that either contain a signature
or not.
○ Signatures Required
When you select this option, the decryptor expects an inbound message that contains a signature.
Signer User Specify the signer user ID of key(s) parts of all expected senders.
ID of Key(s)
from the Based on the signer user ID of key(s) parts, the public key (for message verification) is looked up in the
Public Key PGP public keyring.
ring
The signer user ID of key(s) key parts specified in this step restrict the list of expected senders and, in
this way, act as an authorization check.

2.5.8 Defining Events
Context
Procedure
2.5.8.1 Configuring an End Message Event
An End Message event ends a message processing sequence.
Context
This is how using an End Message event has an impact on the message status (shown in the message
processing log).
 Note
To catch any exceptions thrown in the integration process and handle them, you can use an Exception
Subprocess.
If an exception occurs during the processing sequence which has been handled in an Exception Subprocess,
the message status displayed in the message processing log is Failed.
When there is no error during exception handling, the message status displayed in the message processing log
is Completed.
If you like to configure your integration flow that way that the message status displayed in the message
processing log is Failed (even in case an exception occurs during the processing sequence which has been
handled successfully in an Exception Subprocess), you have the following options:
● Use an Error End event.

● Use an Escalation End event (sets message status to Escalated in that case).

Procedure
2.5.8.2 Configuring Timer Start
You can configure an integration flow to automatically start and run on a particular schedule.
Context
If you want to configure a process to automatically start and run on a particular schedule, you can use this
procedure to set the date and time on which the process should run once or repetitively. The day and time
combinations allow you to configure the schedule the process requires. For example, you can set the trigger
just once on a specific date or repetitively on that date, or you can periodically trigger the timer every day,
specific days in a week or specific days in a month along with the options of specific or repetitive time.
A Timer Start event and a Start Message event (sender channel) must not be modelled in the same integration
flow. This would result in an error ERROR: Multiple 'Start Events' not allowed within an
Integration Process pool.
 Note
When you use timer with Run Once option enabled, the message is triggered only when the integration flow
is deployed. If you want to trigger the message with an integration flow that you have already deployed, you
have to Undeploy the integration flow and Deploy it again. If you restart the integration flow bundle,
message will not be triggered.
When you delploy or undeploy an integration flow with Timer-Scheduler, the system automatically releases
all the scheduler locks.
 Note
You cannot externalize the timer element in older integration flows. If you want to externalize the timer in
existing integration flows, reconfigure the timer and save the integration flow. Extract parameters for the
timer properties to appear in Externalized Parameters tab page.
When you deploy small integration flows with Timer Start (for example, an integration flow with timer,
content modifier and mail adapter), due to extremely fast processing times, multiple schedules are
triggered.
Procedure

2. From the Palette, expand the Event category.
3. Select the Timer Start notation and drop it within the Integration Process pool wherever required.
4. From the speed button of the Timer Start, select the sequence flow and connect to the following element
within the Integration Process pool of the integration flow.
5. Select the Timer Start and in the Properties view, provide values in fields based on description in table.
Parameters & Values of Timer

Field Description
Run once Runs a data polling process immediately after deploying

the project
On Date Specific date on which the data polling process has to be

initiated to fetch data from the SuccessFactors system
Daily Run message polling every day to fetch data from the Suc
cessFactors system
Weekly Run the message polling every week on specified days of

the week to fetch data from the SuccessFactors system.
Monthly on Day Execute the message polling every month on the specified
date to fetch data from the SuccessFactors server.
 Note
If the specified date is not applicable to a month, the
data polling is not executed in that specific month. For
example, if 30th day is selected in the month of Febru
ary, polling is not executed as 30th is not a valid day
for February.
Time The time at which the data polling cycle has to be initiated.
For example, if you want the data polling to be started at
4.1PM, enter 16:10. Note that the time must be entered in
24-hour format.
Every xx minutes between HH hours and HH hours The connector fetches data from the SuccessFactors sys
tem, every ‘xx’ minutes between HH hours and HH hours.
 Note
If you want the polling to run for the entire day, enter 1
and 59.
Time Zone Select the Time Zone that you want to use as reference for
scheduling the data polling cycle.

2.5.8.3 Configuring an Escalation Event
An escalation event stops message processing. For synchronous messages, an error messages is sent to the
sender.
Context
A retry or any other error handling mechanism is not triggered. The message status changes to ESCALATED.
In certain situations it does not make sense to retry the message processing until it finally gets delivered to the
receiver. For example, in case a wrong receiver is configured in the integration flow, it does not make any sense
to retry the processing of the message without having corrected the integration flow configuration. In that case,
it makes more sense to stop message processing and notify the sender that an error occurred.
Procedure

2. From the Palette, expand the Event category.
3. Select the Escalation notation and drop it within the Integration Process pool at the position where the
escalation should be placed.
4. Specify the Escalation Category (in the Properties view).
There are the following Escalation Categories:
Escalation Event Routing condition has not been met.
Receiver not reachable Receiver could not be reached, because it is temporarily

down or not accessible (for example, due to overload or
maintenance work).
Receiver not found Receiver could not be found because the URL points to a
non-existent resource (for example, HTTP 404 error).
Not authenticated to invoke receiver Receiver could not be called because authentication has
failed (for example, HTTP 401 error).
Not authorized to invoke receiver Receiver could not be called because of insufficient per
missions (for example, HTTP 403 error).
Receiver tries to redirect Receiver could not be reached (HTTP 302 error).
Internal server error in receiver Internal server error occurred in the receiver system (for
example, HTTP 500 error).

Others – not further qualified Escalation category has not been further qualified.
2.5.9 Defining Tasks
Context
Procedure
2.5.9.1 Defining Service Call
Prerequisites
You have added the service call element to the integration flow model from the palette.
Context
Service Call is used to call an external system. Such calls enable transaction of data from or to the target
system. It can be used for following types of operations:
1. Request-Reply
2. Content Enrichment
2.5.9.1.1 Defining Request-Reply
Context
You can use this task to enable request and reply interactions between sender and receiver systems.

Example:
Suppose a currency conversion is required for a transaction between Indian and German business partners. In
such a scenario, using the Request Reply pattern, a user can successfully convert Indian currency to German
currency and vice versa. As shown in the integration flow, the request mapping converts the currency in the
payload to Euro and reply mapping converts the currency in the payload back to Indian Rupee.
Procedure

2. If you want to add a Request-Reply element in the integration flow, choose Add Service Call from the
context menu of a connection within the pool.
3. From the Palette, select Others Receiver , and drop it outside the Integration Process pool.
4. From the speed button of the Request-Reply element, create a connection that represents a channel from
the Request-Reply element to the Receiver.
5. Configure the channel with the required adapter details.
6. You can add integration flow elements between the Request-Reply and End Message element, for
processing response payload from Receiver system.
7. You can also connect End Message element back to the sender. Also, ensure that no adapter is configured
for this channel (as highlighted in the integration flow screenshot).
 Note
In this release, the channel connecting the external system with the Request-Reply element can be
configured with the SOAP, SuccessFactors, HTTP and IDOC adapters.

2.5.9.1.2 Defining Content Enricher
Prerequisites
You have created an integration project and integration flow.
Context
The content enricher adds the content of a payload with the original message in the course of an integration
process. This converts the two separate messages into a single enhanced payload. This feature enables you to
make external calls during the course of an integration process to obtain additional data, if any.
Consider the first message in the integration flow as the original message and the message obtained by making
an external call during the integration process as the lookup message. You can choose between two strategies
to enrich these two payloads as a single message:
● Combine
● Enrich
Consider the following original and lookup messages.
Original Message
<EmployeeList>
<Employee>
<id>111</id>
<name>Santosh</name>
<external_id>ext_111</external_id>
</Employee>
<Employee>
<id>22</id>
<name>Geeta</name>
</Employee>
</EmployeeList>
Lookup Message
<EmergencyContacts>
<contact>
<c_id>1</c_id>
<c_code>ext_111</c_code>
<isEmergency>0</isEmergency>
<phone>9999</phone>
<street>1st street</street>
<city>Gulbarga</city>
</contact>
<contact>
<c_id>2</c_id>
<phone>1010</phone>
<street>23rd Cross</street>

<city>Chitapur</city>
</contact>
<contact>
<c_id>3</c_id>
<phone>007</phone>
<street></street>
<city>Raichur</city>
</contact>
</EmergencyContacts>
If you use Combine as the aggregation strategy, the enriched message appears in the following format.
Enriched Message
<multimap:messages xmlns:multimap=”http://sap.com/xi/XI/SplitAndMerge”>
<message1>
<EmployeeList>
<Employee>
<id>111</id>
</Employee>
<Employee>
<id>22</id>
<name>Geeta</name>
</Employee>
</EmployeeList>
</message1>
<message2>
<EmergencyContacts>
<contact>
<c_id>1</c_id>
<phone>9999</phone>
</contact>
<contact>
<c_id>2</c_id>
<phone>1010</phone>
</contact>
<contact>
<c_id>3</c_id>
<phone>007</phone>
<street></street>
</contact>
</message2>
</multimap:messages xmlns:multimap=”http://sap.com/xi/XI/SplitAndMerge”>
Enrich offers you control on how you can merge the original and lookup message. In this example, we consider
the node <ext_111> as the reference to enrich the original message with the lookup message.
Consequently, you specify the following values while configuring the Content Enricher.

Section Field User input
Original Message Path to Node Employees/Employee
Key Element location
Lookup Message Path to Node EmployeeLocations\emplocation
Key Element locationid
The enriched message will be in the following format.
<EmployeeList>
<Employee>
<id>111</id>
<contact>
<c_id>1</c_id>
<phone>9999</phone>
</contact>
<contact>
<c_id>2</c_id>
<phone>1010</phone>
</contact>
</Employee>
<Employee>
<id>22</id>
<name>Geeta</name>
</Employee>
</EmployeeList>
In the enriched message, you can see the content of the lookup message after the node <location>.
 Remember
If lookup message contains more than one entry of the key element, content enricher enhances the
enriched message with all the entries referred by the key element in lookup message. In the above example,
the lookup message contains the key element ext_111 in two places. You can see that the enriched
message contains both the <contact> entries that the key element refers to.
Procedure
You use this procedure to add Content Enricher element to an integration flow.
1. Open the integration flow in Model Configuration editor.
2. From the context menu of integration flow, choose Add Tasks Service Call .
3. From the context menu of the service call element, choose Switch to Content Enricher.

4. In the Properties view, choose the Aggregation Strategy field.
5. Perform the required subprocedure below based on the strategy you want to use.
Using Combine Strategy
Procedure
You use this subprocedure for using the Combine strategy.

1. In the dropdown list, choose Combine.
2. Save changes.
Using Enrich Strategy
Procedure
You use this subprocedure for using the Enrich strategy.

1. In the dropdown list, choose Enrich.
Section Field Description
Original Message Path to Node Path to the node in the original mes
sage where content has to be en
riched. Ensure that you provide it in
the format <xx>/<yy>/<zz> with
<xx> being the root node and <zz>
being the node where new content will
reside
Key Element Key element in the original message

contained in the Path to Node speci
fied above. Ensure that you provide
only the key element name.
Lookup Message Path to Node Path to the node that would be used in
the lookup message to enrich the con
tent. Ensure that you provide it in the
format <xx>/<yy>/<zz> with <xx>
being the root node and <zz> being
the reference node
Key Element Key element in the lookup message

contained in the Path to Node speci
fied above. Ensure that you provide
only the key element name.

2.5.9.1.3 Defining a Send Step
You use the Send step type to configure a service call to a receiver system for scenarios and adapters where no
reply is expected.
Prerequisites
Context
You can use this step in combination with the following adapter types (for the channel between the send step
and the receiver):
● Mail adapter
● SFTP adapter
● SOAP (SAP RM) adapter
Procedure
2. From the context menu of the integration flow, choose Add Tasks Service Call .
3. From the context menu of the service call element, choose Switch to Send.
4. Create a connection between the send step and the receiver and configure the channel (use either an
SFTP, Mail adapter or a SOAP (SAP RM) adapter).
2.5.9.2 Defining a Process Call
You can invoke a local integration process from the main integration process by using a local call.
Related Information
Assigning a Local Integration Process [page 360]

Defining a Looping Process Call [page 360]

2.5.9.2.1 Assigning a Local Integration Process
Prerequisites
You have created a local integration process.
Context
Procedure
1. In the palette, choose Tasks Process Call and drop the shape into the modelling area.
2. Position the cursor on the Process Call shape and in the context menu choose Assign Local Integration
Process.
3. Enter the name of the local integration process you like to assign.
4. Choose Ok.
Related Information
Defining a Local Integration Process [page 364]
2.5.9.2.2 Defining a Looping Process Call
You can execute a local integration process in a loop.
Context

Procedure
1. In the palette, choose Tasks Process Call and drop the shape into the modelling area.
2. Position the cursor on the Process Call shape and in the context menu choose Assign Local Integration
Process.
3. Specify the following attributes.
Field Description
Expression Type Specify the kind of expression you want to enter in the
Condition Expression field.
○ XML
For XPath expressions, for example: //
customerName = ‘Smith’
○ Non-XML
For Camel Simple Expression Language
 Note
Examples:
${header.SenderId}, which indicates the

SenderId header field.
${in.body}, which indicates the body of the

incoming message.
For more information about Camel Simple Expression

Language, see: http://camel.apache.org/simple.html
.
Condition Enter the condition (XML or Non-XML, as specified by the

property Expression Type).
Do not use a mixed expression (containing both XML and

Non-XML expressions).
For more information about the usage of operators, see

Defining Router [page 272]
Max. Number of Iterations Maximum number of iterations that the loop can perform
before it stops (99999 iterations maximum).
You can use this setting to prevent a never-ending loop.
Example Scenario for the Local Loop Process.

 Note
The local loop process refers to a while loop. The sub process will run as long as the loop condition is
fulfilled.
To explain how a local loop process works, we provide a simple example.
Every morning, an account owner wants to check all transactions performed on his account. He calls a
specific web service and has defined this request:
<accountID>12345<accountID>
<action>Transaction_of_last_Day</action>
</accountinfo>
The appropriate response for this request is:
<accountinforesponse>
<transaction>
<id>1</id>
...
</transaction>
...
<transaction>
<id>55</id>
...
</transaction>
<hasMore>true</hasMore>
</accountinforesponse>
The account owner has to call the web service again and again until there are no more transactions
available and he gets the response:
<hasMore>false</hasMore>
To simplify the call, he can use the loop embedded in the HCP Integration Service. He needs to define a
while condition in the Xpath such as/accountinforesponse[hasMore = ‘true’].
As long as data are available, the call will continue. The sub-process inducing the loop uses the ServiceCall
step in the Request-Reply mode to call the web service. As soon as the web service gets the response
<hasMore>false</hasMore>, the processing exits the loop and continues with the next step. The last
response of the web service is the new payload, that will be taken as message body into the next step.

Related Information
Defining a Local Integration Process [page 364]
2.5.10 Defining Additional Elements (Others)
Context
Procedure

2.5.10.1 Defining a Local Integration Process
You can use this task if you want to simplify your integration process. It enables you to fragment your
integration process into smaller processes (local integration processes), which are in turn called from the main
integration process or from other local integration processes.
Context
 Note
For the main integration process the SAP icon is displayed in the top left corner, whereas for the local
integration processes this icon is not displayed.
 Restriction
You cannot use the following integration flow steps within the Local Integration Process step:
● Another Local Integration Process

● End Message
● Sender
● Receiver
● Aggregator
Procedure

2. Add a local integration process.
a. If you want to add a local integration process to the integration flow, choose Others Local
Integration Process from the palette. On the Properties tab, provide a name.
b. You can add various elements between the start event and end event of the process.
A local integration process does not support multicast and splitter elements.
3. Invoke the local integration process.
a. If you want to call the local integration process from the main integration process, add a process call in
the main integration process. To do this, choose Tasks Process Call from the palette.
b. Choose Assign Local Integration Process from the context menu of the process call within the pool.
Select the local integration process that needs to be assigned to the process call in the integration
flow.
 Note
You can use an Error End event to throw the exception to default exception handlers.

2.5.10.2 Defining Exception Subprocess
Context
You use this element to catch any exceptions thrown in the integration process and handle them.
 Restriction
You cannot use Exception Subprocess in a Multicast branch.
Procedure
2. To add an exception subprocess to the integration flow, choose Others Exception Subprocess from
the palette. The subprocess can be dropped into the integration process and should not be connected to
any of the elements of the integration flow.
3. Select the exception subprocess you have added to the integration flow model to configure it.
4. Start the process with Error Start event always.
5. End the process with either End Message or an Error End or Escalation End event.
 Note
○ You can use an End Message event to wrap the exception in a fault message and send it back to the
sender in the payload.
○ You can use an Error End event to throw the exception to default exception handlers.
6. You can also add other flow elements between the start and end events .
 Note
○ For example, you can choose Add Service Call from the context menu of a connection within the
pool. This enables you to call another system to handle the exception.
○ The following elements are not supported within an Exception Subprocess:
○ Another Exception Subprocess
○ Integration Process
○ Local Integration Process
○ Sender
○ Receiver
○ Start Message
○ Terminate Message
○ Timer Start
○ Start Event
○ End Event
○ Router

 Note
○ The message processing log will be in an error state even if a user catches an exception and
performs additional processing on it.
○ You can get more details on exception using ${exception.message} or $
{exception.stacktrace}.
○ You cannot catch exceptions of local integration process in the main integration process.
2.5.11 Defining the Error Configuration
You can define how to handle errors when message processing fails at runtime.
Context
Procedure
1. In the Model Configuration editor, click on the graphical area outside the integration flow model.
2. In the Properties view, select the Error Configuration tab.
3. Select one of the following options.
Error Configuration Parameters
Error Handler Strategy Select one of the following options:
○ None
When a message exchange could not be processed,
no error handling strategy is used.
○ Raise Exception
When a message exchange could not be processed,
an exception is raised back to the sender.
○ Raise Exception (Deprecated)
When a message exchange could not be processed
and there is IDoc or SOAP SAP RM channel in the in
tegration flow, then an exception is raised back to the
sender.

Return Exception to Sender When defining the error handling strategy for SOAP mes
sages, you can now define if in case of an exception the
SOAP fault exception is to be returned to the sender. If you
don’t select this option, an error message containing a
URL is sent back to the sender instead. You can use this
URL to access the message processing log.
2.5.12 Error Classification
At design time of an integration project, the way how a message is to be processed is specified by a number of
integration flow steps (for example, content modifier, encryptor or routing step). When an integration flow is
being processed at runtime, errors can occur at several individual steps within the process flow (referred to as
processing steps to differentiate them from the integration flow steps as modelled at design time).
Integration flow steps can specify message processing at different levels of complexity. Therefore, in general an
integration flow step (design time) can result in multiple processing steps steps at runtime.
Each processing step gets a unique Step ID which is displayed in the message processing log.
For example, a content modifier step in an integration flow can (at runtime) be related to multiple processing
steps: The content modifier step can be configured in a way that one processing step changes the message
header, one the message body, and another one an exchange property.
This content modifier will get three different Step IDs at runtime, for example: CallActivity_9, setBody4
and setProperty1.
To relate a modelled integration flow step (like the content modifier mentioned above) to an error occurring at
a certain processing step at runtime, you can use an identifier which is referred to as Model Step ID.
To allow an integration flow developer to relate to a certain integration flow step during error handling, the
runtime provides the Model Step ID of the integration flow step where the error occurred as Exchange Property
SAP_ErrorModelStepID. The content of the property can then be evaluated in the error handling.
 Note
You can use the property for instance in a condition definition of a Router step to choose a different error
handling strategy depending on the step where the error occurred.
Example for a routing condition : ${property.SAP_ErrorModelStepID} = ‘CallActivity_1’
When referring to an integration flow step for error handling, you need to know which Model Step ID has been
defined for an integration flow step. To display this attribute, position the cursor on the step and in the tooltip
you get the Model Step ID displayed as ID. To display this attribute for an adapter, position the cursor on the
connection shape in the integration flow model and in the context menu choose Technical Information.

2.5.13 Specifying Runtime Configuration
With the Runtime Configuration you can specify general properties of the integration flow.
Context
Procedure
1. In the Model Configuration editor page, select the graphical area outside the integration flow model.
2. In the Properties view, choose the Runtime Configuration tab.
3. Specify the following properties.

Runtime Configuration Properties
Property Allows you to ...
Namespace Mapping Map a prefix to a namespace at runtime.
Enter a namespace-prefix pair with a format

xmlns:<prefix>=<namespace>.
This parameter is required for elements such as the con

tent-based router, content modifier or content filter that
can use namespaces in their configuration. You can either
enter the namespace-prefix pair or the tool automatically
fills the namespace-prefix pair whenever a lookup is per
formed for the assigned WSDL.
You can also enter multiple namespace-prefixes as shown

in the example: xmlns:test=http://sapcd.com/
testABC;xmlns:test2=http://sapcd.com/
testPQR.
 Note
xmlns:ns0=https://
hcischemas.netweaver.neo.com/hciflow
Here, ns0 is the prefix and https://

is the namespace. That way, in a router, you can spec
ify the routing condition for an XML message as:
/ns0:HCIMessage/
SenderID='Sender01'
Message Processing Log Configure the log level to display in the Monitoring editor.
Select one of the log levels from the Message Processing

Log dropdown.
○ All Events: Allows all messages to be logged and dis

played
○ Error Events: Allows only error messages to be logged
and displayed
○ No Logging: Hides logging information

Allowed Header(s) Specify the headers to be retained when the incoming

message is processed.
Enter one or more names of headers by separating them

with pipe (|).
 Note
If you want to enter several headers with similar
names, use wildcards to make the entering faster.
The wildcards are regular expressions, such as .*

and ?.? substitutes exactly one non-space charac
ter..* substitutes zero or more non-space charac
ters.
Example: You want to enter the headers A, A1, A2, A3.
Instead of entering all of them singularly, simply enter

A .*. This will allow all headers starting with A.
In general, headers used by the runtime components are

retained and other headers are removed during message
processing. This field is useful when you need specific
header information along with the message body.
For inbound SSL connections (when a sender calls SAP

Cloud Platform Integration), senders have to authenticate
against a load balancer component. The load balancer
sets the following message header fields:
SSL_CLIENT_CERT (contains the Base64-encoded
sender client certificate) and SSL_CLIENT_USER. En
tering these values in the Allowed Header(s) field, allowes
you to forward these headers during message processing.

HTTP Session Handling Choose one of the following options:
○ None
Session handling is switched off
○ On Exchange
Each exchange corresponds to a single session (use
this option for stateful services)
○ On Integration Flow
Only one session will be used across the whole inte
gration flow (only use this option for stateless serv
ices)
 Note
Once an HTTP session has been initialized, there
is usually no further authentication for the dura
tion of the session (one of the advantages of us
ing sessions). This means that all further HTTP
requests on that server are processed in the con
text of the user that was logged on when the ses
sion was initialized. If, however, this behavior
does not meet your requirements (for example,
the user is dynamic and can change from request
to request), you can select either an exchange
session scope (if the user remains the same for
at least the processing of a single message) or no
session.
 Note
SuccessFactors (OData V4) and SuccessFactors
(REST) adapters do not support HTTP session
handling.
Related Information

Defining Content Filter [page 220]
Defining Content Modifier [page 211]

2.5.14 Defining Transaction Handling
You can configure transaction handling on integration process or local integration process level.
Context
Transactional processing means that the message (as defined by the steps contained in a process) is
processed within one transaction.
For example, consider a process with a Data Store Write operation. When transaction handling is activated, the
Data Store entry is only committed if the whole process is executed successfully. In an error case, the
transaction is rolled back and the Data Store entry is not written. When transaction handling is deactivated, the
Data Store entry is committed directly when the integration flow step is executed. In an error case, the Data
Store entry is nevertheless persisted (and not removed or rolled back).
Note the following limitations and recommendations related to transaction handling:
Integration Flow Contains the Following El

ements Recommendet Settings/Limitations
Aggregator steps Required for JDBC (mandatory)
 Caution
Choosing JDBC transaction handling is mandatory to ensure that ag
gregations are executed consistently.
Data Store operations Required for JDBC (recommended but not mandatory)
In case you choose Not Required, the related database operation is commit
Write
ted per single step and no end-to-end transaction handling is implemented.
JMS sender adapter Not Required
This applies also for scenarios that include In general, no transaction handling is required.
the AS2 adapter.
 Note
These adapters do not require JMS transaction handling. Their retry
handling works independent from the selected transaction handler.
JMS sender adapter together with JDBC re Required for JDBC
sources (Data Store, Aggregator, Write varia
bles)  Note
This applies also for scenarios that include However, note that it is not recommended to use transactional JMS re
the AS2 adapter. sources and JDBC resources in parallel.

JMS receiver adapter in a Send step Required for JMS (mandatory)
This setting is mandatory to ensure that the data is consistently updated in

the JMS queue.
Several JMS receiver adapter together with a Required for JMS (mandatory)
JMS sender adapter
the JMS queue.
One JMS receiver adapter (without Splitter or Not Required

sequential Multicast)
No JMS transaction handler is required.
 Note
Distributed transactions between JMS and JDBC resources are not
supported.
Several JMS receiver adapter or a sequential Required for JMS

Multicast or Splitter step followed by a JMS
receiver adapter
all JMS queues.
Note that aynchronous parallel processing of messages cannot be transactional.
For more details on parallel processing, check the documentation of General or Iterating Splitter and Parallel
Multicast.
Let us assume that you like to configure a message multicast and the integration flow also contains a Data
Store operations step. In this case, you can choose one of the following options to overcome the mentioned
limitation:
● Deactivate transactional processing.

● Use a Sequential Multicast instead of a Parallel Multicast.
Procedure
1. Depending on whether you like to configure transaction handling for an integration process or a local local
integration process, select the header of the corresponding shape in the integration flow modelling area.
2. Specify the details for transactional processing:
To configure transactional process for an Integration Process, select one of the following options for the
Transaction Handling property.

Transaction Handling for Integration Process
Required for JDBC You can specify that Java Database Connectivity (JDBC)
transactional database processing is applied (to ensure
that the process is accomplished within one transaction).
You can define a Transaction Timeout (in minutes). Maxi

mum value is 12 hours. Only specify timeouts longer than
1 hour in cases where this is absolutely necessary because
long running transactions might cause issues with the sys
tem database.
Required for JMS You can specify that Java Message Service (JMS) transac
tional database processing is applied (to ensure that the
process is accomplished within one transaction).

tem database.
Not Required No specific transactional processing is configured. The in

tegration process does not process transactions even if
(for example) data store operations are included.
To configure transactional process for a local Integration Process, select one of the following options for
the Transaction Handling property.
Transaction Handling for Local Integration Process
From Calling Process Transactional processing is inherited from the calling

process. The value defined for the calling process is used
as the timeout.
tional database processing is applied.

tem database.


tem database.
2.5.15 Externalizing Parameters of Integration Flow
Context
Externalizing parameters is useful when the integration content has to be used across multiple landscapes,
where the endpoints of the integration flow can vary in each landscape. This method helps you to declare a
parameter as a variable entity to allow you to customize the parameters on the sender and receiver side with a
change in landscape.
When you externalize a parameter, it will be available in the integration flow configuration when you import
content in SAP Cloud Platform Integration Web Application.
Partial Parameterization enables to change part of a field rather than the entire field. This variable entity of the
field is entered within curly braces.
List of parameters that can be externalized on the sender side
● SOAP (SAP RM) adapter: Address, URL to WSDL

● SOAP (SOAP 1.x) adapter: Address, URL to WSDL, WS Security, Private Key Alias for Response Signing,
Private Key Alias for Encrypting
● IDoc (IDoc-SOAP) adapter: Address, URL to WSDL
● SFTP adapter: Server Host , Server Path, File Name,User Name , Archive Directory
The following parameters under Processing Parameters: Post-Processing (all options that can be selected
in this drodown list), Idempotent Repository, Read Lock Strategy
● SuccessFactors Adapter: Address, Page Size Credential Name, Address Suffix, Parameters
● Sender Authorization: Subject DN and Issuer DN
List of parameters that can be externalized on the receiver side
● Mail Adapter: Address, Protection, Authentication, Credential Name, Mail Attributes (From, To, Cc, Bcc,
Subject, Mail Body)
● IDoc (IDoc SOAP)Adapter: Address, Proxy Type, URL to WSDL, Private Key Alias, Credential Name,
Authentication, Allow Chunking.
● SOAP (SAP RM) adapter: Address, Proxy Type, URL to WSDL, Private Key Alias, Allow Chunking.

● SOAP (SOAP 1.x) adapter: Address, Proxy Type, URL to WSDL, Authentication, Private Key Alias, Credential
Name, User Name Token, Private Key Alias for Signing, Private Key Alias for Encrypting, Allow Chunking.
● HTTP Adapter: Address, Query, Proxy Type, Authentication, Private Key Alias, Credential Name
● SFTP adapter: File Name,User Name , Archive Directory, Address
● SuccessFactors Adapter: Address, Page Size, Credential Name, Address Suffix, Parameters
● OData Adapter: Address, Proxy Type, Authentication, Custom Query Options, Page Size
● Twitter Adapter: Endpoint, User, Page Size, Number of Pages, Locations, Keywords, User Names,
Language, Consumer Key, Consumer Secret, Access Token, Access Token Secret.
 Note
If you externalize the Proxy Type parameter, you do not see the display values from the UI in the parameter
file, but the technical representatives of these values (for example, sapcc for the value On-Premise, and
default for the value Internet).
 Note
You can externalize all attributes related to the configuration of the authentication option. This includes the
attributes with which you specify the authentication option as such (if you either intend to use basic
authentication , certificate-based authentication or no authentication), as well as all attributes with which
you specify further security artifacts that are required for any configurable authentication option (Private
Apply one of the following two recommendations when externalizing such attributes.
● Externalize all attributes related to the configuration of all options (for example, Authentication Option,
Credential Name and Private Key Alias).
● Externalize only one of the following attributes: Private Key Alias or Credential Name.
Avoid incomplete externalization such that, for example, you externalize only the attribute for the
Authentication Option but not the related Credential Name. In such cases, the integration flow configuration
(based on the externalized parameters) cannot work properly.
The reason for this is the following: When you have externalized the Authentication Option attribute and
only the Private Key Alias (but no Credential Name), in the integration flow configuration dialog all
authentication options (Basic, Certificate-Based and None) are selectable in a drop-down list. However,
when you now select Basic Authentication from the drop-down list, no Credential Name can be configured.
Procedure
1. Externalize parameters by extraction.
 Note
You can extract certain parameters that are already configured in the integration flow, so that the
parameters are externalized. You can view the extracted parameters in the Externalized Parameter
view. If you have already extracted a parameter, the parameter cannot be extracted again.
a. From the Project Explorer view, open the <integration flow>.iflw in the editor.

b. In the Model Configuration editor, right-click the graphical area outside the model and choose Extract
Parameters from the context menu.
c. In the Extract Parameters dialog, select the parameters that have to be extracted and be available for
externalization.
 Note
In the Console view, you can see a summary of the parameter extraction.
d. Open the Externalized Parameters view.
 Note
You can view the externalized parameters of the field in the integration flow. The field is now
available as a variable.
e. From the toolbar of the view, choose (Sync with Editor icon) to synchronize the integration flow
that is currently open with the Externalized Parameters view.
f. You can edit parameter values and then choose (Save Parameters icon), from the toolbar of the
view.
 Note
The Save Parameters icon is enabled only if the parameter values and the type are consistent. For
drop down or combo box the values should be edited from here else, the parameter references are
lost.
g. Choose (Reload icon) to update the view with the list of externalized parameters.
h. If you have made modifications to the integration flow model and there are unused parameters then
you must choose (Remove Unused Parameters icon) to remove unused parameters.
2. Externalize parameters by manual configuration.
 Remember
You can use this method to externalize fields that allow text input.
Here's a list of attributes that you cannot externalize using manual configuration method:
○ Channel name
Example: If you are using SuccessFactors adapter, you cannot externalize the Name field in the
General tab.
○ Flow step name
Example: If you are using CSV to XML Converter, you cannot externalize the Name field in the
Properties tab.
○ Branch name in Multicast
Example: When you use Multicast, you can assign a name to each outgoing branch from the
Multicast step in the Branch Name field. You cannot externalize this Branch Name field.
○ Table Elements
Example: If you are configuring the Sender step, you cannot externalize the Subject DN or Issuer
DN fields when you are using certificate-based authentication.

 Note
You can use the step below if you want to externalize certain parameters in such a way that you do
provide any values in the integration flow but want to manually configure the attributes in the
Externalized Parameters view.
a. In the Project Explorer view, open the <integration flow>.iflw in the editor.
b. In the Model Configuration editor, double-click the channel or select the flow step field that you want to
externalize.
c. In the Properties view or the Adapter Specific tab for adapters, enter a value for the field that you want
to externalize in this format: {{<parameter_name>}}.
 Note
○ You can use alphanumeric characters, underscore and hyphen for parameter name.
○ You can externalize the value of the field so that the field is now a variable. For example, you
might need to change the 'Address' field of a connector at the receiver without making any
other changes to the integration flow. So, you enter {{server}} in the 'Address' field. The
steps below show how you can specify data for the externalized parameters.
Only part of the field can also be changed. For example, in the given URL, http://{{host}}:
{{port}}/FlightBookingScenario, host and port are the variable entities.
d. Save the changes in the channel editor.

e. Open the Externalized Parameters view.
f. From the toolbar of the view, choose Sync with Editor (icon) to synchronize the integration flow that is
currently open with the Externalized Parameters view.
 Note
In the Externalized Parameters view, you can see all the parameters that have been externalized in
the integration flow. For example, if you have externalized the 'Address' field of a connector as
{{server}} or you have selected this field for extraction, you can see the parameter under the
Name column.
g. Open the Externalized Parameters view and choose (Reload icon).
 Note
In the Externalized Parameters view, you can view all the parameters that have been externalized in
the integration flow. For example, if you have externalized the 'Address' field of a connector as
{{server}} or you have selected this field for extraction, you can see the parameter under the
Name.
h. From the toolbar of the Externalized Parameters view, choose (Save Parameters icon).
 Note
○ The Save Parameters icon in the Externalized Parameters view is enabled only if the parameter
values and the type are consistent.
○ If you do not save the view using the Save Parameters icon, the parameters.prop file is not
updated with the new externalized parameters, which is indicated with an error marker in the
Integration Flow editor. If the editor has no unsaved changes, the error marker remains even

though the parameter content is saved. In such a case, you can execute the consistency check
by using the Execute Checks context menu option in the Model Configuration editor.
2.5.15.1 Configuring Multiple Externalized Parameters
Prerequisites
You have enabled mass configuration of system properties.
 Note
Please refer to the below procedure steps for enabling mass configuration of system properties.
Context
You use this task when you want to provide the same values for the common parameterized attributes across
multiple integration projects. The tool offers quick parameterization with the Configurations view that displays
a list of externalized parameters from all the projects. If multiple integrations require same values for the
externalized parameters, you can choose the Mass Parameterize option to fill values for all the common
parameters.
Procedure
1. For receiver system, you must have a single participant for every logical system.
 Note
○ If all receivers are the same logical system then you can have one participant rather than multiple
participants in the integration flow to which all channels can be connected.
○ If the channel names are same or not added, then you must add unique channel names.
2. To externalize certificate information at the sender system, execute the following substeps:
a. In the Certificate Based Authentication table, enter the key names( {{sender}}, {{issuer}}).
b. In the Externalized Parameters view, enter the values.
 Note
Do not use Extract Parameters option directly.

3. To externalize private key alias and credential details at the receiver, execute the following substeps:
a. In the channel editor table, enter the key name ({{privatekeyalias}}).
b. In the Externalized Parameters view, enter the values.
c. Select Basic Authentication table.
d. In the channel editor table, enter the key name( {{credential}}).
e. In the Externalized Parameters view, enter the values.
 Note
Do not use Extract Parameters option directly.
4. To externalize system details for receiver address, execute the following substep:
a. In the Address field, enter the value in the format https://{{host}}:{{port}}/<appDetails>?
client={{client}} .
5. To externalize authentication modes at sender and receiver systems, execute the following substeps:
a. Extract all parameters relevant to sender authentication mode using the format
<sender>_enableBasicAuthentication_<randomnumber>.
b. Extract all parameters relevant to receiver channel authentication mode using the format
<receiver>_enableBasicAuthentication_<randomnumber>.
6. In the context menu, select Execute Checks.
7. To view and configure parameters, execute the following substeps:
a. In the main menu, choose Window Show View Others .

b. In the Show View dialog, choose Others Configurations .
c. In the Configurations view toolbar, choose (Mass Configure).

d. In the Mass Configuration wizard, select the projects that contain the common parameters and choose
Next.
e. Enter values for the list of parameters and choose Next. These values get applied to their
corresponding parameters that are common across the selected projects.
 Note
A common parameter that has been assigned different values, is indicated using the tag Parameter
has Different Values. If you delete this tag and enter a new value or keep it empty, the value of the
common parameter changes accordingly across all the projects that use it.
f. Confirm if you want to update the common parameters with the new values.
g. If you want to view or change externalized parameters in the integration flow from the Configurations
view, double-click any file under the Configurations view to open the Model Configuration editor and the
Externalized view.
h. If you want to deploy the projects, select Deploy Integration Content and enter the Tenant ID.
i. Choose Finish.
Results
The completion of this task triggers the build automatically and your projects get deployed with the updated
externalized parameters.

2.6 Working with the Mapping Editor
Context
Procedure
2.6.1 Creating a Message Mapping
Context
You perform this task to create a message mapping when the receiver system accepts a different message
format than that of the sender system. The message mapping defines the logic that maps input message
structures with the required format of output message structures.
You define a message mapping using the mapping editor by following the steps below:
Procedure
1. Create a mapping object under the package src.main.resources.mapping under the Project Explorer view.
2. Define the signature for message mapping by specifying the source and target elements under the
Signature section.
3. Define the mapping logic in the Definition tab page.

2.6.1.1 Multi-Mappings
A multi-mapping is a mapping that allows you to transform a source (input) message to multiple target
(output) messages or multiple source to multiple target messages.
Multi-mappings reference multiple message structures. You can, for example, use a multi-mapping to map a
message to multiple different (and generally smaller) messages. In that case, the cardinality of the mapping is
1:n.
In your mapping, always add the namespace http://sap.com/xi/XI/SplitAndMerge to the root tag.
For the format of a multi-mapping, see below:

<sm:Messages xmlns:sm="http://sap.com/xi/XI/SplitAndMerge">
<Message1>
...
</Message1>
<MessageN>
...
</MessageN>
</sm:Messages>
2.6.1.2 Creating a Mapping Object
Context
You perform this task to create a mapping object required for message mapping.
Procedure
1. In the Project Explorer, select the integration project.

2. Expand the integration project and select the src.main.resources. mapping package.
3. From the context menu, choose New Other... .
4. In the New wizard, select SAP NetWeaver Cloud Integration Message Mapping .
5. Choose Next.
6. In the New Message Mapping wizard, enter a name for the mapping.
7. Choose Finish.

Results
The new message mapping object is created under src.main.resources. mapping package and the Message
Mapping Overview editor opens.
2.6.1.3 Defining the Mapping Signature
Context
You perform this task to define the signature of a mapping object.
Procedure
1. In the Message Mapping Overview editor, under the Signature Source Elements section, Add a file.
 Note
○ If you have selected an XSD or WSDL file, you can also perform multi mapping by selecting another
source WSDL or XSD.
○ If you have selected an EDMX file as your first source element or you are choosing an edmx file as
your next source element then you will not be able to perform multi mapping. The new file will
overwrite the existing file and only a single file can be seen as source elements.
 Restriction
In the content used for mapping, if the XSD indicator maxOccurs value exceeds 65535, replace it with
unbounded. Otherwise, it will cause the tenant to crash.
2. If you are performing multi mapping then change the cardinality of mapping to the required cardinality.
The default cardinality for single mapping is 1:1.
3. Choose OK.
4. Under Target Elements section, repeat steps 1 to 3.

2.6.1.4 Defining the Mapping
Context
You perform this task to the define a mapping for the mapping object.
Procedure
1. In the Definition tab page editor, to map a source field to target field, drag a source node and drop onto a
target node in the tree structure.
 Note
○ Alternately, you right-click on the source field, drag and drop it onto the target node and select Map
automatically
○ If you have selected multiple messages under source or target elements, system creates a new
node Messages, which has all the other nodes under it.
.
2. If you want to perform any of the actions such as duplicating the subtree, disabling a field or adding a
variable, then from the context menu of the selected node, choose the required option.
When you need to map different node structures of the source message to only one node structure of the
target message you use the option of duplicating the subtrees.
3. If you want to map the child elements of a recursive node (if any), from the context menu choose the
option of Expand Recursive Node.
 Note
○ Recursive node acts as a design time placeholder to indicate creation of a node at this location at
runtime of the type indicated in the repeatedNode property.
○ In case you do not want to use the child elements or variable of the recursive node, then from the
context menu, choose the option of Collapse Recursive Node.
4. Double-click a node to view the graphical representation of mapping in the graphical editor.
 Note
If you want to perform mapping directly in the graphical editor, then drag the source and target nodes
from the tree structure into the graphical area.
5. In the graphical editor, connect the source and target node using connectors.
6. If you want to add a function to the connection between the source and target nodes, double-click on the
functions displayed under the Functions folder on the right-side of the graphical editor.
7. Connect the function to the required node with the use of connectors.

8. If you want to add parameters to a function, choose Properties from the context menu of the function.
 Note
○ You can also double-click on the function to add parameters

○ The functions, in which you can add parameters, are displayed with a wheel symbol
a. Add a value for the parameter.

b. Choose OK
9. If you want to find the hierarchy of the node in the tree structure, then from the context menu of the node
in graphical editor, choose Find Field.
10. If you want to change context of the node, then from the context menu, choose Context and select an
option.
11. If the resulting mapping layout in the graphical editor is not in order, from the toolbar of the Properties view,
choose (Organize Layout) to automatically arrange the layout.

12. Save the mapping.
 Note
To check the correctness of the mapping, you can right-click on the editor and choose Execute Checks,
if there are any errors, you get notified by a red error mark close to the field or in Problems view. Some
such errors are described below:
○ In case, there are any unassigned mandatory fields, an error is indicated by a red error mark appears
close to such fields in the Definition tab page.
○ If source or target messages are not assigned, an error message is displayed in the Problems view.
○ If any of the source or target messages are not available in required location, an error mark in red
appears on the element in the Overview tab page.
○ Also, if the mapping is not present in the folder src.main.resources.mapping then an error is shown in
the Problems view.
○ The above errors are also displayed once you have saved the mapping.
2.6.2 Handling Inconsistencies in Mapping Editor
Context
You use this task to handle the inconsistencies in the message structures or mappings that occur due to
modification of source or target elements.
Scenarios where such inconsistencies occur are:
● When you change an XSD or WSDL that are being used in existing mapping as source or target element
● When you change the source or target nodes in the message mapping tree structure

 Note
Whenever you open a mapping where any changes have been made to the source or target element,
the editor notifies you about the change.
Procedure
1. In the Definition tab page editor, choose the icon ( Check for consistencies between changed message
structures ).
2. In the Reload Confirmation dialog, choose OK to continue with correcting of structural inconsistencies.
 Note
This action discards any recent changes or additional mappings that you have done after changing the
source or target element.
3. In the Missing Fields wizard, you can choose to reassign or delete the inconsistent fields.
 Note
○ A red mark appears on the fields with inconsistencies.

○ If there are changes in both source and target structures, then in the Missing Fields wizard,
changes in source structure are displayed first and the follow on screen displays the changes in the
target structure.
4. If you want to reassign the missing fields, then follow the substeps below:
a. Right-click on the missing field in the old structure.
b. Drag the missing field from the old structure and drop it on the required field in the new structure.
c. If you want to map all the children fields related to the selected missing field in old structure with the
matching fields in the new structure, choose the option Map Automatically.
d. If you want to map only the single selected field, then choose Create mapping option.
 Note
○ Alternatively, you can simply drag the fields from old structure and drop onto the fields in the new
structure.
○ In case you have moved a disabled missing field, then the mapping also moves along with the field
but the new field is not marked as disabled.
○ In case you have moved a missing field with a variable defined under it, then the variable also
appears under the new field, and the mapping of the old variable is assigned to the new variable.
5. If you do not require the missing fields in your mapping, then select the missing field and choose the icon
(Delete Field) to mark for deletion.
 Note
If you want to use the field marked for deletion, then select the icon (Delete Field icon) again to cancel
the delete action.

6. Choose Next to check the missing fields of target structure.
7. Repeat the steps above to reassign or delete the missing fields of target structure.
8. Choose Finish.
Now the fields are reassigned and the fields marked for deletion are removed from the structure.
9. Save the mappings.
2.6.3 Exporting Mapping Details to Excel
Context
You use this procedure when you want to see the mapping details offline without signing into the Eclipse or
NWDS.
Procedure
1. Select the required mapping from the package main.resources.mapping .

2. From the context menu of the selected mapping, choose Export to Excel.
3. In the Save As dialog, select the location for saving the excel containing the mapping details.
4. Select Save.
 Note
○ If the mapping is exported to the selected location without any error, a dialog box with message
Export to excel is completed, is displayed.
○ If you are performing Export to Excel on the mapping for the second time, then it displays a dialog
to replace the earlier excel with the new excel.
○ If you trying to export a mapping, for which an excel is already created and in use by another user,
then the excel does not open and an error is displayed.
○ If any target node is disabled in the mapping, then the node is greyed out in excel and it displays
the value Disabled under the under the corresponding cell of column Type.
○ Similarly, if a node or field is recursive, it displays the value ...[Recursive] under the under the
corresponding cell of column Type.
○ Also, currently only .xlsx format of excel is supported.

2.7 Testing an Integration Flow
Context
Procedure
2.7.1 Checking the Consistency
Context
You can execute consistency checks to validate if the configurations of the integration flow elements are
adhering to their definition. This helps you validate the integration flow model and the configured attributes are
supported at runtime. The inconsistencies can occur if the integration flow model does not adhere to the
modeling constraints that SAP supports for specific scenarios. When you trigger consistency check execution,
the tool validates the consistency of your integration flow model against the predefined constraints set by the
SAP supported scenarios.
Procedure
1. Right-click on the project and choose Execute Checks.
 Tip
You can also click on the graphical model outside the Integration Process pool, and choose Execute
Checks from the context menu.
2. Open the Problems view for the consistency check results.

2.8 Operations-Related Tasks
Context
Procedure
2.8.1 Deploying an Integration Project
Prerequisites
You have obtained the details about the system management node from the SaaS Admin and entered in
Windows Preferences SAP Cloud Platform Integration Operations Server page.
You have ensured that the supported version of Eclipse IDE, Eclipse Juno (Classic 4.2.2), is installed on your
system to avoid deployment failure.
Context
You perform this task to trigger deployment of the integration project. The deployment action triggers the
project build and deployment on the Tenant Management Node (Secure).
Procedure
1. If you are deploying only one integration flow project, follow the steps below:
a. Right-click on the project and choose Deploy Integration Content from the context menu.

 Note
You can distinguish each deployment of the project bundle by adding a qualifier in the
MANIFEST.MF file. Open the MANIFEST.MF file of the project and enter the value for Bundle-
Version as <version>.qualifier. For example, 1.0.0.qualifier.
b. In the Integration Runtime dialog, enter the Tenant ID of the Tenant Management Node.
c. Choose OK.
2. Check the deployment status of the integration project in the runtime by following the steps below:
a. In the Node Explorer view, select the Tenant that is represented as <Tenant ID>.
b. Open the Tasks view and check if the 'Generate and Build' task is available.
c. In the Node Explorer, select the worker node type represented as IFLMAP and check for the
project bundle that is deployed in the Component Status view.
 Note
You can identify the project bundle by checking the Version column. If you have specified the
qualifier, the Version column displays the bundle version along with the timestamp.
2.8.2 Viewing Error Logs
Context
You use this procedure to view the errors of an integration content artifact for monitoring purposes.
Procedure
1. Launch SAP Cloud Platform Integration.
2. Choose Window Open Perspective Other .

3. In the Open Perspective dialog box, choose Integration Designer.
4. Choose OK.
5. In the Node Explorer pane, expand cluster <node name> TM:<VM Name> .
6. Choose the Component Status View tab.
7. In the context menu of an artifact in error state, select Show Error Details.

2.8.3 Activating Tracing
You activate tracing to check the message payload after each and every integration flow step.
Prerequisites
 Caution
Do not activate integration flow tracing for productive scenarios. This feature was designed for support use
cases and testing purposes. It can cause problems if used in productive scenarios, especially if you expect a
high message load.
● You have obtained the following roles to retrieve and view traces.
Roles
Operations Roles
View Message Trace IntegrationOperationServer.read
Export MPL IntegrationOperationServer.read
esbmessagestorage.read
NodeManager.read
● You have verified that the integration flow for which tracing is required is deployed.
Context
You use tracing to track the message flow of processed messages, view the relevant message payload at
various points in the message flow, and identify any errors that occur during message execution. Tracing
details are displayed in an integration flow as little yellow envelopes.
You can set the log level for an integration flow scenario in the Manage Integration Content page of the Web-
based Monitor.
Select your integration flow in the Manage Integration Content and set the log level for this integration flow in
the Log Configuration section.
Procedure
1. In Eclipse, in the Node Explorer, double-click the tenant management node to open the tenant editor. To
enable the trace in
2. On the Trace Configuration tab, select the integration flow.

3. Choose Enable.
 Note
On the Trace Configuration tab, under the Trace Status attribute, you can view the following statuses:
Enabled: The trace is enabled.
Disabled: The trace is disabled.
Expired: The trace has expired after being enabled (default duration of expiration time is 10 minutes).
Suspended: The SaaS administrator has switched off the trace temporarily for operational reasons.
4. Run the scenario.

5. In the Node Explorer, double-click the tenant management node to open the tenant editor.
6. On the Message Monitoring tab, select the message.
7. Choose View Trace.
 Note
○ Once you enable the trace, it is enabled for 10 minutes by default.

○ After message processing, the trace data is deleted after 60 minutes.
○ You must run a scenario again after making any configuration changes.
○ If you add a content modifier without a header, body, and property, you cannot trace the element.
○ Tracing is supported only if the total payload size across the entire integration flow is
approximately 50 MB.
○ When tracing is enabled, the message processing log will be written at the highest possible detail
level and the message content gets collected and stored. After expiry of trace during an execution
of an integration flow the collection of message content is stopped but the message processing log
will still be written on the most detailed level. For subsequent executions, the log level falls back to
the one which was set for the integration flow prior to trace.
2.8.3.1 View Trace
You use this task to display message trace for a particular integration flow.
In the Message Monitoring editor, for a completed or failed message, the Properties view displays the message
processing log (MPL) for this message. The MPL provides information on the steps during processing of a
particular message and the View MPL button opens the particular integration flow with the message trace,
displaying path of message flow. If the particular project does not exist in workspace then it automatically
imports project.
If the current project state is different from deployed state then tracing of message flow occurs till the point,
sequence of elements match.
View Trace imports trace content in project with name same as bundle id. If existing project name is not same
as that of bundle id, then view trace creates a new project in the workspace with same bundle-id.
Payload and header tabs appear in property sheet, on clicking the message icon in the message trace. If in any
case splitter is used, then there are multiple message payloads and the icon has multiple message symbols. In

such a scenario, the message heading is displayed between dashed lines and below the heading, payload
content appears. The same is shown below.
-------------------------
Message 1
------------------------
<ns0:BSNMessage xmlns:ns0="https://bsnschemas.netweaver.neo.com/bsnflow">
<SenderId>Token</SenderId>
<ReceiverId></ReceiverId>
<MessageType></MessageType>
<FileName></FileName>
<NumberOfRecords></NumberOfRecords>
<MessageId></MessageId>
<MessageContent></MessageContent>
</ns0:BSNMessage>
There are multiple sequences which traverse one path. The property sheet displays this information. For
example, “Displaying content for message 1 (out of 3)”. Here, ‘3’ denotes number of times the sequence
traverses a particular path. Clicking on the text enables user to switch to a different sequence.
In case of huge payload, the whole information is not visible. In such a scenario, we can use ‘Export Payload’
button to view content using external tool/application.
 Note
● You cannot trace a configure-only integration flow.

● You cannot view trace for multiple messages. Please select one message only.
2.8.3.2 Export MPL
Context
You enable this element to export and analyze a trace.
Procedure
Select a processed message in Message Monitoring editor. On clicking the same, Message Processing Log
dialog box opens. Select one of the following from the dialog box:
○ Export Log – Exports message flow sequence only

○ Export Log with Trace – Exports message flow sequence, message payload and headers at different trace
points
○ Export Log with Trace and Integration Project

 Note
○ You can export only message processing log for a configure-only integration flow.
○ You cannot export MPL for multiple messages. Please select one message only.
2.8.3.3 Import Trace
Context
You can import the content by using Import Trace. Import Trace imports content with trace only.
Procedure
1. Right click on the Project Explorer.

2. Select Import.
3. Select Message Processing Log Archive and click on Next.
4. In the dialog box, select the archived file where the content is saved.
5. The integration flow opens with the message trace.
2.9 References to Additional Help
Cheatsheet
Cheatsheets guide you in performing simple end-to-end use cases. Cheatsheets are very useful if you are
working with the tool for the first time and you want to understand the related steps to complete a task. It
shows you the flow of steps and has UI controls to automatically open the relevant UI elements, such as a
wizard or a view.
To open cheatsheets, follow the steps below:
1. From the main menu, choose Help Cheatsheets... .

2. In the Cheatsheet Selection dialog, expand SAP Cloud Platform Integration folder.
3. Select the most appropriate cheatsheet from the list and choose OK.

4. Follow the instructions mentioned in the cheatsheet.
Context-sensitive Help
Context -sensitive help provides more details about a specific view, wizard or page. It is useful when you want
more information about the parameters in the UI elements.
Select the UI element and press F1 .

3 Packaging Integration Content in SAP
Cloud Platform Integration Web
Application
SAP Cloud Platform Integration Web application allows you to assemble integration contents into packages
and publish them, so that integration developers can use these packages in their integration scenarios.
As an integration developer, you can now create integration packages for your specific domain or organization.
You can also view different packages published by other integration developers and consume them for your
integration purposes. You can modify these packages based on your requirements and upload them through
the web application.
3.1 Uploading Integration Packages
You use this procedure to upload and upload your existing integration packages that suits your integration
scenario in the application. This reduces redundancy and duplication efforts of creating a package from
scratch.
Context
Procedure
1. Launch the SAP Cloud Platform Integration Web application by accessing the URL provided by SAP.
2. Enter your credentials to log on to it.
3. Choose Upload in the Design tab to upload an integration package.
4. Browse and select the integration package for uploading.
5. Choose OK.
Uploaded file appears in the Design tab of the application.

396 PUBLIC Packaging Integration Content in SAP Cloud Platform Integration Web Application
3.2 Creating an Integration Package
You use this procedure to create an integration package that is specific to your integration scenario.
Procedure
1. Launch the SAP Cloud Platform Integration Web application by accessing the URL provided by SAP.
3. Choose the Design tab.
4. Choose Create.
5. In the <integration package name> editor page, enter the required data.
6. Perform the following substeps as required:
○ If you want to add an integration flow as an artifact, perform the following substeps:
1. Choose Add Process Integration in the Artifacts ( ) section.

2. Enter the required details in the Create Process Integration Artifact dialog box.
3. Choose Browse in the Integration Flow field to import an integration flow from your local system.
4. Choose the required file in the Open dialog box.
5. Choose Open.
6. Choose OK.
 Note
○ Create a zip file of the required integration flow in your project folder before importing it as an
artifact. The zip file must not contain any bin folder, and you must not keep the integration flow
in any sub folder.
You can also select Import to upload an integration flow from your local system.
○ If you want to add a mapping as an artifact, perform the following substeps:
1. Choose Add Value Mapping in the Artifacts ( ) section.

2. Enter the required details in the Create Value Mapping Artifact Artifact dialog box.
3. Choose Browse in the File Upload field to import a file from your local system.
4. Choose the required file in the Open dialog box.
5. Choose Open.
6. Choose OK.
 Note
Create a zip file of the required value mapping in your project folder before importing it as an
artifact.
○ If you want to add a data integration as an artifact, perform the following substeps:

Packaging Integration Content in SAP Cloud Platform Integration Web Application PUBLIC 397
1. Choose Add Data Integration in the Artifacts ( ) section..
2. Enter the required details in the Create Data Integration Artifact dialog box.
3. Choose OK.
○ If you want to add an OData service as an artifact, choose Add OData Service in the Artifacts
( ) section. For more information, see .

7. If you want to remove the integration package, choose Delete Package.
8. If you want to keep the integration package, choose Save.
9. If you want to terminate the creation of integration package, choose Cancel before saving it.
3.3 Working with an Integration Package
You use this procedure to perform various miscellaneous functions with the artifacts of an integration package.
Procedure
1. Launch the SAP Cloud Platform Integration application by accessing the URL provided by SAP.
3. Choose the Design tab to view the list of integration packages.
4. If you want to view the details of an integration package, choose <integration package name>.
5. Choose View metadata to view the metadata of the artifact.
6. Choose Deploy to deploy the artifact.

You can only deploy data flows, integration flows and value mappings. You can deploy multiple value
mappings at a time.
7. Choose Configure to configure the artifact.

You can configure only integration flows.
8. Choose Download to download an artifact.

You can only download integration flows, files, and value mappings. Your local file system stores the
downloaded artifact(s) with name as <artifact name>.zip file. If you want to use the artifact in Eclipse, you
need to import it in eclipse after extracting it from the zip file.

3.4 Editing an Integration Package
Procedure
1. Launch SAP Cloud Platform Integration Web application by accessing the URL provided by SAP.
2. If you are a new user, choose Signup.
3. If you have user credentials, choose Login.
5. Select the required integration package.
6. In the <integration package name> editor, choose Package Content.
7. Choose Edit.
8. If you want to edit integration content of type process integration, data integration, file, or value mapping,
choose
You get the following functions:
○ View metadata
○ Delete
○ Download
○ Configure (only for integration flows)
○ Deploy (only for data flows and integration flows)
9. If you want to edit artifact of type URL, choose .

You get the following functions:
○ View metadata
○ Delete
10. If you want to edit the metadata of an artifact, then perform the following substeps:
a. Choose View metadata.
b. In the <Artifact Name Details> dialog box, choose Edit.
 Note
The name of integration flow should begin with alphabets 'Aa' to 'Zz' or underscore '_' . It can also
contain numbers '0-9', space ' ', dot '.' and hyphen '-'.
c. Choose Save to keep the changes.

d. Choose Save as version to retain a copy of the current artifact.
You can view the version history of an artifact by choosing the current version mentioned along with it.
You can save versions of a single or multiple artifacts, or an integration package. You can also view the
list of existing versions of the required artifact(s) or integration package(s). You can choose to make an
existing version as the latest one with or without saving a draft of it.
e. Choose Cancel to revert the changes.
11. If you want to edit a specific integration package that is present in the Discover tab, then perform the
following substeps:
a. Choose the Discover tab.

b. Select the integration package.
c. Choose to copy it to the Design tab.

You can copy an integration package to the Design tab by opening the integration package in the Discover
tab and choosing Copy in the integration package editor. If the copy fails, then choose Create copy to
create a copy of the integration package or Overwrite to erase errors and register new information in the
integration package.
12. If you want to download multiple artifacts at once, then perform the following substeps:
a. Select the Artifacts checkbox.
b. From the list of artifacts, select the ones you want to download.
c. Choose Actions Download all .
13. If you want to keep the changes made to the integration package, choose Save.
14. If you want to discard the changes, choose Cancel before saving it.
3.5 Locking Integration Packages
You use this procedure to restrict multiple users from editing an integration package.
Context
Procedure
1. Launch SAP Cloud Platform Integration Web Application by accessing the URL provided by SAP.
3. Choose an integration package from the list.
4. Choose the Edit button.
When you choose Edit in an integration package editor, it locks the integration package and prevents any
other user from modifying it.
5. Choose Save after making the required changes.
○ Choosing Save, Cancel or Delete releases the integration package and allows it to be modified by other
users.
○ In case you close your browser without saving the integration package or there is a session timeout for
you, the integration package remains locked by you unless you edit and save, cancel or delete it.

3.6 Updating Integration Packages and their Contents
You use this procedure to update integration content to existing integration packages, which ensures that the
package is up-to-date with latest content. This also helps in bringing down your overall operational and
maintenance cost.
Context
Procedure
1. Launch SAP Cloud Platform Integration Web application.

2. In the Discover tab, select the integration package that you want to update.
4. Choose the integration package that you want to update.
5. Choose Publish.
The Publish Content dialog box appears.

6. Choose your update method:
1. If you want to update the content manually, choose Update manually option.
2. If you want to auto update the content in the next polling cycle, choose Publish updates immediately
option.
3. If you want to auto update the content on a specified date, perform the following steps:
1. Choose Publish updates on specified date option.
2. Select the specific date that you want to publish the updates.
 Note
If you want to publish the updates as a configure-only type of content, select the Publish as configure-
only content checkbox.
7. Choose Publish.
An auto-generated email template appears in Microsoft Outlook, with the message to the Content
Reviewer that upon successful review, the selected package needs to be published to the Internal/Public
Catalog.
8. Choose Send.

3.7 Exporting Integration Packages
You use this procedure to download your integration packages in your local system, so that you can provide it
to your content management team to upload and publish them. Publishing integration packages makes them
available to non-SAP integration developers.
Context
Procedure

2. Select the required integration package from the list.
3. 3. Choose Export.
The destination of export depends on the default browser setting. By default, the downloaded file takes the
name of the integration package. In case the name contains special characters, the browser changes the
file name by appending them.

4 Developing Integration Content With the
SAP Cloud Platform Integration Web
Application
The Web application helps you to access and design Cloud integration content available for a particular
account on an OnDemand integration infrastructure.
Use
The Web application provides you with an interface for accessing and managing integration content. You can
either directly use the prepackaged integration content from the catalog or upload it to your workspace to
adapt it to your requirements.
You can use the artifacts available in integration packages to solve the integration challenges of your scenario.
Optionally, you can also upload integration packages from your local folder and use them. You can use the
integration flows available in packages by configuring and deploying them. You can also edit the integration
flows by adding or removing elements, before you configure and deploy them.
The application consists of the following components which allow you to perform different tasks:
Components of the Web Application
Component Allows you to...
Discover View all available integration packages.
Which integration packages are available to you depends on

the permissions for the user (which has logged-in to the Web
application). You can view the description of integration
packages and copy integration packages to your customer
workspace (see Design tab below).
This component is also known as catalog.
Design Configure or model integration flows.
After completing this task, you can save the changes, save
as a version or deploy the integration flow.
This component is also known as customer workspace.

Developing Integration Content With the SAP Cloud Platform Integration Web
Application PUBLIC 403
Component Allows you to...
Monitor Monitor the message processing and manage integration ar

tifacts such as integration flows, value mappings and secur
ity-related artifacts.
You can check the status of messages and integration arti

facts for your tenant cluster.
You can also access the dedicated message monitor and in
tegration content monitor to view more information.
Settings Select the product profile to specify the target runtime for
your content.
Related Information

New and Improved Integration Flow Editor for SAP Cloud Platform Integration [page 485]
4.1 Understanding the Basic Concepts
This section provides an overview of the concepts of integration content design.
Related Information
Elements of an Integration Flow [page 404]

4.1.1 Elements of an Integration Flow
An integration flow allows you to specify how a message is processed on a tenant.
You can use integration flows to specify specific integration patterns like mapping or routing.
A graphical editor allows you, the integration developer, to model the message processing steps and specify in
detail what happens to the message during processing.
In detail, you define the following aspects in an integration flow:

404 PUBLIC Application
● The senders and receivers of the message
● How the senders and receivers are connected to the tenant (adapters)
● The steps that define the message processing
The following figure provides a simplified and generalized representation of an integration flow.
Senders and Receivers
You define a participant of an integration scenario as a sender or receiver. The senders and receivers typically
represent the customer systems that are connected to the tenant and exchange messages with each other.
Connectivity (Adapters)
An integration flow channel allows you to specify which technical protocols should be used to connect a sender
or a receiver to the tenant.
 Note
To specify an adapter, click the connection arrow between the sender/receiver and the Integration Process
box.
Message Processing (Steps)
You use integration flow steps to specify what should happen to a message during processing. Various step
types support the wide range of integration capabilities of the Cloud-based integration platform.
 Note
To insert a step into an integration flow, drag and drop the desired step type from the palette on the right of
the graphical modeling area.
Message Flows
You use message flows to connect various integration flow elements.

Related Information
Configure Adapter in Communication Channels [page 492]
4.1.2 Adapter and Integration Flow Step Versions
Some new features might not be available for your current integration flow due to the following reason:
A feature for a particular adapter or step was released after you created the corresponding shape in your
integration flow.
● You can continue using the older version of the integration flow shape (adapter or step).
● You can use the new integration flow shape (adapter or step).
To do this, you first have to delete the old flow step or channel and then create it again.
4.1.3 Versioning of Artifacts
SAP Cloud Platform Integration offers an easy version management capability for your integration artifacts.
After creating an artifact, when you choose on Save as Version, a new version of the artifact is created. You can
specify the version in the Version information dialog that appears after you choose Save as Version. You can
also add a comment there for your reference so that you have some additional information that indicates the
need for each version.
By default, you only see the latest version of the artifact in the integration package. However, the older versions
of the artifact are available for you in the backend. If you want to switch to a different version of that artifact,
you can easily do that by clicking on the version number and choosing the  (Revert) icon corresponding to the
version that you want to switch to.
 Example
You are currently using the version of the artifact, but you want to switch to version 1.1.8. You click on the
version number 1.2.0, and in the Version History dialog, you choose  (Revert) icon next to 1.1.8. You can
choose More to see comments about each version, if any.
 Remember
● The artifact version management is specific to the tenant that you are using it in. It will not work across
tenants. It is also not user specific.
● When you create an artifact, it is created with the version 1.0.0 by default.
● If you choose Save after editing an artifact, the artifact version will be Draft. Please note that you can
only see the latest Draft version.

● You must follow the versioning convention of <major>.<minor>.<micro> for artifact versions. For
example, you cannot specify the artifact version as 123 or abc.
4.1.4 Product Profiles
The Cloud Integration Web UI (also known as Content Hub) allows you to use Cloud integration content for
different target integration platforms. Accordingly, different product profiles are available to adapt the user
interface of the integration content designer to the specifications and capabilities of the target integration
platform.
A product profile defines a set of capabilities for Cloud integration content design supported by a specific
target integration platform. In particular, a specific product profile supports the configuration of a specific set
of adapter types and integration flow steps.
The following product profiles are available:
● SAP Cloud Platform Integration

Cloud-based integration runtime of SAP Cloud Platform Integration
● SAP Process Orchestration (for specific Process Orchestration release)
For example: SAP Process Orchestration 7.5, SP5
On premise integration runtime of SAP Process Integration (for the available release)
Prior to start working with Cloud integration content, you need to know on which target integration platform(s)
the Cloud integration content is to be deployed and executed.
If you encounter use cases where both on premise and Cloud-based integration platforms are involved, you
might like to have several options and, accordingly, both product profiles are of interest for you.
The following figure illustrates the use case for the product profiles SAP Cloud Platform Integration and SAP
Process Orchestration 7.5 SP0.
When you have decided on the product profiles in question, the process is as follows:
Based on your choice, you request an account and tenant at SAP.

As soon as the tenant is available, you connect to it using the Web application (using the Web UI URL provided
in the mail you received from SAP).
Under Settings, you choose the default product profile. When you create a new integration flow, this choice will
be applied by default.
The integration flow editor shows the options and executes checks based on the chosen product profile. The
reason for this is that the target integration platform imposes specific restrictions on the Cloud integration
content.
You have the option to configure a product profile also for an individual integration flow (under Runtime
Configuration).
Related Information
Set Default Product Profile for HCI Web Application [page 409]
Configure Product Profile for an Integration Flow [page 408]
4.1.4.1 Configure Product Profile for an Integration Flow
You can use product profile in an integration flow, to develop content for a particular runtime.
Prerequisites
● You have connected toSAP Cloud Platform Integration Web Tooling.

● Your user is assigned with integration developer role.
● You have opened an integration flow in the editor.
Context
The tool enables you to design for multiple runtimes at the same time. You should select specific product
profile to develop content for the respective runtime.
 Note
If a product profile does not support a particular capability then the checks report errors for unsupported
components in the integration flow.

Procedure
1. Choose Runtime Configuration tab page.

2. Select relevant product profile from the Product Profile dropdown list.
 Note
○ If you want to publish content in the catalog, then it is a recommendation to select a specific
product profile.
○ If you switch product profiles, then the system reloads the palette and displays relevant
capabilities.
3. Choose Save or Deploy as appropriate.
Related Information
4.1.4.2 Set Default Product Profile for HCI Web Application
The tenant administrator can view and configure the product profile, to mark one of them as default for the
tenant.
Prerequisites
● You have connected to SAP Cloud Platform Integration Web Tooling.

● You have assigned WebToolingSettingsProductProfiles.savetenantconfiguration role or
AuthGroup.Administrator group.
Context
The tool enables you to design for multiple runtimes at the same time. You should select specific product
profile to develop content for the respective runtime. You can execute the following steps to configure a
product profile for a tenant.

Procedure
1. Choose Settings tab page.
 Note
You can click on the product profile name under Name field to see the available capabilities for the
relevant profile.
2. Choose Edit in the Product Profiles tab page.

3. Select the radio button for the product profile you want to mark as default.
4. Choose Save or Cancel as appropriate.
 Note
You can also configure product profile at integration flow level. For more details please refer to Define
Product Profile [page 408].
Related Information

4.1.5 Restrictions
The Integration Designer allows you to model specific patterns which are handled at runtime in an unexpected
way.
Restrictions and Alternative Configuration Settings

Expected Behavior at Run
Modelled Pattern time Actual Behavior at Runtime Alternative Modeling Option
Integration flow step with The same message is proc The messages are delivered Configure only one outgoing
more than one outgoing se essed in parallel after the in to the different receivers in a sequence flow and parallel
quence flows tegration flow step. sequence. processing using a multicast
of messages.
For example, after a Message Hereby, the order in that the
Persistence step the mes messages are delivered is
sage is supposed to be sent randomly generated.
to multiple receivers in paral
In addition to that, the follow
lel.
ing behavior may occur: the
message which results from
the processing in the previ
ous sequence flow is taken
as input for the next se
quence flow.
 Note
As an example, consider
two parallel sequence
flows where the first one
contains an encryption
step and the second one
not. In that case, the re
ceiver of the second se
quence flow also gets an
encrypted message (al
though in the second se
quence flow no encryp
tion step has been con
figured).
Comment on Database Transactions

The following step types include transactional database processing.
If one of the below listed steps is contained in an integration flow, the processing of the message is executed in
one transaction.
● Data Store Operations step

○ Select (in case delete=true)
○ Write
○ Get (in case delete=true)
○ Delete
● Usage of Write variables

● Aggregator step
● Content Enricher
 Caution
Such steps might lead to resource shortages because long running transactions can cause node instability
and impede other processes that are running in transactions.
Some of the above mentioned steps or adapters persist data in the database. In case of an error, the whole
process is rolled back and the original state is being re-established. That means, data from failed processes
remain and, in case message processing fails, customers normally cannot access data about the failed
processing (due to the roll-back).
In case an error is propagated back to the calling component, all data that have been written in the course
of the (failed) transaction are being removed (in other words: not persisted in the database). For the calling
component, an error implies, therefore, to restart the integration flow.
Transactional processing is also to be considered in scenarios that contain asynchronous decoupling. Let’s
assume integration flow A contains a Data Store Operation step. Integration flow B contains a Select
operation on the Data Store and runs into an error. In that case, that data is preserved that has been written
to the database by integration flow A. This behavior makes sense in particular when you consider the case
that integration flow B changes or deletes the data that has been stored by integration flow A. In case
integration flow B fails, the original data from integration flow A can be retrieved.
4.2 Generating Integration Content using APIs
Use APIs to generate integration flows and access them using the SAP Cloud Platform Integration tenant.
Prerequisites
● You have logged-on to SAP Cloud Platform Integration.

● You have created an integration package.
Context
Based on specific end-to-end business integration requirement you can filter and choose prepackaged APIs
from the Discover page. These prepackaged APIs displayed here are from the SAP API Business Hub. Use them
to generate and deploy generic integration flow templates to accelerate your integration process. Prepackaged
API content contains different types of APIs, and each API contains a set of resources and operations. The
operations are available in the open API specification format.

Supported APIs and Operations
APIs Operations
OData GET, POST, and DELETE
REST GET, POST, PUT, and DELETE
 Example
Let us consume an API to create an integration flow. In the Discover page, select the All tab to search and
filter the relevant API. Here we use SAP Cloud Platform API package that contains an artifact for managing
the lifecycle of your application. Select the API that is of the type REST.
Before you generate an integration flow, it is recommended you understand the resources and its
operations. Choose Generate Integration Flow, and provide relevant details for creating an integration flow.
The next action is:
● In the Design tab, find the generated integration flow in the pre-existing package.
● Optional: You can enhance the integration flow and then deploy it.
 Note
Creation of integration flow is only possible for APIs that have Basic Authentication, and DELETE, GET,
POST, PUT, and GET_ID operations.
To generate an integration flow and add it to the workspace of an existing integration package, do as follows:
Procedure
1. Choose Discover APIs to access the prepackaged APIs.

2. Choose an API content package, and then choose the Artifacts tab to select the relevant API type.
3. Choose Generate Integration Flow, and provide the relevant details to create and add the integration flow.
Results
You have generated an integration flow and added it to an existing integration package.
4.3 Working with Prepackaged Integration Content
SAP delivers rich prepackaged integration content out of the box that enables you get started quickly. These
integration packages are created for some of the commonly used integration scenarios. They contain
integration flows, value mappings, documentation, and so on. By using this content, you can easily get started
with minimal integration developer effort.

 Note
You can also find integration content from SAP partners in the Discover tab. If you are viewing the package
in Highlights section, they can be identified by the tag Partner on the top-right part of the integration
package tile. You can also find these packages by filtering for the Vendor with any other available value
apart from SAP.
You cannot download content from integration packages by SAP partner vendors.
You can access this content on the SAP API Business Hub here: https://api.sap.com/shell/integration . Copy
the content to your workspace (Design tab), configure it and deploy it. Here's a representation of the typical
workflow:
You can also watch this video for more information on prepackaged integration content:
4.4 Add Integration Packages to the Customer Workspace
Prerequisites
You have logged-on to the Web application with the integration developer role.
Context
You have to add the integration packages to your customer workspace (Design tab page). This enables you to
access the artifacts in that package, configure, and deploy them. There are two options to do this:
1. Copy integration package from catalog (Discover tab page) to your customer workspace.
2. Upload integration package from your local file system to your customer workspace.
You use this procedure to add integration packages to your customer workspace.
Procedure
1. If you want to copy integration package in catalog to your customer workspace, mouse-over the integration
package tile and choose .

2. If you want to upload an integration package from your local file system to your customer workspace,
perform the following substeps.
a. Choose Design .
b. Choose Import.
c. Navigate to the folder in your local file system in which you have saved the integration package.
 Note
The integration package must be a .zip file.
d. Choose Open.
You see the integration package that you uploaded in your customer workspace.
4.5 Creating an Integration Flow
You can add an integration flow to an integration package.
Prerequisites
● You have logged on to SAP Cloud Platform Integration.

● You have created an integration package. For more information, see Add Integration Packages to the
Customer Workspace [page 414].
Context
An integration flow is a graphical representation of the flow and processing of messages between two or more
participants using an integration runtime platform, ensuring successful communication.
Here's how you can create an integration flow in SAP Cloud Platform Integration.
Procedure
1. Choose  to access your workspace.

2. Select the integration package in which you want to add an integration flow and choose Edit to enable
editing of the package.
3. Choose Add Integration Flow .

4. If you want to create a new integration flow, execute the following substeps:
a. Choose the Create radio button.
b. Enter the integration flow details.
You can select the product profile for the integration flow in theProduct Profile field. The integration
flow templates used during creation adheres to the latest version of a component available in the
product profile.
c. Choose OK.
You see a message confirming that the integration flow has been created.
5. If you want to upload an integration flow, execute the following substeps:
a. Choose the Upload radio button.
b. Choose Browse to select the integration project archive from your local file system. When you select
the archive file, the Name and ID fields in the dialog box are filled automatically.
You can also modify the name of the integration flow.

c. Choose OK.
If there is already an integration flow with the same ID, the upload will throw an error. Change the name
of the integration flow and choose OK. You see a message confirming that the integration flow has
been created.
Changing the name also updates the ID of the integration flow.
 Note
You can copy an integration flow artifact from the Artifact Actions view.
○ An integration flow can be copied within the same package or to a different package.
○ The copied integration flow has the same version as the source.
○ An integration flow can be copied from a configure-only package to a non-configure-only
package.
○ An integration flow cannot be copied from a non-configure-only package to a configure-only
package.
4.6 Integration Flow Extension
SAP Cloud Platform Integration allows you to extend the capabilities of standard integration content provided
by SAP. This approach allows you to implement specific integration scenarios relevant to your business use
case without changing the content provided by SAP.
SAP (or SAP partners) provide prepackaged integration content (also referred to as standard content) that
covers a large variety of integration requirements. This content usually comprises a set of integration flows,
value mappings, and other integration artifacts that cover a standard integration use case. If you want to adapt
these capabilities to specific business requirements, you might consider directly editing and modifying the
related integration flows contained in the standard integration package.
However, this does have some disadvantages. For example, you will not get any further updates to modified
standard integration content. Furthermore, if you copy the updated standard package from the SAP Integration

Content Catalog to the Design workspace of your tenant, you will overwrite all changes that you have made to
that package.
To avoid such implications, we recommend decoupling the modifications (required for your specific business
scenario) from the standard content provided by SAP. To support this pattern, SAP Cloud Platform Integration
comes with dedicated concepts and features. Using these features, a customer can specify requirements in
one or more dedicated custom integration flows, without touching any integration flows from the standard
content. Both the standard and the custom integration flows are deployed on the same tenant and are
processed in conjunction, communicating with each other using a specific adapter, the ProcessDirect adapter.
 Note
Using the described concepts, the customer can keep the standard integration content unchanged and
specify any required enhancements (for example, specific mappings) in one or more custom integration
flows separate from the standard integration flow.
We can summarize the advantages as follows:
● Ensures better lifecycle management of prebuilt integration flows. If you make custom changes to a
standard integration flow (prebuilt by SAP), this has an impact on lifecycle management, as you will not
receive future updates related to modified artifacts on your tenant. Additionally, if you copy the
updated standard package from the content catalog to the Design workspace of your tenant that
contains the modified packages, you will overwrite all changes that have been made to that package.
Therefore, defining all required changes in a dedicated integration flow helps you to better manage the
lifecycle of your integration packages.
● Provides flexibility to integration developers to customize their integration flows without modifying
them entirely.
● Enables the reuse of integration flows for mapping across different integration projects.
Involved Target Groups
As an integration flow extension is based on the interplay of standard integration content with one or more
custom integration flows, two target groups are involved in the overall process:
● Content publisher (at SAP or an SAP partner)

● Customer doing the actual extension (referred to as customer in the following)
This documentation is structured as follows to serve both groups:
Section Target Group
Integration Flow Extension - Concepts [page 418] Content publisher
Provides an overview of the concept and the involved com Customer

ponents; shows how standard content and extended content
work in conjunction.

Section Target Group
Mapping Extension Step by Step (Demo Example) [page Content publisher

424]
Customer
Provides a step-by-step description of a simple demo exam
This scenario is also feasible as a learning scenario: You
ple and covers both sides of the extension story:
should be able to set up and run this example in about an
● Creating the Standard Integration Flow [page 428] hour.
Shows how to design the standard integration content
(with a post-exit step)
● Creating the Custom Integration Flow with the Post-Exit
Mapping [page 440]
Shows how to design a post-exit integration flow (with
the customer mapping extension)
Mapping Extension Step by Step (Example from SAP Hybris Customer

C4C) [page 446]
Shows how a mapping extension is done for a real-life use

case (covering pre-exit and post-exit mappings).
4.6.1 Integration Flow Extension - Concepts
This section provides an overview of the concepts and components required to implement an extension.
 Note
The use cases that we use to explain the concept in detail are all mapping extensions, and we use variations
of mapping extensions for our examples and tutorials as well.
Note that you can, however, extrapolate the concept to any other kind of extension.
 Caution
Customer Exits
The basic concept is that a standard integration flow (predefined by SAP or an SAP partner as part of a
standard integration package) contains one or more customer exits, through which one or more customer
integration flows (designed by the customer who is extending the standard content) are called. The standard
integration flow and the custom integration flows (called through the customer exit) have to be deployed on the
same tenant.

To support mapping extensions, standard integration flows can provide two types of customer exits:
● Pre-exit
This exit is only required if the customer needs to extend the source message of the mapping. Using this
exit, the standard integration flow calls a pre-exit integration flow (which is designed by the customer).
Within the pre-exit integration flow, the extended source message is mapped to the message that is
consumed by the mapping predefined in the standard integration flow.
● Post-exit
This exit is always required. It calls a post-exit custom integration flow that maps the output of the
standard mapping and the extended source structure to the extended target structure.
The following figure shows the general overview of the message flow when a pre-exit and a post-exit are
involved in the extension scenario.
The message flow in such an extension scenario works in the following way:
Let us assume that the mapping predefined in the standard integration flow defines the transformation of an
original message A to message B.
We also assume that the customer has enhanced the source structure of the mapping (resulting in message
A'). The pre-exit integration flow contains a mapping that transforms message A' to message A. Message A is
then handed over to the standard integration flow and can be consumed by the predefined mapping.
The predefined mapping transforms message A to message B. Message B is then passed to the post-exit
integration flow, where it is mapped against the actual enhancement of the target structure (defined as
message C).
As indicated in the figure, the standard integration flow merges the original message (with the extended
structure, message A') with message B before handing it over to the post-exit integration flow. How this is done
is explained further below. The post-exit mapping then consumes the merged message. Merging the message

is a prerequisite for using fields from the original message A' that might have got lost during the standard
mapping step in the post-exit mapping.
 Note
Technically, the communication between the standard integration flow and the pre-exit and post-exit
integration flow is accomplished through the ProcessDirect adapter.
This adapter allows you to directly connect different integration flows deployed on the same tenant. In
contrast to any of the available HTTP-based adapters ( for example, the HTTP or SOAP adapter),
communication through the ProcessDirect adapter is not routed through the load balancer and, therefore,
does not imply any network latency.
The ProcessDirect adapter (both sender and receiver) has only one parameter, which is Address. When two
integration flows need to communicate with each other through this adapter, the value specified for
Address (in the related sender and receiver ProcessDirect adapters) has to match in both integration flows.
More information: Configure Communication Channel with ProcessDirect Adapter [page 684]
 Note
The standard integration flow is developed as part of an integration package that is made available in the
Integration Content Catalog (either by SAP or an SAP partner). For the sake of simplicity, we refer to this
target group as the integration content publisher.
The custom integration flows (pre-exit and post-exit integration flows) are developed by customers who
want to consume the integration package and build the extension on top. For the sake of simplicity, we refer
to this target group as the customer.
Depending on whether the standard integration flow contains both a pre-exit and a post-exit, or only a post-
exit, the customer needs to create either two integration flows (a pre-exit and a post-exit integration flow)
or only one post-exit integration flow to specify its own extensions.
Structure of the Standard Integration Flow
We first describe the structure of the standard integration flow, and then the structure of the custom (pre-exit/
post-exit) integration flows.
The standard integration flow that supports mapping extensions is generally structured in the following way. It
contains one or more customer exits (pre-exit or post-exit). These exits are encapsulated within local
integration processes. From the local integration process, the related pre-exit or post-exit integration flow is
called by the ProcessDirect receiver adapter.
The following figure shows the general structure of the standard integration flow containing both a pre-exit
and a post-exit. Furthermore, the message flow is illustrated using the same notation for the different
messages as already used above.

The standard integration flow contains a main integration process shape and two local integration process
shapes (as we assume that both a pre-exit and a post-exit are involved in this scenario):
● The main integration process contains the main business logic (in this section, we'll just look at a mapping)
and two routing steps leading to two different message processing paths (both containing a Process Call
step).
● The local integration processes contain further steps to modify the message and – most important – the
outbound call to a receiver. The receiver represents the pre-exit or post-exit integration flow. The outbound
communication with the receiver is defined in a ProcessDirect adapter.
In the model, the local integration process on the left represents the pre-exit, and the local integration
process on the right represents the post-exit.
Let's go into more detail. The integration flow is designed so that the message is processed in the following way
at runtime:
Main Integration Process
● The sender system sends a message (A', which is the extended source message structure) to SAP Cloud
Platform Integration through a sender channel.
● The Content Modifier creates two exchange properties:
○ custom_extension_enabled
This exchange property is used as a parameter to control whether the extension concept should be
applied to the standard integration flow or not. If its value is set to true, the pre-exit and post-exit
integration flows are called. If its value is false, the standard mapping is applied without any further
extension.
This parameter is externalized so that the value can be specified during integration flow configuration
without the need to edit the integration flow model.
○ original_payload
In this exchange property, the content of the original message received by the sender is stored (to
make it available in a later step where the original message is merged with the transformed message
as preparation for the post-exit mapping step).

● The first router step opens two alternative processing paths. Which path is processed depends on the
routing condition, which uses the exchange property custom_extension_enabled defined in the
preceding Content Modifier.
○ If the value of the property custom_extension_enabled is false, the default route (upper path) is
taken.
The default route directly leads to the standard mapping.
○ If the value of the property custom_extension_enabled is true, the second route (lower path) is
taken. This route contains a Process Call step that passes the message to the local integration process
on the left (pre-exit).
This route is processed under the condition that the value of the exchange property
custom_extension_enabled is true.
● The mapping step transforms the inbound message to the target message B. The mapping step in this
integration flow contains the standard mapping predefined by SAP or an SAP partner. This step always
expects a predefined original message structure (message A). If the customer has extended the source
structure (to message A'), the message needs to be processed by the pre-exit before the standard mapping
step, to be transformed to the original structure A (as already explained above).
● The subsequent router step also opens two alternative processing paths, using the same routing condition
as the first router step (using the exchange property custom_extension_enabled defined in the
Content Modifier).
○ If the value of the property custom_extension_enabled is false, the default route (upper path) is
taken.
The default route now ends message processing. In this case, the message is not subjected to any
further processing other than the standard mapping.
○ If the value of the property custom_extension_enabled is true, the second route (lower path) is
taken. This route contains a Process Call step that passes the message to the local integration process
on the right (post-exit).
Local Integration Process (Pre-Exit)
If the message is first handed over to the local integration process with the pre-exit, the following steps are
executed on the message:
A Request-Reply step calls a receiver (which represents the pre-exit integration flow) through a ProcessDirect
receiver adapter.
The address of the ProcessDirect adapter is externalized and can be configured during integration flow
configuration. The customer needs to make sure that the address of the ProcessDirect receiver adapter (of the
standard integration flow) is the same as the one used in the ProcessDirect sender adapter of the pre-exit
integration flow (to be connected).
Local Integration Process (Post-Exit)
If the message is first handed over to the local integration process with the post-exit, the following steps are
executed on the message:
● A Content Modifier constructs a message body that is composed of the following two parts:
○ The original payload received from the sender (contained in the original_payload exchange
property created in the Content Modifier of the main integration process)
(message A' in the figure)
○ The message that results as output from the Mapping step in the main process
(message B in the figure)

With this step, the original payload from the sender system (A') is merged with the output message (B)
resulting from the standard mapping step. The concatenated message is denoted as message A',B.
This measure is required for the following reason: The standard mapping step transforms the original
message into a new one (B), which means that certain fields from the original message (A) may no longer
be available in the resulting message B. However, the customer might require such fields in the custom
mapping step (which will be executed in the custom integration flow, as explained below). The message
merge is done in order to make sure that all fields of the original message are still available in the message
that is handed over to the post-exit integration flow.
● A Request-Reply step calls a receiver (which represents the post-exit integration flow) through a
ProcessDirect receiver adapter.
The address of the ProcessDirect adapter is externalized and can be configured during integration flow
configuration. The customer needs to make sure that the address of the ProcessDirect receiver adapter (of
the standard integration flow) is the same as the one used in the ProcessDirect sender adapter of the post-
exit integration flow (to be connected).
Structure of the Pre-Exit and Post-Exit Integration Flows (Designed by

Customer)
The following figure shows the general structure of a pre-exit or post-exit integration flow.
● The sender shape represents the standard integration flow, which passes on the original message. The
sender component is connected to the integration process component through a ProcessDirect sender
adapter.
● Detailed instructions about the mapping are provided in a separate topic. In short, the mapping steps in
the pre-exit and the post-exit integration flow process the inbound message in the following way:
○ Pre-exit mapping: Transforms the extended source message A' into the original message A, which can
be consumed by the standard mapping.
○ Post-exit mapping: Transforms the message A',B from the standard integration flow into the final
message C.

Procedure
The following list contains the main tasks in an integration flow extension process:
Tasks accomplished by the content publisher (SAP or SAP partner):
Create and publish the standard integration flow. Make sure that it contains the required customer exits (post-
exit and, if applicable, pre-exit point). Externalize those parameters that the customer needs to configure the
required parameters (for example, the addresses of the involved ProcessDirect adapters) without changing the
standard integration flow.
Tasks accomplished by the customer (extending the content):
 Note
It is a prerequisite that you, the customer, have imported the integration package that contains the
standard integration flow (that is to be extended) into your own workspace.
1. Copy the desired standard integration flow (as contained in the Integration Content Catalog) into your own
workspace.
2. Create the required custom integration flows (with the pre-exit and post-exit steps).
Make sure you deploy the custom integration flows on the same tenant as the standard integration flow.
3. Configure the standard integration flow so that it can be used together with the custom integration flows.
To access the configuration user interface with the externalized parameters, open the standard integration
flow and select Configure.
Examples:
○ For the custom_extension_enabled parameter, enter the value true.
○ For the Address parameter of the ProcessDirect receiver adapter, enter the same value as used in the
Address field of the custom integration flow's ProcessDirect sender adapter.
Related Information
Configure Communication Channel with ProcessDirect Adapter [page 684]

Configure Externalized Parameters of an Integration Flow [page 479]
Define Process Call [page 842]
Define Local Integration Process [page 847]
Define Content Modifier [page 766]
4.6.2 Mapping Extension Step by Step (Demo Example)
A demo example, explained step by step, covers the key aspects of integration flow extension.
This section provides a more detailed view of the concept overview given in Integration Flow Extension -
Concepts [page 418]. We walk you through the most important concepts and involved components using a
simple demo scenario.
You should be able to set up and run the scenario within approximately one hour.

 Note
The demo scenario covers both the design of the standard integration flow and of the custom integration
flow. Consider the following:
● This demo scenario covers both sides of the extension concept: the design of the standard integration
content and the customer extension (in a post-exit integration flow). Note that these tasks are typically
accomplished by different target groups. Therefore, the demo scenario is aimed at experts from both
target groups who want a more detailed understanding of the concepts and also hands-on experience
of the tasks.
The tasks described in the two parts of the demo scenario are associated with the different target
groups as follows:
○ Creating the Standard Integration Flow [page 428]
Describes the tasks accomplished by the content publisher (at SAP or an SAP partner
organization) who makes this integration flow available as part of a predefined integration package
that customers can copy into their own workspace.
○ Creating the Custom Integration Flow with the Post-Exit Mapping [page 440]
Describes the tasks accomplished by the customer who is extending the content.
● The example scenario does not reflect a real-life integration use case. We keep the mapping as simple
as possible and focus on the main principles and concepts so that you can see the differences between
the standard mapping provided by SAP and the customer extension. To make it easy for you to
reproduce the example, the integration flows are based on the scenario described in SOAP Sender
Adapter: Example Integration Flow [page 525].
● To find instructions for a mapping extension based on a real-life example, check out Mapping Extension
Step by Step (Example from SAP Hybris C4C) [page 446].
● The demo scenario does not use a pre-exit step.
Overview of the Demo Scenario
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
More information: Standard Mapping [page 426]
The mapping extension in the post-exit integration flow (the customer extension) adds an additional field to the
target message and fills it with the value of a field from the original message ( changing uppercase letters to
lowercase letters).
More information: Post-Exit Mapping [page 427]
To learn how to design the standard integration flow, see Creating the Standard Integration Flow [page 428].
To learn how to design the post-exit integration flow, see Creating the Standard Integration Flow [page 428].
To learn how to execute the scenario, see Executing the Scenario [page 444].
4.6.2.1 Standard Mapping
The following figure shows the mapping used in this demo scenario.
The figure also indicates which fields correspond to the messages A and B as used in the concept overview in .

In the standard mapping, the original message A is transformed in the following way:
The fields customerForename and customerForename are concatenated (resulting in the field
customerName of target message B).
4.6.2.2 Post-Exit Mapping
The following figure shows the custom mapping extension in the post-exit integration flow.

Here, the only mapping extension is the addition of the field AdditionalField to the target structure.
The custom mapping maps the customerSurname field of the source message to the new field
AdditionalField and applies a simple function (changing uppercase characters to lowercase characters).
4.6.2.3 Creating the Standard Integration Flow
 Note
This section is targeted at the content publisher at SAP or an SAP partner organization.
The standard integration flow is depicted in the following figure, where the key elements are highlighted.

This is a summary of the elements of the integration flow. Check out the detailed topics below to find out how
to design these shapes.
● 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.
● Content Modifier
This step performs the following tasks:
○ Stores the body of the inbound message in an exchange property (originalpayload).
○ Creates another exchange property custom_extension_enabled, which is used in the subsequent
routing step to separate message processing depending on whether the custom extension is activated
or not.
We show how to externalize this parameter so that you can easily specify its value during the
integration flow configuration without having to redesign the integration flow.
● Message Mapping
This step defines the standard mapping according to Standard Mapping [page 426].
● Router
The Router step leads to two different message processing paths. The routing conditions are expressed
using the exchange property custom_extension_enabled in the following way:
○ Default route: Ends message processing without any further message processing.
○ Route taken if the following condition is met: custom_extension_enabled=true
This message processing path contains a Process Call step, which calls the local integration process
(post-exit).
After the Process Call step, a filter is added. This step filters the relevant parts from the message that
is received from the post-exit integration flow.
The local integration process has the following elements:
● Filter

This step filters the elements from message B (which is the result of the standard mapping step) that are
needed in the merged message (A,B), which is to be sent to the post-exit integration flow. This step is used
to prepare the content of message B before it is merged with the original message A in the subsequent
● Content Modifier
Merges message A and message B by constructing a new message body using dynamic expressions for
the original message A and the processed message B.
● Request-Reply step connected through ProcessDirect adapter with receiver
Uses the ProcessDirect receiver adapter to call the custom integration flow.
At runtime, the target integration flow is called based on the endpoint address configured in the adapter.
You will learn how to externalize this parameter.
The integration flow does not have a receiver component. The result of the mapping can be analyzed in the
response that is sent back to the SOAP client.
Related Information
Creating the SOAP Sender Adapter [page 430]

Defining the Content Modifier [page 430]
Defining the Standard Message Mapping [page 432]
Defining the Local Integration Process [page 436]
Defining the Router, Process Call, and Filter Steps [page 438]
4.6.2.3.1 Creating the SOAP Sender Adapter
Follow the instructions in the following topic: Create the SOAP Sender Channel [page 527]
4.6.2.3.2 Defining the Content Modifier
1. Add a Content Modifier after the start message event.

You find the Content Modifier shape in the palette under Message Transformation Content Modifier .

2. On the Exchange Property tab, enter the following property (by selecting Add and specifying the property):
Parameter Select Option/Enter
Name Enter original_payload
Type Select Expression
Value Enter ${in.body}
This property stores the content of the inbound message (message A, which is retrieved from the
WebShop) by dynamically evaluating the Camel simple expression ${in.body} at runtime.
We define the second property as an externalized parameter.
1. Select Externalize.
2. Go to the Exchange Property tab.
3. Enter custom_extension_enabled under Name, select Expression as the Type, , and enter
{{ custom_extension_enabled }} in the Value field.
4. Click Define Value (in the Value field), and on the next screen enter false. Then, choose OK
The final Content Modifier has the following settings:
When the integration flow is being processed, the Content Modifier does the following:
● It writes the complete message body (retrieved from the external OData service) into the property
original_payload.
● Secondly, it writes the value specified during integration flow configuration for the externalized parameter
custom_extension_enabled into the Exchange property. This property is used in the subsequent
routing step to determine whether the default route is taken (where only the SAP mapping is processed
and nothing else is done to the message) or whether the customer exit is taken (if the value of
custom_extension_enabled is set to true).

4.6.2.3.3 Defining the Standard Message Mapping
Before defining the standard mapping, you need to upload to the tenant certain resource files (Web Services
Definition Language, or WSDL files for short) that define the structure of source message (A) and target
message (B) of the mapping. To facilitate the design of the demo scenario, we provide you with the content of
the WSDL files in this section.
To upload the WSDL files, perform the following steps:
1. Copy the content of the following coding example into a text editor and save it as a file with
extension .wsdl (for example, A.wsdl).
This WSDL file defines the structure of the source message of the standard mapping (corresponding to the
original message A, which is sent to the integration flow through the SOAP client).
 Sample Code

<wsdl:definitions name="SendOrder_Async"
targetNamespace="http://cpi.sap.com/demo" xmlns:p1="http://cpi.sap.com/
demo"
xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-
wssecurity-utility-1.0.xsd"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:documentation />
<wsp:UsingPolicy wsdl:required="true" />
<wsp:Policy wsu:Id="OP_SendOrder_Async" />
<wsdl:types>
<xsd:schema targetNamespace="http://cpi.sap.com/demo"
xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://
cpi.sap.com/demo">
<xsd:element name="Order_MT" type="Order_DT" />
<xsd:complexType name="Order_DT">
<xsd:sequence>
<xsd:element name="orderNumber" type="xsd:string" />
<xsd:element name="customerForename"
type="xsd:string" />
<xsd:element name="customerSurname"
type="xsd:string" />
<xsd:element name="productName" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="Order_MT">
<wsdl:part name="Order_MT" element="p1:Order_MT" />
</wsdl:message>
<wsdl:portType name="SendOrder_Async">
<wsdl:operation name="SendOrder_Async">
<wsp:Policy>
<wsp:PolicyReference URI="#OP_SendOrder_Async" />
</wsp:Policy>
<wsdl:input message="p1:Order_MT" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="SendOrder_AsyncBinding" type="p1:SendOrder_Async">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" />

<soap:operation soapAction="http://sap.com/xi/WebService/
soap1.1"
<wsdl:input>
<soap:body use="literal" xmlns:soap="http://
schemas.xmlsoap.org/wsdl/soap/" />
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
You will notice that the WSDL contains exactly the same fields that are shown in the topic Standard
Mapping [page 426] for message A.
2. Do the same with the following code sample, but save it under a different name, for example, B.wsdl.
This WSDL file defines the structure of the target message B of the standard mapping.
 Sample Code

demo"
<wsdl:types>
cpi.sap.com/demo">
<xsd:sequence>
<xsd:element name="customerName" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
</wsdl:message>
<wsp:Policy>
</wsp:Policy>
</wsdl:operation>
</wsdl:portType>
soap1.1"

<wsdl:input>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
 Tip
You might have noticed that in this WSDL document the namespace prefix p2 is used instead of the
namespace prefix p1 (used in the WSDL for message A). For example, note the following entry:
p2="http://cpi.sap.com/demo.
This is an important detail. Using the correct namespace prefixes (and making some further related
settings in the integration flow as shown below) makes sure that the merged message that is passed on
to the post-exit mapping can be interpreted in the right way. Using namespaces correctly is critical
because the merged message contains the structures of messages A and B, which have many
elements with the same name.
We map the namespaces in the next step to complete this configuration.
3. In the integration flow editor, click somewhere outside the Integration Process shape and select Runtime
Configuration. In field Namespace Mapping enter the following:
xmlns:p1=http://cpi.sap.com/demo;xmlns:p2=http://sap.com/xi/XI/SplitAndMerge
The namespace mapped to the prefix p2 relates to the final merged message.
4. In the integration flow editor, click somewhere outside the Integration Process shape and select Resources.
5. Choose Add Schema WSDL and browse to the A.wsdl file.
6. Repeat these steps for the B.wsdl file.
Now you can define the mapping step.
1. In the integration flow model, select the Message Mapping shape from the palette (under Mapping) and
place it in the model after the second Content Modifier.

2. Choose the + icon next to the message mapping shape and enter a name for the message mapping (for
example, standardmapping).
3. Choose Create.
4. The graphical mapping editor is opened.
5. Choose Add source message and browse to the WSDL file of the source message (in our example, the file
A.wsdl). Choose Upload from file system.
6. Choose Add target message and repeat the steps with the WSDL file for the target message (B.wsdl).
7. Connect the fields of the source and target message in the following way using the cursor:
○ Connect orderNumber in the source message with orderNumber in the target message.
○ Connect customerForename in the source message with customerName in the target message.
○ Connect customerSurname in the source message with customerName in the target message.
○ Connect productName in the source message with productName in the target message.
8. Click customerForename in the source message. The connectors between customerForename and
customerSurname (in the source message) and customerName (in the target message) are highlighted.
9. In the section below the graphical mapping editor, select the function Text Concat . Connect the
source and target fields in the following way:
Connect customerForename with string1 and customerSurname with string2. Connect concat with
customerName.
Furthermore, you can add a delimiter string (for example, / or an empty space).

Your mapping should now look like this:
This mapping function merges the fields customerForename and customerSurname from the source
message to one single field customerName in the target message (where the values are separated in the
target field by the delimiter string).
10. Choose OK. The integration flow model is displayed again.
4.6.2.3.4 Defining the Local Integration Process
Before continuing to the routing step, we first add a local integration process shape to the integration flow
model.
1. In the palette, select Process Local Integration Process and position the shape below the (main)
Integration Process shape.
2. In the palette, select Transformation Filter and place the filter shape to the right of the start event of
the local integration process.
3. Click the Filter shape and, on the Processing tab, enter the following string in the XPath Expression field: /
p1:Order_MT
Keep the default setting of Value Type as Nodelist.
This step will filter the required elements from the message structure Order_MT (associated with the
namespace mapped to prefix p1) from the processed message B (to prepare the message for the
subsequent merge step).

4. Add a Content Modifier to the right of the Filter step (you can find this under Message Transformers in the
palette).
On the Message Body tab, enter the following:
 Sample Code
<Messages>
<Message1>
${property.original_payload}
</Message1>
<Message2>
${in.body}
</Message2>
</Messages>
This step creates the message (A,B), which will be passed on to the custom integration flow.
Again, you will notice the following dynamic expressions:
○ Expression ${property.original_payload} is replaced at runtime by the content of the original
message A (which was stored prior to the standard mapping step in the Exchange property).
○ Expression ${in.body} is replaced at runtime by the content of the message that enters the Content
Modifier. This is message B, which results from the standard mapping.
5. Add a Request-Reply step (you can find this in the palette under Call External Call ) to the right of the
Content Modifier.
6. Add a receiver shape below the local integration process and connect it to the Request-Reply step.
7. When connecting the shapes, select ProcessDirect as the Adapter Type.
8. The ProcessDirect adapter has only one parameter that you need to configure. Specify the Address as an
externalized parameter.
Select Externalize and, on the next screen, enter {{endpoint}} as Address.
9. Choose Define Value and enter any value starting with /.

10. Choose OK.

The local integration process should now look something like this:
Click in the area outside the integration process and the local integration process shapes and select
Externalized Parameters.
You will find the two parameters that you have already defined as externalized parameters (one from the
Content Modifier on the More tab and the endpoint address of the ProcessDirect adapter on the Receiver tab).
4.6.2.3.5 Defining the Router, Process Call, and Filter Steps
Now that you have defined the local integration process, you can continue with the design of the main
integration process.
1. In the main integration process, add a Router step to the right of the message mapping. You can find the
step type in the palette under Message Routing Router .
2. Add another end message event (from the palette under Events) and place it below the existing one.
3. Connect the Router step with the second end message event.
4. Click the upper route (connection of router step and upper end message event) and, on the Processing tab,
select Default Route.

5. Click the lower route and, on the Processing tab, specify the following:
○ Select Non-XML as Expression Type.
○ Under Condition, enter the following routing condition:
${property.custom_extension_enabled} = 'true'
This condition will be evaluated at runtime in the following way: The value of the (externalized)
parameter custom_extension_enabled is checked. If the value is true, this route will be
processed. If not, the default route is processed (which means that message is not subjected to any
further processing after the standard mapping step).
6. In the lower route, add a Process Call step (which you can find in the palette under Call Local Call ).
Select the Process Call shape and, on the Processing tab, choose Select. You can now select the local
integration process that you have already defined in a preceding step.
7. In the lower route, after the Process Call shape, add a Filter step (you can find this in the palette under
Transformation Filter ).
This part of the integration flow model should now look like this:
8. On the properties sheet of the Filter step. under Processing, add the following expressing in the XPath
Expression field:
/p2:Messages/p2:Message1/p1:Order_MT
Note that this setting contains two different namespace prefixes, p1 and p2. The mapping of these prefixes
with the relevant namespaces is defined on the Runtime Configuration tab of the integration flow (as shown
in Defining the Standard Message Mapping [page 432]).
Using different namespace prefixes and addressing them correctly as described is necessary to make sure
that the correct parts of the message are filtered. Note that this Filter step comes after the Process Call
step, and so it gets the message processed in the post-exit integration flow as input.

4.6.2.4 Creating the Custom Integration Flow with the
Post-Exit Mapping
 Note
This section is targeted at the customer who is doing a mapping extension.
This integration flow is kept very simple.
● The sender shape in this model represents the standard integration flow (which is the source integration or
producer integration flow). The custom integration flow receives the message from the producer
integration flow through the ProcessDirect adapter (as both integration flows are deployed on the same
tenant).
● The post-exit message mapping step contains the mapping as explained under Post-Exit Mapping [page
427].
Related Information
Configuring the ProcessDirect Sender Adapter [page 440]

Creating the Custom Mapping [page 441]
4.6.2.4.1 Configuring the ProcessDirect Sender Adapter
1. Create a new integration flow (this will be the custom integration flow).
2. Remove the receiver component.
3. Connect the sender shape with the start message event and select ProcessDirect as Adapter Type.
4. Configure the address of the ProcessDirect adapter as an externalized parameter in the same way as
described in Defining the Local Integration Process [page 436] for the ProcessDirect receiver adapter in
the standard integration flow.

4.6.2.4.2 Creating the Custom Mapping
It is a prerequisite for the custom mapping that you upload the WSDL files defining the source and target
message structures to the Resources tab of the integration flow (as shown for the standard mapping in Defining
the Standard Message Mapping [page 432]). As you can see, three message structures, A, B, and C, are
involved in the mapping, and the corresponding resource files (WSDLs) have to be made available to the
integration flow.
To make it easy for you to define the mapping step, we provide the content of the WSDL files below.
You can use this content to create the WSDL file for the source and target message of the custom mapping:
For the source message, import two WSDL files:
● The WSDL file describing the original message A (as contained in the standard integration content)
Use file A.wsdl from Defining the Standard Message Mapping [page 432].
● The WSDL file describing the message structure after the standard mapping (message B)
Use file B.wsdl from Defining the Standard Message Mapping [page 432].
However, note one important detail: In this WSDL file, you need the original namespace prefix p1.
Otherwise, message processing results in a namespace conflict and the mapping step cannot be executed
without an error.
Correspondingly, to define the WSDL file for message B (B.wsdl), copy the following content:
 Sample Code

demo"
<wsdl:types>
cpi.sap.com/demo">
<xsd:sequence>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
</wsdl:message>
<wsp:Policy>
</wsp:Policy>

</wsdl:operation>
</wsdl:portType>
soap1.1"
<wsdl:input>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
 Note
Both WSDL files together define the structure of the merged message (A, B), which is passed on from the
standard integration flow (as you will see when defining the message mapping).
For target message C, create a WSDL file with the following content and import it to the integration flow
Resources tab:
 Sample Code

demo"
<wsdl:types>
cpi.sap.com/demo">
<xsd:sequence>
<xsd:element name="additionalField" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
</wsdl:message>
<wsp:Policy>

</wsp:Policy>
</wsdl:operation>
</wsdl:portType>
<soap:operation soapAction="http://sap.com/xi/WebService/soap1.1"
<wsdl:input>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
Note that message structure C is similar to message structure B; it has one additional field
additionalField. Save the file with the name C.wsdl.
Perform the following steps to define the mapping:
1. Add a message mapping shape between the start message and the end message event.
Choose the + icon and define a name for the message mapping.
2. Choose Create.
The mapping editor opens.
3. Select Add source message and browse to the file A.wsdl.
4. Choose the Edit message icon.
The Source and Target Messages editor opens.

The structure of message A is already displayed under Source Messages.
5. Choose the + icon beneath Source Messages and add file B.wsdl.
6. In the same way, choose the + icon beneath Target Messages and add file C.wsdl.
After this step, messages A and B are shown under Source Messages and message C is shown under Target
Messages.
7. Choose OK to go back to the mapping editor.

8. In the source message structure on the left side, open the nodes under ns1:Message2 (the lower part of
the source structure), and on the right side open the nodes of the target structure. Then, connect each
field of the source structure to the field with the same name in the target structure. Leave out the field
additionalField in the target structure.
9. Now, open the upper part of the source structure and connect the field customerSurname in the source
structure with the field additionalField in the target structure.
The figure below shows the final mapping and also indicates which parts are associated with the messages
A, B, and C.
10. Finally, to apply the mapping function for the connection of the fields customerSurname (source
structure) and AdditionalField (target structure), open the mapping expression Text
toLowerCase . Connect the source and target field in the following way: customerSurname with
toLowerCase and connect the latter with AdditionalField.
11. Choose OK to return to the integration flow model.
12. Save and deploy the integration flow.
4.6.2.5 Executing the Scenario
To execute the scenario, you need to install a SOAP client (for example, SoapUi) and configure it accordingly.
You need to configure the SOAP client so that it calls the endpoint address of the standard integration flow.
More information: Set Up the SOAP Client and Start Message Processing [page 529]
To define the inbound message (sent by the SOAP client), upload the file A.wsdl in the SOAP client. When the
SOAP client has been configured accordingly, and the message structure is shown, you can enter any values for
the elements, for example:

1. Configure the standard integration flow (open the standard integration flow and choose Configure).
2. Specify a value for the Address parameter of the ProcessDirect adapter (or leave the default value as it is).
3. Go to the More tab and leave the default value for the custom_extension_enabled parameter as false.
4. Choose Save and then Deploy.

5. Choose the Operations view of the Web UI and under Manage Integration Content check the deploy status
of your standard integration flow.
6. As soon as the integration flow deployment has finished (status Started), copy the endpoint address to
your clipboard and paste it into the address field of your SOAP client.
7. Now configure and deploy the custom integration flow. Make sure that you configure the same
ProcessDirect adapter Address parameter as in the standard integration flow.
When the custom integration flow is also deployed, trigger message processing from your SOAP client as
explained in Set Up the SOAP Client and Start Message Processing [page 529].
The SOAP client should receive a response where the standard mapping has been applied to the original
message.
The fields customerForename and customerSurname of the original message have been concatenated
in the field customerName.
8. Repeat all these steps, but with the externalized parameter custom_extension_enabled of the standard
integration flow specified as true.
9. The SOAP client should receive a response in which the custom mapping has been applied.
The field additionalField is available and contains the content from the original field
customerSurname (but uppercase characters have been transformed to lowercase characters).

4.6.3 Mapping Extension Step by Step (Example from SAP
Hybris C4C)
This section explains how to do mapping extensions based on a real example from the product area SAP Hybris
Cloud for Customer (C4C).
 Note
This section is targeted at the customer who is doing a mapping extension.
 Note
For more background information regarding this example, check out the following blog in SAP Community:
Extending standard integration flow to support Customer extensions .
Let's assume that you want to do a mapping extension that also includes the extension of the source message
structure. This means that both a pre-exit and a post-exit are involved. The integration flows discussed in this
section have the same structure as those explained in Integration Flow Extension - Concepts [page 418].
We also assume the following:
● The sender is an SAP ERP system sending an IDoc message to Cloud Integration. An IDoc adapter is used
as the sender channel for the standard integration flow.
● The receiver is an SAP Cloud application that expects a SOAP message (through the SOAP adapter).
● You also need to extend the source IDoc message. To support this use case, the standard integration flow
contains a pre-exit. The pre-exit step will then enable you to design a corresponding pre-exit integration
flow in order to map the extended source message to the original message structure. The message
processed by the pre-exit integration flow can then be consumed by the standard mapping.
You need to create two integration flows, one for the pre-exit mapping and another one for the post-exit
mapping. We explain the required steps to extend the mapping and to connect the custom integration flows
with the standard integration flow.
The following figure shows the overall message flow between the standard integration flow and the pre-exit and
post-exit integration flows, including sender and receiver.

The following message structures are involved in the extension scenario:
● Message A
Contains the original source message structure that is defined by the requirements of the sender system
and can be consumed by the standard mapping.
● Message A'
Contains an extended source structure (defined by the customer-specific requirements with regard to the
sender system).
Typically, the customer derives message structure A' from message structure A by adding additional fields.
In our example, the sender system is an SAP ERP system that sends an IDoc to SAP Cloud for Customer.
Messages A and A' are IDoc messages.
● Message B
This is the target structure of the standard mapping. In other words, the standard integration flow maps
message A to message B.
In order to enable the standard mapping to consume the inbound message in the customer-specific
scenario, message A' first has to be mapped to the original message structure A, which is defined in the
standard integration flow. For this purpose, the message is passed to the pre-exit integration flow and
mapped to message A, which can then be mapped within the standard integration flow.
● Message C
This is the message that results from the post-exit mapping.
Note that the letters A, A', and so on correspond to the notation as used in the general concept description in
Integration Flow Extension - Concepts [page 418].

Related Information
Prerequisites [page 448]

Creating the Pre-Exit Integration Flow [page 449]
Creating the Post-Exit Integration Flow [page 452]
Connecting Pre-Exit and Post-Exit Integration Flows with the Standard Integration Flow [page 453]
4.6.3.1 Prerequisites
Standard Integration Flow with Customer Exits
The standard integration flow (provided as part of a predelivered integration content package) with both a pre-
exit and a post-exit has the following design. The message flow as explained above is also depicted.
Required Integration Flow Resources (WSDLs)
Prerequisite: You have copied the integration package with the standard integration flow into your own
workspace.
We also assume that you, the customer, have already defined the source message structure (the extended IDoc
structure A') and the target message structure that depends on the intended final mapping (this is referred to
as message C).

 Note
The WSDL files defining the message structures A and B (source and target message of the standard
mapping) are contained as part of the standard integration flow (from the predelivered integration
package).
You can get these by deploying the standard integration flow (from the predelivered integration package)
on your customer tenant, opening the standard integration flow, clicking in the area outside the (local)
integration process shapes, and selecting the Resources tab. Here, you will find the related WSDL files and
you can download them.
The following figure shows the resources as uploaded to the standard integration flow:
● COD_STOCK_REPLICATE.COD_STOCK_REPLICATE01.wsdl describes the original source structure for

the standard mapping, which is an IDoc message (message A).
● DOC_INTF_II_STOCK_LOCATION_REPLIC_IN.wsdl describes the target structure of the standard
mapping (message B)
.
The standard integration flow contains a mapping that transforms message A to message B. The following
figure shows this mapping as displayed in the mapping editor:
 Note
You must not change the standard integration flow.
4.6.3.2 Creating the Pre-Exit Integration Flow
Creating the Pre-Exit Mapping
Let's assume that you want to extend the source structure by additional fields.

1. Extend the source structure of the message (to get message A').
You want to add additional elements to the source message, for example, the following element:
Z101YANEXT2.
Edit the WSDL file for message A (COD_STOCK_REPLICATE.COD_STOCK_REPLICATE01.wsdl)
accordingly (using the WSDL for message A from the Resources tab of the standard integration flow).
Save the new WSDL file under any name (for example, YANCOD_STOCK_REPLICATE01.wsdl).
2. Create a new integration flow.
We recommend that you add this new integration flow to the package that contains the standard
integration flow (both have to be deployed on the same tenant).
3. Model the integration flow according to the following figure:
4. When connecting the sender shape with the message start event, select the ProcessDirect adapter type.
Go to the Connection tab of the ProcessDirect adapter and as Address enter any value starting with a slash
(/), for example /preexit_flow.
5. In the integration flow editor, click somewhere outside the Integration Process shape and select Resources.
6. Choose Add Schema WSDL and browse to the WSDL file defining the source message (message A',
this is file YANCOD_STOCK_REPLICATE01.wsdl).
In the same way, add the WSDL file for message A to the integration flow (file
COD_STOCK_REPLICATE.COD_STOCK_REPLICATE01.wsdl).
7. Repeat these steps for the target message (here, add the WSDL file for message A). Note that the pre-exit
steps map the extended source message A' to the original message A. As mentioned above, you get the
resource for message A from the standard integration flow, whereas the resource for message A' depends
on the specific enhancements of the source structure. Typically, it is similar to message A, but contains
additional custom fields.
8. In the integration flow model, select the Message Mapping shape from the palette (under Mapping) and
place it in the model between the message start and message end event.

9. Choose the + icon next to the message mapping shape and enter a name for the message mapping (for
example, pre_exit_mapping).
10. Choose Create.

11. The graphical mapping editor is opened.
12. Choose Add source message and browse to the WSDL file of the source message (message A'). Choose
Upload from file system.
13. Choose Add target message and repeat the steps with the WSDL file for the target message (message A).
14. Connect all fields that are identical in the source and target mapping without assigning any mapping
function. Do not connect the additional fields (which have no equivalence in the target message A) to any
target field.

4.6.3.3 Creating the Post-Exit Integration Flow
Creating the Post-Exit Mapping
Create another integration flow with the same shapes as in the pre-exit integration flow (also within the same
integration package). Make the following specific settings:
● In the Address field of the ProcessDirect adapter, enter a string that is different to the one in the pre-exit
integration flow, for example /postexit_flow.
● Click in the area outside the integration process shape, go to the Resources tab, and upload the WSDL files
for the messages A', B, and C.
Note that you get the resource for message B from the standard integration flow, whereas the resource for
message C depends on the specific custom enhancements related to the target structure. Typically,
message C is similar to message B, but contains additional fields.
● Configure the message mapping in the following way:
For the source message, upload both resource files for messages A' and B. For the target message, upload
the resource file for message C.
You can proceed in the same way as described for the demo example in Creating the Custom Mapping
[page 441].

You will notice that the source message consists of two messages, A' and B.
Connect all fields in the structure below Message2 with the corresponding fields in the target structure.
● Define connections between selected (additional) fields of the extended original message A' (in the
structure below Message1) and selected fields in the target message C (typically, using fields that have
been added in the target structure).
4.6.3.4 Connecting Pre-Exit and Post-Exit Integration Flows

with the Standard Integration Flow
Connecting Custom Integration Flows with the Standard Integration Flow
To make sure that the standard integration flow and post- and pre-exit integration flows are processed in
conjunction as expected, make sure that the ProcessDirect adapter addresses match in the right way.
The ProcessDirect adapter address of the pre-exit integration flow must match the ProcessDirect adapter
address in the pre-exit of the standard integration flow.
The same applies for the ProcessDirect adapter address of the post-exit integration flow and the corresponding
ProcessDirect adapter address in the post-exit of the standard integration flow.
4.7 Content Transport
The content transport mechanism enables you to reuse content between multiple tenants by exporting it from
one tenant and importing it on another.
Let us consider an example where you have two tenants, test and production. You design and test an
integration flow on the test landscape and it works as expected. Instead of redesigning the integration flow on
the production landscape, you can use the same integration content that you have tested in the test landscape
in the production landscape.
Content transport provides four options to do this:

● Transport using CTS+: In this option, with a single click, you can transport integration content from one
landscape to another through CTS+ system. For more information, see Content Transport Using CTS+
[page 457].
● Transport using Transport Management Service: In this option, with a single click, you can transport
integration content from one landscape to another through Transport Management Service. For more
information, see Content Transport Using Transport Management Service [page 458].
● MTAR Download: In this option, you download a MTAR file from the tenant you want to export integration
content and manually upload this MTAR file to a CTS+ system. For more information, see Content
Transport using MTAR Download [page 459].
● Manual export and import: In this option, you use the Export feature in your workspace to export
integration content from the tenant you want to export integration content and manually import this in the
target tenant. For more information, see Content Transport using Manual Export and Import [page 460].
● Content Transport Using CTS+ [page 457]

● Content Transport Using Transport Management Service [page 458]
● Content Transport using MTAR Download [page 459]
● Content Transport using Manual Export and Import [page 460]
Related Information
Enabling Content Transport [page 455]

Creating HTTP Destination in Solutions Lifecycle Management [page 456]
Content Transport Using CTS+ [page 457]
Content Transport Using Transport Management Service [page 458]
Content Transport using MTAR Download [page 459]
Content Transport using Manual Export and Import [page 460]
4.7.1 Enabling Content Transport
All the tasks mentioned here are one-time activities. It is recommended that the tenant administrator performs
these tasks to facilitate content transport.
Enabling Solutions Lifecycle Management
You should enable the service, Solutions Lifecycle Management in your account. Ensure that you perform this
step in all the accounts where you want to use content transport. This is a one-time activity. You can do that by
performing the following steps:
1. Login to your account in the SAP Cloud Platform.

2. Choose Services Solutions Lifecycle Management .
3. Choose Enable.
Selecting the Transport Mode
The content transport mechanism provides you the flexibility of directly exporting integration content to CTS+
system, or exporting the content as an MTAR file to a local file system. To use either of the modes, you need to
enable the Transport Mode found in the Settings ( (settings)). You can do this by navigating to  (settings)in
the Web UI and then choosing the Transport tab. Based on your requirement select either CTS+ or Transport
Management Service or MTAR Download from the dropdown list.
 Remember
● Please note that this step needs to be performed on the tenant from which you want to export content.
For example, if you are exporting content from your Test tenant, you need to perform this step only in
the Test tenant.
● Transport Settings will be available for you only if you have the role AuthGroup.Administrator assigned
to your account. Please assign the role to your user if you do not see the Transport Settings.
 Tip
If you do not see the Settings( ) options, please contact your tenant administrator for performing this
step.
Next Steps
You have to create HTTP destinations to facilitate connections between your tenant, solutions lifecycle
management service and CTS+/Transport Management Service systems. If you want to use:
● MTAR Download option, create a HTTP destination in Solutions Lifecycle Management for your tenant
management node.
● CTS+ option, create two HTTPS destinations in Solutions Lifecycle Management, one for your tenant
management node (Cloud Integration application) and one for the CTS+ system.

● Transport Management Service option, create three HTTPS destinations in Solutions Lifecycle
Management, one for your tenant management node (Cloud Integration application), another one for
getting oauth tokens, and the third one to the Transport Service backend.
For information on how to create HTTP destinations, see Creating HTTP Destination in Solutions Lifecycle
Management [page 456].
4.7.2 Creating HTTP Destination in Solutions Lifecycle

Management
You must create a destination in solutions lifecycle management as the first step to enable content transport.
Prerequisites
You must enable the Solutions Lifecycle Management service. For information on how to do this, see Enabling
Content Transport [page 455].
Context
You should create a destination in the Solutions Lifecycle Management service to enable import of content into
your target tenant.
Procedure
1. Access Solutions Lifecycle Management by choosing Services Solutions Lifecycle Management .
 Tip
You see the page header as Service: Solutions Lifecycle Management - Overview.
2. Choose Configure Destinations.

3. Choose New Destination.
4. In Destination Configuration section, provide values in fields based on description in table.

Field Description
Name Provide value as CloudIntegration. Please note that

this value is case-sensitive.
Type HTTP
Description You can provide a description for your reference. This field
is optional.
URL Provide the URL of the system that you want a create a
destination to.
If it is SAP Cloud Platform Integration tenant, it will be in

the format: https://<AccountName>-
tmn.hci.int.cn1.hana.ondemand.com/itspaces/. For more
information on exporting the content, see Set Up a Direct
Upload of MTA Archives to a CTS+ Transport Request.
If it is the Transport Management Service, you have to pro

vide the URL of the Transport Management Service sys
tem. For more information, see SAP Cloud Platform Trans
port Management.
Proxy Type Internet
Authentication Basic Authentication
 Remember
Please ensure that the credentials of the user used in
the destination is a member of the SAP Cloud
Platform Integration account from which you want to
transport content. The user should also have role
AuthGroup.IntegrationDeveloper and
IntegrationContent.Transport.
5. Choose Save.
4.7.3 Content Transport Using CTS+
Prerequisites
● You have set the Transport Mode as CTS+ in the tenant Transport settings. For more information, see
Enabling Content Transport [page 455].
● You have created two HTTP destinations on Solutions Lifecycle Management. One for the tenant
management node. For more information, see Creating HTTP Destination in Solutions Lifecycle

Management [page 456]. The other one is for CTS+ system via cloud connector. For more information see,
Integration with Transport Management Tools.
Context
SAP Cloud Platform Integration provides an option to transport integration content directly to CTS+ system.
You can then transport this content from the CTS+ system to your target SAP Cloud Platform Integration
tenant. Here's how you can transport content to CTS+ directly:
Procedure
1. Select the integration package that you want to transport.

2. Choose Transport.
If you do not see the Transport button, ensure that you have the role IntegrationContent.Transport. If you
still do not see the Transport icon, please contact your tenant administrator.
3. In the Transport Comments prompt, provide comments and choose Transport.
 Remember
You are not allowed to use the character "_" in the Transport Comments field.
You see a prompt with the Transport ID. The integration package will be transported to the CTS+ system.
4. To import the content in the target system, follow the steps mentioned here.
4.7.4 Content Transport Using Transport Management

Service
Prerequisites
● You have set the Transport Mode as Transport Management Service in the tenant Transport settings. For
more information, see Enabling Content Transport [page 455].
● You have created two HTTP destinations on Solutions Lifecycle Management, one for the tenant
management node and one for the Transport Management Service system. For more information, see
Creating HTTP Destination in Solutions Lifecycle Management [page 456].

Context
SAP Cloud Platform Integration provides an option to transport integration content directly to Transport
Management Service system. You can then transport this content from the Transport Management Service
system to your target SAP Cloud Platform Integration tenant.
For more detailed information with screenshots on working with Transport Management Service, see Cloud
Integration – Using Transport Management Service for a Simple Transport Landscape on SAP Community.
Here's how you can transport content to Transport Management Service directly:
Procedure

 Remember
You see a prompt with the Transport ID. The integration package will be transported to the CTS+ system.
4. To import the content in the target system, follow the steps mentioned in official documentation for
Transport Management Service .
4.7.5 Content Transport using MTAR Download
Prerequisites
● You have logged into the SAP Cloud Platform Integration web application source and target tenants.
Access the (Design) tab (workspace).

● You have selected MTAR Download as your Transport Mode. For more information, see Enabling Content
Transport [page 455].

Context
You can use the MTAR Download option to download a MTAR file/s of the integration content to be transported
Procedure

 Remember
A file with extension mtar is downloaded to your local file system in the download path configured in your
browser.
4. To import the content in the target system, follow the steps mentioned here.
4.7.6 Content Transport using Manual Export and Import
Prerequisites
You have logged into the SAP Cloud Platform Integration web application source and target tenants. Access the
(Design) tab (workspace).
Context
One of the options to transport content from one tenant to another is to use the Export and Import options for
your integration package. The application imports the integration package to your local file system in the form
of a .zip file. You can import the same file in the target tenant using the Import option.

Procedure
1. Select the integration package that you want to export.

2. Choose Export.
A .zip file is downloaded to the default browser download location on your local file system.
3. Log in to the SAP Cloud Platform Integration web application to which you want to import the content.
Choose .
4. Choose Import.
A new window opens in your file system explorer, allowing you to access your local file system.
5. Navigate to the folder path where the .zip file was downloaded in step 3.
6. Select the file and choose Open.
You see a prompt indicating the successful import of the .zip file. You can see the imported integration
package in the Design tab of your target tenant.
4.8 Importing Content from ES Repository
SAP Cloud Platform Integration enables you fetch content directly from ES repository. This enables you to
reuse the integration content that you already have in your ES repository and avoid the overhead of creating
that content again in the Cloud Integration web application.
To enable this content import feature, you have to configure the connection settings to connect to ES
repository. Since this is an on-premise system, you need to connect to it via Cloud Connector.
For more information on Cloud Connector, see SAP Cloud Platform Connectivity Cloud Connector
documentation.
You can also check out this blog on SAP Cloud Platform Integration community: Importing Message Mapping
from ES Repository in SAP Cloud Platform Integration .

4.8.1 Configuring Connectivity to ES Repository
Prerequisites
You have logged in to SAP Cloud Platform Integration web application.
Context
You have to configure connectivity to the ES Repository from SAP Cloud Platform Integration in the
Settings() tab of your application. You need to have tenant administrator role to access this tab. If you do not
see the icon,  in your application, please contact your tenant administrator to obtain this role or configure
connectivity to the ES Repository.
Procedure
1. Choose .
2. Choose the ES Repository tab.
You see some fields that enable to configure connectivity to ES Repository.
3. Choose Edit. Provide values in fields based on description in table:
Field Description
Name Enter a connection name for your reference. This can be

any value of your choice.
Address Enter the URL configured in the cloud connector that con
nects to the ES Repository.
operations view of this application.
Location ID Enter the location ID that you have specified in your cloud
connector.
4. Choose Save.
Results
This establishes a communication to the ES Repository from your

4.8.2 Importing Mapping Content from ES Repository
Prerequisites
You have configured a connection to ES Repository in the Settings() tab. For more information, see
Configuring Connectivity to ES Repository [page 462].
You have opened the integration flow in which you want to add the integration content and you are editing it.
Context
After you have 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:
● Message mapping
● Operation mapping
● WSDL
 Restriction
If the operation mapping that you are importing contains XSLT references, it will not be imported. The
import process will fail.
Here's how you can do it:
Procedure
1. Choose Resources tab in the integration flow settings.

If you do not see the Resources tab, click the empty space in the integration flow editor. You will see the
Resources tab at the bottom of the integration flow editor.
2. Choose Add Mapping Message Mapping/Operation Mapping depending on the resource you want
to import.
An Add Message Mapping prompt, where you can select the source and select target system details is
displayed.
3. Choose ES Repository as the source. You see the details populated in Name and Address fields. Connect.
A connection is established to the ES Repository. A table with the list of available content is displayed.
4. Choose the content that you want to import and choose Select.
A summary of all the artifacts that will be imported is displayed.
5. Choose Add.
You see a confirmation about all the artifacts that are successfully imported.

4.9 Working with Mapping
This feature enables you to define an association between fields of messages with different structuring. For
example, consider the record Employee and we need to update the employee identification number. In the
sender system, the field name is Employee ID. However, in the receiver system, the same field is called ID.
Similarly, the table illustrates how the same fields might have different identifiers in the source and target
systems.
Source Field Target Field
Employee User
Employee ID ID
Employee Name Name
Employee Surname LastName
Date of Birth DOB
 Caution
If you delete a message mapping step and the mapping definition resource associated with it is not used in
any other message mapping step, then the resource also gets deleted.
Use
You use message mapping, to define an association between fields of messages with different structuring. This
enables the Cloud Integration system to recognize and update the relevant fields in the target systems.
Each message mapping flow step in an integration flow is associated with a mapping definition resource. You
create this definition while adding the mapping step to the integration flow. You can also reuse a definition
resource that you have already created in the same integration flow project.
4.9.1 Message Mapping
Let us consider the example of replicating employee details from one system A to system B. Each employee set
in system A contains name, date of birth, address and phone number. System B also provides similar
functionality. However, the field names are different in system B. In system A, the employee date of birth is
stored in DOB field whereas in system B, the employee date of birth is stored in birthday field. In such
scenarios, you need an artifact that can define what the equivalent fields are in system A and system B
respectively. Message mapping can help you achieve that. Using a graphical editor, you can define a table or a

map (hence the name mapping) which the system uses as a reference to identify equivalent fields in system A
and system B.
Standard and Custom Mapping Functions
In the same scenario, let us assume that the date of birth in system A is in YYYY-MM-DD format. You want to
change the format to DD-MM-YYYY, the format in system B. In this case, you can use a mapping function that
will transform the data into the format that you want, which in this case is DD-MM-YYYY.
The mapping editor provides some standard functions like Arithmetic, Boolean, Constants, Conversions and
Date. If you are unable to achieve the desired transformation using standard functions, you can create a
custom function by choosing (create script) to create a custom mapping function by manually entering the
script or choose (add script file) to upload a script file that contains the custom mapping function.
Testing Message Mapping
The mapping editor provides two ways of testing message mapping:
1. Simulate - for testing the entire mapping XML.

2. Display Queue - for testing a specific node of the XML.
1. Simulate: The mapping simulate option enables you to test the entire mapping structure. The system will
show if the mapping contains any errors, giving you a chance to fix these errors before deploying the
integration flow. Once you complete the mapping, you can choose Simulate to run a simulation of the mapping.
2. Display Queue: The display queue option enables you to test the mapping of a specific node. In the Mapping
expression area, provide a Test Input File and choose (Display Queue) to display the simulated output for the
provided test input file.
 Note
● Even if the integration flow is not in edit mode you can execute simulate and display queue test. You can
hence perform the tests for configure only content as well.

● You can refer to input xml file uploaded for simulation, for display queue also, and vice versa.
4.9.1.1 Creating Message Mapping
Prerequisites
You have added a message mapping step in the integration flow and defined the message paths.
Context
In this procedure, you need to understand the different aspects of creating a message mapping step and the
associated mapping definition (mmap) file.
You add a mapping step in the integration flow. However, you should also assign a mapping definition or mmap
file that contains the actual mapping details. Here's a diagram that illustrates a typical workflow for creating or
adding mmap files.

To familiarize yourself with the various features and behavior of elements in the mapping viewer, see the
screenshot below:
Section in Screenshot Description
1 Represents the source structure.
2 Represents the target structure.
3 If any of the entities (source or target) are not visible, a

dotted line indicates the calculated position of the invisible
entity.
4 Solid lines represent visible source and target entities.
5 If you select a line, both source and target entities come to

the center in the table, and the line becomes solid.
6 This section represents the functions of the selected

mapping.
7 The Search option enables you to search for a particular

entity within a source or target structure.
The search result highlights the nodes in the structure that

match the search text that are in the visible area, and also
displays the number of occurrences of that particular entity
within the structure.
You can view the other occurrences by clicking the  (Up)

or  (Down) button.
8
● : This button maps all the entities of the selected
node from the source structure with the target
structure.
● : This button clears all the mapping.

Section in Screenshot Description
● : This button expands the entire source or target

structure.
● : This button collapses the whole structure.
● : This button allows you to edit the entities within the
structure.
9 The Functions pane lists the standard functions that can be

used in the Message Mapping expression.
You can also create a new script  or assign an existing

script  to the mapping expression.
Procedure
1. If you want to use an existing mapping definition (mmap file), select the mapping step and choose
Processing Select and select the mapping definition file.
2. If you want to create a new mapping definition (mmap file), perform the following substeps:
a. Select the mapping step and choose  (Create).
b. Specify a name for the mmap file and choose Create.
c. Add source and target messages.
External reference in WSDL and schema are now supported in Message Mapping with resources.
Reference to the remote reports are not supported.
Example: <?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="EmployeeDetails" targetNamespace="http://com.sap.copy.com"

xmlns:bs="http://B.com" xmlns:ds="http://D.com" xmlns:emp="http://Employee.com"
xmlns:p1="http://demoDisplayQueue" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:documentation/>
<wsdl:types>
<xsd:schema targetNamespace="http://com.sap.copy.com" xmlns="http://com.sap.copy.com"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:import namespace="http://Employee.com" schemaLocation="../../empWsdl/Employee.wsdl"/>
<xsd:import namespace="http://B.com" schemaLocation="./mySchema/B.xsd"/>
<xsd:import namespace="http://D.com" schemaLocation="mySchema/D.xsd"/>
<xsd:complexType name="Employee">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/VersionID">abaed5bfea7111e4c82400000cbe4342
</xsd:appinfo>

</xsd:annotation>
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="EmpAddress" type="Address"/>
<xsd:element name="Id" type="emp:Employee"/>
<xsd:element name="Name" type="bs:B"/>
<xsd:element name="Dept" type="ds:D"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="Address">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="1" name="Line" type="LineText"/>
</xsd:sequence>
<xsd:attribute name="shelly" type="xsd:string" use="optional"/>
</xsd:complexType>
<xsd:complexType name="LineText">
<xsd:sequence>

</xsd:sequence>
</xsd:complexType>
<xsd:element name="EmployeeDetails" type="Employee"/>
</xsd:schema>
</wsdl:types>
</wsdl:definitions>
d. Drag fields from the source to the required field in the target to create a mapping.
e. If you want to perform an operation, add the required function in the Mapping Expression screen area.
3. You can create your own custom mapping function. Here's how:
a. In the Mapping Expression screen area, choose .

4.9.2 Creating Value Mapping
Prerequisites
● You are in the workspace (Design tab).
Context
You use the value mapping artifact to represent multiple values for a single object. For example, a product in
Company A is referred by the first three letters as 'ID The same product is referred in Company B by product
code ''0100IDE". When Company A sends message to Comapny B, it needs to take care of the difference in the
representations of the same product. So Company A defines an integration flow with a mapping element that
contains reference to the value mapping definition. You create such value mapping groups in a Value Mapping
artifact.
Procedure
1. Choose the integration package where you want to add the Value Mapping artifact and choose Edit.
2. Choose Artifacts Add Value Mapping .

3. If you want to upload a value mapping artifact from your local file system, perform the following substeps:
a. Choose Upload Browse .

b. Navigate to the location where the artifact file is located and upload it.
c. Enter values in mandatory fields, & optional fields if required. Choose OK.
You see a message confirming that the value mapping artifact is created successfully.
4. If you want to create a value mapping artifact, perform the following substeps:
a. Enter the Name for your value mapping artifact.
b. If required, enter values in the optional fields and choose OK.
You see a message confirming that the value mapping artifact is created successfully. Configure the value
mapping artifact by referring to Configuring Value Mappings [page 471].

4.9.3 Configuring Value Mappings
You use this procedure to perform various functions in a value mapping.
Prerequisites
● You have created a value mapping artifact. For more information, see Creating Value Mapping [page 470].
● You are editing the value mapping artifact.
Context
You create a value mapping artifact to act as a bi-directional look up table. Value mapping offers the distinct
advantage of giving you bi-directional look up capabilities which is used quite often in productive mapping
scenarios. You can also import CSV files exported from process integration (PI) systems in your value mapping.
Procedure
1. If you want to import a CSV file that contains value mappings, choose Import and select the CSV file you
want to import.
2. In the Bi-Directional mapping section, choose Add to add a bi-directional mapping.
3. In the Value mappings for section, choose Add to add a value mapping.
There are scenarios in which values in the Source Agency are unique but the values in the Target Agency
are repetitive for different source values. For such cases, the default values are generated and auto-
assigned by the application. In case you want to modify the default value, then choose the Default Values
tab and select the Target Value to set the default value for the Source agency.
4. Provide values for the agency and identifier in the respective fields.
5. Choose to remove a bi-directional or value mapping.

You can choose Delete All to remove all bi-directional and value mappings from the respective sections.
6. Choose Save to keep the changes.
7. Choose Save as version to retain a copy of the current artifact.
You can view the version history of an artifact by choosing the current version mentioned along with it.
8. Choose Cancel to revert the changes.
 Note
If you edit a web edited value mapping in eclipse, then you get a default value for 1:N, M:,1 and M:N
mappings. SAP recommends that all groups should contain only one agency identifier and value pair.
Some of the function names in web UI differ from the ones in Eclipse.

Editing of the Value Mapping will no longer be possible if it is configured and saved by choosing the
Configure option from the Actions  button provided for the Value Mapping under the Artfiacts tab.
Deployment of a Value Mapping with configuration details copied from another deployed Value
Mapping is not recommended.
4.9.3.1 Formatting Guidelines for CSV Files used in Value

Mapping
SAP Cloud Platform Integration supports importing of CSV files exported from process integration (PI)
systems into value mapping. This allows you to reuse the value mappings from your PI system and save time.
The CSV files that can be imported to the value mapping should adhere to the same formatting guidelines as
the CSV exported from PI systems. Here's a typical example of a valid CSV file that can be imported into value
mapping:
 Sample Code
,Country1|Receiver1,Country1|Code1
Receiver_US,N75_AAEX_FileSystem_XiPattern2|,US
Receiver_DE,N75_AAEX_FileSystem_XiPattern1|,DE
Receiver_DE,N75_AAEX_FileSystem_XiPattern3|,UK
From the example above, we can infer the following guidelines for a CSV file that can be imported in value
mapping:
● Only comma (,) can be used as the delimiter.

● The Agency ← → Identifier is separated by the pipe (|) character.
4.9.4 Create XSLT Mapping
You perform this task to assign XSLT mapping that is available in your local workspace.
Context
You perform this task to assign XSLT mapping that is available in your local workspace.
Procedure
1. Click on Edit.

2. In the palette, choose XSLT Mapping.
3. In the General tab enter details for Name field.
4. In the Processing tab, select either Integration Flow or Header for mapping Source field.
a. If you select integration flow as source, then click on Select to choose the xslt or xsl file from Resource
folder or file system.
 Note
○ To view or modify content of xslt mapping in the editor, click on the resource name in the
Resource field.
○ For XSLT mapping, you can select the output format of the message to be either string or
bytes from the Output Format field.
b. If you select header as source, then enter name for the header in the Header Name field.
 Note
To assign xslt mapping for partner directory, the valid format for value of header name is
pd:<Partner ID>:<Parameter ID>:<Parameter Type>, where the parameter type is either
Binary or String. For example, the correct header name is pd:SenderABC:SenderXSD:Binary.
5. Save or deploy the changes.
4.10 Migrate to New Version
New features are introduced through new versions of the components. To consume this new feature you must
migrate to new version.
Prerequisites
● You have connected to the Web application.

● Your user is assigned with the integration developer role.
● You have accessed the customer workspace.
Context
Once you migrate, old fields will be retained with same values and new fields are populated with default values.
If default value is not present for the mandatory field, then you must add the value.
 Note
If you want to view the older version, then you must save the integration flow as a version before migrating
to new version.

Migration feature is available for the following components:
● Integration flow configuration

● Integration process
● Local integration process
 Caution
Note relevant for the case when the integration flow contains an older adapter versions that does not
support yet HTTP session handling:
If you like to migrate an integration flow to a new version that supports HTTP session handling and the
original integration flow (to be migrated) contains an earlier version of a receiver adapter that doesn’t
support HTTP session handling yet, you might run into a version conflict. In that case, the following error is
displayed:
Version <adapter component version> is not supported with integration flow

version <target version of integration flow>, remodel the adapter with new
version.
The following adapter types can be affected by this problem: HTTP, SOAP, or IDoc receiver adapter.
What you can do:
● Re-model the adapter in the integration flow migrated to the new version (as proposed in the error
message).This means that you need to re-create the related communication channel.
● Revert back to the earlier integration flow version. To do that, you need to make sure that you save the
original integration flow as version prior to migrating it to the new version.
For additional information on version migration of integration flow components, you can check this SAP
community blog: Versioning & Migration of Components of an Integration Flow in SAP Cloud Platform
Integration’s Web Application .
Procedure
1. Select an integration flow component.

2. Click on the Migrate button.
 Note
Migration option will be available only if the selected component has the highest version in the
component.
3. Click on OK for confirmation.
 Note
You can revert to previous version after migrating also, by executing the following steps:
1. Go to package view.
2. Click on Draft version.
3. Click on the timer icon to revert back to previous version.

4.11 Specify the Runtime Configuration
With Runtime Configuration you can specify general properties of the integration flow.
Context
Procedure
1. Open the integration flow and select the graphical area outside the integration flow model.
2. Choose the Runtime Configuration tab.
3. Specify the following properties.
With the property Product Profile you choose the target runtime environment for the integration content
designed with the application.
A product profile defines a set of capabilities for Cloud integration content design supported by a specific
target integration platform. For example, a specific product profile supports the configuration of a specific
set of adapter types and integration flow steps.

Runtime Configuration Properties
Namespace Mapping Map a prefix to a namespace at runtime.
Enter a namespace-prefix pair with a format

xmlns:<prefix>=<namespace>.
This parameter is required for elements such as the con

tent-based router, content modifier or content filter that
can use namespaces in their configuration. You can either
enter the namespace-prefix pair or the tool automatically
fills the namespace-prefix pair whenever a lookup is per
formed for the assigned WSDL.
You can also enter multiple namespace-prefixes as shown

in the example: xmlns:test=http://sapcd.com/
testABC;xmlns:test2=http://sapcd.com/
testPQR.
 Note
xmlns:ns0=https://
Here, ns0 is the prefix and https://

is the namespace. That way, in a router, you can spec
ify the routing condition for an XML message as:
/ns0:HCIMessage/
SenderID='Sender01'
Message Processing Log Configure the log level to display in the Monitoring editor.
Select one of the log levels from the Message Processing

Log dropdown.
○ All Events: Allows all messages to be logged and dis

played
○ Error Events: Allows only error messages to be logged
and displayed
○ No Logging: Hides logging information

Allowed Header(s) Specify the headers to be retained when the incoming

message is processed.
Enter one or more names of headers by separating them

with pipe (|).
 Note
If you want to enter several headers with similar
names, use wildcards to make the entering faster.
The wildcards are regular expressions, such as .*

and ?.? substitutes exactly one non-space charac
ter..* substitutes zero or more non-space charac
ters.
Example: You want to enter the headers A, A1, A2, A3.
Instead of entering all of them singularly, simply enter

A .*. This will allow all headers starting with A.
In general, headers used by the runtime components are

retained and other headers are removed during message
processing. This field is useful when you need specific
header information along with the message body.
For inbound SSL connections (when a sender calls SAP

Cloud Platform Integration), senders have to authenticate
against a load balancer component. The load balancer
sets the following message header fields:
SSL_CLIENT_CERT (contains the Base64-encoded
sender client certificate) and SSL_CLIENT_USER. En
tering these values in the Allowed Header(s) field, allowes
you to forward these headers during message processing.

HTTP Session Handling Choose one of the following options:
○ None
Session handling is switched off
○ On Exchange
Each exchange corresponds to a single session (use
this option for stateful services)
○ On Integration Flow
Only one session will be used across the whole inte
gration flow (only use this option for stateless serv
ices)
 Note
Once an HTTP session has been initialized, there
is usually no further authentication for the dura
tion of the session (one of the advantages of us
ing sessions). This means that all further HTTP
requests on that server are processed in the con
text of the user that was logged on when the ses
sion was initialized. If, however, this behavior
does not meet your requirements (for example,
the user is dynamic and can change from request
to request), you can select either an exchange
session scope (if the user remains the same for
at least the processing of a single message) or no
session.
 Note
SuccessFactors (OData V4) and SuccessFactors
(REST) adapters do not support HTTP session
handling.
Related Information


4.12 Configure Externalized Parameters of an Integration
Flow
Prerequisites
● You have connected to the Web application.

● Your user is assigned with the integration developer role.
● You have accessed the customer workspace.
Context
SAP Cloud Platform Integration Web application allows you to configure an integration flow individually or
multiple integration flows at once. You can configure the runtime, error configuration and also provide a
description about the integration flow.
 Note
If you want timer or SuccessFactors sender adapter scheduler to be available in quick configuration, you
need to externalize these parameters while creating the integration content.
If you want SucessFactors sender adapter scheduler to be available in quick configure for existing
integration flows, you should externalize the scheduler parameters and republish the integration package.
You must click on the participant’s name of sender and receiver elements, to view the header and property
information. Also, you must drag and drop message flow over the participant's name, to assign
communication channels.
 Restriction
You cannot use quick configure option for integration flows in Monitor and Discover tab pages. You can only
configure integration flows in your customer workspace (Design tab page).
Procedure
1. In Design tab page, select the integration package that contains the integration flow you want to configure.
2. Choose Package content.
You see an overview of all the artifacts available in the selected integration package.
3. In the Actions column for the integration flow you want to configure, choose Configure .

4. Provide the relevant details in Sender, Receiver and More tab pages.
 Note
For more information, see Configure Adapters in Communication Channels [page 492].
5. Select relevant details of externalised components in More tab, to view externalised values for integration
flow configuration or integration flow steps or local integration process or integration process.
a. Select Type of component.
 Note
You can also view all parameters of the component using All Parameters option.
b. Select Name[ID] of component.
You cannot select name for integration flow configuration.

6. If you want to save this configured integration flow as a version, choose Save as version and specify the
version details.
7. If you want to save or deploy this integration flow, choose the appropriate option.
 Note
You can use error configuration to handle errors when message processing fails at runtime. You select
an error handling strategy based on the descriptions below:
Error Handler Strategies
Option Description
None No error handling strategy is used if a message exchange could
(default setting) not be processed .
Raise Exception (Deprecated) If a message exchange could not be processed and there is an
IDoc or SOAP ( SAP RM) channel in the integration flow, an ex
ception is raised to the sender.
Raise Exception If a message exchange could not be processed, an exception is

raised to the sender.
Related Information
Externalize Parameters of an Integration Flow [page 482]

Define a Timer Start Event [page 689]

4.13 Configure Multiple Integration Flows
Prerequisites
You have copied the integration package to your workspace
Context
SAP standard integration packages offer a feature where you can configure multiple integration flows that
connect to the same system at once. You need to enter the configuration details only once in the mass
configuration screen. All the integration flows that connect to that system instance are updated with the
details. This eliminates the need for individually entering the configuration details in each integration flow.
For example, consider a scenario in which all the integration flows connect to the same instance of SAP ERP.
The configuration details like Host, Port and Client are the same for all the integration flows. Once you specify
these details in the mass configuration screen, the application updates these details in all the relevant
integration flows. This simplifies the task of configuring multiple integration flows that share common system
properties.
 Remember
● The system consolidates field names into a single section only if they match exactly across all the
integration flows you select for configuration. These field names are sender and receiver's system and
authentication details.
● You can also configure authentication details during mass configuration.
● Configuring multiple integration flows is only supported for integration flows with SOAP and IDOC
adapters, version 1.0 and 1.1..
Procedure
You use this procedure to configure multiple integration flows.

1. Launch SAP Cloud Platform Integration Web application using the application URL.
2. Choose Design .
3. Select the package that contains the integration flows that you want to configure and choose Package
content.
4. In the Artifacts screen area, select the integration flow(s) you want to configure.
5. Choose Actions Configure .

 Note
You can also download the artifacts to your local folder by choosing Download instead of Configure.
The system displays the externalized system properties pertaining to the selected integration flows that
you want to configure. If there are common properties, the application displays them as a single entry.
6. If you want to save the configuration, choose Save.
7. If you want to deploy the integration flows, choose Deploy.
4.14 Externalize Parameters of an Integration Flow
Context
Use the Externalize feature to declare a parameter as a variable and reuse it across multiple components in the
same integration flow. You can define multiple parameters for each field, but you can only assign a single value
for each parameter. If a value contains common strings that can be reused, then you can split the value and
assign the strings to different parameters.
 Note
● Do not use text editors that does not support text formatting, for pasting content to text area
attributes.
● Do not use the following characters while defining a parameter in an integration flow:
○ &
○ <
○ >
○ "
○ '
 Example
Assume that in an integration flow you are configuring a communication channel with HTTPS sender
adapter. Here let us externalize the Address field, by defining a parameter and value. In the externalization
dialog box, for the Address field, you define a parameter as {{HostPort}} and its value as https://
localhost:8080/dir. Now you have declared a variable for Address parameter that can be reused in
different components in the same integration flow.
Notice that you can assign only one value to a parameter. But if you have a requirement to reuse a specific
string in a value, then we recommended to split the value into multiple strings and define them to individual
parameters as shown in the table.

Define Parameter Define Value
{{Host}} localhost
{{Port}} 8080
 Note
You cannot reuse the same parameter name more than once for the same field, and defining multiple
parameters for the same field or column are not supported for tables.
The integration flow must be in Edit mode to perform the steps.
To create a new parameter in the property sheet of an integration component, perform the
following steps:

2. In the relevant component field define a parameter in curly brackets, and press Enter .
 Example
{{parameter_1}}
○ To externalize the checkbox, choose Externalize and based on the choice (select or deselect) define a
parameter.
○ To externalize the dropdown, choose Externalize and define a parameter for the specific dropdown
value.
3. Choose the <Define Value> tag, and provide a value for the parameter in the Define Value dialog box.
4. Choose OK to save the changes.
 Note
You can update a value from the property sheet for any externalized parameter.
 Note
You can only remove the externalization of a field by manually deleting the parameter from the
Externalization dialog box.
To create a new parameter for a cell in the table, perform the following steps:
1. In the relevant table cell, enter the parameter in curly brackets and press Tab .
 Note
○ If you need to remove the externalization of a parameter click the delete icon.
○ You are not allowed to split a value into multiple strings.

To create a new parameter in the Externalization Editor, perform the following steps:
2. Choose Externalize to define a new parameter.
3. Enter the parameter in curly brackets in the relevant field and press Tab .
 Example
{{Parameter_1}}
 Note
You can remove the externalization of a field by manually removing the parameter.
To externalize text area, perform the following steps:

2. Choose Externalize to define a new parameter and value for the text area.
3. Enter the parameter in curly brackets in the field that shows <Define Parameter> and press Tab .
 Example
{{TextBody}}
 Note
Plain text entered in this field is considered as a value that cannot be modified in the property sheet.
To reuse an existing externalized parameter, perform the following steps:

2. Choose Externalize to reuse a parameter.
3. Enter the parameter that you want to reuse in curly brackets in the relevant field.
 Example
{{Parameter}}.
 Note
By typing {{ in the parameter field, the auto-suggest displays existing parameters.
4. To edit the parameter value, choose the <Define Value> tag.

5. Enter the new value of the parameter in Update Value.
 Note
Modifying the parameter value may change the configuration of other integration flow components
that use the same parameter.

To view and edit externalized parameters, perform the following steps:

1. Choose the Externalized Parameters tab from the Integration Flow section, and the table displays all the
used and unused externalized parameters.
2. Click the relevant Value for editing an existing parameter value.
 Note
Remove Unused option allows you to permanently remove the parameters that are not consumed by
any components of an integration flow.
4.15 Configure Integration Flow Components
SAP Cloud Platform Integration Web application allows you to configure integration flow components in an
editor.
4.15.1 New and Improved Integration Flow Editor for SAP

Cloud Platform Integration
SAP Cloud Platform Integration provides a new version of integration flow editor in the web application. The
new editor comes with a host of enhancements such as:
Improved Look and Feel
You will notice that the new editor provides an improved look and feel when you are viewing or editing
integration flows.

Zoom Capabilities
You can easily zoom in and out of the editor with your mouse scroll or the '+' and '-' action buttons on the top
right of the editor. This feature is particularly helpful when you have to edit large and complex integration flows.

Action Buttons for Integration Flow Steps
All the integration flow steps and adapters provide quick action buttons that help you to connect, delete, view
information, or more such quick actions. This is very helpful in quickly building an integration flow. For example,
when you wanted to delete an adapter in the old WebUI, you had to select the channel and then select the 
(Delete) icon in the palette. This process was time consuming and not very convenient. This process just takes
two clicks with the new editor: you select the channel and choose the  icon.
Quick Buttons
In the old editor, the quick buttons to connect, delete or see technical information were made available when
you hover the mouse pointer over the component, but in the new editor, you need to select the component to
access them

Overview Mode
When you have a large integration flow, you will need a visualization that will help you see the entire integration
flow and also navigate to a specific area in that flow. The overview mode provides you that option. By choosing
the dedicated button on the bottom right of the screen, you get a bird's eye view of the integration flow.

Modelling Constraints (Important)
The new editor also has some constraints to help you ensure that you do not make a mistake while modeling an
integration flow. For example, the editor will not allow you to add integration flow steps outside the integration
process.
The editor also prevents you from adding multiple incoming messages to integration flow steps. Currently, it is
not supported for Request Reply, Content Enricher and Send steps.
Auto-Save
Consider a scenario where you have existed the integration editor while modelling an integration flow or
encountered a sessions timeout. In both these cases, you have not saved the changes made to the integration
flow. To identify an unsaved integration flow artifact, you can find the Unsaved Changes text appearing under
the name of the aritifact.
In such scenarios, the Auto-Save functionality helps you recover the unsaved version of the integration flow.
The next time when you open the specific integration flow in the CPI WebUI, a pop-up appears asking if you
would like to recover the unsaved integration flow. If you choose Recover the application restores the
integration flow you were working on before. If you do not want to keep the version that you were working
before then choose Discard.
This feature prevents you from losing work and by default the application saves your work for every 60
seconds.
Copy and Paste Adapter configurations
You can copy and paste adapter configurations within an integration flow.
Copy and paste only works between two sender adapters and two receiver adapters. Copy of a sender adapter
details to a receiver adapter (or vice versa) is not supported.
For example, to copy and paste the configuration between two receiver adapters, navigate to the Design tab,
and under your integration package, open an artifact in Edit mode. Select one of the receiver adapters and

choose the Copy  button to copy its configuration details. Choose another receiver adapter and click on
Paste  button. The configuration details are copied into this receiver adapter.
 Note
● The paste function overwrites any existing configuration on the adapter including its type.
● The copy and paste only works between two sender adapters and two receiver adapters. Copy of a
sender adapter details to a receiver adapter or the vice versa, is not supported.
● This Copy-Paste feature is available only for adapter within the communication channel.
4.15.2 Assign Sender and Receiver Components
Context
Procedure
1. Open the integration flow in the editor.
2. From the palette, choose Participants ( ) and then Sender or Receiver.

3. Only relevant when you assign a Sender: For certain adapter types, you need to specify the inbound
authorization.
To do this, select the configuration interface of the associated sender adapter.
In case the Authentication Type option is still displayed for the sender participant, you might have created
this integration flow shape some time back or you have selected a certain product profile where inbound
authorization is still be performed per sender participant.
In that case, either proceed with the following step or create a new sender participant shape (and, in that
case, continue configuring the authorization option in the associated sender channel).
4. When you specify the Authentication Type as part of the Sender, consider the following.
You have the following options to authenticate the sender.

○ Role-based Authentication
Select this options if you like to configure one of the following use cases:
○ Basic authentication
○ Client certificate authentication with certificate-to-user mapping
○ Client Certificate Authentication

Select this option if you like to configure the use case that the permissions of the sender are to be
checked on the tenant by evaluating the distinguished name (DN) of the client certificate (sent by the
sender).
Choose Add… to browse and add an authorized client certificate or enter the Subject DN and Issuer DN
manually.
Which option you choose, depends on the combination of authentication and authorization option you like
to configure for inbound calls.
4.15.3 Assign Adapter to Communication Channel
Prerequisites
● You have logged on toSAP Cloud Platform Integration web application.

● You are editing an integration flow.
Context
You must create a communication channel between SAP Cloud Platform Integration and the sender/receiver
system to facilitate communication between them.
 Note
You must click on the participant’s name of sender and receiver elements, to view the header and property
information. Also, you must drag and drop message flow over the participant's name, to assign
communication channels.
You use this procedure if you want to change the adapter assigned to the communication channel in integration
flows.
Procedure
1. Access SAP Cloud Platform Integration web application by launching the URL provided by SAP.
2. Choose Design .
3. Select the integration package that contains the integration flow or create a new
4. Select the integration flow and choose Edit.

 Note
In the case of OData service artifacts in integration packages, you have to edit the OData service
artifact in order to edit the required integration flow.
5. If you want to define sender channel, choose Sender and drag the pointer to Start.
 Note
In the case of integration flows in OData service artifacts, you cannot change the OData sender
adapter.
6. If you want to define receiver channel, choose End and drag the pointer to Receiver.
7. In Adapter Type dialog, select the adapter you want to assign. Choose the message protocol that you want
to use, if prompted.
8. Save or deploy the changes after configuring the adapter and other integration flow elements.
 Note
In the case of integration flows in OData service artifacts, you can save the integration flow and deploy
the OData service.
4.15.4 Configure Adapter in Communication Channels
You should configure the adapters assigned to communication channels before deploying the integration flow.
The following adapter types are available:
Adapter
Feature Description
Ariba Connects an SAP Cloud Platform tenant to the Ariba Network. Using this adapter, SAP and non-SAP
cloud applications can receive business-specific documents in commerce eXtensible Markup Lan
Sender adapter
guage (cXML) format from the Ariba network.
The sender adapter allows you to define a schedule for polling data from Ariba.
Ariba Connects an SAP Cloud Platform tenant to the Ariba network. Using this adapter, SAP and non-SAP
cloud applications can send business-specific documents in commerce eXtensible Markup Language
Receiver adapter
(cXML) format to the Ariba network.
AS2 Enables an SAP Cloud Platform tenant to exchange business-specific documents with a partner
through the Applicability Statement 2 (AS2) protocol.
Sender adapter
A license for SAP Cloud Platform Enterprise Edition is required to use this feature.
Sender adapter: Can return an electronic receipt to the sender of the AS2 message (in the form of a
Message Disposition Notification (MDN))

Feature Description
AS2 Enables an SAP Cloud Platform tenant to exchange business-specific documents with a partner
through the Applicability Statement 2 (AS2) protocol.
Receiver adapter
A license for SAP Cloud Platform Enterprise Edition is required to use this feature.
AS4 Enables an SAP Cloud Platform tenant to securely process incoming AS4 messages using Web Serv
ices. The AS4 sender adapter is based on ebMS specification that supports the ebMS handler con
Sender adapter
formance profile.
● Supports one-way/push message exchange pattern (MEP).

● Supports signature verification and decryption of the message.
● Generates receipts after processing the incoming AS4 message.
● Allows you to restrict the size limit for body and attachment of an incoming message.
AS4 Enables an SAP Cloud Platform tenant to establish connection between any two message service han
dlers (MSHs) for exchanging business documents. The AS4 receiver adapter uses the Light Client
Receiver adapter
conformance policy and supports only message pushing for the sending MSH and selective message
pulling for the receiving MSH.
● Supports one-way/push message exchange pattern (MEP) that involves transfer of business
document from sending MSH to receiving MSH.
● Supports one-way/selective-pull message exchange pattern (MEP) that involves the receiving
MSH initiating a selective pull request to the sending MSH. The sending MSH responds by send
ing the specific user message.
● Supports storing and verification of receipts.
Facebook Enables an SAP Cloud Platform tenant to access and extract information from Facebook based on
certain criteria such as keywords or user data.
Receiver adapter
Using OAuth, the SAP Cloud Platform tenant can access resources on Facebook on behalf of a Face
book user.
HTTPS Establishes an HTTPS connection between an SAP Cloud Platform tenant and a sender system.
Sender adapter
HTTP Establishes an HTTP connection between an SAP Cloud Platform tenant and a receiver system.
Receiver adapter ● Supports HTTP 1.1 only (target system must support chunked transfer encoding and may not rely
on the existence of the HTTP Content-Length header)
● Supports the following methods: DELETE, GET, HEAD, POST, PUT, TRACE
Method can also be determined dynamically by reading a value from a message header or prop
erty during runtime.
IDoc Allows an SAP Cloud Platform tenant to exchange Intermediate Document (IDoc) messages with a
sender system that support communication via SOAP Web services.
Sender adapter
A size limit for the inbound message can be configured for the sender adapter.

Feature Description
IDoc Allows an SAP Cloud Platform tenant to exchange Intermediate Document (IDoc) messages with a re
ceiver system that support communication via SOAP Web services.
Receiver adapter
JDBC Allows an SAP Cloud Platform tenant to connect to a JDBC (Java Database Connectivity) database
and to execute SQL commands on the database.
Receiver adapter
JMS Enables asynchronous messaging by using message queues.
Sender adapter The sender adapter consumes messages from a queue. The messages are processed concurrently.
To prevent situations where the JMS adapter tries again and again to process a failed (large) message,
you can store messages (where the processing stopped unexpectedly) in a dead-letter queue after
two retries.
Certain constraints apply with regard to the number and capacity of involved queues, as well as for the
headers and exchange properties defined in the integration flow before the message is saved to the
queue (as described in the product documentation).
JMS Enables asynchronous messaging by using message queues.
Receiver adapter The receiver adapter stores messages and schedules them for processing in a queue. The messages
are processed concurrently.
LDAP Connects an SAP Cloud Platform tenant to a Lightweight Directory Access Protocol (LDAP) directory
service (through TCP/IP protocol).
Receiver adapter
Supported operations: Modify distinguished name (DN), Insert
SAP Cloud Connector is required to connect to an LDAP service. The LDAP adapter supports version
2.9 or higher of the SAP Cloud Connector.
Mail Enables an SAP Cloud Platform tenant to read e-mails from an e-mail server.
Sender adapter To authenticate against the e-mail server, you can send user name and password in plain text or en
crypted (the latter only in case the e-mail server supports this option).
You can protect inbound e-mails at the transport layer with IMAPS, POP3S and STARTTLS.
For more information on possible threats when processing e-mail content with the Mail adapter, see
the product documentation.
Mail Enables an SAP Cloud Platform tenant to send e-mails to an e-mail server.
Receiver adapter To authenticate against the e-mail server, you can send user name and password in plain text or en
crypted (the latter only in case the e-mail server supports this option).
● You can protect outbound e-mails at the transport layer with STARTTLS or SMTPS.
● You can encrypt outbound e-mails using S/MIME (supported content encryption algorithms:
AES/CBC/PKCS5Padding, DESede/CBC/PKCS5Padding).

Feature Description
OData Connects an SAP Cloud Platform tenant to systems using the Open Data Protocol (OData) protocol in
either ATOM or JSON format (only synchronous communication is supported).
Sender adapter
Supported versions: OData version 2.0
● The adapter receives incoming requests in either ATOM or JSON format.

● Supported operations: Create (POST), Delete (DELETE), Query (GET), Read (GET), Update (PUT)
Using the GET or POST method, the sender adapter can also invoke operations that are not cov
ered by the standard CRUD (Create, Retrieve, Update, and Delete) methods (function import).
OData Connects an SAP Cloud Platform tenant to systems using the Open Data Protocol (OData) protocol in
either ATOM or JSON format (only synchronous communication is supported).
Receiver adapter
Supported versions:
● OData version 2.0

Supported operations: Create (POST), Delete (DELETE), Merge (MERGE), Query (GET), Read
(GET), Update (PUT), Patch (PATCH)
● OData version 4.0
Supported operations: Create (POST), Query (GET), Update (PUT)
ODC Connects an SAP Cloud Platform tenant to SAP Gateway OData Channel (through transport protocol
HTTPS).
Receiver adapter
Supported operations: Create (POST), Delete (DELETE), Merge (MERGE), Query (GET), Read (GET),
Update (PUT)
ProcessDirect Connects an integration flow with another integration flow deployed on the same tenant.
Sender adapter An integration flow with ProcessDirect sender adapter (as consumer) consumes data from another
integration flow.
N:1 cardinality of producer and consumer integration flows is supported.
ProcessDirect Connects an integration flow with another integration flow deployed on the same tenant.
Receiver adapter An integration flow with ProcessDirect receiver adapter (as producer) sends data to another integra
tion flow.
N:1 cardinality of producer and consumer integration flows is supported.
RFC Connects an SAP Cloud Platform tenant to a remote receiver system using Remote Function Call
(RFC).
Receiver adapter
RFC is the standard interface used for integrating on-premise ABAP systems to the systems hosted
on the cloud using SAP Cloud Connector.
The adapter supports SAP NetWeaver, version 7.31 or higher.

Feature Description
SFTP Connects an SAP Cloud Platform tenant to a remote system using the SSH File Transfer protocol to
read files from the system. SSH File Transfer protocol is also referred to as Secure File Transfer proto
Sender adapter
col (or SFTP).
Supported versions:
SSH version 2 (as specified at http://tools.ietf.org/html/rfc4251 ), SSH File Transfer Protocol

(SFTP) version 3 or higher
SFTP Connects an SAP Cloud Platform tenant to a remote system using the SSH File Transfer protocol to
write files to the system. SSH File Transfer protocol is also referred to as Secure File Transfer protocol
Receiver adapter
(or SFTP).
Supported versions:
SSH version 2 (as specified at http://tools.ietf.org/html/rfc4251 ), SSH File Transfer Protocol

(SFTP) version 3 or higher
SOAP SOAP 1.x Exchanges messages with a sender system that supports Simple Object Access Protocol (SOAP) 1.1
or SOAP 1.2.
Sender adapter
The message exchange patterns supported by the sender adapter are one-way messaging or request-
reply.
The adapter supports Web services Security (WS-Security).
SOAP SOAP 1.x Exchanges messages with a receiver system that supports Simple Object Access Protocol (SOAP) 1.1
or SOAP 1.2.
Receiver adapter
The adapter supports Web services Security (WS-Security).
SOAP SAP RM Exchanges messages with a sender system based on the SOAP communication protocol and SAP Re
liable Messaging (SAP RM) as the message protocol. SAP RM is a simplified communication protocol
Sender adapter
for asynchronous Web service communication that does not require the use of Web Service Reliable
Messaging standards.
SOAP SAP RM Exchanges messages with a receiver system based on the SOAP communication protocol and SAP
Reliable Messaging (SAP RM) as the message protocol. SAP RM is a simplified communication proto
Receiver adapter
col for asynchronous Web service communication that does not require the use of Web Service Relia
ble Messaging standards.
SuccessFactors Connects an SAP Cloud Platform tenant to a SuccessFactors sender system using the REST message
REST protocol.
Sender adapter The adapter supports operation GET

Feature Description
SuccessFactors Connects an SAP Cloud Platform tenant to a SuccessFactors receiver system using the REST mes
REST sage protocol.
Receiver adapter The adapter supports operations: GET, POST
SuccessFactors Connects an SAP Cloud Platform tenant to SOAP-based Web services of a SuccessFactors sender
SOAP system (synchronous or asynchronous communication).
Sender adapter The adapter supports operation Query
SuccessFactors Connects an SAP Cloud Platform tenant to SOAP-based Web services of a SuccessFactors receiver
SOAP system (synchronous or asynchronous communication).
Receiver adapter The adapter supports operations: Insert, Query, Update, Upsert
SuccessFactors Connects an SAP Cloud Platform tenant to a SuccessFactors system using OData V2.
OData V2
Features of OData version 2.0 supported by the adapter:
Receiver adapter
● Operations: GET (get single entity as an entry document), PUT (update existing entry with an en
try document), POST (create new entry from an entry document), MERGE (incremental update
of an existing entry that does not replace all the contents of an entry), UPSERT (combination of
Update OR Insert)
● Query options: $expand, $skip,and $top
● Server-side pagination
● Client-side pagination
● Pagination enhancement: Data retrieved in chunks and sent to Cloud Integration
● Deep insert: Creates a structure of related entities in one request
● Authentication options: Basic authentication
● Reference links: Link two entities using the <link> tag
SuccessFactors Connects an SAP Cloud Platform tenant to a SuccessFactors system using OData V4
OData V4
Features of OData version 4.0 supported by the adapter:
Receiver adapter
● Operations: GET, POST, PUT, DELETE
● Navigation
● Primitive types supported according to OData V4 specification
● Structural types supported for create/update operations:
Edm.ComplexType, Edm:EnumType, Collection(Edm.PrimitiveType) and Collection(Edm.Com
plexType)
Twitter Enables an SAP Cloud Platform tenant to access Twitter and read or post tweets.
Receiver adapter Using OAuth, the SAP Cloud Platform tenant can access resources on Twitter on behalf of a Twitter
user.
XI Connects an SAP Cloud Platform tenant to a remote sender system that can process the XI message
protocol.
Sender adapter

Feature Description
XI Connects an SAP Cloud Platform tenant to a remote receiver system that can process the XI message
protocol.
Receiver adapter
In addition to these adapters, SAP OEM partners also provide four additional adapters to improve the
connectivity options:
SAP OEM Adapters
Feature Description
SugarCRM by Advantco SugarCRM adapter helps customers reduce the implemen

tation time by connecting to SugarCRM system. It is in
cluded within SAP Cloud Platform Integration subscription
and customers can download it from SAP Software Down
load Center.
For more information, see SugarCRM Adapter in SAP API

Business Hub .
Amazon WS Adapter by Advantco Amazon Web Services adapter helps customers reduce the
implementation time by connecting to Amazon SQS,SWF,S3
and SNS. It is included within SAP Cloud Platform Integra
tion subscription and customers can download it from SAP
Software Download Center.
For more information, see Amazon WS Adapter in SAP API

Business Hub.
Salesforce Adapter by Advantco Salesforce Adpater helps customers reduce the implemen
tation time by connecting to Salesforce Application. It is in
cluded within SAP Cloud Platform Integration subscription
and customers can download it from SAP Software Down
load Center.
For more information, see Salesforce Adapter in SAP API

Business Hub .
Microsoft Dynamics CRM Adapter by Advantco Microsoft Dynamics CRM adapter helps customers reduce
the implementation time by connecting to MS Dynamics
CRM system. It is included within SAP Cloud Platform Inte
gration subscription and customers can download it from
SAP Software Download Center.
For more information, see Microsoft Dynamics CRM Adapter

in SAP API Business Hub .
If you are quick configuring an integration flow, you can configure a few adapter parameters. Refer to the
relevant adapter configuration details for information on those parameters.

If you are developing an OData service, you can configure a SOAP, OData or HTTP adapter assigned to the
receiver channel and the OData adapter assigned to the sender channel.
 Note
Note regarding the timeout behavior for HTTP communication:
In HTTP communication spanning multiple components (for example, from a sender, through the load
balancer, to a Cloud Integration tenant, and from there to a receiver), the actual timeout period is
influenced by each of the timeout settings of the individual components that are interconnected between
sender and receiver (precisely spoken, of those components that can control the Transmission Control
Protocol (TCP) session). The component or device with the lowest number set for the idle session timeout
will determine the timer that will be used.
● When considering inbound communication (through HTTP-based sender adapters), note that in
particular the load balancer has an own timeout setting that has an influence on the overall timeout.
For the inbound side, SAP Cloud Integration supports no communication that waits for longer than 10
minutes.
● When considering outbound communication, note that in the involved HTTP-based receiver channel
you can configure a dedicated timeout. However, timeout setting has no influence on the TCP timeout
when the receiver or any additional component interconnected between the Cloud Integration tenant
and the receiver have a lower timeout. For example, consider that you have configured a receiver
channel timeout of 10 minutes and there is another component involved with a timeout of 5 minutes. In
case, nothing is transferred for a certain time, the connection will be closed after the 5th minute.
Related Information
Configure Communication Channel with Ariba Adapter [page 621]

Facebook Receiver Adapter [page 652]
HTTP Receiver Adapter [page 600]
HTTPS Sender Adapter [page 611]
Configure Communication Channel with IDoc Adapter [page 582]
Mail Adapter [page 500]
Configure Communication Channel with SFTP Adapter [page 626]
Configure Communication Channel with SOAP (SAP RM) Adapter [page 510]
Configure Communication Channel with SuccessFactors (REST) Adapter [page 553]
Configure Communication Channel with SuccessFactors (SOAP) Adapter [page 542]
Twitter Receiver Adapter [page 644]
Configure Communication Channel with ODC Adapter [page 655]
Configure a Channel with LDAP Adapter [page 657]

4.15.4.1 Mail Adapter
The mail adapter allows you to connect the tenant to an email server.
Context
The sender mail adapter can download e-mails and access the e-mail body content as well as attachments.
The receiver mail adapter allows you to send encrypted messages by e-mail.
Related Information
Configure the Mail Sender Adapter [page 500]

Configure the Mail Receiver Adapter [page 506]
4.15.4.1.1 Configure the Mail Sender Adapter
You can use the sender mail adapter to download e-mails from mailboxes using the IMAP or POP3 protocol, to
access the content of the e-mail body, and to access e-mail attachments
If you have configured a mail sender adapter, message processing is performed as follows at runtime:
According to the Scheduler settings in the mail sender adapter, the tenant sends requests to an email server
(think of this as the sender system), but the data flow is in the opposite direction, from the mail server to the
tenant. In other words, the tenant reads files from the mail server (a process that is also referred to as polling).
 Note
 Caution
Be aware of certain risks (in particular, security risks) when using the mail sender adapter.
To take the necessary precautions in order to avoid any unwanted behavior of your scenario check out the
following topic:
Important Notes [page 505]

 Restriction
An integration flow you deploy in SAP Cloud Platform Integration deploys on multiple IFLMAP runtime
nodes. Polling is triggered from only one of the runtime nodes. Message monitoring currently displays the
process status from the runtime nodes where the Scheduler is not started. This results in the message
Once you have created a sender channel and selected the mail adapter, you can configure the following
attributes.
The General tab shows general information such like the adapter type, its direction (sender or receiver), the
transport protocol, and the message protocol.
Connection
Address Specifies the host name or address of the IMAP server, for
example, mail.domain.com.
● 143 for IMAP+STARTTLS

● 993 for IMAPS
● 110 for POP3+STARTTLS
● 995 for POP3S
Proxy Type The type of proxy that you are using to connect to the target
system.
Select None if you are connecting directly to the email

server.
Select On-Premise if you are connecting to on-premise sys

tem.
Timeout (in ms) Specifies the network timeout for the connection attempt to
the server. The default value is 30000.
Location ID (only if On-Premise is selected for Proxy Type) To connect to an SAP Cloud Connector instance associated
with your account, enter the location ID that you defined for
side, or enter ${header.headername} to dynamically
read the value from a header.

Protection Specifies the method to use to establish an encrypted (se

cure) connection.
● Off
No encryption is initiated by the client.
● POP3S (only when transport protocol POP3 has been
(in POP3S) stands for secure; in technical terms, TLS
● IMAPS (only when transport protocol IMAP4 has been
(in IMAPS) stands for secure; in technical terms, TLS
● STARTTTLS Mandatory
If the server supports STARTTLS, the client initiates en
cryption using TLS. If the server does not support this
option, the connection stops with an error.
● STARTTTLS Optional
If the server supports STARTTLS, the client initiates en
cryption using TLS. If the server does not support this
option, client and server remain connected but commu
nicate without encryption.
Using STARTTLS, an existing connection without encryption

can be changed to an encrypted one using TLS (without the
need to establish a new connection).
Authentication Specifies which mechanism is used to protect user name

and password combination.
● Plain User Name/Password

The user name and password are sent in plain text.You
should only use this option together with SSL or TLS, as
otherwise an attacker could obtain the password.
● Encrypted User/Password
The user name and password are hashed before being
sent to the server. This authentication mechanism
(CRAM-MD5 and DIGEST-MD5) is secure even without
encryption.
Credential Name Specifies the name of the User Credentials artifact that con
tains user name and password (used to authenticate at the
email account).

Processing
Folder Specify the IMAP folder containing the mails to be read.
(only if as Transport Protocol the option IMAP4 has been se

lected)
Selection Specify which mails will be processed (all mails or only un
read ones).
(only if as Transport Protocol the option IMAP4 has been se
lected)
Max. Messages per Poll Defines the maximal number of messages that will be read
from the email server in one polling step.
Post-Processing Specify how to handle processed mails on the server.
 Note
If Post-Processing is set to Mark as Read and the poll
strategy is set to poll for all mails (Selection: All), then
already processed mails will be processed again at every
polling interval.
If you want to use this parameter setting, make sure that

your polling interval is sufficiently large, otherwise your
process might become inefficient.
Remove Attachments Select this options if attachments should be removed from

the mail prior to polling.
Scheduler
Schedule on Day On Date Specify the date on which you want the
operation to be executed.
(mails are to be polled at a specific day)
On Time Specify the time at which you want the



Schedule to Recur Daily Specify that the messages are to be

polled daily (either at a specific time as
(mails are to be polled periodically)
defined next to the checkbox On Time
or in a specific time interval as defined
next to the checkbox Every).
Weekly Specify that the messages are to be

polled weekly. Select the checkboxes to
indicate the days of the week on which
you want the operation to be executed.
Also specify the time (checkbox On
Time) or interval (checkbox Every) for
the schedule to recur.
Monthly Specify that the messages are to be

polled monthly. Select the day of the
month on which you want the operation
to be executed. Also specify the time
(checkbox On Time) or interval (check
box Every) for the schedule to recur.
On Time Specify the time at which you want the


Example: With the configuration shown in the figure below, the integration flow will be activated every week on
Monday to poll emails on this day every hour, between 00:00 and 24:00 (Greenwhich Time Zone).
under Schedule on Day and Schedule to Recur have been changed so that the scheduler runs every 10 seconds
between 00:00 and 24:00.

 Note
Additional Notes
● To access an attachment, you have to use Groovy script or JavaScript.

For more information about how to access attachments, see the documentation for the Script step.
● To access the mail attributes (Subject, From, or To), you have to set them manually as Allowed Headers
on the Runtime Configuration tab. This adds them to a whitelist.
● The mail sender adapter can decrypt encrypted mails and will verify the signature of a signed message.
You can access the results of the verification via headers and Exchange properties. For more
information, see Headers and Exchange Properties Provided by the Integration Framework.
Related Information
Important Notes [page 505]

Options to Protect Mail Connections [page 510]
Headers and Exchange Properties Provided by the Integration Framework [page 856]
4.15.4.1.1.1 Important Notes
When using the mail sender adapter, be aware of the following in order to avoid any unwanted results.
Security Risks
It is not possible to authenticate the sender of an e-mail
Unlike with other adapters, if you are using the sender mail adapter, the Cloud Integration system cannot
authenticate the sender of an e-mail.
Therefore, if someone is sending you malware, for example, it is not possible to identify and block this sender in
the Cloud Integration system.
To minimize this danger, you can use the authentication mechanism of your mailbox. Bear in mind, however,
that this mechanism might not be sufficient to protect against such attacks.
There are three possible threats when processing e-mail content:
● Danger to a receiver system when forwarding e-mail content

E-mails can contain malware, such as viruses or Trojan horses.
These will not affect the Cloud Integration system, but they can cause damage to a receiver system if it
doesn't have sufficient protection strategies.

● Danger to the Cloud Integration system
E-mail content can be designed to affect the processing runtime of a system.
Processing this content overloads the system and prevents requests from being fulfilled (denial of service).
The Cloud Integration system is then unavailable until the problem is fixed.
● Reliability of data
Sending e-mails is anonymous. It is not possible to verify whether the sender of an e-mail really is who they
claim to be.
Even if your mailbox has an authentication mechanism, this mechanism might not be sufficient.
Therefore, data contained in an e-mail (for example, the amount of an order), is not reliable without further
verification.
Notes with Regard to Mailbox Settings
The mailbox settings for downloading e-mails can interfere with the settings in the sender mail adapter.
For example: When using POP3 protocol, the post-processing setting Delete/Remove might not work properly.
In this case, try to configure the correct behavior in the mailbox.
4.15.4.1.2 Configure the Mail Receiver Adapter
You can use the receiver mail adapter to send encrypted messages by e-mail.
 Note
 Note
For an example how to configure the mail receiver adapter in a dedicated demo integration scenario, ceck
out the following topic: .
Once you have created a receiver channel and selected the mail adapter, you can configure the following
attributes.

Connection
Address Specifies the host name and (optionally) a port number of the SMTP server.
An external mail server can be used.
● 25 and 587 for SMTP+STARTTLS

● 465 for SMTPS
If you are using GMail Server, make sure that you allow insecure applications (GMail con
siders only communication based on OAuth2 as secure) when configuring the server. You
can use port 25 for connections to GMail server.
Timeout (in ms) Specifies the network timeout for the connection attempt to the server.
This is only used for Transmission Control Protocol (TCP), there is no timeout for SMTP
commands.
The default value is 30000. The timeout should be more than 0, but less than five mi
nutes.
Location ID (only if On-Premise To connect to a cloud connector instance associated with your account, enter the loca
is selected for Proxy Type) tion ID that you defined for this instance in the destination configuration on the cloud
side, or enter ${header.headername} to dynamically read the value from a header.
Protection Defines whether encryption is used. The possible values are:
● STARTTLS Mandatory
server does not support this option, the connection fails.
● STARTTLS Optional
If the server supports the STARTTLS command, the connection is upgraded to
Transport Layer Security encryption. This works with the normal port 25.
server does not support this option, client and server remain connected but commu
nicate without encryption.
● SMTPS
The TCP connection to the server is encrypted using SSL/TLS. This usually requires
an SSL proxy on the server side and access to the port it runs on.
● Off
No encryption is initiated, whether the server requests it or not.
Using STARTTLS, an existing connection without encryption can be changed to an en

crypted one using TLS (without the need to establish a new connection).

Authentication Specifies which mechanism is used to authenticate against the server with a user name
and password combination. Possible values are:
● None
No authentication is attempted. No credential can be chosen.
● Plain User Name/Password
The user name and password are sent in plain text. You should only use this option
together with SSL or TLS, as otherwise an attacker could obtain the password.
● Encrypted User/Password
The user name and password are hashed before being sent to the server. This au
thentication mechanism (CRAM-MD5 and DIGEST-MD5) is secure even without en
cryption.
Credential Name Specifies the name of a deployed credential to use for authentication.
From E-mail address that the message comes from.
To E-mail address that the message is sent to.
dresses.

name3@example.com
Cc Additional e-mail addresses that the e-mail is to be sent to.
These addresses are visible to the receiver.
dresses.

name3@example.com
Bcc Additional e-mail addresses that the e-mail is to be sent to.
These addresses are not visible to the receiver.
dresses.

name3@example.com
Subject Subject of the e-mail message.
Mail Body Specifies the text of an e-mail message.
Body MIME Type Specifies the type of the message body. This type determines how the message is dis
played by different user agents.

Body Encoding Specifies the character encoding (character set) of the message body. The content of the
input message will be converted to this encoding, and any character that is not available
will be replaced with a question mark ('?'). To ensure that data is passed unmodified, se
lect a Unicode encoding, for example, UTF-8.
Name (under Attachments) Specifies the file name of the attachment.
MIME Type (under The Multipurpose Internet Mail Extensions (MIME) type specifies the data format of the
Attachments) e-mail.
You can select from the following MIME types:
● Text/Plain
● Text/CSV
● Text/HTML
● Application/XML
● Application/JSON
● Application/Octet-Stream
Source Specifies the source of the data. This can be either Body, meaning the body of the input
message, or Header, meaning a header of the input message.
Header Name If the source is Header, this parameter specifies the name of the header that is attached.
Add Message Attachments Select this option to add all attachments contained in the message exchange to the e-
mail.
 Note
The parameters From, To, Cc, Bcc, Subject, Mail Body as well as the attachment name, can be dynamically
set at runtime from message headers or content.
Security
Encryption Type This parameter configures an encryption scheme used for

sending e-mails. The message body and attachments are
encrypted with the selected scheme and can only be de
crypted by the intended recipients.
Content Encryption Algorithm Specifies the symmetric (block) cipher. DESede should only
be chosen if the destination system or mail client does not
support AES.
Secret Key Length Specifies the key size of the previously chosen symmetric ci
pher. To increase the security, choose the maximum key size
supported by the destination.
Receiver Public Key Alias Specifies an alias for the public key that is to be used to en
crypt the message. This key has to be part of the tenant key
store.

Related Information

Options to Protect Mail Connections [page 510]
4.15.4.1.3 Options to Protect Mail Connections
With mail sender and receiver adapter, you have several options to protect the communication.
● SMTPS (receiver adapter), IMAPS (sender adapter) or POP3S (sender adapter)

Using one of these options, an encryption is already initiated when establishing the connection. The
connection in that case is protected using Transport Layer Security (TLS). The mail server needs to offer a
dedicated port in that case.
● STARTTLS
Using this option, an existing, unencrypted connection can be changed to an encryptiod one. This works
that way that, after the connection has been established, the client request from the server which
enhanced operations are supported by the latter. In case it is STARTTLS, the connection is upgraded to an
encrypted one.
The Protection parameter in the mail adapter provides two variants of using STARTTLS:
○ STARTTTLS Mandatory
If the server supports STARTTLS, the client initiates encryption using TLS (otherwise, the connection
stops with an error).
○ STARTTTLS Optional
If the server supports STARTTLS, the client initiates encryption using TLS (otherwise, client and server
remain connected but communicate without encryption).
4.15.4.2 Configure Communication Channel with SOAP (SAP

RM) Adapter
Prerequisites
● You have logged into your customer workspace in Cloud Integration web tooling.
● You have assigned SOAP adapter to the communication channel.
● You have specified SAP RM as the message protocol.

Context
You use this procedure to configure a communication channel with the SOAP (SAP RM) adapter.
Procedure
2. Choose the communication channel with SOAP (SAP RM) adapter that you want to configure.
4. Choose Adapter Specific tab page.
 Note
Parameters and Values of Sender SOAP (SAP RM) Adapter - Connection Details
Address Relative endpoint address at which the ESB listens to the incoming requests, for
example, /HCM/GetEmployeeDetails.

URL to WSDL URL to the WSDL defining the WS provider endpoint (of the receiver). You can
specify the WSDL by selecting a source to browse for a WSDL either from an On-
Premise ES Repository or your local workspace.
In the Resources view you can upload an individual WSDL file or an archive file
(file ending with .zip) that contains multiple WSDLs or XSDs or both resources.
For example, you can upload a WSDL which contains an imported XSD referred
by an xsd:import statement. That means, when you like to upload a WSDL
and dependent resources, you need to add the parent file along with its depend
encies in a single archive (.zip file).
You can download the WSDL by using the Integration Operations user interface
(in the Properties view, Services tab, under the integration flow-specific end
point). For newly deployed integration flows, the WSDL that is generated by the
download corresponds to the endpoint configuration in the integration flow.
Processing Settings This feature corresponds to an older version of this adapter. The reason why it is
shown can be that you either have selected a certain product profile other than
SAP Cloud Platform Integration or (in case you have selected SAP Cloud Plat
form Integration product profile) that you continue editing an integration flow
which exists already for a certain time. If you still like to use this feature, you have
○ Standard: Message is executed with WS standard processing mechanism.

Errors are not returned to the consumer.
○ Robust: WSDL provider invokes service synchronously and the processing
errors are returned to the consumer.
When you use the up-to-date adapter version, the processing setting Robust is
implicit activated.


 Note
○ Client Certificate: Sender authorization is checked on the tenant by evaluat
In the following cases certain
ing the subject/issuer distinguished name (DN) of the certificate (sent to
features might not be available
gether with the inbound request). You can use this option together with the
for your current integration
following authentication option: Client-certificate authentication (without
flow:
certificate-to-user mapping).
○ A feature for a particular
○ User Role: Sender authorization is checked based on roles defined on the
adapter or step was re
tenant for the user associated with the inbound request. You can use this op
leased after you created
tion together with the following authentication options:
the corresponding shape
The authorizations for the user are checked based on user-to-role as
○ You are using a product
signments defined on the tenant.
profile other than the one
expected.
The authorizations for the user derived from the certificate-to-user
More information: Adapter and mapping are checked based on user-to-role assignments defined on the
Integration Flow Step Versions tenant.
[page 406]

Allows you to select one or more client certificates (based on which the in
bound authorization is checked).
Choose Add to add a new certificate for inbound authorization for the se
For each certificate, the following attributes are displayed: Subject DN (infor
mation used to authorize the sender) and Issuer DN (information about the
certificate authority that issues the certificate).
○ User Role
Allows you to select a role based on which the inbound authorization is
checked.
The role ESBMessaging.send is provided by default. It is a predefined role
provided by SAP which authorizes a sender system to process messages on
a tenant. However, using SAP Cloud Platform Cockpit, you can also define
custom roles for the runtime node as well. When choosing Select, a selection
of all custom roles defined that way is offered.
 Note
Note the following:
○ You can also type in a role name. This has the same result as select
ing the role from the value help: If the inbound request is authenti
cated, depends on the correct user-to-role assignment defined in
SAP Cloud Platform Cockpit.

○ When you externalize the User Role, in the integration flow configu-
ration the value help for roles is offered as well.
○ If you have selected a product profile for SAP Process Orchestation,
the value help will only show the default role ESBMessaging.send.
Conditions

○ Body Size
○ Attachment Size

 Note
For Exactly-Once handling, the sender SOAP (SAP RM) adapter save the protocol-specific message ID
in the header SapMessageIdEx. If this header is set, SOAP (SAP RM) receiver use the content of this
header as the message ID for outbound communication. Usually, this is the desired behavior and
enables the receiver to identify any duplicates. However, if the sender system is also the receiver
system, or several variants of the message are sent to the same system (for example, in an external call
or multicast), the receiver system will incorrectly identify these messages as duplicates. In this case,
the header SapMessageIdEx must be deleted (for example, using a script) or overwritten with a new
generated message ID. This deactivates Exactly-Once processing (that is, duplicates are no longer
recognized by the protocol).
If you want to set SOAP headers via the Camel header, the following table shows which Camel header
corresponds to which SOAP header.
Which Camel header corresponds to which SOAP header
MessageId SapMessageIdEx und SapMessageId
QualityOfService SapPlainSoapQoS
ExactlyOnce ExactlyOnce
ExactlyOnceInOrder ExactlyOnceInOrder

QueueId SapPlainSoapQueueId
 Note
Parameters and Values of Receiver SOAP (SAP RM) Adapter - Connection Details
Address Endpoint address at which the ESB posts the outgoing message, for example http://
You can dynamically configure the address field of the SOAP (SAP RM) Adapter.
runtime the value of header a or exchange property (as contained in the incoming mes
sage) will be written into the Camel header CamelDestinationOverrideUrl and will be
used in runtime to send the message to.
The endpoint URL that is actually used at runtime is displayed in the message process
ing log (MPL) in the message monitoring application (MPL property
CamelHttpUri).
Location ID only in case On- To connect to a cloud connector instance associated with your account, enter the loca
Premise is selected for Proxy tion ID that you defined for this instance in the destination configuration on the cloud
Type. side. You can also enter ${header.headername} or ${property.propertyname} to dy
namically read the value from a header or a property.

In the Resources view you can upload an individual WSDL file or an archive file (file end
ing with .zip) that contains multiple WSDLs or XSDs or both resources. For example,
you can upload a WSDL which contains an imported XSD referred by an xsd:import
statement. That means, when you like to upload a WSDL and dependent resources,
you need to add the parent file along with its dependencies in a single archive (.zip
file).
Service Name of the selected service contained in the referenced WSDL.
 Note
Using the same port names across receivers is not supported. To use the same
port names, you need to create a copy of the WSDL and use it.
Operation Name Name of the operation of the selected service (that you provide in the Service Name
 Note
If you have selected the Connect using Basic Authentication option, this field is not
visible.
formance.
Compress Message Enables the WS endpoint to send compressed request messages to the WS provider
and to indicate to the WS provider that it can handle compressed response messages.
Clean Up Request Headers Select this option to clean up the adapter specific-headers after the receiver call.

Request Timeout Specifies the time (in milliseconds) that the client will wait for a response before the
connection is interrupted.
the Cloud Integration tenant and the receiver have a lower timeout. For example, con
sider that you have configured a receiver channel timeout of 10 minutes and there is
another component involved with a timeout of 5 minutes. In case, nothing is transfer
red for a certain time, the connection will be closed after the 5th minute. In HTTP com
munication spanning multiple components (for example, from a sender, through the
load balancer, to a Cloud Integration tenant, and from there to a receiver) the actual
timeout period is influenced by each of the timeout settings of the individual compo
nents that are interconnected between sender and receiver (precisely spoken, of those
components that can control the TCP session). The component or device with the low
est number set for the idle session timeout will determine the timer that will be used.

○ Basic
name and password).
This keystore has to be deployed on the related tenant. The receiver side has to be
configured appropriately.
○ None
the inbound user to the cloud connector, and from there to the back end of the rel
evant on-premise system
 Note
This authentication method can only be used with the following sender adapt
ers: HTTP, AS2, SOAP, IDOC
 Note
 Note
In the following cases certain features might not be available for your current
integration flow:
○ A feature for a particular adapter or step was released after you created
the corresponding shape in your integration flow.
You can dynamically configure the Credential Name field of the adapter, by using a Sim
ple Expression (see http://camel.apache.org/simple.html . For example, you can dy
namically define the Credential Name of the receiver adapter by referencing a message
header ${header.MyCredentialName} or a message property $
6. Save or deploy changes.

Related Information
Setting SOAP Headers [page 791]

https://wiki.scn.sap.com/wiki/display/ABAPConn/Plain+SOAP?original_fqdn=wiki.sdn.sap.com
4.15.4.3 SOAP (SOAP 1.x) Adapter
With this adapter, the tenant can exchange messages with another system that supports Simple Object Access
Protocol (SOAP) 1.1 or SOAP 1.2.
Related Information
Configure SOAP (SOAP 1.x) Sender Adapter [page 519]

Configure SOAP (SOAP 1.x) Receiver Adapter [page 531]
4.15.4.3.1 Configure SOAP (SOAP 1.x) Sender Adapter
 Note
 Note

Connection
Address Relative endpoint address on which the integration runtime expects incoming requests,
for example, "/HCM/GetEmployeeDetails".
Service Definition Specifies the source of the service definition.
You can select the following options:
● Manual: You configure the service behavior manually by the parameters shown be
low.
● WSDL: The service behavior is defined via WSDL configuration.
Use WS-Addressing Select this option to accept addressing information from message information headers
during runtime.
(only if Service Definition:
Manual is selected)
Message Exchange Pattern Specifies the kind of messages that are processed by the adapter.
(only if Service ● Request-Reply: The adapter processes both request and response.
Definition:Manual is selected
 Tip
When using this option, the response code can accidently be overwritten by a
called receiver. For example, when your integration flow contains an SOAP
sender adapter (with a Request-Reply pattern) and an HTTP receiver adapter,
and the HTTP receiver returns an HTTP response code 202 (as it has accepted
the call), the SOAP sender adapter returns in the reply also HTTP response code
202 instead of 200 (OK). To overcome this situation, you have to remove the
header CamelHttpResponseCode before the message reply is sent back to
the sender.
● One-Way

URL to WSDL URL to the WSDL defining the WS provider endpoint (of the receiver). You can specify the
WSDL by selecting a source to browse for a WSDL either from an On-Premise ES Reposi
(only if as Service Definition the
tory or your local workspace.
option WSDL is selected)
In the Resources view you can upload an individual WSDL file or an archive file (file ending
with .zip) that contains multiple WSDLs or XSDs or both resources. For example, you
can upload a WSDL which contains an imported XSD referred by an xsd:import state
ment. That means, when you like to upload a WSDL and dependent resources, you need
to add the parent file along with its dependencies in a single archive (.zip file).
 Note
● 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.
● Do not use WSDLs with blanks.
We recommend that you don't use blanks in WSDL names or directories, as this
can lead to runtime issues.
You can download the WSDL by using the Integration Operations user interface (in the
Properties view, Services tab, under the integration flow-specific endpoint). For newly de
ployed integration flows, the WSDL that is generated by the download corresponds to the
endpoint configuration in the integration flow.
The WSDL download does not work for WSDLs with external references because these
WSDLs cannot be parsed.
Service Name of the selected service contained in the referenced WSDL
field) contained in the referenced WSDL
(only if Service Definition: The
adapter only: WSDL is selected)
Processing Settings ● WS Standard: Message is executed with WS standard processing mechanism. Errors
are not returned to the consumer.
(only if one of the following op ● Robust: WSDL provider invokes service synchronously and the processing errors are
tions is selected: returned to the consumer.
● Service Definition: WSDL

● Service Definition: Manual
andMessage Exchange
Pattern: One-Way

● Client Certificate: Sender authorization is checked on the tenant by evaluating the

subject/issuer distinguished name (DN) of the certificate (sent together with the in
bound request). You can use this option together with the following authentication
option: Client-certificate authentication (without certificate-to-user mapping).
● User Role: Sender authorization is checked based on roles defined on the tenant for
the user associated with the inbound request. You can use this option together with
the following authentication options:
The authorizations for the user are checked based on user-to-role assignments
defined on the tenant.

Allows you to select one or more client certificates (based on which the inbound au
thorization is checked).
adapter. You can then select a certificate stored locally on your computer. You can
also delete certificates from the list.
For each certificate, the following attributes are displayed: Subject DN (information
used to authorize the sender) and Issuer DN (information about the certificate au
thority that issues the certificate).
● User Role
The role ESBMessaging.send is provided by default. It is a predefined role provided
by SAP which authorizes a sender system to process messages on a tenant. How
ever, using SAP Cloud Platform Cockpit, you can also define custom roles for the
runtime node as well. When choosing Select, a selection of all custom roles defined
that way is offered.
 Note
Note the following:
○ You can also type in a role name. This has the same result as selecting the
role from the value help: If the inbound request is authenticated, depends
on the correct user-to-role assignment defined in SAP Cloud Platform
Cockpit.

WS-Security
● Via Manual Configuration in Channel

● None
If you select this option, no further WS-Security-relevant settings can be applied.
WS-Security Type Specifies the combination of message protection methods that are to be applied. There
are the following options:
● Verify Message and Sign Response (default)

A signed payload is expected by the tenant, and the signature has to be verified.
● Verify and Decrypt Message and Sign and Encrypt Response
A signed and encrypted payload is expected by the tenant. The signature has to be
verified and the payload has to be decrypted.
Private Key Alias for Response Specify an alias for the private key that is to be used to sign the response message.
Signing
You can also enter ${header.headername} or ${property.propertyname} to read the name
The tenant private key is used to sign the response message (that is sent to the WS con
sumer). The tenant private key has to be part of the tenant keystore.
Public Key Alias for Response Specify an alias for the public key that is to be used to encrypt the response message..
Encryption
The sender (WS consumer) public key is used to sign the response message (that is sent
(only in case Verify and Decrypt to the WS consumer). This key has to be part of the tenant keystore.
Message is selected for WS-
Security Type)
Save Incoming Signed Message Select this option if the incoming signed (and encrypted) message is to be stored.
Signature Algorithm Specify a signature algorithm to be applied when signing the response message.
Possible values:
● SHA1 (default value)

● SHA256
● SHA512
Signing Order only in case Via Defines the order in which signing and encryption must be applied. There are the follow
Manuel Configuration in ing options:
Channel is selected for WS- ● Sign Before Encryption (default)
Security Configuration. ● Encrypt before Signing

Check Time Stamp Select this option, if the sender (WS consumer) sends a time stamp along with the mes
sage.
In case a request-response pattern is configured, a time stamp is added to the response

message.
Sender is Basic Security Profile As default setting, select this option.

Compliant
This option should be selected in case the sender system supports a dedicated security
level which is described by the Basic Security Profile (as assumed to be the case for most
systems). Only in case the sender system does not support this security profile, deselect
this option.
Algorithm Suite Assertion Specifies which algorithms are to be used by the WS consumer.
Initiator Token ● Include Strategy

Preset value Always to Recipient ensures that the WS consumer sends the certificate
along with the message.
● X509 Token Assertion
Defines the format of the certificate being sent by the WS consumer along with the
message.
Recipient Token Include Strategy
Conditions
Maximum Message Size This parameter allows you to configure a maximum size for
inbound messages (smallest value for a size limit is 1 MB). All
inbound messages that exceed the specified size (per inte
gration flow and on the runtime node where the integration
flow is deployed) are blocked.

● Body Size
● Attachment Size

Related Information
adapter/
WS-Security Configuration for the Sender SOAP 1.x Adapter [page 90]

4.15.4.3.1.1 WS-Security Configuration for the Sender SOAP
1.x Adapter
You use a sender channel to configure how inbound messages are to be treated at the tenant’s side of the
communication.
With regard to WS-Security in a sender channel, you specify the following:
● How the tenant verifies the payload of an incoming message (signed by the sender)
● How the tenant decrypts the payload of an incoming message (encrypted by the sender)
The following figure illustrates the setup of components:
The sender SOAP 1.x adapter allows the following combination of message-level security options:
● Verifying a payload
● Verifying and decrypting a payload
Sender Adapter [page 519] (under WS-Security).
4.15.4.3.1.2 SOAP Sender Adapter: Example Integration Flow
 Note
With the following steps, you can easily modify and extend the basic integration flow that was introduced in
the Getting Started section of this documentation.
More information:

You can easily modify the integration flow described in the Getting Started section by adding a SOAP client as
sender.
The figure shows the integration flow model that you get as a result of this exercise.
In the modified integration flow, a SOAP client instead of a Timer event triggers message processing.
This is how the integration flow processes the message at runtime:
1. The SOAP client (represented by the Sender shape) sends a Simple Object Access Protocol (SOAP)
message toSAP Cloud Platform Integration through a SOAP (SOAP 1.x) sender channel.
The SOAP message contains a product identifier.
2. The Content Modifier creates a message header (which we also call productIdentifier) and writes the
actual value of the productIdentifier element into it. This header will be used in the subsequent step.
3. The Request Reply step passes the message to an external data source and retrieves data (about
products) from there.
The external data source (which is represented by the lower WebShop shape) supports the Open
DataProtocol (OData). For our scenario, we use the ESPM WebShop, which is based on the Enterprise
Sales and Procurement Model (ESPM) provided by SAP. The demo application can be accessed at the
following address: https://espmrefapps.hana.ondemand.com/espm-cloud-web/webshop/
4. An OData receiver channel is used for the connection to the OData source. To query for exactly one
product (for the product identifier provided with the inbound message), the header that was created in the
preceding Content Modifier is used.
5. The OData service provides the details of one specific product, which is identified by the actual value of the
productIdentifier field (provided with the inbound SOAP message).
6. Finally, the result of the request is forwarded to an e-mail account using the Mail receiver adapter (the e-
mail server is represented by the right Mail … shape in the integration flow model).
Related Information
Create the SOAP Sender Channel [page 527]

Set Up the SOAP Client and Start Message Processing [page 529]

4.15.4.3.1.2.1 Create the SOAP Sender Channel
Create a SOAP channel to define how the sender calls the integration flow.
1. Click the Sender shape. The context icons for the Sender appear.
 Note
If you click the information icon, the version of the integration flow component is displayed.
Do not confuse the version of an individual integration flow component with the software version of
SAP Cloud Platform Integration. An integration flow component gets a new version each time a new
feature is added to it by SAP. Let's imagine a situation where you started modeling an integration flow
some time ago and now want to continue working on it. Let's assume that SAP has updated the
software in the meantime. A new version of an integration flow step or shape that you have used is now
available, containing a new feature. You can continue to use the old component version, but if you want
to use the new feature you need to update to the new version.
2. Click the arrow icon and drag and drop the cursor on the Start event.
The list of available adapter types is displayed in a dialog.
3. Choose the adapter type SOAP SOAP 1.x .

The properties of the adapter are shown below the model.

4. The General tab contains information such as the adapter type (SOAP), the direction (sender), and the
message protocol (SOAP 1.x).
5. Go to the Connection tab.
Specify the following parameters:
○ Address: This parameter defines the endpoint under which the integration flow can be called from the
sender. Start the address with a slash, for example, /FirstFlow.
○ Service Definition: Keep the option Manual. You would select the other option, WSDL, if you wanted to
define your service based on an uploaded Web Service Description Language (WSDL) file.
We do use a WSDL when setting up the SOAP sender, but this WSDL is only used to define the
message structure. No further information from the WSDL is used to define the specifics of inbound
message processing.
○ Message Exchange Pattern: Keep Request-Reply, which means that the integration flow sends a
response message to the sender.
○ Authorization and User Role: You want to configure your first integration flow so that the inbound
request is authenticated using basic authentication (based on user credentials). To keep it simple, you
use your dialog user. During onboarding, you also made sure that the role ESBMessaging.send was
assigned to your user (and this setting was also used when configuring the SOAP client).
 Tip
Selecting User Role does not mean that you are determining the usage of basic authentication.
User Role authorization only means that the permissions of the sender of the message are checked
based on roles (which are assigned to the user that is associated with the sender).
However, note that if you select this authorization option, you can also configure other inbound
authentication scenarios. You can, for example, configure client certificate authentication for the
sender and add an additional step (certificate-to-user mapping) to map the certificate to a user
whose permissions are checked (based on the roles assigned to this user).

Furthermore, User Role authorization is compatible with OAuth authentication.
For productive scenarios, we recommend using client certificate authentication with certificate-to-
user mapping. However, to simplify the setup of this integration flow, we propose that you choose
basic authentication - simply because it is much easier to configure the sender in this case.
You can select other roles for inbound authentication (if you have defined these roles for the runtime
node in SAP Cloud Platform Cockpit), but you don't use this option in this scenario.
4.15.4.3.1.2.2 Set Up the SOAP Client and Start Message

Processing
Set up a SOAP client that represents the sender system.
You can use a SOAP client of your choice to send a SOAP message to SAP Cloud Platform Integration.
When configuring the SOAP client, ensure the following:
● The authentication is defined in such a way that the SOAP client is authorized to send a request to SAP
Cloud Platform Integration and process the integration flow.
In the SOAP adapter settings for User Role-based authorization, make sure that you specify the same
credentials for the user associated with the SOAP client as for the user who is authorized to process the
integration flow (in our example, this is the user who is assigned the role ESBMessaging.send).
● As the address for the SOAP request, enter the endpoint address that is displayed for the integration flow
artifact (in the Monitor section of the Web UI under Manage Integration Content).
● To define the message structure for our example integration flow, you can use a WSDL file with the content
from the info box below. Simply copy and paste the content into a text editor, save the file with
extension .wsdl, and import this WSDL file into your SOAP client (if this is supported).
Send the SOAP request with a dedicated value for the productIdentifier (for example, HT-1080).

Check your e-mail account. You should find an e-mail with the following content:
Send another SOAP message with another productIdentifier (for example, HT-2001), and you receive details of
another product.
WSDL File Defining the Inbound Message
 Sample Code

<wsdl:definitions name="Inbound_Async"
targetNamespace="http://cloudintegration.sap.com/demo" xmlns:p1="http://
cloudintegration.sap.com/demo"
<wsp:Policy wsu:Id="OP_Inbound_Async" />
<wsdl:types>
<xsd:schema targetNamespace="http://cloudintegration.sap.com/demo"
cloudintegration.sap.com/demo">
<xsd:sequence>
<xsd:element name="productIdentifier" type="xsd:string" />
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</wsdl:types>
</wsdl:message>
<wsdl:portType name="Inbound_Async">
<wsdl:operation name="Inbound_Async">

<wsp:Policy>
<wsp:PolicyReference URI="#OP_Inbound_Async" />
</wsp:Policy>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="Inbound_AsyncBinding" type="p1:Inbound_Async">
<wsdl:operation name="Inbound_Async">
<soap:operation soapAction="http://sap.com/xi/WebService/soap1.1"
<wsdl:input>
</wsdl:input>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
4.15.4.3.2 Configure SOAP (SOAP 1.x) Receiver Adapter
 Note
 Note
 Caution
Usage of Different WSDL Binding Styles:
Note that messages that contain RPC-style bindings can only be processed by the SOAP receiver channel if
no WSDL file is provided (that is, if you leave the URL to WSDL field empty). We recommend that you use

document-style payloads. In case several XML parts a returned by the receiver system in the RPC
response, only the first part is processed by SAP Cloud Platform Integration. The other parts are ignored.
A WSDL binding describes how the service is bound to a message protocol. For the processing of SOAP
messages, you can choose from the following binding types:
● RPC/encoded (not recommended in WS Basic Profile Version 1.0)

● RPC/literal
● Document/encoded (not recommended in WS Basic Profile Version 1.0)
● Document/literal
RPC stands for Remote Procedure Call. For more information on these options and the meaning of literal
and encoded, see http://www.w3.org/TR/2001/NOTE-wsdl-20010315 .
Connection
Address Endpoint address on which the ESB Bus posts the outgoing message, for example http://
You can dynamically configure the address field of the SOAP (SOAP 1.x) Adapter.
When you specify the address field of the adapter as ${header.a} or ${property.a}, at run
time the value of header a or exchange property (as contained in the incoming message)
will be written into the Camel header CamelDestinationOverrideUrl and will be used in
runtime to send the message to.
The endpoint URL that is actually used at runtime is displayed in the message processing
log (MPL) in the message monitoring application (MPL property
RealDestinationUrl). Note that you can manually configure the endpoint URL us
ing the Address attribute of the adapter. However, there are several ways to dynamically
override the value of this attribute (for example, by using the Camel header
CamelDestinationOverrideUrl).


 Note
If you select the On-Premise option, the following restrictions apply to other pa
rameter values:
○ Do not use an HTTPS address for Address, as it leads to errors when per
forming consistency checks or during deployment.
○ Do not use Certificate-Based Authentication as the Authentication Type, as it
leads to errors when performing consistency checks or during deployment
 Note
If you select the On-Premise option and use the SAP Cloud Connector to connect
to your on-premise system, the Address field of the adapter refers a virtual ad
dress which has to be configured in the SAP Cloud Connector settings.
Location ID only in case On- To connect to a cloud connector instance associated with your account, enter the location
Premise is selected for Proxy ID that you defined for this instance in the destination configuration on the cloud side. You
Type. can also enter ${header.headername} or ${property.propertyname} to dynamically read
the value from a header or a property.
URL to WSDL URL to the WSDL defining the WS provider endpoint (of the receiver). You can specify the
WSDL by selecting a source to browse for a WSDL either from an On-Premise ES Reposi
tory or your local workspace.
In the Resources view you can upload an individual WSDL file or an archive file (file ending
with .zip) that contains multiple WSDLs or XSDs or both resources. For example, you
can upload a WSDL which contains an imported XSD referred by an xsd:import state
ment. That means, when you like to upload a WSDL and dependent resources, you need
to add the parent file along with its dependencies in a single archive (.zip file).
 Note
● 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.
● Do not use WSDLs with blanks:
It is not recommended to use blanks in WSDL names or directories. This could
lead to runtime issues.
Service Name Name of the selected service contained in the referenced WSDL

Port Name Name of the selected port of a selected service (that you provide in the Service Name
field) contained in the referenced WSDL .
Same port names across receivers is not supported. To use the same port names, you
need to create a copy of the WSDL and use it.
Operation Name Name of the operation of selected service (that you provide in the Service Name field)
contained in the referenced WSDL.
Connect Without Client This feature corresponds to the Authentication setting None and is shown when you use
Authentication
an older version of this adapter. The reason why it is shown can be that you either have
selected a certain product profile other than SAP Cloud Platform Integration or (in case
you have selected SAP Cloud Platform Integration product profile) that you continue edit
ing an integration flow which exists already for a certain time.
Select this option to connect the tenant anonymously to the receiver system.
Select this option if your server allows connections without authentication at the trans
port level.
Connect Using Basic This feature corresponds to Authentication setting Basic and is shown when you use an
Authentication
older version of this adapter. The reason why it is shown can be that you either have se
lected a certain product profile other than SAP Cloud Platform Integration or (in case you
have selected SAP Cloud Platform Integration product profile) that you continue editing
an integration flow which exists already for a certain time.
Select this option to allow the tenant to connect to the receiver system using the de
ployed basic authentication credentials.
Credential Name: Enter the credential name of the username-password pair specified dur
ing the deployment of basic authentication credentials on the cluster.

● Basic
name and password).
It is a prerequisite that user credentials are specified in a Basic Authentication arti
fact and deployed on the related tenant.
When you have selected Basic authentication option, you can enter a Credential
Name.
● Client Certificate
It is a prerequisite that the required key pair is installed and added to a keystore. This
keystore has to be deployed on the related tenant. The receiver side has to be config-
ured appropriately.
● None
The tenant authenticates itself against the receiver by forwarding the principal of the
inbound user to the cloud connector, and from there to the back end of the relevant
on-premise system
 Note
This authentication method can only be used with the following sender adapters:
HTTP, SOAP, IDoc.
 Note
receiver channel, the token for principal propagation expires, which leads to er
rors in message processing.
You can dynamically configure the Credential Name field of the adapter, by using a Simple
Expression (see http://camel.apache.org/simple.html . For example, you can dynami
cally define the Credential Name of the receiver adapter by referencing a message header
${header.MyCredentialName} or a message property $

Private Key Alias Allows you to enter the private key alias name that gets the private key from the keystore
and authenticates you to the receiver in an HTTPS communication.
If you have selected the option of Connect using Basic Authentication, this field is not visi
ble.
You can dynamically configure the Private Key Alias property by specifying either a header
or a property name in one of the following ways:
Please be aware that in some cases this feature can have a negative impact on perform
ance.
 Note
You can externalize all attributes related to the configuration of the authentication op
tion. This includes the attributes with which you specify the authentication option as
such (if you either intend to use basic authentication , certificate-based authentica
tion or no authentication), as well as all attributes with which you specify further se
curity artifacts that are required for any configurable authentication option (Private
Apply one of the following two recommendations when externalizing such attributes.
● Externalize all attributes related to the configuration of all options (for example,
Authentication Option, Credential Name and Private Key Alias).
● Externalize only one of the following attributes: Private Key Alias or Credential
Name.
Avoid incomplete externalization such that, for example, you externalize only the at
tribute for the Authentication Option but not the related Credential Name. In such
cases, the integration flow configuration (based on the externalized parameters) can
not work properly.
The reason for this is the following: When you have externalized the Authentication
Option attribute and only the Private Key Alias (but no Credential Name), in the inte
gration flow configuration dialog all authentication options (Basic, Certificate-Based
and None) are selectable in a drop-down list. However, when you now select Basic
Authentication from the drop-down list, no Credential Name can be configured.

Timeout (in ms) Specifies the time (in milliseconds) that the client will wait for a response before the con
nection is being interrupted.
the Cloud Integration tenant and the receiver have a lower timeout. For example, consider
that you have configured a receiver channel timeout of 10 minutes and there is another
component involved with a timeout of 5 minutes. In case, nothing is transferred for a cer
tain time, the connection will be closed after the 5th minute. In HTTP communication
spanning multiple components (for example, from a sender, through the load balancer, to
a Cloud Integration tenant, and from there to a receiver) the actual timeout period is influ-
enced by each of the timeout settings of the individual components that are intercon
nected between sender and receiver (precisely spoken, of those components that can
control the TCP session). The component or device with the lowest number set for the
idle session timeout will determine the timer that will be used.
Compress Message Enables the WS endpoint to send compressed request messages to the WS Provider and
to indicate the WS Provider that it can handle compressed response messages.
Clean Up Request Headers Select this option to clean up the adapter-specific headers after the receiver call.
WS-Security
● Via Manual Configuration in Channel

The security settings are specified as part of the receiver endpoint (within the end
point WSDL) in elements as defined by the WS-Policy standard.
● None

Username Token Specifies the way how Username Token is to be configured. Select this option to authenti
cate at message level based on a user ID and a password (transported within a SOAP
message).
When as WS-Security Configuration you have selected Via Manual Configuration in

Channel, you have the following options:
● Plain Text Password

The Password is transferred in plain text (https encrypted).
● Hashed Password
Cryptographic hash function is applied for password.
● None
No User Name Token is applied.
If you have selected the option Plain Text Password or Hashed Password, enter the creden
tial name, that is, the alias that was assigned to the authorized user and password during
tenant deployment.
 Note
It depends on additional adapter settings how the token is treated during runtime (in
particular, with regard to whether the token will be encrypted or not).
When the security settings are defined by the endpoint WSDL (when for WS-Security
Configuration you have selected Based on Policies in WSDL), the token is treated ac
cording to what is defined within the WSDL.
When the security settings are defined manually (when for WS-Security Configuration
you have selected Via Manual Configuration in Channel), it depends on the selected
WS-Security Type how the token is treated:
● Sign Message selected: The token is not encrypted.

● Sign and Encrypt Message selected: The token is encrypted.
Credential Name Alias that was assigned to the authorized user and password during tenant deployment
option Based on Policies in
WSDL is selected)
WS-Security Type Specifies the combination of message protection methods that are to be applied. There
are the following options:
WS-Security Configuration the ● Sign Message
Tenant signs the payload.
option Via Manual
Configuration in Channel is se ● Sign and Encrypt Message
Tenant signs and encrypts the payload
lected)
● None
No WS-Security Type is applied.

Private Key Alias for Signing Specify an alias for the tenant private key that is to be used to sign the message.
You can also enter ${header.headername} or ${property.propertyname} to read the name

The tenant private key is used to sign the request message (that is sent to the WS pro
vider (receiver)). The tenant private key has to be part of the tenant keystore.
Public Key Alias for Encryption Specify an alias for the public key that is to be used to encrypt the message.
(only configurable when for The receiver (WS provider) public key is used to encrypt the request message (that is sent
WS-Security Type the option to the receiver). This key has to be part of the tenant keystore.
Sign and Encrypt Message is
selected)
Signature Algorithm Specify a signature algorithm to be applied when signing the request message.
Possible values:
● SHA1 (default value)

● SHA256
● SHA512
Set Time Stamp Select this option to send a time stamp along with the message.
In case a request-response pattern is configured, a time stamp is expected in the re

sponse message.
Receiver is Basic Security Leave this option selected if the receiver system complies with the basic security profile
Profile Compliant (as assumed to be the case for most systems). Deselect this option if the receiver system
does not support this security profile.
Layout ● Strict
Items are added to the security header following numbered layout rules according to
a general principle of 'declare before use'.
option Via Manual ● Lax
Items are added to the security header in any order that conforms to WSS: SOAP
Message Security
lected)
Algorithm Suite Assertion Specifies which algorithms are used by the WS consumer

option Via Manual
lected)

Initiator Token These entries define policies for the WS consumer.
(only configurable when for ● Include Strategy

WS-Security Configuration the Value Always to Recipient ensures that the WS consumer sends the certificate along
option Via Manual with the message.
Configuration in Channel is se ● X509 Token Assertion
lected) Defines the format of the certificate being sent by the WS consumer along with the
message.
Recipient Token These entries define policies for the WS consumer.
(only configurable when for ● Include Strategy

WS-Security Configuration the Value Always to Initiator adds the certificate to the response message.
option Via Manual ● X509 Token Assertion
Defines the format of the certificate being sent by the WS consumer along with the mes
lected)
sage.
Related Information
adapter/
WS-Security Configuration for the Receiver SOAP 1.x Adapter [page 91]
4.15.4.3.2.1 WS-Security Configuration for the Receiver

SOAP 1.x Adapter
With a receiver channel you configure the outbound communication at the tenant’s side of the communication.
With regard to WS-Security in a sender channel you specify the following:
● How the tenant signs the payload of a message (to be verified by the receiver)
● How the tenant encrypts the payload of a message (to be decrypted by the receiver)
The following figure illustrates the setup of components.

The receiver SOAP 1.x adapter allows to configure the following combinations of message security methods:
● Signing a payload
● Signing and encrypting a payload
Configuration Options for WS-Security
Signing and encryption (and verifying and decryption) is based on a specific set up of keys as illustrated in the
figures. Moreover, for the message exchange, specific communication rules apply as been agreed between the
administrators of the Web service client and Web service provider (for example, if certificates are to be sent
with the message).
There are two options how these security and communication settings can be specified:

Using this option, the security settings are specified as part of the receiver endpoint (within the endpoint
WSDL) in elements as defined by the WS-Policy standard.
That way you can specify, for example, within the WSDL that certificates for message level security are sent
with the message.
For more information on the WS-Policy standard, see: http://docs.oasis-open.org/ws-sx/ws-
securitypolicy/v1.3/os/ws-securitypolicy-1.3-spec-os.html .
● Manual Configuration in Channel
Using this option, you specify the required settings in the channel.
The naming of the available attributes corresponds to the terminology used in the WS-Policy specification.
If you use manual configuration, a sub set of the options as defined by the standard is supported. For more
information on the standard, see http://www.w3.org/TR/ws-policy/ and http://docs.oasis-open.org/ws-
sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.pdf .
Receiver Adapter [page 531] (under WS-Security).

4.15.4.4 Configure Communication Channel with
SuccessFactors (SOAP) Adapter
Prerequisites
● You have logged in to your customer workspace in the SAP Cloud Platform Integration web tooling.
● You selected the SOAP message protocol when you assigned the SuccessFactors adapter.
Context
The SuccessFactors adapter enables you to communicate with the SuccessFactors system. You use the SOAP
message protocol to connect to the SOAP-based Web services of the SuccessFactors system.
 Note
You can now pass filter conditions via a header or property while performing an asynchronous or ad hoc
operation.
 Restriction
If you deploy an integration flow in Cloud Integration, it deploys in multiple tenants. Polling is triggered from
only one of these tenants. The message monitor displays the process status for the tenants where the
Scheduler has not started. As a result, the message monitor displays messages of less than a few
milliseconds, where the scheduler was not triggered. These entries contain firenow=true in the log. You can
ignore these entries.
 Remember
You must enable HTTP Session Reuse with either the On Exchange or On Integration Flow level.
For more information, see Specify the Runtime Configuration [page 475].
Use the following procedure to configure a communication channel with the SuccessFactors adapter.
Procedure
2. Select the communication channel you want to configure.
3. On the General tab, provide the channel name and description in the relevant fields if required.

4. Go to the Processing tab and provide values in the fields based on the descriptions in the following table.
Field Name and Description for SuccessFactors SOAP Adapter Processing Details
Field Description

connect to. You can browse to and select the SuccessFac
tors data center URL by using the Select option.
Address Suffix The system automatically populates this field with /

sfapi/v1/soap as you have selected the SOAP message
protocol.
Factors system.
If you choose Manual, you need to enter values for the

Credential Name Credential name for your credentials that has been de
ployed on the tenant.
Call Type Default value is Synchronous Query. If you want to execute

an ad hoc operation, select Adhoc / Asynchronous from
the dropdown list.
Operation Operation that you want to perform on the entity that you
are accessing on the SuccessFactors system.
Entity Entity that you want to access in the SuccessFactors sys

tem.
Query Query that you are executing.
Page Size Maximum number of records to be fetched in one page of

response.
Timeout Maximum time the system waits for a response before . If

you do not enter a value, the default value of is used.

Field Description
Retry on Failure Enables the adapter to retry connecting to the Success

Factors system in case of any network issues. The adapter
tries to reestablish the connection every 3 minutes, up to
a maximum of 5 times. The retry happens in the following
scenarios:
○ Upsert: For 412 inner error code along with HTTP re
sponse code 200.
○ Query Operations: For 502, 503, 504 HTTP response
codes (corresponding to Create, Update, and Delete
operations respectively).
5. If you want to select or change the entity, and modify the query, follow the steps in Modifying
SuccessFactors SOAP Entity and Operation [page 545].
6. If you are using the SuccessFactors SOAP adapter in the receiver channel of a Local Integration Process,
select Process in Pages.
You cannot use the Process in Pages option with the Query operation if the Process Call step is used in a
Multicast branch.
 Note
By selecting Process in Pages, you enable the adapter to process messages in batches. The size of a
message batch is defined by the value that you specify in the Page Size field.
 Tip
In the Process Call step that calls the Local Integration Process, ensure that you enable looping and set
Expression Type as Non-XML, Condition Expression as $
{property.SAP_SuccessFactorsHasMoreRecords.<receiver.name>} contains 'true',
and Maximum Number of Iterations as 999.
7. If you are configuring the sender channel, go to the Scheduler tab and provide values in the fields based on
the descriptions in the following table.
Run Once Not applicable Select to execute the operation imme

diately after deploying the integration
content.

At Time Specify the time at which you want





days of the week on which you want
the operation to be executed. Also,
specify the time or interval for the
schedule to recur.

you want the operation to be exe
cuted. Also indicate the time or the in
terval for the schedule to recur.
8. Save or deploy your changes.
Whenever the SuccessFactors SOAP adapter is used, the following headers with the specified values will be
sent to the SuccessFactors back end as HTTP request headers:
1. X-SF-Correlation-Id : MPL ID
2. X-SF-Client-Tenant-Id : Client/Tenant ID
3. X-SF-Process-Name : iFlow Name
4. X-Agent-Name : SAP Cloud Platform Integration
4.15.4.4.1 Modifying SuccessFactors SOAP Entity and

Operation
Prerequisites
● You are configuring the communication channel that is assigned with the SuccessFactors SOAP adapter.
● The TrustedCAs from the service provider you are connecting to have been added to the system keystore
associated with your HCI account.

Context
The SuccessFactors SOAP adapter enables you to modify the entity that you are accessing and the operation
that you are performing on the entity. You can use this adapter to perform the following operations:
● Query
● Insert
● Update
● Upsert
You use the following procedure to change the entity and modify the operation for the SuccessFactors SOAP
adapter.
Procedure
1. In the Entity field, choose Select.
2. If you have not added the system with authentication details, choose and provide values in the
fields, based on the descriptions in the following table. Choose Connect.
Fields Description
System Name of the SuccessFactors data center that you are con
necting to
Address URL of the SuccessFactors data center that you are con
necting to
Company ID Company ID for authentication
User ID User ID associated with the company ID
Password Relevant password for the specified user ID
3. If you have added the system with authentication details, perform the following substeps:
a. In the System field, choose the system you want to connect to from the dropdown list.
b. In the Password field, provide the appropriate password.
c. Choose Connect.
4. In the Entity Selection dialog, select the entity that you want to access.
5. In Operation dropdown list, choose the operation that you want to perform.
 Note
You can only perform the Query operation in the sender channel.
6. In the Fields dropdown list, select the fields that you want to perform the operation on.

 Note
You can select multiple fields by selecting their respective checkboxes. Choose the operation you want
to perform.
7. If you want to specify filter conditions, choose the  icon, select the operation you want to use, and
perform the following substeps:
a. In the Filter By field, enter the fields that you want to filter.
b. In the Operator dropdown list, select the operator that you want to use to define the filter condition.
c. In the Input Type field, select the type of input you want to provide for defining the filter condition.
d. In the Value field, provide the value of the input for the filter condition.
e. Select AND or OR based on how you want this filter condition to be evaluated when the operation is
executed.
f. Choose Add to add more than one filter condition.
8. If you want to specify sorting conditions, choose and perform the following substeps:
a. In the Field field, select the field you want to include in the sorting condition.
b. If you want the sorting to be done in descending order, select the checkbox in the Desc column.
c. Choose to add more than one filter condition.
Results
The system displays a message that an XSD file has been created. You can use this XSD file for mapping steps.
4.15.4.5 SuccessFactors OData V2 Adapter
The SuccessFactors adapter enables you to communicate with the SuccessFactors system. You use the OData
V2 message protocol to connect to the OData V2 Web services of the SuccessFactors system.
The OData V2 message protocol for the SuccessFactors adapter is available only in the receiver channel. For
more information, see Configure SuccessFactors OData V2 Receiver Adapter [page 548].
 Tip
● If your input payload contains nodes without data, the output will also contain empty strings. If you
want to avoid empty strings in the output, ensure that the input payload does not contain any empty
nodes.
● You can use headers and exchange properties in the adapter settings to dynamically pass values at
runtime. For more information, see Headers and Exchange Properties Provided by the Integration
Framework [page 856].

Whenever the SuccessFactors OData V2 adapter is used, the following headers with the specified values will be
sent to the SuccessFactors back end as HTTP request headers:
1. X-SF-Correlation-Id : MPL ID
2. X-SF-Client-Tenant-Id : Client/Tenant ID
3. X-SF-Process-Name : iFlow Name
4. X-Agent-Name : SAP Cloud Platform Integration
4.15.4.5.1 Configure SuccessFactors OData V2 Receiver

Adapter
Configure SuccessFactors OData V2 receiver adapter by understanding the adapter parameters.
SuccessFactors OData V2 receiver adapter supports externalization. To externalize the parameters of this
adapter choose Externalize and follow the steps mentioned in Externalize Parameters of an Integration Flow
[page 482].
 Note
● OData adapter supports sending error response in exception subprocess. The error response body will
be part of expression ${in.body}.
● OData services response code is captured in the camelhttpresponsecode header.
● Message headers are converted to HTTP request headers while sending the request to OData server. If
you do not want to send any specific HTTP headers, then you must explicitly remove the headers using
content modifier or by defining a script before OData receiver adapter.
● In Upsert operation, you can link every entity to the same navigation entity with the same key
parameters, using <link>. You cannot link to different navigation entity.
● Retry for Upsert operation is now enabled for inner error code 412. Retry will be executed once and
after 1 minute only.
 Remember
You must enable HTTP Session Reuse, either On Exchange level or On Integration Flow level.
For more information refer to Specify the Runtime Configuration [page 475].
Connection
Address URL of the SuccessFactors data center that you are connect
ing to. This field is populated based on what you select in
SFSF Data Center. You can browse and select SuccessFac
tors data center URL by using the Select option.
Address Suffix URL suffix to communicate with the SuccessFactors system.

This is populated with /odata/v2 and you cannot change it.

Proxy Type Type of proxy you want to use for connecting to SuccessFac
tors OData V2 service. Currently, only Internet proxy type is
available.
Credential Name Name of the credentials that you have deployed in Security
Material in  (Operations View)
Processing
Operation Details Operation that you want to perform on the SuccessFactors

OData V2 service.
The adapter supports Function Import for functions which

return entity or collection of entities. Below return types are
not supported:
● Complex types
● Collection of complex types
● Simple types
● Collection of simple types
● Void
Resource Path Path of the resource (entity) that you want to perform the
operation on.
Choose Select to launch the Model
Fields The fields in the entity that you want to modify. You can add
this using the Model Operation Wizard [page 551].
This field is available for PUT and POST operations.
Query Options Additional options that you want to add to the query like
$top or how to order the results using orderby. You can add
This field is available for GET operations.
this using the Model Operation Wizard.
Custom Query Options Query options that are specific to the SuccessFactors OData
V2 service like purge.

Pagination Allows you to set the type of pagination for your query re
sults.
By default the value is set to Server Snapshot-Based The

other values are :
● Client : For UI Application based Integrations.

● Server Cursor-Based
For Server side pagination, Session re-use should be set to

Mandatory. If it is set to None, deployment will fail with a
validation error.
 Remember
For more information, see Pagination.
Page Size Maximum number of records in one page of results fetched

from the service. If set to Zero or empty, it will fetch the de
fault page size.
Retry on Failure This option enables you to mitigate intermittent network is
sues. By selecting this, you enable the integration flow to re
try connecting to the SuccessFactors OData V2 service in
case of network issues. The system retries connection every
3 minutes for a maximum of 5 times. The retry happens for
the following scenarios:
● Upsert: For 412 inner error code along with HTTP re
sponse code 200
● Query Operations: Retry will be for 502, 503, 504 HTTP
response codes corresponding to Create, Update and
Delete operations respectively.
Process in Pages The message is processed in pages of size defined in the

Page Size field.
 Remember
Enable this option only if you are using the SuccessFac
tors OData V2 receiver adapter in a Local Integration
Process invoked by a Looping Process Call.
For more information on a on how to use this option, re

fer to the blog Handling Large Data With SAP Cloud Plat
form Integration OData V2 Adapter .
Timeout (in min) Maximum time the system waits for a response before ter
minating the connection.

Modeling Operation
This adapter provides a wizard for modeling operations easily. It is recommended that you use this wizard to
ensure that the operation does not contain any errors. There are two main steps in this wizard:
1. Connect to System: In this step, you provide the details required for connecting to the web service that you
are accessing.
2. Select Entity and Define Operation: In this step, you select the operation you want to perform and the entity
on which you want to perform the operation on. After selecting the entity, you also select the fields, filtering
and sorting conditions.
3. Configure Filter & Sorting: This step is available only for data fetch operations, where you can define the
order in which the records are fetched in the response payload and filter for the fields that you require.
Connect to System
Field Description
Connection Source You can choose between Remote and EDMX.
If you choose Remote, you have to manually specify all the

details like address and authentication details.
If you choose Local EDMX File, you select the service defini-
tion EDMX file which contains all these details that you
specified manually when you selected Remote.
Local EDMX File Choose Select to select the EDMX service schema. You can
also manually upload it from your local file system.
Enabled only if you select Connection Source as Local EDMX
File.
Address URL of the service that you want to access. If you are con
necting to an on-premise system, enter the Virtual Host in
your Cloud Connector installation.
Proxy Type Type of proxy that you want to use to connect to the service.
Enabled only if you select Connection Source as Remote.
Location ID Location ID that you have configured in the Cloud Connector

installation.
Enabled only if you select Proxy Type as On-Premise.
Authentication Only Basic authentication is supported. You can deploy cre

dentials in (Operations View) and provide the Credential
Name or provide the Username and Password.

Select Entity & Define Operation
Field Description
Operation Select the operation that you want to perform.

not supported:
● Complex types
● Simple types
● Void
Function Import can also be consumed in the $batch mode.
Sub-Levels Sub-levels of the entity that you want to access. For exam
ple, if you want to access the field Description in the entity
Products, and the field is located at Category Products
Description , you select the Sub Levels as 3 since the

field you want to access is at the third level.
Select Entity Entity that you want to perform the operation on.
Fields Fields associated with the entity that you want to perform
the operation on.
Top Specifies the top 'n' number of entries to be fetched.
For more information, see Top System Query Option ($top)

in OData V2 URI Conventions
Skip Specifies the top 'n' number of entries to be skipped and the
rest of the entries are fetched.
For more information, see Skip System Query Option

($skip) in OData V2 URI Conventions .
This step is available only for data fetch operations, Query(GET) and Read(GET).

Configure Filter & Sorting
Field Description
Filter By Select the field that you want to use as reference for filtering,
choose the operation (ex: Less Than or Equal), and provide a
value.
 Note
The IN operation is available under filtering when editing
the query manually. This operation is not available in the
Query Modelling wizard.
Sort By Select the field that you want to use as sorting parameter
and choose Ascending or Descending order.

SuccessFactors (REST) Adapter
Prerequisites
● You selected the REST message protocol when you assigned the SuccessFactors adapter.
Context
The SuccessFactors adapter enables you to communicate with the SuccessFactors system. You use the REST
message protocol to connect to the REST-based Web services of the SuccessFactors system.
You use this procedure to configure a communication channel with the SuccessFactors adapter.
Procedure
3. On the General tab, provide channel name and description in the relevant fields if required.

4. Go to the Adapter Specific tab and provide values in the fields based on the descriptions in the following
table.
Field Name and Description for SuccessFactors REST Adapter Processing Details
Field Description
Address URL of the SuccessFactors LMS service
Address Suffix URL suffix for the SuccessFactors LMS service
Credential Name Name of the credentials deployed on the SuccessFactors

LMS service for authentication
Factors system.
If you choose Manual, you need to enter values for the

Operation Operation that you want to perform
 Note
You can only perform GET operations on the sender
channel.
Entity LMS entity that you are accessing
 Note
See the relevant LMS API documentation for more de
tails.
Parameters Operation parameters that you want to send
Page Size Maximum number of records on each page of response
5. If you are configuring the sender channel, go to the Scheduler tab and provide values in the fields based on
the descriptions in the following table.
Run Once NA Select to execute the operation imme

diately after deploying the integration
content.






days of the week on which you want
the operation to be executed. Also,
specify the time or interval for the
schedule to recur.

you want the operation to be exe
cuted. Also indicate the time or the in
terval for the schedule to recur.
6. Save or deploy your configuration.

SuccessFactors (OData V4) Adapter
Context
The SuccessFactors adapter enables you to communicate with the SuccessFactors system. You use the OData
V4 message protocol to connect to the OData V4-based Web services of the SuccessFactors system.
 Note
The OData V4 message protocol for the SuccessFactors adapter is only available in the receiver channel.

 Tip
● If your input payload contains nodes without data, the output also contains empty strings. If you want
to avoid empty strings in the output, ensure that the input payload does not contain any empty nodes.
● You can use headers and exchange properties in the adapter settings to dynamically pass values during
runtime. More information: Headers and Exchange Properties Provided by the Integration Framework
[page 856].
Procedure
1. Choose Adapter Specific tab and provide values in the fields based on the descriptions in the table below.
Field Description

connect to.
Factors system.
Currently, you can only choose Internet as the proxy type.
dropdown list.
Query(GET), Create(POST), and Update(PUT) operations

are currently supported.
Resource Path Provide the resource path of the entity that you want to
access.
Query Options Query options that you want to send to the OData V4 serv
ice with operation details. (Relevant for Query(GET) oper
ation only)
2. Save or deploy your changes.
4.15.4.8 AS2 Adapter
You use the AS2 adapter to exchange business documents with your partner using the AS2 protocol. You can
use this adapter to encrypt/decrypt, compress/decompress, and sign/verify the documents.

 Note
If you (the tenant admin) want to provision the message broker to use AS2 adapter scenarios, you must
have the Enterprise Edition license. You have to set up a cluster to use the message broker. For more
information, see .
 Note
There are certain limitations with regard to the usage of JMS resources.
More information: Optimizing the Usage of JMS Resources [page 651]
 Caution
 Restriction
If you deploy an integration flow in SAP Cloud Platform Integration, it deploys in multiple IFLMAP worker
nodes. Polling is triggered from only one of these nodes. The message monitor displays the process status
for the worker nodes in which the Scheduler has not started. This results in the message monitor displaying
messages with less than a few milliseconds, where the scheduler was not triggered. These entries contain
firenow=true in the log. You can ignore these entries.
 Note
When you deploy an integration flow with AS2/ AS2 MDN adapter, you can see the endpoint information of
this integration flow in Manage Integration Content section of the operations view.
4.15.4.8.1 Configure the AS2 Sender Adapter
 Note
 Note
● If you are configuring the sender channel to receive AS2 messages, select the AS2 message protocol.
● If you are configuring the sender channel to receive asynchronous AS2 MDN, select the AS2 MDN
message protocol.
● If you want to call the AS2 sender channel, then use the pattern http://<host>:<port>/as2/as2;
to call the AS2 MDN sender channel, use http://<host>:<port>/as2/mdn .

● The JMS queue name contains the name of the AS2 sender channel. provide this name in a to make
troubleshooting easier. To analyze a troubleshooting scenario better, we recommend to mention the
name of the AS2 sender channel.
● The expiration period for stored messages is 90 days, after which the messages are deleted.
● The retention threshold for alerting is two days, by which the messages have to be fetched before an
alert is raised.
Once you have created a sender channel and selected the AS2 adapter, you can configure the following
attributes.
Processing
Message ID Left Part Specify the left side of the AS2 message ID. Regular expres
sion or '.*' is allowed.
Message ID Right Part Specify the right side of the AS2 message ID. Regular ex
pression or '.*' is allowed.
Partner AS2 ID Specify your partner's AS2 ID. Regular expression or '.*' is al
lowed.
Own AS2 ID Specify your own AS2 ID. Regular expression or '.*' is al
lowed.
Message Subject Specify the AS2 message subject. Regular expression or '.*'
is allowed.
Number of Concurrent Processes Define how many processes can run in parallel for each
worker node. The value depends on the number of worker
nodes, the number of queues on the tenant, and the incom
ing load, and must be less than 99.

Authorization Select User Role if you want to authorize a sender based on

the roles defined on the tenant for the user associated with
the inbound request. You can use this option together with
the following authentication options:
● Basic authentication (using the credentials of the user)

The authorizations for the user are checked based on
user-to-role assignments defined on the tenant.
● Client-certificate authentication and certificate-to-user
mapping
The authorizations for the user derived from the certifi-
cate-to-user mapping are checked based on user-to-
role assignments defined on the tenant.
Select Client Certificate if you want to authorize a sender

based on a certificate. If you select this option, you have to
add and enter the Subject DN (information used to authorize
the sender) and Issuer DN (information about the Certificate
Authority that issues the certificate). You can use this option
together with the following authentication option: Client-cer
tificate authentication (without certificate-to-user mapping).
AS2 Sender Adapter with Role Based Authentication only,

support Certificate to User Mapping and hence call from
AS2 partner should be sent using Client Certificate Authenti
cation.
User Role The user role that you are using for inbound authorization.
Choose Select to get a list of all the available user roles for
This field is enabled if you select User Role for Authorization.
your tenant and select the one that you want to use.
The default value is ESBMessaging.send. This role au

thorizes a sender system to process messages on a tenant.
 Caution
The role name must not contain any umlaut characters
(for example, ä).
For more information on user roles, see .
Client Certificate Authorization The client certificates that you are using for inbound authori
zation. Choose Add to add a new row and then choose Select
This field is enabled if you select Client Certificate for
to select a certificate stored locally on your computer. You
Authorization.
Message Settings

Mandatory File Name Select to check the incoming AS2 message contains a file-
name. If not found, then an negative MDN is sent as per the
request of the AS2 sender.
Duplicate Message ID Select to ensure that the AS2 message with the same mes
sage ID is not processed more than once.
Define the Persist Duration instant in minutes to store mes

sages for duplicate check. You can also select the appropri
ate MDN Response type when you encounter duplicate file-
name.
Duplicate File Name Select to ensure that the AS2 message with the same file-
name is not processed more than once.
Define the Persist Duration instant in minutes to store mes

sages for duplicate check. You can also select the appropri
ate MDN Response type when you encounter duplicate file-
name.
 Note
● Ensure that the combination of Message ID Left Part, Message ID Right Part, Partner AS2 ID, Own AS2
ID, and Message Subject parameters is unique across all AS2 sender channels.
● If you use regular expressions for the above-mentioned AS2 sender parameters, then you must ensure
that the regular expression configuration is unique across the endpoints.
● The runtime identifies the relevant channel and integration flow for the incoming AS2 sender message
based on the above-mentioned parameters.
Security
Message Security
Decrypt Message Select to ensure that the message is decrypted.
You can also set the value of this attribute dynamically using
the header SAP_AS2_Inbound_Decrypt_Message.
● true
● false
 Note
If the header value is set, it takes precedence over the
actual value configured in the channel.

Private Key Alias Specify the private key alias to decrypt the AS2 message.
This field is enabled if you select Decrypt Message.
Verify Signature Select to ensure that the signature is verified using one of
● Not Required
● Trusted Certificate: Used to verify the Signature.
● Trusted Root Certificate: The trust chain begins with the
use of the public alias as an intermediate certificate to
verify the inbound certificate. After successful verifica-
tion the inbound certificate is used to verify the Signa
ture.
 Note
If Trusted Root Certificate is selected mention the
public key alias immediate root certificate of the in
coming message.
When verification is successful by using trusted root

certificate the following exchange properties are gener
ated:
○ SAP_AS2_Inbound_Certificate
○ SAP_AS2_Inbound_Certificate_DN
the header SAP_AS2_Inbound_Verify_Signature.
 Note
Public Key Alias Specify the public key alias to verify the signature of the AS2
message.
This field is enabled if you select Verify Signature.
MDN
Private Key Alias for Signature Specify the private key alias to sign the MDN on partner's re
quest.
Signature Encoding Select the MDN signature encoding type.

Proxy Type Select the type of proxy you want to use to connect asyn
chronously to an AS2 sender system.

● Select On-Premise if you are connecting to an on-prem
ise system.
 Note
○ Do not use an HTTPS address for Location ID,
○ Do not use Certificate-Based Authentication as
the Authentication Type, as it leads to errors
when performing consistency checks or during
deployment
 Note
SAP Cloud Connector to connect to your on-prem
ise system, the Location ID field of the adapter re
fers a virtual address which has to be configured in
the SAP Cloud Connector settings.
Authentication Select the authentication type for asynchronous MDN.
You can select one of the following authentication methods:
● None
The tenant authenticates itself against the receiver us
ing user credentials (user name and password).
It is a prerequisite that user credentials are specified in
a Basic Authentication artifact and deployed on the re
lated tenant.
Timeout (in ms) Specify how long in milliseconds the client has to accept the
asynchronous MDN. Enter the value '0' if you want the client
to wait indefinitely.

Delivery Assurance
Quality of Service Defines how the message from the AS2 sending partner is
processed by the tenant.
Based on your requirements you can select one of the fol

lowing options:
● Exactly Once
The AS2 message is temporarily stored in the JMS
queue and an MDN is transmitted to the sending part
ner. If an error occurs during processing, the message is
retried from the JMS queue.
● Best Effort
This option allows you to transmit customized MDN ac
knowledgments to the AS2 sending partner. The AS2
messages are processed immediately and the MDN is
only transmitted to the sending partner if the process
ing is successful.
By introducing a Script into the integration flow, you
can customize the original MDN found in the exchange
property SAP_AS2_MDN. For more information, see
Define Script [page 785].
Retry Interval (in min) Define how many minutes to wait before retrying message
delivery.
Exponential Backoff Select this checkbox to double the retry interval after each
unsuccessful retry.
Maximum Retry Interval (in min) Specify the maximum amount of time to wait before retrying
message delivery.
Dead-Letter Queue Select this checkbox to place the message in the dead-letter
queue if it cannot be processed after two retries.
This creates a lock entry, which you can view and release in
the Message Monitoring application under Manage Locks.
Encrypt Message During Persistence Select this option to encrypt the message in the data store.
Conditions (only for AS2 sender)
The parameters in Maximum Message Size allows you to set a maximum size limit for processing inbound messages. All
inbound messages that exceeds the configured limit are rejected from further processing and the sender receives an error
message.
 Note
The minimum allowable size limit is 1MB.

Body Size (in MB) Define the allowable size limit for processing the message
body.
Attachments Size (in MB) Define the allowable size limit for processing the attach
ment.
Save your settings.
● The AS2 sender passes the following headers to the integration flow for message processing:
○ AS2PartnerID
○ AS2OwnID
○ AS2MessageSubject
○ AS2Filename
○ AS2MessageID
○ AS2PartnerEmail
● The AS2 MDN sender passes the following headers to the integration flow for message processing:
○ AS2PartnerID
○ AS2OwnID
○ AS2MessageID
○ AS2OriginalMessageID
● Use the following attributes to reference the values that are associated with MPL:
○ AS2 MDN sender adapter attributes:
○ AdapterId
○ MDNStatus
○ Message Id
○ ErrorDescription
For example:
{AdapterId=AS2 MDN Sender,

adapterMessageId=<qwesdt_123sourcewe_AS2-1479283341389-0@endionAS2_CPIAS2>,
MDNStatus=error,
Message Id=<c31b53255-d799-4219-9f1c-5e63a044e4@CPIAS2>,
ErrorDescription=insufficient-message-security}

○ AdapterId
○ ReceiverAS2Name
○ MDNType
○ MDNStatus

○ MPL ID
○ MDNRequested
○ SenderAS2Name
○ AS2MessageID
For example:
adapterMessageId=<define _AS2-147665710-6@endionAS2_CPIAS2>,
MDNType=Sending,
MDNStatus=Success,
MPL ID=AFgsPspcD-eYhvHFdfOZYKydBmzw,
MDNRequested=Synchronous,
SenderAS2Name=endionAS2,
AS2MessageID=<define _AS2-147665710-6@endionAS2_HCIAS2>}

○ AdapterId
○ ReceiverAS2Name
○ MDNType
○ MDNStatus
○ MPL ID
○ MDNRequested
○ SenderAS2Name
○ AS2MessageID
For example:
adapterMessageId=<define_AS2-14798922282-7@gibsonAS2_HCIAS2>,
MDNType=Sending,
MDNStatus=Success,
MPL ID=AFgsQ0_3KdRx-UiOjcwGruy6Xw4V,
SenderAS2Name= gibsonAS2,
AS2MessageID=<define _AS2-14798922282-7@ gibsonAS2_HCIAS2>}
4.15.4.8.2 Configure the AS2 Receiver Adapter
 Note

Once you have created a receiver channel and selected the AS2 adapter, you can configure the following
attributes.
Processing
File Name Specify the AS2 file name. If no file name is specified, the de
fault file name <Own AS2 ID>_File is used. Simple ex
pressions, ${header.<header-name>}, or $
{property.<property-name>} are allowed.
Message ID Left Part Specify the left side of the AS2 message ID. Regular expres
sion or '.*' is allowed.
Message ID Right Part Specify the right side of the AS2 message ID. Regular ex
pression or '.*' is allowed.
Own AS2 ID Specify your own AS2 ID. Regular expression or '.*' is al
lowed.
Partner AS2 ID Specify your partner's AS2 ID. Regular expression or '.*' is al
lowed.
Message Subject Specify the AS2 message subject. Regular expression or '.*'
is allowed.
Own E-Mail Address Specify your own e-mail ID. Simple expressions, $
{header.<header-name>}, or $
Content Type Specify the content type of the outgoing message. For exam
ple: application/edi-x12. Simple expressions, $
{header.<header-name>}, or $
the header SAP_AS2_Outbound_Content_Type.
 Note
Custom Headers Pattern Specify a regular expression to pick message headers and
add them as AS2 custom headers.
For example, if you want to pick all EDI headers starting with
the name EDI, specify the expression as EDI.*.
Content Transfer Encoding Specify the AS2 message encoding type.

 Note
● Ensure that the combination of Message ID Left Part, Message ID Right Part, Partner AS2 ID, Own AS2
ID, and Message Subject parameters is unique across all AS2 sender channels.
● If you use regular expressions for the above-mentioned AS2 sender parameters, then you must ensure
that the regular expression configuration is unique across the endpoints.
● The runtime identifies the relevant channel and integration flow for the incoming AS2 sender message
based on the above-mentioned parameters.
Security
Message Security
Compress Message Select this checkbox to ensure that the outgoing AS2 mes
sage is compressed.
the header
SAP_AS2_Outbound_Compress_Message.
● true
● false
 Note
Sign Message Select this checkbox to ensure that the outgoing AS2 mes
sage is signed.
the header SAP_AS2_Outbound_Sign_Message.
● true
● false
 Note

Algorithm Select the AS2 message signing algorithm.
This field is enabled if you select Sign Message. You can also set the value of this attribute dynamically using
the header
SAP_AS2_Outbound_Signing_Algorithm.
● SHA1
● SHA224
● SHA256
● SHA384
● SHA512
● MD5
 Note
Private Key Alias Specify the private key alias to sign the AS2 message. Sim
ple expressions, ${header.<header-name>}, or $
This field is enabled if you select Sign Message.
the header
SAP_AS2_Outbound_Signing_Private_Key_Ali
as.
Encrypt Message Select this checkbox to ensure that the message is en
crypted.
the header SAP_AS2_Outbound_Encrypt_Message.
● true
● false
 Note

Algorithm Select the AS2 message encryption algorithm.
This field is enabled if you select Encrypt Message. You can also set the value of this attribute dynamically using
the header
SAP_AS2_Outbound_Encryption_Algorithm.
● 3DES
● AES128
● AES192
● AES256
● RC2
 Note
Public Key Alias Specify the public key alias to encrypt the AS2 message.
Simple expressions, ${header.<header-name>}, or $
This field is enabled if you select Encrypt Message.
{property.<property-name>} are allowed. The
header or property can contain a public key alias or X509
certificate.
Key Length Specify the public key length.
This field is enabled if you select Encrypt Message and select
the header
RC2 in the Algorithm field.
SAP_AS2_Outbound_Encryption_Key_Length.
 Note
MDN
Type Enable this option to request the partner to send a Message

Integrity Check (MIC) in AS2 MDN.
the header SAP_AS2_Outbound_Mdn_Type.
 Note

Target URL Specify the URL where the AS2 MDN will be received from
the partner. Simple expressions, ${header.<header-name>},
This field is enabled if you select the Asynchronous MDN
or ${property.<property-name>} are allowed.
type.
Request Signing Enable this option to request the partner to sign AS2 MDN.
This field is enabled if you select the Asynchronous or You can also set the value of this attribute dynamically using
Synchronous MDN type. the header
SAP_AS2_Outbound_Mdn_Request_Signing.
Algorithm Select the algorithm.
This field is enabled if you enable the Request Signing option. You can also set the value of this attribute dynamically using
the header
SAP_AS2_Outbound_Mdn_Signing_Algorithm.
 Note
Verify Signature You can enable this option to verify the signature of AS2
MDN.
This field is enabled if you select the Synchronous MDN type.
the header
SAP_AS2_Outbound_Mdn_Verify_Signature
Public Key Alias Specify the public key alias to verify the MDN signature. Sim
ple expressions, ${header.<header-name>}, or ${prop
This field is enabled if you select Verify Signature.
erty.<property-name>} are allowed. The header or property
can contain a public key alias or X509 certificate.
Request MIC Enable this option if you want to request an integrity check.
the header SAP_AS2_Outbound_Mdn_Request_Mic.
Verify MIC Enable this option to verify the MIC of AS2 MDN.
This field is enabled if you select the synchronous MDN type. You can also enable this option if you enable the Request
MIC option and want to verify the integrity of the message.
the header SAP_AS2_Outbound_Mdn_Verify_Mic.
 Note
● You can configure the AS2 receiver channel for the Request-Reply integration flow element. If you
request synchronous MDN, the adapter sets the received MDN response as the message payload.

● If you request synchronous MDN in the receiver channel, you may receive positive or negative MDN. In
both cases, the status of the message on the Message Monitoring tab is COMPLETED. You can process
the MDN message on your own and take the required action for positive or negative MDN, post AS2 call
for synchronous MDN.
● In an MDN message, positive MDN is represented as follows:
 Sample Code

<MDNDeliveryReport>
................
...............
<Disposition>
<DispositionMode ActionMode="automatic-action" SendingMode="MDN-sent-
automatically"/>
</Disposition>
<ReceivedContentMIC mic="9I2W0DSFpQOVRH75/1sLGpWAgtc=" alg="sha1"></
ReceivedContentMIC>
● In an MDN message, negative MDN is represented as follows:
 Sample Code

<MDNDeliveryReport>
................
................
<Disposition>
<DispositionModifier>error</DispositionModifier></Disposition>
<Error>insufficient-message-security</Error>
</Disposition>
<ReceivedContentMIC mic="9I2W0DSFpQOVRH75/1sLGpWAgtc=" alg="sha1"></
ReceivedContentMIC>
● If MDN signature validation fails or an incorrect message integrity check (MIC) is received, the status of
the message is FAILED.
Save your settings.

4.15.4.9 AS4 Receiver Adapter
Provides basic insights on how the AS4 messaging protocol enables message exchange between message
service handlers (MSHs).
Use
The SAP Applicability Statement 4 (AS4) receiver adapter is a secure, reliable, and payload-agnostic protocol.
It uses Web services to transmit business-to-business documents. For more information on AS4 conformance
profile defined by OASIS standard, see AS4 Profile of ebMS 3.0 Version 1.0 .
The SAP AS4 receiver adapter uses the Light Client conformance profile to address the functional
requirements of e-commerce and e-governance services. The profile only supports message pushing for
sending MSH and selective message pulling for receiving MSH. The adapter uses secure SAML tokens for
authentication and authorization between two MSHs.
Message Exchange Patterns (MEPs)
The AS4 receiver adapter uses the following message exchange patterns (MEPs) for exchanging business
documents:
● One-way/push: In this pattern, the AS4 receiver adapter is the sending MSH (initiator) that transfers
business documents to the receiving MSH. The initiator receives a acknowledgment as part of the HTTP
response.
● One-way/selective pull: In this pattern, the AS4 receiver adapter is the receiving MSH (initiator) and sends
a selective pull request to the sending MSH. The sending MSH initiates the pull request by identifing the
specific user message using the message ID provided by the initiator.

Visit the blog , to understand how to integrate Business-to-Authority (B2A) Manager of SAP with ATO
(Australian Taxation Office).
Related Information
Configure Receiver Channel with Push Message Protocol [page 573]

Configure Receiver Channel with Pull Message Protocol [page 578]
4.15.4.9.1 Configure Receiver Channel with Push Message

Protocol
Configure the AS4 receiver channel as a sending Message Service Handler (MSH) to send business
documents.
Prerequisites
● You must deploy the private key pair in theCloud Integration keystore for signing the AS4 message.
● You must have configured an integration flow in the editor. For more information, see New and Improved
Integration Flow Editor for SAP Cloud Platform Integration [page 485].
Context
Use the ebMS3 Push message protocol to transmit AS4 message.

Connection
Configure the Connection Details of the Receiving MSH
Field Description
Address Define the endpoint URL of the receiving MSH.
Agreement Define the type of the message exchange pattern as agreed

between the MSHs for a specific type of business transac
tion.
Authentication Type Select the authentication type to process the outbound

message:
● None
● SAML Authentication
the header
SAP_AS4_Outbound_Authentication_Type.
● saml
● basic
● clientCert
● none
SAML Endpoint URL Provide the specific endpoint URL to support SAML-based
authentication that allows access to the sending MSH.
Private Key Alias Determine the private key alias for SAML authentication.
Timeout (in sec.) Provide a connection timeout period (in seconds) to define
how long the receiving MSH waits for the AS4 message to be
received by the sending MSH.
Processing
Configure the Initiator and Responder Party Details
Field Description
INITIATOR PARTY
Party Type Provide the type of the sending MSH. For example:
http://abr.gov.au/PartyIdType/ABN
Party ID Define the ID of the sending MSH.

Field Description
Role Define the role of the sending MSH. For example: http://
sbr.gov.au/ato/Role/Business
RESPONDER PARTY
Party Type Provide the type of the receiving MSH. For example:
http://abr.gov.au/PartyIdType/ABN
Party ID Define the ID of the receiving MSH.
Role Define the role of the receiving MSH. For example: http://
sbr.gov.au/agency
BUSINESS AND PAYLOAD
Service Define the business service of the recipient. For example,

payment details of employees for a specific year: http://
sbr.gov.au/ato/payevnt/2017
Action Define the type of action that the user message is intended
to invoke. For example: Submit.002.00
Additional Properties Define a key and value to modify an existing parameter in the
property sheet. For example, if you want to modify the MSH
details, you must define a key and its value.
Security
Configure to Ensure the Message is Encoded
Field Description
SIGNING AND ENCRYPTION
WS-Security Type Ensures security implemented in web services for SOAP

based messages.
Sign and Enrypt Message Used to sign and encrypt the payload.
You can also set the value of this attribute dynamically by us
ing the header SAP_AS4_Outbound_Security_Type.
● sign
● signAndEncrypt
● none

Field Description
Private Key Alias for Signing Specify an alias for the tenant private key that is to be used
to sign the message. The tenant private key is used to sign
the request message (that is sent to the WS provider (re
ceiver)). The tenant private key has to be part of the tenant
keystore.
Sign Message Ensures that the outgoing AS4 message is signed.
ing the header SAP_AS4_Outbound_Sign_Message.
● true
● false
Private Key Alias If you select Sign Message, this field is enabled. Specify the
private key alias to sign the AS4 message.
Signature Algorithm Use the relevant algorithm to sign the AS4 message.
ing the header
SAP_AS4_Outbound_Signing_Algorithm.
● sha256rsa
● sha384rsa
● sha512rsa
Public Key Alias for Encryption Specify an alias for the public key that is to be used to en
crypt the message.
The receiver (WS provider) public key is used to encrypt the

request message (that is sent to the receiver). This key has
to be part of the tenant keystore.
ing the header
SAP_AS4_Outbound_Encryption_Cert. Use this
header to set the certificate value to X509 certificate object.

Field Description
Encryption Algorithm Specify a encryption algorithm to be applied when encrypt

ing the message.
the header
SAP_AS4_Outbound_Encryption_Algorithm.
● aes128gcm
● aes256gcm
● tripledes
Receipt
Configure to Ensure the Message is Signed and Verified
Field Description
SIGNING AND VERIFICATION
Save Incoming Receipt Saves incoming receipt in the Message Store for 90 days.
You can refer these receipts for auditing purposes.
the header SAP_AS4_Outbound_Save_Receipt.
● true
● false
Verify Receipt Signature Verifies the incoming receipt signature against the public key
alias.
the header SAP_AS4_Outbound_Verify_Receipt.
● true
● false
 Note
You can use the
SAP_AS4_Outbound_Verify_Receipt_Cert
header to set the certificate value to X509 certificate
object.
 Note
Set the value, provided by ATO, to the SAP_AS4_Outbound_ATO_SAML_AppliesTo header for AppliesTo
parameter to fetch SAML token from Vanguard.

Related Information
4.15.4.9.2 Configure Receiver Channel with Pull Message

Protocol
Configure the AS4 receiver channel as a receiving MSH to exchange business documents.
Prerequisites
● You must deploy the public certificate in the Cloud Integration keystore for verification of the business
response.
Context
Use the ebMS3 Pull message protocol to receive AS4 message (User Message).
Connection
Configure the connection details of the sending MSH
Field Description
Agreement Define the operation mode agreed on by the MSHs for a spe
cific type of business transaction. This specifies the type of
the message exchange pattern.
Address Define the endpoint URL of the sending MSH.
Reference Message ID Define the reference ID of the signal message.
SAML Endpoint URL Provide the specific endpoint URL to support SAML-based
authentication that allows access to the sending MSH.
Private Key Alias Determine the private key alias for SAML authentication.
Timeout (in sec.) Provide a connection timeout period (in seconds) to define
how long the sending MSH waits for the AS4 message to be
received by the receiving MSH.

Security
Configure to ensure that the message is compressed and encoded
Field Description
Sign Message Ensures that the outgoing message is signed.
ing the header SAP_AS4_Inbound_Sign_Message.
● true
● false
Private Key Alias If you select Sign Message, this field is enabled. Specify the
private key alias to sign the AS4 message.
ing the header
SAP_AS4_Inbound_Signing_Algorithm.
● sha256rsa
● sha384rsa
● sha512rsa
Verify Signature Ensures that the signature is verified.
ing the header SAP_AS4_Inbound_Verify_Sign.
● true
● false
Public Key Alias If you select Verify Signature, this field is enabled. Provide
the public key alias to verify the signature of the AS4 mes
sage.
 Note
Set the value, provided by ATO, to the SAP_AS4_Outbound_ATO_SAML_AppliesTo header for AppliesTo
parameter to fetch SAML token from Vanguard.
Related Information

4.15.4.10 AS4 Sender Adapter
Use AS4 message exchange protocol to securely process incoming business documents using Web services.
The SAP Applicability Statement4 (AS4) sender adapter is based on the ebMS specification that supports the
ebMS handler conformance profile. For more information, see AS4 Profile of ebMS 3.0 Version 1.0 .
Let's look at how a message is processed: the incoming AS4 message consists of a SOAP body and the
business payload as an attachment. During processing, the payload is extracted from the attachment and
allocated to the related Camel routes. To get a more detailed understanding of the functionality of the AS4
adapter,explained with a scenario, read the blog on Cloud Integration – Working with AS4 adapter .
 Note
It is expected that the incoming AS4 message has an empty SOAP body, otherwise processing-related
errors can occur.
Configure the sender channel with the AS4 adapter as a receiving Message Service Handler (MSH).
Connection
Configure the Connection Details of the Receiving MSH
Field Description
Agreement Define the message exchange pattern agreed between the

MSHs. For example, urn:fdc:peppol.eu:
2017:agreements:tia:ap_provider.
Address Specify the relative endpoint of the receiving MSH. For ex
ample, /orders.
User Role Select a role to authorize the user to access the receiving
MSH endpoint.
Processing
Configure the Initiator and Responder Party Details
Field Description
INITIATOR PARTY
Party ID Specify the ID of the initiating partner. For example,

APP_10000000100.
Party Type Specify a party type to identify the initiating partner. For ex
ample, urn:fdc:peppol.eu:
2017:identifiers:ap
Role Specify the role of the initiating partner. For example,

http://docs.oasis-open.org/ebxml-msg/
ebms/v3.0/ns/core/200704/initiator

Field Description
RESPONDER PARTY
Party ID Specify the ID of the responding partner. For example,

APP_10000000200.
Party Type Specify a party type to identify the responding partner. For
example, urn:fdc:peppol.eu:
2017:identifiers:ap
Role Specify the role of the responding partner. For example,

p://docs.oasis-open.org/ebxml-msg/ebms/
v3.0/ns/core/200704/responder
BUSINESS INFO
Service Specify the process identifier of the business document. For

example,
urn:www.cenbii.eu:profile:bii01:ver2.0.
Service Type Specify the process identifier schema of the business docu
ment. For example, cenbii-procid-ublui.
Action Specify the document type identifier of the business docu

ment with the following format:
urn:www.cenbii.eu:profile:bii01:ver2.0 .
Security
Configure to Ensure Message Is Verified and Encoded
Field Description
MESSAGE SECURITY
Verify Signature Select the checkbox to ensure that the signature is verified
using one of the following options:
● Not Required
● Trusted Certificate: Used to verify the signature.
● Trusted Root Certificate: The trust chain begins with the
use of the public alias as an intermediate certificate to
verify the inbound certificate. After successful verifica-
tion, the inbound certificate is used to verify the signa
ture.
 Note
If Trusted Root Certificate is selected, mention the
immediate root certificate of the public key alias of
the incoming message.

Field Description
Public Key Alias Define the public key alias or aliases to verify the signature of
the AS4 message.
This field is enabled if you select Trusted Certificate.
Public Key Aliases
This field is enabled if you select Trusted Root Certificate.
Decrypt Message Select the option appropriate for your requirements to de
crypt an AS4 message.
Receipt
Configure to Ensure Message Is Signed
Field Description
Signing Ensures that the outgoing AS4 message is signed.
Private Key Alias If you select Required, this field is enabled. Specify the pri
vate key alias to sign the AS4 message.
Conditions
Configure to Ensure Message Is Set to a Maximum Size Limit
The parameters in Maximum Message Size allow you to set a maximum size limit for processing inbound messages. Any
inbound message that exceeds the configured limit is rejected from further processing and the sender receives an error
message.
Body Size (in MB) Define the size limit for processing the message body.
Attachment Size (in MB) Define the size limit for processing the attachment.
4.15.4.11 Configure Communication Channel with IDoc

Adapter
Prerequisites
● You have logged into your customer workspace in SAP Cloud Platform Integration web tooling.
● You have assigned the IDoc adapter to the communication channel.

Context
You use the IDoc adapter to communicate IDoc messages with other systems that support communication via
SOAP web services.
Supported Headers (Receiver Adapter):
1. General Headers:
○ SOAPAction Header
2. IDoc specific Headers:
The IDoc Receiver Adapter sends a Request and gets an XML Response.
 Note
This response is standardized. It looks the same for all IDocs, with the exception of the type.
○ SapIDocType <XML Response>

The adapter parses the XML Response and generates the SapIdocType header from it.
.
○ SapIDocTransferId <XML Response>
The adapter parses the XML Response and generates the SapIDocTransferId header from it.
SapIDocTrandferId 0000000000166099
.
○ SapIDocDbId <XML Response>
The adapter parses the XML Response and generates the SapIDocDbId header from it.
SapIDocDbId 0000000000160816
Supported Headers (Sender Adapter):
1. General Headers:
○ SapAuthenticatedUserName
If the sender channel is configured to use client certificate authentication, no such header is set (as it
is not available in this case).
2. IDoc specific Headers:
These headers can be used to generate a response.
○ SapIDocType <XML Response>

○ SapIDocTransferId <XML Response>
SapIDocTrandferId 0000000000166099
.
○ SapIDocDbId <XML Response>
SapIDocDbId 0000000000160816
 Note
○ If the receiver adapter was not an IDoc adapter, these headers are not provided. So a standardized
response is generated from the request.
○ If the receiver adapter was an IDoc adapter, these headers are provided.
If the type and transfer Id of the message in sender and receiver adapter are the same, and if there
is only one (IDoc) receiver, you can get the response from the headers.
If not, a standardized response is generated from the request.
Procedure
3. In General tab page, provide channel name and description in the relevant fields if necessary.
Parameters and Values of Sender IDoc (IDoc SOAP) Adapter (Connection Details)
Address Relative endpoint address on which ESB Bus listens to the incoming requests, for ex
ample, /HCM/GetEmployeeDetails.
URL to WSDL You can download the WSDL by using the Integration Operations user interface (in the
 Note


 Note
In the following cases cer
tain features might not be
available for your current
integration flow:
ping).
○ A feature for a partic
ular adapter or step
was released after
you created the cor
responding shape in
○ You are using a prod
uct profile other than
the one expected.
More information: Adapter
and Integration Flow Step
Versions [page 406] ○ Client Certificate Authorization
○ User Role
 Note
Note the following:
Platform Cockpit.

Conditions

○ Body Size
○ Attachment Size

Parameters and Values of Receiver IDoc (IDoc SOAP) Adapter (Connection Details)
Address Endpoint address on which the ESB Bus posts the outgo
ing message, for example http://<host>:<port>/payment.
You can dynamically configure the address field of the IDoc

SOAP Adapter.
When you specify the address field of the adapter as $

{header.a} or ${property.a}, at runtime the value of header
a or exchange property (as contained in the incoming
message) will be written into the Camel header CamelDes
tinationOverrideUrl and will be used in runtime to send the
message to.
Also in case the CamelDestinationOverrideUrl header has

been set by another process step (for example, a Content
Modifier), its value will be overwritten.


get system:
tem.
premise system.
 Note
during deployment
 Note
URL to WSDL URL to the WSDL defining the WS provider endpoint (of
the receiver). You can provide the WSDL by:
○ Directly entering /wsdl/<interfacename>.wsdl where
the WSDL is available in src.main.resources.wsdl.
○ Selecting a source to browse for a WSDL, either from
an On-Premise ES Repository or your local work
space.
 Note

IDoc Content Type Application/x-sap.doc

○ Allows only single IDoc record for each request
○ Enables Exactly-Once processing
○ Enables message sequencing
Text/XML
○ Allows multiple IDoc records for each request
Request Timeout Specifies the time (in milliseconds) that the client will wait
for a response before the connection is being interrupted.
Compress Message Enables the WS endpoint to send compressed request

messages to the WS Provider and to indicate the WS Pro
vider that it can handle compressed response messages.
Allow Chunking Used for enabling HTTP chunking of data while sending
messages.
Clean up Request Headers Select this option to clean up the adapter specific- head
ers after the receiver call.

Connect using Basic Authentication Select this option to allow the ESB to connect to the re
ceiver system using the deployed basic authentication cre
dentials. When you select this option, you need to provide
the credential name.
Credential Name: Enter the credential name of the user

name-password pair specified during the deployment of
basic authentication credentials on the cluster.
 Note

○ Externalize all attributes related to the configura-

tion of all options (for example, Authentication

work properly.
ternalized the Authentication Option attribute and only
the Private Key Alias (but no Credential Name), in the
integration flow configuration dialog all authentication
options (Basic, Certificate-Based and None) are se
lectable in a drop-down list. However, when you now
select Basic Authentication from the drop-down list,
no Credential Name can be configured.

Private Key Alias Allows you to enter the private key alias name that gets the
private key from the keystore and authenticates you to the
receiver in an HTTPs communication.
If you have selected the option of Connect using Basic

Authentication, this field is not visible.
You can dynamically configure the Private Key Alias prop

erty by specifying either a header or a property name in
one of the following ways:
Please be aware that in some cases this feature can have a

negative impact on performance.

Authentication You can select one of the following authentication meth

ods:
○ Basic
related tenant.
○ None
 Note
IDoc.
 Note
Please note that the token for principal prop
agation expires after 30 minutes.
If it takes longer than 30 minutes to process

the data between the sender and receiver
channel, the token for principal propagation
expires, which leads to errors in message
processing.
 Note
released after you created the corresponding
shape in your integration flow.

○ You are using a product profile other than the

one expected.

You can dynamically configure the Credential Name field of

the adapter, by using a Simple Expression (see http://
camel.apache.org/simple.html . For example, you can
dynamically define the Credential Name of the receiver
adapter by referencing a message header $
{header.MyCredentialName} or a message prop
erty ${exchangeProperty.MyCredentialName}.
4.15.4.12 OData Adapter
OData adapter allows you to communicate with an OData service using OData protocol. You use messages in
ATOM or JSON format for communication. This OData adapter uses OData V2 message protocol.
In the sender channel, the OData adapter listens for incoming requests in either ATOM or JSON format.
More information: Configure OData Sender Adapter [page 592].
OData adapters only support synchronous communication. In other words, every request must have a
response.
In the receiver channel, the OData adapter sends the OData request in the format you choose (ATOM or JSON)
to the OData service provider.
 Note
In the case of OData service artifacts, OData adapter in the sender channel is not editable. It is
prepopulated with data you have provided when binding OData objects to a data source.
 Tip
4.15.4.12.1 Configure OData Sender Adapter
OData sender adapter supports externalization. To externalize the parameters of this adapter choose
Externalize and follow the steps mentioned in Externalize Parameters of an Integration Flow [page 482].

Adapter Specific
Field Description
Authorization Select User Role if you want to authorize a user to send

OData requests based on the ESBMessaging.send.
Select Client Certificate if you want to authorize a user to

send OData requests based on a certificate. If you select this
option, you have to add and enter the Subject DN (informa
tion used to authorize the sender) and Issuer DN (informa
tion about the Certificate Authority who issues the certifi-
cate).
User Role The user role that you are using for authorization. Choose
Select to get a list of all the available user roles for your ten
This field is enabled only if you select Authorization as User
ant and select the one that you want to use.
Role
For more information on user roles, see .
Client Certificate The client certificate that you are using for authorization.
Choose Add to add a new row and then choose Select to add
This field is enabled only if you select Authorization as Client
the Subject DN and Issuer DN.
Certificate.
EDMX Select the EDMX file that contains the OData service defini-
tion.
Operation Select the operation that you want to perform on the se
lected Entity Set in the OData service.
Entity Set Entity set in the OData service that you want to perform the
operation on.
4.15.4.12.2 Configure OData Receiver Adapter V2
Configure the OData receiver adapter by understanding the adapter parameters.
OData receiver adapter supports externalization. To externalize the parameters of this adapter choose
 Note
● OData adapter supports sending error response in exception subprocess. The error response body will
be part of expression ${in.body}.
● OData services response code is captured in the camelhttpresponsecode header.
● Message headers are converted to HTTP request headers while sending the request to OData server. If
you do not want to send any specific HTTP headers, then you must explicitly remove the headers using
content modifier or by defining a script before OData receiver adapter.
● All the response headers will be converted to message headers. This may overwrite or interfere with
any of headers you have defined in your integration flow, which has to be explicitly handled. For

example, in such a scenario, you should take back-up of your defined headers key and value via script
step.
Connection
Field Description
Address URL of the OData V2 service that you want to connect to.
Proxy Type The type of proxy you want to use for establishing connec
tion with OData V2 service.
Currently, you can choose between Internet (default) and

On-Premise.
Location ID Location ID that you have configured in the cloud connector

installed on your system.
Enabled only if you choose Proxy Type as On-Premise.
Authentication Authentication method that you want to use for connecting

to the OData V2 service. Currently, you can choose between
● None
● Basic
● OAuth2 Client Credentials: Use this a grant type to ac
cess web resources by authorizing the client application
to perform required actions on behalf of an user.
● OAuth2 SAML Bearer Assertion: If you have chosen this
option, the identity of the user associated with the
sender application is forwarded from the sender ac
count to the receiver account.
Enabled only if you choose Proxy Type as Internet.
Credential Name Credential name of the credentials that you have deployed in
Security Material section of (Operations View).
Enabled only if you choose Authentication as Basic, OAuth2
Client Credentials, or OAuth2 SAML Bearer Assertion.
 Note
 Restriction
This option is enabled only if you select client certificate
The values true and false are not supported for this
authentication.
field.
CSRF Protected By default this option is enabled; disable this option if the
service is not CSRF protected

Processing
Field Description
Operation Details The operation that you want to perform on the selected
OData entity or resource.
Resource Path Choose Select to launch the Model Operation wizard. Refer
to table Model Operation for fields and description for
model operation wizard.
 Note
You can also specify the Resource Path parameter dy
namically using a header or a property (with an expres
sion such like ${header.resourcePath}, for ex
ample). Note that, however, XPath expressions are not
supported for this parameter.
 Note
When you use this adapter with the Update or Merge op
eration, use the following format when specifying the
value of the Resource Path parameter:
EntitySetName(key=value) or
EntitySetName(key).
Example (for EntitySetName=Product):
Product(productId='001')
Query Options Query options that you are passing as a part of the URI to
the OData V2 service.
Enabled for Query(GET) and Read(GET) operations.
Fields Fields in the entity that you are performing the operation on.
If you use the Model Operation wizard, the input for this field
Enabled for Create(POST), Merge(MERGE), Patch(PATCH)
is provided by the wizard.
and Update(PUT) operations.
Enable Processing Select to perform multiple operations in one request to the

OData V2 service.
Custom Query Options Additional query options that are not available in the Model
Operation wizard.
Content Type Type of content that you are sending to the OData service.
Available only for Merge(MERGE) and Patch(PATCH) opera

tion.

Field Description
Content Type Encoding Encoding type used for sending content to OData service.
Available only for Merge(MERGE) and Patch(PATCH) opera

tion.
Page Size Maximum number of records that should be fetched in one

page of results.
Timeout (in min) Maximum time the adapter should wait for receiving a re
sponse from the OData V2 service.
HEADER DETAILS Request Headers : Provide the Comma seperated value list of
HTTP request headers that has to be sent to the OData
backend
Response Headers : Provide the comma seperated value list

of HTTP response headers. The received header values will
then be converted to message/exchange headers.
 Note
If the value * is entered, then all the response/request
header values will be fetched.
Metadata Details OData receiver adapter makes a $metadata call, before the
actual endpoint call. Not all headers or query parameters are
passed to the $metadata call. If your service needs some
headers (for example header apikey, which is a customer
authorization header to invoke API endpoints) or parameters
then you can provide the same in the request headers and
query parameters.
Request headers provide comma separated HTTP request

headers to be sent to $metadata call. Custom query param
eters enter key value pair(s) of query parameters, separated
by & in case of multiple entries.
Process in Pages is a checkbox that is enabled only when you are performing the Query(GET) operation. By
selecting Process in Pages, you enable the adapter to process messages. The size of a message is defined by
the value that you specify in Page Size.
IMPORTANT: You should select the Process in Pages checkbox if you are using the adapter in a Local
Integration Process that is invoked by a Looping Process Call step.
In the Looping Process Call, select Expression Type as Non-XML, Condition Expression as $
{property.<receiver.name>.<channel.name>.hasMoreRecords} contains 'true', and Maximum
Number of Iterations as 999.

 Note
You can pass custom HTTP headers to OData receiver if you have defined the header in content modifier or
script element and the element is placed before OData receiver adapter in an integration flow.
Modeling Operation
This adapter provides a wizard for modeling operations easily. It is recommended that you use this wizard to
ensure that the operation does not contain any errors. There are two main steps in this wizard:
1. Connect to System: In this step, you provide the details required for connecting to the web service that you
are accessing.
2. Select Entity and Define Operation: In this step, you select the operation you want to perform and the entity
on which you want to perform the operation on. After selecting the entity, you also select the fields, filtering
and sorting conditions.
3. Configure Filter & Sorting: This step is available only for data fetch operations, where you can define the
order in which the records are fetched in the response payload and filter for the fields that you require.
Connect to System
Field Description
Connection Source You can choose between Remote and EDMX.
If you choose Remote, you have to manually specify all the

details like address and authentication details.
If you choose Local EDMX File, you select the service defini-
tion EDMX file which contains all these details that you
specified manually when you selected Remote.
Local EDMX File Choose Select to select the EDMX service schema. You can
also manually upload it from your local file system.
Enabled only if you select Connection Source as Local EDMX
File.
Address URL of the service that you want to access. If you are con
necting to an on-premise system, enter the Virtual Host in
your Cloud Connector installation.
Proxy Type Type of proxy that you want to use to connect to the service.
Enabled only if you select Connection Source as Remote.
Location ID Location ID that you have configured in the Cloud Connector

installation.
Enabled only if you select Proxy Type as On-Premise.
Authentication Only Basic authentication is supported. You can deploy cre

dentials in (Operations View) and provide the Credential
Name or provide the Username and Password.

Select Entity & Define Operation
Field Description
Operation Select the operation that you want to perform.

not supported:
● Complex types
● Simple types
● Void
Function Import can also be consumed in the $batch mode.
Sub-Levels Sub-levels of the entity that you want to access. For exam
ple, if you want to access the field Description in the entity
Products, and the field is located at Category Products
Description , you select the Sub Levels as 3 since the

field you want to access is at the third level.
Select Entity Entity that you want to perform the operation on.
Fields Fields associated with the entity that you want to perform
the operation on.
Top Specifies the top 'n' number of entries to be fetched.
For more information, see Top System Query Option ($top)

in OData V2 URI Conventions
Skip Specifies the top 'n' number of entries to be skipped and the
rest of the entries are fetched.
For more information, see Skip System Query Option

($skip) in OData V2 URI Conventions .
This step is available only for data fetch operations, Query(GET) and Read(GET).

Configure Filter & Sorting
Field Description
Filter By Select the field that you want to use as reference for filtering,
choose the operation (ex: Less Than or Equal), and provide a
value.
 Note
The IN operation is available under filtering when editing
the query manually. This operation is not available in the
Query Modelling wizard.
Sort By Select the field that you want to use as sorting parameter
and choose Ascending or Descending order.
4.15.4.12.3 Configure OData Receiver Adapter V4
Configure the OData receiver adapter by understanding the adapter parameters.
OData receiver adapter supports externalization. To externalize the parameters of this adapter choose
Connection
Field Description
Address Service root URI of the OData V4 service that you want to
connect to.
Authentication Authentication method that you want to use for connecting

to the OData V4 service. Currently, you can choose between
● None
● Basic
Proxy Type The type of proxy you want to use for establishing connec
tion with OData V4 service.
The value is set as Internet
 Caution
The OData V4 receiver adapter cannot be used together
with SAP Cloud Connector.
Credential Name Credential name of the credentials that you have deployed in
Security Material section of (Operations View).
Enabled only if you choose Authentication as Basic.

Processing
Field Description
Operation The operation that you want to perform on the selected

OData entity or resource.
Resource Path Enter a valid resource path.
Query Options Query options that you are passing as a part of the URI to
the OData V4 service.
Enabled for Query(GET) operation.
4.15.4.13 HTTP Receiver Adapter
You use the HTTP adapter to communicate with receiver systems using HTTP message protocol.
Prerequisites
If you like to send strings with the HTTP receiver adapter which contain non-ASCII characters (for example,
German umlaut or cyrillic characters), make sure that you do the following (using a Content Modifier):
Use the Content-Type header to specify the media type that the receiver can expect (for example, text/
plain for unformatted text).
Set the value of the CamelCharsetName property or header to the desired character set (for example, UTF-8).
 Note
If you don't specify the character set in the proposed way, the HTTP adapter sends ASCII strings. This will
lead to errors when your data contains non-ASCII characters.
Context
The HTTP adapter supports only HTTP 1.1. This means that the target system must support chunked transfer
encoding and may not rely on the existence of the HTTP Content-Length header.
 Note
If you want to dynamically override the configuration of the adapter, you can set the following headers
before calling the HTTP adapter:
● CamelHttpUri

● CamelHttpQuery
● Content-Type
The content type is composed of two parts: a type and a subtype.For example, image/jpeg (where
image is the type and jpeg is the subtype).
Examples:
format
The list of available content types is maintained by the Internet Assigned Numbers Authority (IANA).
For more information, see http://www.iana.org/assignments/media-types/media-types.xhtml .
 Note
If transferring text/* content types, you can also specify the character encoding in the HTTP
header using the charset parameter.
Text data in string format is converted using UTF-8 by default during message processing. If you
want to override this behavior, you can use the Content Modifier step and specify the
CamelCharsetName Exchange property. To avoid encoding issues when using this feature together
with the HTTP adapter, consider the following example configuration:
If you use a Content Modifier step and you want to send iso-8859-1-encoded data to a receiver,
make sure that you specify the CamelCharsetName Exchange property (either header or property)
as iso-8859-1. For the Content-Type HTTP header, use text/plain; charset=iso-8859-1.
HTTP content encoding that indicates the encoding used during message transport (for example, gzip
for GZIP file compression).
This information is used by the receiver to retrieve the media type that is referenced by the content-
type header.
The list of available content types is maintained by the Internet Assigned Numbers Authority (IANA).
For more information, see:http://www.iana.org/assignments/http-parameters/http-

 Note
Adapter tracing is supported for HTTP adapter. For more information, see .
You use this procedure to configure HTTP adapter in receiver channel.
Procedure
2. Choose the receiver channel.

Field Name and Description for HTTP Adapter
Field Description
Address URL of the target system that you are connecting to, for
example, https://mysystem.com
Note that the authentication method Client

Certificate requires the HTTPS protocol. For Basic
authentication it is strongly recommended that you
use the HTTPS protocol.
If you have selected one of these authentication methods,

you therefore have to enter an https URL.
You can also specify HTTP parameters in the URL. How

ever, if you select the HTTP method POST, parameters are
usually sent in the body. You therefore get a warning mes
sage if you configure this parameter-value combination.
The following URL parameters are currently not allowed

for technical reasons:
○ throwExceptionOnFailure
○ bridgeEndpoint
○ transferException
○ client
○ clientConfig
○ binding
○ sslContextParameters
○ bufferSize
You can dynamically configure the Address field of the

HTTP adapter.
When you specify the Address field of the HTTP adapter

as ${header.a}, at runtime the value of header a (as
contained in the incoming message) will be written into
the Camel header CamelHttpUri.
Also in case the CamelHttpUri header has been set by

another process step (for example, a Content Modifier),
its value will be overwritten.


Field Description
Query Query string that you want to send with the HTTP request
Query strings must not be entered in the Address field.
This parameter can be externalized.
You can dynamically configure the Query field of the HTTP

adapter.
When you specify the Query field of the HTTP adapter as

${header.a}, at runtime the value of header a (as con
tained in the incoming message) will be written into the
Camel header CamelHttpQuery.
 Note
If you want to send parameters in the query string of
the HTTP adapter, these parameters must be coded
in a URL-compatible way. Individual parameter-value
pairs must be separated with an ”&” and there must
be an “=” between the name of a parameter and its
value.
Example 1)
parameter1=123, parameter2=abc
You must specify the following in the query field: pa

rameter1=123&parameter2=abc
Example 2)
Manufacturer = Mars Inc. Product = M&M
You must specify the following in the query field: Man

ufacturer =Mars+Inc.&Product=M%26M

Field Description
get system:
tem.
premise system.
 Note
during deployment
 Note

Field Description
Method Action that the HTTP request should perform
○ POST
Requests that the receiver accepts the data enclosed
in the request body.
○ Delete
Requests that the origin server delete the resource
identified by the Request-URl
○ Dynamic
The method is determined dynamically by reading a
value from a message header or property such as $
{header.abc} or ${property.abc} during runtime.
○ GET
Sends a GET request to the receiver.
○ HEAD
Sends a HEAD request which is similar to a GET re
quest but does not return a message body.
○ PUT
Updates or creates the enclosed data on the receiver
side.
○ TRACE
Sends a TRACE request to the receiver that sends
back the message to the caller.
Send Body Select this checkbox if you want to send the body of the
message with the request. For methods GET, DELETE, and
HEAD, the body is not sent by default because some HTTP
tion GET, DELETE, HEAD or "Dynamic".
servers do not support this function.
Expression The expression field allows you to enter a simple expres

sion that specifies the HTTP method for the HTTP call .
For example, you can define that the method is deter
tion Dynamic.
mined dynamically by reading a value from a message
header or property such as ${header.abc} or ${prop
erty.abc}. If the header or property does not exist or its
value is empty, the POST method is used by default.

Field Description
Authentication Defines how the tenant (as the HTTP client) will authenti
cate itself against the receiver.
You can select one of the following authentication meth

ods:
○ None
○ Basic
related tenant.
 Note

○ Externalize all attributes related to the configu-

ration of all options (for example, Authentication

work properly.

Field Description
ternalized the Authentication Option attribute and
only the Private Key Alias (but no Credential Name), in
the integration flow configuration dialog all authenti
cation options (Basic, Certificate-Based and None)
are selectable in a drop-down list. However, when you
now select Basic Authentication from the drop-down
list, no Credential Name can be configured.
 Note
IDOC
 Note
Please note that the token for principal propaga
tion expires after 30 minutes.
If it takes longer than 30 minutes to process the

data between the sender and receiver channel,
the token for principal propagation expires, which
leads to errors in message processing.
For special use cases, this authentication method can

also be used with the AS2 adapter.
 Note
released after you created the correspond
ing shape in your integration flow.
○ You are using a product profile other than
the one expected.

○ OAuth2 SAML Bearer Assertion

Field Description
If you have chosen this option, the identity of the user

associated with the sender application is forwarded
from the sender account to the receiver account.
Enabled only if you choose Proxy Type as Internet.
Credential Name Identifies the User Credential artifact that contains the
credentials (user name and password) for the Basic au
 Note thentication. For OAuth2 SAML Bearer Assertion type au
This field is enabled only if you select for thentication provide the OAuth2 Credential artifact name.
Authentication the option Basic or OAuth2 SAML For more information see, .
Bearer Assertion . You can dynamically configure the Credential Name prop
erty by specifying either a header or a parameter name in
one of the following ways: ${header.headername}
or ${parameter.parametername}. As an example,
you can use a Script step before the adapter where you
look-up the User Credentials and enter the base64-en
coded values for user and password into the header
Authorization. The HTTP adapter will then use this
header in the HTTP request.
Although you can configure this feature, it is not sup

ported when using the corresponding integration content
with the SAP Process Orchestration (SAP PO) runtime in
releases lower than SAP PO 7.5 SP5.
 Note
 Restriction
This option is enabled only if you select client certifi-
The values true and false are not supported for
cate authentication.
this field.

Field Description
Timeout (in ms) Maximum time that the tenant waits for a response before
terminating message processing
Note that the timeout setting has no influence on the

Transmission Control Protocol (TCP) timeout when the re
ceiver or any additional component interconnected be
tween the Cloud Integration tenant and the receiver have a
lower timeout. For example, consider that you have config-
ured a receiver channel timeout of 10 minutes and there is
another component involved with a timeout of 5 minutes.
In case, nothing is transferred for a certain time, the con
nection will be closed after the 5th minute. In HTTP com
munication spanning multiple components (for example,
from a sender, through the load balancer, to a Cloud Inte
gration tenant, and from there to a receiver) the actual
timeout period is influenced by each of the timeout set
tings of the individual components that are intercon
nected between sender and receiver (precisely spoken, of
those components that can control the TCP session). The
component or device with the lowest number set for the
idle session timeout will determine the timer that will be
used.
 Note
In the case of integration flows in OData service artifacts, you can save the integration flow and deploy
the OData service.
Related Information

Script Example for Exception Handling in HTTP Receiver [page 259]

4.15.4.14 HTTPS Sender Adapter
Context
You use the HTTPS sender adapter to communicate with receiver systems using HTTPS message protocol.
 Note
Supported Header:
The following HTTPS request headers for the sample HTTPS endpoint https://
test.bsn.neo.ondemand.com/http/hello?abcd=1234 are added to exchange headers for further
processing in integration flow:
● CamelHttpUrl
● CamelHttpQuery
● CamelHttpMethod
DELETE, and so on.
 Note
● Adapter tracing is supported for HTTPS adapter. For more information, see .
● When you deploy an integration flow with HTTPS sender adapter, you can see the endpoint information
of this integration flow in Manage Integration Content section of operations view.

When you have created a sender channel with HTTPS adapter, you can configure the following attributes:
Connection
Parameters of the HTTPS Sender Adapter
Address Enter the URL of the HTTP system to connect to.
 Note
● Use the following pattern: http://
<host>:<port>/http . This should be ap
pended by the unique address apecified in the
channel.
● The field value supports these characters ~, -, . , $
and * .
● The Address field should start with '/ ' and can con
tain alphanumeric values, '_' and '/ '. For example a
valid address is /test/123.
● In the example mentioned above, you can use ~
only for the address part which succeeds /test/
● You can use $ only at the beginning of the address
after /.
● You can use* only at the extreme end of the ad
dress and no characters are allowed after *. A * can
only be preceded with /.
● You cannot begin address with., - or ~ . Alphanu
meric value or _ must succeed these characters.
● If you are using /*, it implies that uri containing the
prefix preceding the /* is supported. For example. if
the address is /Customer/* then uris supported are
http://<host>:<port>/http/Customer/<Any-url>.
● Uris are case insensitive. So, http://<host>:<port>/
http/test and http://<host>:<port>/http/Test is
treated as same.

● Client Certificate: Sender authorization is checked on

the tenant by evaluating the subject/issuer distin
guished name (DN) of the certificate (sent together with
the inbound request). You can use this option together
with the following authentication option: Client-certifi-
cate authentication (without certificate-to-user map
ping).
● User Role: Sender authorization is checked based on
roles defined on the tenant for the user associated with
the inbound request. You can use this option together
with the following authentication options:
○ Basic authentication (using the credentials of the
user)
The authorizations for the user are checked based
on user-to-role assignments defined on the tenant.
○ Client-certificate authentication and certificate-to-
user mapping
The authorizations for the user derived from the
certificate-to-user mapping are checked based on
user-to-role assignments defined on the tenant.
Depending on your choice, you can also specify one of the

following properties:

Allows you to select one or more client certificates
(based on which the inbound authorization is checked).
Choose Add to add a new certificate for inbound author
ization for the selected adapter. You can then select a
certificate stored locally on your computer. You can also
delete certificates from the list.
For each certificate, the following attributes are dis
played: Subject DN (information used to authorize the
sender) and Issuer DN (information about the certifi-
● User Role
Allows you to enter a role based on which the inbound
authorization is checked.
The role ESBMessaging.send is provided by default. It is
a predefined role provided by SAP which authorizes a
sender system to process messages on a tenant.

CSRF Protected This option prevents Cross-Site Request Forgery (CSRF),

which is a malicious online attack. Such attacks exposes
user content without their authorization.
 Note
Include X-CSRF-Token in the HTTP header field for all
modifying requests and these requests are validated
during runtime. If the validation fails then the server re
turns “HTTP 403 Forbidden” status code.
Conditions
Configure to set size limit
The parameters in Maximum Message Size allows you to set a maximum size limit for processing inbound messages. All
inbound messages that exceeds the configured limit are rejected and the sender receives an error message.
 Note
The minimum allowable size limit is 1MB.
Body Size (in MB) Define the allowable size limit for processing the message
body.
Save the settings.
 Note
● Additional incoming request headers and URL parameters can be added to exchange headers for
further processing in integration flow. You must define these headers and paramters in Allowed
Headers list at integration flow level.
● Once the integration flow processing completes, the HTTPS sender adapter returns header and body
to end user and sets the response code. You can use Content Modifier element to send back specific
http response and customize the response.
● The sample integration flow is as shown below:
● Address URLs for http endpoints across integration flow must be unique. If it is not unique then the
integration flow does not start.
● Adapter returns the following HTTP response code:
○ 200 - Processing is successful

○ 503 - Service is not available
○ 500 - Exception during integration flow processing
Also, you can set the header CamelHttpResponseCode to customize the response code.
● You can invoke the HTTP endpoints using the syntax <Base URI>/http/<Value of address field>. You
can get Base URI value from Services tab in Properties view of a worker node.
Atleast one integration flow with SOAP endpoint must be deployed to view details in Services tab.
● You should useScript element to customise which headers can be sent in response to the HTTP call. It
is a recommendation that you must remove internal headers and sent back only required headers.
● If an exception occurs during the HTTPS call, it is thrown back with a message and MPL ID explaining
the exception, rather than displaying the stack trace.
Related Information
HTTPS Adapter: Example Integration Flow [page 615]
4.15.4.14.1 HTTPS Adapter: Example Integration Flow
Create a simple example integration flow to learn how the HTTPS sender adapter works.
 Note
With the following steps, you can easily modify and extend the basic integration flow that was introduced in
the Getting Started section of this documentation.
More information:
You can easily modify the integration flow described in the Getting Started section by adding a SOAP client as
the sender.
The figure shows the integration flow model that you get as a result of this exercise.

In the modified integration flow, a SOAP client instead of a Timer event triggers message processing.
This is how the integration flow processes the message at runtime:
1. The HTTP client (represented by the Sender shape) sends an HTTP request to
SAP Cloud Platform Integration through an HTTPS sender channel. The HTTPS request body, which is in
JavaScript Object Notation (JSON) format, contains a product identifier.
2. The JSON-to-XML converter transforms the request body into XML format (which can be processed in the
following step, the Content Modifier).
3. The Content Modifier creates a message header (which we also call productIdentifier) and writes the
actual value of the productIdentifier element into it. This header is used in the subsequent step.
4. The Request Reply step passes the message to an external data source and retrieves data (about orders)
from there.
The external data source (which is represented by the lower OData … shape) supports the Open
DataProtocol (OData). We use the publicly available OData test service Northwind, which has the following
address: http://services.odata.org/Northwind/Northwind.svc (see also: https://services.odata.org ).
5. An OData receiver channel is used for the connection to the OData source. To query for exactly one
product (for the product identifier provided with the inbound message), the header that was created in the
preceding Content Modifier is used.
6. The OData service provides the details of one specific product, which is identified by the actual value of the
productIdentifier field (provided with the inbound SOAP message).
7. Finally, the result of the request is forwarded to an e-mail account using the Mail receiver adapter (the e-
mail server is represented by the right Mail … shape in the integration flow model).
Related Information
Create the HTTPS Sender Channel [page 616]

Add the JSON to XML Converter [page 618]
Send the HTTP Request and Process the Integration Flow [page 620]
4.15.4.14.1.1 Create the HTTPS Sender Channel
Add an HTTPS sender channel to enable the integration flow to receive HTTP requests.
1. Select the integration flow and choose Edit.

2. Click the Sender shape. The context icons for the Sender appear.

 Note
If you choose the information iconthe version of the integration flow component is displayed.
Do not confuse the version of an individual integration flow component with the software version of
SAP Cloud Platform Integration. An integration flow component gets a new version each time a new
feature is added to it by SAP. Let's imagine a situation where you started modeling an integration flow
some time ago and now want to continue working on it. Let's assume that SAP has updated the
software in the meantime. A new version of an integration flow step or shape that you have used is now
available, containing a new feature. You can continue to use the old component version, but if you want
to use the new feature you need to update to the new version.
3. Click the arrow icon and drag and drop the cursor on the Start event.
The list of available adapter types is displayed in a dialog.
4. Choose adapter type HTTPS .

The properties of the adapter are shown below the model.
5. Go to the Connection tab.
Specify the following parameters:

○ Address: This parameter defines the endpoint under which the integration flow can be called from the
sender. Start the address with a slash, for example,/FirstFlow.
○ Authorization and User Role: You want to configure your first integration flow so that the inbound
request is authenticated using basic authentication (based on user credentials). To keep it simple, you

use your dialog user. During onboarding, you also made sure that the role ESBMessaging.send was
assigned to your user (and this setting was also used when configuring the SOAP client).
 Tip
Selecting User Role does not mean that you are determining the usage of basic authentication.
User Role authorization only means that the permissions of the sender of the message are checked
based on roles (which are assigned to the user that is associated with the sender).
However, note that if you select this authorization option, you can also configure other inbound
authentication scenarios. You can, for example, configure client certificate authentication for the
sender and add an additional step (certificate-to-user mapping) to map the certificate to a user
whose permissions are checked (based on the roles assigned to this user).
Furthermore, User Role authorization is compatible with OAuth authentication.
For productive scenarios, we recommend using client certificate authentication with certificate-to-
user mapping. However, to simplify the setup of this integration flow, we propose that you choose
basic authentication - simply because it is much easier to configure the sender in this case.
You can select other roles for inbound authentication (if you have defined these roles for the runtime
node in SAP Cloud Platform Cockpit), but you don't use this option in this scenario.
○ CSRF Protected: Keep this option selected (default setting). It ensures that your integration flow is
protected against Cross-Site-Request-Forgery, a kind of attack where a malicious party can perform
harmful actions by masquerading as the logged in user (the user specified for the HTTP client in our
case).
Related Information
HTTPS Sender Adapter [page 611]
4.15.4.14.1.2 Add the JSON to XML Converter
Add a JSON-to-XML converter to convert the HTTP request, which is in JavaScript Object Notation (JSON)
format, to XML for further processing.
With the HTTP client, we send a POST request with a request body in JSON format. To enable the subsequent
steps to process the message, it needs to be converted to XML first. To perform the required conversion, you
can use the JSON-to-XML converter.
1. In the palette, select the Message Transformers entry and then choose Converter.

2. In the submenu, choose JSON to XML Converter.
3. In the integration flow model, place the shape inside the Integration Process shape after the Start event.
The model should now look like this:
Related Information

4.15.4.14.1.3 Send the HTTP Request and Process the
Integration Flow
Set up an HTTP client using Postman and send the HTTP request.
1. Install an HTTP client on your computer.

2. Since the HTTPS sender adapter is configured to expect User Role authorization, the authentication mode
used is basic authentication (using user credentials).
Select the corresponding authentication mode for your HTTP client.
Specify the credentials of the user that is associated with the inbound HTTP request (and that is assigned
the role ESBMessaging.send in SAP Cloud Platform Cockpit).
3. As you have selected CSRF Protected in the HTTPS adapter, you need to fetch a CSRF token.
The CSRF token is then used to place the POST request for your integration flow.
1. Find out the endpoint address of the integration flow. To do this, go to the Monitor section of the Web
UI.
2. Choose a tile under Manage Integration Content.
3. Select your integration flow. It should be displayed in the list of deployed artifacts with status Started.
4. Copy the endpoint URL to the clipboard.

The URL should end with /http/<Address specified in the HTTPS adapter>.
4. Using your HTTP client, send a GET request to the endpoint address.
Make sure that you send a header with the key X-CSRF-token and the value fetch with the request.
5. You should receive the CSRF token.
You can now send the POST request to the integration flow.
1. Specify the same authentication settings as for the GET request above.
2. Specify the following HTTP request body (JSON format):
 Sample Code

"productIdentifier": "HT-1080"
}
3. Copy the value of the CSRF token (obtained from the GET request above) to the clipboard.
4. Add a header to the request.
In the Key field, enter X-CSRF-Token and in the Value field, enter the value of the CSRF token from your
clipboard.
5. Send the request.
You should get the details of the product with productIdentifier HT-1080.
6. Go to the e-mail account specified in the Mail adapter. You should have received an e-mail like this:
7. Place another POST request with a body containing productIdentifier HT-2001, and you receive details of
another product.
8. Finally, check how the message was processed by opening the Monitor section of the Web UI.
Choose a tile under Monitor Message Processing and you should find your message with the integration
flow name.
4.15.4.15 Configure Communication Channel with Ariba

Adapter
Prerequisites
● You have created an integration project and an integration flow.

● You have the credentials to log on to the Ariba Network.
● You have a certificate from Ariba or a trusted third party who is a certification authority.
● You have deployed the following artifacts: User Credentials and Keystore.

Context
You use this procedure to configure a sender and receiver channel of an integration flow with the Ariba Network
adapter. These channels enable the SAP and non-SAP cloud applications to send and receive business-specific
documents in cXML format to and from the Ariba Network. Examples of business documents are purchase
orders and invoices.
 Restriction
Procedure
1. Select the integration flow that you want to configure and choose Edit.
3. In the General tab page, provide channel name and description in the relevant fields if required.
Parameters and Values of a Channel for the Ariba Adapter

Connection Details Ariba Network URL Specify the URL to which the cXML re
quests are posted, or from where the
cXMLs are polled.
Connection Mode Select one of the options based on the

Test - If you select this option, the

Ariba Network will not process the
messages, and treats the messages
as test data.
Production - If you select this option,

the Ariba Network processes the mes
sages.
Default deployment mode is “Produc

tion”.

Account Type Select one of the options based on the

Buyer - If you hold a buyer account on

the Ariba Network.
Supplier - If you hold a supplier ac

count on the Ariba Network.
Request Type (this field is available Select one of the options based on the
only in the sender channel) request types of buyer/supplier that
you want to poll.
Use Quote Message to poll the quote

request for Buyer account type.
Maximum Messages (this field is Enter the number of messages to be

available only in the sender channel) polled from the Ariba Network for the
above-selected Request Type.
The maximum allowed value is 200.
System ID Provide the System ID for receiving

the requests from a specific ERP sys
tem belonging to a supplier. If the sys
tem ID is not provided, then the
adapter fetches all requests from ev
ery ERP systems belonging to that
specific supplier.
 Note
If the buyers’ account is enabled
with multi-ERP. It is mandatory to
provide the system ID for multi-
ERP systems belonging to the
buyer.
Authentication Domain Select one of the options based on the

Network ID: A unique alphanumeric

value assigned to every organization
registered on Ariba SN; for example,
AN01000000001.
Network User Id: A login name of an

Ariba SN user. These names typically
have the format of an e-mail address;
for example, xyz@abc.com.

Authentication Select one of the options based on the

Shared Key: If you have set the shared

key in your Ariba account.
Client Certificate: If you have config-

ured your certificate from a trusted
certificate authority in the Ariba ac
count.
Credential Name Enter a name. This name is treated as

an alias to the secure store where the
user credentials are deployed. This
value should be set according to the
Authentication selected above. If you
have selected Client Certificate, then
enter the alias details in the Private
Key Alias field.
This alias is used to identify the key

store credentials deployed on the SAP
Cloud Platform Integration account.
Ariba Network ID Enter the ID that is associated with

the Ariba Network. Default value is
AN01000000001.
Processing Details cXML version Default value provided by SAP is

1.2.025. If you are entering the ver
sion, it must be above 1.2.018.
User Agent Enter the user agent details. The con

vention is a textual string representing
the client system that is conducting
the cXML conversation. It must con
sist of the software company name
and the product name.
Language Language that is used for construct

ing the cXML conversation.
The only supported language is EN.
Scheduler (only valid for the sender Schedule on Day Specify a date and time or interval for
channel) executing the data polling.
On Date Specific date on which the data poll

ing process has to be initiated to fetch
data from the Ariba system.
Schedule to Recur Specify a recurring pattern for consis

tently running the polling process. It
can be scheduled on daily, weekly, or
monthly basis.

Daily Run message polling every day to

fetch data from the Ariba system.
Weekly Run the message polling every week

on specified days of the week to fetch
data from the SuccessFactors system.
Monthly Execute the message polling every

month on the specified date to fetch
data from the Ariba server.
 Note
If the specified date is not appli
cable in a particular month, the
data polling is not executed in
that month. For example, if the
30th day is selected, polling will
not be executed in the month of
February, as 30th is not a valid
day for February.
Time The time at which the data polling cy

cle has to be initiated. For example, if
you want the data polling to be started
at 4:10 p.m., enter 16:10. Note that the
time must be entered in 24-hour for
mat.
Every xx minutes between HH hours The connector fetches data from the
and HH hours Ariba system every ‘xx’ minutes be
tween HH hours and HH hours.
 Note
If you want the polling to run for
the entire day, enter 1 and 59.
Time Zone Select the time zone that you want to

use as reference for scheduling the
data polling cycle.
 Note
The Run Once option has been removed in the newest version of the adapter. Default values for the
interval under Schedule on Day and Schedule to Recur have been changed so that the scheduler runs
by default every 1 min between 00:00 and 24:00 o'clock.

Results
Choose Deploy at the bottom right corner of the page, to apply the configuration settings and run the
integration flow.
4.15.4.16 Configure Communication Channel with SFTP

Adapter
Prerequisites
● You have assigned SFTP adapter to the communication channel.
Context
SFTP adapter uses a certificate and keystore to authenticate the file transfer unlike the standard FTP. The
SFTP adapter achieves secure transfer by encrypting sensitive information before transmitting it on the
network. It uses SSH protocol to transfer files.
If you want to dynamically override the configuration of the adapter, you can set the following header before
calling the SFTP adapter:
● CamelFileName
The following examples show the header CamelFileName, read via XPath from the payload, or set using an
expression:
Example of Header
CamelFileName xpath java.lang.String /p:<XYZ>MessageBulk/

<XYZ>Message/FileName/
text()

CamelFileName expression java.lang.String <myapplication>/

template/out/output$
{date:now:yyyyMMddHHmm
 Note
ss}.xml
Be aware of the following
behavior if you have con
figured the file name dy
namically: If you have se
lected the Append
Timestamp option, the
timestamp overrides the
file name defined dy
namically via the header
(CamelFileName).
CI-PI currently supports the following ciphers for SSH (SFTP) communication: blowfish-cbc,3des-cbc,aes128-
cbc,aes192-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr,3des-ctr,arcfour,arcfour128,arcfour256.
 Caution
The ciphers listed above can change in the future. New ciphers can be added and existing ones can be
removed in case of security weaknesses. In such cases, you will have to change the ciphers on the SFTP
server and reconfigure the integration flows that contain SFTP adapter. SAP will inform customers, if
necessary.
 Caution
This results in the integration flows getting deployed again and you see messages from these integration
flows with Run Once setting.
Related Information
Configure Communication Channel with SFTP Sender Adapter [page 628]

Configure Communication Channel with SFTP Receiver Adapter [page 637]

4.15.4.16.1 Configure Communication Channel with SFTP
Sender Adapter
Context
How the Sender SFTP Adapter Works
If you have configured a sender SFTP adapter, message processing is performed as follows at runtime: The
tenant sends a request to an SFTP server (think of this as the sender system), but the data flow is in the
opposite direction, from the SFTP server to the tenant. In other words, the tenant reads files from the SFTP
server (a process that is also referred to as polling).
SFTP Sender Adapter: Tenant reads files from SFTP server
 Note
This adapter does not support connections to FTP servers.
 Note
Procedure
To configure a sender channel, click on a connection between a sender and the Integration Process
component.
3. On the General tab, provide a channel name and description in the relevant fields if required.
4. On the Source tab, specify the following attributes.

Field Description
Directory Use the relative path to read the file from a directory, for example, <dir>/<subdir>.
File Name Name of the file to be read.
 Note
If you do not enter a file name and the parameter remains blank, all the files in
the specified directory are read.
 Note
Usage of file name pattern:
Expressions, such as ab*, a.*, *a*, ?b, and so on, are supported.
The expression * replaces no character or an arbitrary number of characters.
The expression ? replaces exactly one arbitrary character.
Examples:
If you specify file*.txt as the File Name, the following files are polled by
the adapter: file1.txt, file2.txt, as well as file.txt and
file1234.txt, and so on.
If you specify file?.txt as the File Name, the following files are polled by
the adapter: file1.txt, file2.txt, and so on, but not the files
file.txt or file1234.txt.
Although you can configure this feature, it is not supported when using the cor
responding integration content with the SAP Process Orchestration (SAP PO)
runtime in releases lower than SAP PO 7.5 SP5.
 Caution
Files with file names longer than 100 characters will be processed with the fol
lowing limitations:
○ If two files with names longer than 100 characters are available for proc
essing, only one of these files will be processed at a time. This means that
both files will be processed, but not in parallel. This is also the case if two
runtime nodes are available. If the node fails multiple times while process
ing a file with a file name longer than 100 characters, none of the files
sharing the first 100 characters with that file can be executed without
manual intervention from the administrator.
○ The option Keep File and Mark as Processed in Idempotent Repository (for
sender channels under Processing) will not work for these files.
Address Host name or IP address of the SFTP server and an optional port, for example,
wdfd00213123:22.

Field Description
Select None if you are connecting directly to the SFTP server.
For more information on how to use the On-Premise option to connect to an on-
premise SFTP server, check out the SAP Community blog Cloud Integration – How
to Connect to an On-Premise sftp server via Cloud Connector .
Location ID To connect to an SAP Cloud Connector instance associated with your account, en
(only if On-Premise is selected for ter the location ID that you defined for this instance in the destination configuration
Proxy Type on the cloud side.
Authentication Authentication option for the connection to the SFTP server.
SFTP server authenticates the calling component based on the user name and
password. To make this configuration setting work, you need to define the user
name and password in a User Credential artifact and deploy the artifact on the
tenant.
○ Public Key
SFTP server authenticates the calling component based on a public key.
Credential Name Name of the User Credential artifact that contains the user name and password.
(Only available if you have se

lected User Name/Password for
Authentication)
(Only available if you have se Make sure that the user name contains no other characters than A-z, 0-9, _ (un
lected Public Key for derscore), - (hyphen), / (slash), ? (question mark), @ (at), ! (exclamation mark),
Authentication) $ (dollar sign ), ' (apostrophe), (, ) (brackets), * (asterisk), + (plus sign), ,
(comma), ; (semicolon), = (equality sign), . (dot), or ~ (tilde). Otherwise, an at
tempt for anonymous login is made which results in an error.
Timeout (in ms) Maximum time to wait for the SFTP server to be contacted while establishing con
nection or performing a read operation.
The timeout should be more than 0, but less than five minutes.
Maximum Reconnect Attempts Maximum number of attempts allowed to reconnect to the SFTP server.
Default value: 3

Field Description
Reconnect Delay (in ms) How long the system waits before attempting to reconnect to the SFTP server.
Automatically Disconnect Disconnect from the SFTP server after each message processing.
5. On the Processing tab, specify the following attributes.

Fields and Descriptions for SFTP Adapter Sender Channel
Field Description
Read Lock Strategy Prevents files that are in the process of being written from
being read from the SFTP server. The endpoint waits until
it has an exclusive read lock on a file before reading it.
Select one of the following options based on the capabili

ties of the SFTP server:
○ None: Does not use a read lock, which means that the
endpoint can immediately read the file. None is the
simplest option if the SFTP server guarantees that a
file only becomes visible on the server once it is com
pletely written.
○ Rename: Renames the file before reading. The Re
name option allows clients to rename files on the
SFTP server.
○ Content Change: Monitors changes in the file length/
modification timestamp to determine if the write op
eration on the file is complete and the file is ready to
be read. The Content Change option waits for at least
one second until there are no more file changes.
Therefore, if you select this option, files cannot be
read as quickly as with the other two options.
○ Done File Expected : Uses a specific file to signal that
the file to be processed is ready for consumption.
If you have selected this option, enter the name of the
done file. The done file signals that the file to be proc
essed is ready for consumption. This file must be in
the same folder as the file to be processed. Place
holders are allowed. Default: ${file:name}.done.
Sorting Select the type of sorting to use to poll files from the SFTP
server:
○ None: The sorting is specified by the STFP server

○ File Name: Files are polled sorted by file name
○ File Size: Files are polled sorted by file size
○ Time Stamp: Files are polled sorted by the modifica-
tion time stamp of the file
Sorting Order Select whether to sort in ascending or descending order.

Field Description
Lock Timeout (in min) Specify how long to wait before trying to process the file
again in the event of a cluster outage. If it takes a very long
time to process the scenario, you may need to increase
the timeout to avoid parallel processing of the same file.
This value should be higher than the processing time re
quired for the number of messages specified in Max.
Messages per Poll.
Default: 15
Change Directories Stepwise Select this option to change directory levels one at a time.
Include Subdirectories Selecting this option allows you to look for files in all the
subdirectories of the directory.

Field Description
Post-Processing Allows you to specify how files are to be handled after

processing.
Note that only successfully processed messages can be

post-processed. If message processing fails, the Post-
Processing settings are not effective.
You can select one of the following options from the drop
down list:
○ Delete File: The file is deleted after it has been read.

Lock Strategy, the file to be processed as well as the
done file will be deleted.
○ Keep File and Mark as Processed in Idempotent
Repository: Enables an idempotent repository to pre
vent a file from being consumed twice. Select this op
tion for SFTP servers that do not allow deletion or
moving of files, but the files are to be read only once.
Lock Strategy, an entry will be created in the idempo
tent repository; the done file will not be deleted.
○ Keep File and Process Again: The file is kept on the
SFTP server and file processing is repeated. You can
use this option for testing purposes, for example.
○ Move File: The file is moved to another directory.
If you select this option, you need to specify the tar
get directory.
Make sure that you specify a relative file path for the
target directory. Note that the specified file path is
defined relative to the directory specified with the
Directory parameter.
 Note
If you specify an absolute file path, it may occur
that the file cannot be stored correctly at run
time.
You can also specify the target directory dynamically,

for example, using the timestamp of the message.
The following example uses backup folders with time
stamps and replaces the file extension with bak:
backup/${date:now:yyyyMMdd}/$
{file:name.noext}.bak
Lock Strategy, only the file to be processed will be
moved and the done file will be deleted.

Field Description
Idempotent Repository You can select one of the following idempotent repository
options:
(Only available if you have selected Keep File and Mark as
Processed in Idempotent Repository for Post-Processing) ○ In Memory: Keeps the file names in the memory. Files
are read again from the SFTP server when the run
time node is restarted. It is not recommended to use
the In Memory option if multiple runtime nodes are
used. In this case the other nodes would pick the file
and process it because the memory is specific to the
runtime node.
○ Database(default): Stores the file names in a data
base to synchronize between multiple worker nodes
and to prevent the files from being read again when
the runtime node is restarted. File name entries are
deleted by default after 90 days.
 Note
The idempotent repository uses the username,
host name, and file name as key values to identify
files uniquely across integration flows of a tenant.
Retry Threshold for Alerting If the number of attempts to retry polling of a message
from the SFTP server exceeds this threshold value, an
alert is raised. The default value '0' indicates that the alert
is not raised.
 Note
If two or more sender channels are configured with
the SFTP connector, the value for the Alert Threshold
for Retry parameter should be the same.
6. On the Advanced tab, specify the following attributes.
Field Description
Default: 128 KB

Field Description
 Note
tion:

runtime.
processing log.
 Note
7. On the Scheduler tab, specify the following attributes.
Related Information
https://blogs.sap.com/2018/11/16/cloud-integration-how-to-connect-to-an-on-premise-sftp-server-via-cloud-
connector/

4.15.4.16.2 Configure Communication Channel with SFTP
Receiver Adapter
Context
How the Receiver SFTP Adapter Works
If you have configured a receiver SFTP adapter, message processing is performed as follows at runtime: The
tenant sends a request to an SFTP server (think of this as the receiver system), and the data flow is in the same
direction, from the tenant to the SFTP server. In other words, the tenant writes files to the SFTP server (from
where the communication partner can read them).
SFTP Receiver Adapter: Tenant writes file to SFTP server
 Note
This adapter does not support connections to FTP servers.
 Note

Procedure
To configure a receiver channel, click on a connection between Integration Process component and a
receiver.
3. On the General tab, provide a channel name and description in the relevant fields if required.
4. On the Target tab, specify the following attributes.
Field Description
Directory Use the relative path to write the file to a directory, for ex
ample <dir>/<subdir>.
File Name Name of the file to be written.
 Note
If you do not enter a file name and the parameter re
mains blank, the content of the CamelFileName
header is used as file name. If this header is not speci
fied, the Exchange ID is used as file name.
Expressions, such as ab*, a.*, *a*, and so on, are not

supported.

ProducedFile). Note that you can manually configure
the endpoint URL using the File Name attribute of the
SFTP adapter. However, you can dynamically override the
value of this attribute by using the Camel header
CamelFileName.

Name (through a Camel simple expression) must not be
used together. The reason is that using the Append
Timestamp option results in generating a simple expres
sion for the date. Both simple expressions result in an in
valid expression that cannot be processed correctly.

Field Description
Append Timestamp Appends a timestamp at the end of the file name.
If the file has an extension (for example, .xml), the time

stamp is appended to the file extension itself. Example: If
the file name is myfile.xml, the Append Timestamp
option (assuming the timestamp is Nov 30, 2015,
10:10:20) generates the following file name:
myfile20151201170800.xml
 Note
Be aware of the following behavior if you have config-
ured the file name dynamically: If you have selected
the Append Timestamp option, the timestamp over
rides the file name defined dynamically via the header
(CamelFileName).

Name (through a Camel simple expression) must not
be used together. The reason is that using the Append
Timestamp option results in generating a simple ex
pression for the date. Both simple expressions result
in an invalid expression that cannot be processed cor
rectly.
 Caution
Note that in case files are processed very quickly, the
Append Timestamp option might not guarantee
unique file names.
Address Host name or IP address of the SFTP server and an op

tional port, for example, wdfd00213123:22.
get system.
Select None if you are connecting directly to the SFTP

server.

system.
For more information on how to use the On-Premise op

tion to connect to an on-premise SFTP server, check out
the SAP Community blog Cloud Integration – How to Con
nect to an On-Premise sftp server via Cloud Connector .

Field Description
Location ID To connect to an SAP Cloud Connector instance associ
(only if On-Premise is selected for Proxy Type ated with your account, enter the location ID that you de
the cloud side.
Authentication Authentication option for the connection to the SFTP

server.
based on the user name and password. To make this
configuration setting work, you need to define the
user name and password in a User Credential artifact
and deploy the artifact on the tenant.
○ Public Key
based on a public key.
Credential Name Name of the User Credential artifact that contains the user
name and password.
(Only available if you have selected User Name/Password
for Authentication)
(Only available if you have selected Public Key for Make sure that the user name contains no other charac
Authentication) ters than A-z, 0-9, _ (underscore), - (hyphen), /
(slash), ? (question mark), @ (at), ! (exclamation mark), $
(dollar sign ), ' (apostrophe), (, ) (brackets), * (asterisk),
+ (plus sign), , (comma), ; (semicolon), = (equality
sign), . (dot), or ~ (tilde). Otherwise, an attempt for anon
ymous login is made which results in an error.
Timeout (in ms) Maximum time to wait for the SFTP server to be contacted
while establishing connection or performing a read opera
tion.
The timeout should be more than 0, but less than five mi
nutes.
Maximum Reconnect Attempts Maximum number of attempts allowed to reconnect to the

SFTP server.
Default value: 3

Field Description
Reconnect Delay (in ms) How long the system waits before attempting to recon
nect to the SFTP server.
Automatically Disconnect Disconnect from the SFTP server after each message
processing.
5. On the Processing tab, specify the following attributes.
Parameters and Descriptions for SFTP Adapter Receiver Channel
Field Description
Handling for Existing Files If the file already exists in the target, allow the following:
Override: Replace the existing file content with the new

one.
Append: Add the new file content to the end of the existing
one.
Fail: Do not perform any action and raise a failure.
Ignore: Do not perform any action.
Change Directories Stepwise Changes directory levels one at a time.
Create Directories Automatically creates missing directory levels as provided

in the file's path name.

Field Description
Temporary File Name Allows you to specify a name for a temporary file.
(Only visible when Handling for Existing Files is set to If you override an existing file (on the SFTP server) with a
Override) new one, the following situation can occur: The subse
quent file processor (implemented on the receiver side)
already starts processing the file, even though it is not yet
completely written (by the SFTP adapter) to the SFTP
server. Together with the Override option, you can specify
the name of a temporary file. The SFTP adapter then fin-
ishes writing the file with the temporary file name to the
SFTP server first. After that, the temporary file is renamed
according to the target file name specified in the SFTP
adapter (according to the setting for File Name under
Target). This makes sure that the subsequent processor
only processes a completely written file.
 Caution
Make sure that the name of the temporary file is
unique on the server, otherwise problems can occur
when different clients try to access the SFTP server
using the same temporary file name.
To make sure the name of the temporary file is

unique, you can enter one of the following strings, for
example:
${exchangeId}.tmp (because the Camel Ex

change ID is unique)
${file:name}.tmp (in this case, make sure that

the file name is unique, which anyway is a reasonable
requirement for a scenario including a SFTP file trans
fer)
Use Temporary File For synchronization reasons, the SFTP receiver writes the
data to a temporary file initially. Once the write procedure
is finished, the temp file is renamed to the target file. The
temp file is deleted automatically, irrespective of whether
the write procedure is successful or contains errors.
Enter a temporary file name.
You can either use a static file name such as

large.file.temp or a placeholder such as $(file:name).temp
6. On the Advanced tab, specify the following attributes.

Field Description
Default: 128 KB
 Note
tion:

runtime.
processing log.
 Note

Related Information
https://blogs.sap.com/2018/11/16/cloud-integration-how-to-connect-to-an-on-premise-sftp-server-via-cloud-
connector/
4.15.4.17 Twitter Receiver Adapter
Use the Twitter receiver adapter to integrate with the Twitter application.
Prerequisites
● You must deploy the private key pair in theCloud Integration keystore for signing the AS4 message.
 Note
Context
You can use the Twitter receiver adapter to extract information from the Twitter platform (which is the receiver
feature to send, search for and receive Twitter feeds.
The connection works that way that the tenant logs on to Twitter based on an OAuth authentication mechnism
and searches for information based on criteria as configured in the adapter at design time. OAuth allows the
tenant to access someone else’s resources (of a specific Twitter user) on behalf of the tenant. As illustrated in
the figure, the tenant (through the Twitter receiver adapter) calls the Twitter API to access resources of a
specific Twitter user. Currently, the Twitter adapter can only be used as receiver adapter. For more information
on the Twitter API, go to: https://dev.twitter.com/ .

Connection
Attributes of the Twitter Receiver Adapter (Twitter Components)
Field Description
Endpoint To access Twitter content, you can choose among the following general options.
● Send Tweet
Allows you to send content to a specific user timeline.
● Search
Allows you to do a search on Twitter content by specifying keywords.
● Send Direct Message
Allows you to send messages to Twitter (write access, direct message).
User Specifies the Twitter user from which account the information is to be extracted.
(If you select

Send Direct
Message end
point)
Page Size Specifies the maximum number of results (tweets) per page.
Number of Pages Specifies the number of pages which you want the tenant to consume.
Max. Characters Select the maximum numbers of characters that are fetched from a tweet.
Retrieved from
 Note
Tweet
● If you select 140 and tweet contains more than 140 characters, then the tweet is truncated and
(If you select
the tweet URL is appended.
Search endpoint)
● If you select 280 and the tweet contains more than 140 characters, then for regular tweets and
for retweets the adapter fetches the entire tweet.
Attributes of the Twitter Receiver Adapter (Filter Settings)

Field Description
Keywords Specifies the keywords used to filter the results.
(If you select Use commas to separate different keywords or a valid Twitter Search API query (for more information,
Search endpoint) go to https://dev.twitter.com/rest/public/search ).
Language Specifies the search language.
(If you select

Search endpoint)
Attributes of the Twitter Receiver Adapter (OAuth Settings)

Field Description
Consumer Key An alias by which the consumer (tenant) that requests Twitter resources is identified

Field Description
Consumer Secret An alias by which the shared secret is identified (that is used to to define the token of the consumer
(tenant))
Access Token An alias by which the access token for the Twitter user is identified
In order to make authorized calls to the TwitterAPI, your application must first obtain an OAuth access
token on behalf of a Twitter user
Access Token Se An alias by which shared secret is identified that is used to define the token of the Twitter user
cret
communication share a piece of data that is known only to the parties involved. Using OAuth in the context of
this adapter, the Consumer (that calls the API of the receiver platform on behalf of a specific user of this
platform) identifies itself using its Consumer Key and Consumer Secret, while the context to the user itself is
defined by an Access Token and an Access Token Secret. These artifacts are to be generated for the receiver
platform app (consumer) and should be configured that way that they will never expire. This adapter only
supports consumer key/secret and access token key/secret artifacts that do not expire.
token key/secret artifacts are to be deployed as Secure Parameter artifact on the related tenant. To do this, use
the Integration Operations feature, position the cursor on the tenant and chosen Deploy Artifact. As artifact
type, choose Secure Parameter.
4.15.4.18 Configure Communication Channel with JMS

Adapter
You configure the JMS adapter to enable asynchronous messaging using message queues.
Prerequisites
The JMS messaging instance that is used in asynchronous messaging scenarios with the JMS or AS2 adapter
has limited resources. Cloud Platform Integration Enterprise Edition sets a limit on the queues, storage, and
connections that you can use in the messaging instance.
Resource Limits for Cloud Platform Integration Enterprise Edition:
● Maximum number of queues: 30

● Total queue capacity: 9.3 GB
● Maximum capacity for one queue: 95% of the total queue capacity
● 150 transactions
● 150 consumers
● 150 providers
● 150 GB of data per month can be processed by JMS messaging

● 256 messages can be processed in one transaction
You can activate JMS resources on Cloud Integration tenants without having the CPI Enterprise Edition. For
more information about JMS resource and size limits, visit the following blog: Cloud Integration – JMS
Resource and Size Limits .
Also check out the following topic: Optimizing the Usage of JMS Resources [page 651]
You can also increase the JMS resources and assign more Enterprise units containing one queue and a
dedicated set of JMS resources.
Resource limits for 5 Enterprise Messaging Units:
● Number of JMS queues in Cloud Integration: 1

● Queue capacity: 300 MB
● 5 transactions
● 5 consumers
● 5 providers
● 5 GB of data per month can be processed by JMS messaging
There are also technical restrictions on the size of the headers and exchange properties that can be stored in
the JMS queue.
The following size limits apply when saving messages to JMS queues:
● There are no size limits for the payload. The message is split internally when it is put into the queue.
● There are no size limits for attachments. The message and the attachment are split internally when put
into the queue.
● Headers and exchange properties defined in the integration flow before the message is saved to the queue
must not exceed 4 MB in total.
 Note
The JMS adapter generates a message queue during deployment.
Message queues that are no longer used (in deployed integration flows) are deleted automatically by a
system job, which runs daily. The Message Queues monitor is adapted accordingly so that deleted message
queues are no longer displayed in this case.
Unused message queues are only deleted automatically if they don’t contain any messages. Message
queues that still contain messages but are no longer required in the Message Queues monitor have to be
deleted manually.
Information on deleted message queues is available in the audit log.
 Caution
There are certain limitations related to transactional behavior when using this adapter type together with
Data Store Operations steps, Aggregator steps, or global variables. For more information, visit the following
blog: Cloud Integration – How to configure Transaction Handling in Integration Flow .

Context
You configure the JMS receiver and sender adapters to enable asynchronous messaging using message
queues. The incoming message is stored temporarily in a queue and scheduled for processing in a queue. The
processing of messages from the queue is not serialized.
 Note
The JMS adapter stores only simple data type headers (primitive data types or strings).
Supported Headers: Headers and Exchange Properties Provided by the Integration Framework [page 856]
Procedure
3. On the General tab, provide the channel name and description in the relevant fields, if necessary.
4. Go to the Connection tab and enter the details as shown in the following table:
Parameters and Values of Sender JMS Adapter


queue.
Number of Concurrent Processes Enter the number of concurrent proc

esses for each worker node. The rec
ommended value depends on the
number of worker nodes, the number
of queues on the tenant, and the in
coming load. The value should be as
small as possible (1-5).
Retry Handling Retry Interval (in m)* Enter a value for the amount of time
to wait before retrying message deliv
ery.
Exponential Backoff Enter a value to double the retry inter

val after each unsuccessful retry.
Maximum Retry Interval (in m)* Enter a value for the maximum
amount of time to wait before retrying
message delivery.

Dead-Letter Queue If selected, the message will be taken

out of processing and marked as
Blocked in the queue if it cannot be
processed after two retries.
In certain cases, usage of the JMS

sender adapter can cause a node fail
ure. This can happen, for example, if
the JMS adapter tries repeatedly to
process a failed (large) message. To
avoid such a situation, select this op
tion (switched on by default).
In such cases, a lock entry is created,

which you can view and release in the
Message Monitoring application under
Managing Locks.

JMS Adapter .
 Note
For high-load scenarios, or if you
are sure that only small messages
will be processed in your scenario,
you should deselect the checkbox
to improve the performance. But
be aware that there is a risk of an
outage, for example,if you run out
of memory.

JMS Adapter .
JMS Retry Handling
Note the following behavior, which can be observed in message monitoring if you have configured a Retry
Interval in the adapter:
The following figure shows a straightforward case when JMS queues are configured during message
processing between a sender and a receiver.

In the setup shown, integration flow 1 receives a message from a sender, processes it, and writes the result
to JMS queue 1 (using a JMS receiver adapter), from where it is picked up by integration flow 2 (using a
JMS sender adapter). The latter processes the message and writes it to another queue, JMS queue 2
(using a JMS receiver adapter). From there, integration flow 3 picks up the message (using a JMS sender
adapter), processes it, and sends it to a receiver.
Each integration flow generates a message processing log (MPL1, MPL 2, and MPL3). The following table
summarizes the resulting MPLs in our example:
Involved Message Processing Logs (MPLs)
MPL Description
MPL 1 Shows that message is received from sender and submit

ted to JMS queue queue1

and submitted to JMS queue queue2

and submitted to receiver
MPLs for those messages that are reading from and writing into one queue (using the JMS sender,
respectively receiver adapter) are correlated with each other using a correlation ID. You can use the
Message Monitor or the OData API to search for messages that belong to one correlation ID. To get back to
our example, the MPLs are correlated in the following way:
○ MPL1 and MPL2 are correlated by a correlation ID (for example, by correlation ID: ABC)
○ MPL2 and MPL3 are correlated by another correlation ID (for example, by correlation ID: XYZ)
If an error occurs when sending the message to the receiver (for example, the receiver cannot be reached),
the following happens:
During a retry, the message is in status Retry. For each retry, a separate Run is generated and displayed in
the Monitoring application within one MPL (and can be accessed using one MPL ID).
Parameters and Values of JMS Receiver Adapter

queue.
Retention Threshold for Alerting (in d) Enter the time period (in days) by
which the messages have to be
fetched. The default value is 2.

Expiration Period (in d)* Enter the number of days after which
the stored messages are deleted (de
fault is 90).
The minimum value for Expiration Pe

riod should be at least twice the value
for Retention Threshold for Alerting.
Encrypt Stored Message Select this option to encrypt the mes

sage in the data store.
Transfer Exchange Properties You can select this option to also

transfer the exchange properties to
the JMS queue.
However, we do not recommend using

this option because headers and ex
change properties are subject to size
restrictions, which can result in prob
lems or errors.
Related Information
https://blogs.sap.com/2017/07/17/cloud-integration-configure-dead-letter-handling-in-jms-adapter/
4.15.4.18.1 Optimizing the Usage of JMS Resources
The JMS messaging instance that is used in asynchronous messaging scenarios with the JMS or AS2 adapters
has limited resources. This topic shows how to deal with this limitation.
To check the currently used resources, go to the Monitor application and open the Message Queues tile (under
Manage Stores). The JMS resources are shown at the top of the page.
Processing JMS messages always requires a consumer (JMS sender adapter) or provider (JMS receiver
adapter) and a transaction. In critical resource situations (as analyzed by the Manage Queues monitor), you
can optimize the usage of transactions based on the following calculations.

Min. No. of ... Max. No. of ...
Consumers No. of runtime nodes * No. of JMS No. of runtime nodes * No. of JMS
queues queues * No. of concurrent processes
(where the value of the latter argument

is derived from the sender channel pa
rameter Number of Concurrent
Processes)
Providers Number of providers for a tenant cannot be calculated (depends on the sender
system).
The no. of providers is equal to the no. of parallel sender calls.
Transactions Min. no. of consumers + No. of provid Max. no. of consumers + No. of provid
ers ers
Notes
● No. of JMS queues: Note that when the first integration flow that uses a JMS queue is deployed, a queue is
created.
● To find out the number of runtime nodes, open the tile System Log Files (in the Monitor section under
Access Logs) and count the numbers of system log files (entries starting with ljs_trace_) written at the
same time (one for each runtime node).
● Note that transactions are distributed dynamically to providers and consumers.
For more information, read the SAP Community blog: Cloud Integration – JMS Resource and Size Limits .
4.15.4.19 Facebook Receiver Adapter
Context
You can use the Facebook receiver adapter to extract information from Facebook (which is the receiver
feature in social marketing activities to do social media data analysis based on Facebook content.
 Note
● Facebook applications that access content of public pages need to request Page Public Content Access
feature and require review by Facebook.
● A user can only query their own comments. Other users' comments are unavailable due to privacy
concerns.
The connection works that way that the tenant logs on to Facebook based on an OAuth authentication
mechanism and searches for information based on criteria as configured in the adapter at design time. OAuth

allows a the tenant to access someone else’s resources (of a specific Facebook user) on behalf of the tenant. As
illustrated in the figure, the tenant (through the Facebook receiver adapter) calls the Facebook API to access
resources of a specific Facebook user. For more information on the Facebook API, go to: https://
developers.facebook.com/ .
 Note
You can also use headers to provide values in Connection settings of Facebook adapter. You can use both
exchange headers (see Dynamic Parameters (Example) [page 14] for more information) and Apache Camel
headers (see Facebook Component in Apache Camel for more information ).
Procedure
3. Select Facebook in the Choose Adapter window and choose OK.
 Tip
You can obtain the values required for Facebook adapter configuration in the Facebook for Developers
page.
Login to Facebook for Developers . Choose My Apps <Your Facebook App> Roles Test
Users . In this page, you will get details like User/Page ID.
To get the Post ID, you should fetch the posts using Get Posts. This will have the Post ID

Attributes of the Facebook Receiver Adapter (Facebook Components)
Field Description
Endpoint To access Facebook content, you can choose among the following general options.
○ Get Posts
Allows you to fetch specific Facebook posts.
○ Get Post Comments
Allows you to fetch specific Facebook post comments.
○ Get Users
Allows you to fetch details of a specific user.
○ Get Feeds
Allows you to fetch feeds of a specific user or a page.
User/Page ID Specifies the Facebook user from which account the information is to be extracted.
Timeout (ms) Specifies a timeout (in miliseconds) after which the connection to te Facebook platform should be
terminated.
Attributes of the Facebook Receiver Adapter (OAuth Settings)

Field Description
Application ID An alias by which the consumer (tenant) that requests Facebook resources is identified
Application An alias by which the shared secret is identified (that is used to to define the token of the consumer
Secret (tenant))
Access Token An alias by which the access token for the Facebook user is identified
In order to make authorized calls to the Facebook API, your application must first obtain an OAuth
access token on behalf of a Facebook user

4.15.4.20 Configure Communication Channel with ODC
Adapter
Prerequisites
● You have logged into your customer workspace in SAP Cloud Platform Integration web application.
● You have assigned the ODC adapter to the communication channel.
Context
The ODC adapter enables you to communicate with systems that expose data through the OData Channel for
SAP Gateway.
 Note
The ODC adapter is available only in the receiver channel.
Procedure
1. Choose Adapter Specific tab page.

Field Description
Address URL of the SAP NetWeaver Gateway OData Channel that

you are accessing
Client Backend sytem client that you want to connect to
Credential Name Alias that you used while deploying basic authentication
credentials
dropdown list.

Field Description
Resource Path Path to the resource that you want to perform the opera
tion on
3. In the <EDMX> field, choose Select.
You see a prompt to connect to the system.

4. If you have already added a system, perform the following substeps:
a. In the <System> field, select the system from dropdown list.
b. If you want to use basic authentication, in <Authenticate Using> field, choose Basic
Authentication from dropdown list. Provide username and password in the relevant fields and
choose Connect.
c. If you want to use the deployed credentials, in <Authenticate Using> field, choose Deployed
Credentials from dropdown list. In <Credential Name> field, enter the alias you used while
deploying basic authentication credentials and choose Connect.
5. If you want to connect to a new system, perform the following substeps:
a. Choose .
b. Provide values in fields based on description in table and choose Connect.
Field Description
System System name that you want to specify. You can use this
name as reference for selecting the same system for
future use.
Address URL of the system that you are connecting to
Client Backend system client that you are connecting to
Authenticate Using Authentication method you want to use for connecting

to the system. You can choose Basic
Authentication or Deployed Credentials.

4.15.4.21 Configure a Channel with LDAP Adapter
Prerequisites
● • You have assigned the LDAP adapter to the receiver channel in an integration flow. For more information,
see Assign Adapter to Communication Channel [page 491]
● You are editing the integration flow.
Context
The LDAP adapter enables you to communicate with systems that expose data through LDAP service.
In case you have input messages in different formats, you need to use a mapping step to create a target
payload that can be recognized by the LDAP adapter. You can use this schema as a template for the target in
mapping step.

<complexType>
<sequence>
type="string"/>
type="string"/>
<complexType>
<sequence>
<element name="cn" type="string" maxOccurs="1"
<element name="sAMAccountName" type="string"
<element name="sn" type="string" maxOccurs="1"
<element name="givenName" type="string"
<element name="displayName" type="string"
<element name="name" type="string" maxOccurs="1"
</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
The LDAP adapter is available only in the receiver channel.
 Note
● You cannot update multiple records in a single processing cycle. You can only perform a given operation
on one record at a time.

● You can update attribute with multiple values.
 Remember
You must use SAP Cloud Connector for connecting to an LDAP service using the LDAP adapter. LDAP
adapter supports version 2.9 or higher versions of the cloud connector.
For more information on using the SAP Cloud Connector, see SAP Cloud Platform Connector.
Procedure
1. Choose the receiver channel in the integration flow.

2. In General tab, enter name and description in the relevant fields, if required.
3. MULTIDRAGChoose Processing.
Field Description
Address Enter the URL of the LDAP directory service that you are
connecting to
Proxy Type Select the proxy type that you want to use. Currently, only
On Premise is supported.
Authentication Select the authentication type that you want to use. Cur
rently, only Simple is supported.
tenant
Operation Select the operation that you want to perform. Currently,

only Insert and Modify operations are supported.
Input Type Select the type of input that you are providing (Applicable
only for Insert operation)

4.15.4.21.1 Specific Use Cases for LDAP Adapter
Using Input Type Java (JNDI) Attributes
The LDAP adapter supports input via JNDI attributes. If you choose this as the input type, you use a script step
to obtain values to attributes that are then passed to the LDAP service.
For example, consider this script being used in a Script step.
importClass(com.sap.gateway.ip.core.customdev.util.Message);
importClass(java.util.HashMap);
importClass(javax.naming.directory.Attribute);
importClass(javax.naming.directory.BasicAttribute);
importClass(javax.naming.directory.BasicAttributes);
importClass(javax.naming.directory.Attributes);
function processData(message) {
var body = message.getBody();
var dn= "cn=Markus,ou=users,dc=testcompany,dc=com";
var givenNameAttr = new BasicAttribute("givenName", "Jack");
var displayNameAttr = new BasicAttribute("displayName", "Reacher");
var telephoneNumberAttr = new BasicAttribute("telephoneNumber",
"100-100-100");
var attributes = new BasicAttributes();
attributes.put(givenNameAttr);
attributes.put(displayNameAttr);
attributes.put(telephoneNumberAttr);
attr =new BasicAttribute("title", "Developer");
attr =new BasicAttribute("sn", "Brutus");
var resultingMap = new HashMap();
resultingMap.put("dn", dn);
resultingMap.put("attributes", attributes);
message.setBody(resultingMap);
return message;
}
In the script, the values for attributes givenName, displayName and telephoneNumber are declared in the
script before they are passed to the LDAP adapter. Similarly, you can also create a script where these values
are dynamically fetched during runtime.
Adding Attributes to Template Schema
The example schema contains a set of attributes for a given record. In case you want the schema to contain
additional attributes, you can manually edit the schema before using it in the mapping step.
For example, if you want to add a field, telephone number, you can add an element in the schema under the
sequence element.
Here’s how the edited schema will look like:

<complexType>
<sequence>
type="string"/>
type="string"/>
<complexType>
<sequence>
<element name="sAMAccountName" type="string"></
element>
<element name="sn" type="string"></element>
<element name="givenName" type="string"></element>
<element name="displayName" type="string"></element>
<element name="name" type="string"></element>
<element name="telephoneNumber" type="string"></
element>

</sequence>
</complexType>
</element>
</sequence>
</complexType>
</element>
</schema>
Add Additional Attributes to the Message after Mapping using Script
Let us consider a scenario where you want to add an attribute to the message (payload) that you are sending to
the LDAP service. For example, you want to add a password attribute. Due to security concerns, you should
encode the password before you add it.
You can achieve this by adding a Script step after the mapping step in the integration flow. Here's an example of
the script that you can use in the Script step:
import java.util.HashMap;
import javax.xml.bind.DatatypeConverter;
import javax.naming.directory.Attribute;
import javax.naming.directory.Attributes;
import javax.naming.directory.BasicAttribute;
import javax.naming.directory.BasicAttributes;
def Message processData(Message message)
{
Attributes attributes = new BasicAttributes();
String quotedPassword = '"'+"Initial@1"+'"';
byte[] unicodePasswordByteArray = quotedPassword.getBytes("UTF-16LE");
attributes.put(new BasicAttribute("unicodePwd", unicodePasswordByteArray));
message.setHeader("SAP_LDAPAttributes",attributes);
return message;
}

Using Modify Operation to Change DN
You can use the Modify operation to change the DN of an LDAP record. You can do this by adding the tag
<DistinguishedName_Previous> to the input payload with the old DN. Specify the modified DN in
<DistinguishedName> tag and perform the Modify operation.
Here's an example that shows a sample input payload for modiying the DN of an LDAP record:

<Schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DistinguishedName>CN=CMD ABC,CN=Users,DC=dev109,DC=dev-
wdf,DC=sap,DC=corp</DistinguishedName>
<DistinguishedName_Previous>CN=CMD,CN=Users,DC=dev109,DC=dev-
wdf,DC=sap,DC=corp</DistinguishedName_Previous>
<ObjectClass>user</ObjectClass>
<Attributes>
<mail>123@xyz.com</mail>
<telephoneNumber>123456789</telephoneNumber>
</Attributes>
</Schema>
4.15.4.22 Configure Communication Channel with XI Adapter
Related Information
Configure XI Sender Adapter [page 661]

Configure XI Receiver Adapter [page 667]
4.15.4.22.1 Configure XI Sender Adapter
The XI sender adapter allows you to connect a tenant to a local Integration Engine in a sender system.
 Note

Use
With this adapter you can connect on-premise backend system to SAP Cloud Platform Integration. The XI
sender adapter communicates (receive messages) over the XI 3.0 protocol.

● The XI adapter does not support attachments.
When you have created a sender channel (with XI adapter selected), you can configure the following attributes.
Connections Tab
Parameters and Values of Sender XI Adapter/Connection
Address Address under which a sender system can reach the tenant

● Client Certificate: Sender authorization is checked on the tenant by evaluating the sub
ject/issuer distinguished name (DN) of the certificate (sent together with the inbound
request). You can use this option together with the following authentication option: Cli
ent-certificate authentication (without certificate-to-user mapping).
● User Role: Sender authorization is checked based on roles defined on the tenant for the
user associated with the inbound request. You can use this option together with the fol
lowing authentication options:
The authorizations for the user are checked based on user-to-role assignments de
fined on the tenant.

Allows you to select one or more client certificates (based on which the inbound authori
zation is checked).
Choose Add to add a new certificate for inbound authorization for the selected adapter.
You can then select a certificate stored locally on your computer. You can also delete
certificates from the list.
For each certificate, the following attributes are displayed: Subject DN (information used
to authorize the sender) and Issuer DN (information about the certificate authority that
issues the certificate).
● User Role
The role ESBMessaging.send is provided by default. It is a predefined role provided by
SAP which authorizes a sender system to process messages on a tenant. However, us
ing SAP Cloud Platform Cockpit, you can also define custom roles for the runtime node
as well. When choosing Select, a selection of all custom roles defined that way is offered.
 Note
Note the following:
○ You can also type in a role name. This has the same result as selecting the role
from the value help: If the inbound request is authenticated, depends on the
correct user-to-role assignment defined in SAP Cloud Platform Cockpit.
○ When you externalize the User Role, in the integration flow configuration the
value help for roles is offered as well.
○ If you have selected a product profile for SAP Process Orchestation, the value
help will only show the default role ESBMessaging.send.

Parameters and Values of Sender XI Adapter/Delivery Assurance

Quality of Service Defines how the message (from the sender) is processed by the tenant.
● Best Effort
The message is sent synchronously; this means that the tenant waits for a re
sponse before it continues processing.
No temporaty storage of the message needs to be configured, as message re
quest and response are processed immediately after another.
● At Least Once
for a response before continuing processing. It is expected that the receiver
guarantees that the message is processed exactly once.
This option guarantees that the message is processed at least once on the ten
sender,, all of them will be processed.
● Exactly Once (Only possible if as Temporary Storage the option Data Store is se
lected)
for a response before continuing processing.
This option guarantees that the message is processed exactly once on the ten
sender, only the first one will be processed. The subsequent messages can be
identified as duplicates (based on the value of the message header
SapMessageIdEx, see below) and will not be processed.
 Note
For Exactly Once handling, the sender XI adapter saves the protocol-spe
cific message ID in the header SapMessageIdEx. If this header is set, XI
receiver uses the content of this header as the message ID for outbound
communication. Usually, this is the desired behavior and enables the re
ceiver to identify any duplicates. However, if the sender system is also the
receiver system, or several variants of the message are sent to the same
system (for example, in an external call or multicast), the receiver system
will incorrectly identify these messages as duplicates. In this case, the
header SapMessageIdEx must be deleted (for example, using a content
modifier) or overwritten with a new generated message ID. This deactivates
Exactly Once processing (that is, duplicates are no longer recognized by the
protocol).

Temporary Storage Temporary storage location for messages that are processed asynchronously. Mes
sages for which processing runs into an error can be retried from the temporary
(only if as Quality of Service the op
storage.
tion Exactly Once is selected)
You can choose among the following storage types:
● Data Store
The message is temporarily stored in the database of the tenant (in case of an
error). In case of successful message processing, the message is immediately
removed from the data store.
UI under Manage Stores in the Data Stores tile.
 Note
The data store name is automatically generated and contains the following
parts:
<name of participant connected with XI adapter>_<

XI channel name>
This automatically generated name is subject to a length restriction and

must be no more than 40 characters (including the underscore). If the data
store name exceeds this limit, you must shorten the participant name or
channel name accordingly.
Below the data store name, you find a reference to the associated integra
tion flow in the following form: <integration flow name>/XI
● JMS Queue
The message is stored temporarily in a JMS queue on the configured message
broker.
UI under Manage Stores in the Message Queues tile.
 Note
The name of the JMS queue is automatically generated and contains the
following parts:
 Note

Retry Interval (in min) Enter a value for the amount of time to wait before retrying message delivery.
Exponential Backoff Select this option to double the retry interval after each unsuccessful retry.
Maximum Retry Interval (in min) You can set an upper limit on that value to avoid an endless increase of the retry in
(only configurable when Exponential terval. The default value is 3600 seconds.
Backoff is selected)
Dead-Letter Queue Select this option to place the message in the dead-letter queue if it cannot be proc
essed after three retries caused by an out-of-memory. Processing of the message is
(only if as Temporary Storage the op
stopped then.
tion JMS Queue is selected)
In such cases, a lock entry is created which you can view and release in the Monitor
section of the Web UI under Managing Locks.
Use this option to avoid out-of-memory situations (caused in many cases by large
messages).
For more information, read the SAP Community blog Cloud Integration – Configure
Dead Letter Handling in JMS Adapter .
Encrypt Message during Persistence Select this option in case the messages should be stored in an encrypted way during
(only in case you have selected certain processing steps.
Exactly Once as Quality of Service)
Explicit Retry Configuration Using Specific Headers
When as Quality of Service you have selectedExactly Once, you can use certain headers to specify that after a
defined number of message retries message processing is changed in a specific way. For example, you can
configure the integration flow so that after 5 retries the message is routed to a specific receiver (who will then
receive an alert email). You can do this by using one of the following mentioned headers in a dynamc
expression.
Which header you can use, depends on the chosen kind of temporary storage.
● If as Temporary Storage you have chosen the option Data Store, you can use header
SAP_DataStoreRetries.
● If as Temporary Storage you have chosen the option JMS Queue, you can use header SAPJMSRetries.
 Tip
Example
When as Temporary Storage you have chosen the option Data Store, you can use the following expression in
the route that is supposed to forward the message to the receiver of the alert email:
${header.SAP_DataStoreRetries} > '5'
In this example, the message is routed to the related receiver after 5 retries.

Conditions
Maximum Message Size This parameter allows you to configure a maximum size for
inbound messages (smallest value for a size limit is 1 MB). All
inbound messages that exceed the specified size (per inte
gration flow and on the runtime node where the integration
flow is deployed) are blocked.

● Body Size
● Attachment Size

Related Information
https://blogs.sap.com/2018/06/04/cloud-integration-configuring-scenario-using-the-xi-sender-adapter/
https://blogs.sap.com/2018/12/04/cloud-integration-configuring-scenario-with-xi-sender-handling-multiple-
interfaces/
https://blogs.sap.com/2018/08/15/cloud-integration-configuring-explicit-retry-in-exception-sub-process-for-
xi-adapter-scenarios/
4.15.4.22.2 Configure XI Receiver Adapter
The XI receiver adapter allows you to connect a tenant to a local Integration Engine in a receiver system.
 Note

● The XI Adapter can be used in an Exactly Once scenario (as Quality of Service) in the Send step.
● The XI Adapter can be used in an Best Effort scenario (as Quality of Service) in the Request-Reply step.

● The XI adapter does not support attachments.
● ExactlyOnceInOrder (EOIO) is not supported by the XI adapter.
When you have created a receiver channel (with XI adapter selected), you can configure the following
attributes.

Connection Tab
Parameters of Receiver XI Adapter/Connection

Address Address under which the local integration engine of the receiver system can be called
The integration engine address is composed in the following way:
https://<host name>:<port>/sap/xi/engine?type=receiver&sap-
client=<client>
 Note
You can find out the constituents (HTTPS port) of the URL by choosing transaction SMICM in the receiver
system and choosing Goto Services .
The endpoint URL that has actually been used at runtime is displayed in the message processing log (MPL) in
the message monitoring application (MPL property RealDestinationUrl).

 Note
If you select the On-Premise option, the following restrictions apply to other parameter values:
○ Do not use an HTTPS address for Address, as it leads to errors when performing consistency
○ Do not use Certificate-Based Authentication as the Authentication Type, as it leads to errors
when performing consistency checks or during deployment
 Note
If you select the On-Premise option and use the SAP Cloud Connector to connect to your on-premise
system, the Address field of the adapter refers a virtual address which has to be configured in the
SAP Cloud Connector settings.
Location ID To connect to an ASP Cloud Connector instance associated with your account, enter the location ID that you
only in case defined for this instance in the destination configuration on the cloud side. You can also enter $
On-Premise {header.headername} or ${property.propertyname} to dynamically read the value from a
is selected header or a property.
for Proxy
Type.

Authenticat Defines the tenant authenticates itself against the receiver.

ion Type
● None
No authentication is configured.
The tenant authenticates itself against the receiver based on user credentials (user and password).
Note that when this authentication option is selected, the required security artifact (User Credentials)
has to be deployed on the tenant.
● Certificate-Based Authentication
The tenant authenticates itself against the receiver based on X.509 certificates.
Note that when this authentication option is selected, the required security artifact (Keystore) has to be
deployed on the tenant.
The tenant authenticates itself against the receiver by forwarding the principal of the inbound user to the
cloud connector, and from there to the back end of the relevant on-premise system. You can only use
principal propagation if you have selectedBest Effort as the Quality of Service.
 Note
This authentication method can only be used with the following sender adapters: HTTP, SOAP, IDoc,
XI sender (and Quality-of-Service Best Effort)
 Note
If it takes longer than 30 minutes to process the data between the sender and receiver channel, the
token for principal propagation expires, which leads to errors in message processing.
For special use cases, this authentication method can also be used with the AS2 adapter.
Credential Name of User Credentials artifact that needs to be deployed separate on the tenant (it contains user name
Name and password for the user to be authenticated).

you have
selected
Basic
Authenticat
ion as
Authenticat
ion Type)

Private Key Optional entry to specify the alias of the private key to be used for authentication. If you leave this field empty,
Alias the system checks at runtime for any valid key pair in the tenant keystore.

you have
selected
Certificate-
Based
Authenticat
ion as
Authenticat
ion Type)
Compress Enables the tenant to send compressed request messages to the receiver (which acts as WS provider) and to
Message indicate to the receiver that it can handle compressed response messages.
Allow Used for enabling chunking of data while sending messages.

Chunking
Clean Up Select this option to clean up the adapter-specific headers after the receiver call.
Request
Headers

Identifiers Specifies the Communication Party header value of the request message sent to the receiver system.
for Sender A communication party typically represents a larger unit involved in an integration scenario. You usually
An XI mes
sage con
tains spe
Specifies the Communication Component header value of the request message sent to the receiver sys
cific header
tem.
elements
that are
messages.
used to ad
dress the
sender or a
receiver of
the mes
sage, such
as commu
nication
party, com
munication
compo
nent, and
service in
terface. For
more infor
mation on
the con
cepts be
hind these
entities,
see the
documen
tation of
SAP Proc
ess Integra
tion at
https://
help.sap.co
m/viewer/
product/
SAP_NET
WEA
VER_PI/
ALL/.

Identifiers Specifies the Communication Party header value of the response message received from the receiver
for Receiver system.
A communication party typically represents a larger unit involved in an integration scenario. You usually
An XI mes
sage con
tains spe
cific header
Specifies the Communication Component header value of the response message received from the re
elements
ceiver system.
that are
used to ad
messages.
dress the
sender or a
receiver of
 Note
the mes
sage, such To get this information, go to the receiver system and choose transaction SLDCHECK. In section
as commu LCR_GET_OWN_BUSINESS_SYSTEM, you find the business system ID (which typically has the form
nication <SID>_<client>).
party, com
● Service Interface and Service Interface Namespace
munication
These attributes specify the service interface that determines the data structure of the response mes
compo
sage received from the receiver system.
nent, and
The receiver interface is described according to how interfaces are defined in the Enterprise Services Re
service in
pository, that means, with a name and a namespace.
terface. For
more infor
mation on
the con
cepts be
hind these
entities,
see the
documen
tation of
SAP Proc
ess Integra
tion at
https://
help.sap.co
m/viewer/
product/
SAP_NET
WEA
VER_PI/
ALL/.

Parameters of Receiver XI Adapter/Delivery Assurance

XI Message Select this option to specify how the XI Message ID shall be defined.
ID
You can choose among the following options:
Determinati
on ● Generate (default)
Generates a new XI message ID.
● Reuse
Take over the message ID passed with the header SAPMessageIdEx. If the header is not available in
runtime, a new message ID is generated
● Map
Maps a source message ID to the new XI message ID.
For more information on how to use this option in an end-to-end scenario, check out the SAP Community
blog Cloud Integration – Configuring ID Mapping in XI Receiver Adapter
Source for To map the source message ID to the XI message ID enter:

XI Message
${header.headername} or ${property.propertyname}
ID (only in
case you
 Note
selected
Map as XI If no header or property is available at runtime, a new message ID is generated.
Message ID
Determinati
on)
Quality of Defines how the message (from the tenant) is expected to be processed by the receiver.
Service
● Best Effort
The message is sent synchronously; this means that the tenant waits for a response before it continues
processing.
No temporary storage of the message needs to be configured, as message request and response are
processed immediately after another.
● Exactly Once
The message is sent asynchronously. This means that the tenant does not wait for a response before
continuing processing. It is expected that the receiver guarantees that the message is processed exactly
once.
If you choose this option, the message needs to be temporarily stored on the tenant (in the storage con
figured under Temporary Storage). As soon as the message is store there, the sender receives success
fully received status message. If an error occurs, the message is retried from the temporary storage.

Temporary Temporary storage location for messages that are processed asynchronously. Messages for which processing
Storage runs into an error can be retried from the temporary storage.
(only if as You can choose among the following storage types:

Quality of
● Data Store
Service the
The message is temporarily stored in the database of the tenant (in case of an error). In case of success
option
ful message processing, the message is immediately removed from the data store.
Exactly
Once is se
in the Data Stores tile.
lected)
 Note
The data store name is automatically generated and contains the following parts:
<name of participant connected with XI adapter>_< XI channel name>
This automatically generated name is subject to a length restriction and must be no more than 40
characters (including the underscore). If the data store name exceeds this limit, you must shorten
the participant name or channel name accordingly.
Below the data store name, you find a reference to the associated integration flow in the following
form: <integration flow name>/XI
● JMS Queue
The message is stored temporarily in a JMS queue on the configured message broker.
in the Message Queues tile.
 Note
The name of the JMS queue is automatically generated and contains the following parts:
 Note
Retry Enter a value for the amount of time to wait before retrying message delivery (in case of an error).
Interval (in
min)
Exponential Select this option to double the retry interval after each unsuccessful retry.
Backoff

Maximum You can set an upper limit on that value to avoid an endless increase of the retry interval. The default value is
Retry
3600 seconds.
Interval (in
min)
(only con
figurable
when
Exponential
Backoff is
selected)
Dead-Letter Select this option to place the message in the dead-letter queue if it cannot be processed after three retries
Queue caused by an out-of-memory. Processing of the message is stopped then.
(only if as In such cases, a lock entry is created which you can view and release in the Monitor section of the Web UI
Temporary under Managing Locks.
Storage the
Use this option to avoid out-of-memory situations (caused in many cases by large messages).
option JMS
Queue is For more information, read the SAP Community blog Cloud Integration – Configure Dead Letter Handling in
selected) JMS Adapter .
Encrypt Select this option in case the messages should be stored in an encrypted way during certain processing
Message steps. It is recommended to choose this option if the message can contain sensitive data. Note that this set
during ting might decrease performance of the integration scenario.
Persistence
(only in
case you
have se
lected
Exactly
Once as
Quality of
Service)
Explicit Retry Configuration Using Specific Headers
When as Quality of Service you have selectedExactly Once, you can use certain headers to specify that after a
defined number of message retries message processing is changed in a specific way. For example, you can
configure the integration flow so that after 5 retries the message is routed to a specific receiver (who will then
receive an alert email). You can do this by using one of the following mentioned headers in a dynamc
expression.
Which header you can use, depends on the chosen kind of temporary storage.
● If as Temporary Storage you have chosen the option Data Store, you can use header
SAP_DataStoreRetries.
● If as Temporary Storage you have chosen the option JMS Queue, you can use header SAPJMSRetries.

 Tip
Example
When as Temporary Storage you have chosen the option Data Store, you can use the following expression in
the route that is supposed to forward the message to the receiver of the alert email:
${header.SAP_DataStoreRetries} > '5'
In this example, the message is routed to the related receiver after 5 retries.
Related Information
https://blogs.sap.com/2018/06/04/cloud-integration-configuring-scenario-using-the-xi-receiver-adapter/
https://blogs.sap.com/2018/06/04/cloud-integration-configuring-scenario-using-the-xi-sender-adapter/
https://blogs.sap.com/2018/08/15/cloud-integration-configuring-explicit-retry-in-exception-sub-process-for-
xi-adapter-scenarios/
https://blogs.sap.com/2018/09/21/cloud-integration-usage-of-xi-adapter-in-send-and-request-reply-step/
https://blogs.sap.com/2018/11/16/cloud-integration-configuring-id-mapping-in-xi-receiver-adapter/
4.15.4.23 Configure Communication Channel with RFC

Receiver Adapter
You can use Remote Function Call (RFC) to integrate on-premise ABAP systems with the systems hosted on
the cloud using the Cloud connector.
Prerequisites
● You have defined the required RFC destination for your application. To create destinations you need to
either have administrator or developer role in SAP Cloud Platform cockpit.
 Note
For more information on how to create RFC destinations, see Creating an RFC Destination [page 680] .
● You have opened the integration flow in the editor for editing purposes.
● SAP Netweaver ABAP system is up and running.
● You have generated the remote function module XSD file. For more information on how to generate XSD
file, see Generating XSD/WSDL for Function Modules Using ESR (Process Integration) [page 680].

Context
RFC executes the function call using synchronous communication, which means that both systems must be
available at the time the call is made. When the call is made for the function module using the RFC interface,
the calling program must specify the parameters of the connection in the form of an RFC destination. RFC
destinations provide the configuration needed to communicate with an on-premise ABAP system through an
RFC interface.
The RFC destination configuration settings are used by the SAP JAVA Connector (SAP JCo) to establish and
manage the connection.
 Remember
● The RFC adapter supports SAP NetWeaver 7.31 and higher.

● From RFC adapter version 1.2.0, function modules that contains "/" in their names are also supported.
For these function modules you need to replace "/" with "_-" (underscore and hyphen) in the input
XML.
● The date provided in the input XML must be of format "YYYY-MM-DD".
● If the parameters of the ABAP function are changed, the integration flow containing the RFC adapter
must be redeployed for the new parameters to be reflected in the output XML. However, this doesn't
hold good in case the RFC adapter is configured with dynamic destination. For the changed parameters
to be reflected in the output, the integration flow must be redeployed with the static destination only.
Procedure
1. Launch the SAP Cloud Platform Integration Web application by using the URL provided by SAP.
4. Go to Connection tab and provide necessary details and save changes.
Field Description

application.

Field Description
Send Confirm Transaction (Applicable to BAPI functions) By default this option is dis
abled. You can enable this option if you want to support
BAPI functions that require BAPI_TRANSACTION_COM
MIT to be invoked implicitly by the RFC receiver adapter.
 Note
○ BAPI_TRANSACTION_COMMIT
○ BAPI_TRANSACTION_ROLLBACK
 Caution
which is redundant and hence may impact RFC func
tion execution time.
Create New Connection If you enable this option, the adapter creates a new RFC
connection in the backend system, every time a new call is
made to the target system.
 Remember
This option must be selected if you are using principal
propagation. If you do not select this option, principal
propagation will not work as expected.
 Note
Modifier. Select Content Modifier in the integration flow. Then go to Message Header in Content
Modifier properties and assign corresponding value to the header name as the destination name.
Select your RFC adapter and assign dynamic destination by using the expression: ${header/
property.<header/property name>}. For example ${header.abc} or ${property.abc} where
abc is the value of the header or property.

4.15.4.23.1 Generating XSD/WSDL for Function Modules
Using ESR (Process Integration)
Generate an XSD/WSDL file for a function module using the Enterprise Services Repository (ESR).
Procedure
1. Log on to the remote machine with your credentials.

2. Open the browser and enter <host:port>/dir.
3. Under Enterprise Service Repository, select Enterprise Service Builder and log on.
The repository.jnlp file is downloaded.

4. Click repository.jnlp to launch the Enterprise Services Builder.
5. Under Design Objects, select the appropriate object and expand it.
6. Right-click Imported Objects and select Import of SAP Objects.
7. Provide the appropriate information in the mandatory fields and choose Continue.
8. Under Select Objects, expand RFC, search for your function module, and choose Continue.
9. Choose Finish.
The object is imported successfully.

10. On the Design Objects tab, navigate to the imported objects under RFC.
11. In the right pane, open Source (Read-Only) to view the WSDL/XSD file.
Related Information
Configuring a Channel with RFC Receiver Adapter [page 202]

Configure Communication Channel with RFC Receiver Adapter [page 677]
4.15.4.23.2 Creating an RFC Destination
Create an RFC destination by adding necessary properties before using it in the integration flow of RFC adapter.
Context

Procedure
1. Log into the SAP Cloud Platform cockpit and choose Connectivity Destinations .
2. Choose New Destination and enter destination name.
3. Enter the details for the parameters <Name>, <URL>, <User>, <Password>, and select <Type> as RFC.
4. Add the following properties (first four properties are mandatory) and assign appropriate values:
○ jco.client.ashost
 Note
The value provided for application server host (ashost) property is the access control value created
in the Cloud connector.
○ jco.client.client
○ jco.client.lang
○ jco.client.sysnr
○ (optional) jco.destination.pool_capacity
○ jco.destination.auth_type
 Note
If you are using principal propagation for authentication, for the property jco.destination.auth_type,
specify the value as PrincipalPropagation. Do not specify any additional credentials in the
destination.
5. Select Save.
4.15.4.24 JDBC Receiver Adapter
The JDBC (Java Database Connectivity) adapter enables you to connect integration flows with HANA or ASE
databases hosted on customers (subscriber) global account.
 Note
The JDBC receiver adapter helps the SAP Cloud Platform Integration tenant to connect to a JDBC (Java
Database Connectivity) database and to execute SQL commands on the database. Use it to perform

operations such as read, write, update or delete database entries. The following figure shows how the JDBC
adapter communicates with an HANA or ASE database hosted on the subscribers Global Account:
The JDBC receiver adapter uses XML SQL Format message protocol. For more information on modifying or
structuring the content of the message payload, see Defining XML Documents for Message Protocol XML SQL
Format
 Note
● UPSERT operation is currently not supported for XML SQL format.

● Batch messages are not be processed by JDBC adapter. If the adapter receives a batch message, then
only the first record is processed the remining records are ignored.
● You must deploy the public certificate in the Cloud Integration keystore for verification of the business
response.
● You must have configured an integration flow in the editor. For more information, see New and
Improved Integration Flow Editor for SAP Cloud Platform Integration [page 485].
● JDBC receiver adapter supports externalization. To externalize the parameters of this adapter choose
Externalize and follow the steps mentioned in Externalize Parameters of an Integration Flow [page
482].
Generating Access Token for JDBC Data Source
You need to generate tokens for newly deployed JDBC Data Source artifacts for a database. If the artifacts
already exist reuse the token until there is at least one artifact deployed for the database and you cannot
generate new tokens for an existing JDBC Data Source. In case you undeployed the last artifact, you need to
generate a new token for a new artifact for the specific database. Use the following command to list all grants
for the specified schema:
 Source Code
neo list-schema-access-grants --account owner --host hanatrial.ondemand.com --

user myuser --id schema1

For more information on allowing access and to generate a one-time access token that permits the requesting
application to access your schema from its subaccount, see Grant Access to Schemas. To lists all current
schema access grants for a specified subaccount, see list-schema-access-grants.
Connection
Configure the connection details as per the description
Field Description
JDBC Data Source Alias Enter the data source name. For more information, see .
 Note
● Deployment of JDBC Data Source fails if you have
heterogeneous cluster setup, i.e. the cluster setup
must be configured with the same product profiles
combination of different product profiles are not
supported.
● You can use the same JDBC Data Source in differ-
ent integration flows configured with JDBC adapter.
But you cannot use the same JDBC Data Source to
configure multiple JDBC adapters within an integra
tion flow. You need to deploy two JDBC Data Source
artifacts with different names for the same data
base and use them in the integrations flows having
multiple JDBC adapters.
Connection Timeout (in s) Provide a connection timeout, in seconds, to define how long
the adapter waits for a server response before the connec
tion retry is terminated.
Query/Response Timeout (in s) Provide a query timeout, in seconds, to define the waiting
duration for receiving a query response. After the elapsed
time the adapter stops waiting for response.
Maximum Records Determine a value to display the maximum number of

fetched records.

ProcessDirect Adapter
Use ProcessDirect adapter (sender and receiver) to establish fast and direct communication between
integration flows by reducing latency and network overhead provided both of them are available within a same
tenant.
Prerequisites
● Deployment of the ProcessDirect adapter must support N:1 cardinality, where N (producer) → 1
(consumer).
 Caution
Multiple producers can connect to a single consumer, but the reverse is not possible. The cardinality
restriction is also valid across integration projects. If two consumers with the same endpoint are
deployed, then the start of the second consumer fails.
● The Address mentioned in ProcessDirect configuration settings must match for producer and consumer
integration flows at any given point.
Context
ProcessDirect Receiver Adapter: If the ProcessDirect adapter is used to send data to other integration flows,
the integration flow is considered as a producer integration flow. In this case, the integration flow has a receiver
ProcessDirect Sender adapter: If the ProcessDirect adapter is used to consume data from other integration
flows, the integration flow is considered as a consumer integration flow. In this case, the integration flow has a
sender ProcessDirect adapter.
The ProcessDirect adapter supports the following features:
● Decompose large integration flows: You can split a large integration flow into smaller integration flows
and maintain the in-process exchange without network latency.
● Customize the standard content: SAP Cloud Platform Integration enables integration developers to
customize their integration flows without modifying them entirely. The platform provides plugin
touchpoints where integration developers can add custom content. This custom content is currently
connected using HTTP or SOAP adapters. You can also use the ProcessDirect adapter to connect the
plugin touchpoints at a lower network latency.
● Allow multiple integration developers to work on the same integration flow: In some scenarios,
integration flows can be large (100 steps or more), and if they are owned or developed by just one
integration developer this can lead to an overreliance on one person. The ProcessDirect adapter helps you
to split a large integration flow into smaller parts that can be owned and managed by multiple integration
developers independently. This allows several people to work on different parts of the same integration
flow simultaneously.

● Reuse of integration flows by multiple integration processes spanning multiple integration projects:
Enables the reuse of integration flows such as error handling, logging, extension mapping, and retry
handling across different integration projects and Camel context. Integration developers therefore only
need to define repetitive logic flows once and can then call them from any integration flow using the
● Dynamic endpoint: Enables the producer integration flow to route the message dynamically to different
consumer integration flow endpoints. The producer integration flow look ups the address in the headers,
body, or property of the exchange and the corresponding value is then resolved to the endpoint to which
the exchange is to be routed.
● Multiple MPLs: MPL logs are interlinked using correlation IDs.
● Transaction processing: Transactions are supported on integration flows using the ProcessDirect adapter.
However, the scope of the transaction is isolated and restricted to a single integration flow.
● Header propagation: Header propagation is not supported across producer and consumer integration
flows unless configured in <Allowed Header(s)> in the integration flow's runtime configuration.
● Property propagation: Property propagation is not supported across producer and consumer integration
flows, except for SAP_SAPPASSPORT property. This property is for internal use only and users are not
allowed to modify it.
 Tip
ProcessDirect adapter improves network latency, as message propagation across integration flows do not
involve load balancer. For this reason, we recommend that you consider memory utilization as a parameter
in scenarios involving heavy payloads and alternatively use HTTP adapter in such scenarios because, the
behavior will be the same.
 Restriction
Cyclic loop deployment of integration flows must be avoided.
Procedure
1. Select the integration flow that you want to configure and choose Edit.
3. Create a mapping between Sender and the integration flow.
4. Choose ProcessDirect as the adapter type.
On the General tab, the relevant details for channel and adapter are populated automatically.
5. Go to the Connection tab and specify the following attributes:

Parameters of the ProcessDirect Adapter
Address URL of the target system that you are connecting to. For
example, /localiprequiresnew.
 Note
It may or may not start with "/". It can contain alpha
numeric characters and special characters such as
underscore "_" or hyphen "-". You can also use simple
expressions, for example, ${header.address}.
 Remember
○ If the consumer has an <Escalated End Event> in the <Exception Sub-Process>, then in
case of exception in the consumer, the MPL status for the producer varies based on the following
cases:
○ If the producer integration flow starts with <Timer>, the MPL status for the consumer will be
Escalated and for Producer, it will be Completed.
○ If the producer integration flow starts with <HTTP> Sender, the MPL status for the consumer
will be Escalated and for producer, it will be Failed.
○ The combination of <Iterating Splitter> and <Aggregator> in the producer integration
flow might generate an extra MPL (Aggregator MPL) due to the default behavior of Aggregator.
○ The <Send> component is incompatible with the ProcessDirect adapter as the adapter supports
asynchronous mode for message exchange and it expects a response.
To learn more about the adapter, see blog on ProcessDirect Adapter in SAP Community .
4.15.5 Define Events
4.15.5.1 Define End Message Event
An End Message event ends a message processing sequence.
Context
This is how using an End Message event has an impact on the message status (shown in the message
processing log).

 Note
To catch any exceptions thrown in the integration process and handle them, you can use an Exception
Subprocess.
If an exception occurs during the processing sequence which has been handled in an Exception Subprocess,
the message status displayed in the message processing log is Failed.
When there is no error during exception handling, the message status displayed in the message processing log
is Completed.
If you like to configure your integration flow that way that the message status displayed in the message
processing log is Failed (even in case an exception occurs during the processing sequence which has been
handled successfully in an Exception Subprocess), you have the following options:
● Use an Error End event.

● Use an Escalation End event (sets message status to Escalated in that case).
Procedure
1. In the palette, choose End Message Event .

4.15.5.2 Define an Escalation Event
Context
Procedure
1. In the palette, choose Escalation Event .

2. Specify the Escalation Category.

There are the following Escalation Categories:
Escalation Event Routing condition has not been met.
Receiver not reachable Receiver could not be reached, because it is temporarily

down or not accessible (for example, due to overload or
maintenance work).
Receiver not found Receiver could not be found because the URL points to a
non-existent resource (for example, HTTP 404 error).
Not authenticated to invoke receiver Receiver could not be called because authentication has
failed (for example, HTTP 401 error).
Not authorized to invoke receiver Receiver could not be called because of insufficient per
missions (for example, HTTP 403 error).
Receiver tries to redirect Receiver could not be reached (HTTP 302 error).
Internal server error in receiver Internal server error occurred in the receiver system (for
example, HTTP 500 error).
Others – not further qualified Escalation category has not been further qualified.
4.15.5.2.1 Escalation End Event Behavior
This topic describes the behavior of integration processes containing an escalation end event.
The Escalation Event does not abort the integration flow processing as a whole but only throws the Escalation
Event .
Main integration process:
If an Escalation End Event is used in the main integration process, the escalation end event throws an Escalated
event and the processing stops afterwards as there are no further steps to execute
Local integration process:
If an integration process is calling a local integration process and an escalation event has been defined in the
local integration process, the Escalation Event is thrown, and the processing continues in the calling flow. If
there are still steps to process in the main flow, the processing continues normally at this level and the main
flow message status will be Completed.
 Note
In case of a synchronous exchange pattern, the process raises an exception and the message will be
marked as Escalated. This behavior violates the process described above and no exception will be raised,
but this handling was explicitly chosen, since the event is usually defined in the exception sub-process and
the sender expects a valid response in a synchronous exchange pattern.

 Note
In case of an asynchronous exchange pattern no exception will be raised and the message status will be
Escalated.
Related Information
Define an Escalation Event [page 687]
4.15.5.3 Define a Timer Start Event
You can configure an integration flow to automatically start and run on a particular schedule.
Context
If you want to configure a process to automatically start and run on a particular schedule, you can use this
procedure to set the date and time on which the process should run once or repetitively. The day and time
combinations allow you to configure the schedule the process requires. For example, you can set the trigger
just once on a specific date or repetitively on that date, or you can periodically trigger the timer every day,
specific days in a week or specific days in a month along with the options of specific or repetitive time.
A Timer Start event and a Start Message event (sender channel) must not be modelled in the same integration
flow. This would result in an error ERROR: Multiple 'Start Events' not allowed within an
 Note
When you use timer with Run Once option enabled, the message is triggered only when the integration flow
is deployed. If you want to trigger the message with an integration flow that you have already deployed, you
have to Undeploy the integration flow and Deploy it again. If you restart the integration flow bundle,
message will not be triggered.
When you delploy or undeploy an integration flow with Timer-Scheduler, the system automatically releases
all the scheduler locks.
 Note
When you deploy small integration flows with Timer (for example, an integration flow with timer, content
modifier and mail adapter), due to extremely fast processing times, multiple schedules are triggered.

Procedure
1. In the palette, choose Events Timer (choose icon and icon ).

2. In the Name field, provide a name for the timer.
3. Choose Scheduler.
4. Select options or provide values in fields based on description in table.
Option Field Description
Run Once NA NA
Select if you want the message proc

essing to be triggered immediately af
ter you deploy the integration flow.
Schedule on Day On Date Select the date on which you want the
message processing to be triggered
Select if you want the message proc
essing to be triggered on a specific
On Time Select the time on which you want the
date and time.
Every Select this option if you want to trig

ger message processing repeatedly in
a specific time interval.
Time Zone The time zone that you want to be

used as reference for the configured
date and time.
Schedule to Recur Schedule to Recur From the dropdown, choose Daily,

Weekly, or Monthly based on how to
Select if you want to repeatedly trig
want the schedule to recur.
ger message processing according to
a specific schedule. Accordingly, if you choose
○ Weekly, choose the day or days of
the week
○ Monthly, choose the day of the
month from the dropdown list.
On Time Select the time at which you want the

Every Select this option if you want to trig

ger message processing repeatedly in
a specific time interval.

Option Field Description
Time Zone The time zone that you want to be

used as reference for the configured
date and time.
 Note
If you configure the Timer to trigger message processing on a specific time and date, and once this
message processing is completed, the integration flow will be in error state. You can see this in the
Manage Integration Content view in Monitor tab. This is because the configured time and date is in the
past and the integration flow cannot process any further messages.
4.15.6 Define Routing
Message routers enable you to define the message path. You can also perform operations like splitting the
message based on configured conditions and routing the split messages to different message paths.
 Note
The Throw Exception option is selected to set the behavior of the router to respond to error occurrence.
4.15.6.1 Define General Splitter
Prerequisites
● You have logged in to your customer workspace in the SAP Cloud Platform Integration web application.
● You are editing the integration flow in the editor.
Context
The General Splitter breaks down a composite message containing n messages into n individual messages.
Each individual message is enveloped by the same elements that enveloped the composite message.
If you use a Splitter step in a local integration process, the following limitations apply:
● You can use Splitter and Gather steps together, but you must close each Splitter step with a Gather step.

● You cannot use a Splitter without a child element.
● If a Splitter is used in combination with Gather, the message returned to the main process is the message
at the end of the local process.
● If a Splitter is used in the local process with a step other than Gather, the message returned to the main
process is the message before the Splitter step.
● Combinations with other steps may behave unexpectedly.
Procedure
1. In the palette, choose  (Message Routing), then Splitter General Splitter .

2. Place the General Splitter element in the integration process and define the message path.
3. On the General tab, you can change the name of the General Splitter element.
4. On the Processing tab, define the attributes of the element based on the descriptions in the following table.
Field Description
 Note which the message is to be split).
In the following cases certain features might not be

 Note
available for your current integration flow:
○ A feature for a particular adapter or step was re The defined Stop on Exception handling takes priority
leased after you created the corresponding over the end event defined in an exception subpro
shape in your integration flow. cess with respect to continuing with the next split. It
○ You are using a product profile other than the one means that the next split is only executed if Stop on
expected. Exception is not set.
More information: Adapter and Integration Flow Step If Stop on Exception is set, the next split is not exe
Versions [page 406] cuted, irrespective of the end event used in an excep
tion subprocess.
○ XPath
pression.
○ Line Break

Field Description
XPath Expression XPath to the split term
field)
 Note

ple, /A/B/C/D

XPath expression:
○ |
○ +
○ *
○ >
○ <
○ >=
○ <=
○ [
○ ]
○ @
 Note
tain convention:



that case.
 Caution

Field Description
<customerList>
<customers>
customerNumber>
customerName>
</customers>
<customers>
customerNumber>
<customerName>Seena
</customers>
</customerList>

customerNumber=0001
 Note
Note the following behavior if the specified XPath ex
pression does not match the inbound payload: If no
split point is found for the specified XPath, no out
bound payload will be generated from the Splitter
step and the integration flow will be ended with status
Completed.
is to be split.

nodes each.


runtime node).

than activating it.

Field Description
Parallel Processing Select this checkbox if you want to enable (parallel) proc
essing of all the split messages at once.
 Caution


tion occurs.
 Note
If Stop on Exception is set, the exception subprocess
stopped, and the message is set to Failed.
Next Steps
● CamelSplitIndex
● CamelSplitSize

Related Information

https://blogs.sap.com/2018/02/07/cloud-integration-usage-of-splitter-flow-steps-in-local-process/
https://blogs.sap.com/2018/10/17/cloud-integration-usage-of-general-and-iterating-splitter-with-exception-
handling/
https://blogs.sap.com/2018/10/17/cloud-integration-using-parallel-processing-in-general-and-iterating-
splitter/
4.15.6.2 Define Router
Prerequisites
Context
You perform this task when you have to specify conditions based on which the messages are routed to a
receiver or an interface during runtime. If the message contains XML payload, you form expressions using the
XPath-supported operators. If the message contains non-XML payload, you form expressions using the
operators shown in the table below:
Usage of Operators in Non-XML Conditions

Operator Example
= ${header.SenderId} = '1'
!= ${header.SenderId} != '1'
> ${header.SenderId} > '1'
>= ${header.SenderId} >= '1'
< ${header.SenderId} < '1'

Operator Example
<= ${header.SenderId} <= '1'
and ${header.SenderId}= '1' and ${header.ReceiverId} = '2'
or ${header.SenderId}= '1' or ${header.ReceiverId}= '2'
contains ${header.SenderId} contains '1'
not contains ${header.SenderId} not contains '1'
in ${header.SenderId} in '1,2'
not in ${header.SenderId} not in '1,2'
regex ${header.SenderId} regex '1.*'
not regex ${header.SenderId} not regex '1.*'
 Example
A condition with expression ${header.SenderId} regex '1.*' routes all the messages that have a
Sender ID starting with 1.
 Note
● You can define a condition based on property or exception that may occur.
● If the condition ${property.SenderId} = '1' is true, then Router routes the message to a
particular sender whose Sender ID is 1.
● If the condition ${exception.message}contains 'java.lang.Exception' is true, then Router
routes the message to a particular receiver, otherwise it routes to another receiver.
Procedure
1. In the palette, choose  (Message Routing), then Router.

2. Place the Router element in the integration process and define the message path.
3. Select either Router or the routing branch (Route) splitting from the router.
4. If you select Router, then execute the following steps:
a. On the General tab, you can change the name of the Router element.
b. On the Processing tab, select Throw Exception to respond to an error occurence.
You can also use Error End Event to raise an exception.

c. In the Routing Condition table, select the default route.
If you select Throw Exception, the default route must terminate with Terminate Message.
5. If you select Route, then execute the following steps.
a. On the General tab, you can change the name of the route.
b. On the Processing tab, from the Expression Type dropdown, select the type of expression used to
formulate the routing condition.
c. Select XML to form an expression using XPath or select Non-XML to form an expression using
message header, property, or exception.

d. In the Condition field, formulate a valid XML or non-XML condition that routes the message to its
associated receiver.
 Recommendation
We recommend that you ensure that the routing branches of a router are configured with the same
type of condition, either XML or non-XML, and not a combination of both. At runtime, the specified
conditions are executed in the same order. If the conditions are a combination of both non-XML
and XML type, the evaluation fails.
e. If you want to set the selected route as the default, so that its associated receiver handles the error
situation if no receiver is found, select the Default Route option.
 Note
Only the route that you last selected as Default Route is considered the default route.
4.15.6.3 Define Iterating Splitter
Prerequisites
Context
The Iterating Splitter splits a composite message into a series of smaller messages without copying the
enveloping elements of the composite message.
If you use a Splitter step in a local integration process, the following limitations apply:
● You can use Splitter and Gather steps together, but you must close each Splitter step with a Gather step.
● You cannot use a Splitter without a child element.
● If a Splitter is used in combination with Gather, the message returned to the main process is the message
at the end of the local process.
● If a Splitter is used in the local process with a step other than Gather, the message returned to the main
process is the message before the Splitter step.
● Combinations with other steps may behave unexpectedly.

Procedure
1. In the palette, choose  (Message Routing), then Splitter Iterating Splitter .

2. Place the Iterating Splitter element in the integration process and define the message path.
3. On the General tab, you can change the name of the Iterating Splitter element.
Field Description
which the message is to be split).
 Note
The defined Stop on Exception handling takes priority
over the end event defined in an exception subpro
cess with respect to continuing with the next split. It
means that the next split is only executed if Stop on
Exception is not set.
If Stop on Exception is set, the next split is not exe

cuted, irrespective of the end event used in an excep
tion subprocess.
○ XPath
pression.
○ Token
The splitter argument is specified by a keyword.
○ Line Break
Token (Enabled only if you select Token in the Expression The keyword or token to be used as a reference for split
Type field) ting the composite message

Field Description
XPath XPath to the split term
field)
 Note

ple, /A/B/C/D

XPath expression:
○ |
○ +
○ *
○ >
○ <
○ >=
○ <=
○ [
○ ]
○ @
 Note
tain convention:



that case.
 Caution

Field Description
<customerList>
<customers>
customerNumber>
customerName>
</customers>
<customers>
customerNumber>
<customerName>Seena
</customers>
</customerList>

customerNumber=0001
is to be split.

nodes each.


runtime node).

than activating it.
Parallel Processing Select this checkbox if you want to enable processing of all
the split messages at once.

Field Description
 Caution


tion occurs.
 Note
If Stop on Exception is set, the exception sub-process
stopped, and message is set to Failed.
Next Steps
● CamelSplitIndex
● CamelSplitSize

Related Information

https://blogs.sap.com/2018/02/07/cloud-integration-usage-of-splitter-flow-steps-in-local-process/
https://blogs.sap.com/2018/10/17/cloud-integration-usage-of-general-and-iterating-splitter-with-exception-
handling/
https://blogs.sap.com/2018/10/17/cloud-integration-using-parallel-processing-in-general-and-iterating-
splitter/
4.15.6.4 Define PKCS#7/CMS Splitter
Prerequisites
Context
You use a PKCS#7/CMS Splitter if you want to break down a PKCS7 Signed Data message into two files: one
containing the signature and one containing the content.
Procedure
1. In the palette, choose  (Message Routing), then Splitter PKCS#7/CMS Splitter .

2. Place the PKCS#7/CMS Splitter element in the integration process and define the message path.
3. On the General tab, you can change the name of the PKCS#7/CMS Splitter element.
Field Description
Payload File Name Name of the file that should contain the payload after the
splitting step

Field Description
Signature File Name Name of the file (extension .sig) that should contain the
signature after the splitting step
Wrap by Content Info Select this option if you want to wrap PKCS#7 signed data
containing the signature into PKCS#7 content.
PayloadFirst Select this option if you want the payload to be the first
message returned.
BASE64 Payload Select this option if you want to encode the payload with
the base64 encoding scheme after splitting.
BASE64 Signature Select this option if you want to encode the signature us
ing the base64 encoding scheme after splitting.
4.15.6.5 Defining Multicast
Prerequisites
You have logged into SAP Cloud Platform Integration and editing the integration flow.
Context
You can use the Multicast step to send copies of the same message to multiple routes. You can send copies to
all routes at once using Parallel Multicast or in an order of your choice using Sequential Multicast. This allows
you to perform multiple operations on the same message in a single integration process. Without Multicast, you
needed multiple integration processes to perform this task.
Procedure
1. In the palette, choose  (Message Routing), then Multicast .

2. Choose Parallel Multicast or Sequential Multicast based on your requirement and place the step inside the
integration process. Define the message paths based on the scenario.
Based on the order in which you define the message path, the system assigns names to each message
route branch as Branch 1, Branch 2, and so on.
3. If you want to specify a name for this step, enter the value in Name field.

4. If you are using Parallel Multicast, no further configuration is required for the multicast step.
5. If you are using Sequential Multicast, you can change the order in which the message should be sent to the
Sequential Multicast branches:
a. Choose Routing Sequence.
b. Select the branch which you want to move up or down in the order.
c. Use Move Up and Move Down buttons to change the order.
The branch name is dependent on the order in which you have defined the message path. If you change the
order, the branch name will not change.
4.15.6.6 Define EDI Splitter
Prerequisites
● You have logged in to your customer workspace in the SAP Cloud Platform Integration Web tools.
Context
You use the EDI splitter to split inbound bulk EDI messages, and configure the splitter to validate and
acknowledge the inbound messages. If you choose to acknowledge the EDI message, then the splitter
transmits a functional acknowledgement after processing the bulk EDI message. A bulk EDI message can
contain one or more EDI formats, such as EDIFACT, EANCOM, and ASC-X12. You can configure the EDI splitter
to process different EDI formats depending on the business requirements of the trading partners.

Procedure
1. In the palette choose , and choose Splitter EDI Splitter .

2. Choose EDI Splitter and provide values in property sheet based on the descriptions in the table.
Field Description
General
Name Define a relevant name for the EDI splitter or

use the default name.
Processing
Parallel Processing This mode creates multiple processes for

each split message, and individual EDI mes
sages are processed simultaneously.

Field Description
Timeout (in sec) Set the time limit in seconds for the EDI split
ter to process individual split messages. If
there are any processes still pending once the
time has lapsed, the splitter terminates the
processes and updates the MPL status.
EDIFACT

bound EDIFACT interchange. The following en
coding formats are available in the EDI split
ter:
○ UTF-8
○ ISO-8859-1

SAP_EDISPLITTER_EDIFACT_SOURCE_
ENCODING. The values for the headers can
○ UTF-8
○ ISO-8859-1
Validate Message This mode initiates the validation of the split

EDI messages.

SAP_EDISPLITTER_EDIFACT_VALIDAT
E_MESSAGE. The values for the headers can
○ true
○ false
Validate The EDI splitter performs validation of either

Envelope or Envelope and Message for the EDI
content.

SAP_EDISPLITTER_EDIFACT_VALIDAT
ION_METHOD. The values for the headers
can be one of the following:
○ envelop
○ envelopAndMessage

Field Description
Transaction Mode This feature is available only in Envelope and

Message validation mode. The following two
options are available:
○ Interchange
 Example
Consider a scenario where you receive a
bulk EDI message containing five pur
chase orders. In Interchange mode, if a
single EDI message fails, the entire inter
change is rejected. However, in Message
mode, if a single EDI message fails, only
the invalid message is rejected and the
valid messages are dispatched for further
processing.

SAP_EDISPLITTER_EDIFACT_TRANSAC
TION_MODE. The values for the headers can
○ interchange
○ message

Field Description


Integration Flow.
2. Choose Add.
3. Choose Select, to add a file from the XSD
folder found in the same integration
project.
 Note
During runtime only XSD’s from Inte
gration Content Advisor (ICA) are
supported.

SAP_EDISPLITTER_EDIFACT_SCHEMA_
SOURCE. The values for the headers can be
○ Header
Process Invalid Messages This feature is available only for Message op
tion in transaction mode. If you select this op
tion, you must use a router after the splitter to
process the split messages.
Use the following conditions to configure the

router to:
○ $
{header.SAP_EDI_MESSAGE_STAT
US}= 'failure' : Route all invalid
messages.
○ $
{header.SAP_EDI_INTERCHANGE_
STATUS}= 'failure' : Route all in
terchanges that has error.

Field Description

 Note

value, /xsd/UN-
IFACT.

value, /xsd/ASC-
X12_810_004010.xsd for ASC-X12.

Field Description
Create Acknowledgement The following options are available to process

the functional acknowledgement:
an EDI interchange.
 Note
Configure a router and apply the
routing condition $
{header.SAP_EDI_ACKNOWLED
GEMENT} = 'true' to route the
functional acknowledgement.

SAP_EDISPLITTER_EDIFACT_CREATE_
ACK. The values for the headers can be one of
the following:
○ required
○ notRequired
○ checkEDIEnvelop
 Note
In case of rules violation, you see the ac
knoedgement in a specific format. Here's
how the acknowledge is formatted:
AK4 is represented only for the first ele

ment of the conditional rule. For example,
AK4*2*358*2.
If there are two or more violations for a

single element, the same AK4 segment is
repeated for each violation. For example,
AK4*2*358*2 AK4*2*358*2
If there is an exclusive violation, AK4 is

represented for only the first element. For
example, AK4*2*358*10.

Field Description


SAP_EDISPLITTER_EDIFACT_INTERCH
ANGE_NUMBER. The values for the headers
○ numberRange
Number range Define the number range assigned to an inter

edgement.

SAP_EDISPLITTER_EDIFACT_NUMBER_
RANGE. The value for the header should be
the number range artifact name.
CONTRL Message Version Determine the appropriate EDIFACT CONTRL

message version to be transmitted to the
trading partner.

SAP_EDISPLITTER_EDIFACT_CONTRL_
MSG_VERSION. The values for the headers
○ defaultVersion
Include UNA Segment The trading partner uses the UNA segment in
the CONTRL message to define special char
acters, such as separators and indicators.
This option enables the splitter to include spe
cial characters in the CONTRL message. If not
selected, the UNA segment is not included in
the CONTRL message.

SAP_EDISPLITTER_EDIFACT_INCLUDE
_UNA. The values for the headers can be one
of the following:
○ true
○ false

Field Description
X12

bound X12 interchange. The following encod
ing formats are available in the EDI splitter:
○ UTF-8
○ ISO-8859-1

SAP_EDISPLITTER_X12_SOURCE_ENCO
DING. The values for the headers can be one
of the following:
○ UTF-8
○ ISO-8859-1
Validate Message The EDI splitter performs validation on incom

ing ASC X12 message against the XSD
scheme, and has the following options availa
ble during validation:
○ No Validation: Validation is not performed
on the incoming payload.
○ Standard Validation : Validates the incom
ing payload for the structural violations
defined in XSD schema.

SAP_EDISPLITTER_X12_VALIDATE_ME
SSAGE_OPTION. The values for the headers
○ none
○ basic
Transaction Mode The splitter has two modes for validating a

transaction:
tity.

SAP_EDISPLITTER_X12_TRANSACTION
_MODE. The values for the headers can be one
of the following:
○ interchange
○ message

Field Description


Integration Flow.
3. Choose Select to add an XML Schema file
from the XSD folder found in the integra
tion project.
 Note
○ During runtime only XSD’s from
Integration Content Advisor
(ICA) are supported.
○ If you wish to remove an XSD file
from the project, then select the
relevant XSD file and choose
Remove.

SAP_EDISPLITTER_X12_SCHEMA_SOUR
CE. The values for the headers can be one of
the following:
○ Header

Field Description

 Note

value, /xsd/UN-
IFACT.

value, /xsd/ASC-
X12_810_004010.xsd for ASC-X12.

Field Description
Create Acknowledgement The following options are available for proc

essing a functional acknowledgement:
an EDI interchange.
 Note
Configure a router and apply the
routing condition $
{header.EDI_ACKNOWLEDGEME
NT}='true' to process the func

SAP_EDISPLITTER_X12_CREATE_ACK.
following:
○ required
○ notRequired
○ checkEDIEnvelop


SAP_EDISPLITTER_X12_INTERCHANGE
_NUMBER. The values for the headers can be
○ numberRange

Field Description
Number Range Define the number range assigned to an inter

edgement.

SAP_EDISPLITTER_X12_NUMBER_RANG
E. The value for the header should be the
number range artifact name.
Exclude AK3 and AK4 Notifies the splitter to exclude the AK3 and
AK4 segments from the functional acknowl
edgement message. However, it retains the
details of the AK1, AK2, AK5, and AK9 seg
ments in the functional acknowledgement.

SAP_EDISPLITTER_X12_EXCLUDE_AK3
_AK4. The values for the headers can be one
of the following:
○ true
○ false
Error Codes for EDI Splitter
The error codes for UN-EDIFACT interchange and message levels are given below:
Interchange Level
2 Syntax version and/or level is not supported by the recipi

ent.
 Note
If you select Interchange transaction mode, the splitter treats the entire EDI interchange as a single
entity, and includes interchange errors in the acknowledgement.
Interchange and Message Level
18 An error has been identified, but the nature of the error is

not reported.
28 The control reference in UNB, UNG, or UNH does not

match the one in UNZ, UNE, or UNT respectively.

29 The number of groups, messages, or segments does not

match the number given in the UNZ, UNE, or UNT seg
ment.
30 Groups have been mixed with messages/packages out

side of groups in the interchange.
Message Level
12 The value of a stand-alone data element, composite data

element, or component data element does not conform to
the relevant specifications for the value.
13 Mandatory (or otherwise required) service or user seg

ment, data element, composite data element, or compo
nent data element is missing.
16 The identified segment contains too many data elements

or the identified composite data element contains too
many component data elements.
31 Different message types are contained in a functional

group.
35 A segment was repeated too many times.
36 A segment group is repeated to many times.
37 One or more numeric characters were used in an alpha

betic (component) data element or one or more alpha
betic characters were used in a numeric (component)
data element.
38 A decimal sign is not preceded by one or more digits.
39 The length of the data element received exceeds the maxi

mum length specified in the data element description.
40 The length of the data element received is shorter than

the minimum length specified in the data element descrip
tion.

The error codes for ASC-X12 are given below:
AK3 Segment Level Error Codes
Error Codes Error Text Notifies That...
3 Mandatory segment is missing.
4 Maximum number of loops exceeded.
5 Segment exceeds maximum use.
6 Segment is not defined in transaction set.
7 Segment is not in proper sequence.
AK4 Data Element Level Error Codes
1 Mandatory data element is missing.
3 Too many data elements.
4 Data element is too short.
5 Data element is too long.
6 Invalid character in data element.
7 Invalid code value.
8 Invalid date.
AK5 Transaction Set Level Error Codes
3 Transaction set control number in header and trailer do

not match.
4 Number of included segments does not match actual

count.
AK9 Functional Group Level Error Codes
4 Group control number in the functional group header and

trailer do not match.
5 Number of included transaction sets does not match ac

tual count.

 Example
UNB+UNOC:3+4006501000002:14+5790000016839:14+100818:0028+0650+++++XXXXX'
Header Name Value
UNB+UNOC:3+4006501000002:14+5790000016839:14+100818:0028+0650+++++XXXXX'
Header Name Value

Header Name Value
810*0001~
Header Name Value

Header Name Value
4.15.6.7 General and Iterating Splitter
The two splitter types General Splitter and Iterative Splitter behave differently in their handling of the
enveloping elements of the input message.
The General Splitter splits a composite message comprising N messages into N individual messages, each
containing one message with the enveloping elements of the composite message. We use the term enveloping
elements to refer to the elements above and including the split point.
The Iterative Splitter splits a composite message into a series of messages without copying the enveloping
elements of the composite message.
The following figures illustrate the behavior of both splitter types. In both cases an input message comprising
four items is split into individual messages.

General Splitter

Iterative Splitter
If you expect a non-XML file as the input message and, as a result, selectLine Break in the Expression Type field,
General Splitter and Iterative Splitter process the message differently, as shown for the following example.
Let's assume the input message has the following content:
 Sample Code

"0001", "100", "1000 EUR"
"0009", "1", "10000 EUR"
"0011", "20", "999 EUR"
The General Splitter would transform this into the following messages:

"0001", "100", "1000 EUR"

"0009", "1", "10000 EUR"

"0011", "20", "999 EUR"

The Iterative Splitter would transform this into the following messages:
"0001", "100", "1000 EUR"
"0009", "1", "10000 EUR"
"0011", "20", "999 EUR"
Example for General Splitter (XML Message)
Assume you expect an XML message and like to address elements with a Expression Type XPath. This is an
example for an input message representing items ordered by a certain customer.
<order id="100">
<items>
<item>Shirt</item>
<item>Shoe</item>
</items>
</order>
<order id="101">
<items>
<item>Shoe</item>
<item>Car</item>
<item>Watch</item>
</items>
</order>
</customer>
When configuring the General Splitter and like to address the message element with an XPath expression,
make sure that you refer to the namespace prefix.
/n1:customer/n1:order
 Note
Namespaces are inherited from parent to child element. This is why you need to indicate the namespace
explicitly in the XPath expression.
Then the message is split with the General Splitter into the following two chunks:
<order id="100">
<items>
<item>Shirt</item>
<item>Shoe</item>
</items>

</order>
</customer>
<order id="101">
<items>
<item>Shoe</item>
<item>Car</item>
<item>Watch</item>
</items>
</order>
</customer>
Example for Iterative Splitter (XML Message)
This is an example for an input message representing orders from different customers.
<customerList xmlns=”http://myCustomer.com”>
<customers>
</customers>
<customers>
</customers>
</customerList>
/n2:customerList/n2:customers
Then the message is split with the Iterative Splitter into the following two chunks:
<customers>
</customers>
<customers>
</customers>

4.15.6.8 Defining Gather and Join
Prerequisites
● You have accessed the customer workspace in SAP Cloud Platform Integration web application.
Context
The Gather step enables you to merge messages from more than one route in an integration process. You
define conditions based on the type of messages that you are gathering using the Gather step. You can choose
to gather:
● XML messages of different format

● XML messages of the same format
● Plain text messages
The Join element enables you to bring together the messages from different routes before combining them into
a single message. You use this in combination with the Gather element. Join only brings together the messages
from different routes without affecting the content of messages.
 Remember
● If you want to combine messages that are transmitted to more than one route by Multicast, you need to
use Join before using Gather.
● If you want to combine messages that are split using Splitter, you use only Gather.
Based on this, you choose the strategy to combine the two messages.
● For XML messages of the same format, you can combine without any conditions (multimapping format) or
specify the XPath to the node at which the messages have to be combined
● For XML messages of different formats, you can only combine the messages For plain text messages, you
can only specify concatenation as the combine strategy
● Specify valid xpath expression that includes namespace prefixes if incoming payload contains namespace
declarations, including default namespace declarations
If your incoming payload contains namespace declarations including default namespace, ensure that you
specify xpath with namespace prefixes. Also ensure that the namespace prefix mapping is defined in the
runtime configuration. If the xpath you have defined does not exist in any of the branches of the incoming XML,
the scenario fails with an exception.
Consider the following XML:
 Sample Code
<root xmlns="http:defaultnamespace.com">
<f:table xmlns:f="http://www.w3schools.com/furniture">

<f:name>African Coffee Table</f:name>
<f:width>80</f:width>
<f:length>120</f:length>
</f:table>
<table>
<name>African Coffee Table</name>
<width>80</width>
<length>120</length>
</table>
</root>
f and d are the prefixes defined in the Namespace Mapping field of Runtime Configuration and mapped to the
namespaces http://www.w3schools.com/furniture and http:defaultnamespace.com respectively. Examples of
valid xpaths for the above XML are:
● //f:table
● /d:root/f:table
● /d:root/d:table
 Note
You can only edit the properties of gather and the integration elements of the integration flow that support
editing. Modeling palette is not available for integration flows containing gather.
Procedure
1. Choose the gather element you want to configure.

2. In Incoming Format dropdown list, select value based on description in table.
Value Description
XML (Same Format) If messages from different routes are of the same format
XML (Different Format) If messages from different routes are of the different for
mat
Plain Text If messages from different routes are of the plain text for
mat
3. In Aggregation Algorithm dropdown list, select value based on description in table.
Incoming Format Aggregation Algorithm Description Additional Fields Description
XML (Same Format) Combine Combine the NA NA

incoming messages
without any
conditions. The
messages are

combined in
Multimapping format.
 Note
In case you are
using the
mapping step to
map the output
of this strategy
you can have the
source XSD in the
LHS and specify
the Occurrence
as 0..Unbounded.
Combine at XPath Combine the Combine from Source XPath of the node
incoming messages (XPath) that you are using as
at the specified XPath reference in the
source message to
retrieve the
information.
Combine at Target Path to node which

(Path) would act as the root
for combined
message
XML (Different Combine Combine the NA NA

Format) incoming messages
without any
conditions in multi
mapping format.
 Note
In case you are
using the
mapping step to
map the output
of this strategy
you can add the
XSD’s from the
different
multicast
branches one

after another in
LHS. The
sequence of the
messages is
important and so
this strategy
makes sense only
with the
sequential
multicast.
Plain Text Concatenate Concatenate the NA NA

information from the
different sources one
after another
This flow element does not work directly with Router. It is recommended to model the flow using Local
Integration Process.
4.15.6.9 Define Aggregator

You can use the Aggregator step to combine multiple incoming messages into a single message.
Prerequisites
 Caution
Context
 Note
When you use the Aggregator step in combination with a polling SFTP sender adapter and you expect a
high message load, please consider the following recommendation:
For the involved in SFTP sender adapter set the value for Maximum Messages per Poll to a small number
which is larger than 0 (for example, 20) (under Advanced Parameters). That way, you ensure a proper
message processing status logging at runtime.

Procedure
1. In the palette, choose Aggregator .

2. Place Aggregator in the integration process and define the message path.
3. Specify the attributes of the aggregator.
Incoming Format Content type of the incoming message
Currently, only XML (Same Format) can be selected.
It is important that the incoming messages have the same

format.
Aggregation Algorithm Specifies how the correlated messages should be treated.
○ Combine in Sequence
messages, and the original messages are put into a
sequence.
○ Combine
messages.
The Aggregator step generates an SAP Process Integra

tion multi mapping as specific format. This is important
to know because the integration developer typically has to
create a mapping from the generated format to the mes
sage structure required by the receiver.
Message Sequence Expression (XPath) Enter an XPath expression for that message element
based on which a sequence is being defined.
(only if for Aggregation Algorithm the option Combine in
Sequence has been selected) You can use only numbers to define a sequence. Each se
quence starts with 1.

Last Message Condition (XPath) Define the condition (XPATH = value) to identify the
last message of an aggregate.

following values:
○ timeout
reached.
○ predicate
Completion Timeout Defines the maximum time between two messages before
aggregation is being stopped (period of inactivity).

following values:
○ timeout
reached.
○ predicate

Data Store Name Enter the name of the transient data store where the ag
gregated message is to be stored. The name should begin
with a letter and use characters (aA-zZ, 0-9, - _ . ~ ).
Note that only local data stores (that apply only to the in
tegration flow) can be used. Global data stores cannot be
used for this purpose.
 Note
The Integration Operations feature provides a Data
Store Viewer that allows you to monitor your transient
data stores.
Next Steps
The following header is supported by this step:
○ timeout
reached.
○ predicate
4.15.7 Define Message Transformers
Message transformers enable you to convert messages in one format to another.
Here's a list of the message transfermers available in SAP Cloud Platform Integration and links to their
documentation.
Message Transformer Documentation Link
EDI Extractor
CSV to XML Converter Configure CSV to XML Converter [page 734]
XML to CSV Converter Configure XML to CSV Converter [page 735]

Message Transformer Documentation Link
JSON to XML Converter Define JSON to XML Converter [page 737]
XML to JSON Converter Define XML to JSON Converter [page 741]
EDI to XML Converter Define EDI to XML Converter [page 748]
XML to EDI Converter Define XML to EDI Converter [page 755]
Content Modifier Define Content Modifier [page 766]
Encoder Define an Encoder [page 778]
Decoder Define a Decoder [page 781]
Message Digest Define Message Digest [page 222]
Script Define Script [page 785]
Filter Define Filter [page 782]
4.15.7.1 Configure CSV to XML Converter
Prerequisites
● You have logged into your customer workspace.

Context
The CSV to XML converter converts content in CSV format into XML format.
You use this procedure to configure CSV to XML converter.
Procedure
1. In the palette, choose Converter CSV to XML Converter .

2. Place the CSV to XML converter in the integration process and define the message path.
3. Choose CSV to XML Converter and provide values in fields based on description in table.
Field Description
XML Schema Choose Browse. Select the XML schema you want to use.
Optionally, you can also upload the XML schema from

your local file system by choosing Upload from File
System.
Path to Target Element in XSD XPath in the XML schema file where the content from CSV
file has to be placed.
Record Marker in CSV The record in CSV file that indicates the entry which the
converter has to consider as the starting point of the con
tent.
 Note
If you do not provide a value for this field, all the re
cords in the CSV file are considered for conversion
Field Separator in CSV Select the character from dropdown list that is used as
the field separator in CSV file.
 Tip
If you want to use a field separator that is not available
in the dropdown list, manually enter the character.
4. If you want to exclude the header information in first line of CSV file for conversion, select Exclude First Line
Header checkbox.
4.15.7.2 Configure XML to CSV Converter
Prerequisites
● You have logged into your customer workspace.


Context
The XML to CSV converter converts content in XML format into CSV format.
 Note
Note that for the schema of the source XML document only simple type is supported.
You use this procedure to configure XML to CSV converter.
Procedure
1. In the palette, choose Converter XML to CSV Converter .

2. Place the XML to CSV converter in the integration process and define the message path.
3. Choose XML to CSV Converter and provide values in fields based on description in table.
Field Description
Path to Source Element in XSD Path to the source element in the XSD file
Field Separator in CSV Select the character that you want to use as the field sep
arator in CSV file from dropdown list
 Tip
If you want to use a field separator that is not available
in the dropdown list, manually enter the character.
Include Field Name as Headers Select this checkbox if you want to use the field names as
the headers in CSV file
Include Parent Element Select this checkbox if you want to include the parent ele
ment of the XML file in CSV file
Include Attribute Values Select this checkbox if you want to include attribute val
ues in the CSV file

4.15.7.3 Define JSON to XML Converter
The JSON to XML converter enables you to transform messages in JSON format to XML format.
Prerequisites
● You are familiar with the conversion rules for JSON to XML conversion.
For more information see Conversion Rules for JSON to XML Conversion [page 738].
● You are familiar with the limitations for JSON to XML conversion.
For more information see Limitations for JSON to XML Conversion [page 739].
Procedure
1. Launch SAP Cloud Platform Integration web application by accessing the URL provided by SAP.
4. In the Package content view, choose the integration flow you want to edit.
5. In the Integration Package Editor page, choose Edit.
6. In the palette, choose Transformation Converter JSON to XML Converter .

7. Insert the converter at the desired position in your integration process.
The converter appears as a graphical element in your integration process.
The properties tab page for the XML to JSON Converter opens.
8. Define the parameters for your conversion, see table below.
Option Description
JSON Prefix (only if the option Use Namespace Mapping is Enter the mapping of the JSON prefix to the XML name
selected) space. The JSON namespace/prefix must begin with a let
ter and can contain aA-zZ and 0-9.
JSON Prefix Separator Enter the JSON prefix separator to be used to separate
the JSON prefix from the local part. The value used must

9. If you want to continue editing the integration package without exiting, choose Save.

10. If you want to retain your changes as a variant, choose Save as version to retain a copy of the current
artifact.
11. If you want to terminate the creation of package, choose Cancel before saving it.
Related Information

Define Message Transformers [page 733]
4.15.7.3.1 Conversion Rules for JSON to XML Conversion
To ensure a successful conversion of you data, you should make yourself familiar with the conversion rules.
The conversion from JSON format to XML format follows the following rules:
"$":"value".
appears twice.
● A member with JSON null value is transformed to empty element; example: "C":null is converted to
<C/>.
● Conversion of "@attr":null to XML is not supported (you get a NullPointerException, since cluster
version 1.21 you get a JsonXmlException).
● The result XML document is encoded in UTF-8 and gets the XML header "<?xml version='1.0'
encoding='UTF-8'?>".
● The content of the XML-Namespace-to-JSON-Prefix map is transformed to namespace prefix declarations
on the root element.
● If for a JSON prefix no XML Namespace is defined, then the full member name with the prefix and JSON
delimiter is set as element name: "p.A" leads to <p.A>.

Related Information

4.15.7.3.2 Limitations for JSON to XML Conversion
To ensure a successful conversion frrm JSON to XML format you have to know the limitations for this
conversion.
The JSON to XML conversion has the following limitations:
● Conversion of "@attr":null to XML is not supported. You get a NullPointerException; as of cluster version
1.21 you get a JsonXmlException.
● JSON member names must not contain in their local or prefix part any characters that are not allowed for
XML element/attribute names (for example, space or column (':') are not allowed). XML element/attribute
names are of type NCName (see http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName
).
● JSON texts that start with an array (for example, [{"a":{"b":"bvalue"}}] ) are not supported. The
JSON text must start with a JSON object such as {{"a":{"b":"bvalue"}}}. A
javax.xml.stream.XMLStreamException is thrown. As of cluster version 1.21, a JsonXmlException is thrown.
● The root JSON object must contain exactly one member. If the root JSON object contains more than one
member (for example, {"a":"avalue","b":"bvalue"}), a javax.xml.stream.XMLStreamException is
thrown. If the root JSON object is empty ({}), a javax.xml.stream.XMLStreamException is thrown. As of
cluster version 1.21, a JsonXmlException or IllegalStateException (for {}) is thrown.
 Tip
If you need to convert a JSON file that doesn't fulfil this requirement, you can do the following:
Add a content modifier before the JSON to XML converter that changes the message body. In the entry
field in tab Message Body, enter:
{"root": ${in.body}}
● If no XML namespace is defined for a JSON prefix, the full member name with the prefix and JSON
delimiter is set as the element name: "p:A" -> <p:A>.
Related Information

Conversion Rules for JSON to XML Conversion [page 738]

4.15.7.3.3 Example: Transformations from JSON format to
XML format with and without Namespace
Mapping

● The JSON-prefix-to-XML-namespace mapping is as follows:
JSON Prefix XML Namespace
abc http://com.sap/abc
xyz http://com.sap/xyz
We get the following XML document:

<abc:A xmlns:abc="http://com.sap/abc" xmlns:xyz="http://
com.sap/xyz"><xyz:B xyz:attr1="1" attr2="2">valueB</xyz:B><C>valueC1</
C><C>valueC2</C><D/><E>valueE<E></abc:A>
{"abc.A":{"xyz.B":{"@xyz.attr1":"1","@attr2":"2","$":"valueB"},"C":

We get the followingXML document:
<?xml version='1.0' encoding='UTF-8'?><A><B attr1="1" attr2="2">valueB</

B><C>valueC1</C><C>valueC2</C><D/><E>valueE<E></A>

4.15.7.4 Define XML to JSON Converter
The XML to JSON converter enables you to transform messages in XML format to JSON format.
Prerequisites
● You are familiar with the conversion rules for XML to JSON conversion.
For more information see Conversion Rules for XML to JSON Conversion [page 743].
● You are familiar with the limitations for XML to JSON conversion.
For more information see Limitations for XML-to-JSON Conversion [page 744].
● You are familiar with streaming for XML to JSON conversion.
For more information see How Streaming in the XML-to-JSON Converter Works [page 745]
Procedure
1. Launch the SAP Cloud Platform Integration web application by accessing the URL provided by SAP.
6. In the palette, choose Transformation Converter XML to JSON Converter .
Your cusor symbol

7. Insert the converter at the desired position in your integration process.
The converter appears as a graphical element in your integration process.
The properties tab page for the XML to JSON-Converter opens.

8. Define the parameters for your conversion, see table below.
Option Description
JSON Output Encoding Enter the JSON output encoding. The default value is from
header or property.
If you select from header or property, the converter tries to

read the encoding from the message header or exchange
property CamelCharsetName. If there is no value de
fined, UTF-8 is used.

Option Description
XML Namespace (only if the option Namespace Mapping If you select from header or property, the converter tries
is selected) to read the encoding from the message header or ex
change property CamelCharsetName. If there is no value
defined, UTF-8 is used.
JSON Prefix Separator (only if the option Namespace Enter the JSON prefix separator to be used to separate
Mapping is selected) the JSON prefix from the local part. The value used must

Suppress JSON Root Element Choose this option to create the JSON message without
the root element tag.
9. Specify whether to enable Streaming or not.
With streaming you can specify whether the whole XML document or only specified XML elements are to
be presented by JSON arrays.
All All elements are presented as JSON arrays.
Specific Ones Only the specified elements will be represented as JSON

arrays, the others as JSON objects.
 Note
A JSON object is an unordered set of name/value
pairs that begins with { and ends with }. Each name
is followed by : and the name/value pairs are sepa
rated by ,.
A JSON array is an ordered collection of values. An ar

ray begins with [ and ends with ]. Values are sepa
rated by ,.
Enter the absolute paths to the XML elements to be con

verted to JSON arrays. Specify all elements with a multi
plicity larger than one. Otherwise, it cannot be ensured
that streaming will result in a valid JSON document.
Familiarize yourself with streaming in the XML-to-JSON

converter, as documented in a separate topic.
11. If you want to retain your changes as a variant, choose Save as version to retain a copy of the current
artifact.

4.15.7.4.1 Conversion Rules for XML to JSON Conversion
To ensure a successful conversion from XML format to JSON format, you should make yourself familiar with
the conversion rules.
The conversion from XML format to JSON format follows the following rules:
appears twice.
"$":"value".
● Elements with mixed content (for example. <A>mixed1_value<B>valueB</B>mixed2_value</A>) are
not supported. Currently you get wrong results for XML to JSON: {"A":
{"B":"valueB","$":"mixed1_valuemixed2_value"}} in the non-streaming case or
{"A":"$":mixed1_value","B":"valueB","$":"mixed2_value"}} in the streaming case.
● All element/attribute values are transformed to JSON string.
● No namespace declaration is written into the JSON document.
● Tabs, spaces, new lines between elements and attributes are ignored. However, a white space value of an
element with simple type is represented in JSON; example <A> </A> is represented by "A":" ".
● If you have an element with namespace but without XML prefix whose namespace is not contained in the
XML-namespace-to-Json-prefix map, then you get an exception: <A xmlns="http://test"/> leads to
IllegalStateException Invalid JSON namespace: http://test.
This is not the case if you choose the streaming option. With streaming the namespace is just ignored: <A
xmlns="http://test"/>v</A> leads to {"A":"v"}.
● If you have an element with namespace and XML prefix whose namespace is not contained in the XML-
namespace-to-Json-prefix map then the XML prefix is used as JSON prefix <ns:A xmlns:ns:="http://
test"/> leads to "ns.A":"" (if JSON delimiter is '.').
Related Information


4.15.7.4.2 Limitations for XML-to-JSON Conversion
To ensure a successful conversion form XML to JSON format you have to know the limitations for this
conversion.
The XML to JSON conversion has the following limitations:
● XML comments () are not represented in the JSON document; they are ignored.
● DTD declarations are not represented in the JSON document; they are ignored.
● XML processing instructions are not represented in the JSON document; they are ignored.
● No conversion to JSON primitive types for XML to JSON. All XML element/attribute values are transformed
to a JSON string.
● Entity references (except the predefined entity references & < > " ') are not
represented in the JSON document; they are ignored.
● If a sibling with another name resides between XML sibling nodes with the same name, then the order of
the siblings is not kept in JSON in the non-streaming case, because siblings with the same name are
represented by one array. Example: <root><childA>A1</childA><childB>B</
childB><childA>A2</childA></root> leads to {"root":{"childA":
["A1","A2"],"childB":"B"}}.
In the streaming case this leads to an invalid JSON document: {"root":{"childA":
["A1"],"childB":"B","childA":["A2"]}.
● If you have an element with a namespace but no XML prefix whose namespace is not contained in the XML-
namespace-to-JSON-prefix map, you get an exception: <A xmlns="http://test"/> -> IllegalStateException
Invalid JSON namespace: http://test.
If you choose the streaming option, the namespace is ignored: <A xmlns="http://test"/>v</A> leads
to {"A":"v"}.
Related Information


4.15.7.4.3 How Streaming in the XML-to-JSON Converter
Works
During streaming the XML document is processed in parts or segments:
The individual tags of an XML document are processed consecutively,irrespective of where in the overall
structure the tag occurs and how often (multiplicity). This means that during the streaming process the
converter cannot know if an element occurs in the structure more than once. In other words, during the
streaming process the object model that reflects the overall structure of the XML document (and, therefore,
also all information that can only be derived from the object model, like the multiplicity of elements) is not in
place. This is different to the non-streaming case, where the converter can calculate the multiplicity of the XML
elements from the object model of the complete XML document. The multiplicity is needed to create a correct
JSON document. Elements whose multiplicity is greater than one must be transformed to a JSON member
with an array. For example, you may think that for the XML document <root><B>b1</B><B>b2</B></root>,
you create the JSON document {“root”:{“B”:”b1”,”B”:”b2”}}. However, this JSON document is invalid,
because the member name “B” occurs twice on the same hierarchy level.
To ensure nevertheless a conversion that creates correct JSON documents during streaming, you need to
either manually provide the information about which XML elements are multiple in advance, or decide that
every XML element is converted to a JSON array (when configuring the converter in the Integration Designer).
To illustrate this behavior, let’s consider how the following simple XML structure has to be converted to JSON:
<root>
<A>a</A>
<B>b1</B>
<B>b2</B>
<C>c</C>
</root>
Note that the element root/B occurs twice (multiplicity = 2).
Without streaming, the converter would produce the following JSON structure:
{"root":{"A":"a","B":["b1","b2"],"C":"c"}}
As expected, the XML element root/B would transform into a JSON member with an array as value, where the
array has two values (b1 and b2) – according to the multiplicity of root/B. Note that a JSON array is indicated
by the following type of brackets: [ … ].
With streaming with all elements to JSON arrays, the converter would produce the following JSON structure:
{"root":[{"A":["a"],"B":["b1","b2"],"C":["c"]}]}
All XML elements are transformed into members with a JSON array as value.
With streaming and specific elements as arrays (where root/A and root/B are specified), the converter would
produce the following JSON structure:
{"root":{"A":["a"],"B":["b1","b2"],"C":"c"}}
An array is produced only for the XML elements root/A and root/B, but not for root/C.
With streaming and specific elements as arrays (where only root/A is specified), the converter would produce
the following invalid JSON structure:
{"root":{"A":["a"],"B":"b1",”B”:"b2","C":"c"}}

4.15.7.4.4 Example: Transformations from XML format to
JSON format with and without Namespace
Mapping
 Example

<n1:A xmlns:n1="http://com.sap/abc" xmlns:n2="http://
com.sap/xyz">
<n2:B n2:attr1="1" attr2="2">valueB</n2:B>
<C>valueC1</C>
<C>valueC2</C>
<D/>
<E>valueE<E>
</n1:A>

● The XML-namespace-to-JSON-prefix mapping is as follows:
XML Namespace JSON Prefix
http://com.sap/abc abc
http://com.sap/xyz xyz
We get the following JSON document:
 Note
Line breaks and spaces between the elements are ignored.

 Example

<abc:A xmlns:abc="http://com.sap/abc"
xmlns:xyz="http://com.sap/xyz"><xyz:B xyz:attr1="1" attr2="2">valueB</
xyz:B><C>valueC1</C><C>valueC2</C><D/><E>valueE</E></abc:A>
For the transformation we choose the following settings:

We get the following JSON Document:
{"A":{"B":{"@attr1":"1","@attr2":"2","$":"valueB"},"C":
4.15.7.4.5 Example: Transformation to a JSON Message

without Root Element Tag
Examples and Special Cases of JSON Message without Root Element Tag
The following examples apply to XML-to-JSON conversion:
 Example
The following example shows the transformation from XML to JSON (option Suppress JSON Root Element
is selected).
Input XML Message
<root>
<A>a</A>
<B>b</B>
<C>c</C>
<D>d</D>
</root>
Output JSON Message
{
"A": "a",
"B": "b",
"C": "c",
"D": "d"
}
Special Cases

Input XML Message: Root Element with Simple Value
<root>v</root>
Output JSON Message
"v"
Input XML Message: Root Element with no Value
<root></root>
Output JSON Message
""
Input XML Message: Root Element with Simple Value (options Suppress JSON Root Element, Steaming All
are selected)
<root><A>a<A><B><C>c</C></B></root>
Output JSON Message
{"A":["a"],"B":[{"C":["c"]}]}
with dropRootElement=false
{"root":{["A":["a"],"B":[{"C":["c"]}]]}}
4.15.7.5 Define EDI to XML Converter
The EDI to XML converter enables you to transform single incoming EDI messages from EDI to XML format.
Prerequisites
You needSAP Cloud Platform Integration Enterprise Edition licence.
Context
Use the procedure here to convert EDIFACT and ASC-X12 format into XML format.

Procedure
6. In the graphical editor of integration flow, choose the EDI to XML Converter element..
7. Define the parameters to convert the EDI data format to XML data format.
Field Description
Source Encoding Select encoding format for the incoming payload.
EDI Schema Definition Select the source of schema definition.

Field Description
Schemas If you select Integration Flow as EDI Schema

Definition, then you can see the table Schemas, in
Properties view. Select the valid schemas against which
the conversion will take place.
 Note
○ You can add XSD files to the integration flow. For
more details, please refer to the topic Validating
Message Payload against XML Schema, in de
veloper's guide.
○ The file name of the xml schema for EDIFACT
UN-EDIFACT_ORDERS_D96A.xsd
separated by '_':
○ First part "UN-EDIFACT" refers to the EDI
○ Second part "ORDERS" refers to the mes
sage type.
○ Third part "D96A" refers to the version .
○ The file name of the xml schema for ASC-X12
ASC-X12_810_004010.xsd
separated by '_':
○ First part "ASC-X12" refers to the ASC-X12
○ Second part "810" refers to the message
type.
○ Third part "004010" refers to the version .
○ The above mentioned values should match with
schema content.
○ During runtime only XSD’s from Integration Con
tent Advisor (ICA) are supported.

Field Description
HeaderName If you select Header as EDI Schema Definition, then you

can see the field HeaderName, in Properties view. Enter a
valid header name for the field.
 Note
This header name is fetched from camel header. The
header is added in script element. This script element
is added before converter element. You can add value
for this header in the script element.
For example, you can add the value, /xsd/UN-

EDIFACT_ORDERS_D96A.xsd for EDIFACT.
For example, you can add the value, /xsd/ASC-

X12_810_004010.xsd for ASC-X12.
Exclude Interchange and Group envelopes If selected the feature notifies the converter to exclude the
interchange and group envelopes found in an EDI docu
ment.
 Note
 Note
SAP_EDI_Document_Number header contains document number for the single incoming EDI file.
 Example
● The following example shows the transformation from EDI to XML format of EDIFACT message.
Input sample EDIFACT EDI Message
UNA:+.? '
++A+++1'

BGM+220+MY_ID+9+NA'
DTM+137:201507311500:203'
DTM+2:201508010930:203'
CNT+16:10'
UNT+5+1'
UNZ+1+1'
Output sample EDIFACT XML Message

<S_UNA>:+.? '</S_UNA>
<S_UNB>
<C_S001>
<D_0001>UNOC</D_0001>
<D_0002>3</D_0002>
</C_S001>
<C_S002>
<D_0007>14</D_0007>
<D_0008>XXXX</D_0008>
</C_S002>
<C_S003>
<D_0007>14</D_0007>
<D_0014>YYYYY</D_0014>
</C_S003>
<C_S004>
<D_0017>150831</D_0017>
<D_0019>1530</D_0019>
</C_S004>
<D_0020>1</D_0020>
<C_S005>
</C_S005>
<D_0029>A</D_0029>
<D_0035>1</D_0035>
</S_UNB>
<M_ORDERS>
<S_UNH>
<D_0062>1</D_0062>
<C_S009>
<D_0065>ORDERS</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
</C_S009>
<C_S010>
<D_0070>2</D_0070>
</C_S010>
</S_UNH>
<S_BGM>
<C_C002>
<D_1001>220</D_1001>
</C_C002>
<D_1004>MY_ID</D_1004>
<D_1225>9</D_1225>
<D_4343>NA</D_4343>
</S_BGM>
<S_DTM>
<C_C507>
<D_2005>137</D_2005>
<D_2380>201507311500</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_DTM>

<C_C507>
<D_2005>2</D_2005>
<D_2380>201508010930</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_CNT>
<C_C270>
<D_6069>16</D_6069>
<D_6066>10</D_6066>
</C_C270>
</S_CNT>
<S_UNT>
<D_0074>5</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</M_ORDERS>
<S_UNZ>
<D_0036>1</D_0036>
<D_0020>1</D_0020>
</S_UNZ>
</Interchange>
● The following example shows the transformation from EDI to XML format of ASC-X12 message.
Input sample ASC-X12 EDI Message
 Sample Code
ISA*00* *00* *01*784849291 *01*315029991

*051007*0928*/*4010 *000000001*0*P*^~
GS*PO*784849291*315029991*20051007*0928*1*U*004010~
ST*850*10001~
BEG*00*NE*228914**20051006~
CUR*BY*EUR*0100~
LIN**MF*2109308~
SCH*17*EA***002*20060401~
CTT*1~
SE*10*10001~
GE*1*1~
IEA*1*000000001~
Output sample ASC-X12 XML Message

<S_ISA>
<D_I01>00</D_I01>
<D_I02> </D_I02>
<D_I03>00</D_I03>
<D_I04> </D_I04>
<D_I05_1>01</D_I05_1>
<D_I06>784849291 </D_I06>
<D_I05_2>01</D_I05_2>
<D_I07>315029991 </D_I07>
<D_I08>051007</D_I08>
<D_I09>0928</D_I09>
<D_I10>/</D_I10>
<D_I11>4010 </D_I11>
<D_I12>000000001</D_I12>
<D_I13>0</D_I13>
<D_I14>P</D_I14>
<D_I15>^</D_I15>
</S_ISA>

<S_GS>
<D_479>PO</D_479>
<D_142>784849291</D_142>
<D_124>315029991</D_124>
<D_373>20051007</D_373>
<D_337>0928</D_337>
<D_28>1</D_28>
<D_455>U</D_455>
<D_480>004010</D_480>
</S_GS>
<M_850>
<S_ST>
<D_143>850</D_143>
<D_329>10001</D_329>
</S_ST>
<S_BEG>
<D_353>00</D_353>
<D_92>NE</D_92>
<D_324>228914</D_324>
<D_373>20051006</D_373>
</S_BEG>
<S_CUR>
<D_98_1>BY</D_98_1>
<D_100_1>EUR</D_100_1>
<D_280>0100</D_280>
</S_CUR>
<G_N1>
<S_N1>
<D_98_1>SF</D_98_1>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_N1>
<S_N1>
<D_98_1>ST</D_98_1>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_PO1>
<S_PO1>
<D_350>10000</D_350>
<D_330>17</D_330>
<D_355>EA</D_355>
<D_212>91.8074</D_212>
<D_639>EA</D_639>
<D_235_1>BP</D_235_1>
<D_234_1>2112910003</D_234_1>
<D_235_2>PD</D_235_2>
<D_234_2>Radiator</D_234_2>
</S_PO1>
<S_LIN>
<D_235_1>MF</D_235_1>
<D_234_1>2109308</D_234_1>
</S_LIN>
<G_SCH>
<S_SCH>
<D_380>17</D_380>
<D_355>EA</D_355>
<D_374_1>002</D_374_1>
<D_373_1>20060401</D_373_1>
</S_SCH>
</G_SCH>
</G_PO1>
<G_CTT>

<S_CTT>
<D_354>1</D_354>
</S_CTT>
</G_CTT>
<S_SE>
<D_96>10</D_96>
<D_329>10001</D_329>
</S_SE>
</M_850>
<S_GE>
<D_97>1</D_97>
<D_28>1</D_28>
</S_GE>
<S_IEA>
<D_I16>1</D_I16>
<D_I12>000000001</D_I12>
</S_IEA>
</ns0:Interchange>
4.15.7.6 Define XML to EDI Converter
The XML to EDI converter transforms a XML message in XML format to EDI format. You can convert EDIFACT
and ASC-X12 format into XML format.
Context
Procedure
6. In the graphical editor of integration flow, choose the XML to EDI Converter element..
7. Define the parameters to convert the XML data format to EDI data format.
General Name Enter a name for the flow step.
EDIFACT Source Encoding Select encoding format for the incom

ing payload.

EDI Schema Definition Select the source of schema defini-

tion.
Schemas If you select Integration Flow as EDI

 Note
against XML Schema.
X12_810_004010.xsd. It con
by _:
to the version.
schema content.

HeaderName If you select Header as EDI Schema

 Note
Camel header. The header is
the converter element. You can
add value for this header in the
script element.

value, /xsd/UN-
EDIFACT_ORDERS_D96A.xs
d.

 Note
custom separator.

{header.HEADER_NAME
}
X12 Source Encoding Select encoding format for the incom

ing payload.

EDI Schema Definition If you select Integration Flow as EDI

 Note
against XML Schema, in de
veloper's guide.
X12_810_004010.xsd. It con
by _:
to the version.
schema content.
○ During runtime only XSD’s
from Integration Content Ad
visor (ICA) are supported.


 Note
camel header. The header is
converter element. You can add
value for this header in the script
element.

value, /xsd/ASC-
X12_810_004010.xsd.

 Note
custom separator.

{header.HEADER_NAME
}
 Note

○ SAP Cloud Platform Integration generates EDI file which uses the following separators for EDIFACT
message:
○ Data Element separator +
○ Segment separator ‘
○ SAP Cloud Platform Integration generates EDI file which uses the following separators for ASC-X12
message:
○ Data Element separator *
○ Segment separator ~
○ During runtime only XSD’s from Integration Content Advisor (ICA) are supported.
 Note
SAP_EDI_Document_Number header contains document number for the single incoming EDI file.
○ The following example shows the transformation from XML to EDI format of EDIFACT message.
Input sample EDIFACT XML Message

<S_UNA>:+.? '</S_UNA>
<S_UNB>
<C_S001>
<D_0001>UNOC</D_0001>
<D_0002>3</D_0002>
</C_S001>
<C_S002>
<D_0007>14</D_0007>
<D_0008>XXXX</D_0008>
</C_S002>
<C_S003>
<D_0007>14</D_0007>
<D_0014>YYYYY</D_0014>
</C_S003>
<C_S004>
<D_0017>150831</D_0017>
<D_0019>1530</D_0019>
</C_S004>
<D_0020>1</D_0020>
<C_S005>
</C_S005>
<D_0029>A</D_0029>
<D_0035>1</D_0035>
</S_UNB>
<M_ORDERS>

<S_UNH>
<D_0062>1</D_0062>
<C_S009>
<D_0065>ORDERS</D_0065>
<D_0052>D</D_0052>
<D_0054>96A</D_0054>
<D_0051>UN</D_0051>
</C_S009>
<C_S010>
<D_0070>2</D_0070>
</C_S010>
</S_UNH>
<S_BGM>
<C_C002>
<D_1001>220</D_1001>
</C_C002>
<D_1004>MY_ID</D_1004>
<D_1225>9</D_1225>
<D_4343>NA</D_4343>
</S_BGM>
<S_DTM>
<C_C507>
<D_2005>137</D_2005>
<D_2380>201507311500</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_DTM>
<C_C507>
<D_2005>2</D_2005>
<D_2380>201508010930</D_2380>
<D_2379>203</D_2379>
</C_C507>
</S_DTM>
<S_CNT>
<C_C270>
<D_6069>16</D_6069>
<D_6066>10</D_6066>
</C_C270>
</S_CNT>
<S_UNT>
<D_0074>5</D_0074>
<D_0062>1</D_0062>
</S_UNT>
</M_ORDERS>
<S_UNZ>
<D_0036>1</D_0036>
<D_0020>1</D_0020>
</S_UNZ>
</Interchange>
Output sample EDIFACT EDI Message
UNA:+.? '
++A+++1'
BGM+220+MY_ID+9+NA'
DTM+137:201507311500:203'
DTM+2:201508010930:203'
CNT+16:10'
UNT+5+1'
UNZ+1+1'
○ The following example shows the transformation from XML to EDI format of ASC-X12 message.
Input sample ASC-X12 XML Message

<S_ISA>
<D_I01>00</D_I01>
<D_I02> </D_I02>
<D_I03>00</D_I03>
<D_I04> </D_I04>
<D_I05_1>01</D_I05_1>
<D_I06>784849291 </D_I06>
<D_I05_2>01</D_I05_2>
<D_I07>315029991 </D_I07>
<D_I08>051007</D_I08>
<D_I09>0928</D_I09>
<D_I10>/</D_I10>
<D_I11>4010 </D_I11>
<D_I12>000000001</D_I12>
<D_I13>0</D_I13>
<D_I14>P</D_I14>
<D_I15>^</D_I15>
</S_ISA>
<S_GS>
<D_479>PO</D_479>
<D_142>784849291</D_142>
<D_124>315029991</D_124>
<D_373>20051007</D_373>
<D_337>0928</D_337>
<D_28>1</D_28>
<D_455>U</D_455>
<D_480>004010</D_480>
</S_GS>
<M_850>
<S_ST>
<D_143>850</D_143>
<D_329>10001</D_329>
</S_ST>
<S_BEG>
<D_353>00</D_353>
<D_92>NE</D_92>
<D_324>228914</D_324>
<D_373>20051006</D_373>
</S_BEG>
<S_CUR>
<D_98_1>BY</D_98_1>
<D_100_1>EUR</D_100_1>
<D_280>0100</D_280>
</S_CUR>
<G_N1>
<S_N1>
<D_98_1>SF</D_98_1>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_N1>
<S_N1>
<D_98_1>ST</D_98_1>
<D_66>92</D_66>
<D_67>1939</D_67>
</S_N1>
</G_N1>
<G_PO1>
<S_PO1>
<D_350>10000</D_350>
<D_330>17</D_330>
<D_355>EA</D_355>
<D_212>91.8074</D_212>

<D_639>EA</D_639>
<D_235_1>BP</D_235_1>
<D_234_1>2112910003</D_234_1>
<D_235_2>PD</D_235_2>
<D_234_2>Radiator</D_234_2>
</S_PO1>
<S_LIN>
<D_235_1>MF</D_235_1>
<D_234_1>2109308</D_234_1>
</S_LIN>
<G_SCH>
<S_SCH>
<D_380>17</D_380>
<D_355>EA</D_355>
<D_374_1>002</D_374_1>
<D_373_1>20060401</D_373_1>
</S_SCH>
</G_SCH>
</G_PO1>
<G_CTT>
<S_CTT>
<D_354>1</D_354>
</S_CTT>
</G_CTT>
<S_SE>
<D_96>10</D_96>
<D_329>10001</D_329>
</S_SE>
</M_850>
<S_GE>
<D_97>1</D_97>
<D_28>1</D_28>
</S_GE>
<S_IEA>
<D_I16>1</D_I16>
<D_I12>000000001</D_I12>
</S_IEA>
</ns0:Interchange>
Output sample ASC-X12 EDI Message
ISA*00* *00* *01*784849291 *01*315029991

*051007*0928*/*4010 *000000001*0*P*^~
GS*PO*784849291*315029991*20051007*0928*1*U*004010~
ST*850*10001~
BEG*00*NE*228914**20051006~
CUR*BY*EUR*0100~
LIN**MF*2109308~
SCH*17*EA***002*20060401~
CTT*1~
SE*10*10001~
GE*1*1~
IEA*1*000000001~
 Example
UNB+UNOC:3+4006501000002:14+5790000016839:14+100818:0028+0650+++++XXXXX'

Header Name Value
UNB+UNOC:3+4006501000002:14+5790000016839:14+100818:0028+0650+++++XXXXX'
Header Name Value

Header Name Value
810*0001~
Header Name Value

Header Name Value
4.15.7.7 Define Content Modifier
Prerequisites
Context
You use the content modifier step to modify the content of incoming message by providing additional
information in the header or body of the message.
The Content Modifier allows you to modify a message by changing the content of the data containers that are
involved in message processing (message header, message body, or message exchange). Depending on which
container you want to modify, select one of the tabs Message Header, Message Body, or Exchange Property. If
modifying the Message Body, you can enter the data you want to add to the message body in an editor. If
modifying the Message Header or the Exchange Property, you can define how to access the content of the
incoming message (which is then used to change the selected data container). For example, you can select the
Type XPath to specify an XPath expression that addresses a particular element in the incoming message, which
will be used to change the message header.
Note that data written to the message header during a processing step (for example, in a Content Modifier or
Script step) will also be part of the outbound message addressed to a receiver system (whereas properties will
remain within the integration flow and will not be handed over to receivers). Because of this, it is important to

consider the following header size restriction if you are using an HTTP-based receiver adapter: If the message
header exceeds a certain value, the receiver may not be able to accept the inbound call (this applies to all
HTTP-based receiver adapters). The limiting value depends on the characteristics of the receiver system, but
typically ranges between 4 and 16 KB. To overcome this issue, you can use a subsequent Content Modifier step
to delete all headers that are not supposed to be part of the outbound message.
 Note
Procedure
1. If the Content Modifier step is present in the integration flow, select it to edit the properties.
2. If you want to add Content Modifier step to the integration flow, perform the following substeps:
a. In the palette, choose  (Message Transformers)and then choose  (Content Modifier).
b. 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).
4. Choose Add to define a new entry.
5. Specify and define the parameters of the entry as shown below.
Content Modifier Attributes for Message Header or Exchange Property
Action You can specify whether the Content Modifier should cre
ate or delete the header or property defined by the table
row.
You must specify the name of the header or property you

want to delete.
Name Name under which the specified data has to be stored in

the selected header or property data container.

Type Indicates the kind of data you want to use to change the
content of the selected header or property data container.
You can select from the following types:
○ Constant
Allows you to write a constant value to the header or
property data container.
Special characters like {} and [] are not allowed.
○ Header
Allows you to specify the name of a Camel header.
You can then use this header to dynamically define
properties in subsequent steps.
For example, if you specify the header name
CamelSplitIndex, the Camel header of the same
name, which counts the actual number of splits in a
message split scenario, is accessed from the incom
ing message.
In a subsequent step, you use the following expres
sion to refer to this header (for dynamic configura-
tion): ${header.CamelSplitIndex}.
To enter a header, select header in the Type column
and in the Value column choose Select to browse for
predefined headers.
 Note
During outbound communication, headers will be
handed over to all message receivers and inte
gration flow steps, whereas properties will remain
within the integration flow and will not be handed
over to receivers.
 Note
The Select Header dialog shows you a list of
headers that you have specified:
○ In the Header tab page of Content Modifier

flow steps
○ In the Allowed Headers field of the Runtime
Configuration tab page
○ XPath
Allows you to retrieve data from the incoming mes
sage using XML Path Language (XPath). For example,
if you have selected this type, you can specify the fol
lowing Value to point to an element customerName
in the incoming message: /Order/Customer/
CustomerNumber.

To enter XPath, select XPath in the Type column and

in the Value column choose Select to browse for pre
defined xpath listed in wsdl of SOAP adapter for the
sender.
 Note
If the XPath contains a namespace prefix, specify
the association between the namespace and the
prefix in the Runtime Configuration of the integra
tion flow.
For example, let's assume that the following

XPath expression is used:
/ns1:order/ns1:customer/ns1:ID
In this case, you need to specify a namespace

mapping in the runtime configuration as follows:
xmlns:ns1=http://mycompany.com/
order
○ Expression
Allows you to enter a Camel simple expression (see
http://camel.apache.org/simple.html ).
For example, you can use the expression $
{exchangeId} to add the exchange ID (a unique
identifier of the message exchange) to a data con
tainer.
○ Property
Allows you to specify an exchange property.
To enter a property, select property in the Type col
umn and define a value based on the selected value
type.
 Note
During outbound communication, headers will be
handed over to all message receivers and inte
gration flow steps, whereas properties will remain
within the integration flow and will not be handed
over to receivers.
○ External Parameter
This option is not available in WebUI but for compati
bility reasons we still support content using this field.
Integration developer can use externalization and ex
ternalize any type of headers or exchange properties.
Please refer to Externalize Parameters of an Integra
tion Flow [page 482] for more details.

○ Local Variable
Allows you to define a local variable and write its
value at runtime to the header or property data con
tainer. The value can then be evaluated in subsequent
steps of the integration flow.
A local variable can be used in the context of the inte
gration flow.
○ Number Range
Allows you to retrieve the value (a unique identifier) of
a predefined number range.
 Example
○ If you want to increase the value in the mes
sage header define the name of the Number
Range.
○ If you do not want to increase the value in
the message header, then define the value
as <name of the Number Range>:$
{header.headername} or <name of
the Number Range>:<correlation
ID>.
 Note
Make sure you use the same correlation ID for all
future processing.
For more information on adding number range, see .

○ Global Variable
Allows you to define a global variable and to write its
value at runtime to the header or property data con
tainer.
A local variable can be used across different integra
tion flows of the same tenant.

DataType Valid Java data type
The Data Type column is used only for the XPath type. 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 http://
camel.apache.org/simple.htm .
If the XPath contains a namespace prefix, specify the as

sociation 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.
Value Value of the property
Default If you have selected Local Variable or Global Variable as

Type, the value specified as Default will be assigned to the
(Only relevant if you have selected Local Variable or Global
header value if the variable is not found at runtime.
Variable as Type)
6. Go to the Message Body tab, and define the fields as shown below.
Type The default value is Expression. If the payload contains ex

pressions within it, then set the type as Expression; if the
payload is huge and it has no expressions within it, then it
is recommended to use the type Constant.
Body Enter the content expected in the outgoing message.
 Remember
Ensure that you set a placeholder for the existing
header information.
 Note
○ If you add a Content Modifier step without a header, body, and property, you cannot trace the
element.
○ The Data Type column is mainly used for the XPath type. The data type can belong to any Java
class. An example of a data type for an XPath is java.lang.String.

 Example
Suppose the incoming message has the following information:
<order>
<book>
<Count>5<Count>
</book>
</order>
In the Body tab of the Content Modifierstep, you specify the content expected in the outgoing message.
Keep a placeholder for the header information to modify the content as shown below:
<invoice>
${in.body}
<deliverydate>${header.date}</delivery>
</invoice>
In the Header tab of the Content Modifier step, enter the following:
Name Type Value
<invoice>
<order>
<book>
<Count>5<Count>
</book>
</order>
</invoice>
Related Information

Content Modifier Basics [page 772]
4.15.7.7.1 Content Modifier Basics
An integration flow is a BPMN (Business Process Model and Notation)-like model that allows you to specify
how a message is to be processed on a tenant.

To interpret an integration flow model at runtime, it is transformed into an XML structure that is compatible
with Apache Camel (http://camel.apache.org ), an Open Source integration framework for Java that
supports the mediation and routing of messages of any format.
The only prerequisite for a message that is to be processed by the Camel framework is that it comprises the
following elements:
● Headers
Contain information related to the message, for example, information for addressing the message sender.
● Attachments
Contain optional data that is to be attached to the message.
● Body
Contains the payload (usually with the business-related data) to be transferred in the message.
seen as an abstraction of a message exchange process as it is executed by the Camel framework. An Exchange
is identified uniquely by an Exchange ID. In the Properties area of the Exchange, additional data can be stored
temporarily during message processing. This data is available for the runtime during the whole duration of the
message exchange.
You can use the Content Modifier step to modify a message by adding additional data to it.
More precisely, this step type allows you to modify the content of the following three data containers during
message processing:
● Message Header
You can add headers to the message, and edit and delete headers.
● Message Body
You can modify the message body part.
● Exchange Property
You can write data to the message exchange, and edit and delete the properties.
For example, you can retrieve the value of a particular element of the payload of an inbound message and write
this value to the header of the message (to make it available for subsequent processing steps).
You need to specify additional parameters in the Content Modifier step to tell the integration runtime how
exactly to access the data from the incoming message (which is to be written to one of the three data
containers above).
Here's a simple example to show how this works: Let's say you want to write the value of the element
CustomerNumber from an inbound XML message to the message header, to make it available for subsequent
process steps.
In this case, you could configure the Content Modifier as follows:
On the Message Header tab of the Content Modifier, add a new entry. Specify XPath as the Type (because you
want to address the CustomerNumber element in an incoming XML message). For Value, enter the exact XPath
expression that is to be used to address this element (for example, /Order/Customer/CustomerNumber). In an
additional field, you now need to specify the data format expected for the content of the CustomerNumber
element. To express that this is a String element, you need to specify a valid Java data type, which is
java.lang.string in this case. For Name, enter the desired name of the message header (which should
contain the CustomerNumber value), for example, CustomerNo.

The following screenshot shows our example configuration:
Example
The following example shows how to modify both the header and body data container of a message using the
Suppose that the incoming message has the following information:
<order>
<book>
<Count>5</Count>
</book>
</order>
On the Header tab of the Content Modifier, enter the following to write constant values to the message header:
Name Type Value
On the Body tab, keep placeholders for the header information specified in the first Content Modifier step ($
{header.vendor} and ${header.date}) to modify the content as shown below. Additionally, use a
placeholder ${in.body} for the incoming message.
<invoice>
${in.body}
<deliverydate>${header.delivery date}</delivery>
</invoice>
<invoice>
<order>
<book>
<Count>5</Count>
</book>
</order>
</invoice>

4.15.7.7.2 Avoiding Encoding Issues
The integration runtime supports the following two kinds of (internal) data representations: binary data and
string (sequence of characters). Conversions between these representations may cause issues that can result
in erroneous message processing.
This topic lists the main measures to help you avoid any such issues.
The Content Modifier step provides the following options for configuring how data is to be encoded (based on
the CamelCharsetName element):
● Configuring the Exchange Property

● Configuring the Message Header
General Recommendations
As far as applicable for your scenario, try to implement the following measures:
Recommendations
Recommendation Required Tasks Conditions and Challenges
Use UTF-8 character encoding only You do not have to set any Make sure that all mappings use UTF-8
CamelCharsetName property or for output encoding. If you do not de
Try to use UTF-8 encoding for all binary
header (as UTF-8 is the default), or any fine an output encoding, UTF-8 is used
character representations throughout
XML declaration (as UTF-8 is also the as the default.
the scenario.
default for XML).
The challenge with this solution is that
it requires all your communication part
ners to send and receive data in UTF-8
character encoding (which, although
not uncommon, is unfortunately not al
ways the case).
Use a fixed character encoding Perform the following steps: The challenge with this solution is that if
throughout the whole integration flow you have more than one communica
● Set the CamelCharsetName ex
tion partner, it is rather unlikely that
If your communication partners require change property to your character
they all agree on a character encoding
a character encoding for communica set.
different from UTF-8.
tion other than UTF-8 (for example, ● Make sure that all your mappings
ISO-8859-15), and this character en have the required output. Make
coding is the same for all communica sure that you do not remove the
tion partners, you can set up your inte XML declaration for binary XML
gration flow to use that character en representation as this could cause
coding. the parsing of binary XML content
to fail.

Recommendation Required Tasks Conditions and Challenges
Avoid binary-to-string conversions If you are working with XML data and If using this solution, the integration
you are communicating with different flow developer must not modify a mes
communication partners using different sage body that contains an XML docu
character encodings, one way to avoid ment with a content modifier or a
character encoding issues is to avoid string-based script.
the serialized string representation of
The filter and XSLT mapping steps both
XML documents altogether.
have the option to provide string out
In this case, the content of the put. This option should only be used if
CamelCharsetName is irrelevant as the result is a non-XML string, not an
no string-to-binary conversion occurs XML document or fragment.
(only XML parsing and marshaling).
The integration developer must there
fore exercise caution and due care if ap
plying these measures.
Related Information
Character Encodings: Background Information [page 776]
4.15.7.7.2.1 Character Encodings: Background Information
When configuring integration flows, you are usually dealing with the following kinds of data representations:
Binary Data
There is always some loss of data when binary data is converted into strings. You should therefore avoid
converting pure binary data to strings.
Text Data
Text data can be represented in binary or string form. In order to convert string representation to binary
representation and the other way round,, the desired (or existing) binary encoding needs to be known.
The integration framework uses the following scheme to determine the type of character encoding:
1. If the header CamelCharsetName is set, the value of this header is used as the character encoding.
2. If the exchange property CamelCharsetName is set, the value of this exchange property is used as the
character encoding.

3. If neither the header nor the exchange property are defined, UTF-8 is used as the character encoding.
There is no universal way to determine the correct encoding for the data. However, for some communication
protocols (such as mail or HTTP) this information may be transferred via the protocol header.
The integration developer needs to make sure that the character encoding that is defined by the header or
exchange property and the binary content encoding are in sync. Otherwise, subtle, hard-to-solve issues can
occur. These issues often aren't revealed by testing, as they usually only occur with non-ASCII characters.
XML Data Conversions
There are three type of representation for XML data:
● Serialized binary representation of the XML document

● Serialized string representation of the XML document
● Parsed (binary) representation of the XML document
This representation is used for operations such as XPath or XSLT processing.
XML documents usually contain information about the character encoding in serialized form within the XML
declaration (at the beginning of the XML document).
However, note that this XML declaration is irrelevant if string representation is used for the document. If the
XML document is parsed from or marshaled (serialized) to binary representation, the charset definition (and
the byte order marker (BOM)) are used to determine the content encoding.
If no encoding is defined, UTF-8 is assumed (unless a BOM is present when it is UTF-16).
 Caution
The conversion between the parsed and the serialized form works fine without any configuration and has a
mechanism to determine and use the correct character set for the conversion. However, issues can occur
when converting directly between the two serialized forms (binary and string). This conversion is not XML-
specific and uses the scheme for text data. This conversion will actually damage the content of the
document if the character encoding used in Camel does not match the character encoding used in the XML
document.
The following figure illustrates this.

If a conversion between binary XML and parsed XML takes place, the encoding that is defined in the XML
declaration is used as the character encoding in the XML document. If it is converted to a string first, the
encoding defined in the CamelCharsetName header or property is used. If these values do not match,
conversion via a string might break the document.
Conversions between binary and string (highlighted in the figure) generally require attention from the
integration developer because there is no generic way to determine the character encoding of the binary text
or XML content (and the integration developer must be sure to set the correct value there).
XSLT sheets can change the content encoding of the XML document if they convert XML to XML. In this case,
the output encoding will either be defined by the XSLT or it will be UTF-8, even if the input document has a
different encoding. If direct binary-to-string conversion takes place before and after the XSLT, the integration
developer has to make sure that the CamelCharsetName property or header is defined appropriately.
4.15.7.8 Define an Encoder
You use this task to encode messages using an encoding scheme to secure any sensitive message content
during transfer over the network.
Procedure
2. From the palette, choose Transformation Encoder .

3. Select one of the following encoding schemes:
○ Base64 Encode
Encodes the message content using base64.
○ GZIP Compress: Compresses the message content using GNU zip (GZIP).
○ ZIP Compress: Compresses the message content using zip (only zip archives with a single entry
supported).
○ MIME Multipart Encode: Transforms the message content into a MIME multipart message.
If you want to send a message with attachments, but the protocol (for example, HTTP or SFTP) does
not support attachments, you can send the message as a MIME multipart instead.
 Example
A message with the header Content-Type "text/plain" is sent to a MIME multipart encoder. The add
multipart headers inline functionality is activated.
 Sample Code
from("...").marshal().mimeMultipart("related", true, true, "(included|

x-.*)", true);

The resulting message body will be:
 Sample Code
Message Body
Message-ID: <...>
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_0_1134128170.1447659361365"
------=_Part_0_1134128170.1447659361365
Content-Type: text/plain
Content-Transfer-Encoding: 8bit
Body text
------=_Part_0_1134128170.1447659361365
Content-Type: application/binary
Content-Transfer-Encoding: binary
Content-Disposition: attachment; filename="Attachment File Name"
[binary content]
------=_Part_0_1134128170.1447659361365
Consider the input XML payload structure to the encoder:
<message>
Input for encoder
</message>
If you select Base64 Encode, the output message would look like this:
4.15.7.8.1 MIME Multipart Messages
A Multipurpose Internet Mail Extensions (MIME) multipart message allows you to combine different kinds of
content in one message (for example, plain text and attachments).
To mention a use case, if you want to send a message with attachments, but the protocol (for example, HTTP or
SFTP) does not support attachments, you can send the message as a MIME multipart instead.
With a multipart subtype you can specify how the different content types are combined as MIME multipart
message. The property Multipart Subtype in the Encoder step allows you to specify the Content-Type property
of the MIME message. For more information on the different options for Multipart Subtype, refer to the general
definition of the Multipart Content-Type.
An input message for the MIME Multipart Encoder step doesn’t have to be composed in a specific way.
An inbound message for a MIME Multipart Decoder step has to be a MIME multipart message. Hereby, the
multipart headers can either be stored as Camel headers or as part of the message body.

Usage of Dynamic Headers
You have the option to dynamically (based on the content of the processed message) add custom headers to a
MIME multipart message. Do enable this option, you have to activate Add Multipart Header Inline. In that case,
the option Include Headers is displayed.
You can now enter regular expressions for the headers which are to be added dynamically. With such regular
expressions (regex), you can define placeholders for the custom headers:
 Tip
Example:
When you enter for Include Headers the string (x-.*|myAdditionalHeader), all headers that start with
x- and the header myAdditionalHeader are added dynamically.
MIME Multipart Encoder
The following table summarizes how the Encoder step transforms the message depending on whether you
select or deselect the option Add Multipart Header Inline.
Encoder: Add Multipart Header Inline Option
Add Multipart Header Inline Description
Selected The Encoder transforms the inbound message into a new message where the message
body (of the resulting message) is a MIME multipart message with headers.
Body and attachments (if available) of the inbound message will be added as separate
parts of the multipart message. The attachments are removed from the resulting message.
Note that the message will also always be transformed into a MIME multipart message, re
gardless whether it contains attachments or not.
● The inbound message has attachments: Encoder transforms message body and at
tachments of the inbound message into a MIME multipart message. The headers of
the multipart message will be added as Camel headers. The message body will be re
placed by the rest of the message.
● The inbound message has no attachments: Encoder does not change the inbound
message.
The following figures illustrate how the property Add Multipart Header Inline influences the processing of the
message.
Add Multipart Header Inline selected

Add Multipart Header Inline deselected
MIME Multipart Decoder
The following table summarizes how the Decoder step transforms the message depending on whether you
select or deselect the option Multipart Headers Inline.
Decoder: Multipart Headers Inline Option
Multipart Headers Inline Description
Selected The Decoder transforms the first part of the multipart message into the message body of
the resulting message and the following parts (if available) will be transformed into attach
ments of the resulting message.
In case the inbound message is, other than expected, no MIME multipart message with in
line headers, the complete message body is interpreted as a preamble of the MIME multi
part, and the resulting message is empty.
● The inbound message either doesn’t contain the multipart header as Camel header or
the Content-Type is no multipart, the Decoder step doesn’t change the inbound mes
sage.
● In all other cases, the header of the inbound message will be used as header of the
multipart message (and deleted). The message body of the resulting message will be
built up out of those parts which are contained in the message body (and, if available,
out of the attachments).
4.15.7.9 Define a Decoder
You use this task to decode the message received over the network to retrieve original data.
Procedure
2. From the palette, choose Transformation Decoder .

3. Select one of the following decoding schemes:
○ Base64 Decode: Decodes base64-encoded message content.

○ GZIP Decompress: Decompresses the message content using GNU zip (GZIP).
○ ZIP Decompress: Decompresses the message content using zip.
○ MIME Multipart Decode: Transforms a MIME multipart message into a message with attachments.
If the multipart headers are part of the message body, select Multipart Headers Inline.
 Note
If this option is not selected and the content type camel-header is not set to a multipart type, no
decoding takes place.
If this option is selected and the body of the message is not a MIME multipart (with MIME headers
in the body), the message is handled as a MIME comment and the body is empty afterwards.
 Example
Let us suppose that an input message to the decoder is a message encoded in Base64 that looks like this:
The output message of the decoder would be as follows:
<message>
Input for encoder
</message>
4.15.7.10 Define Filter
Prerequisites
● You have logged on to SAP Cloud Platform Integration web application.

● You have copied or imported the integration package to your workspace.
● You are editing the integration flow.
Context
You use Filter to extract information from an incoming message. In other words, you filter out parts of the
message that you do not want and extract only the data that you want.
Here's an example for a message:
<Message>
<orders>
<order>

<count>100</count>
</order>
<order>
<count>10</count>
</order>
</orders>
</Message>
Let us assume that you are interested only in the count. You use the Filter and specify an Xpath /Message/
orders/order/count/text().
The output of the content filter would be data in count fields of the message. The output in this example with
the specified Xpath is 10010
.
Procedure
1. In the palette, choose Filter .

2. Place Filter in the integration process and define the message path.
3. Select Filter and provide values in fields based on description in table.
Field Description
Name Specify a name for filter step. By default, the value is Filter.
XPath Expression Specify Xpath to the message node that contains informa
tion to be extracted
4. In Value Type dropdown list, select value type based on description in table.
Value Type Description
String The output of filter is of type string
Integer The output of filter is of type integer
Boolean The output of filter is of type boolean
Node The output of filter is of type node
Nodelist The output of filter is a collection of nodes

4.15.7.11 Define Message Digest
This integration flow step is used to calculate a digest of the payload or parts of it and store the result in a
message header.
Context
In detail, the Message Digest integration flow step transforms a message into a canonical XML document. From
this document, a digest (hash value) is calculated and written to the message header.
 Note
Canonicalization transforms an XML document into a form (the canonic form) that makes it possible to
compare it with other XML documents. With the Message Digest integration flow step, you can apply
canonicalization to a message (or to parts of a message), calculate a digest out of the transformed
message, and add the digest to the message header.
In simple terms, canonicalization skips non-significant elements from an XML document. To give some
examples, the following changes are applied during the canonicalization of an XML document: Unification
of quotation marks and blanks, or encoding of empty elements as start/end pairs.
The original message remains unchanged.
You also have the option to define a filter to apply canonicalization only to a sub-set of the message.
Procedure

2. Select the Message Digest step and add it to the integration flow.
3. Specify the following attributes for the step.
Option Description
Filter (XPath) If you only want to transform part of the message, enter an XPath expression to specify the part (op
tional attribute).
You can also define a prefix namespace mapping.
Canonicaliza You can choose between the following methods.

tion Method ○ Canonical XML Version 1.0
More information: http://www.w3.org/TR/2001/REC-xml-c14n-20010315
○ Canonical XML with Comments Version 1.0
More information: http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments
○ Exclusive XML Canonicalization Version 1.0
More information: http://www.w3.org/2001/10/xml-exc-c14n
○ Exclusive XML Canonicalization with Comments Version 1.0

Option Description
More information: http://www.w3.org/2001/10/xml-exc-c14n#WithComments
This is an optional attribute.
Digest Algo Select the hash algorithm to be used to calculate the digest.
rithm
You can choose between the following hash algorithms:
○ SHA-1
○ SHA-256
○ SHA-384
○ SHA-512
○ MD5
Target Enter the name of the target header element which is to contain the hash value (digest).
Header Name
4.15.7.12 Define Script
Context
You use this task to execute custom Java script or Groovy script for message processing. SAP Cloud Platform
Integration provides a Java API to support this use case.
 Note
Modifier or Script step) will also be part of the outbound message addressed to a receiver system. Because
of this, it is important to consider the following restriction regarding the header size if you use an HTTP-
based receiver adapter: If the message header exceeds 8 KB, it might lead to situations that the receiver
cannot accept the inbound call (relevant for all HTTP-based receiver adapters).
 Note
The Java standard libraries of Java 7 can be used.
Cloud Integration supports the XML Document Object Model (DOM) to process XML documents.
 Note
Any application that parses XML data is prone to the risk of XML External Entity (XXE) Processing attacks.
More information: https://www.owasp.org/index.php/XML_External_Entity_%28XXE%29_Processing

To overcome this issue, you should take the following measures to protect integration flows that contain
Script steps (using Groovy script or Java Script) against XXE Processing attacks:
● Do not use XML parsing (for example, DocumentBuilderFactory) at all or

● Switch off the processing of external entities as described at https://www.owasp.org/index.php/
XML_External_Entity_%28XXE%29_Prevention_Cheat_Sheet#Java .
Procedure
1. In the palette, choose Message Transformers Script .

2. Choose Groovyscript or Javascript.
3. In the Script Editor, specify the script and modify the script function as per the scenario.
4. Add or modify Header, Body, and Property by using the functions below on the "message" object.
1. You can use the following for Header:
○ public java.util.Map<java.lang.String,java.lang.Object> getHeaders()
○ public void setHeaders(java.util.Map<java.lang.String,java.lang.Object> exchangeHeaders)
○ public void setHeader(java.lang.String name, java.lang.Object value)
2. You can use the following for Body:
○ public java.lang.Object getBody()
○ public void setBody(java.lang.Object exchangeBody)
○ public java.lang.Object getBody(java.lang.Class fullyQualifiedClassName)
 Note
Cloud Integration framework supports conversion of payload into the following formats:
○ String
○ InputStream
○ byte[]
To convert the payload into String or InputStream use the following fullyQualifiedClassName:
○ java.lang.String
○ java.io.InputStream
To convert the payload into byte[] use the following:
○ For groovy script:
def body = message.getBody((byte[]).class);
○ For java script:
var body =
message.getBody( java.lang.reflect.Array.newInstance(java.lang.Byte.T
YPE,0).getClass());
To convert payload into String (in JavaScript):
var body = message.getBody( new java.lang.String().getClass() );

 Note
Depending on the actual Camel message content, the getBody(<type>) can still use wrong
encoding.
Consider the following to avoid encoding issues:

○ Avoiding Encoding Issues [page 775]
○ Character Encodings: Background Information [page 776]

3. You can use the following for Property:
○ public java.util.Map<java.lang.String,java.lang.Object> getProperties()
○ public void setProperties(java.util.Map<java.lang.String,java.lang.Object> exchangeProperties)
○ public void setProperty(java.lang.String name, java.lang.Object value)
4. You can use the following for MPL Attachment:
○ public java.util.Map<java.lang.String,javax.activation.DataHandler> getAttachments()
○ public void setAttachments(Map<java.lang.String, javax.activation.DataHandler>)
 Note
○ You should not add or modify a property or header name starting with sap.
○ If no Script Function is specified in the script flow step, processData function is called by default.
 Caution
When converting parts of the message object like the body or even headers or properties into a string
(as string) or into a byte array (as byte[]) please consider copies of the existing data is created which
requires extra memory. This resource consumption may even exceed the memory size of the original
object if string conversion is executed.
Example:
def body = message.getBody(java.lang.String) as String;
Depending on the size of the object byte[] or string conversion can endanger worker node of OOM
failure. Please consciously decide which part of the message object should be converted.
5. Click on OK.
6. Specify the script step name in Name.
7. Specify a custom function that will take the message object as the argument in Script Function.
In the script you require Script Function, which will be executed at runtime.
 Note
○ In the properties section, you can also choose Select to browse another script.
○ You can add external jar(s) using Resource view. You can then invoke functions from these external
jar(s) in the script.
 Example
If you want to access the security artifacts such as secure store and keystore that are delpoyed using the
deployment wizard, refer the table below.

Secure Store Import packages
import
com.sap.it.api.securestore.exception.SecureStoreException;
 Sample Code
def service =
ITApiFactory.getApi(SecureStoreService.class, null);

{
//Get UserCredential containing user credential
details deployed on the node with the given alias.
def credential =
service.getUserCredential(aliasname);
……………………………
}
Keystore Import packages
import com.sap.it.api.keystore.KeystoreService;
import com.sap.it.api.keystore.exception.KeystoreException;
 Sample Code
def service = ITApiFactory.getApi(KeystoreService.class,

null);

{
//Get all trust manager implementation instances
using the service for the default trust store
def trustmanager = service.getTrustManagers();
//Get all KeyManager implementation instances using
the service
def keymanagers = service.getKeyManagers(alias);

……………………………
}

Value Mapping Import Packages
import com.sap.it.spi.ITApiHandler;
import com.sap.it.api.mapping.ValueMappingApi;
def service = ITApiFactory.getApi(ValueMappingApi.class,

null);

{
def mappedValue = service.getMappedValue("SuccessFactors",
"locale", "de_DE", "SAPHCM", "language");
//
(SrcAgencey,SrcSchema,SrcValue,TargetAgency,TargetSchema)
messageLog.setStringProperty("Information","The transformed
locale value is : " + mappedValue);
}
}
catch(Exception e)
{
messageLog.setStringProperty("Exception",e.toString())
return null;
}
return message;
}
Number Ranges Import packages
import com.sap.it.api.nrc.NumberRangeConfigurationService;
import
com.sap.it.api.nrc.exception.NumberRangeConfigException;
 Sample Code
def service =
ITApiFactory.getApi(NumberRangeConfigurationService.class
, null);

{
//Get next value from number range configured in web
tooling.
def nextValue =
service.getNextValuefromNumberRange("new", null);
}

Next Steps
There are the following additional Java interfaces for the message processing log (MPL) which you can address
with the script step (either in Groovy Script or JavaScript):
● MessageLogFactory
Provides access to the message processing log.
● MessageLog
Supports writing properties and adding attachments to the message processing log.
The interface MessageLogFactory can be used through the variable messageLogFactory in order to
retrieve an instance of MessageLog.
You can use the following methods in an instance of MessageLog in order to set a property of a given type in
the message processing log:
● void setStringProperty(String name, String value)

● void setIntegerProperty(String name, Integer value)
● void setLongProperty(String name, Long value)
● void setBooleanProperty(String name, Boolean value)
● void setFloatProperty(String name, Float value)
● void setDoubleProperty(String name, Double value)
● void setDateProperty(String name, Date value)
You can use the following method in an instance of MessageLog in order to add string to an attachment using
message processing log:
● void addAttachmentAsString(String name, String text, String mediaType)
You can use the following method in an instance of MessageLog in order to add, set, get, remove headers to/
from an attachment using message processing log:
● void addAttachmentHeader(String headerName, String headerValue,AttachmentWrapper

attachment)
● void setAttachmentHeader(String headerName, String headerValue,AttachmentWrapper
attachment)
● getAttachmentHeader(String headerName,AttachmentWrapper attachment)
● void removeAttachmentHeader(String headerName, AttachmentWrapper attachment);
You can use the following method in an instance of MessageLog in order to add, set attachment objects as a
map using message processing log:
● Map<String, AttachmentWrapper> getAttachmentWrapperObjects()

● void setAttachmentWrapperObjects(Map<String, AttachmentWrapper>
attachmentObjects)
● void addAttachmentObject(String id, AttachmentWrapper content)
Use method addAttachmentAsString to add a longer, structured document to the message processing log
(MPL). Use method setStringProperty only for short strings (containing one or a few words).
If the value "null" is specified for the parameter mediaType, then the value "text/plain" is assumed as
media type.”

As an example, the following code lines allow you to set a string property:
Groovy:
def messageLog = messageLogFactory.getMessageLog(message)

JavaScript:
var messageLog = messageLogFactory.getMessageLog(message)

 Caution
Note that the properties provided by the script step are displayed in alphabetical order in the resulting
message processing log (MPL). That means that the sequence of properties in the MPL does not
necessarily reflect the sequence applied in the script.
The method addCustomHeaderProperty allows you to to add user-defined attributes (name/value pairs) to
the message processing log. These attributes are then persisted and can be used for message search.
4.15.7.12.1 Setting SOAP Headers
You can use Groovy programming language (Groovy script) to set SOAP headers.
The following example shows a SOAP message with a SOAP header.
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<AuthHeader soap:actor="actor_test" soap:mustUnderstand="1" xmlns="http://
www.Test.com/">
<ClientId>username</ClientId>mustUnderstand
<Password>password</Password>
</AuthHeader>
</soap:Header>
<soap:Body>
<test:TestMessage xmlns:test="http://hci.sap.com/ifl/test">
<MessageContent>customer1</MessageContent>
</test:TestMessage>
</soap:Body>
</soap:Envelope>
To set such a SOAP header, use the following script.
import java.util.ArrayList;
import java.util.List;
import javax.xml.namespace.QName;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import org.apache.cxf.binding.soap.SoapHeader;
import org.w3c.dom.Document;
import org.w3c.dom.Element;

// First fetch user name and password which must be entered into the SOAP
header from the secure store service.
// This is not necessary if your SOAP header does not require data from the
secure store service.
def service = ITApiFactory.getApi(SecureStoreService.class, null);
def credential = service.getUserCredential("partner1_credential_alias");
if (credential == null){
throw new IllegalStateException("No credential found for alias
'partner1_credential_alias'");
}
String userName = credential.getUsername();
String password = new String(credential.getPassword());
// Create Soap Header as DOM Element; the attributes "actor" and
"mustUnderstand" must not be added;
// these attributes can be added later see below.
// The following lines create the DOM Element.
//<AuthHeader xmlns=http://www.Test.com/><ClientId>"+userName+"</
ClientId><Password>"+password+"</Password></AuthHeader>"
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
dbf.setNamespaceAware(true);
dbf.setIgnoringElementContentWhitespace(true);
dbf.setValidating(false);
DocumentBuilder db = dbf.newDocumentBuilder();
Document doc = db.newDocument();
Element authHeader = doc.createElementNS("http://www.Test.com/",
"AuthHeader");
doc.appendChild(authHeader);
Element clientId = doc.createElementNS("http://www.Test.com/", "ClientId");
clientId.setTextContent(userName);
authHeader.appendChild(clientId);
Element passwordEl = doc.createElementNS("http://www.Test.com/", "Password");
passwordEl.setTextContent(password);
authHeader.appendChild(passwordEl);
// Create SOAP header instance.
SoapHeader header = new SoapHeader(new QName(authHeader.getNamespaceURI(),
authHeader.getLocalName()), authHeader);
header.setActor("actor_test");
header.setMustUnderstand(true);
// Add the SOAP header to the header list and set the list to the message
header "org.apache.cxf.headers.Header.list".
List headersList = new ArrayList<SoapHeader>();
headersList.add(header);
message.setHeader("org.apache.cxf.headers.Header.list", headersList);
return message;
}
4.15.7.12.2 Script Example for Exception Handling in HTTP

Receiver
Script example to identify any exceptions that arise when sending messages using the HTTP receiver.
You can use Groovy programming language (Groovy script) to identify any exceptions that arise when sending
messages using the HTTP receiver.
The Groovy script provides examples how to do following:
● Save the value of http response as a message attachment
● Copy the value of the http error to a ‘http.ResponseBody’ property

● Copy the value of the http error to the message body
● Copy http error text and error code to properties
1. Copy the following script to the script flow step.
 Sample Code
// get a map of iflow properties

def map = message.getProperties();
// get an exception java class instance

def ex = map.get("CamelExceptionCaught");
if (ex!=null) {
// an http adapter throws an instance of

org.apache.camel.component.ahc.AhcOperationFailedException
if
(ex.getClass().getCanonicalName().equals("org.apache.camel.component.ahc.Ah
cOperationFailedException")) {
// save the http error

response as a message attachment
def messageLog =
messageLogFactory.getMessageLog(message);
messageLog.addAttachmentAsString("http.ResponseBody",
ex.getResponseBody(), "text/plain");
response to an iflow's property
message.setProperty("http.ResponseBody",ex.getResponseBody());
response to the message body
message.setBody(ex.getResponseBody());
error code (i.e. 500) to a property
message.setProperty("http.StatusCode",ex.getStatusCode());
error text (i.e. "Internal Server Error") to a property
message.setProperty("http.StatusText",ex.getStatusText());
}
}
return message;
}
2. Call the script flow step in an exception subprocess.

4.15.7.12.3 Accessing Partner Directory Content with the
Script Flow Step
You can use the Script step to access Partner Directory content.
The following code snippets show the interface. An example how to access the Partner Directory is given below.
/**
* Looks-up the partner ID for the triple scheme, agency, alternative
* partner ID. The partner ID is needed for the other methods in this class.
*
* @param agency
* issuing agency of the external partner ID
* @param scheme
* identification scheme
* @param alternativePartnerId
* alternative partner ID
* @return partner ID, or <code>null</code>, if no partner ID exists for the
* specified triple
* @throws PartnerDirectoryException
* if an error occurs
* @throws IllegalArgumentException
* if an input argument is <code>null</code> or empty
*
*/
String getPartnerId(String agency, String scheme, String
alternativePartnerId) throws PartnerDirectoryException;
/**
* Looks-up the alternative partner ID for the triple scheme, agency,
* partner ID.
*
* @param agency
* issuing agency of the external partner ID
* @param scheme
* identification scheme
* @param partnerId
* partner ID
* @return alternative partner ID, or <code>null</code>, if no alternative
* partner ID exists for the specified triple
* if an input argument is <code>null</code> or empty
*
*/
String getAlternativePartnerId(String agency, String scheme, String
partnerId) throws PartnerDirectoryException;
/**
* Returns the partner specific value of a partner directory parameter.
*
* @param parameterId
* ID of the Partner Directory parameter
* @param partnerId
* ID of the partner
* @param type
* the type of the parameter, supported types are
* <code>java.lang.String.class</code> for String parameters,
* <code>com.sap.it.api.pd.BinaryData.class</code> for Binary
* Data parameters
* @return value of the parameter, or <code>null</code> if the parameter

* does not exist in the Partner Directory
* if an input argument is <code>null</code> or the given
* <code>type</code> is not a supported type or if
* <tt>parametrId</tt> or <tt>partnerId</tt> is empty
*
*/
<T> T getParameter(String parameterId, String partnerId, Class<T> type)
throws PartnerDirectoryException;
/**
* Returns a X.509 certificate for a binary parameter with content type
* "crt".
*
* @param parameterId
* ID of the Partner Directory parameter
* @param partnerId
* ID of the partner
* @return java.security.cert.X509Certififate instance, or <code>null</code>
* if the parameter does not exist in the Partner Directory
* if the parameter is not a certificate parameter, or another
* error occurs
* if an input argument is <code>null</code> or the given
* <code>type</code> is not a supported type or if
* <tt>parametrId</tt> or <tt>partnerId</tt> is empty
*/
Certificate getCertificateParameter(String parameterId, String partnerId)
throws PartnerDirectoryException;
/**
* Returns the Partner ID to which a authorized user was assigned to. Or
null if the user does not exist.
*
* @param authorizedUser
* authorized User
* if the input argument is <code>null</code> or empty
*/
String getPartnerIdOfAuthorizedUser(String authorizedUser) throws
PartnerDirectoryException;
/**
* Returns the authorized users of a partner.
*
* The authorized user names will be returned with lower case characters
(Locale.English).
*
* @param partnerId
* @return list of users or empty list if no authorized user exists
* if the input argument is <code>null</code> or empty
*/
List<String> getAuthorizedUsers(String partnerId) throws
PartnerDirectoryException;
/**

* Container to store store binary data (as byte array) and the associated
* content type for Partner Directory Binary Parameters.
*/
public class BinaryData {
private final byte[] data;
private final String contentType;
public BinaryData(byte[] data, String contentType) {

if (data == null) {
throw new IllegalArgumentException("Parameter 'data' is null");
}
if (contentType == null) {
throw new IllegalArgumentException("Parameter 'contentType' is
null");
}
this.data = data;
this.contentType = contentType;
}
/** Returns the binary data. Cannot be <code>null</code>. */

public byte[] getData() {
return data;
}
/** Returns the content type. Cannot be <code>null</code>. */

public String getContentType() {
return contentType;
}
Example
This example shows how to perform partner authentication.
It checks that the partner ID associated with the logged-in user is consistent with the partner ID which can be
derived from the message content.
It is assumed that the alternative partner ID of the message has been set before into the property
AlternativePartnerID.
import com.sap.it.api.pd.PartnerDirectoryService;
import com.sap.it.api.pd.BinaryData;
import java.util.Map;
import java.security.cert.X509Certificate;
import javax.security.auth.Subject;
import java.security.Principal;
import java.util.Set;
// get the logged-in user from header 'SapAuthenticatedUserName'

map = message.getHeaders();
String user = map.get("SapAuthenticatedUserName");
if (user == null || user.isEmpty()){
throw new IllegalStateException("Logged-in user not available in header
SapAuthenticatedUserName.");
}
// look-up Partner Directory Service

def service = ITApiFactory.getApi(PartnerDirectoryService.class, null);
if (service == null){
throw new IllegalStateException("Partner Directory Service not found");

}
// get partner ID from user

String pid = service.getPartnerIdOfAuthorizedUser(user);
if (pid == null){
throw new IllegalStateException("No partner ID found for user "+user);
}
// alternative partner ID from property which has been filled before from
the message
map = message.getProperties();
def apid = map.get("AlternativePartnerID");
if (apid == null || apid.isEmpty()){
throw new IllegalStateException("Property AlternativePartnerID does
not contain a value");
}
// look-up parter ID for the alternative partner ID

def partnerIdForAlternativePid = service.getPartnerId("companies",
"company_scheme",apid);
if (partnerIdForAlternativePid == null ||
partnerIdForAlternativePid.isEmpty()){
throw new IllegalStateException("No partner ID found for alternative
partner ID "+apid);
}
// compare the two partner IDs

if (!partnerIdForAlternativePid.equals(pid)){
throw new IllegalStateException("User "+user+" is not authorized to send
messages with ID "+apid);
}
// set pid as property

message.setProperty("PartnerID",pid);
return message;
}
4.15.8 Define Security Elements
Security elements in the integration flow enable you to encrypt, decrypt, sign and verify messages. This
ensures that the message is secure and can only be accessed by the intended recipient. Encryption also
prevents non-repudiation of messages during message exchange.

4.15.8.1 Sign the Message Content with Simple Signer
Simple Signer makes it easy to sign messages to ensure authenticity and data integrity when sending a
message to participants on the cloud.
Context
You work with the Simple Signer to make the identity of the sender known to the receiver or receivers and thus
ensure the authenticity of the messages. This task guarantees the identity of the sender by signing the
messages with a private key using a signature algorithm.
The following prerequisites must be met:
Procedure
1. In the palette, choose  (Security Elements), then Signer Simple Signer .

2. Place Simple Signer in the integration process and define the message path.
3. Define the parameters to sign the incoming message with one or more signatures.
Option Description
Name Enter a name for the signer. It must consist of alphanumeric ASCII characters or underscores and
start with a letter. The minimum length is 3, the maximum length is 30.
Private Key Alias Enter an alias to select the private key from the keystore.
You can also specify that the alias is read dynamically from a message header; for example, if you
specify ${header.abc} then the alias value is read from the header with the name "abc“.
Signature Select a signature algorithm for the RSA or DSA private key type.
Algorithm
Signature Header Enter the name of the message header where the signature value in Base64 format is stored.
Name

4.15.8.2 Sign the Message Content with PKCS#7/CMS
Signer
Context
You work with the PKCS#7/CMS signer to make your identity known to the participants and thus ensure the
authenticity of the messages you are sending on the cloud. This task guarantees your identity by signing the
messages with one or more private keys using a signature algorithm.
Procedure
1. In the palette, choose  (Security Elements), then Signer PKCS7 Signer .

2. Place PKCS7 Signer in the integration process and define the message path.
3. Define the parameters to sign the incoming message with one or more signatures.
Parameters and Values of PKCS#7/CMS Signer
Name Name for the signer step

is encoded.
Include Content in Signed Data You can choose to include the original content that is to be
signed in the SignedData element. This SignedData ele
ment is written to the message body. Otherwise, you can
choose to include the signed data in the
SapCmsSignedData header and only keep the original
content in the message body.

Encode Signed Data with Base64 You can also Base64-encode the signed data in either the
message body or the message header, to further protect it
during message exchange.
 Note
When you Base64-encode the signed data, you en
code either the message header or body, depending
on where the signed data is placed. When verifying
the message, make sure you specify which part of the
message (header or body) was Base64-encoded.

added to the SignedData element.
○ Include Signing Time
If you activate this option (value true), the signing
time for the signed attributes will be added to the
SignedData element.
4.15.8.3 Sign the Message Content with XML Digital

Signature
You sign a message with an XML digital signature to ensure authenticity and data integrity while sending an
XML resource to the participants on the cloud.
Context

Procedure
1. In the palette, choose  (Security Elements), then Signer XML Digital Signer .
2. Place XML Digital Signer in the integration process and define the message path.
3. Define the parameters to create an XML digital signature for the incoming message.
Private Key Alias Enter an alias for selecting a private key from keystore.
You can also enter ${header.headername} or ${prop
erty.propertyname} to read the name dynamically from a
header or exchange property.
Signature Algorithm Signature algorithm for the RSA or DSA private key type
Using the private key, the sender encrypts the digest.
Digest Algorithm Digest algorithm that is used to calculate a digest from the
canonicalized XML document
Note that if the digest algorithm is not specified, the digest

algorithm of the signature algorithm is used by default.
Signature Type ○ Enveloping XML Signature

The input message body is signed and embedded in
the signature. This means that the message body is
wrapped by the Object element, where Object is
a child element of the Signature element.
○ Enveloped XML Signature
The digital signature is embedded in the XML mes
sage to be signed. This means that the XML message
contains the Signature element as one of its child
elements.
○ Detached XML Signature
The digital signature is a sibling of the signed ele
ment. There can be several XML signatures in one
XML document.
XML Schema file path (only if the option Detached XML Choose Browse and select the file path to the XML
Signatures is selected) schema file that is used to validate the incoming XML
document. This file has to be in the package
source.main.resources.xsd
Signatures for Elements (only if the option Detached XML Choose Add to enter the XPath to the attribute of type ID,
Signatures is selected) in order to identify the element to be signed. Example: /
nsx:Document/SubDocument/@Id
Namespaces prefixes must be defined in the namespaces

mapping of the runtime configuration.

Parent Node (only if the option Enveloped XML Signature is Specify how the parent element of the Signature element
selected for the attribute Signature Type) is to be specified. You have the following options:
○ Specified by Name and Namespace (using local name

and namespace)
○ Specified by XPath expression (using an XML Path
Language (XPath))
Parent Node Name (only if the option Enveloped XML A local name of the parent element of the Signature ele
Signature is selected for the attribute Signature Type and ment
Specified by Name and Namespace is selected for Parent
Node)
ture case. The Signature element is added at the end of
the children of the parent.
Parent Node Namespace (only if the option Enveloped Namespace of the parent element of the Signature ele
XML Signature is selected for the attribute Signature Type ment
and Specified by Name and Namespace is selected for
Parent Node)
ture case. In the Enveloped XML Signature case, a null
value is also allowed to support no namespaces. An empty
value is not allowed.
XPath Expression (only if the option Enveloped XML Enter an XPath expression for the parent node to be speci
Signature is selected for the attribute Signature Type and fied.
Specified by XPath expression is selected for Parent Node)
ture case.

Key Info Content Specifies which signing key information will be included in
the KeyInfo element of the XML signature. You can select a
combination of the following attribute values:
○ X.509 Certificate Chain

X509Certificate elements representing the certificate
chain of the signer key
 Note
The KeyInfo element might not contain the whole
certificate chain, but only the certificate chain
that is assigned to the key pair entry.
○ X.509 Certificate
X509Certificate element containing the X.509 certifi-
cate of the signer key
○ Issuer Distinguished Name and Serial Number
X509IssuerSerial element containing the issuer dis
tinguished name and the serial number of the X.509
certificate of the signer key
○ Key Value
Key Value element containing the modulus and expo
nent of the public key
 Note
You can use any combination of these four attrib
ute values.
Sign Key Info With this attribute you can specify a reference to the Key
Info element.
For more information about the various attributes, see the following:
http://www.w3.org/TR/xmldsig-core/
4. On the Advanced tab page, under Transformation Parameters, specify the following parameters.
Canonicalization Method for SignedInfo Specify the canonicalization method to be used to trans
form the SignedInfo element that contains the digest
(from the canonicalized XML document).
Transform Method for Payload Specify the transform method to be used to transform the
inbound message body before it is signed.
○ CamelXmlSignatureTransformMethods

 Example
 Sample Code
Example of this use case: The XML signature verifier of the receiving system expects an XML
signature as shown in the following code snippet.
The signature is a detached signature, because the signature element is a sibling of the signed
element B. However, the receiving system requires the enveloped-signature transform method to
be specified in the Transforms list. To ensure this, you have to configure a detached signature in the
XML Signer step, then add a Content Modifier step before the XML Signer step, where you specify
the header "CamelXmlSignatureTransformMethods" with the constant value “http://www.w3.org/
2000/09/xmldsig#enveloped-signature,http://www.w3.org/TR/2001/REC-xml-c14n-20010315".

<root>
<B ID="IDforB">
...
</B>
Id="_6bf13099-0568-4d76-8649-faf5dcb313c0">
<ds:SignedInfo>
...
<ds:Transforms>
www.w3.org/TR/2001/REC-xml-c14n-20010315" />
</ds:Transforms>
...
</ds:Reference>
</ds:SignedInfo>
</ds:Signature>
<root>
For more information about the various methods, see the following:
http://www.w3.org/2000/09/xmldsig#enveloped-signature,http://www.w3.org/TR/2001/REC-xml-
c14n-20010315
http://www.w3.org/2000/09/xmldsig#enveloped-signature
http://www.w3.org/TR/2001/REC-xml-c14n-20010315
http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments
http://www.w3.org/2001/10/xml-exc-c14n#
http://www.w3.org/2001/10/xml-exc-c14n#WithComments
5. On the Advanced tab page, under XML Document Parameters, specify the following parameters.

Reference Type Enter the value of the type attribute of the content refer
ence.
If you enter null or empty, no reference type is created.
More information: http://www.w3.org/2000/09/

xmldsig#Object
Namespace Prefix Enter a prefix for the XML signature namespace.
Default value is ds.
Signature Id Specifies the value of the Id attribute of the Signature ele

ment.
If you specify no value, no Id attribute is added to the Sig

nature element.
Output Encoding Select an encoding scheme for the output XML document.
The encoded output document will be written into the

message header. If no encoding scheme is specified, the
output will be UTF-8-encoded.
Exclude XML Declaration Specify whether the XML declaration header shall be
omitted in the output XML message.
Disallow DOCTYPE Declaration Specify whether DTD DOCTYPE declarations shall be dis
allowed in the incoming XML message.
Related Information
XML Digital Signature [page 805]
4.15.8.3.1 XML Digital Signature
The following types of XML digital signatures are supported:
● Enveloping XML Signature: The input message body is signed and embedded within the signature. This
means that the message body is wrapped by the Object element, where Object is a child element of the
Signature element.

 Example
A template of the enveloping signature is shown below and describes the structure supported by XML
values can vary.)
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference URI="#[generated object_id]"
type="[optional_type_value]">
<Transform Algorithm="canonicalization method">
<DigestMethod>
<DigestValue>
</Reference>
(<Reference URI="#[generated keyinfo_id]">
c14n-20010315"/>
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
<Object Id="[generated object_id]"/>
</Signature>
● Enveloped XML Signature: The digital signature is embedded in the XML message to be signed. This
means that the XML message contains the Signature element as one of its child elements. The Signature
element contains information such as:
○ Algorithms to be used to obtain the digest value
○ Reference with empty URI, which means the entire XML resource
○ Optional reference to the KeyInfo element (attribute Also Sign Key Info)
 Example
A template of the enveloped signature is shown below and describes the structure supported by XML
values can vary):
<[parent element]>
...
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference URI="" type="[optional_type_value]">
<Transform Algorithm="http://www.w3.org/2000/09/
xmldsig#enveloped-signature"/>
<DigestMethod>
<DigestValue>
</Reference>
(<Reference URI="#[generated keyinfo_Id]">
c14n-20010315"/>
<DigestMethod>
<DigestValue>
</Reference>)?

</SignedInfo>
<SignatureValue>
</Signature>
</[parent element]>
● Detached XML Signature: The digital signature is a sibling of the signed element. There can be several
XML signatures in one XML document.
You can sign several elements of the message body. The elements to be signed must have an attribute of
type ID. The ID type of the attribute must be defined in the XML schema that is specified during the
configuration.
Additionally, you specify a list of XPath expressions pointing to attributes of type ID. These attributes
determine the elements to be signed. For each element, a signature is created as a sibling of the element.
The elements are signed with the same private key. Elements with a higher hierarchy level are signed first.
This can result in nested signatures.
 Example
A template of the detached signature is shown below and describes the structure supported by XML
values can vary):
 Sample Code
(<[signed element] Id="[id_value]">


...
</[signed element]>
<other sibling/>* 
<Signature>

<SignedInfo>
<SignatureMethod>
<Reference URI="#[id_value]" type="[optional_type_value]">

<DigestMethod>
<DigestValue>
</Reference>
(<Reference URI="#[generated_keyinfo_Id]">
c14n-20010315"/>
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfo Id="[generated_keyinfo_id]">)?

</Signature>)+
Note that the following elements are generated and cannot be configured with the Integration Designer:
● Key Info ID

● Object ID
The sender canonicalizes the XML resource to be signed, based on the specified transform algorithm. Using a
digest algorithm on the canonicalized XML resource, a digest value is obtained. This digest value is included
within the 'Reference' element of the 'SignedInfo' block. Then, a digest algorithm, as specified in the signature
algorithm, is used on the canonicalized SignedInfo. The obtained digest value is encrypted using the sender's
private key.
 Note
Canonicalization transforms the XML document to a standardized format, for example, canonicalization
removes white spaces within tags, uses particular character encoding, sorts namespace references and
eliminates redundant ones, removes XML and DOCTYPE declarations, and transforms relative URIs into
absolute URIs. The representation of the XML data is used to determine if two XML documents are
identical. Even a slight variation in white spaces results in a different digest for an XML document.
4.15.8.4 Encrypt and Sign the Message Content with

PKCS#7/CMS Encryptor
Context
You perform this task to protect the message content from being altered while it is being sent to other
participants on the cloud, by encrypting the content. In the integration flow model, you configure the Encryptor
by providing information on the public key alias, content encryption algorithm, and secret key length. The
encryptor uses one or more receiver public key aliases to find the public key in the keystore. The encryption
process uses a symmetric key of specified length for content encryption. The symmetric key is encrypted by
the public recipient key with the cipher. The encryption is determined by the type of Content Encryption
Algorithm that you select. The encrypted content and the receiver information containing the symmetric
encryption key are placed in the message body.
In addition to encrypting the message content, you can also sign the content to make your identity known to
the participants and thus ensure the authenticity of the messages you are sending. This task guarantees your
identity by signing the messages with one or more private keys using a signature algorithm.
Procedure
1. In the palette, choose  (Security Elements) , then Encryptor PKCS7 Encryptor .

2. Place PKCS7 Encryptor in the integration process and define the message path.
3. Define the general parameters for encryption.
Name Enter a name for the signer. It must consist of alphanu

meric ASCII characters or underscores and start with a
letter. The minimum length is 3, the maximum length is
30.

is encoded.
Encode Body with Base64 Select this option if the message body will be base64-en
coded.
Signatures Select one of the following options:
○ Enveloped Data Only

Select this option if you want to apply encryption
only.
○ Signed and Enveloped Data
Select this option if you want to apply both encryp
tion and signing.
4. Define the parameters for the encryption process.
Content Encryption Algorithm Specify the algorithm that is to be used to encrypt the
payload.
Secret Key Length Specify the key length.
The offered key lengths depend on the chosen encryption

algorithm.
Receiver Public Key Alias Specify one or more aliases.
Enter an alias to select the public key from the keystore.

You can enter ${header.headername} or $
{property.propertyname} to read the name dy
namically from a header or exchange property.
5. Define the parameters for the signing process (only if you selected Signed and Enveloped Data for
Signatures).


added to the SignedAndEnvelopedData element.
4.15.8.5 Define PGP Encryptor
Prerequisites
Context
You use the PGP Encryptor to encrypt or sign and encrypt the payload using OpenPGP standard.
Procedure
1. In the palette, choose Encryptor PGP Encryptor .

2. Place PGP Encryptor in integration process and define the message path.
3. In Name field, provide a name for the element.
4. If you want to sign the payload with a signature, in Signatures field, choose Including.
5. In Encryption section, provide values in fields based on description in table.

Field Description
Content Encryption Algorithm In the dropdown list, select the algorithm you want to use
to encrypt the payload.
Secret Key Length Enter the secret key length.
 Note
The length of the secret key depends on the encryp
tion algorithm that you choose.
Compression Algorithm Select the algorithm you want to use to compress the pay
load.
Armored Select if you want the output to be radix 64 (base64) en

coded with additional header.
Integrity protected Data Packet Select if you want to create an Encrypted Integrity Pro
tected Data Packet. This is a specific format where an ad
ditional hash value is calculated (using SHA-1 algorithm)
and added to the message.
This increases the message security level.
Encryption User ID of Key(s) from Public Keyring You can specify the encryption key user IDs (or parts of
them). Based on this, system look for the public key in
PGP public keyring.
You can specify multiple user IDs.
4.15.8.6 Define PGP Decryptor
Prerequisites
Context
You use the PGP Decryptor to decrypt a message using OpenPGP standards.

Procedure
1. In the palette, choose Decryptor PGP Decryptor .

2. Place PGP Decryptor in integration process and define the message path.
4. In Signatures dropdown list, select option based on description in table.
Option Description
None Expected Select if you do not expect a signature in the inbound

message.
Optional Select if you are not sure of the inbound message contain
ing a signature. This enables the decryptor to decrypt
messages that contain signature and do not contain sig
nature.
Required Select if you are sure of the inbound message containing a

signature.
5. If you have selected Optional or Required in Signatures field, choose to add signer user ID.
 Note
This field is disabled if you select None Expected in Signatures field.
4.15.8.7 Define PKCS7 Decryptor
Prerequisites

Context
You use the PKCS7 decryptor to decrypt messages from a participant on the cloud. You can also verify the
authenticity of a signed message by verifying the signature of SignedAndEnvelopedData object.
Procedure
1. In the palette, choose Decryptor PKCS7 Decryptor .

2. Place PKCS7 Decryptor in integration process and define the message path.
4. In Signatures dropdown list, select option based on description in table.
Option Description
Enveloped Data Only Select if you want decryptor to process only encrypted
payloads.
Signed and Enveloped Data Select if you want decryptor to process payloads that are
signed and encrypted.
Enveloped or "Signed and Enveloped" Data Select if you want decryptor to process both encrypted
payloads and, encrypted and signed payloads.
5. If you expect the body of payload to be Base64 encoded, select Body is Base64 Encoded.
6. Choose Add to enter the public key alias of the expected senders.
 Note
○ You can add multiple aliases of all the expected senders.

○ This option is enabled only if you have selected Signed and Enveloped Data or Enveloped or "Signed
and Enveloped" Data in Signatures field.

4.15.8.8 Verify the PKCS#7/CMS Signature
You perform this task to ensure that the signed message received over the cloud is authentic.
Context
In the integration flow model, you configure the Verifier by providing information about the public key alias, and
whether the message header or body is Base64-encoded, depending on where the Signed Data is placed. For
example, consider the following two cases:
● If the Signed Data contains the original content, then in the Signature Verifier you provide the Signed Data
in the message body.
● If the Signed Data does not contain the original content, then in the Signature Verifier you provide the
Signed Data in the header SapCmsSignedData and the original content in the message body.
The Verifier uses the public key alias to obtain the public keys of type DSA or RSA that are used to decrypt the
message digest. In this way the authenticity of the participant who signed the message is verified. If the
verification is not successful, the Signature Verifier informs the user by raising an exception.
Under Public Key Alias you can enter one or multiple public key aliases for the Verifier.
 Note
In general, an alias is a reference to an entry in a keystore. A keystore can contain multiple public keys. You
can use a public key alias to refer to and select a specific public key from a keystore.
You can use this attribute to support the following use cases:
● Management of the certificate lifecycle. Certificates have a certain validity period. Using the Public Key
Alias attribute in the Verifier step, you can enter both an alias of an existing certificate (which will expire
within a certain time period) and an alias for a new certificate (which does not necessarily have to exist
already in the keystore). In this way, the Verifier is configured to verify messages signed by either the old or
the new certificate. As soon as the new certificate has been installed and imported into the keystore, the
Verifier refers to the new certificate. In this way, certificates can be renewed without any downtime.
● You can use different aliases to support different signing senders with the same Verifier step. Using the
Public Key Alias attribute, you can specify a list of signing senders.
 Note
Exceptions that occur during runtime are displayed in the Message Processing Log view of the Operations
Integration perspective.
Procedure
1. In the palette, choose Verifier PKCS#7 Verifier .

2. Place PKCS#7 Verifier in integration process and define the message path.
3. Enter the details to verify the signatures of the incoming message.
Parameters and Values of PKCS#7/CMS Signature Verifier
Header is Base64 Encoded Select this option to verify if the Signed Data encoded in
Base64 is included in the header
Body is Base64 Encoded Select this option to verify if the Signed Data encoded in
Base64 is included in the message body
ing certificate from the keystore
4.15.8.9 Verify the XML Digital Signature
Context
The XML Signature Verifier validates the XML signature contained in the incoming message body and returns
the content which was signed in the outgoing message body.
 Note
For enveloping and enveloped XML signatures the incoming message body must contain only one XML
signature.
The Verifier supports enveloping and enveloped XML signatures and detached XML signatures. In the
enveloping XML signature case, one reference whose URI references the only allowed 'Object' element via ID,
and an optional reference to the optional KeyInfo element via ID is supported
Working of XML Signature Verifier
In the validation process, a public key is required and it is fetched from the worker node keystore. On receiving
the XML message, the Verifier canonicalizes the data identified by the 'Reference' element and then digests it
to give a digest value. The digest value is compared against the digest value available under the 'Reference'
element of the incoming message. This helps to ensure that the target elements were not tampered with.
Then, the digest value of the canonicalized 'SignedInfo' is calculated. The resulting bytes are verified with the
signature on the 'SignedInfo' element, using the sender's public key. If both the signature on the 'SignedInfo'
element and each of the 'Reference' digest values verify correctly, then the XML signature is valid.

 Note
XML Signature Verifier supports both enveloping and enveloped signatures
Procedure
1. In the palette, choose Verifier XML Verifier .

2. Place XML Verifier in integration process and define the message path.
3. Enter the parameters to verify XML digital signature for the incoming message.
Parameters and Values of XML Signature Verifier

Expected Signature Type Select the expected Signature type:
○ Enveloping or Enveloped XML Signature: If the sig

nature is contained within the content or the signa
ture contains the signed data.
Verifying Enveloping Signature: If the incoming
message has enveloping signature
○ an optional 'Reference' to the optional 'KeyInfo'
element via ID is supported
○ 'References' can have one optional transform
whose algorithm must be a canonicalization
method
So it implies, an enveloping XML signature with only
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference
URI="#[object_id]">
(<Transform
method]/>)?
<DigestMethod>
<DigestValue>
</Reference>
(<Reference
(<Transform
method]/>)?
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfo
<Object Id="[object_id]"/>
</Signature>
Verifying Enveloped Signature: If the incoming mes

sage has enveloped signature
○ One reference with empty URI and an optional
reference to the KeyInfo element via its ID is al
lowed
○ An additional transform containing a canonicali
zation method is supported, beside the trans

form with algorithm "http://www.w3.org/

2000/09/xmldsig#enveloped-signature".
So it implies, an enveloped XML signature with only
<[parent]>
<Signature>
<SignedInfo>
<SignatureMethod>
<Reference URI="">
<Transform
Algorithm="http://www.w3.org/
2000/09/xmldsig#enveloped-
signature"/>
(<Transform
method]"/>)?
<DigestMethod>
<DigestValue>
</Reference>
(<Reference
(<Transform
method]"/>)?
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfo
</Signature>
</[parent]>
○ Detached XML Signatures: If the signature is con

tained within the content or the signature contains
the signed data.
Verifying Detached Signature If the incoming mes
sage has detached signature:
○ Signature element must be a sibling of the
signed element
○ Signed element must have an attribute of type ID
○ Signature references signed element via the ID
value
So it implies, a detached XML signature with only the
following structure is supported ("?" denotes zero or

one occurrence, the brackets [] denotes variables

(<[signed element]
Id="[id_value]">

...
</[signed element]>
<other sibling/>* 
<Signature>
<SignedInfo>
<SignatureMethod>
<ReferenceURI="#[id_value]"type="
[optional_type_value]">

<TransformAlgorithm=[canonicaliza
tion method]/>
<DigestMethod>
<DigestValue>
</Reference>
(<ReferenceURI="#[generated_keyin
fo_Id]">
<TransformAlgorithm="http://
c14n-20010315" />
<DigestMethod>
<DigestValue>
</Reference>)?
</SignedInfo>
<SignatureValue>
(<KeyInfoId="[generated_keyinfo_i
d]">)?
<Signature>)+

Check for Key Info Element Select this option to check that the XML Signature con
tains a Key Info element
The KeyInfo element has to contain either the certificate

chain, the certificate, the Issuer Distinguished Name and
Serial Number, or the Key Value element (or combinations
of these attributes).
 Note
In case multiple public key aliases are specified (using
the Public Key Alias attribute), this option is manda
tory (to make sure that from the KeyInfo the public
key can be derived).
Disallow DOCTYPE Declaration Select this option to disallow DTD DOCTYPE declaration in
the incoming XML message

ing certificate
Using the Public Key Alias, you can enter one or multiple
public key aliases for the Verifier.
 Note
In general, an alias is a reference to an entry in a key
store. A keystore can contain multiple public keys. You
can use a public key alias to refer to and select a spe
cific public key from a keystore.
You can use this attribute to support the following use

cases:
○ Management of the certificate lifecycle: Certificates

have a certain validity period. Using the Public Key
Alias attribute in the Verifier step, you can enter both
an alias of an existing certificate (which will expire
within a certain time period) and an alias for a new
certificate (which not necessarily has to exist already
in the keystore). That way, the Verifier is configured to
verify messages signed by either the old or the new
certificate. As soon as the new certificate has been in
stalled and imported into the keystore, the Verifier re
fers to the new certificate. That way, certificates can
be renewed without any downtime.
○ You can use different aliases to support different sign
ing senders with the same Verifier step. Using the
Public Key Alias attribute, you can specify a list sign
ing senders.
4.15.9 Define Message Persistence

4.15.9.1 Define Data Store Operations
You can use the transient data store to temporarily store messages.
Context
The transient data store (data store for short) supports four types of operations:
Data Store Operations
Operation Used to ...
Write Store the messages temporarily in the data store.
If you use a Write operation, you can store the messages in the data store by configuring the data store
name and a unique Entry ID.
More information: Define Data Store Write Operations [page 827]
Delete Trigger the deletion of messages in the data store.
More information: Define Data Store Delete Operations [page 831]
Select Fetch messages in bulk from the data store.
You can also specify the maximum number of messages you fetch in each poll.
More information: Define Data Store Select Operations [page 822]
Get Fetch a specific message from the data store.
More information: Define Data Store Get Operations [page 829]
4.15.9.1.1 Define Data Store Select Operations
This step selects entries from a transient data store and creates a bulk message containing the data store
entries.
Context
 Note
A data store can be created during message processing using the following options:
● Process a data store Write operation

● Create a data store in an XI adapter (the option Data Store must be selected in the Temporary Storage
parameter)
 Caution
This step overwrites the body of the input message.
This step selects messages from the data store and provides as output a bulk message with all entries,
according to the specified value of the parameter Number of Polled Messages (see below).
Procedure
1. In the palette, choose  (Persistence), then Data Store Operations Select .

2. Place the Select element in the integration process and define the message path.
3. On the General tab, you can change the name of the Select operation.
4. On the Processing tab, define the attributes of the data store operation based on the descriptions in the
following table. The set of attributes depends on the chosen operation.
exchange property.
tenant.
Number of Polled Messages Specifies the maximum number of messages to be fetched from the data store
within one poll (default is 1).
If the number of messages fetched per poll is specified in the header

SapDataStoreMaxResults, the header takes the precedence.

You can also configure this property in such a way that the number of fetched
messages per poll is dynamically evaluated at runtime based on the incoming
message. To do this, you can enter the following kind of expressions:
○ ${header.headername} to dynamically retrieve the number of fetched

messages per poll from the message header
○ ${xpath.<xpath>} to dynamically retrieve the number of fetched
messages per poll from an element in the message indicated by an xPath
expression
Results
This step provides an output message with a structure as defined by the following DTD content.
 Sample Code

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="messages">
<xs:complexType>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:element name="message" type="messageType" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="messageType" mixed="true">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:any namespace="##any" processContents="lax" />
</xs:sequence>
<xs:attribute name="id" type="idType" use="required" />
</xs:complexType>
<xs:simpleType name="idType">
<xs:restriction base="xs:string">
<xs:maxLength value="255" />
</xs:restriction>
</xs:simpleType>
</xs:schema>
Example structure for the case when two messages are retrieved from the data store:
 Sample Code

<messages>
<message id="<ID of first message>">
<content of first message>
</message>
<message id="<ID of second message>">
<content of second message>

</message>
<messages>
There is no in-order processing of data store entries. In other words, the sequence of data store entries
selected with a Select operation is random and non-deterministic. If you have restricted the number of
entries to be fetched (with the Number of Polled Messages attribute), the selection of retrieved entries is also
random.
Next Steps
To find out how a data store Select operation works, you can enhance the sample integration flow Timer-
Initiated Scenario with a Mail Receiver with a few clicks.
More information on the sample integration flow:
Enhance the sample integration flow in the following way:
● Add a data store Write step after the Request Reply step.
● Add a data store Select step after the data store Write step.
When you deploy and run the integration flow once, the received message should look like this (example
settings):
 Sample Code

<messages>
<message id="9197e678-345e-4e3b-ae51-3bfaa8990918">
<Products>
<Product>
<WeightUnit>KG</WeightUnit>
<CategoryName>Scanners</CategoryName>
<DimensionHeight>0.07</DimensionHeight>
<DimensionUnit>m</DimensionUnit>
<CurrencyCode>EUR</CurrencyCode>
<ProductId>HT-1081</ProductId>
<ShortDescription>Flatbed scanner - 1200 dpi x 1200 dpi - 216 x 297 mm
- Hi-Speed USB - Bluetooth Ver. 1.2</ShortDescription>
<Name>Power Scan</Name>

<Category>Scanners</Category>
<LongDescription>Flatbed scanner - 1200 dpi x 1200 dpi - 216 x 297 mm -
Hi-Speed USB - Bluetooth Ver. 1.2</LongDescription>
<QuantityUnit>EA</QuantityUnit>
<Weight>2.4</Weight>
<DimensionWidth>0.31</DimensionWidth>
<Price>89.0</Price>
<PictureUrl>HT-1081.jpg</PictureUrl>
<DimensionDepth>0.43</DimensionDepth>
<SupplierId>100000049</SupplierId>
</Product>
</Products>
</message>
In the data store Select step, specify a value bigger than 1 for the parameter Number of Polled Messages. Then,
in the first content modifier (on the Body tab), specify a different value for the element productIdentifier
than for the first message processing run. When you deploy and run the integration flow again, the resulting
message (after the integration flow has been processed) should look like this:
 Sample Code

<messages>
<message id="9197e678-345e-4e3b-ae51-3bfaa8990918">
<Products>
<Product>
<Name>Power Scan</Name>
<Price>89.0</Price>
</Product>
</Products>
</message>
<message id="b4c0f332-ec8e-4edf-81d8-3a64f374123c">
<Products>
<Product>
<Name>Photo Scan</Name>

<Price>51.0</Price>
</Product>
</Products>
</message>
</messages>
You can monitor the content of the data store in the Monitor section. Under Manage Stores, choose the Data
Stores tile. For more information, see .
4.15.9.1.2 Define Data Store Write Operations
This step performs a Write operation on the transient data store.
Context
Procedure
1. In the palette, choose  (Persistence), then Data Store Operations Write .

2. Place the Write element in the integration process and define the message path.
3. On the General tab, you can change the name of the Write operation.
 Note
The data store Write operation stores the payload, but not the header.
exchange property.

tenant.

message header
Retention Threshold for Alerting Time period (in days) within which the messages have to be fetched before an alert
in (d) is raised.
Expiration Period in (d) Number of days after which the stored messages are deleted (default is 90 days,
maximum possible value is 180 days).
The minimum value of Expiration Period should be at least twice that of Retention
Threshold for Alerting.
Encrypt Stored Message Select this option to encrypt the message in the data store.
Overwrite Existing Message Select this option to overwrite an existing message in the data store.
Trying to overwrite an existing entry without having this option selected will result
in a DuplicateEntryException.

Next Steps
Be aware of the following fact when you plan to execute a data store Select operation in a subsequent
integration flow step: When retrieving a message body from a data store in a subsequent step, only XML is
supported.
The only option to read non-XML data is provided by the data store Get operation.
4.15.9.1.3 Define Data Store Get Operations
This step gets a specific entry from the transient data store.
Context
 Note

parameter)
 Caution
This step overwrites the body of the input message.
Procedure
1. In the palette, choose  (Persistence), then Data Store Operations Get .

2. Place the Get element in the integration process and define the message path.
3. On the General tab, you can change the name of the Get operation.

exchange property.
tenant.

message header
Throw Exception on Missing You have the option to throw an exception if the entry with the specified Entry ID
Entry does not exist in the datastore.
This checkbox is selected by default.
 Remember
If you disable this option, the header SAP_DatastoreEntryFound is set
to false and no exception is thrown, even if the Entry ID does not exist.

Next Steps
4.15.9.1.4 Define Data Store Delete Operations
This step deletes an entry from a transient data store.
Context
 Note

parameter)
Procedure
1. In the palette, choose  (Persistence), then Data Store Operations Delete .

2. Place the Delete element in the integration process and define the message path.
3. On the General tab, you can change the name of the Delete operation.
exchange property.

tenant.

message header
Next Steps
4.15.9.2 Define Write Variables
Prerequisites

Context
You define variables and specify values to use them in integration flows to support message flow execution. You
can also use these variables across multiple integration flows.
Procedure
1. If a Write Variables element is present in the integration flow, choose it to define variables.
2. If you want to add a Write Variables element to the integration flow, perform the following substeps:
a. In the palette, choose  (Persistence), then Write Variables.
b. Place the Write Variables element in the integration process and define the message path.
3. On the General tab, you can change the name of the Write Variables element.
4. On the Processing tab, choose Add to add a new variable.
5. In the Name column, enter the variable name.
 Note
The value for the name of the variable must be constant and should not be a reference to some other
value. For example, a valid value is Variable1 and not ${header.source}.
6. In the Type column, select a value from the dropdown list based on the descriptions in the following table.
Variable Types
Variable Type Description
Constant If you want the variable to contain a constant
Header If you want the variable to contain header information
Xpath If you want the variable to contain XPath
To enter XPath, select XPath in the Type column, and in

the Value column choose Select to browse predefined
XPath listed in WSDL of the SOAP adapter for the sender.
 Remember
You need to enter a valid Java data type when you de
fine a variable of type XPath
Expression If you want the variable to contain an expression
Property If you want the variable to contain a property
7. In the Value column, either enter a value for the variable or choose Select to browse predefined headers.
 Note
Ensure that the value matches the type of variable you are defining.

8. If you want the variable to be used in other integration flows, select the checkbox in the Global Scope
column.
Variables cannot be downloaded using the data store viewer.
4.15.9.3 Persist Messages Permanently
Store a message payload so that you can access the stored message and analyze it at a later point in time.
Context
In an integration flow, you add a process step for persistence to store a message at a specific point in the
process.
At runtime, information such as message GUID, timestamp, and payload are stored for the messages at the
persistence process steps.
The message storage feature is useful for auditing purposes.
 Note
A message is stored on the runtime node for 90 days. After this time, the message is automatically deleted.
Procedure
1. In the palette, choose  (Persistence), then Persist.

2. Place the step in your integration flow model at the location where you want to store the message.
3. On the General tab, you can change the name of the Persist element.
4. On the Processing tab, specify the following attributes:
Option Description
Step ID Provide a unique Step ID, which can be a descriptive name or a step number. For example, for a persis
tence step configured after a mapping step it could be MessageStoredAfterMapping.
Encrypt To store the message encrypted, keep the checkbox selected.

Stored Mes
If selected, the stored message is encrypted with an encryption key that is unique for each tenant (using
sage
AES and a key length of 128 bits). The encryption key is generated automatically, stored in a different
database than the encrypted data, and periodically regenerated (to increase security).

Next Steps
To access and analyze the stored messages, you can use the OData API. For more information, see .
4.15.10 Validating Message Payload against XML Schema in

Web UI
The XML validator validates the message payload in XML format against the configured XML schema.
Prerequisites
You have the XML schema (XSD files) added in the .src.main.resources.xsd location of your integration flow
project. If you do not have the specified location in your project, you need to create one first and then add the
XSD files.
Context
You use this procedure to assign XML schema (XSD files) to validate the message payload in a process step.
The validator checks the message payload against configured XML schema, and report discrepencies in
message payload. If the validation fails, the Cloud Integration system stops the whole message processing by
default.
 Note
The XML Validator 2.0 version allows you to validate XML files against an XML schema. It supports
validation of XSD 1.1 specification along with XSD 1.0 specification.
Procedure
1. In the palette, choose  (List of Validators), and then choose XML Validator.
2. In the Name field, enter an appropriate validator flow step name.
3. In the XML Schema field, select Browse.
4. Choose an XSD file that you want to use to validate the format.
 Note
○ You can have references to other XSDs within the same project. XSDs residing outside the projects
cannot be referred.

○ You can enter a value less than 5000 for attribute maxOccurs, in input xsd. You can also enter
unbounded, if you do not want to check for max occurrence but would like to support any number
of nodes.
○ If there are any validation errors in the payload, the details of the error is visible in MPL
attachment. The link for the attachment is available in MPL log.
○ Use ${header.XmlValidationResult to get more details on validation excecptions.
5. If you want to continue the processing even if the system encounters error while validating, then select the
check box Prevent Exception on Failure.
 Note
If an exception occurs, then the error payload is added to SAP_XmlValidationResult header.
4.15.11 Define Call
You can define verious steps that execute a call into a remote (external) component or into a sub process of the
integration flow.
Related Information
Define External Call [page 836]

Define Local Call [page 842]
4.15.11.1 Define External Call
Related Information
Define Content Enricher [page 837]

Define a Send Step [page 840]
Define Request Reply [page 841]

4.15.11.1.1 Define Content Enricher
Prerequisites
● You have accessed your customer workspace in SAP Cloud Platform Integration web application.
● You are editing the integration flow in integration flow editor.
Context
The content enricher adds the content of a payload with the original message in the course of an integration
process. This converts the two separate messages into a single enhanced payload. This feature enables you to
make external calls during the course of an integration process to obtain additional data, if any.
Consider the first message in the integration flow as the original message and the message obtained by making
an external call during the integration process as the lookup message. You can choose between two strategies
to enrich these two payloads as a single message:
● Combine
● Enrich
Consider the following original and lookup messages.
Original Message
<EmployeeList>
<Employee>
<id>111</id>
</Employee>
<Employee>
<id>22</id>
<name>Geeta</name>
</Employee>
</EmployeeList>
Lookup Message
<EmergencyContacts>
<contact>
<c_id>1</c_id>
<phone>9999</phone>
</contact>
<contact>
<c_id>2</c_id>

<phone>1010</phone>
</contact>
<contact>
<c_id>3</c_id>
<phone>007</phone>
<street></street>
</contact>
If you use Combine as the aggregation strategy, the enriched message appears in the following format.
Enriched Message
<multimap:messages xmlns:multimap=”http://sap.com/xi/XI/SplitAndMerge”>
<message1>
<EmployeeList>
<Employee>
<id>111</id>
</Employee>
<Employee>
<id>22</id>
<name>Geeta</name>
</Employee>
</EmployeeList>
</message1>
<message2>
<EmergencyContacts>
<contact>
<c_id>1</c_id>
<phone>9999</phone>
</contact>
<contact>
<c_id>2</c_id>
<phone>1010</phone>
</contact>
<contact>
<c_id>3</c_id>
<phone>007</phone>
<street></street>
</contact>
</message2>
</multimap:messages xmlns:multimap=”http://sap.com/xi/XI/SplitAndMerge”>
Enrich offers you control on how you can merge the original and lookup message. In this example, we consider
the node <ext_111> as the reference to enrich the original message with the lookup message.

Consequently, you specify the following values while configuring the Content Enricher.
Section Field User input
Original Message Path to Node Employees/Employee
Key Element location
Lookup Message Path to Node EmployeeLocations\emplocation
Key Element locationid
The enriched message will be in the following format.
<EmployeeList>
<Employee>
<id>111</id>
<contact>
<c_id>1</c_id>
<phone>9999</phone>
</contact>
<contact>
<c_id>2</c_id>
<phone>1010</phone>
</contact>
</Employee>
<Employee>
<id>22</id>
<name>Geeta</name>
</Employee>
</EmployeeList>
In the enriched message, you can see the content of the lookup message after the node <location>.
 Remember
If lookup message contains more than one entry of the key element, content enricher enhances the
enriched message with all the entries referred by the key element in lookup message. In the above example,
the lookup message contains the key element ext_111 in two places. You can see that the enriched
message contains both the <contact> entries that the key element refers to.
Procedure
1. If you want to add Content Enricher to the integration process, perform the following substeps.

a. In the palette, choose Content Enricher .
b. Place Content Enricher in the integration process and define message path.
2. Choose the Content Enricher.
3. In Content Enrichment Type field, select value from dropdown list based on description in table.
Value Description
Combine Combines the original and lookup messages. You cannot

define any rules for combining messages.
Enrich You can define the path to node and key element based on
which the original message is enriched with the lookup
message.
4. If you have selected Enrich as the Content Enrichment Type, provide values in fields based on description in
table.
Section Field Description
Original Message Path to Node Path to the reference node in the origi
nal message
Key Element Key element in the original message
Lookup Message Path to Node Path to the reference node in the

lookup message
Key Element Key element in the lookup message
4.15.11.1.2 Define a Send Step
You use a send step type to configure a service call to a receiver system for scenarios and adapters where no
reply is expected.
Context
Using this step makes only sense in combination with one of the following adapter types (for the channel
between the send step and the receiver):
● AS2 adapter
● JMS adapter

● Mail adapter
● SOAP SAP RM adapter
● SFTP adapter
Procedure
1. In the palette, click Call ( icon) and choose External Call Send , and drop it inside the
2. In the palette, click Participants ( icon), select Receiver, and drop it outside the Integration Process
pool.
3. Create a connection between the send step and the receiver and configure the channel (selecting one of
the above mentioned adapter types).
4.15.11.1.3 Define Request Reply
You use this step to call an external receiver system in a synchronous step and get back a response.
Context
Certain integration scenarios might require that the Cloud Integration tenant communicates with an external
service, retrieves data from it, and further processes the data. In such cases, you can use the request reply step
as an exit to connect to the external service.
For example, in your integration scenario the tenant needs to retrieve data on electronic products from a
product catalog (the external service) and to further process the data. If the external service exposes the data
through a REST API, you can use the request reply step to connect to the service via the HTTP or OData
receiver adapter.
In the integration flow model, you design the external service as a receiver shape and to connect the request
reply step with the receiver shape with a receiver channel.
 Caution
The request reply step does not work with all available Cloud Integration adapter types.
Adapters that can be used with the request reply step are the following ones (to mention examples):
● OData receiver adapter

● HTTP receiver adapter
● SOAP (SOAP 1.x) receiver adapter
For a detailed instruction on how to use this step in a simple example scenario, check out .

Procedure
1. In the palette, choose Call External Call Request Reply .

2. To add this shape to the model, click somewhere inside the Integration Process box of the integration flow
model.
No further attributes are to be specified for this step type.
3. In the palette, click Participants ( icon), select Receiver, and drop it outside the Integration Process
pool.
4. Create a connection between the request reply step and the receiver and configure the channel.
4.15.11.2 Define Local Call
You can invoke a local integration process from the main integration process by using a local call.
Related Information
Define Process Call [page 842]

Define Looping Process Call [page 843]
4.15.11.2.1 Define Process Call
Context
You can use this step type to invoke a local integration process from the main integration process.
You use local integration processes to keep the size of a process model at a manageable scale. That way, you
can break down the main integration process into smaller fragments (represented by local integration
processes). You combine these fragments to achieve the complete message processing design of your
integration flow.

Procedure
1. In the palette, choose Call Local Call Process Call .

2. Click somewhere inside the Integration Process box of the integration flow model.
3. Choose Select to search for the local integration process you like to connect to.
All local integration processes are listed that are modeled for this integration flow.
Related Information
4.15.11.2.2 Define Looping Process Call
Execute a local integration process in a loop.
Context
Procedure
1. In the palette, choose Call Local Call Looping Process Call .

2. Click somewhere inside the Integration Process box of the integration flow model.
3. Specify the following attributes.

Field Description
Expression Type Specify the kind of expression you want to enter in the
Condition Expression field.
○ XML
For XPath expressions, for example: //
customerName = ‘Smith’
○ Non-XML
For Camel Simple Expression Language
 Note
Examples:
${header.SenderId}, which indicates the

SenderId header field.
${in.body}, which indicates the body of the

incoming message.
For more information about Camel Simple Expression

Language, see: http://camel.apache.org/simple.html
.
Condition Enter the condition (XML or Non-XML, as specified by the

property Expression Type).
Do not use a mixed expression (containing both XML and

Non-XML expressions).
For more information about the usage of operators, see

Max. Number of Iterations Maximum number of iterations that the loop can perform
before it stops (99999 iterations maximum).
You can use this setting to prevent a never-ending loop.
Example Scenario for the Local Loop Process.
 Note
The local loop process refers to a while loop. The sub process will run as long as the loop condition is
fulfilled.
To explain how a local loop process works, we provide a simple example.
Every morning, an account owner wants to check all transactions performed on his account. He calls a
specific web service and has defined this request:
<accountID>12345<accountID>

<action>Transaction_of_last_Day</action>
</accountinfo>
The appropriate response for this request is:
<accountinforesponse>
<transaction>
<id>1</id>
...
</transaction>
...
<transaction>
<id>55</id>
...
</transaction>
<hasMore>true</hasMore>
</accountinforesponse>
The account owner has to call the web service again and again until there are no more transactions
available and he gets the response:
<hasMore>false</hasMore>
To simplify the call, he can use the loop embedded in the HCP Integration Service. He needs to define a
while condition in the Xpath such as/accountinforesponse[hasMore = ‘true’].
As long as data are available, the call will continue. The sub-process inducing the loop uses the ServiceCall
step in the Request-Reply mode to call the web service. As soon as the web service gets the response
<hasMore>false</hasMore>, the processing exits the loop and continues with the next step. The last
response of the web service is the new payload, that will be taken as message body into the next step.

Related Information
4.15.12 Define Additional Elements
4.15.12.1 Define Exception Subprocess
Context
You use this element to catch any exceptions thrown in the integration process and handle them.
Procedure
2. To add an exception subprocess to the integration flow, choose Process Exception Subprocess from
the palette. The subprocess can be dropped into the integration process and should not be connected to
any of the elements of the integration flow.
3. Select the exception subprocess.
a. In the property sheet specify a name.
4. Start the process with Error Start event always.
5. End the process with either End Message or Error End or Escalation event.
 Note
○ You can use an End Message event to wrap the exception in a fault message and send it back to the
sender in the payload.
○ You can use an Error End event to throw the exception to default exception handlers.
6. You can also add other flow elements between the start and end events .
 Note
○ For example, you can choose Add Service Call from the context menu of a connection within the
pool. This enables you to call another system to handle the exception.
○ The following elements are not supported within an Exception Subprocess:

○ Another Exception Subprocess
○ Integration Process
○ Local Integration Process
○ Sender
○ Receiver
○ Start Message
○ Terminate Message
○ Timer Start
○ Start Event
○ End Event
○ Router
 Note
○ The message processing log will be in an error state even if a user catches an exception and
performs additional processing on it.
○ You can get more details on exception using ${exception.message} or $
{exception.stacktrace}.
○ You cannot catch exceptions of local integration process in the main integration process.
4.15.12.2 Define Local Integration Process
You use the local integration process to simplify your integration process. You can break down the main
integration process into smaller fragments by using local integration processes. You combine these fragments
to achieve your main integration process.
Prerequisites
● You have accessed the customer workspace in SAP Cloud Platform Integration web application.
● You are editing the integration flow containing local integration process element.
Context
You use the Local Integration Process to define an integration process that is specific to the integration flow in
which it is created. You can use this integration process with the Process Call step.

 Restriction
You cannot use the following integration flow steps within the Local Integration Process step:
● Another Local Integration Process

● End Message
● Sender
● Receiver
Procedure
1. Choose the local integration process element you want to configure.

2. If you want to provide a name for the local integration process element, in the Name field, enter name.
3. If you want to configure the elements inside the local integration process, refer to the documentation
relevant to those elements.
4. If you want to add the local integration process to a process call element, perform the following substeps:
a. Select the process call element in integration flow editor.
b. In Local Integration Process field, choose Select.
c. In Select Local Integration Process window, select the local integration process you want to assign to
the process call.
 Note
You can use an Error End event to throw the exception to default exception handlers.
4.15.13 Defining Transaction Handling
You can configure transaction handling on integration process or local integration process level.
Context
Transactional processing means that the message (as defined by the steps contained in a process) is
processed within one transaction.
For example, consider a process with a Data Store Write operation. When transaction handling is activated, the
Data Store entry is only committed if the whole process is executed successfully. In an error case, the
transaction is rolled back and the Data Store entry is not written. When transaction handling is deactivated, the
Data Store entry is committed directly when the integration flow step is executed. In an error case, the Data
Store entry is nevertheless persisted (and not removed or rolled back).

Note the following limitations and recommendations related to transaction handling:

Aggregator steps Required for JDBC (mandatory)
 Caution
Choosing JDBC transaction handling is mandatory to ensure that ag
gregations are executed consistently.
Data Store operations Required for JDBC (recommended but not mandatory)
In case you choose Not Required, the related database operation is commit
Write
ted per single step and no end-to-end transaction handling is implemented.
JMS sender adapter Not Required
This applies also for scenarios that include In general, no transaction handling is required.
the AS2 adapter.
 Note
These adapters do not require JMS transaction handling. Their retry
handling works independent from the selected transaction handler.
JMS sender adapter together with JDBC re Required for JDBC
sources (Data Store, Aggregator, Write varia
bles)  Note
This applies also for scenarios that include However, note that it is not recommended to use transactional JMS re
the AS2 adapter. sources and JDBC resources in parallel.
JMS receiver adapter in a Send step Required for JMS (mandatory)

the JMS queue.
Several JMS receiver adapter together with a Required for JMS (mandatory)
JMS sender adapter
the JMS queue.
One JMS receiver adapter (without Splitter or Not Required

sequential Multicast)
No JMS transaction handler is required.
 Note
Distributed transactions between JMS and JDBC resources are not
supported.

Several JMS receiver adapter or a sequential Required for JMS

Multicast or Splitter step followed by a JMS
receiver adapter
all JMS queues.
Note that aynchronous parallel processing of messages cannot be transactional.
For more details on parallel processing, check the documentation of General or Iterating Splitter and Parallel
Multicast.
Let us assume that you like to configure a message multicast and the integration flow also contains a Data
Store operations step. In this case, you can choose one of the following options to overcome the mentioned
limitation:
● Deactivate transactional processing.

● Use a Sequential Multicast instead of a Parallel Multicast.
Procedure
1. Depending on whether you like to configure transaction handling for an integration process or a local local
integration process, select the header of the corresponding shape in the integration flow modelling area.
2. Specify the details for transactional processing:
To configure transactional process for an Integration Process, select one of the following options for the
Transaction Handling property.
Transaction Handling for Integration Process

tem database.

tional database processing is applied (to ensure that the
process is accomplished within one transaction).

tem database.
Not Required No specific transactional processing is configured. The in

tegration process does not process transactions even if
(for example) data store operations are included.
To configure transactional process for a local Integration Process, select one of the following options for
the Transaction Handling property.
Transaction Handling for Local Integration Process
From Calling Process Transactional processing is inherited from the calling

process. The value defined for the calling process is used
as the timeout.
tional database processing is applied.

tem database.

tem database.
Related Information
Define General Splitter [page 691]

Define Iterating Splitter [page 698]

4.15.14 Dynamically Configure Integration Flow Parameters
For can certain integration flow parameters you can enter a reference to a header or property instead of a fixed
value. At runtime, the actual value of the header or property in the incomung message is then used as
parameter value. This is referred to as dynamic configuration.
Prerequisites
● The parameter supports dynamic configuration.

More information: Parameters That Support Dynamic Configuration [page 854]
● There is a header or property that you can use for dynamic configuration of the parameter. Either the
header/property is defined by a preceding component in the integration flow or it is provided by the
integratrion framework.
Context
The following kinds of headers and properties can be used to dynamically configure a certain parameter.
● Headers or properties defined by a content modifier step (preceding the step or adapter for which you like
to define a dynamic parameter)
More information:
● Predefined headers or properties that are provided by the integration framework.
More information:
Procedure
1. Open the integration flow in edit mode and select the component where you like to dynamically configure a
parameter.
2. Specify the parameter value by entering an expression of the following form.
${header.<name of header>}
or
${property.<name of property>}
Example:
In a content modifier step that is placed before the component where you dynamically configure a
parameter, you have defined the following header (which contains the customer number of an inbound
message): customerNo.

For the parameter (to be defined dynamically) enter the following expression:
${header.customerNo}
At runtime, the actual value for the header customerNo (derived from the inbound message) is used as
parameter value.
3. Finish the configuration of the integration flow.
Related Information

4.15.14.1 Dynamic Parameters (Example)

You can define placeholders for parameters of certain adapters or step types. The values of these parameters
will then dynamically be set based on the content of the processed message.
For example, parameters From, To, Cc, Bcc, Subject, Mail Body as well as the attachment name, can be
To set an attribute to be dynamically filled by a message header attribute, enter a variable in the form $
{header.attr} in the corresponding field for the attribute of the corresponding step or adapter.
At runtime, the value of the header attribute (attr) of the processed message is written into the field for the
corresponding attribute of the outbound email.
Example: Dynamic Attributes for the Mail Adapter
For example, assume that you dynamically define the email Subject of the mail adapter as shown in the figure
below by the variable {header.attr}.
At runtime, a message is received whose header contains a header attribute attr with the value value1. The
mail adapter will then dynamically set the subject of the outbound email with the entry value1.
Note that the mail adapter processes message content either already contained in the inbound mail (from a
sender system) or as modified by content modifier steps on its way between sender and mail adapter.

As shown in the figure, we assume that the inbound message contains a header header1 with value value1.
Let us assume that you like to define the Subject attribute of the mail receiver adapter dynamically via this
header. To do that, specify the Subject field by the following entry:
${header.header1}
As a result, the mail adapter dynamically writes value value1 of header header1 (from inbound message) into
the subject of the outbound email.
Related Information
4.15.14.2 Parameters That Support Dynamic Configuration
The following tables list all parameters that can be configured dynamically (for the various adapter types and
integration flow steps).
For more information on the individual adapter and step types, see the documentation of the related
integration flow component.
Adapters
Adapter Type Dynamically Configurable Parameters
HTTP receiver ● Address (uses header CamelHttpUri)

● Location ID
● Query (uses header CamelHttpQuery)
● Method
● Credential Name
● Private Key Alias
IDoc receiver ● Address

● Location ID
● Credential Name
Mail receiver ● Location ID

● From
● To
● Cc
● Bcc
● Subject
● Mail Body
● Attachment Name

Adapter Type Dynamically Configurable Parameters
Mail sender Location ID
OData V2 receiver ● Query

● Custom Query Options
● Resource Path
ProcessDirect receiver Address
RFC receiver Destination
SFTP receiver File Name
SFTP sender File Name
SOAP 1.x receiver ● Address

● Location ID
● Credential Name
● Private Key Alias for Signing (WS Security)
SOAP 1.x sender ● Private Key Alias for Response Signing (WS Security)
● Public Key Alias for Response Encryption (WS Security)
SOAP SAP RM receiver ● Address

● Location ID
● Credential Name
Success Factors (SOAP) sender Query
XI receiver ● Address
● Credential Name
● XI-specific identifiers (Communication Party (for
sender and receiver), Communication Component (for
sender and receiver), Service Interface (for receiver),
and Service Interface Namespace (for receiver))
Integration Flow Steps
Step Type Dynamically Configurable Parameters
Data Store Select ● Data Store Name

● Number of Polled Messages
Data Store Write ● Data Store Name

● Entry ID

Step Type Dynamically Configurable Parameters
Data Store Get ● Data Store Name

● Entry ID
Data Store Delete ● Data Store Name

● Entry ID
Simple Signer Private Key Alias
XML Signer Private Key Alias
Related Information
4.15.14.3 Headers and Exchange Properties Provided by the

Integration Framework
Headers and Exchange Properties
Type (Prop
erty or Related
Name Header) Component Description
Archived-At Header Mail adapter Specifies a link to the archived form of an e-mail.
CamelAggregated Header Aggregator Is relevant for use cases with message aggregation.
CompletedBy
● timeout
Processing of the aggregate has been stopped because the con
figured Completion Timeout has been reached.
● predicate
Processing of the aggregate has finished because the Comple
tion Condition has been met.
CamelCharset Property Encoder Specifies the character encoding to be applied for message process
Name ing.
Is relevant for content encoding steps.

Type (Prop
erty or Related
CamelFileName Header SFTP re Overrides the existing file and directory name that is set directly in
ceiver the endpoint.
adapter
You can use this header to dynamically change the name of the file
and directory to be called.
If you do not enter a file name in the SFTP receiver adapter, the con
tent of the CamelFileName header (if set) is used as file name. If
this header is not specified, the Exchange ID is used as file name.
CamelHttpMethod Header HTTPS Refers to the HTTP method name of the incoming request (GET,
sender POST, PUT, DELETE, and so on).
adapter
The HTTPS sender adapter sets this header.
CamelHttpQuery Header HTTPS Refers to the query string that is contained in the request URL (for ex
sender ample, CamelHttpQuery=abcd=1234).
adapter
HTTP re
In the context of a receiver adapter, this header can be used to dy
ceiver
namically change the URI to be called.
adapter
CamelHttpRespon Header HTTPS You can use this header to manually set the HTTP response status
seCode sender code.
adapter
CamelHttpUri Header HTTP re Overrides the existing URI set directly in the endpoint.
ceiver
You can use this header to dynamically change the URI to be called.
adapter
CamelHttpUrl Header HTTPS Refers to the complete URL called, without query parameters.
sender
For example, CamelHttpUrl=https://
adapter
test.bsn.neo.ondemand.com/http/hello.
CamelServletCon Header HTTPS Refers to the path specified in the address field of the channel.
textPath sender
For example, if the address in the channel is /abcd/1234, then
adapter
CamelServletContextPath is /abcd/1234.
CamelSplitCom Property Splitter Indicates whether an Exchange is the last split.

plete
CamelSplitIndex Property Splitter Provides a counter for split items that increases for each Exchange
that is split (starts from 0).

Type (Prop
erty or Related
CamelSplitSize Property Splitter Provides the total number of split items (if you are using stream-
based splitting, this header is only provided for the last item, in other
words, for the completed Exchange).

Type (Prop
erty or Related
CamelXmlSignatur Header XML signer Specifies transformation methods in a comma-separated list.

eTransformMe
You can use this header to specify transformation methods in a
thods
comma-separated list. This header will overwrite the value of the op
tion Transform Method for Payload.
 Example
 Sample Code
Example of this use case: The XML signature verifier of the re
ceiving system expects an XML signature as shown in the follow
ing code snippet.
The signature is a detached signature, because the signature ele

ment is a sibling of the signed element B. However, the receiving
system requires the enveloped-signature transform method to
be specified in the Transforms list. To ensure this, you have to
configure a detached signature in the XML Signer step, then add
a Content Modifier step before the XML Signer step, where you
specify the header "CamelXmlSignatureTransformMethods" with
the constant value “http://www.w3.org/2000/09/
xmldsig#enveloped-signature,http://www.w3.org/TR/2001/
REC-xml-c14n-20010315".

<root>
<B ID="IDforB">
...
</B>
<ds:Signature
xmlns:ds="http://www.w3.org/2000/09/
xmldsig#"
Id="_6bf13099-0568-4d76-8649-
faf5dcb313c0">
<ds:SignedInfo>
...
<ds:Reference
URI="#IDforB">
<ds:Transforms>
www.w3.org/2000/09/xmldsig#enveloped-
signature" />
c14n-20010315" />
</ds:Transforms>
...
</ds:Reference>
</ds:SignedInfo>

Type (Prop
erty or Related
<ds:SignatureValue>aUDFmiG71</
ds:SignatureValue>
</ds:Signature>
<root>
CamelXmlSignatur Header XML Signer Specifies the Id attribute value of the QualifyingProperties element.
eXAdESQualifying
PropertiesId
CamelXmlSignatur Header XML Signer Specifies the Id attribute value of the SignedDataObjectProperties
eXAdESSignedDa element.
taObjectPropertie
sId
CamelXmlSignatur Header XML Signer Specifies the Id attribute value of the SignedSignatureProperties el
eXAdESSigned ement.
SignaturePropertie
sId
CamelXmlSignatur Header XML Signer Specifies the value of the Encoding element of the DataObjectFor
eXAdESDataOb mat element.
jectFormatEncod
ing
CamelXmlSignatur Header XML Signer Overwrites the namespace parameter value.

eXAdESName
space
CamelXmlSignatur Header XML Signer Overwrites the prefix parameter value.

eXAdESPrefix
Cc Header Mail receiver Additional e-mail address that the message is sent to.
adpter

Type (Prop
erty or Related
Content-Encoding Header HTTP re The encoding used during message transport (for example, gzip for
ceiver GZIP file compression).
adapter
This information is used by the receiver to retrieve the media type
that is referenced by the content-type header.
If this header is not specified, the default value identity (no com
pression) is used.
More information: https://tools.ietf.org/html/rfc2616 (section

14.11)
The list of available content types is maintained by the Internet As

signed Numbers Authority (IANA). For more information, see:http://
www.iana.org/assignments/http-parameters/http-parame
ters.xhtml#content-coding .

Type (Prop
erty or Related
Content-Type Header HTTP re HTTP content type that fits to the body of the request.
ceiver
The content type is composed of two parts: a type and a subtype.For
adapter
example, image/jpeg (where image is the type and jpeg is the
Mail receiver subtype).
adapter
Examples:
● text/plain for unformatted text

● text/html for text formatted with HTML syntax
● image/jpeg for a jpeg image file
● application/json for data in JSON format to be processed
by an application that requires this format
More information on the available types: https://www.w3.org/Proto

cols/rfc1341/4_Content-Type.html
The list of available content types is maintained by the Internet As

signed Numbers Authority (IANA). For more information, see http://
www.iana.org/assignments/media-types/media-types.xhtml .
 Note
If transferring text/* content types, you can also specify the
character encoding in the HTTP header using the charset pa
rameter.
The default character encoding that will be applied for text/*

content types depends on the HTTP version: us-ascii for
HTTP 1.0 and iso-8859-1 for HTTP 1.1.
Text data in string format is converted using UTF-8 by default

during message processing. If you want to override this behavior,
you can use the Content Modifier step and specify the
CamelCharsetName Exchange property. To avoid encoding is
sues when using this feature together with the HTTP adapter,
If you use a Content Modifier step and you want to send

iso-8859-1-encoded data to a receiver, make sure that you
specify the CamelCharsetName Exchange property (either
header or property) as iso-8859-1. For the Content-Type
HTTP header, use text/plain; charset=iso-8859-1.

Type (Prop
erty or Related
Date Header Mail adapter The date and time when the e-mail was sent.
From Header Mail adapter Email address that the message comes from.
JMSTimestamp Header JMS Con Time when a JMS message was created.
sumer
Message-ID Header Mail adapter ID that the mail system assigned to the e-mail when it was first cre
ated.
Reply-to Header Mail adapter Message ID of the message that this e-mail is a reply to.
SAP_ApplicationID Header When you monitor the messages at runtime, you can search for all
messages whose defined SAP_ApplicationID has a specific
value (displayed as the MessageID attribute in the Message Monitor
ing editor).
As Type, select the XPath expression that points to the message ele
ment that is to be used as the application ID.
SapAuthenticate Header SOAP sender User name of the client that calls the integration flow.
dUserName adapter
If the sender channel is configured to use client certificate authenti
XI sender cation, no such header is set (as it is not available in this case).
adapter
SAP_Correla Property Specifies whether message processing logs (MPLs) are to be corre
teMPLs lated with each other using a correlation ID.
By default, MPL correlation is switched on. To specify this property,

select Constant as Type and enter True or False as Value.
SAP_DataStoreRe Header XI sender Number of retries of a message.

tries adapter
The XI adapter sets this header (when as Quality of Service you have
XI receiver selectedExactly Once and as Temporary Storage you have chosen the
adapter option Data Store).
You can use this header to specify that the behavior of the integration
flow changes depending on the number of retries that are actually
performed. For example, you can use this header to define that after a
certain number of retries the message is routed to a specific receiver
(for example, to send an alert message to a recipient).
You can use this header in case you configure the XI adapter with
Data Store as temporary storage.

Type (Prop
erty or Related
SAP_ErrorModel Property You can use this property to set a Model Step ID for an integration
StepID flow step. This identifier is required to relate to an integration flow
step in error handling.
SAP_MAIL_EN Property Mail sender The alias used for decryption of an encrypted mail.
CRYPTION_DE adapter
TAILS_DECRYP
TION_ALIAS
(String)
SAP_MAIL_EN Property Mail sender The received mail was successfully decrypted (not set, true, false).
CRYPTION_DE adapter
TAILS_DECRYP
TION_OK (boolean)
SAP_MAIL_EN Property Mail sender The received mail was encrypted.

CRYPTION_DE adapter
TAILS_ENCRYPTED
(boolean)
SAP_MAIL_EN Property Mail sender There is an error message if the mail could not be decrypted.
CRYPTION_DE adapter
TAILS_ER
ROR_MESSAGES
(String)
SAP_MAIL_SIGNA Property Mail sender Is true if all signatures could be validated.

TURE_OVER adapter
ALL_VERIFICA
TION_OK (boolean)
SAP_MAIL_SIGNA Property Mail sender The signer certificate.

TURE_DE adapter
TAILS_CERTIFI
CATES (Array of
java.secur
ity.cert.X509Certifi
cate)
SAP_MAIL_SIGNA Property Mail sender The result of the verification.

TURE_DE Adapter
TAILS_VERIFICA
TION_OK (Array of
boolean)

Type (Prop
erty or Related
SAP_MAIL_SIGNA Property Mail sender The error message for a failed verification.
TURE_DE Adapter
TAILS_ER
ROR_MESSAGES
(Array of String)
SAP_MessageType Header Makes an application-specific Message Type avalable for monitoring.

When set in the integration flow, this header will be stored in the mes
sage processing log.
SAP_MessagePro Header Contains the ID of the message processing log.

cessingLogID
You can use this property to read the ID of the message processing
log (no write access supported).
SAP_MessagePro Property Points to the message Pprocessing log for the respective Exchange.
cessingLogID
You can use this property to read the ID of the message processing
log (no write access supported).
SAP_MessagePro Header You can use this property to set an at most 40 characters alphanu
cessingLogCustom meric custom status for the current message processing log. The
Status value is transferred as CustomStatus attribute to the root part of
the message processing log and then stored in the message process
ing log header table.
SAP_MessagePro Header Log level under which the message processing log for the corre
cessingLogLevel sponding message exchange is written. Allowed values are INFO,
NONE, DEBUG (case-insensitive).

Type (Prop
erty or Related
SAP_ReceiverOver Property Defines the handling of the message header SAP_Receiver . If set
write to true, the header SAP_Receiver will be overwritten with the
new value in case a value is assigned to the SAP_Receiver header.
If set to false, the new value is added to the already existent header
content. The content is stored as a comma-separated list,
Default value: java.lang.Boolean.FALSE
This behavior is helpful in scenarios like,the multicast pattern, for ex

ample, where a message is sent to several receivers and all receivers
are to be collected in the MPL (not just the last added header).
 Note
Example configuration:
Name: SAP_ReceiverOverwrite
Type: Constant
Value: True
SAP_Receiver Header Makes available the name of the receiver to monitoring.
If you have specified SAP_Sender or SAP_Receiver, the corre

sponding values are displayed in the message processing log. If you
change the SAP_Receiver value during message processing, all
values are added to the receiver field in the message processing log
as a comma-separated list. If you don't want this behavior, you can
specify the exchange property SAP_ReceiverOverwrite (see
below).
SAP_Sender Header Makes available the name of the sender to monitoring.
If you have specified SAP_Sender or SAP_Receiver, the corre

sponding values are displayed in the message processing log. If you
change the SAP_Receiver value during message processing, all
values are added to the receiver field in the message processing log
as a comma-separated list. If you don't want this behavior, you can
specify the exchange property SAP_ReceiverOverwrite (see
below).
SapDataStoreId Header Data Store Entry ID used/set by the Data Store component.
SapDataStoreMax Header Data Store Used dynamically overwrite the configured number of polled mes
Results sages in case of Data Store SELECT operation.
SapInterfaceName Header XI adapter XI protocol header

Type (Prop
erty or Related
SapInterfaceName Header XI adapter XI protocol header

space
SAPJMSAlerttime Header JMS Con Specifies the time when an alert needs to be sent.
sumer
SAPJMSRetries Header JMS Con Number of retries of a JMS message.

sumer
The JMS sender adapter sets this header.
You can use this header to specify that the behavior of the integration
flow changes depending on the number of retries that are actually
performed. For example, you can configure a scenario where a mail is
sent to an administrator with the message as an attachment and the
integration flow is terminated successfully after a specified number
of retries.
You can use this header in case you configure the XI adapter with JMS
Queue as temporary storage.
SAPJMSRetryAt Header JMS Con

sumer
SapReceiverParty Header XI adapter XI protocol header
SapReceiverService Header XI adapter XI protocol header
SapRefToMessageI Header XI adapter XI protocol header

dEx
SapRefToMessa Header XI adapter XI protocol header

geId
SapSenderParty Header XI adapter XI protocol header
SapSenderService Header XI adapter XI protocol header
Sender Header Mail adapter Specifies the actual sender (acting on behalf of the e-mail address
stated in the From header).
SOAPAction Header SOAP This header is part of the Web service specification.
adapter
Subject Header Mail adapter Specifies the subject of the e-mail message.
To Header Mail adapter Specifies the e-mail address that the message is sent to.

Related Information

About Headers and Exchange Properties [page 868]
4.15.14.3.1 About Headers and Exchange Properties
The integration framework gives you options to evaluate certain parameters at runtime, which allows you to
define sophisticated ways of controlling message processing. There are two different kinds of parameter:
● Message header
This is transferred as part of the message header.
When you use an HTTP-based receiver adapter, these parameters are converted to HTTP headers and
transferred asi such to the receiver.
 Note
Note that data written to the message header during a processing step (for example, in a Content
Modifier or Script step) will also be part of the outbound message addressed to a receiver system
(whereas properties will remain within the integration flow and will not be handed over to receivers).
Because of this, it is important to consider the following header size restriction if you are using an
HTTP-based receiver adapter: If the message header exceeds a certain value, the receiver may not be
able to accept the inbound call (this applies to all HTTP-based receiver adapters). The limiting value
depends on the characteristics of the receiver system, but typically ranges between 4 and 16 KB. To
overcome this issue, you can use a subsequent Content Modifier step to delete all headers that are not
supposed to be part of the outbound message.
● Exchange property
seen as an abstraction of a message exchange process as it is executed by the Camel framework. An
Exchange is identified uniquely by an Exchange ID. In the Properties area of the Exchange, additional data
can be stored temporarily during message processing. This data is available for the runtime during the
whole duration of the message exchange.
When you use an HTTP-based receiver adapter, Exchange properties are not converted to an HTTP header
for transfer to the receiver.
You can use the Content Modifier to modify the content of the message header and the Exchange property (as
well as of the message body) at one or more steps during message processing.
You can use the message header and the Exchange property to configure various sophisticated ways of
controlling message processing.
One option is to use dynamic parameters:
When configuring an integration flow using the modeling user interface, you can define placeholders for
attributes of certain adapters or step types. The value that is actually used for message processing is set
dynamically based on the content of the message. You can use a certain message header or Exchange property
to dynamically set a specific integration flow property.

Another option to derive such data from a message at runtime is to access a certain element in the message
payload.
The following headers and Exchange properties are supported by the integration framework.
 Note
A subset of these parameters is provided by the associated Open Source components, such as Apache
Camel.
4.15.15 Define Error Configuration
You can define how to handle errors when message processing fails at runtime.
Context
Procedure
1. Open the Design tab and select the integration flow.

2. Click the area outside the Integration Process shape and choose Error Configuration.
3. Specify the error handling strategy.
Option Description
Select Return Exception to Sender When a message exchange could not be processed, an exception is raised
back to the sender.
Deselect Return Exception to Sender When a message exchange could not be processed, no error handling strat
(default setting) egy is used.
4.15.16 Manage Resources of an Integration Flow
Use Resources to manage different resources associated within an integration content optimally. The term
"resources" refers to a collection of different categories of file types. 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 allows 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.
 Note
Mouseover the filename to view the access path.
Category File Type Extensions
Archives Archive .jar
Mappings Message Mapping .mmap
Operation Mapping .opmap
XSLT Mapping .xslt
.xsl
Scripts Groovy Script .gsh
.gy
.groovy
Java Script .js
Schemas XSD .xsd
WSDL .wsdl
EDMX .edmx
.xml
Adding Resources
To add files from the file system, do the following:

You can add multiple resources from the file system and also add dependent resources by archiving the parent
along with its dependent resources in a single *.zip file.
But you cannot add multiple archive (*.zip) files or an archive file along with other resource files, only
resources with the following extensions and dependencies are uploaded:

Resource Type Dependent Resources You can...
WSDL WSDL, XSD Upload individual files or an archive file

that contains multiple WSDL or XSD or
both type resources.
XSD XSD Upload individual files or an archive file

that contains only XSD resources.
EDMX EDMX, XML Upload individual EDMX or XML files, or

an archive file that contains multiple
EDMX or XML files or both type resour
ces.
Ensure that your XML file contains the

valid EDMX tag.
XSLT mapping XSL Upload individual files or an archive file

that contains only XSL resources.
 Note
The above resource view uploaders is supported for Remote APIs as well
1. In the Resources tab, choose Add and select a file type.

2. Select the File System as the source.
3. Choose Browse to select one or more files from the file system.
4. Choose OK to upload the files.
To add files from an integration flow project, do the following:

1. In the Resources tab, choose Add and select a file type.
2. Select the Integration Flow as the source.
3. To import files from other integration projects, select the relevant Package and the Integration Flow.
4. In the Resources table, select one or more files and choose OK to upload the files.
5. To add dependent resources select Include dependent resources.
6. In the Resources table, select one or more dependent files and choose OK to upload the files.
Quick Actions
You can perform the following actions for managing resource files:
Actions Description
 (Delete) Removes relevant resource file from the integration flow. Be
fore deleting make sure that the selected file is not being re
ferred in other integration flows.

Actions Description
 (Download) Downloads the respective resource file to your local file sys
tem.
4.15.17 Problems View
Use this view to see all errors and warnings associated with integration components and resources.
The Problems view displays all issues related to integration components and resources occurred during design
time. This helps you identify and resolve issues that have an impact during runtime.
The first column in the table displays the Severity status of an issue. In the second column, there is a
Description of the issue. The third column highlights the Location of the integration component or resource
where the issue was encountered. When you click the location ID, the application redirects you to the affected
configuration of the integration component or to the affected resource.
 Example
Consider a location is displayed as SFTP [Receiver_1]. Here the issue is related to a SFTP receiver adapter.
This is identified by noticing the name and ID displayed in brackets, sometimes components may only have
ID displayed. You must note that for resources ID's are not displayed.
 Note
Content validation issues of resources when edited in their respective editors are not propagated to the
Integration Flow.
4.15.18 Error Classification
At design time of an integration project, the way how a message is to be processed is specified by a number of
integration flow steps (for example, content modifier, encryptor or routing step). When an integration flow is
being processed at runtime, errors can occur at several individual steps within the process flow (referred to as
processing steps to differentiate them from the integration flow steps as modelled at design time).
Integration flow steps can specify message processing at different levels of complexity. Therefore, in general an
integration flow step (design time) can result in multiple processing steps steps at runtime.
Each processing step gets a unique Step ID which is displayed in the message processing log.
For example, a content modifier step in an integration flow can (at runtime) be related to multiple processing
steps: The content modifier step can be configured in a way that one processing step changes the message
header, one the message body, and another one an exchange property.

This content modifier will get three different Step IDs at runtime, for example: CallActivity_9, setBody4
and setProperty1.
To relate a modelled integration flow step (like the content modifier mentioned above) to an error occurring at
a certain processing step at runtime, you can use an identifier which is referred to as Model Step ID.
To allow an integration flow developer to relate to a certain integration flow step during error handling, the
runtime provides the Model Step ID of the integration flow step where the error occurred as Exchange Property
SAP_ErrorModelStepID. The content of the property can then be evaluated in the error handling.
 Note
You can use the property for instance in a condition definition of a Router step to choose a different error
handling strategy depending on the step where the error occurred.
Example for a routing condition : ${property.SAP_ErrorModelStepID} = ‘CallActivity_1’
4.16 Deploying Data Flows
Context
Procedure
1. In the Integration Package Editor, in the Artifacts section, select the required data flow from the list.
2. Choose Deploy.
3. In the Settings dialog box that appears, enter the following details:
○ Data Center URI

○ Application Name
○ Organization Name
Once you enter the above mentioned details, the application forms the Data Service URL.
4. Choose OK.
5. In the LOG ON screen that appears, enter the organization name.
6. Choose Log On.
The Data Integration application opens its Projects tab.
7. In the dialog box that appears, enter the following details as required:
○ Name
○ Source

○ Target
8. Choose OK.
The newly deployed data flow appears as an entry in the Projects tab page. If required, you can switch back
to the SAP Cloud Platform Integration Web application.
 Note
To switch to SAP Cloud Platform Integration Web Catalog view from Data Integration using the Back
Button in the browser, perform the required substeps:
○ If you use Internet Explorer, from the context menu of Back Button , select Cloud Integration.
○ If you use Google Chrome, click twice on Back Button .
○ If you use Mozilla Firefox, from the context menu of Back Button , select Cloud Integration .
If you want to switch to SAP Cloud Integration Web Catalog view from Data Integration using the
Forward Button in the browser then by default, it displays the Projects tab page without the Settings
option. This behavior remains the same for Internet Explorer, Google Chrome, and Mozilla Firefox.
If you do not have authorization to access the Data Integration application then you get the following
error messages:
○ Error message for Google Chrome and Mozilla Firefox:
User is not included in the organization. Contact your security administrator for assistance.
○ Error message for Internet Explorer:
HTTP 404: Not found error

Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information PUBLIC 875
www.sap.com/contactsap
© 2019 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

Developer's Guide: Managing Integration Content: Public SAP Cloud Platform Integration For Processes 2019-02-15

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Developer's Guide: Managing Integration Content: Public SAP Cloud Platform Integration For Processes 2019-02-15

Uploaded by

Copyright:

Available Formats

PUBLIC

SAP Cloud Platform Integration for Processes

Developer's Guide: Managing Integration Content

THE BEST RUN

1 Managing Integration Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Developing Integration Content Using the Eclipse Integration Designer. . . . . . . . . . . . . . . . . . . 6

Developer's Guide: Managing Integration Content

Developer's Guide: Managing Integration Content

Developer's Guide: Managing Integration Content

Developer's Guide: Managing Integration Content

Installing Features of SAP Cloud Platform Integration

2.1 Understanding the Basic Concepts and the

2.1.1 Elements of an Integration Flow

An integration flow allows you to specify how a message is processed on a tenant.

In detail, you define the following aspects in an integration flow:

● The senders and receivers of the message

Developer's Guide: Managing Integration Content

Message Processing (Steps)

2.1.1.1 Headers and Exchange Properties

Developer's Guide: Managing Integration Content

One option is to use dynamic parameters:

Headers Relevant for Signing with XML Digital Signature

Developer's Guide: Managing Integration Content

<?xml version="1.0" encoding="UTF-8" ?>

Headers Relevant for Message Splitting

Developer's Guide: Managing Integration Content

Headers Relevant for Content Encoding

Headers Relevant for the HTTP and HTTPS Adapter

Developer's Guide: Managing Integration Content

Here is an example of such a header:

Content-Type: text/html; charset=utf-8

Headers Relevant for the SFTP Adapter

Headers Relevant for the Mail Adapter

Developer's Guide: Managing Integration Content

Headers Relevant for the Aggregator Step

Headers Relevant for JMS Messages

Developer's Guide: Managing Integration Content

Developer's Guide: Managing Integration Content

Dynamic Parameters (Example) [page 14]

2.1.1.1.1 Dynamic Parameters (Example)

Example: Dynamic Attributes for the Mail Adapter

Developer's Guide: Managing Integration Content

Parameters That Support Dynamic Configuration [page 854]

2.1.2 Understanding the Integration Content Types

Types of Integration Projects

Developer's Guide: Managing Integration Content

Integration Flow Project Structure

Elements in Project Structure Description

src.main.resources.mapping Package for mappings to be used in scenario

src.main.resources.scenarioflows.integrationflow Package for BPMN integration flow

src.main.resources.wsdl Package for interfaces like IDOC , WSDL used in scenario

MANIFEST.MF File contains dependencies to runtime components and inte­

Additional Elements in Project Structure Description

src.main.resources Package for parameters.prop and parameters.propdef

parameters.prop File contains externalized attributes representing a varia­

parameters.propdef File contains metadata such as value type of the parame­

Value Mapping Project Type

Value Mapping Project Structure

Elements in Project Structure Description

MANIFEST.MF File contains dependencies to runtime components

The following table lists the restrictions.

Developer's Guide: Managing Integration Content

Comment on Database Transactions

MANIFEST.MF File contains dependencies to runtime components and inte

parameters.prop File contains externalized attributes representing a varia

parameters.propdef File contains metadata such as value type of the parame

URL Tenant management node URL (also referred to as manage

Parameters declared through Parameter section of mapping edi

Operation mapping containing multiple operations are not sup

Since parameters are not supported in Message Mapping, so op

Only synchronous operation mappings with at least one map