Contents

Foreword by Andreas Quenstedt ..................................................................................................... 19

Preface ....................................................................................................................................................... 21
Acknowledgments ................................................................................................................................ 27

1 Introduction to Cloud Integration 31

1.1 The Role of Cloud Integration in a Cloud-Based Strategy ................................... 33

1.2 Use Cases ................................................................................................................................... 36

1.2.1 Point-to-Point versus Mediated Communication ....................................... 36
1.2.2 Message-Based Process Integration ................................................................ 37
1.2.3 Cloud-to-Cloud Integration ................................................................................. 38
1.2.4 Cloud-to-On-Premise Integration ..................................................................... 39
1.2.5 On-Premise-to-On-Premise Integration ......................................................... 40
1.2.6 Hybrid Usage of Cloud and On-Premise Integration Solutions .............. 41
1.2.7 Usage in Different Cloud Environments ......................................................... 42
1.3 Capabilities ............................................................................................................................... 44
1.3.1 Integration Platform as a Service ...................................................................... 44
1.3.2 Message Processing Step Types (Integration Capabilities) ...................... 45
1.3.3 Connectivity Options ............................................................................................. 46
1.3.4 Prepackaged Integration Content .................................................................... 51
1.3.5 Security Features .................................................................................................... 52
1.3.6 High Availability ...................................................................................................... 52
1.3.7 Integration Design and Monitoring Tools ...................................................... 53
1.4 Editions ...................................................................................................................................... 53

1.5 Summary ................................................................................................................................... 54

2 Getting Started 57

2.1 Architecture Overview ........................................................................................................ 57

2.1.1 Containerized and Clustered Integration Platform .................................... 58
2.1.2 Basic Constituents of the Cloud Integration ................................................. 62
2.1.3 Architecture: User Access and Data Storage Areas ..................................... 64

7
Contents Contents

2.1.4 Secure Communication ........................................................................................ 70

2.1.5 Implementation of Message Flows .................................................................. 70
2.1.6 Architecture Summary ......................................................................................... 74
2.1.7 Environment-Specific Aspects of the Architecture ..................................... 77
2.2 Tools and Processes .............................................................................................................. 78
2.2.1 Tools ............................................................................................................................ 78
2.2.2 Processes ................................................................................................................... 84
2.3 Running Your First Integration Scenario ..................................................................... 86
2.3.1 Demo Scenario and Landscape .......................................................................... 86
2.3.2 Prerequisites ............................................................................................................ 87
2.3.3 Setting Up the Landscape and the Technical Connections ...................... 88
2.3.4 Developing the Integration Flow ...................................................................... 89
2.3.5 Creating and Deploying a User Credentials Artifact .................................. 114
2.3.6 Importing Certificates Required by the Mail Server into a Keystore ..... 117
2.4 Summary ................................................................................................................................... 123

3 SAP Integration Content Catalog 125

3.1 Introduction to SAP Integration Content Catalog .................................................. 125

3.2 Terms and Conditions of Using Prepackaged Integration Content ................ 128
3.2.1 Quick Configure versus Content Edit ............................................................... 128
3.2.2 Notify about Update (Manual Updates) ......................................................... 129
3.2.3 Automatic Updates ................................................................................................ 131
3.3 Consuming Prepackaged Content ................................................................................. 131
3.3.1 Searching SAP Integration Content Catalog ................................................. 132
3.3.2 Importing Prepackaged Integration Content ................................................ 136
3.3.3 Modifying or Configuring the Integration Package .................................... 137
3.3.4 Deploy Content ....................................................................................................... 143
3.4 Prepackaged Content Provided by SAP ....................................................................... 143
3.4.1 Content for SAP SuccessFactors ........................................................................ 144
3.4.2 Content for SAP Cloud for Customer ............................................................... 145
3.4.3 Content for Integrating with SAP Customer Experience .......................... 147
3.4.4 Content for Integrating with SAP Business Network ................................. 149
3.4.5 Content for Globalization Scenarios ................................................................ 151
3.4.6 Content for ELSTER Integration ......................................................................... 152
3.4.7 Content for Salesforce Integration ................................................................... 154
3.5 Creating Your Own Content Package ........................................................................... 156

8 8
 Contents

3.6 Adapters to Third-Party Applications for SAP Integration Suite ...................... 159

3.7 Summary ................................................................................................................................... 162

4 Basic Integration Scenarios 163

4.1 Working with Cloud Integration’s Data Model ....................................................... 163

4.1.1 Message Processing: The Apache Camel Framework ................................ 165
4.1.2 Working with Apache Camel’s Message Model ........................................... 168
4.1.3 Connecting and Configuring a Sender with an Integration Flow .......... 170
4.1.4 Adding and Configuring Steps in the Integration Flow ............................. 174
4.1.5 Checking Configuration Using the Problems Tab ....................................... 178
4.1.6 Running the Integration Flow ............................................................................ 179
4.1.7 Troubleshooting ..................................................................................................... 183
4.2 Using Externalization to Enable Easy Reuse of Integration Flows .................. 185
4.2.1 Externalizing ............................................................................................................ 186
4.2.2 Configuring and Running the Scenario ........................................................... 190
4.3 Calling External Systems by Invoking an OData Service ..................................... 192
4.3.1 The Target Scenario ............................................................................................... 193
4.3.2 Invoking an OData Service .................................................................................. 194
4.3.3 Configuring the OData Connection ................................................................. 195
4.3.4 Creating the Resource Path Using the Query Editor ................................... 197
4.3.5 Using the Content Enricher Step ....................................................................... 203
4.3.6 Using the Poll Enrich Step .................................................................................... 208
4.4 Working with Mappings .................................................................................................... 214
4.4.1 The Scenario ............................................................................................................. 215
4.4.2 Adding and Using Resources via the References Tab ................................. 217
4.4.3 Applying the Mapping Step in the Message Processing Chain ............... 222
4.4.4 Using Value Mappings to Enhance Your Scenario ...................................... 229
4.5 Defining and Provisioning API-based Integration .................................................. 234
4.5.1 The Target Scenario ............................................................................................... 234
4.5.2 Providing an OData Service ................................................................................. 234
4.5.3 Providing a SOAP Service ..................................................................................... 245
4.5.4 Providing a REST Service ....................................................................................... 249
4.6 Message Routing ................................................................................................................... 250
4.6.1 The Scenario ............................................................................................................. 251
4.6.2 Configuration of the Content-Based Router ................................................. 253
4.6.3 Running the Content-Based Router Scenario ............................................... 257
4.7 Summary ................................................................................................................................... 260

9
Contents Contents

5 Advanced Integration Scenarios 261

5.1 Working with an Aggregator .......................................................................................... 261

5.1.1 Sample Scenario ..................................................................................................... 262
5.1.2 Sending Messages via SoapUI ............................................................................ 266
5.2 Working with Lists ................................................................................................................ 271
5.2.1 The Scenario ............................................................................................................. 271
5.2.2 Configuring the Integration Flow ..................................................................... 273
5.2.3 Running the Integration Flow ............................................................................ 283
5.2.4 Enriching Individual Messages with Additional Data ................................ 287
5.3 Asynchronous Message Handling .................................................................................. 289
5.3.1 Synchronous versus Asynchronous Communication from the
Cloud Integration Perspective ............................................................................ 290
5.3.2 Adding an Asynchronous Receiver ................................................................... 301
5.3.3 Routing a Message to Multiple Receivers Using the
Multicast Pattern .................................................................................................... 304
5.4 Reliable Messaging Using the JMS Adapter .............................................................. 311
5.4.1 Asynchronous Decoupling of Inbound Communication ........................... 311
5.4.2 Configuring Retry for Multiple Receivers ....................................................... 322
5.4.3 Configuring Explicit Retry with Alternative Processing ............................ 329
5.5 SAP Process Integration and the XI Adapters ........................................................... 336

5.6 Using Event-Driven Messaging ....................................................................................... 336

5.6.1 Configuring a Publish-Subscribe Scenario ..................................................... 337
5.6.2 Reading Business Details from Providers ....................................................... 352
5.6.3 Sending Events to SAP Integration Suite, Advanced Event Mesh .......... 355
5.7 Summary ................................................................................................................................... 359

6 Special Topics in Integration Development 361

6.1 Timer-Based Message Transfers ..................................................................................... 362

6.1.1 The Scenario ............................................................................................................. 362
6.1.2 Configuring a Timer-Based Integration Flow ................................................ 363
6.1.3 Externalizing Timer Configurations ................................................................. 367
6.1.4 Running the Integration Flow ............................................................................ 369
6.2 Using Dynamic Configuration via Headers or Properties .................................... 370
6.2.1 An Integration Flow with a Dynamically Configured Attribute .............. 372
6.2.2 Monitoring Dynamically Configured Attributes at Runtime ................... 377

10 10
 Contents

6.2.3 Using Predefined Headers and Properties to Retrieve Specific

