Using Local Monitoring functions for AS Java (SAP MC and NWA)

Objectives

After completing this lesson, you will be able to:
  • Describe the monitoring infrastructure and use SAP MC for Monitoring
  • Use SAP NetWeaver Administrator (NWA) for Monitoring
  • Adjust threshold values using NWA

Monitoring Infrastructure

Monitoring the AS Java system helps the administrator to identify resource bottlenecks or problems early on and to take any action that is required.

The monitoring in AS Java is based on the standard Java Management Extension (JMX). JMX provides a flexible administration infrastructure that is used for the monitors. The JMX infrastructure allows different resources to register as suppliers for monitoring data. Through the JMX API, data is made available for resources of all server components (services, interfaces, libraries, and managers), and applications using MBeans

During the start of the sapstartsrv the monitoring segment is created. The data collector of AS Java stores the current status and open alerts of the monitoring objects in the monitoring segment. Completed alerts are removed from the monitoring segment.

The data of the JMX monitors is stored in the monitoring segment. Since JMX is a standard, this ensures that external tools can also access the monitoring data. The external tools connect through the JMX API and can display all current values in the JMX monitors. They can also create, delete, and change groups, as well as installing and uninstalling monitor nodes. The JMX infrastructure is provided by the JMX Adapter service.

The data in the monitoring infrastructure is grouped in several areas like Applications, Kernel, Services and Performance.

  • Applications: This branch contains information about the status of applications that are running on AS Java and for which monitoring functions are implemented in the coding. This is a configurable type of monitor, since you can specify which information is displayed in the monitor for your own applications. An application developer usually creates his or her own monitors and objects under the Applications branch.

    The monitor Table Buffer is always displayed in the Applications area along with other items.

  • Kernel: Status information for the managers registered for monitoring is displayed under the Kernel entry.

  • Services: Status information for the services registered for monitoring is displayed under the Services entry.

  • Performance: The Performance area displays available data about performance measurements of AS Java, e.g. communication to external systems.

Note

The monitor branches, such as Kernel and System are reserved for data that is directly and automatically collected by the system.

There are various tools for the operating with the monitoring data.

Local Monitoring Tools

SAP MC and SAP MMC

With the SAP MC and SAP MMC you are able to view the current status and open alerts of monitoring attributes. The SAP MC and SAP MMC communicates directly with the sapstartsrv and gets the information out of the monitoring segment of AS Java, this means, that e.g. performance issues of AS Java doesn't affect the monitoring and alerting.

NWA - System Overview

The system overview is available in two versions. One version is available in the NWA and the other is available via sapstartsrv (this is called the offline system overview). The system overview gives you an graphical overview of the current status of some monitoring attributes and their values. The system overview in the NWA provides a navigation to expert functions in the NWA for the displayed attributes.

NWA - Monitoring Browser

The monitoring browser is available in the NWA. The monitoring browser shows the current status of the monitoring attributes and you can maintain thresholds and activate/deactivate monitoring attributes.

Central Monitoring Tools

SAP Solution Manager

The System Monitoring application in SAP Solution Manager provides an overview of the current status of technical systems, including their associated instances, databases and hosts.

System Monitoring is based on automated checks in regular time intervals in the four categories Availability, Performance, Exceptions, and Configuration. In each of these categories, several metrics and corresponding thresholds can be defined per managed object.

The configuration is based on a template concept. Pre-defined templates can be used as a starting point to derive own customer specific templates.

CCMS-Monitoring RZ20

The RZ20 in a CEN (central monitoring system) is a tool to monitor multiple SAP systems and their operating systems. You can set up additional notifications in case of alerts and auto-reaction methods there. Beyond that, you are able to view the current status and open alerts of monitoring attributes. You can maintain thresholds and complete open alerts. The RZ20 gets its information out of the monitoring segment of AS Java, this means, that e.g. performance issues of AS Java doesn't affect the monitoring and alerting in the CEN system.

Monitoring with the SAP MC

The monitoring area in the SAP MC or SAP MMC is divided in two parts. One area is for the open alerts and in the other the current status are displayed.

Each area is structured in several parts, for example Java Instance, Server or Application where you can drill down. If you select Kernel from one server process, you get displayed all monitoring attributes in the right window pane. Time indicates the time, where the value was reported from the AS Java. You can see all available alerts of the monitoring attribute by selecting the monitoring attribute and choose All Alerts from the context menu. This option is available in the current status area and open alert area.

