sap solution manager-agents administration.pptx

8/10/2019 SAP Solution Manager-Agents Administration.pptx

1/30

SAP Solution Manager-Agents Administration

Presented byRishav Garg


2/30

Overview


3/30

Setting Up Agents in the SAPSolution Manager

To be able to use agents data, you need to configure them. This isdone in SAP Solution Manager.

There are two steps you have to perform:Registration of Agents in the SAP Solution Managaer. This is donein step System Preparation in transaction SOLMAN_SETUP.

Assignment of the Diagnostics Agent(s) to a Technical System. Thisis done in step Managed System Configuration in transactionSOLMAN_SETUP.Once these steps have been performed, your Technical System hasbeen set up to be managed by SAP Solution Manager.


4/30

Agent TypesThere are two agents which need to be installed for better systemmanagement:

Host Agentsgather 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 detailedpresentation as an attachment. The setup of the automatic update processis described in SAP note 1473974 .)

Diagnostics Agents (formerly called Solution Manager Diagnostics [ SMD ] Agent)

gather information of the managed application on the host systemssend it together with the data collected by the SAP Host Agent to SAPSolution Manager


5/30

ContinuedOne Host Agent must be installed for each physical host and one Diagnostics

Agent for each managed host represented by physical, virtual or logical hostname. One Diagnostic Agent can support multiple managed systemcomponents running on the same named host


6/30

Landscape Data and OutsideDiscovery

Most of the landscape data application is already sent by the managed applicationsystems to the System Landscape Directory (SLD) and from there synchronized tothe 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 beencollected 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 applicationsystem 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 sendingprocess to SAP Solution Manager. Outside discovery works on three different areas:OS discovery provides details about the operating systemDB discovery provides details about installed database software(s)

MS discovery provides details about Microsoft Internet Information Services onMicrosoft operating systems.


7/30

Diagnostic AgentsArchitecture


8/30

SAP Host agent connectivity

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

Hostagent .


9/30

DiagnosticThe Agent Admin applications is the main tool to manage diagnosticagents and their application.


10/30

Agents Administration (Contd)


11/30



12/30



13/30

Agents Overview


14/30



15/30


16/30

ContinuedDuring Diagnostics Agent installation, the SAP Solution Manager system is known:a. The Diagnostic Agent is already connected to SAP Solution Manager (the direct registrationcan 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 aDiagnostic Agent is optionally written to an SLD (in an SLD the agent itself is considered as a SAPtechnical 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 managedsystem.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 andregistered 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 ManagerThe host agent does neither register itself to an SLD nor directly to SAP Solution Manager. Thecommunication to the SAP Host Agent is managed via Diagnostics Agent


17/30

Agents On Fly


18/30

Interoscope Java Agents (ISagents)


19/30

IS AgentsThe ISAgent is a third party tool created by CA Technologies. TheISAgent is part of the CA Introscope. The CA Introscope is anenterprise application performance management solution that enablesyou to monitor complex web applications in production environments

24x7. The main purpose of the ISAgent is to collect data from theapplications and systems running on Java Virtual Machines (JVMs),then the data is transferred to the Enterprise Manager to be stored andanalyzed.To have Root Cause Analysis and complete Early Watch Alerts for SAP

Netweavers JAVA and Dual systems, it is required to install theIntroscope JAVA Agent in the target systems. The following picutreshows the archtecture of the Instrscope JAVA Agents in SAPNetweaver systems.


20/30

Setting up wily agent usingmanual procedure

Introduction Willy Introscope is used mainly to monitor Java systemsSetting Up Wily Agent (Manual Procedure) The Wily Agent can be downloaded from the Service Market Place from the

below path:-


21/30

Installationwe 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 xvfand extract the .SAR file in the

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


22/30

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 inthis 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 tospecify 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 tospecify thevalue for the port which the Enterprise Manager listens to. (Default is 6001)Now we have located the 1 st parameter mentioned above from the IntroscopeAgentProfile

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


23/30

Installation (Contd)


24/30

Installation (Contd)Creating AutoProbe Connector

We need to create a connector to fit the JDK version. This is requiredeverytime we install or upgrade a new JDK versionNote: - A better solution is available with JDK 1.5. The option

Xbootclasspath disappears.Instead the option javaagent:d:/usr/sap/ccms/wily/Agent.jar is used.(No connector.jar anymore).We need to use the CreateAutoProbeConnector.jar tool presentinside the /wily/connectors to create a connector specificto the JVM used in our system. Refer to the below screenshot:-


25/30

Installation (Contd)Now, we need to create the Autoprobe connector by this tool. We need torun the following command:-

java -jar CreateAutoProbeConnector.jar -jvm -outputconnector.jar From the above command we can get that a .jar file named connector.jar iscreated in the connectors directoryWe can find the java_home path specified in the command by:-env | grep JAVA command.So executing the command will result in the below shown output:-


26/30

Installation (Contd)


27/30

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 theserver.The 3 parameters are:--Dcom.wily.introscope.agentProfile=:/usr/sap/ccms/wily/IntroscopeAgent.profile -Dcom.wily.introscope.agent.agentName= -Xbootclasspath/p::/usr/sap/ccms/wily/connectors/connector.jar::/usr/sap/ccms/ wily/Agent.jar Note:- Note the difference between Unix and Windows in the class path-The entries are separatedby ;on Windows, but by : on Unix

The 1st

profile specifies the IntroscopeAgent.profile path. Since IntroscopeAgent.profile containsall the necessary Java parameters for the agent to connect to the Central System (EnterpriseManager)The 2 nd Profile specifies the Agent Name. The naming convention is=SID_Instance_Nodename. Ex:- DE1_DVEBMGS00_server03 rd profile specifies the path of connector.jar file and agent.jar file.


28/30


29/30

Installation (Contd)We need to restart the SAP only not the database. It will also work if we restartthe Java only from smicm or restartthe 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 tocreate a log folder inside the wily directory and set permissions 775 and make sure the owner and the group is adm and sapsys. Refer thebelow screenshot:-


30/30

Installation (Contd)In NW 7,1 and 7,2 and 7,3 the java parameters are kept in different locations in theconfigtool, 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 forRemote Support Component

sap solution manager-agents administration.pptx

Documents