On this page:
On this page:
- ABAP agent (includes Datavard Insights)
- HTTP SDK and related components
- Machine agent
Install ABAP Agent
You install the ABAP agent on the SAP system by importing standard SAP transport requests. The installation requires several transport requests to be imported in the correct order due to dependencies.
Check your SAP NetWeaver release, before the installation. There are two ABAP agent versions:
- ABAP agent for NetWeaver earlier than version 7.4.0
- ABAP agent for NetWeaver version 7.4.0 or later
Import SAP requests into production systems when the traffic and load are minimal. It is recommended to import SAP requests outside of business hours or during weekends. ABAP Agent takes advantage of several enhancements placed in standard objects that trigger the recompilation of these objects during import.
This affects SAP standard HTTP client, HTTP server, SOAP handler, BSP controllers, UI5 apps, WebDynpro pages, WebGUI pages, SAP Gateway/Backend, ST05 trace, Application Log, and Read Access Log.
Install SAP NetWeaver Earlier Than Version 7.4
To install the ABAP agent without import errors with RC=8, import the following transport requests in the sequence:
- Datavard Reuse Library
- Datavard Insights
- AppDynamics ABAP Agent Core
Install SAP NetWeaver Gateway Earlier Than Version 7.4
To install the ABAP agent on the NetWeaver Gateway system, import the following transport requests on both front end and back end systems:
- All transport requests for ABAP Agent and Datavard Insights on SAP NetWeaver
- AppDynamics BEP instrumentation
Install the Agent on SAP NetWeaver Version 7.4 or Later
To install the ABAP agent on SAP NetWeaver 7.4 or later, import the following transport requests:
- Datavard Reuse Library
- Datavard Insights
- AppDynamics ABAP agent 7.4
For IS-U systems, the following transport request can be imported on top of previously listed transport requests:
AppDynamics ABAP agent for IS-U
Install the Agent on SAP NetWeaver Gateway Version 7.4 or Later
SAP NetWeaver 7.4 includes NW Gateway, so the instrumentation is part of ABAP Agent version 7.4. Use the same transport requests for all SAP NetWeaver version 7.4 or later systems.
If you have a separate NW Gateway system version 7.4 or later, the installation steps are the same as all ABAP version 7.4 systems. See Instrument NetWeaver Gateway.
Datavard Insights Authorizations
To authorize a user to start the Datavard Insights monitoring tool, add the user to the /DVD/MON_ADMIN role. The role is part of the Datavard Insights transport request.
ABAP Agent Authorizations
To authorize a SAP user to administer the ABAP agent, add the user to the /DVD/APPD_ADMIN role.
Role /DVD/APPD_USER exists as a subset of the Admin role and allows execution of certain ABAP agent and SAP components (start, stop, collect SQL trace, call AppDynamics RFC Function Modules from external systems, etc.). The User role is meant for users to be monitored and technical users utilized during RFC calls. The roles are part of the AppDynamics ABAP agent transport requests.
New elementary and composite authorization roles are available since ABAP Agent version 4.5.1911. The composite roles consist of all relevant elementary roles and are intended to replace user role /DVD/APPD_USER:
- Intended for all SAP users and technical users utilized during RFC calls from Java (via JCo)
- Contains all elementary roles listed below
- Intended for all other users (non-technical and technical) that are not involved utilized during any RFC calls from Java (via JCo)
- Contains all elementary roles except /DVD/APPD_RFC_JAVA
Elementary roles exist to provide necessary authorizations for a specific area. When one of the composite roles cannot be used, it is possible to choose specific elementary roles instead, but this limits the ABAP Agent functionality in certain ways. Impact of omitting an elementary role is explained under Not assigned bullet points.
- Purpose: allows assigned users to call RFC function modules from /DVD/* function groups
- Needed for: RFC correlation between ABAP Agents
- User groups: Users utilized during RFC calls or assigned to RFC destinations; all users when RFC destinations with trust relation are used
- Not assigned: RFC exit calls from ABAP Agent business transactions generate run-time errors, but do not affect the end-user
- Fallback: This role is necessary for smooth ABAP Agent operation, but the impact of the missing role is mitigated by automatic temporary RFC destination blacklisting
- Purpose: allows assigned users to call RFC function modules from function groups SRFC, SUNI, SYST
- Needed for: RFC correlation between Java Agent with JCo plugin and ABAP Agent
- User groups: users utilized during RFC calls or assigned to RFC destinations called from Java systems using JCo
- Not assigned: RFC exit calls from Java Agent business transactions generate run-time errors, but do not affect the end-user
- Fallback: this role is necessary for smooth JCo plugin and ABAP Agent operation, but the impact of the missing role is mitigated by automatic temporary RFC destination blacklisting
- Purpose: allows assigned users to start, stop, and process SQL trace (ST05)
- Needed for: Top 5 SQL statements in business transaction snapshots
- User groups: all users
- Not assigned: full business transaction snapshots may not contain Top 5 SQL statements, application log error messages will be written
- Fallback: uncheck Include SQL trace into snapshots checkbox in Snapshot settings. If the primary database is HANA, Include SQL trace into snapshots and Always use HANA expensive statements can both be checked to omit ST05 trace completely
- /DVD/APPD_TRACE_ABAP_AUTO or /DVD/APPD_TRACE_ABAP_MANUAL
- Purpose: allows assigned users to delete ABAP trace (SAT) files generated by ABAP Agent
- Needed for: Housekeeping after collecting Top 5 ABAP statements or call graphs in business transaction snapshots
- User groups: all users
- Not assigned: ABAP trace files generated by ABAP Agent will not be deleted at the end of the business transaction
- Fallback: when /DVD/APPD_TRACE_AUTO cannot be used, use role /DVD/APPD_TRACE_ABAP_MANUAL and carry out necessary manual steps described in the role long text. When none of these roles can be used, trace files generated by the ABAP Agent is automatically deleted by ABAP Agent housekeeping job on a daily basis
Make sure that all /DVD/APPD* authorization roles have an active generated profile for the current role version. This can be checked and adjusted via t-code PFCG on the Authorizations tab.
Install the HTTP SDK
Installation steps depend on SAP application server Operating System (OS):
- For supported application server OS, see Installing HTTP SDK Automatically.
- For unsupported OS, see Installing HTTP SDK Manually.
SSL Communication with On-premises Controllers
HTTP SDK is delivered with a default certificate used for SSL communication with SaaS controllers only. A custom SSL certificate must be installed if you want to use SSL communication with the On-premises controller. Installation steps depend on how HTTP SDK was installed.
- For HTTP SDK installed automatically, see Install Custom Certificate for Local HTTP SDK.
- For HTTP SDK installed manually, see Install Custom Certificate for Remote HTTP SDK.
Install the AppDynamics Machine Agent
The Machine Agent collects the OS performance metrics, such as CPU, RAM, disk, and network, for the SAP application servers. Datavard Insights uses the Machine Agent to report SAP-specific events. Install the Machine Agent on all SAP application servers and enable the HTTP listener.
Enable Machine Agent HTTP Listener
The Machine Agent HTTP listener is used to pass events from SAP system. Do the following when you install the standalone Machine Agent from the RPM package:
- To enable the HTTP listener, edit the
/opt/appdynamics/machine-agent/etc/sysconfig/appdynamics-machine-agentconfiguration file and add the following line:
JAVA_OPTS="-Dmetric.http.listener=true -Dmetric.http.listener.port=8293 -Dmetric.http.listener.host=0.0.0.0"
- Save the changes.
- Restart the Machine Agent service.
For a non-RPM installation, enable the HTTP listener of the machine. See Standalone Machine Agent HTTP Listener.