Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on
05-15-2018
04:35 PM
- edited on
01-13-2022
07:46 PM
by
Claudia.Landiva
SAP applications have different supported versions, platforms, and functionality. Therefore, there are different supported protocols used for communication between SAP systems and external applications, as well as different supported user interface technologies. Depending on your application and platform, you will have Analytics, Business Transactions, or both.
For details on supported environments and functionality, see SAP Supported Environments.
The visibility currently available differs from what you are familiar with. Every SAP application server is tightly coupled to a database and all code uses that database. The node that displays in the flow map includes the application server and database.
In ABAP, there is no specific protocol to access the database since it's tightly coupled. You can monitor the databases with database monitoring and view information but that information isn’t tied in with the flow map.
Also, you can’t implement the instrumentation and inject your own code at runtime in ABAP as you can in Java; it can only be done at compile time. There are specific static implicit enhancement points where you can inject, typically at the beginning or end of a method.
Additionally, you can’t inject code at SQL execution since this is happening inside the SAP kernel rather than in ABAP.
Baselining is done on the complete Business Transaction, not the individual RFCs. However, if you configure a Business Transaction for a specific RFC, you will get a baseline of that RFC.
This information is listed in the snapshot properties under the URL section.
This data comes directly from SQL traces on the SAP System or the Expensive Statement Trace on HANA (tcode DB02).
How is this solution different than Syslink Xandria's solution? (www.syslink-xandria.com)
Hello, Kevin. The Xandra product uses synthetic transactions to verify that things "should" work when a user tries to execute a transaction (similar to AppDynamics Synthetics on web applications). The issue is that when things don't work, why are they failing? AppDynamics for SAP does transaction tracing from end to end, and we do deep monitoring of the SAP components in both Java and ABAP to help identify the root cause of the issues. This means we look at every transaction from web, mobile, and SAPGUI.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form