Data Provided by the Integration Framework .............................................. 381
6.2.4 Adding a Custom Header to the Message Exchange ................................. 389
6.2.5 Monitoring Messages Using Custom Headers ............................................. 390
6.3 Structuring Large Integration Flows Using Local Processes ............................... 391
6.3.1 Managing Complexity through Modularization ......................................... 392
6.3.2 Developing an Integration Flow with a Local Integration Process ........ 392
6.3.3 Using Exception Subprocesses .......................................................................... 399
6.4 Connecting Integration Flows Using the ProcessDirect Adapter ..................... 405
6.4.1 Use Cases for the ProcessDirect Adapter ....................................................... 406
6.4.2 A Simple Example ................................................................................................... 407
6.4.3 Using Variables to Share Data between Different
Integration Flows ................................................................................................... 412
6.4.4 Dynamic Endpoint Configuration with the ProcessDirect Adapter ...... 415
6.5 Connecting to a Database Using the JDBC Adapter ............................................... 421
6.5.1 JDBC Adapter Concepts ........................................................................................ 422
6.5.2 Setting Up a Database System .......................................................................... 423
6.5.3 Setting Up an Example Scenario ....................................................................... 425
6.6 Connecting to an AS2 Server Using an AS2 Adapter ............................................. 428
6.6.1 Configuration of Sender Adapter to Receive Messages ............................ 429
6.6.2 Configuration of the Receiver Adapter to Send AS2 Messages .............. 432
6.7 Versioning and Migration of Integration Flows ...................................................... 436
6.7.1 Integration Flow Component Versions ........................................................... 436
6.7.2 Upgrading an Integration Flow Component ................................................. 438
6.7.3 Adapting Integration Content for SAP Process Orchestration ................ 442
6.8 Simulation of Integration Flow Processing ................................................................ 448

6.9 Transporting Integration Packages to Another Tenant ....................................... 455

6.9.1 Manually Transporting Integration Packages .............................................. 456
6.9.2 Transporting Integration Packages Using Enhanced Change and
Transport System ................................................................................................... 456
6.9.3 Transporting Integration Packages Using the Cloud-Based
Transport Management Service ........................................................................ 457
6.10 Using the Adapter Development Kit ............................................................................. 460
6.10.1 Overview .................................................................................................................... 460
6.10.2 Installing the Adapter Development Kit ......................................................... 461
6.10.3 Developing a Sample Adapter (SAP BTP, Neo and Cloud Foundry
Environments) ......................................................................................................... 464
6.10.4 Deploying the Adapter (SAP BTP, Neo Environment) ................................. 470
6.10.5 Deploying the Adapter (SAP BTP, Cloud Foundry Environment) ............ 472
6.10.6 Testing the New Adapter ..................................................................................... 475

11
11
Contents Contents

6.11 Guidelines for Integration Flow Development ........................................................ 478

6.11.1 Running an Integration Flow Under Well-Defined Boundary
Conditions ................................................................................................................. 479
6.11.2 Relaxing Dependencies to External Components ....................................... 480
6.11.3 Keeping Readability in Mind ............................................................................... 480
6.11.4 Handling Errors Gracefully .................................................................................. 481
6.11.5 Applying the Highest Security Standards ...................................................... 481
6.11.6 Additional Best Practices ..................................................................................... 481
6.12 Working with Script Collections ..................................................................................... 482
6.12.1 Creating a Script Collection ................................................................................. 483
6.12.2 Using the Script Collection in an Integration Flow ..................................... 485
6.13 Advanced Message Mapping Concepts ....................................................................... 488
6.13.1 Creating Message Mapping as an Artifact .................................................... 489
6.13.2 Using the Message Mapping in Integration Flow ....................................... 490
6.14 Summary ................................................................................................................................... 492

7 Cloud Integration Operations 493

7.1 Operations: Overview ......................................................................................................... 493

7.2 Monitoring Integration Content and Message Processing ................................. 495

7.2.1 Managing Integration Content ......................................................................... 497
7.2.2 Log Configuration ................................................................................................... 501
7.2.3 Monitoring Message Processing ....................................................................... 502
7.2.4 Managing Tiles ........................................................................................................ 518
7.3 Managing Security ................................................................................................................ 521
7.3.1 Maintaining Security Material ........................................................................... 523
7.3.2 Managing the Keystore ........................................................................................ 526
7.3.3 Maintaining Pretty Good Privacy Keys ............................................................ 534
7.3.4 Defining User Roles ............................................................................................... 535
7.3.5 Maintaining Certificate-to-User Mappings ................................................... 537
7.3.6 Defining Access Policies ....................................................................................... 539
7.3.7 Managing Java Database Connectivity Data Sources ................................ 543
7.3.8 Testing Outbound Connectivity ........................................................................ 547
7.4 Managing Temporary Data ............................................................................................... 560
7.4.1 Monitoring Data Stores ........................................................................................ 560
7.4.2 Monitoring Variables ............................................................................................ 564
7.4.3 Maintaining Message Queues ........................................................................... 566
7.4.4 Maintaining Number Ranges ............................................................................. 575

12 12
 Contents

7.5 Accessing Logs ......................................................................................................................... 576

7.5.1 Monitoring Audit Logs .......................................................................................... 577
7.5.2 Checking System Log Files ................................................................................... 579
7.6 Managing Locks ...................................................................................................................... 580
7.6.1 Dealing with Message Locks ............................................................................... 581
7.6.2 Managing Design Time Artifact Locks ............................................................. 584
7.7 Monitoring Message Usage .............................................................................................. 585

7.8 Integrating Cloud Integration with Enterprise Monitoring Tools ................... 588
7.8.1 Configuring Splunk to Receive Data from Cloud Integration .................. 589
7.8.2 Enabling External Logging from SAP BTP Cockpit ....................................... 593
7.9 Summary ................................................................................................................................... 597

8 Application Programming Interfaces 599

8.1 Introduction ............................................................................................................................. 599

8.2 Java APIs Provided by Cloud Integration .................................................................... 600

8.3 Using the Java API in a User-Defined Function ........................................................ 602

8.4 Using the Script Step ............................................................................................................ 606

8.4.1 Target Scenario ....................................................................................................... 607
8.4.2 Enhancing the Integration Flow ........................................................................ 608
8.5 Open Data Protocol API ...................................................................................................... 611
8.5.1 SAP Business Accelerator Hub ............................................................................ 615
8.5.2 Cross-Site Request Forgery Token Handling for SAP BTP,
Neo Environment ................................................................................................... 628
8.5.3 Monitoring Message Flows Using the API ..................................................... 631
8.5.4 Managing Deployed Integration Content Using the API .......................... 636
8.5.5 Managing Log Files Using the APIs ................................................................... 639
8.5.6 Managing Message Store Entries Using APIs ............................................... 640
8.5.7 Managing Security Material Using the API .................................................... 644
8.5.8 Managing the Partner Directory Using the API ............................................ 645
8.6 Using Cloud Integration with API Management ..................................................... 646
8.6.1 Establishing a Connection between Cloud Integration and
API Management .................................................................................................... 648
8.6.2 Provisioning APIs .................................................................................................... 650
8.6.3 Consuming APIs ...................................................................................................... 657
8.7 Summary ................................................................................................................................... 660

13
13
Contents Contents

9 Connecting to External Third-Party Systems 661

9.1 Introduction ............................................................................................................................. 661

9.2 Open Connectors: Connectors Catalog ........................................................................ 663

9.2.1 Overview Tab ........................................................................................................... 666
9.2.2 Information Tab ...................................................................................................... 668
9.2.3 Setup Tab .................................................................................................................. 669
9.2.4 Resources Tab .......................................................................................................... 670
9.2.5 Validation Tab ......................................................................................................... 671
9.2.6 API Docs Tab ............................................................................................................. 672
9.3 Open Connectors: Understanding Connectors ......................................................... 675
9.3.1 Authenticate Connections with API Providers ............................................. 677
9.3.2 Inspect Authenticated Connector Instances ................................................. 680
9.3.3 Testing in the API Docs ......................................................................................... 682
9.4 Open Connectors: Understanding Common Resources ....................................... 686
9.4.1 Creating a Common Resource ............................................................................ 688
9.4.2 Cloning Common Resources ............................................................................... 690
9.4.3 Transforming Resources ...................................................................................... 691
9.5 Using Cloud Integration with Open Connectors ..................................................... 695
9.5.1 Scenario ..................................................................................................................... 695
9.5.2 The Solution ............................................................................................................. 696
9.6 Using Cloud Integration to Connect to Third-Party Systems without
Open Connectors ................................................................................................................... 704
9.6.1 Connecting to Salesforce ..................................................................................... 705
9.6.2 Connecting to Amazon Web Services .............................................................. 711
9.7 Summary ................................................................................................................................... 719

10 Cloud Integration Security 721

10.1 Technical System Landscape ............................................................................................ 722

10.1.1 Architecture .............................................................................................................. 722
10.1.2 Network Infrastructure ........................................................................................ 725
10.1.3 Data Storage Security ........................................................................................... 727
10.1.4 Data Protection and Privacy ................................................................................ 728
10.1.5 Malware Scanner .................................................................................................... 730
10.1.6 Physical Data Security ........................................................................................... 731

14 14
 Contents

10.2 Processes ................................................................................................................................... 731

