When monitoring for SAP Fiori apps, you monitor the components of the SAP Fiori system landscape. In particular, monitoring SAP Gateway is essential for monitoring SAP Fiori apps.
SAP Gateway has a key role in the system landscape for SAP Fiori apps as it is the underlying technical system in the front-end server. Therefore, monitoring SAP Gateway is essential for monitoring SAP Fiori apps. In SAP Gateway, you can, for example, monitor the end-user experience as seen from a specific app.
There are severals levels on which you can monitor SAP Gateway.
SAP Gateway is registered in the Landscape Management Database (LMDB).
SAP Gateway is connected to SAP Solution Manager as a managed system.
In the Landscape Management Database (LMDB), you get an overview of the system status of SAP Gateway as a technical system.
In SAP Solution Manager, in the Technical Monitoring
work center, System Monitoring
view, you monitor the system status of SAP Gateway. For example, you monitor for errors, performance, and availability.
For more information, see System Monitoring in the SAP Library for SAP Solution Manager at
In SAP Solution Manager, in the Technical Monitoring
work center, End-User Monitoring
view, you monitor the end-user experience as seen from a specific app. That is, you can monitor the connection between end-user device (client) and SAP Gateway in a front-end server.
For more information, see End User Experience Monitoring in the SAP Library for SAP Solution Manager at
In SAP Solution Manager, in the Root Cause Analysis work center, in the Exception Management
view, you monitor for underlying exceptions that impact the service quality.
For more information, see Exception Management in the SAP Library for SAP Solution Manager at
For an overview of which products are available for end-to-end root cause analysis, see SAP Note 1478974.
To monitor for errors and performance issues, for example, if an app runs not as expected, you can trace the app.
Activate end to end tracing on the device as follows:
On a desktop computer, press CTRL ALT SHIFT s.
On a mobile device:
Press two fingers on a non-interactive screen area (for example, a blank area) for at least 3 seconds.
Tap with a third finger while holding the other two on the screen.
In the app, perform the actions that you want to trace.
After every action, confirm that you want to continue tracing.
When you want to quit tracing, choose Cancel
and then choose OK
.
The device sends the trace data to SAP Solution Manager via SAP Gateway.
In SAP Solution Manager, in the Root Cause Analysis
work center, open the End-to-End Analysis
view.
In the End-to-End Analysis
view, select a system and start Trace Analysis
.
The E2E Trace Analysis
opens.
To collect all data in the connected systems that relate to the trace data, select a business transaction.
A window appears.
Make sure at least the first option is selected and confirm your entries.
Display and analyze the collected trace data: For example, analyze how long it took for requests to execute.
For more information, see End-to-End Analysis in the SAP Library for SAP Solution Manager at
You can also monitor SAP Gateway without using SAP Solution Manager.
For more information about the error log for SAP Gateway hub, see the following documentation:
For SAP NetWeaver 7.31, see SAP Help Portal at
.For SAP NetWeaver 7.4, see SAP Help Portal at
.For more information about logging, see Logging and Tracing at:
For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at
.For SAP NetWeaver 7.4, see SAP Help Portal at
.No additional monitoring for SAP Fiori apps.
For more information about monitoring SAP Gateway, see the following documentation:
For SAP NetWeaver 7.31, see SAP Help Portal at
.For SAP NetWeaver 7.4, see SAP Help Portal at
.