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