Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

SAP monitoring

NAM monitors users and application operations when a SAP client and a SAP application server communicate.

Benefits of SAP monitoring with NAM

NAM provides answers to common questions about the status of the SAP application:

  • How many users use the application and its modules or transactions, and when.
  • How many users have performance problems with SAP; what are those performance problems, when do they occur, and what transactions are causing performance problems.
  • How many users encounter errors working with SAP applications, what are the exact errors returned by the server and for which transactions.
  • What causes the problems that end users experience: the application server, the database server, or the network.
  • Why are particular transactions slow: is it the application logic, system resources, database throughput, or one of many other reasons.

SAP GUI binary traffic (also known as the DIAG protocol) is observed by the NAM Probe as a series of data portions referred to as command chunks. Each chunk type is identified by the command chunk ID, an important element of SAP GUI monitoring. The most important are the IDs associated with the user names and operation names. By default, the NAM Probe is configured to monitor the most common IDs.

SAP GUI over HTTP (or SAP GUI over HTTPS) analysis is identical to web application performance monitoring. It can be configured to monitor specific URLs or ranges of URLs, or to automatically recognize and analyze the URLs that appear most frequently. You can also configure many other aspects of web application monitoring, such as user recognition, HTTP and SSL error groups, object and frame recognition, or synthetic agent recognition.

SAP multi-tier monitoring

SAP software is a large and complex system composed of three tiers (client, application server, and database) and involving network interactions between these tiers: between client and application server and between application server and database.

SAP uses a third-party DBMS such as Oracle or Microsoft SQL Server. The application server relies on the DBMS network protocols to access the database. A separate monitoring configuration is required for the database back-end. You can use one or two NAM Probes to listen both in front of the SAP servers and in front of the database servers.