Title Goes Here and Here and Here

Event Brokering Using SAP Cloud Platform Enterprise Messaging Karsten Strothmann, SAP SE December 5th, 2019

PUBLIC Disclaimer

▪ The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to develop or release any functionality mentioned therein. ▪ This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross negligence. ▪ All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

SAP Cloud Platform Enterprise Messaging

Event-Driven architectures with SAP

How to event enable SAP Backends

Selected Event-Driven Use Cases

Short Demo

Key takeaways

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3 SAP Cloud Platform Enterprise Messaging Hybrid Integration Platform Enterprise Integration Suite for hybrid and heterogenous environments

API Business Hub Out-of-the-box Integration for Intelligent Enterprise Suite as packaged integrations | Open APIs for extensions and Cloud integrations | Support for Partner Integration packages

Cloud Integration Integration Advisor Data Intelligence Open Connectors API Management ▪ A2A, B2B, B2G integrations ▪ Interface Management and ▪ Data ingestion, preparation ▪ Pre-built connectors to ▪ Apply API security best ▪ Integration flow deployment Mapping & Governance non-SAP SaaS apps practices and govern to PI/PO ▪ Runtime artifact generations ▪ Complex data orchestration ▪ Integration with LOBs, e. g. access to APIs. ▪ Hybrid integration via Cloud for CPI, PI/PO & pipelining Marketing Cloud, Analytics ▪ Developer engagement

Connectivity, PI/PO, DS Cloud, Data Hub and I/O and API Monetization.

Integration Suite SAP Cloud Platform SAP

Enterprise Messaging ▪ Build extensible integration for event-based use cases ▪ Send, consume and react to business changes ▪ Events across hybrid landscapes

Process Integration and Orchestration Data Integration and Orchestration Applications Non-SAP Cloud Applications ▪ A2A ▪ Data Lakes, Integration Databases, SAP ▪ B2B & B2G Data services AIF Integration ▪ Information and more Cloud SAP Process SAP Management and … and Connectivity Orchestration Data Hub Governance more …

Fully-managed cloud service for enabling applications to communicate asynchronously through messages and events.

Seamless connectivity Reliable communication Non-blocking communication Event enablement

• Connect your applications and ▪ Messaging middleware ▪ Asynchronous message patterns ▪ Transports events (type of services seamlessly using decouples communication provide elasticity meaning message) from event source to standard protocols (MQTT, AMQP between senders and receivers unexpected peaks in data traffic the Cloud for seamless 1.0, REST) for greater scalability. can be handled efficiently. integration of hybrid landscapes. • APIs (Java JMS, Node.js) ▪ Choose from different Quality of ▪ Build responsive applications and Service levels to ensure extensions that can react to • Exchange patterns (e.g. pub/sub, messages are delivered reliably. events without disrupting core point-to-point, request/reply) business systems.

✓Heterogeneous integration: connect and integrate all kinds of different clients. ✓Fire and forget: message broker delivers messages to consumers so applications can concentrate on their core competencies.

✓Scalability: decouples communication between consumers and producers to handle peak loads (e.g. rush hour).

✓Buffering: message broker buffers data during times of high load and when consumers are offline, which means no loss of data.

✓Flexibility/agility: loose coupling enables you to switch seamlessly between architectures if environment changes.

SAP Cloud Platform Enterprise Messaging

Publish Subscribe

Events Events

• Asynchronous, non-blocking, communication Digital core publishers: Subscribers: • Standard protocols (AMQP 1.0, Webhook, REST, MQTT) • SAP e.g. • Cloud-native extension • SAP S/4HANA • Libraries (Java JMS, Node.js) applications

• SAP SuccessFactors • Exchange patterns (pub/sub, point-to-point, request/reply)

• SAP C/4HANA

• Non SAP

▪ An event is a significant change in state (of an object in an enterprise system)

▪ Event notifications can be sent from the ▪ cloudevents is a specification for system in which the event occurred to describing event data in a common way inform other systems, microservices, and applications of the change. ▪ SAP, Google, Microsoft … support cloudevents

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11 Event-Driven Architectures in Nature Event A significant change of status in a spider‘s web Event A significant change of status in a spider‘s web

Event Messaging Consumer Broker Listening for and Spider‘s web passes reacting to events on events via vibrations

System SAP Cloud Platform

Change (event) Event Message Business Extension / Object Integration

Call API for event details

Highly decoupled, single-purpose event processing components that asynchronously receive and process events.

Senders of events are not aware of event receivers.

Defining elements Benefits

▪ Distributed asynchronous architecture ▪ Decouples communication pattern used to produce highly scalable applications. ▪ Removes idle downtimes

