Skip to Content

Setting up wily agent using manual procedure

Introduction

Willy Introscope is used mainly to monitor Java systems. This article describes how to manually install Willy Agent in each satellite systems.

Setting Up Wily Agent (Manual Procedure)

The Wily Agent can be downloaded from the Service Market Place from the below path:-

.

Note: – If we configure the wily agent manually we need to download the .SAR file else we want to go for the automatic method (i.e deployment through SDM)

we need to download the .SCS for te same.

After downloading the SAR file put it in the /usr/sap/ccms folder in the satellite system

 

Now extract the .SAR file in this folder only i.e (cd /usr/sap/ccms)
Run the command SAPCAR –xvf<ISAgent.SAR>and extract the .SAR file in the CCMS directory.

After extracting a folder wily is created with contains many files.


In the above screenshot it is shown wily folder is created in ccms after extracting the .SAR file

If we go into the wily folder we can see the below folders.

Configuring Introscope Agent Settings

The Agent configuration settings are found by default in the file:-

/usr/sap/ccms/wily/IntroscopeAgent.profile

This filescontains SAP specific customizations. So we need to change 2 parameters in this file to make it connect to the Central System (Solman)

Below are the two parameters we need to modify.

  1. 1. introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT – We need to specify the Host name or Ip Address of the machine where the Enterprise Manager lies (Central System)
  2. 2. introscope.agent.enterprisemanager.transport.tcp.port.DEFAULT– We need to specify thevalue for the port which the Enterprise Manager listens to. (Default is 6001)

Now we have located the 1st parameter mentioned above from the IntroscopeAgent Profile

As shown below the value of the profile is localhost. We need to change it.

So we are changing it via winscp or vi editor and save the file.

Creating AutoProbe Connector

We need to create a connector to fit the JDK version. This is required everytime we install or upgrade a new JDK version

Note: –A better solution is available with JDK 1.5.  The option –Xbootclasspath disappears.

Instead the option–javaagent:d:/usr/sap/ccms/wily/Agent.jaris used. (No connector.jar anymore).

We need to use the CreateAutoProbeConnector.jartool present inside the /wily/connectors to create a connector specific

to the JVM used in our system. Refer to the below screenshot:-

Now, we need to create the Autoprobe connector by this tool.  We need to run the following command:-

java -jar CreateAutoProbeConnector.jar -jvm <java_home> -output connector.jar

From the above command we can get that a .jar file named connector.jar is created in the connectors directory

We can find the java_home path specified in the command by:-

env | grep JAVAcommand.

So executing the command will result in the below shown output:-

Below file will be created:-

Activating the Agent: Set Java VM Parameters

Now to activate the agent we need to specify 3 parameters in the config tool and restart the server.

The 3 parameters are:-

-Dcom.wily.introscope.agentProfile=<drive>:/usr/sap/ccms/wily/IntroscopeAgent.profile

-Dcom.wily.introscope.agent.agentName=<AgentName>

-Xbootclasspath/p:<drive>:/usr/sap/ccms/wily/connectors/connector.jar:<drive>:/usr/sap/ccms/ wily/Agent.jar

Note:-Note the difference between Unix and Windows in the class path-The entries are separated by ;on Windows, but by : on Unix

  1. The 1st profile specifies the IntroscopeAgent.profile path. Since IntroscopeAgent.profile contains all the necessary Java parameters for the agent to connect to the Central System (Enterprise Manager)
  2. The 2nd Profile specifies the Agent Name. The naming convention is <AgentName>=SID_Instance_Nodename. Ex:- DE1_DVEBMGS00_server0
  3. 3rd profile specifies the path of connector.jar file and agent.jar file.

Config Tool

We need to set the above parameters in theconfig tool. So go to /usr/sap/<SID>/DVEBMGS00/j2ee/configtool

Run ./configtool.sh

Add the parameters mentioned above:-

Save it and the below popup comes:-

We need to restart the SAP only not the database. It will also work if we restart the Java only from smicm or restart

the server0 process from jcmon. Since we are adding parameters to server0.

Note:-

Before restarting the server there is another activity to be done. We need to create a log folder inside the wily directory and set permissions 775

and make sure the owner and the group is <SID>adm and sapsys.Refer the below screenshot:-

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Andy Silvey

    Hi Ranjith,

    nice blog, a couple of things to add,

    . It’s always handy to have the Wily Introscope Setup Guide available, which also describes the manual installation and autoprobe java parameters, version 8.x or 9.x,

    . In NW 7,1 and 7,2 and 7,3 the java parameters are kept in different locations in the

    configtool, eg

              Instance/VM Parameters/System

              Instance/VM Parameters/Additional

    this is described in detail in OSS Note:

              1654426 – How to instrument SAP NetWeaver J2EE stack for

               Remote Support Component

    I’ve experienced on PI 7,1 that JSMON Server Node restarts was not enough and instance restart was required, the OSS Note also recommends an instance restart.

    All the best,

    Andy.

    (0) 
  2. Aniket Singh

    Hi Ranjith,

    Thanks for this blog. It is really useful.

    Can you also throw some lights regarding the java agent deployment using the automatic method through Solman.

    Appreciate it.

    Regards,

    Aniket

    (0) 
    1. Ranjith Jacob Post author

      Hi Aniket,

      the java agent deployment will be done via managed system configuration. the process is very simple and we just need to ensure the diagnostics agents in managed system and solman are running, EM also should be reachable.

      Thanks,
      Ranjith

      (0) 

Leave a Reply