openSAP Modernize Integration with SAP

Integration Suite

Exercise

Week 3: API and Event-Based Integration

SAP Integration Suite, advanced event mesh

PUBLIC
This guide will walk you through some small exercises to give you a first look at SAP Integration Suite,
advanced event mesh.

SAP Integration Suite, advanced event mesh

SAP Integration Suite, advanced event mesh is a fully managed event streaming and management
service that enables enterprise-wide and enterprise-grade event-driven architecture.
AEM offers it all: performance, reliability, security and governance. It scales to very large use cases
– and very means very in this case. On top, it offers sophisticated features as a market leading best of
breed broker.

SAP Integration Suite, advanced event mesh offers deployment options across different hyperscalers
and in private cloud environments. It can be configured to form a distributed mesh of event brokers
deployed across environments in private or public clouds. A full purpose set of eventing services
including event streaming, event management and monitoring is provided and on top advanced
features like dynamic message routing and fine-grained filtering.

2
Overview and Description of Hands-On Exercises
These exercises allow you to get a quick first impression of SAP Integration Suite, advanced event mesh.
You will be able to experience selected features SAP Integration Suite, advanced event mesh.
Your user has not been assigned with a full admin role and therefore what you can do is slightly limited. You
can do much more with a full admin role, obviously. Spinning up brokers or deleting brokers, for example, is
not possible. Since share the environment with a lot of participants, this limitation is unfortunately needed.
You will be able to:
• Explore SAP Integration Suite, advanced event mesh and some of its main features.
• Simulate how an event mesh works.
• See the advantages of a mesh of event brokers over a single event broker.
Features touched include:
• SAP Integration Suite, advanced event mesh queues
• SAP Integration Suite, advanced event mesh topics and queue subscription
• SAP Integration Suite, advanced event mesh Try Me! Tool

Requirements
• Understanding the basics of event-driven architectures, namely events, queues, topics, event
subscriptions would be helpful.
• You would be able to execute the exercises without prior experience by just following the
descriptions. For taking value out of the chance to explore Advanced Event Mesh some experience
with event-driven architectures is recommended.

Additional Background Information

A lot of material to get up to speed with SAP Integration Suite, advanced event mesh is
available.
• Videos
o Discover Event-driven Integrations
• Blogs
o SAPs Event-Driven Ecosystem
o Advanced Event Mesh
o SAP Event Mesh and Advanced Event Mesh
• Documentation
o Help

User Data and Passwords

Hint: Please make sure that you use the Incognito Mode of your browser.

3
To log into Advanced Event Mesh, use one of the email addresses provided below as a username –
pick one randomly. The password is the same for all users.
We would kindly ask not to change any user settings or passwords so that other users can take
advantage of this exercise as well.
Keep in mind that users are shared. So please be mindful in respect to the artifacts you create, and
ideally clean up after finishing your session.

USERS (pick one randomly):