10.2.1 Software Development Process ......................................................................... 732
10.2.2 Operating the Cloud Infrastructure and Providing and
Updating the Software ......................................................................................... 732
10.2.3 Setting Up Secure Connections between the Tenant and
Remote Systems ..................................................................................................... 734
10.3 User Administration and Authorization ...................................................................... 735
10.3.1 Technical Aspects of User Management ........................................................ 736
10.3.2 Personas, Roles, and Permissions ...................................................................... 736
10.3.3 Managing Users and Authorizations for a Cloud Integration
Subaccount ............................................................................................................... 738
10.3.4 Authorization on the Package and Integration Flow Level ...................... 748
10.4 Data and Data Flow Security ............................................................................................ 754
10.4.1 Basic Cryptography in a Nutshell ...................................................................... 755
10.4.2 Transport-Level Security Options ...................................................................... 761
10.4.3 Authentication and Authorization ................................................................... 763
10.4.4 Securely Connecting a Customer System to Cloud Integration
through HTTPS ........................................................................................................ 777
10.4.5 Setting Up a Scenario Using OAuth with the Twitter Adapter ............... 787
10.4.6 Message-Level Security Options ........................................................................ 795
10.4.7 Designing Message-Level Security Options in an Integration Flow ...... 799
10.5 Keystore Management ....................................................................................................... 819
10.5.1 Using X.509 Security Material for Cloud Integration ................................. 819
10.5.2 Managing Security Material in the Tenant Keystore ................................. 823
10.5.3 Managing the Lifecycle of Keys Provided by SAP ......................................... 827
10.6 Summary ................................................................................................................................... 832

11 Productive Scenarios Using Cloud Integration 835

11.1 Integration of SAP Cloud for Customer and SAP ERP ............................................ 835
11.1.1 Technical Landscape .............................................................................................. 836
11.1.2 Example Adapter Configurations ..................................................................... 837
11.2 Integration of SAP Cloud for Customer with SAP S/4HANA Cloud ................. 840

11.3 Integration of SAP Marketing Cloud and Various Applications ....................... 840

11.4 Integration of SAP SuccessFactors and SAP ERP ...................................................... 842

11.4.1 Technical Landscape .............................................................................................. 843
11.4.2 SAP SuccessFactors Adapter ............................................................................... 844

15
15
Contents Contents

11.5 Integration of SAP Applications with SAP Business Network ........................... 846

11.6 Integration with German Tax Authorities Using the ELSTER Adapter ........... 848
11.7 SAP S/4HANA Integration with Salesforce ................................................................ 851
11.7.1 Technical Landscape .............................................................................................. 852
11.7.2 Example Adapter Configurations ..................................................................... 853
11.8 Summary ................................................................................................................................... 855

12 Special Topics in Cloud Integration 857

12.1 Edge Integration Cell: Overview ..................................................................................... 857

12.2 Edge Integration Cell: High-Level Architecture ....................................................... 859

12.2.1 Edge Lifecycle Management ............................................................................... 861
12.2.2 Runtime and Operations ...................................................................................... 862
12.2.3 External Services ..................................................................................................... 863
12.3 Edge Integration Cell: Setup and Installation ........................................................... 864

12.4 Develop, Deploy, and Monitor Your Integrations in the Edge

Integration Cell ....................................................................................................................... 869

12.5 Migration from SAP BTP, Neo Environment to SAP BTP,

Cloud Foundry Environment ............................................................................................. 871
12.5.1 Benefits of Migration to SAP BTP, Cloud Foundry Environment ............ 871
12.5.2 Availability Zones and Regions .......................................................................... 872
12.5.3 Migration Approach .............................................................................................. 872
12.6 Migration from SAP Process Orchestration to Cloud Integration .................... 874
12.6.1 Assessment and Evaluation ................................................................................ 874
12.6.2 Planning and Preparation .................................................................................... 877
12.6.3 Migrate and Manage ............................................................................................. 878
12.7 Summary ................................................................................................................................... 879

13 Summary and Outlook 881

13.1 Integration Content Design .............................................................................................. 882

13.2 Connectivity ............................................................................................................................. 883

13.3 Edge Integration Cell ........................................................................................................... 884

16 16
 Contents

13.4 Migration from SAP Process Orchestration to Cloud Integration .................... 885

13.5 Summary ................................................................................................................................... 885

The Authors ............................................................................................................................................. 887

Index .......................................................................................................................................................... 889

17
17
 Chapter 3
SAP Integration Content Catalog 3
SAP provides prepackaged integration content to enable the quick
implementation of integration scenarios. These packages are found in
SAP Integration Content Catalog. In this chapter, we’ll dive into SAP Inte-
gration Content Catalog, present its available features, and explore the
prepackaged integration content currently available.

In Chapter 1, we discussed the role that SAP Integration Suite plays within SAP’s cloud
strategy. We also discussed SAP Integration Suite’s positioning within the SAP land-
scape and presented a number of use cases.
As the adoption of cloud-based applications keeps growing, the likelihood that more
customers will need to build the same integration scenarios will continue to increase.
Why not build these common integration scenarios in advance and reduce implemen-
tation costs for customers? With this approach, customers simply need to reuse exist-
ing integration scenarios, rather than build their own.
This standardization and reuse capability is exactly what SAP has made available
through its SAP Integration Content Catalog. In this chapter, we’ll introduce you to SAP
Integration Content Catalog and walk you through the steps required to consume pre-
packaged, SAP-provided content. We’ll explore available prepackaged content and dis-
cuss some use cases. You’ll also learn about creating your own content package and
using adapters to third-party applications.

3.1 Introduction to SAP Integration Content Catalog

Since the introduction of cloud computing technologies, organizations have shifted
investments in software licenses. Organizations have rapidly moved from the concept
of software ownership to software rental. As a result, SAP is also growing its cloud-
based portfolio with standardized products in HR (with SAP SuccessFactors), market-
ing, sales, service, procurement, supply chain management, and finance. We’re con-
vinced that this portfolio will continue to grow.
Most customers may find themselves needing to integrate cloud-based applications
with other on-premise or cloud-based applications to cover the total end-to-end busi-
ness process. As described in previous chapters, Cloud Integration is well positioned as
the integration platform for such use cases.

125
125
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Most capabilities provided by these cloud-based applications are standardized in terms

of protocols, endpoints, and message structures. Therefore, integration scenarios built
over Cloud Integration for these cloud-based applications have a good chance of being
implemented and reused by many other customers and partners. This reusability is
exactly what SAP provides with its prepackaged integration content for the most fre-
quently used SAP cloud-based applications. This integration content is available in SAP
Integration Content Catalog.
The catalog includes templates with prebuilt integration flows (iFlows), value map-
pings, and other integration artifacts that you can reuse, thus significantly reducing
implementation time, cost, and risk. The catalog presents and categorizes content in a
simple manner, allowing you to browse and discover content that might be relevant
for your scenarios. SAP Integration Content Catalog content is bundled in packages.
Each package contains artifacts and objects that logically belong together and support
a particular integration scenario. The artifacts and objects bundled in a package can be
organized into four categories: data integration, iFlow, OData service, or value mapping
(see the information box on basic artifact types in Chapter 2, Section 2.3.4).
When dealing with SAP Integration Content Catalog, you’ll need to understand the dif-
ferent roles involved in consuming and publishing content. We generally distinguish
among the following roles:
 Integration developer
A member of the partner or customer organization responsible for consuming the
prepackaged content available in SAP Integration Content Catalog.
 Content publisher
The person responsible for building and making the integration package available in
SAP Integration Content Catalog.
 Content reviewer
The person responsible for reviewing and ensuring the quality of the content deliv-
ered in SAP Integration Content Catalog by the publisher.

Separating roles during the publication process helps improve the correctness of the
content published in the catalog. Note that, at the time of this writing, only SAP can
publish content packages. Consequently, the content publisher and reviewer roles
aren’t yet relevant to customers. This chapter will therefore primarily focus on the role
of the integration developer, which is the role that you, as a reader of this book, will
most likely play.
You can access SAP Integration Content Catalog in two different ways:
 Via a publicly accessible URL
You can access the publicly (and freely) available SAP Integration Content Catalog
web-based application at https://api.sap.com. The landing page for SAP Integration
Content Catalog is shown in Figure 3.1.

126 126
 3.1 Introduction 3toSAP
SAP Integration
Integration Content Catalog

Figure 3.1 Publicly Accessible SAP Integration Content Catalog

Note that SAP Integration Content Catalog is published on SAP Business Accelerator
Hub. You don’t need a Cloud Integration tenant to use this web application. From
this publicly available URL, only read access is available. If you need to reuse this
content or have access to other features, you must access a Cloud Integration tenant.
 Via your own tenant
You can access SAP Integration Content Catalog via your own Cloud Integration
tenant at http://<server>:<port>/itspaces.
As shown on the left side of Figure 3.2, the Cloud Integration Web UI consists of four
main pages:
– Discover – Monitor
– Design – Settings
Refer to Chapter 2, Section 2.2.1, for more details about each section.

Figure 3.2 Landing Page of the Web UI

127
127
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

As shown in Figure 3.2, the Discover page can be used to browse through SAP Integra-
tion Content Catalog. Let’s dive more deeply into how to consume the available inte-
gration content.

3.2 Terms and Conditions of Using Prepackaged Integration Content

Terms and conditions, within the context of Cloud Integration, refer to usage restric-
tions that affect prepackaged content. The publisher of the content can determine what
content in their packages can be used and how. The terms and conditions mainly affect
three aspects (at the time of this writing):
 Quick configure versus content edit
Conditions the publisher applies that influence how the content can be consumed.
 Notify about update (manual update)
Related to updating the prepackaged content included in SAP Integration Content
Catalog.
 Automatic update
Related to consumed prepackaged content automatically being updated.

We’ll discuss these three aspects in the following sections.

3.2.1 Quick Configure versus Content Edit

One of the conditions that a publisher can apply to prepackaged content is the quick
configure versus content edit condition. Quick configure or content edit conditions are
used during the publication process to restrict the usage of the content. Let’s explore
these two conditions:
 Quick configure (also called configure-only)
