Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 

Hello All,

Today I would like to talk about the Introscope Host Adapter (WilyHost application), an application which runs inside the SMDAgent to collect data from the managed systems. I already did a allam.drebes/blog/2014/04/23/troubleshooting-workload-analysis-for-abap-java-and-dual-stack-systems showing how to check this application, but now I would like to provide some details about how this application works.

As I already mentioned, the Introscope Host Adapter is an application which runs inside the SMDagent, it is also known as SMDAgent agelet or WilyHost agent. The main goal of the WilyHost agent 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 wilyhost agent.

All applications running inside the SMDAgent can be found win the Agent Administration UI. The WilyHost Agent can be found as shown in the below picture.

  1. Agent Administration UI
  2. Application Configuration

All resources used by the WilyHost application can be found under the 'Application Resources' node:

N.B.: When using the application configuration take care when performing changes. Do not perform changes in the scope GLOBAL if you do not know exactly what you are doing. The changes in scope global affect ALL SMDAgents connected to the Solution Manager system.

In Solution Manager 7.10, the WilyHost Agent is configured during the activity 'Introscope Host Adapter' of the Managed System Configuration for the target system. The following picture shows the exact location:

When the activity Introscope Host Adapter is performed, the wilyhost agent application is configured to collect data from the managed system that will be monitored. The main files used by the agent are the following:

  • Files create/modified by setup:
    • SAPAgentConfig.xml
      • File created during the Wily host agent setup step. It contains the destinations configuration and the link to actions to be performed for each destination
    • IntroscopeSAPAgent.profile
      • File is created from the IntroscopeSapAgent.profile.template. The host and port of the Enterprise Manager are configured in this file.
  • Files used by application:
    • WilyHostAgentTemplate.xml
      • The is a global template file that defines all the possible actions possible for collecting all the Wily Host Agent data.
    • WilyHost.xsd
      • The is the XML schema file that defines the rules of validation for the WilyHostAgentTemplate.xml file. If you modify the action template it needs to conform to the schema.

N.B.: No manual configuration must be performed to the above files. The activity Introscope Host Adapter will configure the WilyHost 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.

  • Destinations: The destinations will point out where the information will be collected. The destinations are configurable, for example a destination might be a Jco connection to the managed system or the location of a specific file.

For a typical double stack system you will have configurations generated for the following destinations:

    • ABAP instance
    • JAVA instance
    • SAPStartSrv
    • File (for GC)

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.

  • Actions: The actions indicates to the WilyHost Agent what are the metrics to be collected from the managed system. For all destinations in the SAPAgentConfig.xml a pool of actions are configured. The actions point to an action templates that are defined in the WilyHostAgentTemplate.xml file.

The following picture shows an example of some actions defined in a SAPAgentConfig.xml.

A SAPAgentConfig.xml fully configured will look 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 WilyHost application what is the Enterprise Manager that the wilyhost 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 you find out that there is some issue with the wilyhost application, 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 wilyhost application may not work correctly due to distinct issues and the SMDAgent logs will show the root cause.

The SMDAgent logs can be downloaded using the Agent Administration UI:

The logs related to the wilyhost application are the following:

Logging informationLog File

SMD Agent System log file


SMD Agent Application log file. All of the interesting logging for the Wily Host Agent will be found here


Host Agent Information when trying to connect to the Enterprise Manager

RFC Connections/usr/sap/SMD/SMDA<xx>/SMDAgent/dev_jrfc.trc

1) How to check if the WilyHost agent is connected to the EM: Check the jmv_smdagent.log, this file shows the information about the connection between the wilyhost application and the Enterprise Manager. If the WilyHost application cannot connect to the EM the jvm_smdagent.log will show the root cause. The following picture shows an example of log entry for a successful connection:

It is also possible to check if the wily host application is connected to the EM directly in the Introscope Investigator. By default the wilyhost application connects to the EM using the process name = 'SAP HostAgent Process' and agent name 'SAP HostAgent <SMDAgent_instancename>'. The following picture shows the same agent of the above log entry connected to the EM.

2) How to check if actions are being collected: Compare actions defined in the SAPAgentConfig.xml with information available in the Wily Investigator. You should see nodes in the investigator with the same prefix of the actions.

If you find out that some actions are not started, e.g. workload analysis is missing, nodes in the introscope investigator are not available. Then the SMDAgentApplication.log must be checked. Usually, the actions are started when the SMDAgent process is started. So, to check issues with the actions it is good to restart the SMDAgent. It can be done in the Agent Administration UI as follows:

3) Example ABAP Instance action cannot be started: You see that you have no ABAP data in Introscope or in workload. You download the SMD log files and you see that you have a JCO issue. The SMDAgentApplication.log shows that the user is locked:

Solution: The WilyHost application uses the SMDAGENT_<Solman_SID> to connect to the managed system. In this case, it is necessary to check the password of user SMDAGENT_<Solman_SID> and unlock the user. This can be performed in step Create Users of the Managed System Configuration for the affected system.

4) Example SAP GC action cannot be started: You see that you have no SAP GC instance data in Introscope or in workload. The SMD Agent logs shows the following errors:

Solution: The SAP GC is collected from file std_server* which is located in the managed system work folder. In this case, it is required to ensure that the path to the files is correct. It is possible to compare the file shown in the log error or in the action definition in the SAPAgentConfig.xml. If the path is wrong, check the paths provided in step Enter Landscape Parameters in the Managed System Configuration for the affected system.

I hope you enjoy this post.

You can leave questions below, I will try to answer them as soon as possible.

Thanks / Obrigado

Allam Drebes