NAM enables you to monitor the SAP front-ends and database back-end of your SAP deployment.
Monitoring SAP GUI users
The SAP GUI analysis module decodes the SAP GUI protocol and obtains the names of the users logged on to SAP. The decode also detects the names of the transactions that the SAP GUI users execute. Monitoring is performed individually for each user, each recognized ABAP transaction, and on an aggregated level of the SAP server.
The SAP GUI analysis module covers SAP GUI for Windows and SAP GUI for Java.
Monitoring SAP RFC
SAP Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems or SAP systems and non-SAP systems. The SAP RFC analysis module enables end-to-end monitoring of the SAP transactions and enables precise measurements of SAP integration layer transactions, known by name and user, reporting on transaction availability and response time.
With SAP RFC decode, you can precisely troubleshoot integration problems within SAP systems and between 3rd-party systems. Trending and base-lining of the SAP RFC transactions allows you to instantly detect changes within the integrated systems
The SAP RFC analyzer will identify operations (name, parameters), detect errors, user names and operation attributes, and report this data to the report servers.
Monitoring SAP HTTP users
There are two types of SAP Web users: SAP GUI for HTML (SAP WebGUI) and SAP Web portal. NAM modules allow you to fully or partially monitor SAP HTTP users:
- The SAP GUI over HTTP analyzers of the NAM Probe, together with the website reports of the report server, provide a detailed view of all operations invoked by the SAP WebGUI users.
- The HTTP analyzer recognizes all URLs and URL parameters to isolate the individual transactions and report down to the T-Code level.
The SAP Web portal user names are recognized but individual operations require custom configuration in order to report valuable information. Contact Support for configuring the individual operations.
Monitoring the Database
The database tier is monitored with database protocol analysis modules. NAM has analysis modules for Oracle, DB2, Microsoft SQL Server, Sybase, and Informix. For each of these databases, NAM reports the database server performance, and to a more granular level, the performance of the individual queries and stored procedure calls.
SAP support on the NAM Probe
|SAP GUI||SAP GUI protocol (DIAG)||6.40, 7.10, 7.20, 7.30||SAP GUI for Java 7.10rev8, SAP GUI for Windows 7.10, SAP GUI for Windows 7.30, SAP GUI Console, Net weaver Business Client 4.0.|
|SAP RFC||SAP RFC||SAP PI, SAP BW, Excel plugin for SAP|
|SAP GUI over HTTP||HTTP||1.1, 1.0 (RFC 2616)||Support for SAP 7.01 SP3 and 7.02. Support for SAPGUI for HTML (WebGUI) only. No support for SAP portal application and user name recognition.||SAP GUI for HTML|
|SAP GUI over HTTPS||HTTPS||HTTP 1.1 encapsulated in SSL, SSL 3.0, TLS1.0 (RFC 2246), TLS 1.1 (RFC 4507, 4680), TLS 1.2 (RFC 5878)||Support for SAP 7.01 SP3 and 7.02. Support for SAPGUI for HTML (WebGUI) only. No support for SAP portal application and user name recognition.||SAP GUI for HTML|
Reporting SAP performance
NAM includes service-module-task-operation hierarchy on the technical side and application-transaction-step on the business data grouping side. Together, these hierarchies present information on performance from the top-level end-user visible application down to individual technical operations that application server processes.
The SAP RFC reporting hierarchy is based on the configuration of SAP RFC operations in the SAP RFC related software services. This will let you precisely measure SAP integration-layer transactions, known by name and user, and report on transaction-availability and response-time problems. The analyzer can tell you precisely whether:
- The analytics are slow because of network-capacity problems that are caused by interference between SAP transactions and other data.
- The SAP server is responding slowly.
- The amount of data read from the SAP database is too large for network transfers to Excel.
The SAP reporting hierarchy is included out of the box and can be adjusted to business needs by importing custom CSV file.
The business hierarchy settings imported from the CSV file also drive reporting of the multi-step transactions that represent business processes. Multi-step transactions are aligned with the technical hierarchy – the tasks have steps that represent SAP T-Codes that have to be invoked by end users to complete a business task, in order.