The user of the package can only configure the options already made available by the
package artifacts. Depending on the specifics of the concerned package, this condi-
tion usually only includes configuring the different adapters used in the iFlow. The
configure-only option also means that the integration content itself (e.g., the steps in
an iFlow) can’t be changed and are therefore use-only. This option is somewhat
restrictive because you must stick to the provided content. However, one of the
advantages of this approach is that managing the various versions of the content is
easier for the content publisher, who can also be certain that the content is being
used in the intended way. For example, you’re usually allowed to adjust the adapter’s
specific settings, including connection parameters and user name/password, but you
wouldn’t be allowed to change the adapter type from, for instance, Simple Object
Access Protocol (SOAP) to Java Message Service (JMS). The impact of new versions
is, therefore, controllable and predictable. If your integration content has quick

128 128
 3.2 3 Prepackaged
Terms and Conditions of Using SAP Integration Content Content
Integration Catalog

configure terms and conditions, the configure-only approach of configuration will

apply, which we’ll discuss further in Section 3.3.3.
 Content edit
Under this condition, you’re free to modify the content as needed, and thus, this 3
approach provides a lot of flexibility; however, with great power comes great
responsibility, as they say. With content editing open to the user, integration devel-
opers can change the content and fully deviate from the original intention of the
content. For example, an integration developer might decide to add new steps to an
iFlow or change the type of adapter used to communicate with the sender or
receiver system. The changes made to the content by its consumer might make
future updates to the content more difficult. The resulting conflicts will need to be
manually resolved. At the time of this writing, no automatic conflict resolution solu-
tion is available. Therefore, as the consumer, you must consider the impact of the
changes you make to prepackaged content with regard to future updates of the con-
tent package. If your integration content uses the content edit terms and conditions,
the content edit approach of configuration will apply, which we’ll discuss further in
Section 3.3.3.

Note that currently these options are only available to SAP because only SAP publishes
content to SAP Integration Content Catalog.

3.2.2 Notify about Update (Manual Updates)

During the publishing process, the Notify about Update checkbox is available. If this
option is selected, you’ll be notified of any updates made to the integration package.
Notifications are sent automatically to consumers using the integration content. As
shown in Figure 3.3, a green Update Available link accompanies all updatable artifacts
in the prepackaged content. In this way, the consumer is made aware that his content
has an update available and can decide whether to perform the update.

Figure 3.3 Notification of Updated Content in the Catalog

129
129
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Note
This type of notification is also called manual update. With manual update, the cus-
tomer has the option of implementing the update whenever they like or perhaps even
decide not to implement the changes at all. Not updating the content package doesn’t
run the risk that the deployed artifact will stop working. But the customer will obvi-
ously not benefit from the newly added features. Furthermore, reverting back to an
older version if necessary is also possible.

As a consumer, you can update your entire content package using the Update package
button in the top-right corner of the screen shown in Figure 3.4. You can also update
individual objects in a package instead of the entire package by following these steps:
1. Select the content package containing the object you would like to update.
2. Under the Artifacts tab of the package, select the artifacts that you want to update by
selecting the relevant checkboxes. This tab lists all artifacts contained in the package
and indicates which artifacts can be updated with the Update Available link, as
shown previously in Figure 3.3.
3. Click on the Update package button, as shown in Figure 3.4.

Figure 3.4 Updating Selected Items of the Content Package

Note that you can also update a single iFlow by selecting the Update option from the
Actions menu, as shown in Figure 3.5.

Figure 3.5 Updating a Particular Item of the Content Package

Note
If a consumer modifies integration content in the modifiable mode, a notification
won’t be sent when the content is updated by the publisher. The notification is only
sent in the following cases:

130 130
 3.3 3 Consuming
SAP Integration Content Content
Prepackaged Catalog

 The consumed prepackaged content is in configure-only mode.

 The consumed prepackaged content is in modifiable mode but has only been con-
figured and not modified. In other words, the package is being used as if it were a
3
configure-only package.

3.2.3 Automatic Updates

Instead of being notified of an update and being free to choose if/when to perform the
actual update (as discussed in Section 3.2.2), in some cases, the publisher of the prepack-
aged content chooses automatic updating. The main difference is that, for manual
update, the user explicitly must perform the update operation, whereas no user inter-
action is required for automatic updates. The updated content is automatically pushed
to the tenant, and the deployed content is updated in one of two ways:
 Immediate
With this approach, customers have a window of up to 12 hours before the update is
automatically applied to the corresponding deployed artifacts.
 Scheduled
With this approach, the corresponding artifacts are marked with the date when the
automatic update will be applied, for example, the artifact marked with the message
Will be updated on . . ., as shown in Figure 3.6.

Figure 3.6 Artifact with Automatic Update Scheduled

Note
Irrespective of whether the automatic update is immediate or scheduled, the customer
has the option of applying the update before the update is automatically performed.
An automatic update will always be applied, leaving the consumer without control.

Up to this point, you’ve learned the steps involved in finding and consuming prepack-
aged content in general. Let’s now explore some of the content packages in SAP Inte-
gration Content Catalog at the time of this writing.

3.3 Consuming Prepackaged Content

We touched on the role of an integration developer in Section 3.1. In most cases, the
integration developer is a member of the partner or customer organization and has

131
131
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

been tasked with developing well-defined integration scenarios. Figure 3.7 shows the
steps involved in consuming prepackaged content from the catalog.

Import Modify or
Search the
prepackaged configure Deploy
SAP Integration
integration integration content
Content Catalog
content package

Figure 3.7 Process of Consuming Prepackaged Integration Content

We’ll discuss these tasks in more detail in this section with a hands-on, step-by-step
guide.

3.3.1 Searching SAP Integration Content Catalog

A good practice is to search through SAP Integration Content Catalog for existing con-
tent before attempting to develop your own content from scratch. To search the cata-
log, follow these steps:
1. Navigate to your Cloud Integration tenant using the link provided by SAP on your
browser. The link follows the format http://<server>:<port>/itspaces.
2. Select the Discover menu item on the left side of the page to access SAP Integration
Content Catalog, as shown in Figure 3.8.

Figure 3.8 Accessing the SAP Integration Content Catalog Main Page

3. In SAP Integration Content Catalog, you’ll see a list of integration packages to choose
from. By default, only the latest packages are listed. To view all existing packages,
click on the ALL link in the top left of the page shown in Figure 3.9. You’ll then see a
page similar to the page shown in Figure 3.10.
4. A new screen will appear offering a variety of filtering categories. You can apply fil-
ters using categories such as Line of Business, Products, Countries, Supported Plat-
forms, Vendor, Industries, and Keywords, as shown in Figure 3.10. Note that you can
also perform a keyword search on this screen.

132 132
 3.3 3 Consuming
SAP Integration Content Content
Prepackaged Catalog

Figure 3.9 Discover Landing Page

Figure 3.10 Filtering or Searching SAP Integration Content Catalog

The resulting list provides the name, high-level description of the package, published
date, vendor, and version. Additionally, a user rating of the integration content is also
available.
To view details about a particular package, select the package from the list. As a result,
you’ll see a page similar to that shown in Figure 3.11.
This integration content detail page contains the following tabs:
 Overview
Contains the description of the package and scenarios it covers.
 Artifacts
Includes a list of iFlows, data iFlows, and other integration artifacts that make up the
bundle.

133
133
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

 Documents
Includes guides and links to provide more documentation and information about
the integration content to assist the user further. Commonly, integration guides are
included among these documents. An integration guide provides step-by-step
guidelines on how to set up and configure the integration scenario. Note that the
corresponding contacts or components are mentioned in the release notes of the
content. This information is useful if issues with the artifacts arise, and you want to
report the issue to SAP.
 Tags
Provides different metadata to help classify content. The list of metadata includes
industry, line of business, keywords, supported platforms, and so on.
 Ratings
Contains details about consumer ratings as well as the logged-in user’s own ratings.

Figure 3.11 Viewing Details of an Integration Package

The items listed under the Artifacts tab, as shown in Figure 3.12, can be clicked to view
further information. For instance, you can click on an iFlow’s name to display more
details about the iFlow, as shown in Figure 3.13.
After browsing around and finding the integration package that fits your needs, you’re
now ready to further modify and configure it according to your requirements. Note
that whether you can configure or modify the integration package depends on the
mode of the prepackaged content, as we’ll discuss in Section 3.3.3.
In the next section, we’ll show you how to consume the content by copying it into your
customer workspace.

134 134
 3.3 3 Consuming
SAP Integration Content Content
Prepackaged Catalog

Figure 3.12 List of Artifacts in an Integration Package

Figure 3.13 Details of the iFlow: Preproduction Delivery Service

135
135
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

3.3.2 Importing Prepackaged Integration Content

You can copy the content available in SAP Integration Content Catalog into your own
design workspace for further customer-specific configuration and enhancements. You
can use the template contained in the package as the basis upon which to make
changes to suit your specific business requirements. To copy an integration package,
perform the following steps:
1. After selecting the package that you want to copy (in our example, the NL Electronic
VAT Return Statement and EC Sales List integration package), a Copy link will appear
in the top-right corner, as shown in Figure 3.14. Clicking this Copy link enables you to
copy the integration package to your own customer workspace.

Figure 3.14 Copying Templates to Your Own Workspace

2. After performing the copy action, the copied package and its artifacts are displayed
in your own design workspace. Click on the Design menu item (refer to Figure 3.8) to
further enhance the copied content. Figure 3.15 shows that the copied package is now
available in the customer’s workspace, on the left.

Figure 3.15 Design Component with Copied Templates

136 136
 3.3 3 Consuming
SAP Integration Content Content
Prepackaged Catalog

Note
Once you’ve copied a package from the Discover view to the Design view, a subscrip-
tion is created in the background for each artifact contained in the package. Having a 3
subscription means that Cloud Integration knows you’re interested in any changes or
planned updates to the concerned prepackaged integration content.
When anything changes on the package, you’re informed via a tag next to the con-
cerned artifacts. This subject was mentioned earlier in Section 3.3.1, and we’ll revisit
tags in Section 3.5.

3.3.3 Modifying or Configuring the Integration Package

The content copied in the previous step is now ready for configuration. Such configu-
ration steps might include configuring adapter-specific endpoints. Depending on your
requirements, you can also remodel and completely change the content. As mentioned
earlier, there are two approaches to configuring integration packages: content edit and
configure-only. Let’s explore each approach in a bit more detail.

Content Edit Approach

This approach allows you to perform configuration steps to remodel and change the
package content.

Note
The ability to completely remodel and change the content of a copied package can be
restricted by the terms and conditions of the integration package. When the package is
restricted, use the configure-only approach. The subject of terms and conditions was
also discussed in Section 3.2.

The integration package copied to your tenant can be modified and configured to your
own needs by following these steps:
1. Click on the desired package’s name from the list of packages displayed in the
screen, as shown in Figure 3.15.
2. A new page, similar to the page shown earlier in Figure 3.12, will load. The page
should display the full list of objects contained in the integration package. Note that
the artifacts can be a mixture of iFlows, data integration, OData services, and value
mappings. Furthermore, the Documents tab can contain files and URLs.
3. To display an iFlow, click on its name. You’ll then see a detailed view of the flow, as
shown in Figure 3.16.
4. To change an iFlow, click the Edit button in the upper-right corner of the screen.
Note that, when in edit mode, the integration package editor locks the object and
prevents any other user from changing it.

137
137
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Figure 3.16 Details of the iFlow

5. For most iFlows, connectivity details on the sender and receiver side will need to be
changed. Figure 3.17, for instance, shows that the SOAP receiver connection details
can be filled in by selecting the relevant connector and specifying the properties
under the Connection tab.
6. After you’ve made the desired changes, click on the Save button in the top-right cor-
ner of the page, as shown in Figure 3.17. Alternatively, click Save as version to save a
new version of the iFlow. You’ll then be asked to provide a comment for the new ver-
sion. Note that the version number is automatically incremented.
7. After saving your work in the previous step, you can now choose to deploy the iFlow
on the tenant by using the Deploy option (shown previously in Figure 3.16). If you
attempt to deploy without saving, a popup message will warn you that unsaved
changes exist. You’ll also be asked whether you want to save the iFlow and deploy at
the same time.

The iFlow can now be used at runtime to process actual messages. Figure 3.18 shows
how you can download the content of an iFlow.
The content is downloaded to your local machine in an archive file (e.g., ZIP file) con-
taining the entire iFlow project. The iFlow’s project ZIP file can then be imported into
another package or deployed to run on an SAP Process Orchestration server, as
described in Chapter 17 of SAP Process Orchestration: The Comprehensive Guide (SAP
PRESS, 2017).

138 138
 3.3 3 Consuming
SAP Integration Content Content
Prepackaged Catalog

Figure 3.17 Adding Different Items to an Existing iFlow Template

Figure 3.18 Overview of Updated Package

139
139
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

As shown in Figure 3.18, every iFlow contains a version number. After consuming a par-
ticular version of the iFlow, you have the option of reverting to an older version by per-
forming the following steps:
1. Under the Artifacts tab shown in Figure 3.18, click on the Version number of the
iFlow. Note that this step works in design mode only.
2. The next screen displays the history of the various versions of the iFlow, as shown in
Figure 3.19.

Figure 3.19 Reverting to a Different Version in the Version History

3. Hover over the version that you want to revert to, and click on the clock-like icon on
the left side of the Version history screen, as shown in Figure 3.19.
4. A new screen pops up, from which you’ll need to confirm your action by clicking the
OK button.

Now that the consumed prepackaged content is configured to suit your needs, it’s time
to deploy the content and make it available in your tenant’s runtime. We’ll discuss this
next step in Section 3.3.4.

Configure-Only Approach
The configure-only option provides an easy-to-use method of quickly adapting an
iFlow to meet your requirements. You can perform only configuration activities, such
as adding adapter-specific endpoints and assigning values to externalized parameters.
If you want to modify the content of the integration package, such adding an extra step
to the iFlow, you should use the content edit approach discussed earlier.
The following steps are performed when using the configure-only approach:
1. Navigate to your design workspace by selecting the Design page (refer to Figure 3.8).
2. Click on the package’s name (refer to Figure 3.15). The next screen displays a list of
artifacts contained in the package, under the Artifacts tab.
3. Select the Action button on the row corresponding to the iFlow that you want to con-
figure, and then choose Configure from the dropdown menu, as shown in Figure
3.20.

140 140
 3.3 3 Consuming
SAP Integration Content Content
Prepackaged Catalog

Figure 3.20 Accessing the Configure-Only Option

If the iFlow lacks configurable attributes, a warning message pops up, as shown in
Figure 3.21.

Figure 3.21 Warning for Missing Attributes in the Configure-Only Approach

4. If the iFlow does have configurable attributes, configure the details of each tab
shown in Figure 3.22. Notice that, on this screen, only the Sender, Receiver, and More
tabs are displayed, but the Timer tab is also available. All four configuration tabs and
their descriptions are listed in Table 3.1.

Figure 3.22 Configuring the Receiver Connection Details of an iFlow

141
141
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Configuration Tab Description

Timer If the iFlow uses a scheduler (a timer start event), its settings can be
configured under this tab. Possible options include Run once, Schedule
on Day, or Schedule to Recur. We’ll cover how you can use a timer start
event in an iFlow in Chapter 6, Section 6.1.2.

Sender Configure the connectivity details of the sender adapter.

Receiver Configure the connectivity details of the receiver adapter. See the
example shown in Figure 3.22.

More Provide a configuration feature for externalized parameters. Note

that, at the time of this writing, all string fields can be externalized in
all flow steps. Externalized parameters allow you to define variables
and use them in an iFlow. The values of these variables can be
assigned later in the configuration process. Parameters and external-
ization are further discussed in Chapter 4, Section 4.2.

Table 3.1 Available Configuration Tabs for the Configure-Only Approach

5. After you’ve made the desired changes in the previous step, click on the Save button
(shown earlier in Figure 3.22).
6. Deploy the iFlow on the tenant by using the Deploy button (shown earlier in Figure
3.22).

Note
Note that the four tabs listed in Table 3.1 are available after you’ve clicked on the Con-
figure option. However, the tabs are only populated with configurable properties
under the following conditions:
 The presence of a sender adapter in the iFlow (Sender tab)
 The presence of a receiver adapter in the iFlow (Receiver tab)
 The presence of a timer start event (Timer tab)
 When you’ve externalized any string fields in any flow step (More tab)

For instance, when you have an iFlow beginning with a timer start event (i.e., no sender
system is involved), the Sender tab won’t be populated. If nothing has been external-
ized in the entire flow, you’ll receive an error message stating, No attributes available
for quick configuration in the selected artifact.

We’ll explore the subject of externalizing parameters further in Chapter 4, Section 4.2.

142 142
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

3.3.4 Deploy Content

Your iFlow is now configured and ready to be deployed. You can deploy the iFlow by fol-
lowing these steps:
3
1. From within your customer workspace, on the Design page, select the iFlow that you
configured in Section 3.3.3.
2. Click on the Deploy button, shown in the top-right corner of Figure 3.23.

The deployed iFlow is now ready to reliably connect systems with each other through
message exchange. Congratulations—you just learned how to consume prepackaged
integration content! Imagine how much time you would’ve needed to figure out the
mapping requirements and build this entire iFlow from scratch.

Figure 3.23 Deploying an iFlow

Now, let’s explore the wide range of prepackaged integration content available for you
to use in your integration scenarios.

3.4 Prepackaged Content Provided by SAP

Let’s showcase the available content in SAP Integration Content Catalog, which
includes integration scenarios for the most commonly used cloud-based applications
from SAP:
 SAP SuccessFactors
 SAP Cloud for Customer
 SAP Ariba
 SAP Customer Experience
 Content for globalization scenarios

143
143
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

 Content for ELSTER (Elektronische Steuererklärung) integration for German tax

requirements
 Adapters to third-party applications for SAP Integration Suite

For each category, we’ll explore the provided content and specify their use cases in this
section.

3.4.1 Content for SAP SuccessFactors

