In case of data collection issues you will need to troubleshoot Simple Diagnostic agent logs .
In some cases you might need to get further details after you see an error message in the standard SDA logs in Agent Internals. In such cases you will need to enable application specific logging. E.g. activate debug logging in order to analyze issues with a specific application or component of the SDA
For E.g.: You saw an error in agent internals like
2019-08-15 15:48:01,696 ERROR [MAI FRD 5] com.sap.solman.agent.mai.http.WebDispGetServerListCollector com.sap.solman.agent.mai.cim.EvaluationException: division by zero at com.sap.solman.agent.mai.cim.ExpressionEvaluator.evaluate(ExpressionEvaluator.java:72)
In this case, you will want to put to debug this class: com.sap.solman.agent.mai
Following Application components of SDA for which logging can be enabled.
Application / Component
Name (Column in Log Configuration Dialog)
JCo
com.sap.solman.agent.conn.jco
MAI
com.sap.solman.agent.mai
SDA Core
com.sap.solman.agent.core
SSL
com.sap.solman.agent.core
SLDR
com.sap.solman.agent.sldr
To enable logging you can follow the following steps.
Step 1 : Open Agent Administration in Focused Run Launchpad.
Step 2: Select the agent/host for which you want to enable logs in Debug, on the option Agent Action select “Open Log Configuration” and click on Go.
In the next dialog screen enter the application classes for which you want to enable debug as shown below. After entering the classes click on Save.
In the next execution, the Agent logs will present more details.
You can collect the log files by selecting the Option Download Log File and then click on Go. It will download all SDA logs in a zip file to your desktop/laptop.
Note: Do not forget to remove the log configurations after downloading the logfiles.
You may need to connect the same managed system to more than one Focused Run System. For instance, connecting a sandbox managed system to a development Focused Run system for test purpose and to a production Focused Run system where it is actually monitored.
In our previous blogs we have explained how you connect an SAP ABAP or SAP JAVA system to a focused run system and perform the Simple System Integration (SSI).
For connecting the same system to one more Focused Run system you basically need to perform the same steps again but this time targeting to the new Focused Run systems.
Perform host outside discovery to register the host on focused run system. Execute the following commands using the credentials of the new focused run system to which you want to connect the managed system.
On the new Focused Run system agent administration configure the agent on the host you registered in previous step..
Install/Update Agent
2. Configure Agent
Note: The agent installation will not deploy a new SDI binary to the hostagent in this case as there is already a SDI in the host agent coming from the previous Focused Run system. However the installation step will simply link the new Focused Run system to the existing SDI by pushing its new configuration XML file to the SDI. This you can check by logging on to agent internals.
Configure SLDR to send data to both Focused Run Systems. This the most important step that you do differently than connecting the managed system to the first Focused run system. This will ensure data suppliers from managed system get forwarded to both Focused Run systems. Two know more about SLDR setup you can follow the SAP documentation here.
Now update the data supplier settings of the managed system to send data to this SLDR .( For example RZ70 in SAP ABAP system and NWA in SAP JAVA system).
Now the managed system will be listed in the Simple System Integration app of the new Focused Run system. Configure the SSI of the managed system to enable the managed system in the new Focused Run systems monitoring.
Deploying Simple Diagnostic Agents (SDA) on Managed System hosts is a prerequisite to performing Simple System Integration (SSI) of Managed systems on focused run system.
The SDA is installed/deployed as an add-on to the SAP host agent. Hence it’s mandatory to install SAP Host Agent on each host of the managed system which needs to be monitored by SAP Focused Run System.
The deployment of the SDA on the managed system system host is carried out from the SAP Focused Run system itself.
Below steps need to be performed for deploying SDAs on managed system hosts.
Download binaries from marketplace
Download the latest version of the binaries SDA and SAP JRE (Java Runtime Environment) from SAP Support Portal as follows:
Select tab Support Packages & Patches –> By Category –> SAP Technology Components –> Focused Run –> Focused Run 3.0 –> Downloads –> Comprised Software Component Versions
Download from SAP JRE 8.1 and SIMPLE DIAGNOSTICS AGENT 1.0
Following platforms are supported
IBM AIX
HP-UX on IA64
Linux on Power BE & LE
Linux x86_64
Oracle Solaris SPARC
Oracle Solaris x86
Microsoft Windows Server on x86_64
You can find all information regarding latest available version of SDA and its compatible JRE version in SAP Note 2369401 – Release Note for Simple Diagnostics Agent 1.0
Upload Binaries onto SAP Focused Run system
Upload the binaries to SAP Focused Run, by running the report SRSM_AMA_UPLOAD_BINARY, with transaction SA38.
Upon completion of the upload you will see the below output.
Deploy SDA on Managed system host
Register Managed system host on Focused Run system: Before you can deploy SDA on managed system host, the host has to be registered to the Focused Run System. For this execute the following script at OS level as sapadm user from folder /user/sap/hostctrl/exe
./saphostctrl -function ConfigureOutsideDiscovery -enable -sldusername FRN_LDDS_FRS -sldpassword xxxxxxxxxx -sldhost <hostname of FRUN system> -sldport <http/https port of FRUN system>
Upon executing the above commands at host level, you can see the host listed in Agent Administration of Focused Run system. Navigate to the Agent Administration app in the Infrastructure Administration block of the Focused Run launchpad.
In the Agent Administration App, select the host for which you want to deploy the SDA, select Install/Update Agent and click on Go.
Upon completion of the deployment, you will see the agent version listed in the Diagnostic Agent Version column.
After SDA installation/update is successful you also need to configure the agent. This will enable the agent to receive monitoring definitions from the focused run systems as well as enable Self Monitoring of the agent.
Upon completion of configuration, you will see green icon under availability column. Also Configuration status updated to Confirmed.
You need to follow the same steps for installing and configuring agents on all application server hosts as well as database hosts of the managed system.
Note: You should perform the Simple System Integration of a managed system only after you install and configure agents on all its hosts. You can also list hosts and their agent status of a particular managed system in the By Technical System tab of the Agent Administration app.
SAP Focused Run system collects performance metrics and trace data of the SAP Netweaver Java systems through the CA Wily Introscope Byte Code Injection (BCI) Adapter.
Before you perform SSI for a SAP JAVA system you need to install and configure the BCI Adapter on each instance of the Java stack
Upon installing the BCI Adapter, SAP JAVA system reports performance and trace data to the CA Wily Enterprise Manager (Wily EM) and later on SAP Focused Run monitoring will collect the data from Wily EM for the relevant monitoring metrics.
Unlike SAP Solution Manager, for SAP Focused Run BCI Adapter setup for managed system is a completely manual step. This blog is therefore intended for the technical or SAP BASIS consultants who are responsible for installation and setup of SAP Focused Run system.
The following steps are required to install and configure the Introscope Agent
Extract the Introscope Agent files
Configure the Introscope Agent
Introscope-enable the application code by setting Java VM parameters
Pre-Requisite
The BCI Adapter needs to connect to a Wily Enterprise Manager. You must ensure the Wily Enterprise Manager is already connected and configured for your SAP Focused Run system. In our blog we have explained how to configure Wily EM to connect to a Focused Run system.
Extract the agent installer file ISAGNTJ5STD*.zip into the Netweaver CCMS directory, usually: :\usr\sap\ccms.
Upon extracting you will find wily directory in the :\usr\sap\ccms directory
Configuring Introscope Agent Settings
For a SAP JAVA System the agent configuration settings are found by default in the file :\usr\sap\ccms\wily\core\config\IntroscopeAgent.profile.
To configure the Introscope Agent you need to locate the following parameter and set the values.
1. introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT = <IP address or hostname of the Enterprise Manager
2. introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT = <port on which the Enterprise Manager listens for Agent connection. Default is 6001>
3. introscope.autoprobe.directivesFile = < DEFAULT is sap_typical.jar,sap_ep.jar,sap_ep_iviews.jar,sap_xi_typical.jar > . You may need to add further duirective jar files by adding entries to the property, separated by comma.
Below table shows the various directive file names for various java application types.
sap_typical.jar
Main instrumentation set for SAP Netweaver. Includes support for generic Netweaver functionality, like database, JCO, Web Services. This jar is always mandatory.
sap_sapvm.jar
For SAP Netweaver 7.10 and higher with JDK5 or higher. Specific instrumentation, e.g. memory allocation. Do not activate for Java 1.4!
sap_bo_enterprise.jar
SAP Business Objects Enterprise 3.x instrumentation
sap_boe_webapp.jar
SAP Business Objects Enterprise 4.x instrumentation
sap_ep.jar
SAP Portal specific instrumentation
sap_ep_iviews.jar
AP Portal instrumentation: One node per iView – should be preferred for installations with many roles or when collaboration rooms are used. Requires sap_ep.jar
sap_ep_iviews_rolename.jar
Re-activate metrics for each iView/rolename combination. Activate only one of these 2: sap_ep_iviews.jar or sap_ep_iviews_rolename.jar!
sap_duet.jar
SAP Duet specific instrumentation
sap_hybris.jar
Instrumentation for Hybris.
sap_smp.jar
Instrumentation for SAP Mobile Platform.
sap_omnichannelbanking.jar
SMP instrumentation extension for Omni Channel Banking
sap_xi_typical.jar
Default and mandatory instrumentation file for PI
sap_xi_adapters.jar
Extended instrumentation for PI adapters.
sap_xi_passport.jar
Extended PI instrumentation to detect passport propagation.
sap_xi_full.jar
Extended instrumentation for PI. Some of these metrics might have a performance impact
sap_smd.jar
Solution Manager self-monitoring
sap_mdm.jar
SAP Master Data Management
sap_compliance.jar
SAP Compliance (SAP GRC, SAP EC, SAP REACH, …)
sap_epm.jar
SAP EPM (SAP SSM, …) instrumentation
sap_retail.jar
SAP Retail (SAP POS, SAP Triversity…)
sap_hilo.jar
SAP Visual Intelligence instrumentation
sap_srm_crm.jar
SAP SRM & SAP CRM (SAP Convergent Charging, SAG Frictionless e-Commerce, …)
sap_manufacturing.jar
SAP Manufacturing (SAP SAP Manufacturing Execution, SAP xMII, …)
Sap_hadoop.jar
SAP Hadoop instrumentation
sap_partner.jar
Instrumentation for SAP partner products. See SAP Note 1852015.
sap_tomcat_typical.jar
Default and mandatory instrumentation file for Apache Tomcat
sap_tomcat_full.jar
Extended instrumentation for Apache Tomcat
sap_websphere_typical.jar
Default and mandatory instrumentation file for IBM WebSphere Application Servers
sap_websphere_full.jar
Extended instrumentation for IBM WebSphere Application Servers
sap_weblogic_typical.jar
Default and mandatory instrumentation file for Oracle WebLogic Server
sap_cem_integration.jar
Instrumentation for integration with CA product CEM (only for SED)
Activating the Agent: Set Java VM Parameters
You have to add Java VM options to enable the agent. Typically, you will only want to activate the agent on the SAP J2EE server nodes, not on dispatchers.
You need to set the following parameters for the Java VM.
Run the SAP J2EE Configtool.
Navigate to Instance/VM Parameters/System and enter the following new parameters
3. Navigate to Instance/VM Parameters/Additional and enter the following new java parameter
-javaagent:/usr/sap/ccms/wily/Agent.jar
4. Save and Repeat steps 1 to 3 for all instances of the SAP JAVA system.
5. Restart the SAP instances.
To verify that Config tool changes were made, open the file: :\usr\sap\\\j2ee\cluster\instance.properties and check for a line beginning with ID.JavaParameters, and see if it contains the lines you entered in the step above.
You need to ensure the below pre-requisites are met which are same as the pre-requisite for for performing SSI of ABAP systems.
Focused Run Prerequisites
Before you can perform SSI for any managed system, you need to ensure the basic framework setup prerequisites are met. For this ensure all activities mentioned in section 5.2.4 Preparing Simple System Integration of the SAP Focused Run master guide.
Managed System Prerequisites
1.) Simple Diagnostics Agent deployed on all hosts of Java Managed system.
In this blog we have explained the steps for deploying SDAs on managed systems.
2.) JAVA Managed system is registered in LMDB and Data Supplier Completeness check is green.
In our future blogs we will explain how to register various types of managed systems into LMDB. And for troubleshooting in case Data Supplier Completeness check is not green, you can follow SAP’s documentation here.
3.) Database preparation is complete.
You need to perform certain database specific pre-requisite configurations in order to perform the integration of the underlying database of the managed system. In this SAP documentation SAP has outlined the steps for various types of databases.
4.) A system user is created in the managed system. This user will be required to authenticate local HTTP and P4 calls by the simple Diagnostics Agent for data collection. We refer to this user as FRUN user.
You can refer to this SAP documentation to get the list of roles that needs to be assigned to this FRUN user.
Additional Pre-requisite for JAVA Managed Systems.
Other than the above mentioned pre-requisites, for JAVA systems, you also need to Install BCI Adapter ( CA Introscope Wily Adapter) to collect performance metrics and trace data of the NW Java.
In this blog we explain how to install and configure the BCI Adapter for Java systems.
You can also refer to section SAP NetWeaver Application Server Java in this SAP Focused Run expert portal blog for managed system preparation.
Performing SSI of JAVA managed system
For executing SSI navigate to the SSI app in the Infrastructure Administration section of the Focused Run launchpad.
In the SSI app scope selection area you can enter the managed system extended SID individually or you can select a more generic filter to list multiple systems.
SSI is performed in 2 steps for JAVA managed systems.
Step 1: Edit Configuration
In this step you provide the credentials for the SDA agent to connect to JAVA Managed System.
The FRUN User and password you created as a pre-requisite
The HTTP and P4 ports for connecting to the Java managed system.
Step 2: Configure Automatically
In this step, select the JAVA managed system for which you want to perform the SSI and click on the button Configure Automatically.
Note: When you perform SSI for the main technical system , it will automatically perform the SSI for all the underlying components in the system hierarchy. That is, if you perform SSI for Application Server JAVA, it will also perform the SSI for the system’s database. However the if you perform first the SSI of the system’s database it will not automatically perform the SSI of the main technical system and you will again have to perform the SSI for the technical system again separately.
Simple System Integration (SSI) of SAP ABAP Systems made easy.
For activating SAP Focused RUN monitoring functionalities on an SAP ABAP system you need to perform Simple System Integration of SAP ABAP Systems
Simple System Integration, or shortly known as SSI, is a guided procedure similar to the managed system setup in SAP Solution Manager. SSI is used for integrating a managed system to SAP Focused Run system. Unlike SAP Solution Manager managed system setup, SSI is fully automatic and has no manual steps.
In order to ensure SSI is completed successfully we need to ensure all -prerequisites are met.
Focused Run Prerequisites
Before you can perform SSI for any managed system, you need to ensure the basic framework setup prerequisites are met. For this ensure all activities mentioned in section 5.2.4 Preparing Simple System Integration of the SAP Focused Run master guide.
Managed System Prerequisites
1.) Simple Diagnostics Agent deployed on all hosts of ABAP Managed system.
In this blog we have explained the steps for deploying SDAs on managed systems.
2.) ABAP Managed system is registered in LMDB and Data Supplier Completeness check is green.
In our future blogs we will explain how to register various types of managed systems into LMDB. And for troubleshooting in case Data Supplier Completeness check is not green, you can follow SAP’s documentation here.
3.) Database preparation is complete.
You need to perform certain database specific pre-requisite configurations in order to perform the integration of the underlying database of the managed system. In this SAP documentation SAP has outlined the steps for various types of databases.
4.) A system user is created in the managed system production/main client. This user will be required for RFC connection to the managed system. We refer to this user as FRUN user.
You can refer to this SAP documentation to get the list of roles that needs to be assigned to this FRUN user.
Performing SSI of ABAP managed system
For executing SSI navigate to the SSI app in the Infrastructure Administration section of the Focused Run launchpad.
In the SSI app scope selection area you can enter the managed system extended SID individually or you can select a more generic filter to list multiple systems.
SSI is performed in 2 steps for ABAP systems.
Step 1: Edit Configuration
For ABAP systems in this step you need to enter the details of the FRUN user that you created as a prerequisite.
For this select the row for the ABAP system and click on the Edit Configuration button as shown in below screenshot. Next in the pop-up enter the credentials of the FRUN user.
Step 2: Configure Automatically
In this step, select the ABAP managed system for which you want to perform the SSI and click on the button Configure Automatically.
Note: When you perform SSI for the main technical system , it will automatically perform the SSI for all the underlying components in the system hierarchy. That is, if you perform SSI for Application Server ABAP, it will also perform the SSI for the system’s database. However the if you perform first the SSI of the system’s database it will not automatically perform the SSI of the main technical system and you will again have to perform the SSI for the technical system again separately.
Mass SSI
Focused Run also provides even higher level of automation by allowing to perform SSI at a time for multiple systems. Mass update is explained in this blog.
Once the SSI automatic activities finish, you can check the logs of the SSI automation steps in the Log Messages area.
In our future blog we will explain details of each step in the Configure Automatically guided procedure of SSI and how to troubleshoot in case of error.
In our future blogs we will also explain how to perform SSI for various system types.
