Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

SAP Monitoring FAQs - ABAP Agent

Table of Contents

How does ABAP work?

How is the agent different than traces on SAP?

How does the AppDynamics Setting screen get into SAPGUI in order to configure the ABAP agent?

Where do I configure the ABAP agent?

Does the ABAP language support dynamic bytecode instrumentation?

How does the ABAP Agent decide when to enable a trace?

What is the performance overhead of the ABAP Agent?

Additional Resources

 

Q: How does ABAP (Advanced Business Application Programming) work?

A: Unlike other programming languages, ABAP code is stored in the database. When it’s time to execute an ABAP function, the system pulls the code from the database, compiles it, and runs it. This is why it has been more difficult in the past to understand the root cause of performance issues because the code is tucked away within the database. The code itself is also highly dependent on the database and other SAP application components.

 

Q: How is the agent different than traces on SAP?

A: Traditionally, a SAP admin would manually start a trace to capture data.  They would leave that trace (along with the associated overhead) running for some amount of time. AppDynamics effectively automates that functionality and correlates that data to the Business Transaction. With AppDynamics, traces are started only for isolated transactions, not globally. The data that is returned from an individual trace on SAP is presented in a silo without business context and visibility end-to-end.

 

Q: How does the AppDynamics Setting screen get into SAPGUI in order to configure the ABAP agent?

A: When you start the transfer request, all programs and screens are imported. You will place the files in the transport queue on the SAP system. The import needs to be done once per SAP system, not per application server.

 

Q: Where do I configure the ABAP agent in SAPGUI?

A:  Instrumentation is completed through the AppDynamics Settings in SAPGUI, which is located under the  /DVD/APPD_CUST transaction code. From here, you will connect to your AppDynamics Controller and and configure the SDK settings. For detailed instructions and screenshots to guide you, review the following three resources:

 

Q: Does the ABAP language support dynamic bytecode instrumentation?

No, the ABAP language doesn’t support it so you will not be able to intercept arbitrary ABAP commands during runtime. However, you can still make manual code adjustments, like custom actions and RFC exit calls. For instructions, see Instrument Custom ABAP Code.

 

Q: How does the ABAP Agent decide when to enable a trace?

A: An ABAP trace is initiated when requested by the SDK. A SQL trace is started at the same time.

 

Q: What is the performance overhead of the ABAP Agent?

A: The performance overhead varies. If you look at the traces, we capture the overhead that we introduce. When we instrument a really fast transaction, the overhead will be a higher percentage than when we instrument a slow transaction. A lot of the data collection is done out-of-band so is minimal impact on the actual performance of the transaction. Much of the trace correlation is done asynchronously.

 

Additional Resources

Version history
Revision #:
4 of 4
Last update:
‎05-16-2018 12:57 PM
Updated by:
 
Labels (1)
Tags (3)
0 Kudos