Operations

Understanding Monitoring

Objective

After completing this lesson, you will be able to understand monitoring

SAP Gateway Technical Operations

Figure outlines the technical operations of the SAP Gateway

After the configuration has been set up, the SAP Gateway Foundation Technical Operations Guide is the starting point for maintenance tasks that have to be carried out in the system landscape in which SAP Gateway Foundation components run.

Technical operations refer to the tools and documentation needed to carry out various administration tasks, such as monitoring, backup and restore, transports, and tests.

This figure lists some tools available for customers operating SAP Gateway. For the complete list, refer to the SAP Gateway Foundation Technical Operations Guide section in the SAP S/4HANA online documentation (at Enterprise Technology→ABAP Platform→Administrating the ABAP Platform→Technical Operations for the ABAP Platform).

Figure shows the Application Log in the system

Logs are automatically written by SAP Gateway components according to the log levels set in the system. Customers can monitor log files using transaction SLG1.

For FES systems, filter for object /IWFND/. For BES systems use object /IWBEP/.

Figure shows the SAP Gateway Error Log

The Error Log for SAP Gateway Foundation is a helpful addition to the Application Log Viewer. It provides detailed context information about errors that have occurred at runtime.

Developers, administrators, support consultants, and end users can launch the Error Log in transaction /IWFND/ERROR_LOG for FES and /IWBEP/ERROR_LOG in BES systems to obtain important context information about the time and location of errors. The Error Log facilitates easy navigation to the affected source code where you can make the necessary corrections.

The Error Log enables you to do the following:

  • Identify precise time and location of errors in source code

  • Determine how often an error has occurred

  • Perform root cause analysis

  • Reproduce and correct errors

The Error Log comprises of two screen areas:

  • Overview

  • Error Context

Figure shows SAP Gateway Statistics in the system

For increased transparency of processing times for the SAP Gateway, use the SAP Gateway Statistics transaction /IWFND/STATS. It also provides an aggregated statistics view to further facilitate monitoring at all times and on all levels.

SAP Gateway Statistics provides the following information in a tabular overview. Times refer to processing times and are given in milliseconds. You can expand or collapse entries depending on the level of granularity you require.

Figure shows the SAP Gateway Performance Trace using the SAP Gateway: Tracing Tools pane and the SAP Backend Tracing Tools pane

The Performance Trace tool enables developers, administrators, support consultants, and end users to monitor system performance at the service call level. You can trace the performance of both the BES system (SAP Gateway: Back-end Tracing Tools, transaction /IWBEP/TRACES) and the FES system (SAP Gateway: Tracing Tools, transaction /IWFND/TRACES).

After you have configured and saved the Performance Trace and started an accompanying OData service call, you can display detailed service call information that has been recorded by the trace function. Choose the Performance Trace tab to obtain a tabular overview. As standard, the active trace is valid for two hours, so all service calls executed within this time are listed in the table.

Work with the Performance and Payload Trace

Task 1: Configure and Activate the Performance and Payload Trace

Steps

  1. In your SAP S/4HANA system, set the following global configuration:

    • Duration in Hours for Active Trace: 1 hour

    • Keeping Days for Performance Trace Data: 7 days

    • Keeping Days for Payload Trace Data: 7 days

    1. Log on to your SAP system using the train-## user.

    2. Enter transaction /IWFND/TRACES.

    3. Navigate to Tools→Global Configuration.

    4. In the Duration in Hours for Active Trace field, enter 1.

    5. In the Keeping Days for Performance Trace Data field, enter 7.

    6. In the Keeping Days for Payload Trace Data field, enter 7.

      Figure shows the SAP Gateway: Global Configuration pane in the system

    7. Choose Save (Ctrl+S).

    8. Choose Continue (Enter) to confirm the information pop-up.

    9. Choose Back (F3).

  2. In your SAP S/4HANA system, activate the Performance and Payload Trace for your user train-##.

    1. Continue working in transaction /IWFND/TRACES.

    2. On the Configuration tab, select both Performance Trace and Payload Trace.

      Figure shows the SAP Gateway:Tracing Tools pane in the system

      Note

      This change becomes active immediately – therefore, you do not have to save it.

Task 2: Perform Activities

Steps

  1. Perform some activities in the FLP.

    1. Start or reload the SAP Fiori launchpad of your SAP system in a client of your choice.

    2. Make sure that you are logged on with your train-## user.

    3. Perform some arbitrary activities - for example, launch some of the available SAP Fiori apps.

Task 3: Analyze the Performance and Payload Trace

Steps

  1. In your SAP S/4HANA system, access and analyze the recent performance and payload trace.

    1. Continue working in your SAP system using the train-## user.

    2. Enter the transaction /IWFND/TRACES.

    3. Select the Performance Trace tab and note the recorded data.

      Figure shows the Performance Trace tab in the system

    4. Select the Payload Trace tab and note the recorded data.

      Figure shows the Payload Trace tab in the system

  2. For any of the requests, launch the trace details.

    1. Double-click any of the entries in the performance or payload trace.

      Figure shows the entries in the performance or payload trace

    2. Select Trace Details.

      Figure shows Trace Details in the system

System Monitoring with SAP Solution Manager

Figure shows SAP Fiori in SAP Solution Manager 7.2

SAP Solution Manager uses a combination of SAP Fiori applications and other types of SAP Solution Manager applications to provide users with access to SAP Solution Manager processes. Users access these applications from the SAP Fiori launchpad. SAP Solution Manager has its launchpad. Before you can use this, you must install, set up, and configure the SAP Solution Manager Fiori environment.

SAP Solution Manager Launchpad offers role-based access to all relevant applications and Work Centers. SAPUI5 / Fiori apps for key business-facing UIs and mobile applications. Vital SAP Solution Manager UIs are revamped incrementally using SAPUI5 / Fiori, based on customers' usage and demand. All Adobe Flash-based UIs for Run SAP applications and the existing SAP Solution Manager dashboards have been converted to SAPUI5.

Figure shows a graphical outline of the SAP Solution Manager: Embedded Deployment

Note the section SAP Fiori for SAP Solution Manager 7.2 at the SAP Help Portal for configuration details.

Essentially, there are two options to consume SAP Fiori in SAP Solution Manager 7.2. In case of an Embedded Deployment, all functions for SAP Fiori are processed in the AS ABAP part of SAP Solution Manager 7.2.

Figure shows a graphical outline of the SAP Solution Manager: Central Hub Deployment

Alternatively, in case of a Central Hub Deployment, you connect the SAP Solution Manager 7.2 to your (central) front-end server.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn