Discussion Feed

If you continue to experience issues with AppDynamics for SAP after following the steps in our AppDynamics for SAP troubleshooting article, our Support team may need to access your SAP system. For this purpose, SAP provides an “SAP Service Backbone” infrastructure. This is the way our Support team can help debug issues with your SAP Basis team. In this case, the frontend is the SAPGUI client.   In these instances, please create a ticket (“OSS incident” in SAP terminology) following these steps:   1. Go to https://support.sap.com/en/index.html    2.  Log on using the S-user account (#1 in the screenshot above), which is maintained by your SAP Basis team.   3. Click the “Report an Incident” link (#2 in the screenshot above).   4. Search for an answer to the issue before creating a case by typing into the “Enter search term” field.   5. Click the button to “Submit an Incident.”       6. On the next screen, identify the system where the problem occurred. You can choose from recently used systems or search available systems (#1 in the screenshot below).   7. Once the system is selected, you will see its status: Access data available/missing (i.e. username, password, and validity) Connection opened/closed Clicking the links allows you to maintain these properties.   8. Provide incident details. Note: Do not change the priority to a level higher than Medium.   9. Important – Select the proper component (#1 in the screenshot below), which means XX-PART-DVD . It ensures that the OSS incident is dispatched to the Datavard incident queue.   10. Finally, click the “Submit” button (#2 in the screenshot above) and the OSS incident will be sent to us. If everything is set up correctly, we will be able to start assisting with the analysis in 15-20 minutes. ... View more

This article guides you through how to troubleshoot two types of AppDynamics for SAP issues: Missing Tier in the Dashboard Missing Metrics   Missing Tier in the Dashboard 1. Check if the monitored system is running and available to be logged into. If it’s not, contact your SAP Basis team. You may need to work with your SAP Basis team to verify this. If the monitored system is not running and/or logging in is not possible, the system may be down.   2. If the ABAP agent causes the system dump, deactivate the integration (/DVD/APPD_CUST). Execute the /DVD/APPD_CUST transaction to open the AppDynamics settings screen.     Please don't change any other settings. Only if the ABAP Agent itself is causing system dumps can you deactivate the integration using the steps below: Click the “Display <-> Change” button in the top-left of the menu bar to transition into edit mode. You’ll notice the UI changes. Click the “Deactivate integration” button, which will deactivate the integration immediately.   3. Check the HTTP SDK Proxy status (transaction /DVD/APPD_STATUS) and take the proper action to remedy. Execute the /DVD/APPD_STATUS transaction to open the AppDynamics SDK status screen. From here, you can: Check if the HTTP SDK proxy is reached. Check if the process is running. Start/Restart the process. Stop the process. Read logs - From the “AppDynamics HTPP SDK proxy log files” screen, you can save the logs to the local file and send them to Datavard for analysis.     Missing Metrics 1.  Check Insights integration (transaction /DVD/APPD_CC) Execute the /DVD/APPD_CC transaction to open the “Select Insights KPI for AppDynamics” screen. Here you can verify that the “Enable AppDynamics Insights connector” box is checked. If it’s not, enter edit mode by clicking the “Display <-> Change” button in the menu bar and enable it. Ensure you save the changes and check if the metrics start replicating from “Insights KPIs.”     ... View more

To begin, execute the /DVD/MON transaction to open the Datavard Insights cockpit. Here you can check if the monitoring jobs are running and collecting the KPIs correctly.   As shown in the screenshot below, look at the “Status icon” and “Job Status” columns in the “Collector Jobs” tab and the graphs in the “KPI charts” tab.   ... View more

