SAP Solution ManagerAgents Administration

Presented by
Rishav Garg

Overview

Setting Up Agents in the SAP

Solution Manager
To be able to use agents data, you need to configure them. This is
done in SAP Solution Manager.
There are two steps you have to perform:
Registration of Agents in the SAP Solution Managaer. This is done
in step System Preparation in transaction SOLMAN_SETUP.
Assignment of the Diagnostics Agent(s) to a Technical System. This
is done in step Managed System Configuration in transaction
SOLMAN_SETUP.
Once these steps have been performed, your Technical System has
been set up to be managed by SAP Solution Manager.

Agent Types
There are two agents which need to be installed for better system
management:
Host Agents
gather information about the hosts operating system
important to have at least the minimum version of the host agent installed
(For more information refer to SAP note 1365123, which contains a detailed
presentation as an attachment. The setup of the automatic update process
is described in SAP note 1473974.)
Diagnostics Agents (formerly called Solution Manager Diagnostics [SMD]
Agent)
gather information of the managed application on the host systems
send it together with the data collected by the SAP Host Agent to SAP
Solution Manager

Continued
One Host Agent must be installed for each physical host and one Diagnostics
Agent for each managed host represented by physical, virtual or logical host
name. One Diagnostic Agent can support multiple managed system
components running on the same named host

Landscape Data and Outside

Discovery

Most of the landscape data application is already sent by the managed application
systems to the System Landscape Directory (SLD) and from there synchronized to
the Landscape Management Database (LMDB) of the SAP Solution manager 7.1.
However, in some cases this data needs to be enriched by data which has been
collected by agents and written directly to the CIM model based LMDB.
As the agents are neither part of the operating system nor of the installed application
system of a host, the term Outside Discovery is used for this kind of data collection.
In Outside Discovery both agent types work together in the gathering and sending
process to SAP Solution Manager. Outside discovery works on three different areas:
OS discovery provides details about the operating system
DB discovery provides details about installed database software(s)
MS discovery provides details about Microsoft Internet Information Services on
Microsoft operating systems.

Diagnostic Agents
Architecture

SAP Host agent connectivity

SAP Hostagent is installed per default under /usr/sap/hostctrl on Unix based and
under C:\ Program Files\SAP\hostctrl on windows operating system. In order for
the communication to enable between the saphost agent and diagnostic agent
the diagnostic agent had to be added as service user to the host_profile for SAP
Hostagent .

Diagnostic

The Agent Admin applications is the main tool to manage diagnostic

agents and their application.

Agents Administration (Contd)

Agents Administration (Contd)

Agents Administration (Contd)

Agents Overview

Agents Administration (Contd)

Agent Registration

In order to have a fully functional agent, two registration steps need to be done.
The Diagnostics agent need to be connected to a SAP Solution Manager to download the latest
applications from the managing system
The managed systems need to be connected to the Diagnostics Agent(s)
For the first step depending on the installation strategy the agent is either registered directly to the
SAP Solution Manager (mainly during the agent installation) or by usage of the agent candidate
management during the SAP Solution Manager setup (when the agent has registered to SLD).

Continued

During Diagnostics Agent installation, the SAP Solution Manager system is known:
a. The Diagnostic Agent is already connected to SAP Solution Manager (the direct registration
can also be performed after the agent installation using a configuration script on the agent host).
b. Data is available in SAP Solution Manager directly and information about the existence of a
Diagnostic Agent is optionally written to an SLD (in an SLD the agent itself is considered as a SAP
technical system. Please note that the SLD must not necessarily be the same as used for the
content synchronization to LMDB).
c. During managed system setup, the system(s) running on the host with the Diagnostics Agent is
(are) connected to the SAP Solution Manager and therefore can directly be linked to the managed
system.
During Diagnostics Agent installation, SAP Solution Manager is not known:
a. The Diagnostics Agent is registered in an SLD (setting is done during installation).
b. SAP Solution Manager in Solution Manager Setup during phase Preparation for SLDs and
registered Diagnostics Agents.
c. Available (not already used) Diagnostics Agents are connected to the SAP Solution Manager.
d. During managed system setup, the managed system running on the host with the Diagnostics
Agent is connected to the SAP Solution Manager
The host agent does neither register itself to an SLD nor directly to SAP Solution Manager. The
communication to the SAP Host Agent is managed via Diagnostics Agent

Agents On Fly

Interoscope Java Agents (IS

agents)

IS Agents
The ISAgent is a third party tool created by CA Technologies. The
ISAgent is part of the CA Introscope. The CA Introscope is an
enterprise application performance management solution that enables
you to monitor complex web applications in production environments
24x7. The main purpose of the ISAgent is to collect data from the
applications and systems running on Java Virtual Machines (JVMs),
then the data is transferred to the Enterprise Manager to be stored and
analyzed.
To have Root Cause Analysis and complete Early Watch Alerts for SAP
Netweavers JAVA and Dual systems, it is required to install the
Introscope JAVA Agent in the target systems. The following picutre
shows the archtecture of the Instrscope JAVA Agents in SAP
Netweaver systems.

Setting up wily agent using

manual procedure

Introduction
Willy Introscope is used mainly to monitor Java systems
Setting Up Wily Agent (Manual Procedure)
The Wily Agent can be downloaded from the Service Market Place from the
below path:-

Installation

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.

Installation (Contd)
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. 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. 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.

Installation (Contd)

Installation (Contd)
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 optionjavaagent: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:

Installation (Contd)

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:-

Installation (Contd)

Installation (Contd)

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/cc
ms/ 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
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)
The 2nd Profile specifies the Agent Name. The naming convention is
<AgentName>=SID_Instance_Nodename. Ex:- DE1_DVEBMGS00_server0
3rd profile specifies the path of connector.jar file and agent.jar file.

Installation (Contd)

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:-

Installation (Contd)
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:-

Installation (Contd)
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