CA APM Introscope(R) is an application performance management solution created to manage Java Application performance. Unlike development tools, Introscope(R) is designed to scale with minimal performance impact. This allows you to monitor and manage your application performance in live production environments.
The Right to View (RTV) version of CA APM Introscope is a restricted, read-only form of the full product and is bundled with SAP Solution Manager. With the RTV version, support is limited to products that are licensed and supported by SAP. The instrumentation, dashboards, Probe Builder Directives (PBDs), management modules, and Smartstor data contained within the RTV version of CA APM Introscope as provided by SAP is the intellectual property of SAP. Use of these functions is restricted by SAP and may only be used in an unrestricted manner by licensing SAP Extended Diagnostics by CA, foundation from SAP.
In this Solution Manager setup step, you connect existing CA Introscope Enterprise Managers to SAP Solution Manager.
When discovering EMs these are made known to Solution Manager.
For this setup action some files of Enterprise Manager have to be read:
Also some files of the Enterprise Manager get edited by different Solution Manager setup steps:
Accordingly the user running the Diagnostics Agent assigned to the Enterprise Manager host has to have read/write permissions to the above listed folders and files.
In this automatic activity, you send the Data Provider Connector configuration to the CA Introscope Enterprise Managers. This information is required to enable CA Introscope Enterprise Managers to send data via the DPC push functionality to the SAP Solution Manager system. In other words the Enterprise Manger then knows to which Solution Manager(s) it has to send metrics to Monitoring and Alerting Infrastructure.
You may also see SAP Note 1751225 Introscope Push.
If the Diagnostics Agent assigned to the Enterprise Manager host got changed this activity has to be executed again.
In this step you can choose the Enterprise Manager which will be used by the managed system agents to report performance data.
The Enterprise Managers of type MoM (Manager of Managers) and Standalone are available to be chosen. The Enterprise Managers defined as Collectors will not be shown in this step. If a MoM scenario is configured, it is required to choose the MoM EM. In this case, the agents will connect firstly to the MoM EM and then they will be automatically redirected to a collector node.
In this automatic activity, you enable CA Introscope Enterprise Manager to aggregate performance metrics on system and instance level. System and instance level aggregates of selected metrics are used in system monitoring.
Introscope agents report metrics per Java node to the Enterprise Manager. By adapting the agentclusters.xml file, the Enterprise Manager is enabled to build instance and system level aggregates for selected metrics.
The Introscope Host Adapter (aka WilyHost agent) is an application which runs inside the SMDAgent. One of the tasks of the Introscope Host Adapter is to collect data from different configurable destinations and push them to the Introscope Enterprise Manager. The following picture provide a big picture of the architecture of the Introscope Host Adapter.
All applications running inside the SMDAgent are available in the Agent Administration UI. The Introscope Host Adapter can be found as shown in the picture below.
The resources used by the Introscope Host Adapter application can be found under the 'Application Resources' node:
Note: When using the application configuration take care when performing changes. Changes should not be performed in the scope GLOBAL unless they are strictly required. The changes in scope global affect ALL SMDAgents connected to the Solution Manager system.
In SAP Solution Manager, the Introscope Host Adapter is configured during the activity 'Introscope Host Adapter' of the Managed System Configuration for the target system: Step 7 "Finalize Configuration".
When the activity Introscope Host Adapter is performed, the application is configured to collect data from the managed system that will be monitored. The main files used by the agent are the following:
Note: No manual configuration must be performed to the above files. The activity Introscope Host Adapter will configure the application automatically.
The file SAPAgentConfig.xml holds the configuration of the Destinations and the Actions that will be used/performed to collect data from the managed system.
For a typical double stack system you will have configurations generated for the following destinations:
The following picture shows an example of a Jco destination. As you can see, the Jco destination has the connection information to the managed system, client, user, password, system number and hostname of the application server.
The following picture shows an example of some actions defined in a SAPAgentConfig.xml.
The SAPAgentConfig.xml fully configured looks as follows:
The following picture describes how the destinations and actions work in the managed system. As you can see, the destinations are the location where the data will be collected and the actions are the collections of data.
The file IntroscopeSAPAgent.profile holds the connection configuration to the Introscope Enterprise Manager. This file will tell the Introscope Host Adapter application what is the Enterprise Manager that the application must connect. The activity Introscope Host Adapter in the Managed System Configuration uses the IntroscopeSapAgent.profile.template file and then creates the IntroscopeSapAgent.profile. The following picture shows an example of IntroscopeSapAgent.profile.
If the Introscope Host Adapter applications shows issues, for example: agent is not connected to the Enterprise Manager or managed system metrics are not being collected. Then the SMDAgent logs must be checked to find out what is the root cause of the issue. The Introscope Host Adapter application may not work correctly due to distinct issues and the SMDAgent logs will show the root cause.
|Logging Information||Log File|
|Host Agent Information when trying to connect to the Enterprise Manage||/usr/sap/SMD/SMDA<xx>/work/jvm_SMDAgent.out|
|SMD Agent Application log file. All of the interesting logging for the Wily Host Agent will be found here||SMDAgentApplication.X.log|
|SMD Agent System log file||SMDSystem.X.log|
The Introscope Java Agent is a third party tool created by CA Technologies and is used in combination with the CA Introscope Enterprise Manager. The Introscope Java Agents and Introscope Enterprise Manager is used in the context of the SAP Solution Manager to collect performance information of Java applications, its main purpose is to collect data from the applications and systems running on Java Virtual Machines (JVMs), the data collected is pushed to the Introscope Enterprise Manager where it is stored.
The following picture shows the architecture of the Introscope Java Agents in SAP NetWeaver, but the same Introscope Java Agent is also used to monitor others SAP systems, for example: SAP Mobile Platform and SAP BusinessObjects Enterprise.
Each Introscope Java Agent release supports certain JVM versions. The following table provides an overview about the supported JVMs depending on the Introscope Java Agent release. The download location of the Introscope Java Agent is stated in the Introscope release notes.
It is not possible to connect Introscope Java Agents to an Introscope Enterprise Manager with a version lower than the agent's, i.e. do not choose an Introscope Java Agent with higher release than the Enterprise Manager for any Managed System.
The configuration of the Introscope Java Agent consists in the following steps:
Introscope Java Agent Profile
The configuration of the Introscope Java Agent is stored in the IntroscopeAgent.profile. The main properties configured in this file are as follows:
Auto Probe Directive Files
The Introscope Java Agent instruments the SAP JVM inserting probes (measurement points) on the Java byte codes during their executions. The measurement points are configured by the Directive Files (*.pbd), which are added in the IntroscopeAgent.profile. SAP provides standard Directive Files that should be used depending on the managed system type. The available Directives Files are mentioned in the IntroscopeAgent.profile of each release of Introscope Java Agent (check the section Directives Files of the profile file).
For NetWeaver systems, the configuration of the Auto Probe files is usually done automatically during the Managed System Configuration (activity Byte Code Adapter Installation). For non-NetWeaver systems, the required files are mentioned in the setup guides for each system type. Take care when changing the Auto Probe files configuration, as some Auto Probe files might cause a performance impact.
The Java parameters required to start the Introscope Java Agent are as follows:
-Javaagent:<path to the agent.jar file>
-Xbootclasspath: <path to connector.jar>;<path to the agent.jar file>
Refers to the Agent.jar file, used in systems with JVM 5 and higher.
Refers to the Auto Probe Connector and to the Agent.jar file. This parameter is used in systems running on JVM 4.
|-Dcom.wily.introscope.agentProfile=<path to the IntroscopeAgent.profile>||Refers to the IntroscopeAgent.profile which holds the agent configuration.|
|-Dcom.wily.introscope.agent.agentName=<AgentName>||Defines the name used by the agent to connect to the Enterprise Manager.|
SAP NetWeaver Java Systems
The configuration of the Introscope Java Agent of SAP NetWeaver systems is performed automatically by the activity "Byte Code Adapter Installation" in the step "Finalize Configuration of the Managed System Configuration". This activity extracts the Introscope Java Agent files to the server, configures the IntrosocopeAgent.profile and adds the required Java parameters to the Java server nodes.
Non-NetWeaver Java Systems
The Introscope Java Agent is also used to monitor Java systems that are not based on the SAP NetWeaver platform. The support and the configuration steps of these systems vary depending on the system type. Refer to the configuration guide of each system type in the Maintenance of Product in the System Landscape Wiki.
When the Introscope Java Agents are configured and started for the managed system, the Introscope Java Agent will create log files which will provide runtime information. The Introscope Java Agent log files are:
The location of the log files may vary depending on the configuration and system type, some example are below:
SAP NetWeaver Java Systems:
When the automatic setup is used for SAP NetWeaver Java systems (activity Byte Code Adapter Installation), the Introscope Java Agent log files will be available at \usr\sap\SMD\SMDA97\SMDAgent\temp.
If the Diagnostics Agents on-the-fly feature is used in the managed system, the flag "Deploy Byte Code Adapter under Managed System Instance(s)" must be selected during the Managed System Configuration. In this case the Introscope Java Agent log files will be located at /usr/sap/<ManagedSID>/<InstanceID>/ByteCodeAdapter/logs.
If the manual installation has been performed, the Introscope Java Agent logs are available by default in the following location \usr\sap\ccms\wily\logs.
SAP BusinessObjects Enterprise:
How to Read the Log
If the connection has been established successfully, the following entry is shown in the IntroscopeAgent* .log:
Connected controllable Agent to the Introscope Enterprise Manager at myhostname.domain.com:6001 [...]
Host = "myhostname", Process = "SAP Netweaver", Agent Name = "SMJ_J002_server0", Active = "true".
The above log entry shows the Introscope Enterprise Manager host name and port as well as the host name, the process name and the agent name used by the Introscope Java Agent to report the performance information. This information is useful in order to find the Introscope Java Agent in the Web View or Workstation Investigator. The following picture shows the Introscope Java Agent node in the Introscope Investigator:
Byte Code Adapter Does not Start
After performing the configuration of the Introscope Java Agent it is not possible to see the Java metrics in the Introscope Enterprise Manager. Refer to the Byte Code Adapter Does not Start wiki page.
Managed System Does not Start When Byte Code Adapter is Active
In case you need to disable the Introscope Agent in an emergency case, follow SAP Note 2246406.
JMX Metrics Missing in the Introscope Web View
If the JMX metrics are missing, the Early Watch Alert will be rated gray as metrics "APPLICATION THREADS" and "ACTIVETHREADSCOUNT" will be missing. Refer to SAP Note 2461965 (Missing metrics: Java performance data missing).
High availability is typically requested for the MoM of an Enterprise Manager (EM) cluster, but can also be implemented for a stand-alone EM. HA for collectors is less common because the assumption is that other collectors take over the load of a failing collector.
There are two approaches to achieve high availability of the EM:
EM Hot Failover
This solution is defined by Introscope and relies on features built into the Enterprise Manager. Two EMs are active at the same time and they negotiate which of them should be responsible for alerts etc. The setup is described in the Config and Admin Guide. Switching between the EMs relies on DNS changes. Unfortunately this approach cannot be used in combination with Solution Manager since the SMDAgent responsible for administrating the EM are not capable of supporting this.
Standard Approach based on HA software
The standard approach is to install services on a logical host and to switch this logical host between different physical hosts using some kind of HA software. This is supported by diagnostics agents and can also be used for Enterprise Managers. In comparison to the EM Hot Failover approach this approach causes the additional delay of starting the EM.
Introscope EM Setup
The following steps refer to Microsoft Cluster Services (MSCS) as HA solution. If needed adapt the procedure to your solution.
Connect EM to Solution Manager
Click User Management to set the connection user to the EM.
This section summarizes hints on upgrading the Introscope Enterprise Manager (EM). The focus is to run the upgrade in a way to minimize the effort on Solution Manager side.
Procedures for Solution Manager 7.2
With Solution Manager 7.2 you can install the EM into the same folder (after removing the old installation in that folder) or into a new folder. In any case the procedure will be the same:
Copy files from the old EM after an upgrade
Starting with Introscope 9 the CA Introscope documentation is delivered with the management modules and can be called on the EM via URL http://<EM_HOST>:<EM_HTTP_PORT>/IntroscopeHelp.
The Sizing and Performance Guide is part of the CA APM help (e.g. http://<EM_HOST>:<EM_HTTP_PORT>/IntroscopeHelp → Planning Information → Sizing and Performance Guide).
When the Introscope start to present Agent disconnection, missing metrics, Introscope stopping due memory issues or the connection limit is reached, the best option is install the Introscope on a cluster scenario. More details on this scenario can be found on:
http://<EM_HOST>:<EM_HTTP_PORT>/IntroscopeHelp → Planning Information → Sizing and Performance Guide → CA APM Environment Options → Clustered Environment
The installation and configuration details for Clustered Scenario, can be found in the Introscope Installation Guide.
ABAP kernel 7.20 and higher offer a functionality to collect performance data per function module, form, and method. This can be configured and viewed on ABAP side, and also be monitored with the Introscope Host Adapter. The steps to use it are described here.
Requirements and Setup on ABAP Side
The hot spots must be defined in table HOTSPOT_DEF. The entries can either be created with SE16 or via an XML file which can be uploaded with function module SHSTI_UPLOAD_XML.
Example of the xml file:
<?xml version="1.0" encoding="utf-8"?>
<!-- all Function Modules of the specified function pools-->
<hotspot prog="SAPLSHSTI" type="C" name="*" class="" component=""/>
<!-- specified Function Modules -->
<hotspot prog="SAPLTHFB2" type="C" name="TH_WP_DETAIL_INFO64" class="" component=""/>
<!-- Global Classes with specified method-->
<hotspot prog="CL_SOAP_RUNTIME_ROOT==========CP" type="" name="EXECUTE_PROCESSING" class="" component=""/>
Be careful with class names. They needs to be entered with runtime name, which means the name must end with the pattern ====CP. The number of '=' depends on the class name and must be filled until the complete length has 32 character.
After each change of instrumentation the kernel needs to know that a change of instrumentation happened. This can be done with function module SHSTI_START_TRACE( per Instance). Once the instrumentation is ready the hot spot measurement can be started automatically with each restart by setting profile parameter abap/hotspot_trace to auto.
The user SMDAGENT_<SOLMAN_SID> needs the authorization to execute function modules in function group SHSTI. In case the role template SAP_IS_MONITOR does not contain the authorization you need to enhance role ZSAP_IS_MONITOR (or the customer specific role) for authorization object S_RFC with following values:
ACTVT = 16
RFC_NAME = SHSTI
RFC_TYPE = FUGR
Setup on Introscope Host Adapter
Currently the corresponding action is not active by default. It must be configured manually. For this purpose, two changes must be done:
1. An ActionTemplate must be defined in the file WilyHostAgentTemplate.xml. This should be done by uploading a modified file into scope Global via agent administration. Here are the lines to be added:
<actiontemplate name="AbapHotspot" class="com.sap.smd.wily.hostagent.action.SimpleActionTemplate"method="SHSTI_GET_RESULTS2"
2. On each instance where the hotspot monitoring should be enabled an action must be defined in file SapAgentConfig.xml. This file exist in scope of the SMDAgent. The example snippet re-uses a destination SD7|ldai1sd7_SD7_89 that was already defined by the managed system setup. The RFC connection is then shared by the hotspot action and the standard Abap polling actions.
<action prefix="SD7|ldai1sd7_SD7_89|AbapHotspot" name="SD7|ldai1sd7_SD7_89 AbapHotspot" destination="SD7|ldai1sd7_SD7_89" template="AbapHotspot" />
<?xml version="1.0" encoding="UTF-8" ?>
<destination class="com.sap.smd.wily.hostagent.destination.JCODestination" name="SD7|ldcisd7_SD7_89">
<action prefix="..." />
<action prefix="SD7|ldcisd7_SD7_89|AbapHotspot" name="SD7|ldcisd7_SD7_89 AbapHotspot"destination="SD7|ldcisd7_SD7_89" template="AbapHotspot" />
The Introscope Investigator tree of the Introscope host agent contains an additional tree AbapHotsport under the instance. When selecting the instance node you get three additional tabs in the right area of the Investigator: Function Modules, Form Routines, Methods. Each tab displays a table of metrics for the corresponding category. Selecting a sub-node in the tree on the left automatically filters the graph/table to the selected subset.
Information to be Provided for Support Messages
The following items are required for support messages:
The mapping between Introscope versions and SAP versions of the Introscope delivery is as follows:
Additional Information to be Provided for EM Issues
EM Additional Diagnostics Options
To enhance the diagnostics options the following configuration changes are recommended (at least in case problems occur)
Enterprise Manager Log Files
Most relevant log files for problems with EM in sub directory logs are:
To get log out put with log level DEBUG in file IntroscopeEnterpriseManager.log replace line
in file file <EM_Home>/config/IntroscopeEnterpriseManager.properties.
On Unix platforms the file em.log in the EM home directory contains helpful information. All console output of the Java VM, including full thread dumps, goes here.
On Windows platforms the logs folder contains an additional file EMService.log. This is written by the Windows service wrapper and may contain important information in case the EM fails to start as Windows service.
Enterprise Manager Version
There are multiple ways to determine the EM version:
The log file IntroscopeEnterpriseManager.log contains the full version string at each startup of the EM. Example:
|8/23/12 09:49:47.289 AM MESZ [INFO] [WrapperSimpleAppMain] [Manager] Introscope Enterprise Manager Release 220.127.116.11(Build 581100)|
Solution Manager 7.1 discovers the version and displays it in Basic Configuration.
Adapt Enterprise Manager Java VM Parameters
Depending on the OS there are different locations where you adapt the Java VM parameters.
Adapt the file <EM_HOME>/bin/EMService.conf. The properties wrapper.java.additional.<number> contain the Java parameters. Java heap size is specified in parameters wrapper.java.maxmemory and wrapper.java.initmemory.
Adapt the file Introscope_Enterprise_Manager.lax in the EM home directory. Property lax.nl.java.option.additional contains all JVM parameters. For Java heap size see Java parameter -Xmx and -Xms.
Recommended Java VM parameters for Enterprise Manager
In case the EM crashes with OutOfMemory (OOM) it makes sense to analyze the Garbage Collections (GC) in more detail. So setting additional java parameters
-verbose:gc -XX:+PrintGCTimeStamps -XX:+PrintGCDetails is recommended.
With java parameter -Xloggc:gc.log the GC output is redirected from file em.log to a dedicated file gc.log.
The parameter -XX:+HeapDumpOnOutOfMemoryError is useful to trigger automatically a heap dump in case of OOM.
NOTE: heap dumps get a big as the Java heap size is configured. So make sure you have enough disk space available.
The bigger the Java heap size is configured the more it makes sense to work with parallel GCs by
setting additional java parameters -XX:+UseParNewGC -XX:+UseConcMarkSweepGC or -XX:+UseG1GC.
Start/Stop the Enterprise Manager
Register/Unregister Windows Service
The Windows Service to start/stop the Enterprise Manager usually gets registered by default during EM installation. In case you want to register or unregister this Windows Service manually you can do that with the script <EM_HOME>/bin/EMCtrl32.bat respectively EMCtrl64.bat. The command to register the service is EMCtrl64.bat register and EMCtrl64.bat unregister to remove the Windows Service.
The Windows Service display name and other details can be set in file <EM_HOME>\bin\EMService.conf. Changes to e.g. property wrapper.displayname modifying the default service display name "Introscope Enterprise Manager" of an already registered Windows Service only take effect after unregistering and registering the Windows Service.
Other properties you may need to change e.g. if you run several EMs on the same Windows host are wrapper.name and wrapper.description.
Collect Thread Dumps from the Enterprise Manager
If the Enterprise Manager appears stuck it may make sense to trigger a thread dump. The procedure differs depending on the operating system and the mode it is started.
If the EM is running as service (which is normal): Open a command prompt as administrator and issue the command sc control IScopeEM 255 (IScopeEM is the default name of the service). The thread dump will be appended to the service log file logs/EMService.log. For processing in any thread dump analysis tools you will have to remove the wrapper prefix added to every line.
Example output of the command:
C:\usr\sap\ccms\apmintroscope>sc control IScopeEM 255
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
Using jmxremote or SAP JVM is an alternative, but requires extra configuration.
If the EM is launched interactively (Introscope_Enterprise_Manager.exe) you can hit Ctrl-Break to trigger a dump. Unfortunately you get it on the console, difficult to capture.
On OS level identify the process ID of the Enterprise Manager, e.g. via the command ps -ef|grep java.
Send signal 3 to this process: kill -3 pid.
The thread dump will be written to the file em.log in the EM installation directory
Collect Heap Dumps from the Enterprise Manager
If the EM crashes and you find errors like "JAVA heap space out of memory" in the IntroscopeEnterpriseManager.log may have either configured the EM with low Java heap size (then see "Adapt Enterprise Manager Java VM parameters" above to increase the heap size) or there could be a memory leak. For the latter heap dumps are needed for analysis. To get heap dumps in case of an OutOfMemory set the additional java parameter -XX:+HeapDumpOnOutOfMemoryError (see "Adapt Enterprise Manager Java VM parameters" above; a restart of the EM is needed). Setting this parameter automatically a heap dump is triggered if an OutOfMemory occurs. The heap dump could consist of more than one file and is usually named java_pid<pid>.*.
In case you want to trigger heap dumps manually set java parameter -XX:+HeapDumpOnCtrlBreak. With every triggered thread dump (see "Collect Thread Dumps from the Enterprise Manager") you then also get a heap dump.
NOTE: heap dumps get a big as the Java heap size is configured. So make sure you have enough disk space available.
Performance / Scalability / Capacity
The EM provides several self-monitoring metrics about its internal status. The metric Overall Capacity (%) is also reported for each EM in the Solution Manager Administration work center. A value of 100% means that it has reached its capacity limit. Short peaks beyond 100% are not critical. Only if the capacity is permanently substantially beyond 100% you will experience problems like missing data points, poor performance, etc. You can find this Overall Capacity (%) metric in the Introscope Investigator via this path: Superdomain -> Custom Metric Host -> Custom Metric Process -> Custom Metric Agent -> Enterprise Manager -> Overall Capacity (%).
A more detailed view is available in the Introscope Investigator tree via the following path: Superdomain → Custom Metric Host → Custom Metric Process → Custom Metric Agent → Enterprise Manager. If you select the node Enterprise Manager in the tree, the tab Overview on the right side displays eight charts on EM sanity, as shown in the screenshot. It reveals heap utilization, number of metrics and agents.
The EM collects Metrics about itself and reports them to a file called perflog.txt under 15 second time periods. By analyzing the entries in this file, it is possible identify beforehand if the EM is becoming overloaded and avoid future issues. The EM Perflog Analyzer performs this analysis automatically and provides the user with recommendations on each point checked.
All known Webstart problems documented here were resolved with Introscope version 9.7 and subsequent versions. It might be easier to upgrade the Introscope Enterprise Manager and get a Webstart Workstation that works out of the box than to tweak the webstart for older versions. See SAP Note 2138309 and SAP Note 2285189.
The Java WebStart for the Introscope Workstation fails for higher patch levels of Java 7 and for Java 8 due to changes in the security checks of Java WebStart. In some cases the launch of the Workstation fails silently, in other cases an exception is shown.
In any case the following generic workarounds exist:
In addition, for the following Java patch levels workarounds are available:
Workstation Webstart: Expired Certificates as of March 1, 2015
Furthermore as of March 1, 2015, the CA APM Java JRE certificate has expired. This will impact all the customers who use web start client, version 9.7 and lower. Customers who initiate the workstation through the downloaded JNLP will be blocked if their security is set beyond medium. This issue is independent from issues related to individual Java Updates as listed above.
Below are options to work around this issue:
In order to do this → Go to Control Panel → Java → Security and adjust the security level.
In order to do this → Go to Control Panel → Java → Security → Click on Edit Site List and add the URL in the location box.
Webstart Additional Hints
We have not found a way to launch the Workstation 9.1.5 with recent Java 7 and Java 8 versions. You can, however, have multiple JRE versions installed on the same host. In particular, you could have Java 6 installed to launch the Workstation, and at the same time use a recent Java 8 version for webstart of other applications.
Use an absolute path like "C:\Program Files\Java\jre6\bin\javaws" http://emhost:8081/workstation to launch the Workstation.
Try launching the Webstart bypassing the browser In a command window. This isolates any potential browser add-in issues and allows to use webstart even if the browser add-in is disabled: Use a call like this:
"C:\Program Files\Java\jre6\bin\javaws" http://emhost:8081/workstation
Introscope agents of a certain version can connect to Introscope Enterprise Managers of the same or higher version. It is not possible to connect them to an EM with a lower version than the agent is. For more information, refer to the Introscope JAVA Agent WIKI.
Relevant log files for problems with the BCA are:
If requested by SAP Development set in IntroscopeAgent.profile the property log4j.logger.IntroscopeAgent from
A restart is not required. Do not forget to reset the value back to INFO after investigating the issue.
The agent version can be determined via one of the following procedures:
Byte Code Adapter does not start
Missing CPU Metrics
The CPU node in the Investigator tree of the byte code instrumentation agent (e.g. Netweaver agent) is populated via a native library, the so-called platform monitor. There are multiple possible reasons why this node might be missing:
Missing JMX Metrics
For troubleshooting JMX metric collection in the agent you can increase logging of the JMX service by setting these two additional properties:
JMX debug logging
log4j.logger.IntroscopeAgent.JMX\ Service=ALL, logfile
In general polling of particular MBeans will be switched off until the next restart of the Java VM as soon as any exception occurs for polling that MBean.
For Netweaver there is a known problem that reporting of http sessions ("Current Http Sessions") stops reporting. See SAP Note 2067705 for a fix.
Java Managed System does not start due to missing Agent.jar
If a Java Managed System has been instrumented for CA Introscope via the Java VM parameter -javaagent:/some/path/to/Agent.jar and the file Agent.jar is not accessible by the instrumented Java VM then it fails to start. Possible reasons why the file Agent.jar is not accessible:
In the first case the instructions for uninstalling the Introscope Byte Code Agent were not followed correctly.
You can find those instructions in the Introscope Installation or Setup Guide for your Solution Manager Release.
These installation or setup guides can be found here.
=> Alphabetical Index => S
=> SAP Solution Manager
=> "your solution manager release"
=> "one of the sections on installations"
=> "respective Wily Introscope guide".
In these guides, please refer to the section titled "Uninstalling Introscope Agents". It is recommended to use the SAP Solution Manager provided mechanism to remove the problematic properties.
In case the Diagnostics Agent was already deleted, it may be necessary to delete the properties by hand. In case of problems please create a ticket at component SV-SMG-DIA-WLY-BCA.
Known problems for Bytecode Agent
Check if Introscope Host Adapter is connected to the Enterprise Manager
Missing ABAP metrics
Log Files and Log Levels
Relevant logfiles for problems with Introscope Host Adapter are:
The log level for SMDAgentApplication.log might have to be increased to DEBUG for troubleshooting. This is done via diagnostics agent administration.
If the Introscope host adapter does not show up in the Investigator the file jvm_SMDAgent.out may also be relevant. It corresponds to IntroscopeAgent*.log of the BCA. To increase the log level for the Introscope runtime of the host adapter (in jvm_SMDAgent.out) edit the application resource "IntroscopeSapAgent.profile" and change the property
Thread dumps for the Introscope host adapter means thread dumps for the whole diagnostics agent. They can be triggered in various ways, e.g.:
In any case the thread dump is written to the file std_smdagent.out in the work directory of the diagnostics agent.