▪ Made up of highly decoupled, single- ▪ Enables responsive applications purpose event processing components that react to events in other that asynchronously receive and process systems/applications events. ▪ Permits events to trigger functions ▪ A key element of event notification is that (as a service) in response to execute the source system doesn't really care much defined business logic about the response. ▪ Facilitates pay-per-use consumption costs by removing “always on”

Real-Time Event Information Event-Driven Architectures

Use Case Inform all interested apps/services of changes, Distributed and Flexible Architectures Isolation Resilience updates, and additions to data in underlying processes Description An event, a change of state, is communicated to all Event processing engines and Isolate event publisher Loose coupling leads to higher interested parties. downstream event-driven activities can from other components by resilience since components, flexibly change over time allowing for limiting access channels specifically event publisher, do extremely loose coupling and a highly to events for information not block and can operate distributed landscape. and clearly defined APIs independently from each other in for access. case of a failure of a component

Advantages • Events are communicated as they happen (real-time) • Supports highly distributed • API calls only when • Systems remain reactive architectures needed (after relevant • Components still remain autonomous event received) • Higher resilience • Event publisher does not need to • Clearly separates / • Interested parties can listen to events in different know about architecture or who is isolates components networks listening to events • Is highly scalable

• Is non-blocking for event publisher (fire and forget) • Provides great flexibility

• Event publisher and event processing engine can work • Allows for a completely new at their own speed development paradigm

• Enables greater responsiveness

Example Project Car Production Updates – TechEd 2018 Keynote Cache data in the Cloud – Chemical Restrict backend access – Protect backend – Airline Company CP Mission

SAP S/4HANA Cloud + S/4 SAP SuccessFactors On Premise1

A number of business objects have been event- SuccessFactors Intelligent Service events can be enabled with more to come. Can be used out-of- enabled for Enterprise Messaging following this the-box. blog How to use SAP Enterprise Messaging as an event bus for SuccessFactors

1 Planned innovation

Make EM Instance ready for Create S/4 Communication Maintain Event Topics for a Queue Subscription to the Eventing - Service Key with System, User and Arrangement Channel Event Topic Pattern clientID, clientsecret and URI 1 2 3

SAP S/4HANA SAP Cloud Platform

Change

Business Topic Consumer A Event Channel Object 2 3 Communication Queue Arrangement 1 Communication SAP Cloud Platform Consumer B System & User Enterprise Messaging

Make EM Instance ready for Expose Intelligent Services Queue Subscription to the Eventing - Service Key with Enable Intelligent Services Events in Admin Center Event Topic Pattern clientID, clientsecret and URI

SAP SuccessFactors SAP Cloud Platform

REST Topic Intelligent Services Gateway Consumer A

Queue

SAP Cloud Platform Consumer B Enterprise Messaging

© 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 19 Selected Use Cases TechEd 2019 Hands-On Exercise: Integration using Event Pattern Business Partner Replication from S/4Hana Cloud to Slack and HubSpot

Third-Party Application

HubSpot Neo Environment

Third-Party Application Open Cloud Integration Connectors Subscriber Slack HTTPS

ODATA SAP Cloud Applications Cloud Foundry Environment

MQTT(ws) Publisher Sales Rep Application Client SAP Enterprise Messaging (Event Hub)

Corporate Identity Provider

1 2. Generates event BusinessPartner.Created 3 2 3. Event sent using Enterprise Messaging to extension application where it triggers 8 short-lasting function.

4. Function extracts BusinessPartnerID and 4 EmployeeID from event.

5. Uses API call to retrieve employee‘s name from SAP S/4HANA. 7 6 5 6. Calls Consent Repository using OData service to ascertain permission to share data.

7. Calls Skills Management to retrieve skills.

8. Data retrieved is published to Slack Channel using Open Connectors. © 2019 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 22 SAP S/4HANA Cloud & Cloud Platform Mission Example App

Extension application on SAP Cloud Platform to react to changes in S/4 BusinessPartner BO

SAP Enterprise Messaging

• Is SAP’s Messaging as a Service and highly scalable

• Supports extensible event-driven integrations

• Is available as Message broker standalone or as part of SAP offerings for the Intelligent Enterprise like the Integration Suite.

Event Bus:

▪ SAP Community: https://community.sap.com/topics/enterprise-messaging

▪ Blog: https://blogs.sap.com/2019/01/17/sap-cloud-platform-enterprise-messaging-as-an- eventbus-for-successfactors/

Extensibility:

▪ SAP Help Portal: ▪ Extending SAP Solutions ▪ Extending SAP SuccessFactors

Karsten Strothmann Product Management SAP Cloud Platform Core