Installing CA WIly Introscope BCI Adapter for SAP Java Systems

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

  1. Extract the Introscope Agent files
  2. Configure the Introscope Agent
  3. Introscope-enable the application code by setting Java VM parameters


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.

You can also refer to this SAP Blog.

Extracting Introscope Agent Files

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. = <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.jarMain instrumentation set for SAP
Netweaver. Includes support for generic
Netweaver functionality, like database,
JCO, Web Services. This jar is always
sap_sapvm.jarFor SAP Netweaver 7.10 and higher with
JDK5 or higher. Specific
instrumentation, e.g. memory
allocation. Do not activate for Java
sap_bo_enterprise.jarSAP Business Objects Enterprise 3.x
sap_boe_webapp.jarSAP Business Objects Enterprise 4.x
sap_ep.jarSAP Portal specific instrumentation
sap_ep_iviews.jarAP Portal instrumentation: One node
per iView – should be preferred for
installations with many roles or when
collaboration rooms are used. Requires
sap_ep_iviews_rolename.jarRe-activate metrics for each
iView/rolename combination. Activate
only one of these 2:
sap_ep_iviews.jar or
sap_duet.jarSAP Duet specific instrumentation
sap_hybris.jarInstrumentation for Hybris.
sap_smp.jarInstrumentation for SAP Mobile
sap_omnichannelbanking.jarSMP instrumentation extension for Omni
Channel Banking
sap_xi_typical.jarDefault and mandatory instrumentation
file for PI
sap_xi_adapters.jarExtended instrumentation for PI
sap_xi_passport.jarExtended PI instrumentation to detect
passport propagation.
sap_xi_full.jarExtended instrumentation for PI. Some
of these metrics might have a performance impact
sap_smd.jarSolution Manager self-monitoring
sap_mdm.jarSAP Master Data Management
sap_compliance.jarSAP Compliance (SAP GRC, SAP EC, SAP
sap_epm.jarSAP EPM (SAP SSM, …) instrumentation
sap_retail.jarSAP Retail (SAP POS, SAP Triversity…)
sap_hilo.jarSAP Visual Intelligence instrumentation
sap_srm_crm.jarSAP SRM & SAP CRM (SAP Convergent
Charging, SAG Frictionless
e-Commerce, …)
sap_manufacturing.jarSAP Manufacturing (SAP SAP
Manufacturing Execution, SAP xMII, …)
Sap_hadoop.jarSAP Hadoop instrumentation
sap_partner.jarInstrumentation for SAP partner
products. See SAP Note 1852015.
sap_tomcat_typical.jarDefault and mandatory instrumentation
file for Apache Tomcat
sap_tomcat_full.jarExtended instrumentation for Apache
sap_websphere_typical.jarDefault and mandatory instrumentation
file for IBM WebSphere Application
sap_websphere_full.jarExtended instrumentation for IBM
WebSphere Application Servers
sap_weblogic_typical.jarDefault and mandatory instrumentation
file for Oracle WebLogic Server
sap_cem_integration.jarInstrumentation 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.

  1. Run the SAP J2EE Configtool.
  2. Navigate to Instance/VM Parameters/System and enter the following new parameters
com.wily.introscope.agentProfile<drive>:/usr/sap/ccms/wily/core/config/ IntroscopeAgent.profile

3. Navigate to Instance/VM Parameters/Additional and enter the following new java parameter


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\ and check for a line beginning with ID.JavaParameters, and see if it contains the lines you entered in the step above.

Simple System Integration of SAP JAVA Systems

For activating SAP Focused RUN monitoring functionalities on an SAP JAVA system you need to perform Simple System Integration of SAP JAVA Systems.

In our previous post we explained how to perform Simple System Integration (SSI) of ABAP systems. Performing SSI for SAP JAVA systems is similar to that of ABAP systems.

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.

You can also refer to the SAP documentation here.

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.

  1. The FRUN User and password you created as a pre-requisite
  2. 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.