SAP SuccessFactors is a cloud-based human capital management (HCM) solution that
integrates onboarding, social business and collaboration tools, a learning management
system (LMS), recruiting software, performance management, succession planning,
applicant tracking software, talent management, and HR analytics to deliver business
strategy alignment, team execution, and maximum people performance. SAP has
another HR product called SAP ERP Human Capital Management (SAP ERP HCM),
which provides an integrated set of modules to help an organization manage its peo-
ple. SAP ERP HCM is effectively an on-premise HCM product.
Some customers have opted for a hybrid approach, where SAP ERP HCM (on-premise)
and SAP SuccessFactors (in the cloud) work in tandem. In these cases, customers must
decide which part of the end-to-end HCM process runs on which system. One popular
approach is to use SAP ERP HCM for core HR processes and use SAP SuccessFactors for
one or more talent management processes. With such a division of responsibilities
between two HCM systems, integration plays a critical part in linking and synchroniz-
ing them.
For the sake of illustration, Figure 3.24 shows a common onboarding process between
SAP ERP HCM and SAP SuccessFactors. This process shows a requirement to export an
employee’s prehire data (information about the candidate before they become an
employee) from SAP ERP HCM to SAP SuccessFactors Onboarding. Moreover, when the
process is completed in SAP SuccessFactors Onboarding, you can export the employee
data from SAP SuccessFactors Onboarding back to SAP ERP HCM and create employee
master data. The complete use case is shown in Figure 3.24.

Employee’s prehire data

SAP Employee’s information SAP ERP

SuccessFactors HCM (on-
premise)
Hire confirmation

Figure 3.24 Use Case Integrating SAP SuccessFactors Onboarding and SAP ERP HCM

By integrating and combining the functionalities of these two platforms, you can
achieve a better end-to-end process result. SAP Integration Content Catalog provides a

144 144
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

variety of packages to cover different integration scenarios, including for the use case
shown in Figure 3.24. Refer to SAP Integration Content Catalog for the most up-to-date
list of SAP SuccessFactors–related packages.
To discover all packages related to SAP SuccessFactors, you’ll need to apply a filter on
3
the main page of SAP Integration Content Catalog by selecting any entry with the word
SuccessFactors as the value of the Products dropdown list. This filtering exercise is
shown in Figure 3.25.

Figure 3.25 Filtering SAP SuccessFactors Packages

Most packages are self-explanatory. In addition, you can further explore and consume
their content as already discussed in Section 3.2.

SAP SuccessFactors Adapter

Most iFlows included in this package make use of SAP SuccessFactors adapter for Cloud
Integration. This special adapter was developed to connect solely to SAP Success-
Factors applications. Refer to Chapter 1, Section 1.3.3, to read more about Cloud Integra-
tion’s connectivity options.

3.4.2 Content for SAP Cloud for Customer

SAP Cloud for Customer is SAP’s cloud customer relationship management (CRM) solu-
tion, which brings marketing, sales, commerce, and customer service together.
As a cloud-based CRM system, SAP Cloud for Customer needs to interact with a number
of other systems to ensure that accounts, materials, price conditions, and other master
data are in sync.

145
145
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Currently, SAP Integration Content Catalog provides three main content packages
related to SAP Cloud for Customer. These packages include content that supports the
following use cases:
 SAP Cloud for Customer integration with SAP ERP
 SAP Cloud for Customer integration with SAP CRM
 SAP Cloud for Customer integration with SAP Marketing Cloud

To further illustrate how the integration packages for SAP Cloud for Customer can be
used, let’s dig a bit deeper into a use case for integrating SAP Cloud for Customer with
SAP ERP.

SAP Cloud for Customer Integration with SAP ERP

As mentioned earlier, SAP Cloud for Customer must exchange master and transac-
tional data with SAP ERP. In terms of master data, in most use cases, SAP ERP acts as the
master system. As a result, master data is synchronized one way—from SAP ERP to SAP
Cloud for Customer. In addition, transactional data, such as opportunity, pricing, and
quotes, is also exchanged between these platforms. An overview of the data exchanged
between these two systems is shown in Figure 3.26.

SAP ERP SAP Cloud for Customer

Currency Conv. Rates Currency Conv. Rates

Employee Employee

Sales Org. Hierarchy Sales Org. Hierarchy

Material Product

Customer Material Info Customer Material Info

Account Account

Customer Hierarchy Account Hierarchy

Contact Contact

Functional Location Installation Point

Equipment Registered Product

Measuring Point Measuring Point

Measurement Document Measurement Document

Figure 3.26 Master Data Synchronization between SAP Cloud for Customer and SAP ERP

146 146
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

Through SAP Integration Content Catalog, SAP provides the needed iFlows to synchro-
nize your on-premise SAP ERP and SAP Cloud for Customer systems. The iFlows cover
the scope of business objects shown in Figure 3.26.
3
SOAP Adapter
From a technical perspective, the SOAP adapter is used to integrate Cloud Integration
and SAP Cloud for Customer. The consumer of the integration package needs to per-
form configuration tasks under the Adapter Specific tab of the concerned iFlow, as
explained in Section 3.3.3. Refer to Chapter 1, Section 1.3.3, to read more about Cloud
Integration connectivity options.

To discover SAP Cloud for Customer–related integration packages, you’ll need to apply
a filter on the main page of SAP Integration Content Catalog by selecting the SAP Hybris
Cloud for Customer entry from the Product dropdown list.

3.4.3 Content for Integrating with SAP Customer Experience

SAP Customer Experience is a family of cloud-based solutions that includes the follow-
ing products:
 SAP Commerce Cloud
 SAP Customer Data Cloud
 SAP Sales Cloud
 SAP Service Cloud
 SAP Marketing Cloud

Among this list of products, SAP Sales Cloud and SAP Service Cloud are included under
the umbrella of SAP Cloud for Customer. The integration content for SAP Cloud for Cus-
tomer was already covered in Section 3.4.2. In this section, we’ll explore the content
provided for SAP Commerce Cloud, SAP Marketing Cloud, SAP Subscription Billing, and
SAP Billing and Revenue Innovation Management (formerly SAP Hybris Revenue and
SAP Hybris Billing).

Note
For the most up-to-date information about the current integration packages for SAP
Commerce Cloud, SAP Subscription Billing (or SAP Billing and Revenue Innovation
Management), and SAP Marketing Cloud, refer to the Documents tab within each
package, which generally contains integration guides and various informative docu-
ments. You can also refer to the SAP Community site for more information. Note that
while the billing and revenue functionality was part of the old SAP Hybris suite, this
functionality isn’t part of the new SAP Customer Experience suite.

147
147
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

SAP Commerce Cloud

The integration content for SAP Commerce Cloud/SAP Cloud for Customer enables you
to perform the following activities:
 Synchronize customer data from SAP Commerce Cloud to SAP Cloud for Customer.
 Synchronize customer service ticket data between the two systems to more effi-
ciently connect customers with service or sales agents.

After SAP Commerce Cloud and SAP Cloud for Customer are connected, customer ser-
vice representatives (agents) can provide service through the ticket or directly over the
phone, all while accessing the same storefront as the customer, through the Assisted
Service Module (ASM) for SAP Commerce Cloud for exceptional service and sales assis-
tance on the spot.
At the time of this writing, the SAP Customer Engagement Center Integration with SAP
Commerce integration package is an example package used to synchronize data be-
tween SAP Commerce Cloud and SAP Customer Engagement Center integration. To
illustrate some common use cases, the following business objects are exchanged:
 Customer address replication from SAP Commerce Cloud to SAP Customer Engage-
ment Center
 Customer replication from SAP Commerce Cloud to SAP Customer Engagement
Center
 Basic sales order details replication from SAP Commerce Cloud to SAP Customer
Engagement Center for indexing

SAP Subscription Billing and SAP Billing and Revenue Innovation Management
At the time of this writing, the Integration with SAP Subscription Billing integration
package is an example package that provides capabilities for processing bills originat-
ing from SAP Subscription Billing in SAP S/4HANA for billing and revenue innovation
management. Common use cases include the following:
 Extracting billing documents from SAP Subscription Billing to SAP S/4HANA
 Sending back customer IDs from SAP S/4HANA to SAP Subscription Billing when
customers are created or updated
 Extracting customers from SAP Subscription Billing and then replicating them to
SAP S/4HANA
 Replicating customers from SAP S/4HANA to SAP Subscription Billing

SAP Marketing Cloud

At the time of this writing, the available integration content covers many integration
scenarios for SAP Marketing Cloud, including the following:

148 148
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

 Master data and basic replication

The accounts, contacts, individual customers, leads activities, and opportunities are
replicated from SAP Cloud for Customer to SAP Marketing Cloud.
 Call center scenarios 3
This scenario creates a call center campaign in SAP Marketing Cloud and executes
the campaign in SAP Cloud for Customer.
 Lead management scenarios
Any lead that is converted into an opportunity further creates an opportunity inter-
action in SAP Marketing Cloud. These leads and opportunities in SAP Cloud for Cus-
tomer also contain information about the corresponding campaigns from SAP
Marketing Cloud.

Furthermore, several integration packages cover a number of use cases with SAP Mar-
keting:
 SAP S/4HANA Enterprise Management on-premise – SAP Marketing Cloud integra-
tion
 SAP Marketing Cloud – SAP Customer Relationship Management (SAP CRM) integra-
tion
 SAP Cloud for Customer – SAP Marketing integration
 SAP Marketing Cloud – SAP Customer Attribution integration
 SAP Marketing Cloud – SAP ERP order and business partner integration
 SAP Marketing Cloud – Twitter integration
 SAP Marketing Cloud – Content Management System integration
 SAP Marketing – Google AdWords Paid Search integration
 SAP Marketing Cloud – Twitter integration admin
 SAP Marketing Cloud – Facebook integration admin
 SAP Marketing Cloud – Facebook integration
 SAP Marketing – Google Analytics integration

