SAP GUI and ABAP Platform extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor your SAP Application Server's user transactions, RFC, and jobs.
Get started
Overview
Monitor SAP ABAP platforms remotely via Dynatrace, analyzing key metrics and response times.
This extension queries SAP servers for key performance counters. The collected metrics are analyzed in Dynatrace, using ABAP platform health indicators including response time breakdowns of the response times between ABAP-specific application server activities, tasks, and database interaction, as adviced by the SAP expert community’s established best-practices.
Requirements
-
You have an environment ActiveGate with Dedicated Performance Profile.
-
Make sure the ActiveGate size is appropriate, especially if you configure several configurations which poll from a single ActiveGate. A monitoring configuration to an SAP application server with production load can consume up to 0.5 CPU cores and 1.5 GB RAM on the ActiveGate.
-
When setting up the dedicated profile, the RUM Beacon Forwarder is disabled by default. You must change the ActiveGate's
custom.propertiesfile as follows to turn it on.[beacon_forwarder]beacon_forwarder_enabled = true
-
-
You have SAP Java Connector on the ActiveGate host. To learn how to configure it, see SAP Java Connector configuration.
-
The ActiveGate requires remote access to the SAP application server (AS ABAP) over RFC protocol.
-
If the endpoint is configured to poll all clustered instances, the ActiveGate requires remote access to all the SAP AS instances.
-
A user account that has permission to execute the following monitoring functions
Authorization Object
Details
S_RFC
- Activity:
16 - RFC Type:
FUNC - RFC Name:
/SDF/GET_DUMP_LOGGET_SYSTEM_TIME_REMOTESWNC_GET_WORKLOAD_SNAPSHOTTH_SERVER_LISTTH_USER_LISTRFC_METADATA_GETRFCPINGRFC_GET_FUNCTION_INTERFACEDDIF_FIELDINFO_GETRFC_READ_TABLE
/SDF/E2E
- Activity:
03
S_RZL_ADM
- Activity:
03
S_TOOLS_EX
- AUTH:
S_TOOLS_EX_A
S_TCODE
- TCD:
SM51
S_TABU_NAM
- ACTVT:
03 - TABLE:
TBTCO
- Activity:
Compatibility information
SAP NetWeaver ABAP release 7.31+
Activation and setup
Activate the extension in your environment using the in-product Hub. Provide the necessary configuration and you’re all set up.
Details
SAP Java Connector configuration
Configure the SAP Java Connector on the ActiveGate host
- Download the 64-bit version of the SAP Java Connector to the ActiveGate.
- Place the
sapjco3.jarfile into theJCofolder, as configured below when adding a new monitoring endpoint (step 7 in extension installation). - Depending on the OS running on the ActiveGate host, place
sapjco3.dll(Windows) orlibsapjco3.so(Linux) into theJCodirectory. - Make sure that the user account executing the plugin is permitted to read from the
JCofolder. - Windows only Make sure that the Windows-based ActiveGate host has the Visual C++ Redistributable Packages for Visual Studio 2013 installed. The SAP Java Connector depends on it.
Configuration Details
| Setting | Details | |
|---|---|---|
| Connect to SAP via | Connect directly to an SAP application server or via a message server. Once the list of SAP application servers is collected, the extension connects directly to the servers. If the message server is down, the availability of the SAP application servers behind the message server will not be collected. To detect and configure alerting for such a state, set up a missing data alert custom event that alerts on the condition if data is missing. | |
| SAP Application Server Address | The IP or host name of the SAP application server. Not used when connecting via a message server. | |
| Instance ID | The instance ID to connect to (this is a numeric, two digit value). Not used when connecting via a message server. | |
| System ID | The system ID to connect to. Only used when connecting via a message server. | |
| Message Server Host Name or Address | The IP or host name of the message server. Only used when connecting via a message server. | |
| Message server port number | The port that the message server is listening on. Only used when connecting via a message server. | |
| Group/server | The group/server configured on the message server. Only used when connecting via a message server. | |
| Keystore path | Path to keystores if required for the connection, defined as SECUDIR. | |
| Username | The username for the account connecting to the SAP application server. | |
| Password | The password for the account. | |
| Client Number | The client number to use for the connection. | |
| Poll all Clustered SAP Instances | Instead of creating one endpoint per SAP instance, this option polls all clustered SAP instances at once. | |
| Use 'SAP Application Server Address' as the Application Server Name | Instead of the entity using the name returned by the application server instance, use the value entered in SAP application server address. Not possible when Poll all Clustered SAP Instances is enabled. | |
| Path to a JCo Destination File | optional If a specific destination file is required to connect to the SAP server, enter the path here. This will override all of the above settings except for the keystore path. | |
| SAP JCo folder | The folder containing the sapjco3.jar and the native Java Connector file. | |
| Task types to report on | List of task types to report on, the rest will be combined. The possible task types are: NONE, DIALOG, UPDATE, SPOOL, BCKGRD, ENQUEUE, BUF.SYN, AUTOABA, UPDATE2, NATIVE_RFC, PLUGIN, AUTOTH, RPCTH, RFCVMC, DDLOGCLEANUP, DEL.THCALL, AUTOJAVA, LICENCESRV, AUTOCCMS, MSADM, SYS_STARTUP, BGRFCSDL, BGRFC, APC, OTHERS, DINOGUI, B.INPUT, HTTP, HTTPS, NNTP, SMTP, FTP, LCOM, HTTP/JSP, HTTPS/JSP, AUTO_RFC, WS-RFC, WS-HTTP, ESI, ALE, RFC and CPIC | |
| Report User Sessions | Select this to create user sessions and user actions based on the customer-executed Tcodes. This functionality requires a custom application to be created. | |
| The Application ID of the custom application | To create user sessions, fill in the Application ID you are prompted with after creating the custom application. | |
| Inactivity time out (in minutes) when capturing user sessions | Enter a number between 5 and 25, default is 25. | |
| Capture Usernames as part of the User Sessions | Select to capture usernames. | |
| Use Terminal Name for End User Location | When capturing user sessions, use the IP resolved from the first 20 characters of the terminal name instead of the SAP returned user IP. This is useful when the application server does not know the client IP, for example when the users connect via SAP Router. | Reduces overhead on SAP application server, but lowers the granularity in charts and delays data retrieval. During heavy load on the SAP application server this might cause the SAP server to not send all user actions to Dynatrace. |
| Report on RFC Client/Server Metrics | Select whether to only report on the servers communicating to/from the SAP Application server, or to additionally split up the metrics on individual function names. | |
Capture Usernames as part of the Per Function Call RFC Metrics | Include Usernames as a dimension when capturing RFC Metrics Per Function Call | |
| Poll Less Often | Reduces overhead on SAP application server, but lowers the granularity in charts and delays data retrieval. During heavy load on the SAP application server this might cause the SAP server to not send all user actions to Dynatrace. | |
| Enable Debug Logging | Select this only if a Dynatrace product expert requests it to investigate an issue. |
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
Dialog Metrics
| Metric name | Metric key | Description |
|---|---|---|
| GUI User count | sap.guiusercount | — |
| Dialog response time | sap.guiresponsetime | — |
| Dialog steps | sap.guidialogsteps | — |
| Dialog network time | sap.guinetworktime | — |
RFC Metrics
| Metric name | Metric key | Description |
|---|---|---|
| RFC Incoming Execution Time | sap.rfcIncomingExecutionTime | — |
| RFC Incoming Call Time | sap.rfcIncomingCallTime | — |
| RFC Incoming Receive Bytes | sap.rfcIncomingReceive | — |
| RFC Incoming Send Bytes | sap.rfcIncomingSend | — |
| RFC Incoming Requests | sap.rfcIncomingRequests | — |
| RFC Outgoing Execution Time | sap.rfcOutgoingExecutionTime | — |
| RFC Outgoing Call Time | sap.rfcOutgoingCallTime | — |
| RFC Outgoing Receive Bytes | sap.rfcOutgoingReceive | — |
| RFC Outgoing Send Bytes | sap.rfcOutgoingSend | — |
| RFC Outgoing Requests | sap.rfcOutgoingRequests | — |
Threshold Metrics
| Metric name | Metric key | Description |
|---|---|---|
| 50% boundary | sap.fiftyline | — |
| 10% boundary | sap.tenline | — |
| 2% boundary | sap.twoline | — |
Application Server Instance Metrics
| Metric name | Metric key | Description |
|---|---|---|
| Runtime errors | sap.runtimeErrorsByCat | — |
| Connected users | sap.sessions | — |
| CPU time/Response time ratio | sap.cpuratio | — |
| Wait time/Response time ratio | sap.waittimeratio | — |
| Load time/Response time ratio | sap.loadtimeratio | — |
| Database time/Response time ratio | sap.dbtimeratio | — |
default
| Metric name | Metric key | Description |
|---|---|---|
| Availability | sap.avail | — |
Job Metrics
| Metric name | Metric key | Description |
|---|---|---|
| Job Count | sap.job.count.gauge | — |
| Job Status Count | sap.job.status_count.gauge | — |
| Job Avg Duration | sap.job.avg_duration | — |
| Job Max Duration | sap.job.max_duration | — |
| Job Avg Delay | sap.job.avg_delay | — |
| Job Max Delay | sap.job.max_delay | — |
Task Metrics
| Metric name | Metric key | Description |
|---|---|---|
| Average task time | sap.Task.avgtottime | — |
| Average time | sap.avgtime | — |
| Dialog steps | sap.Task.dialogsteps | — |
| CPU time | sap.Task.cputime | — |
| Database time | sap.Task.dbtime | — |
| Roll in time | sap.Task.rollintime | — |
| Roll wait time | sap.Task.rollwaittime | — |
| Load + generation time | sap.Task.loadgentime | — |
| Database calls | sap.Task.dbcalls | — |
| User count | sap.Task.usercount | — |
FAQ
What is the Custom Metric Usage of this extension?
The formula for consumption of the extension depends on the enabled feature set.
-
Default:
2 * <# of App Servers> -
Threshold Metrics
3 * <# of App Servers> -
Application Server Instance Metrics:
21 * <# of App Servers> -
Tasks Metrics:
((8 * <# of Tasks configured>) + 8) * <# of App Servers> -
Dialog Metrics:
4 * <# of App Servers> -
Jobs Metrics:
6 * < # of Jobs> -
RFC Metrics:
Depending on your configuration
- Per Remote Destination:
10 * < # of Remote Destinations > * <# of App Servers> - Per Function Call:
10 * < # of Remote Destinations > * <# of Program Names> * <# of Location Destinations> * <# of client numbers> * <# of user ids> * <# of function names> * <# of App Servers>
- Per Remote Destination:
