This public repository is read-only and no longer maintained.
This guide has been created for the SAP TechEd 2018 session OPP362.
Monitoring cloud native applications or solutions running in a hybrid landscape is becoming more and more complex without the right tools. In this session, you will learn how to use the basic monitoring features of the SAP Cloud Platform, how to do end-to-end tracing with the SAP Solution Manager or how to trace each call and spot each bottleneck immediately with Dynatrace.
The different systems and their relation we use for our scenario are sketched out by the following landscape diagram.
The used landscape consists of the following systems:
- On-premise backendsystem hosting the ICF service to be consumed in the cloud application. The backend with system name TE3 is based on SAP NetWeaver 7.52 and runs in the cloud.
- On-premise Cloud Connector to enable access to the backend. A productive version of the Cloud Connector (v.2.11.1) is running on your student notebook.
- SAP Cloud Platform subaccount to create, run and operate the cloud application. A new trial subaccount (Neo and Cloud Foundry environments) has been already created for each of the students. Everything has been already configured and deployed so that you can focus on the monitoring part.
- SAP Solution Manager to configure and run an end-to-end trace analysis. A dedicated system (v.7.2.) has been installed in the cloud for each student.
- Dynatrace environment. For the Teched session, we will used a dedicated cluster but you can do exactly the same exercise with a trial environment.
Everything has been already configured for you so that you can focus on the monitoring topic. Nethertheless, here is a summary of the requirements that re needed if you want to set up the same hybrid landscape later on your own:
- Configuration of on-premise S/4HANA system and activation of Fiori Reference Apps OData Services. See SAP tutorial for more details.
- Installation of Cloud Connector. See SAP tutorial for more details.
- Installation of SAP Solution Manager. See SAP official documentation for more details.
- Installation of the NEO Console and configuration of the environment variables to facilitate its usage in the console. See SAP official documentation for more details.
- Creation of SAP Cloud Platform trial account. See SAP tutorial for more details.
- Deployment of the SAP demo app ESPM application. See Github repository for more details.
- Adaptation of the ESPM application to deploy the retailer app to the Cloud Foundry environment and establish connectivity between Neo and Cloud Foundry environments. See SAP tutorial for more details.
- Creation of Dynatrace trial environment. See Dynatrace website for more details.
To finalize the setup for the exercises, some mandatory steps are required before starting the exercises:
- Access the SAP Cloud Platform cockpit and restart the cloud HANA database.
- Connect the Cloud Connector to your SAP Cloud Platform subaccount and add an access control.
- Verify that the cloud application runs without any issue.
Follow the instructions on the preparation page to get all the details.
The actual exercises are grouped into three lessons
- Lesson A: Basic monitoring features of SAP Cloud Platform
In this lesson, you will explore how to use the out-the-box basic monitoring features of the SAP Cloud Platform to monitor your Java applications running in the Neo environment. You will create availability checks, alerts notifications, JMX checks and used the monitoring REST API. - Lesson B: Trace analysis using SAP Solution Manager
In this lesson, you will learn step-by-step how to configure your dedicated SAP Solution Manager and your SAP Cloud Platform account to run a trace analysis of your hybrid application. You will define the technical systems and the cloud services, create a scenario, activate the statistics in the cloud and then start the tracing. - Lesson C: Application performance using Dynatrace
In this lesson, you will learn how to use the third-party APM tool Dynatarce to monitor your application running on the SAP cloud Platform. You will connect your dedicated Dynatrace environment with your Neo and your Cloud Foundry subaccounts, you will configure alert notifications and experiment how to debug different application anomalies.
- As the 3 lessons don’t depend on each other, you can choose which lessons you want to learn. In 2 hours, you should be able to run 2 of them, 3 if you are really fast. So you can start with one or the other lesson. Only the preparation steps need to be done at the beginning.
- Lessons A and B can be done later on as the cloud systems (SAP Cloud Platform Account and Dynatrace environment) will be available for the next 2 weeks.
- Multiple systems with different users: As you are working on different systems that use all different user / password combinations you need to be very careful where to use which user. Too many failed login attempts will lock the systems. Please remember the following rules:
- The user Demo is always used for the SAP backend TE3 or SAP Solution Manager TE2 user
- Users starting with p are always SAP Cloud Platform users.
- The user Administrator is only used for the Cloud Connector.
- The Dynatrace requires always an email address to login.
- Use the provided Student Overview Paper to verify credentials during the hands-on session.
- Explore the Student File Share to check the assets needed during the exercises. You will find a shortcut on the desktop of your notebook. All assets are in the folder called OPP362.
- Your Teched image will be automatically deleted 5 minutes after the end of the session.
- SAP Cloud Platform Trial
- Cloud Connector
- SAP official documentation:
- Dynatrace environment
- Dynatrace documentation
If you need any support, have any question, or have found a bug, please report it as an issue in the repository.
Currently there are no known issues.
This content is currently maintained by Matthieu Pelatan.
Copyright (c) 2018 SAP SE or an SAP affiliate company. All rights reserved.
This project is licensed under the Apache Software License, v. 2 except as noted otherwise in the LICENSE file.