[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

PASSWORD: openSAP!

Link to AEM (from Incognito Mode of Browser):

https://eu10.console.pubsub.em.services.cloud.sap/login?zone-id=908a280d-c2f1-4d2b-b003-de94ffc5a4ee

Exercise 1: First Steps in Advanced Event Mesh

After completing these steps you will have familiarized yourself with AEM.

Exercise 1.1 - Log into Advanced Event Mesh and explore

1. Log into Advanced Event Mesh

4
Link: https://eu10.console.pubsub.em.services.cloud.sap/login?zone-id=908a280d-c2f1-4d2b-b003-
de94ffc5a4ee

User: opensap_handson_**@education.cloud.sap (replace with the user you have picked)

Password: openSAP!

2. Explore Advanced Event Mesh

Check out the different areas in the Advanced Event Mesh cockpit, representing the different categories of
services AEM offers.

Again, note that some important areas are not included with your role like for example Mesh Manager
features.

What you see below is what an administrator user would see, with some explanations.

5
• Event Streaming: Mission Control makes it easy to deploy event brokers, create event meshes, and
optimize and monitor the health/performance of an event-driven system. Mission Control is a section
in the Cloud Console that permits you to access event brokers, visualize and manage your event
broker services, and visualize and design event meshes. Mission Control has a Cluster Manager and
Mesh Manager that permits you to create event broker services and manage your event mesh.
o Cluster Manager: event broker services are made available via Cluster Manager. Each
event broker service consists of event brokers configured in a High-Availability (HA) setup.
o Mesh Manager: use Mesh Manager to connect multiple event broker services that span
different data centers to create an event mesh. An event mesh is an architectural layer that
allows events from one application to be dynamically routed and received by any other
application no matter where these applications are deployed (no cloud, private cloud, public
cloud). This layer is composed by a network of event broker services. Event broker services
are a modern form of messaging middleware, which are designed to move events across the
distributed enterprise.

• Event Management: Event Portal provides event management services. This subscribed service
provides powerful tools to create, design, share, and manage various aspects of an EDA based on
event brokers or other streaming technologies (such as Kafka).

• Event Monitoring and Insights: With Insights, we provide curated dashboards, easy-to-understand
visualizations based on historical and real-time metrics, and timely notifications about your event
broker services. This advanced information allows you to identify problems before they occur and
helps you to better manage your services as your EDA scales. You can work with SAP to configure
your monitoring to meet your needs. For advanced monitoring requirements, there's a single entry
point to build custom visualizations to meet your organization's requirements. Coupled with
visualizations is a notification email framework that alerts you when key metrics fall outside of your
established thresholds. These notifications allow you to monitor what's occurring and correct
developing issues before they impact or degrade your EDA. You can configure these notifications to
integrate with your existing notification and logging systems.

6
 This is what you see with your more limited role:

You do have access to:

• Cluster Manager
• Mesh Manager
• Some features of Event Portal
• Event Insights, no Data Dog access though

3. Click on Cluster Manager

Hint: if you don't see any broker, please uncheck Only show my services

7
4. Select a Broker (clicking on the tile)
5. You should see the broker status screen.

6. Click on View Mesh Details to see an overview of the event mesh that your broker is part of. Check
on the details of the mesh.

7. Go back to broker status screen, either by just clicking Back on your browser or by taking the path
you had taken before

8
Exercise 1.2 - Create a queue in Advanced Event Mesh
After completing these steps, you will have created a queue in Advanced Event Mesh.

1. Click in Manage

2. Under Broker Manager Quick Settings click the Queues tile. A new window opens up. This windows
allows you to execute a number of features in respect to this specific broker.

9
3. We will now create a queue. For that, click the +Queue button on the top right

4. In the pop up enter the queue name: opensap_** (replace ** with your number)

5. Click Create

6. The next screen allows you to enter settings for this queue. We will go with the standard settings. To
do this, click Apply

10
 7. Check whether you can find your queue in the list

You have now created your first queue in SAP Integration Suite, advanced event mesh.

Exercise 1.3 - Create a queue subscription for events in Advanced Event Mesh
1. Click on your queue

2. Click on Subscriptions

3. Click on +Subscription

11
 4. Enter the topic into the field. Use opensap_**_TOPIC as the topic (replace ** with your user
number).

HINT: Please note that this topic is very simple to facilitate this exercise. In real world scenarios, you can
work with topic hierarchies that allow for filtering etc.

14. Click on Create

15. Check on whether your queue subscription got created

Summary

You have now created a queue in AEM and have subscribed to events coming in via a topic. This means that
events that are published to your topic will get stored in the queue until they are consumed.

12
Exercise 2: Send an Event to a topic and find it in your queue
In this exercise, we will send an event on a second broker via a topic using the Try Me ! tool that comes with
Advanced Event Mesh. You will receive it in your queue via your queue subscription.

To put this into perspective: AEM provides an intelligent distribution of events throughout the mesh of Event
Brokers. This is what you experience here. The event will be made available wherever there is an interested
consumer.

1. Go to the cluster manager and select another broker in the mesh (for example the on in the US).

2. Click Try Me !

3. In the Publisher section, click on Connect

13
The icon behind Establish Connection should change from Red to Green.

4. Fill your topic into Publish --> Add Topic

14
Your topic is: opensap_**_TOPIC (replace ** with your number)

5. Optional: you can obviously adjust the message to a message of your choice or a real business
event. Hello World works fine for our exercise though.

6. Click Publish in the Publisher

15
7. The Publish status is updated

8. Go back to the broker where you have created your queue.

Hint: if you want to, keep two browser windows open.

9. Click on Manage and Queues

16
 10. Check on the number of messages in your queue. The count should have increased.

11. Click on your queue

12. Click on Messages Queued

13. Check on the message creation time

We have seen that our event has ended up in the queue. It is not possible to look into the event without
consuming it. What we could do now is to connect an event consumer and consume the event. In this short
exercise we will clean up behind us by deleting our queue and instead play around with the Try Me ! tool
some more.

Exercise 1.3 - Delete a queue in Advanced Event Mesh

17
 1. Go to your queue.

2. Mark it by clicking the radio button in front

3. Click on Action

4. Select Delete

5. Click Ok

You have now deleted your queue and cleaned up for the next participant. Thank you! Highly appreciated.

Exercise 1.4 – Play around with the Try me Tool

Now is your chance to play around some with topics and filters using the Try Me Tool!

1. Go to one of the brokers

2. Open the Try Me ! Tool

18
 1. Connect the Publisher by Clicking Connect
2. Connect the Subscriber by Clicking Connect
3. Establish Connection should now be green for both Subscriber and Publisher
4. Read the below on how topics work:

Each and every message can be published to a unique topic, depending on the event metadata. Some
examples of valid AEM topics are:

• hello/world/aem
• acme/taxi/rider/hail
• city/train/1234/alert/stopped
• mfg/plant42/inv/update/p12345667

19
 • payme/debit/qr/bank01/f89a09-2b9c065a3/ok

Because published topics can be so variable and dynamic, subscribers can use wildcards to match a
single subscription to multiple published topics. AEM supports two different types of wildcards:

• Single-level wildcard, 0-or-more chars, matches up to the next level /.

a. Can be used with a prefix e.g.: abc*, but not a suffix.
• Multi-level wildcard, matches one-or-more levels.
a. Must occur at the end of the topic subscription.

Some examples of AEM topic subscriptions, and topics that they match:

5. Check out the hierarchical categorization of animals below

20
Now try out different combinations of publishing to a topic and listening to a topic and see which events you
receive.

6. Register the consumer to listen to the Zebra topic - we just want to learn about Zebras getting born

7. For this subscribe the consumer to the topic animals/vertebrates/warm-blooded/mammals/zebra

8. Send a Zebra.born event to the topic animals/vertebrates/warm-blooded/mammals/zebra

21
Go to the Publisher, add Zebra.born to the message field, put animals/vertebrates/wam-
blooded/mammals/zebra into the topic field and click Publish

You should receive the message.

9. Now we want to learn about all warm-blooded animals getting born

• Go to the Subscriber

• Delete the topics your are listening to

• Subscribe to animals/vertebrates/warm-blooded/asteriks/asteriks

22
 • Send a Falcon.born event to animals/vertebrates/warm-blooded/birds/falcon

10. Try out a few combinations on your own and see what works and what does not

To make this easier for you, find the topics below for copy and paste.

• animals/vertebrates/warm-blooded/mammals/lion

• animals/vertebrates/warm-blooded/mammals/zebra

• animals/vertebrates/warm-blooded/birds/falcon

• animals/vertebrates/warm-blooded/birds/sparrow

• animals/vertebrates/cold-blooded/fish/shark

• animals/vertebrates/cold-blooded/fish/salmon

• animals/vertebrates/cold-blooded/reptiles/python

• animals/vertebrates/cold-blooded/reptiles/alligator

23
Summary

- You have made your first steps with SAP Integration Suite, advanced event mesh:

- You have created a queue

- You have subscribed a queue to a topic

- You have published an event to a topic from a broker in the US (using the Try Me ! tool)) and have
consumed the event on an event broker in Europe.

- You have deleted a queue

- You have played around some with topics and filtering in the Try Me ! tool

24
Coding Samples
Any software coding or code lines/strings (“Code”) provided in this documentation are only examples and are not intended for use in a production system environment. The Code is only intended to better
explain and visualize the syntax and phrasing rules for certain SAP coding. SAP does not warrant the correctness or completeness of the Code provided herein and SAP shall not be liable for errors or
damages cause by use of the Code, except where such damages were caused by SAP with intent or with gross negligence.

www.sap.com/contactsap

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements
accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. 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, and they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.