3.4.4 Content for Integrating with SAP Business Network

SAP Business Network is a cloud-based procurement solution that allows you to locate
new suppliers, streamline transaction processes, and save costs. One of the largest trad-
ing partner communities, SAP Business Network provides connectivity and online ser-
vices to organizations engaged in business-to-business (B2B) e-commerce.
With SAP Business Network, buyers and suppliers can conduct business with each
other over the internet and access each other’s services. SAP Business Network con-
tains additional functionalities such as directory services, reporting tools, supplier
tools, payment processing, and sourcing.

149
149
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

To illustrate a common use case, customers can create purchase orders, goods receipts,
invoices, and so on through SAP Business Network and have these transactions syn-
chronized back to their own (on-premise) SAP Business Suite operational purchasing or
supplier-side processes. An overview of these common use cases between SAP ERP
Materials Management (MM) and SAP Supplier Relationship Management (SAP SRM) is
shown in Figure 3.27.

Purchase orders and order changes

SAP ERP MM
SAP Ariba or
Order confirmation, ASN, invoices SAP SRM

Figure 3.27 Integration Use Cases between SAP Ariba and SAP ERP or SAP SRM

Currently, one package is available to cover the need for integrating SAP Business Net-
work with your existing SAP ERP using Cloud Integration. This content package inte-
grates and automates your SAP Business Suite operational purchasing processes or
supplier-side processes with SAP Business Network.
For buyers, the scope of this mediated connection based on the SAP Business Network
integration for SAP Business Suite Add-On 1.0 includes the following capabilities:
 Purchase order and invoice automation for MM and SAP SRM classic
 Discount management integration (optional)

The scope supports selected aspects of the following procure-to-pay end-to-end busi-
ness scenarios:
 Self-service and indirect procurement
 Direct procurement
 Service procurement
 Invoice management
 Collaborative Supply Chain 1.0 with schedule agreement release order processing

For suppliers, the scope of this mediated connection, based on the SAP Business Net-
work integration with SAP Business Suite Add-On 1.0, includes the following:
 Sales order and billing integration with SAP Business Network for SAP ERP Sales and
Distribution (SAP SD)

Note
From a technical perspective, the SOAP adapter is used to integrate Cloud Integration
with SAP Ariba. The consumer of the integration package must perform several

150 150
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

configuration tasks under the Adapter Specific tab of the concerned iFlow. Refer to
Chapter 1, Section 1.3.3, to read more about the Cloud Integration connectivity options.

3
To discover SAP Ariba–related integration packages, you’ll need to apply a filter on the
main page of SAP Integration Content Catalog by selecting SAP Business Network with
SAP Business Suite from the Product dropdown list.

3.4.5 Content for Globalization Scenarios

Recently, many government agencies have moved from traditional paper-based docu-
ments to digital or electronic documents. As such, businesses dealing with these gov-
ernment agencies (e.g., the tax office) must quickly adapt their internal processes to
comply.
For multinational companies that must, for instance, report their taxes in many coun-
tries, one challenge will be sending documents to the necessary tax offices, all in differ-
ent countries with different formats and standards, from the same source application
(SAP ERP system). Another aspect to consider, in most cases, is that the transmission of
these government-related documents requires a high level of security.
The mapping of the source application’s messages to the required government for-
mats, and the transmission of these message is a classic integration scenario. The need
to transfer electronic documents to government agencies around the world is a use
case Cloud Integration covers with its integration content for globalization. This con-
tent is also known as the eDocument Framework.
The eDocument Framework provides a generic approach for creating, processing, and
managing electronic documents. The framework supports handling country-specific
requirements for electronic documents with regard to the format of messages, security
requirements, and processing steps in end-to-end integration scenarios. The source
data for the documents may originate in any application that implements the web ser-
vices available in the iFlows. At the time of this writing, a number of integration pack-
ages are provided in Cloud Integration to support the eDocument Framework for Chile,
Italy, Spain, Peru, The Netherlands, Great Britain, Colombia, Germany, India, Mexico,
the United States, and Hungary.
With these packages, you won’t need to spend time trying to figure out how to perform
mappings or finding which security levels are required to comply with government-
specific electronic document formats. You can simply reuse the provided integration
content to reduce implementation time and costs.
To find a particular eDocument Framework package for a specific country, you’ll need
to apply a filter on the main SAP Integration Content Catalog page by selecting a coun-
try (e.g., Netherlands) from the Country dropdown list.

151
151
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

3.4.6 Content for ELSTER Integration

ELSTER (i.e., electronic tax declaration) is a German online tax office system designed
by the Federal Central Tax Office (Bundeszentralamt für Steuern) to enable anyone to
submit their tax returns online.
A number of businesses are also obliged to use ELSTER to submit their monthly
employee tax statements and value-added tax (VAT) returns. As discussed in Section
3.4.5, submitting documents to governmental institutions electronically is more effec-
tive than traditional documents and is a growing trend around the world. ELSTER is the
German tax equivalent for this growing electronic document trend.
Because most businesses typically use an ERP system (e.g., SAP) to maintain sales infor-
mation as well as HR data, automatically retrieving the relevant data from the ERP sys-
tem and submitting this data to the German tax authorities makes sense. You’ll need to
establish an integration from the ERP system on one side and the tax authority’s sys-
tem on the other. Given that many businesses use SAP both for finance- and HR-related
processes, Cloud Integration provides standard content to help SAP customers easily
integrate with the German tax authorities and therefore save costs. Cloud Integration
provides integration content that cover the following areas:
 Sending HR tax data
 Sending finance tax data
 Sending tax data to the German tax office

You can find all ELSTER-relevant packages in Cloud Integration on the Discover page by
selecting ELSTER in the Products filter, as shown in Figure 3.28.

Figure 3.28 Integration Content Packages for ELSTER

152 152
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

We’ll discuss the two packages shown in Figure 3.28 further in this section. Note that all
these iFlows make use of the ELSTER adapter, mentioned in Chapter 1, which was spe-
cially developed for this purpose.
3
Note
To establish a connection between Cloud Integration and the tax agency’s servers, you
must obtain several certificates and then deploy these certificates to the Cloud Integra-
tion tenant.

Sending HR Tax Data

The first iFlow shown in Figure 3.28 is for exchanging HR notifications with the tax
authority in Germany. To exchange tax notifications, ELSTER Rich Client (ERiC) compo-
nents are used for signing, encryption, and transport.
For the transfer, the integration package applies specific requirements for message
security, which are set by the German authorities. Therefore, the integration package
uses the mandatory ERiC Libraries. The functionality is valid for German customers
only. As a prerequisite, at a minimum, you must have an SAP ERP 6.00 on-premise sys-
tem and Employee Central Payroll (ECP). As shown in Figure 3.29, this flow uses the
ELSTER adapter to send data to the tax authority.

Figure 3.29 Sending Data to the Tax Authority Using the ELSTER Adapter

153
153
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Transferring Tax Notifications to the German Tax Office

This integration package enables you to transfer German tax-specific notifications to
the tax authority. To transfer this data, the related iFlow applies specific requirements
for message-level security, which are set by German authorities using ELSTER. The
package uses a mandatory ERiC (Elster Rich Client Development Toolkit) Library.
This package includes a single iFlow for exchanging finance notifications with the tax
German tax office using ELSTER. As shown in Figure 3.30, this flow doesn’t use the
ELSTER adapter to send data to the tax authority; instead, a plain HTTP adapter is used
(with HTTPS as a transport protocol).

Figure 3.30 Sending Data to the Tax Authority Using the HTTP Adapter

3.4.7 Content for Salesforce Integration

Salesforce is a cloud-based customer relationship management (CRM) solution that
provides applications focused on sales, customer service, marketing automation, e-
commerce, analytics, and application development.
Several businesses use both SAP ERP and Salesforce for their day-to-day activities. In
such cases, the business processes span across SAP and Salesforce. To ensure the good
execution of these processes, integration needs to be developed to exchange and syn-
chronize data between SAP S/4HANA, SAP S/4HANA Cloud, or SAP ERP, and Salesforce.
There are some packages in SAP Integration Content Catalog that can be reused for this
purpose. At the time of publication, the following packages are available:
 SAP ERP Integration with Salesforce
 SAP S/4HANA Cloud Integration with Salesforce
 SAP S/4HANA Integration with Salesforce

154 154
 3.4 3 SAP Integration
Prepackaged ContentContent
ProvidedCatalog
by SAP

Example packages are shown in Figure 3.31.

Figure 3.31 Integration Content Packages for Integrating with Salesforce.

Let’s look into these packages to get an idea of the included use cases.

SAP ERP Integration with Salesforce

This package supports the integration of some business processes between your Sales-
force and your SAP ERP applications. The included iFlows can be used as a starting point
to accelerate your integration journey between SAP ERP and Salesforce. It supports the
following business transactions:
 Receive Product Availability from SAP ERP
 Receive Sales Order History from SAP ERP
 Replicate Account from SAP ERP to Salesforce
 Replicate Product from SAP ERP to Salesforce
 Replicate Sales Contract from Salesforce to SAP ERP
 Replicate Sales Order from Salesforce to SAP ERP
 Replicate Sales Order from SAP ERP to Salesforce
 Replicate Sales Prices from SAP ERP to Salesforce
 Update Account from Salesforce to SAP ERP

SAP S/4HANA Cloud Integration with Salesforce