In the right pane press the left mouse button on the Alert Name headline for choosing the different sort criteria. Every click alternates between sorting "by alert", "order of the monitoring structure" or "by reverse alert".

Monitoring with the NWA

With the SAP NetWeaver Administrator (NWA), you can monitor the application server itself and the components and applications running on top of it. You can also extend the functionality of your custom applications by adding monitoring capabilities to them, and thus to take advantage of the monitoring tools and infrastructure for monitoring your own applications.

Monitoring with the NWA – System Overview

You can access the System Overview in the NWA in the workcenter Availability and Performance in the work set System Overview.

It shows the current values of the displayed monitoring attributes, and you can navigate to other functions by choosing the primary mouse button on the monitoring attribute.

On the selected attribute the following information are available:

context based analyze method allows you to get more information about the monitored value or even solve the problem.

View History to jump to the history report application.

  • Configure Thresholdsto configure the Thresholds for this metric in the Monitoring Browser application
  • Helpto access the available online documentation for this metric

Monitoring with the Monitoring Browser

The current status values for the monitoring attributes are displayed with alert colors in accordance with the "traffic light system" in SAP NetWeaver Administrator (NWA), the data is displayed in the Monitoring Browser. You are taken to the Monitor Browser with Availability and Performance → Resource Monitoring → History Reports. Here you can select the Monitor Browser tab.

In the Monitor Browser you have two views, one for the Active/Used monitoring attributes and one for the Inactive/Not used monitoring attributes. In the Monitor Browser you can activate/deactivate monitor attributes (there is no other tool for activation or deactivation of monitoring attributes). In the lower part of the Monitor Browser you can see the period of the data collection.

In the NWA, the Monitor Browser displays all the running nodes in the system with the current value of the selected monitoring attribute.

A threshold value determines when which alert (color in the monitor) is to be triggered. For a working monitoring that is individually adjusted to your system, you should adjust the threshold values. In the Monitor Configuration area it is possible to maintain the thresholds.

In the monitor itself, the statuses are identified with different colors. A color changes when a value exceeds or falls below a threshold value. Errors are highlighted in red and passed on to the highest level of the monitor. You can find the alert that has occurred by expanding the monitor. The following colors can be displayed in the monitor:

Optional: Monitoring using SAP NetWeaver Administrator (NWA)

Business Example

For successful monitoring using the Monitoring service in SAP NetWeaver AS Java, you must set the threshold values appropriately.

Valid for this Exercise

ParameterValue
SAP ClassroomWTS
SAP System IDSMJ
Host name (FQDN)smhost.wdf.sap.corp
Operating SystemWindows
Central Services InstanceSCS90
Primary Application Server (PAS)J91
SAP NetWeaver AdministratorNWA
Java Administrator / passwordtrain-## / <your password>
Always replace ## with ...<group no.>

Task 1: Logon to SAP NetWeaver Administrator (NWA)

To use the SAP NetWeaver Administrator you first need to log on.

Steps

  1. On the WTS open an Edge browser, enter the Start page of the AS Java, start SAP NetWeaver Administrator and Log on.

    1. In the SAP Solution Manager SMJ-WTS start anEdge browser.

    2. Enter the URL http://smhost.wdf.sap.corp:59100

    3. Use SAP NetWeaver Administrator link on the start page or change your URL to:http://smhost.wdf.sap.corp:59100/nwa

    4. On the Logon Page enter:

      • User:*train-##
      • Password:*<your password>.

Task 2: Using System Overview

Using System Overview for Monitoring, using the details in the steps. Try to answer the questions.

Steps

  1. Using System Overview for Monitoring

    1. Select the Work CenterAvailability and Performance.

    2. Select function System Overview (default).

    3. By using this tool answer the following questions:

      • What is the value for Requests per Second from the Users to the ICM? ________
      • What is the Response Time between ICM and AS Java? ______
      • How many External Calls are currently reported? ________
      • How many logs are written per Minute? _____________

      Result

      Result: You have seen some important performance indicators in the System Overview. For example the Response Time between ICM and AS Java: It represents time (in milliseconds) between the call of the send method and the actual writing of the message in the socket. More information for the single KPIs can be taken from the online documentation. The System Overview can help you identify quickly which areas currently are covering problematic issues.

    4. In section Nodes press Failed: xx

    5. Select Manage Server Nodes

    6. On the top right of the screen press Back

    7. Check if you find Failed Components on the AS Java.

    8. Press Applications and select View Failed Applications.

    9. Press Back to return to the System Overview.

    10. In section Memory Consumption press Average.

    11. In the Context Menu select Manage User Sessions and answer the following question:.

    12. How many Bytes does your user consume (column: Allocated Memory (Bytes))? ___________

    13. On the top right press Back.

    14. In section Memory Utilization press Average: <xx>% and select View Engine Performance Statistics.

    15. On the top right press Back