The SAPGUI client is available for MS Windows OS (written in C++/C#) and for MacOS (written in Java). The Windows version is preferred because of its stability, performance and better Office integration.   In the SAPGUI window, look for “Command Bar” the field. This is where you will type in the required tcode prefixed by /n if you want to reuse the existing SAPGUI window or /o to open a new window.     Example In this example, you want to execute the /DVD/MON  transaction. If you want to reuse the SAPGUI window, type in /n/DVD/MON and hit Enter. If you want to open a new SAPGUI window, type in /o/DVD/MON and hit Enter.   Troubleshooting When working with SAP transactions, you have two options for troubleshooting that do not require us having direct access to your system or SAP Service Backbone: You can provide Support with supervised remote access, for example, WebEx, based on your organization’s security policies (preferred). If you are experienced in running transactions from within SAPGUI, you can work with Support to execute the transaction and share the results. ... View more

Table of Contents Does AppDynamics for SAP use the standard SDK? Do I need to install the C++ SDK separately? When using a separate Linux box, what “starts” the C++ SDK? Does the C++ SDK run on PowerPC hardware? Do I need to install a separate file to enable support for JCo? Additional Resources   Q: Does AppDynamics for SAP use the standard SDK? A: Yes, this is the 4.4 SDK.   Q: Do I need to install the C++ SDK separately? A: No, running the HTTP SDK proxy that is in the SAP download includes the C++ SDK inside of it. For instructions on installing the C++ SDK and HTTP SDK proxy, click here .   Q: When using a separate Linux box, what “starts” the C++ SDK? A: The HTTP SDK proxy will call the C++ SDK, so there is no need to start anything other than the proxy.   Q: Does the C++ SDK run on PowerPC hardware? A: No, our C++ currently only runs on Intel.   Q: Do I need to install a separate file to enable support for JCo? A: Yes, you will need to copy the SAP_JCO_iSDK.jar file to the sdk-plugins directory of the Java Agent. This enhanced protocol support is added via our Java iSDK. This will allow us to catch Java calls to the SAP System via RFC protocol. For instructions on enabling Business Transaction correlation with SAP JCo, click here .   Additional Resources Introducing AppDynamics for SAP SAP Monitoring FAQs - ABAP Agent SAP Monitoring FAQs - Functionality and Visibility ... View more

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: Set up SAP ABAP Agent. Configure HTTP Transaction Detection Connect to AppDynamics   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 Introducing AppDynamics for SAP SAP Monitoring FAQs - Functionality and Visibility SAP Monitoring FAQs - C++ SDK and JCo ... View more

Table of Contents What monitoring capabilities are available for SAP applications? Do flowmaps provide visibility into databases? Can I baseline specific RFCs? Where can I see which RFC was called? Where does the SQL Statement data in Data Collectors come from? Additional Resources   Q: What monitoring capabilities are available for SAP applications? 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 . ( Please note that AppDynamics for SAP doesn’t yet work with Business iQ.)   Q: Do flowmaps provide visibility into databases? A: 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 flowmap 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 flowmap. In ABAP, you can’t do the instrumentation and inject your own code at runtime like you can in Java; it can only be done at compile time. There are specific static Announcement 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.     Q: Can I baseline specific RFCs? A: 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.   Q: Where can I see which RFC was called? A: This information is listed in the snapshot properties under the URL section.   Q: Where does the SQL Statement data in Data Collectors come from? A: This data comes directly from SQL traces on the SAP System or the Expensive Statement Trace on HANA.   Additional Resources Introducing AppDynamics for SAP SAP Monitoring FAQs - ABAP Agent SAP Monitoring FAQs - C++ SDK and JCo ... View more

Overview AppDynamics for SAP helps ensure that all of your SAP applications are performing well and that your business is successfully operating by providing an understanding of the availability and performance of these systems. The key capabilities of this offering are transaction tracking and transaction correlation. When there is a slowdown, AppDynamics isolates which component is slow and provides the code-level visibility necessary to diagnose the problem, down to the ABAP code. We also provide dashboards and views of the complete system, including our flow map that shows an overall view of application components. There are also dashboards for specific personas who are interested in the SAP technologies themselves. As a performance monitoring tool, we want to ensure we are not adding too much burden to the system we are monitoring so we automatically limit our capture to keep overhead low. When we see specific issues, we take snapshots that provide a lense into the slowness.  For a complete list of SAP-supported environments, click here.    With AppDynamics for SAP, you get: Flow maps that reveal dependencies with real-time views of every component Manually defined and auto-detected Business Transactions for end-to-end application context Dashboards that show the health of SAP components and databases (relational or HANA) Insight into the baseline performance of transactions starting in, passing through, or ending in SAP Transaction snapshots when performance deviates to analyze application and system errors Monitoring of ABAP and associated database queries made from ABAP to identify the cause of slowness Dynamic baselines that detect performance anomalies and help you take action based on resulting health alerts The ability to adopt S/4HANA on-premises or in the cloud with less risk, plan migrations more effectively, and measure post-migration results   Implementation SAP monitoring is made up of two components: the ABAP Agent and SAP Analytics. The installation process varies depending on if you are using a Linux or non-Linux OS. The AppDynamics C++ SDK requires Linux OS. If you are using another OS, you will need to install the AppDynamics C++ SDK on a separate machine (Gateway system). Deployment instructions and architecture overviews are available here: Install SAP Agent Monitoring .   Note: SAP monitoring is available for AppDynamics version 4.3 or later with the applicable licenses .   You can also enable Business Transaction correlation for Java applications that communicate with SAP systems using SAP JCo. The package supports both Java to SAP System and SAP System to Java calls: Enable Business Transaction Correlation with SAP JCo   Viewing metrics Within the Application section of your Controller, open the Application Dashboard to review flow maps of SAP components and monitor key performance metrics with the Transaction Scorecard.   Build custom dashboards to monitor tier and node health, such as processes, utilization, and problematic background jobs.   FAQs For answers to your most common questions about SAP monitoring, visit the links below: SAP Monitoring FAQs - Functionality and Visibility SAP Monitoring FAQs - ABAP SAP Monitoring FAQs - C++ SDK and JCo ... View more