This package supports the integration of some business processes between your Sales-
force and your SAP S/4HANA Cloud applications. The included iFlows can be used as a
starting point to accelerate your integration journey between SAP S/4HANA Cloud and
Salesforce. It supports the following business transactions:
 Replicate sales orders from Salesforce to SAP S/4HANA Cloud
 Replicate sales contract from Salesforce to SAP S/4HANA Cloud
 Receive sales order history from SAP S/4HANA Cloud

155
155
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

 Update account from Salesforce to SAP S/4HANA Cloud

 Receive sales pricing from SAP S/4HANA Cloud
 Receive availability information from SAP S/4HANA Cloud
 Replicate sales orders from SAP S/4HANA Cloud to Salesforce
 Replicate account from SAP S/4HANA Cloud to Salesforce
 Replicate product master data from SAP S/4HANA Cloud to Salesforce

SAP S/4HANA Integration with Salesforce

This package supports the integration of some business processes between your Sales-
force and your SAP S/4HANA applications. The included iFlows can be used as a starting
point to accelerate your integration journey between SAP S/4HANA and Salesforce. It
supports the following business transactions:
 Replicate sales orders from Salesforce to SAP S/4HANA
 Replicate sales contract from Salesforce to SAP S/4HANA
 Receive sales order history from SAP S/4HANA
 Update account from Salesforce to SAP S/4HANA
 Receive sales pricing from SAP S/4HANA
 Receive availability information from SAP S/4HANA
 Replicate sales orders from SAP S/4HANA to Salesforce
 Replicate account from SAP S/4HANA to Salesforce
 Replicate product master data from SAP S/4HANA to Salesforce

3.5 Creating Your Own Content Package

In the previous section, you learned about the prepackaged content delivered by SAP in
SAP Integration Content Catalog. In this section, we’ll cover how you can create your
own content. If the existing prepackaged content doesn’t meet your business needs,
you can create your own package that can be used and reused specifically by team
members within your organization.
The first step to publishing your own content is to create the desired integration con-
tent. The process of creating your own content was discussed when creating your first
iFlow in Chapter 2. Furthermore, Chapter 4 will walk you through the process of creat-
ing different integration content artifacts. Therefore, we won’t go into the develop-
ment details in this section and instead focus on creating an integration package.
To create an integration package, follow these steps:
1. Open the Design page (refer to Figure 3.8).
2. Select the Create option to create an integration package, as shown in Figure 3.32.

156 156
 3.5 3 SAP Integration
Creating Content Package
Your Own Content Catalog

Figure 3.32 Creating an Integration Package

3. On the next screen, specify the name for the new integration package. Additional
metadata details, such as the version, owner, mode, description, tags, products,
industries, line of business, country, and keywords, can be provided. Some of this
metadata is shown in Figure 3.33. You can maintain this metadata in several tabs
such as the Overview and Tags tabs. Keep in mind that this metadata is important to
better classify content and allow consumers to find content easily. Therefore, pro-
viding as much detail as possible is important.

Figure 3.33 Specifying Details in the New Integration Package

4. Save the package by clicking the Save button, as shown in Figure 3.33.
5. Under the Artifacts tab, click Add and choose an artifact of type Integration Flow,
REST API, Message Mapping, SOAP API, Value Mapping, OData API, Script Collection,
or Integration Adapter to add it to the integration package, as shown in Figure 3.34.
6. Artifacts can be added to the newly created package by creating them from scratch if
they don’t already exist. Alternatively, existing artifacts can also be imported. These
two options are made possible using the Create or Upload radio buttons, as shown in
Figure 3.35.

157
157
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Figure 3.34 Adding Artifacts to an Integration Package

Figure 3.35 Creating or Importing a Process Integration Artifact

7. To provide documentation for the integration package, click on Add under the Doc-
uments tab, as shown in Figure 3.36. Documents of type File or URL can be added to
this tab.

After packaging and saving the integration content, this integration package will be
available in your own design space and can therefore be used by team members of your
organization.

158 158
 3.6 3 SAP Integration
Adapters to Third-Party Applications Content Catalog
for SAP Integration Suite

Figure 3.36 Adding a File or URL to a Content Package

Note
A content package is automatically locked against modification from other users when
someone is in the process of editing the package. The package is only released for mod-
ification after the content package has been saved. If the session times out, or if the
browser closes while you’re still working on your integration package, the content
package will remain locked until saved, canceled, or deleted by the lock owner.

Currently, only SAP is allowed to publish data to SAP Integration Content Catalog, so
packages created by customers or partners are for internal use only and can’t be
directly leveraged by other customers. Different SAP Partners have listed their prepack-
aged integration content on SAP Integration Content Catalog, but you’ll need to con-
tact the specific SAP Partner to purchase and obtain an archive of the package.

3.6 Adapters to Third-Party Applications for SAP Integration Suite

Most customers may find themselves needing to integrate to non-SAP cloud-based
applications. Cloud Integration has various adapters for third-party applications. At the
time of publication, the following adapters are included:
 Salesforce Adapter for SAP Integration Suite
 Microsoft Dynamics CRM Adapter for SAP Integration Suite
 Amazon Web Services Adapter for SAP Integration Suite
 Workday Adapter for SAP Integration Suite
 ServiceNow Adapter for SAP Integration Suite
 Splunk Adapter for SAP Integration Suite
 Azure Adapter for SAP Integration Suite

159
159
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

 SugarCRM Adapter for SAP Integration Suite

 Slack Adapter for SAP Integration Suite

Note that depending on the type of Cloud Integration license used by the customer,
some of these adapters might not be included or might need to be purchased sepa-
rately.
Furthermore, this list is growing rapidly and provides an alternative to Open Connec-
tors (discussed in Chapter 9). These adapters can also be found in SAP Integration Con-
tent Catalog. To illustrate its usage, we'll use the Salesforce Adapter for SAP Integration
Suite.
As shown in Figure 3.37, this package contains details about the functionality and capa-
bilities of the Salesforce adapter. It also describes how to download the adapter and
deploy it to your Cloud Integration content. The package contains a link that redirects
the user to SAP Service Marketplace (see Figure 3.38).

Figure 3.37 Package for the Salesforce Adapter for SAP Integration Suite

160 160
 3.6 3 SAP Integration
Adapters to Third-Party Applications Content Catalog
for SAP Integration Suite

Figure 3.38 SAP Service Marketplace Page to Download Adapters

After downloading the adapter’s ZIP file, the adapter files and various documents that
describe the installation steps can be extracted. Figure 3.39 shows the extracted adapter
file name salesforce.esa. This file can be imported into your Integration package as one
of the artifacts.

Figure 3.39 The Adapter File to Be Installed in Cloud Integration

The following lists the steps to be to install the adapter:

1. Open an integration package in Cloud Integration.
2. Under the Artifacts tab, click Add, and choose an artifact of type Data Integration to
add the adapter to the integration package, as shown in Figure 3.40.
3. Navigate to the location where the adapter file was extracted on your local system,
and select the file named salesforce.esa.
4. After the adapter has been added to Cloud Integration, it becomes available to be
used by any iFlow. It’s important, however, to deploy the adapter before it can be
used in runtime. For that, select the Deploy option, as shown in Figure 3.41, before
the adapter can be used in runtime.

After a successful installation and deployment of the adapter, you can use it in any of
your own iFlows or any integration content related to Salesforce. These integration
packages can also be found in SAP Integration Content Catalog, as we discussed in Sec-
tion 3.4.7.

161
161
3 SAP Integration Content Catalog 3 SAP Integration Content Catalog

Figure 3.40 Adding an Adapter to Cloud Integration

Figure 3.41 Deploy the Salesforce Adapter to Cloud Integration

3.7 Summary
In this chapter, we introduced you to the capabilities and features of SAP Integration
Content Catalog in Cloud Integration. A systematic guide was used to demonstrate how
to consume the contents of the catalog. You also learned about how terms and condi-
tions can affect and restrict the way prepackaged content is consumed.
This chapter then explored the prepackaged content that SAP delivers in SAP Integra-
tion Content Catalog to speed up implementation time and save costs related to per-
forming integration with SAP’s most-used cloud-based applications. SAP Integration
Content Catalog is expected to grow and have new packages added on a regular basis.
Therefore, be sure to first check SAP Integration Content Catalog before developing
your own integration scenarios from scratch to save time and costs.
In the next chapter, we’ll further explore how Cloud Integration empowers developers
to create their own basic integrations when prepackaged content won’t suffice.

162 162
 Bilay, Singh, Singh, Gutsche, Krimmel

Cloud Integration
with SAP Integration
Suite
The Comprehensive Guide

■ Your complete guide to Cloud

Integration in SAP Integration Suite
■ Model synchronous and asynchro-
nous integration scenarios
■ Monitor, maintain, secure, and
enhance integration flows

www.sap-press.com/5760

We hope you have enjoyed this reading sample. You may

recommend or pass it on to others, but only in its entirety,
including all pages. This reading sample and all its parts
are protected by copyright law. All usage and exploitation
rights are reserved by the author and the publisher.

John Mutumba Bilay, Shashank Singh, and Swati Singh are enterprise integra-
tion architects at Rojo Consultancy B.V. with more than 30 years of combined
experience. Dr. Peter Gutsche is a technical writer at SAP. Mandy Krimmel is a
product owner of cloud integration components at SAP.

ISBN 978-1-4932-2471-5 • 900 pages • 06/2024

E-book: $84.99 • Print book: $89.95 • Bundle: $99.99