Task 3: Optional: Using the Monitor Browser

Use the Monitoring Browser within NWA to check alerts for different monitoring attributes, activate an inactive monitoring attribute, and change thresholds.

Steps

  1. Within NWA open the Monitoring Browser, and check whether an alert has occurred in the memory service.

    1. You are still connected to the NWA with an Edge browser.

    2. Use the Search field on top and enter: History Report.

    3. In the resulting screen select Monitor Browser. Alternatively use path Availability and Performance → Resource Monitoring → History Reports → Views (the small triangle) → Monitor Browser.

    4. Choose the tab Monitor Browser.

    5. In field Show select Active/Used(default).

      Hint

      Here you can see the various monitors. You can use the colors (red, yellow, green, gray) to identify whether an alert has occurred.

    6. Below field Name use the filter and enter: Memory.

    7. Press ENTER.

    8. Select the row /Services/Memory Info/Available Memory.

    9. In the section Monitor Details for: Available Memory you can see the configured HEAP memory for each Server Process.

      Hint

      This is a cross-instance view, representing the complete Java infrastructure in terms of Server Processes.

    10. Now select the line /Kernel/SAPJVM/GCProblemReporting/Out Of Memory Errors.

    11. Check the status of each Server Node ID.

  2. Activate the inactive Monitor Kernel/Application Threads Pool/Waiting Tasks Count in the NWA Monitoring Browser.

    1. In the NWA, in application History reports: Monitor Browser select the in fieldShow the valueInactive/Not Used.

    2. Under the field Name use the filter by entering the following value: Application Threads

    3. Press ENTER.

    4. Select the line Kernel/Application Threads Pool/Waiting Tasks Count.

    5. In the lower part of the screen within section Monitor Configuration press the push-button Activate.

      Hint

      A message is displayed to inform you that the "Changes were successfully saved".

    6. In field Show select Active/Used.

    7. Under the field Name use the filter by entering the following value: Application Threads

    8. Press ENTER.

    9. Select the line Kernel/Application Threads Pool/Waiting Tasks Count.

    10. In the field Monitor Details for: Waiting Tasks Count you should find the current value for every Server Process.

  3. Set the threshold values for the monitor /Services/Memory Info/Usage Rate to the following entries: GY/YR/RY/YG to 75/90/85/70.

    1. Under the field Name use the filter by entering the following value: Info/Usage

    2. Press ENTER.

    3. Select the line /Services/Memory Info/Usage Rate.

    4. In the area Monitor Configuration enter the following threshold settings:

      • Changes from Green to Yellow:75

      • Changes from Yellow to Red:90

      • Changes from Red to Yellow:85

      • Changes from Yellow to Green:70

    5. Press Save.

      Hint

      A message is displayed to inform you that the "Changes were successfully saved".

Task 4: Optional: Create a History report

Create your own History Report for your monitoring.

Steps

  1. Create a History Report showing Thread Pool Usage Rate and Used Memory Rate.

    1. Still in NWA, using function Monitor Browser, switch to the tab History Reports.

    2. Under the tab History Reports change to sub-tab Configure.

    3. Press New Report.

    4. In the popup window New Report enter the following information:

      Name Label:ADM800-##
      Default Report Time Unit:Quarters
      Default Report Type:Chart per note

    5. Press OK.

    6. Re-size the table with the wrench icon on the right in the header area of the table and select Medium (10 Rows).

    7. Use the filter field below column Monitor Name and enter: Rate.

    8. Select the following rows:

      Note

      To select multiple rows hold CTRL key whilst selecting the rows.
      • Thread Pool Usage Rate
      • Used Memory Rate

    9. Press Add to Report.

    10. Press Save Reports.

      Result

      The message "Report successfully saved" confirms your saving action. The history report includes two Key Performance Indicators (KPI).

    11. Change to tab Display.

      Hint

      The display of your new History Report is presented in a sub-optimal way - this is a rendering problem and should be solved with a patch apply. Usually the Metrics/Charts should use more space of the screen.

      Because in our landscape WTS only one participant is using the SAP Java-based SAP System, the Thread Pool Usage Rate is very low. In practice this indicator could cover very useful information.

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn