Agent installation strategy

Solution Manager 7.1 and 7.0 EhP1(SP20 and higher)

July 2011
Introduction

Scope
Following rules are in most cases relevant for Solution Manager 7.0 EhP1 and 7.1,
but in case restrictions apply the rule item is tagged [7.0 EhP1 only] or [7.1 only]

Terminology
The term “host” in this slide set does NOT designate network alias. Hosts (virtual or
logical) MUST have their own IP address.
A “Virtual host” designates a simulated host running for example on top of a VMware.
A “Logical host” designates a network / host configuration which associates a physical
host with one or several additional hostnames and dedicated IP addresses. This is for
example used to easily move systems from one physical host to another.
N.B.: To double check which hostname is used by an ABAP system, use transaction
sm51 and for Java systems refer to the System Info Web page.

© 2011 SAP AG. All rights reserved. 2

What is needed and where? (Diagnostics Agent)

Rule #1:
Have the required amount of Diagnostics Agent(s) installed
 For each Solution Manager install only one Diagnostics Agent per host (physical, virtual or
logical)
 Each Diagnostics Agent manages the supported systems / components running on the host
where it is installed (and is considered as being representative for the host)
– Refer to the next slides to understand what is considered to be a supported system component
– Nevertheless, the “Managed System configuration” (solman_setup) must be repeated for each technical
system running on that host (physical, virtual or logical)
 For landscapes with logical hostnames, take care to specify the adequate hostname during
installation
– Only when installing an (additional) Agent for a logical host, using the Diagnostics Agent installation
package, provide in the SAPInst step that requests a “Virtual hostname”, the short hostname of the host
for which this Agent should be representative.

© 2011 SAP AG. All rights reserved. 3

 What is needed and where? (Diagnostics Agent)

Rule #1 (details):
Have required amount of Diagnostics Agent(s) installed
LogicalHost3 LogicalHost1 LogicalHost2

C1 C2 C7 C8 C3 C4 C5 C6

cluster

Diagnostics Diagnostics Diagnostics Diagnostics

Agent 1 Agent 2 Agent 3 Agent 4

SAP Host SAP Host

Agent Agent
PhyHost2 PhyHost3 .

 To simplify this slide considers a VMware host also

as a Physical host.
 For each Solution Manager, have only one DA Diagnostics Agent
Diagnostics Agent per “host”: Physical or Logical Diagnostics
 Each Diagnostics Agent will be uniquely identifiable SAP Solution Manager Agent 5
HA SAP Host Agent
in Solution Manager via this “host” (short) name
Managed Component
 A Diagnostics Agent will support the Managed (see following slides)
SAP Host
Components, running on that host. Agent
 Have one SAP HostAgent per physical host. PhyHost1
© 2011 SAP AG. All rights reserved. 4
 What is needed and where? (Diagnostics Agent)

Amount of Diagnostics Agents depending on Managed components distribution

 Example where all components are running one host (physical, virtual or logical)

Solution Manager Enterprise Portal ERP / ECC Server

ABAP stack on 1 Host

ABAP Central Instance Central Instance

Java stack on 1 Host

Dual stack on 1 Host

Central Instance
+ ABAP Central Services + ABAP Central Services

Java Central Instance

Dialog Instance Dialog Instance

Java Central Services

Central Services

DB DB

DB

Diagnostics Agent Diagnostics Agent Diagnostics Agent

© 2011 SAP AG. All rights reserved. 5

 What is needed and where? (Diagnostics Agent)

Amount of Diagnostics Agents depending on Managed components distribution

 Example where each component is running on a different host (physical , virtual or logical)

Solution Manager Enterprise Portal ERP / ECC Server

Distributed ABAP stack

Distributed Java stack
Distributed Dual stack

ABAP Central Instance Central Instance Central Instance

+ ABAP Central Services + ABAP Central Services

Java Central Instance Diagnostics Agent Diagnostics Agent

Diagnostics Agent
Dialog Instance Dialog Instance

Java Central Services Diagnostics Agent Diagnostics Agent

Central Services

DB DB
Diagnostics Agent Diagnostics Agent
DB
Diagnostics Agent

Agent required in the scope Agent required in the scope Agent required in the scope
of Solution Manager 7.1 of Solution Manager 7.1 of Solution Manager 7.1
© 2011 SAP AG. All rights reserved. 6
 What is needed and where? (Diagnostics Agent)

Covering 3-System landscape by installing an additional Diagnostics Agent (QA Portal)

Solution Manager
Dev SolMan
Collected config of
Managed systems
Dev & QA Dev Enterprise Portal Introscope
Agents

3-System landscape
Comparison possible Diagnostics Agent

Introscope
Enterprise Manager

Use Dev IS EM to
retrieve Perf data of QA Enterprise Portal Introscope
QA Managed systems Agents
Solution Manager Diagnostics Agent
Prod SolMan

Diagnostics Agent
Collected config of
Managed systems
QA & Prod

Comparison possible Prod Enterprise Portal Introscope

Agents
Introscope Diagnostics Agent
Enterprise Manager

© 2011 SAP AG. All rights reserved. 7

 What is needed and where? (Diagnostics Agent)

[7.1 only] Covering 3-System landscape requires installing a 2nd Diagnostics Agent (Dev IS EM)
Solution Manager
Dev SolMan
Collected config of
Managed systems
Dev & QA Dev Enterprise Portal

3-System landscape
Introscope
Enterprise Manager
Diagnostics Agent
Use Dev IS EM to Diagnostics Agent
retrieve Perf data of QA Enterprise Portal
QA Managed systems
Solution Manager
Prod SolMan

Collected config of
Managed systems
QA & Prod

Prod Enterprise Portal

Introscope
Enterprise Manager
Diagnostics Agent

© 2011 SAP AG. All rights reserved. 8

 What is needed and where? (Diagnostics Agent)

Dev System landscape

Covering 3-System
Dev Enterprise Portal Introscope Dev ECC Server
Landscape (continued) Agents
Diagnostics Agent Diagnostics Introscope
 Managed systems part Agent Agent
of an E2E Solution must
be connected to the QA System landscape
same Solution Manager
QA Enterprise Portal Introscope QA ECC Server
system Agents
Diagnostics Agent Diagnostics Introscope
Diagnostics Agent Agent
Diagnostics Agents
Introscope
Prod SolMan

Agent Agent
Solution Manager

Prod Managed Prod System landscape

Systems data
EP & ECC

E2E Trace Analysis Prod Enterprise Portal Introscope Prod ECC Server
Agents
Diagnostics Agent Diagnostics Introscope
Introscope
Agent Agent
Enterprise Manager

© 2011 SAP AG. All rights reserved. 9

What is needed and where? (SAP Host Agent)

Rule #2:
Have up-to-date SAP Host Agent(s)
 Always refer to SAP note 1365123 to find out the currently requested minimum version
– This note also confirms whether the installation / upgrade of the SAP Host Agent performed jointly with
the installation of a Diagnostics Agent (installer 7.30 SPxx) is sufficient to cover currently know defects.
 Install a SAP Host Agent in case none has been installed yet (one per physical host)
– Checking whether a SAP Host Agent exists using file structure at OS level:
o For Windows look under: "%ProgramFiles%"\SAP\hostctrl
o For Unix under: /usr/sap/hostctrl/
 Update the SAP Host Agent following SAP note 1031096 in case the version is not adequate
– Check version by executing at OS level (looking in the output at SAPHOSTAGENT Information section):
o For Windows: "%ProgramFiles%"\SAP\hostctrl\exe\saphostctrl -function ExecuteOperation -name versioninfo
o For Unix: /usr/sap/hostctrl/exe/saphostctrl -function ExecuteOperation -name versioninfo
– [7.1 only] Currently installed Host Agent version is also visible in Host browsing, in case the associated
“Managed System Configuration” has been performed with solman_setup
o Navigate to Solution Manager Administration Work Center -> Select Landscape + Technical System
selection type -> System Details -> System Details -> Hosts -> <search for your host> -> Host Status

© 2011 SAP AG. All rights reserved. 10

What is needed and where? (SAP Host Agent)

Rule #2 (continued):
Have up-to-date SAP Host Agent(s)
 Ideally put in place the automatic upgrade process (especially if you need to plan an update)
– SAP note 1473974 describes ways to centrally and automatically upgrade running SAP Host Agents.

© 2011 SAP AG. All rights reserved. 11

Diagnostics Agent is a SAP system

Rule #3:
Consider the Diagnostics Agent as a standard SAP system
 Therefore the rules common to all SAP Systems apply
 Never install an Agent into the directory structure of another system (also do not copy or
move the files)
– Agents must be independent from any other kind of system installation
 Exception: Several Diagnostics Agents (with same kernel release) can be installed using
the same SID, but using different Instance Numbers
– This also means that the Agent SID must contain only Diagnostics Agent instances
 Diagnostics Agents typically have different System / Instance ID patterns depending on the
release (see following slides)

© 2011 SAP AG. All rights reserved. 12

Diagnostics Agent is a SAP system

Rule #3 (details):
Possible alternatives to install multiple Diagnostics Agents on the same host (to be
connected to different Solution Manager systems)
 Use the same dedicated System ID (and like always different Instance Numbers)
– Recommendation: Do not use the same SID for Diagnostics Agents having different Kernel Releases
(in general this is prevented by the installer).
 Using different System IDs (and like always different Instance Numbers)
– Allows to have totally independent installations, but requires also internal allocation rules in case the
file system is mounted.

© 2011 SAP AG. All rights reserved. 13

Diagnostics Agent file structure

Description 7.0 / 7.01 SR1 7.11 / 7.20 / 7.30 SP02

Global exe /usr/sap/<SMDSID>/exe /usr/sap/<DASID>/SYS/exe

SAPJVM No SAPJVM (using separately installed JDK) /usr/sap/<DASID>/SYS/exe/jvm

global directory /usr/sap/<SMDSID>/SYS/global /usr/sap/<DASID>/SYS/global

profile directory /usr/sap/<SMDSID>/SYS/profile /usr/sap/<DASID>/SYS/profile

Instance directory /usr/sap/<SMDSID>/J<XX> /usr/sap/<DASID>/SMDA<XX>

script directory /usr/sap/<SMDSID>/J<XX>/script /usr/sap/<DASID>/SMDA<XX>/script

work directory /usr/sap/<SMDSID>/J<XX>/work /usr/sap/<DASID>/SMDA<XX>/work

Local exe No local exe directory /usr/sap/<DASID>/SMDA<XX>/exe (1)

Local SAPJVM No SAPJVM /usr/sap/<DASID>/SMDA<XX>/exe/sapjvm_xx (1)

Agent software and /usr/sap/<SMDSID>/J<XX>/SMDAgent /usr/sap/<DASID>/SMDA<XX>/SMDAgent

properties files
Agent logs /usr/sap/<SMDSID>/J<XX>/SMDAgent/log /usr/sap/<DASID>/SMDA<XX>/SMDAgent/log

(1) Contains executable kernel programs that are replicated (even moved for the SAPJVM) from SYS/exe
every time the Agent instance is started.
© 2011 SAP AG. All rights reserved. 14
Diagnostics Agent releases

Rule #4:
In case you need to install a Diagnostics Agent to comply with rule#3 use the
standalone Diagnostics Agent installation package 7.30 SP02
 A summary of various Diagnostics Agents releases an characteristics are presented on the
next slide
 Only the older Diagnostics Agent release 7.01 SR1 could be connected to a Solution
Manager having a release lower than 7.0 EhP1 SP20. This Agent release is installable with
the SAP EhP1 for SAP Netweaver 7.0 Installation Master, Kernel & Java DVDs. A
separately installed JDK 1.4.2 is also required.

© 2011 SAP AG. All rights reserved. 15

Diagnostics Agent release constraints

Agent releases 7.0 / 7.01 SR1 7.20 7.30 SP02

Solution Manager Solution Manager Solution Manager
Compatible with Solution
lower than 7.0 EhP1 SP 20 since 7.0 EHP1 SP20 (included) since 7.0 EHP1 SP20 (included)
Manager (1) (1)(2) (1)(2)
Support Managed system
6.40, 7.00 and higher 6.40, 7.00 and higher 6.40, 7.00 and higher
NW releases
https://websmp110.sap- https://websmp110.sap-
ag.de/~form/handler?_APP=002006 ag.de/~form/handler?_APP=0020
82500000001303&_EVENT=DISP_ 0682500000001303&_EVENT=DI
Supported OS http://service.sap.com/pam
NEW&00200682500000002804=01 SP_NEW&002006825000000028
200615320900004494 04=01200314690900002540
-> JSE Platforms -> JSE Platforms

Installation SAP note 1357812 1368413 1448655

Installer recommended Installer recommended

when new installations required when new installations required
(only for older Managed OS platforms)

(1) When a Solution Manager system is upgraded the associated connected Diagnostics Agents do generally not need to be manually
upgraded. See also next slide and later rule #5. IMPORTANT: But in all cases rule #2 must be followed.
(2) N.B.: It means that this Diagnostics Agent release could be also used in the scope Solution Manager 7.1.
© 2011 SAP AG. All rights reserved. 16
Diagnostics Agent characteristics for each release

Agent releases 7.0 / 7.01 SR1 (1)(2) 7.11 7.20 7.30 SP02 (4)
CE 7.20 & NW 7.0 NW 7.3 (and soon 7.0
Installed already silently 7.0 & EhP1 NW
PI & CE 7.1 EhP1 EhP2 NW Java, EhP3) Java, ABAP or
with Products based on … Java or dual stacks
ABAP or dual stacks dual stacks

Kernel release (like SAP Products) 7.0 / 7.01 7.11 7.20 7.20

JVM JDK 1.4.2 SAPJVM 5 SAPJVM 6 SAPJVM 6

(installed separately / out of maint.)

SMD DAA DAA DAA

Default System ID / Instance
/ J<98 to 00> / SMDA<97 to 00> / SMDA<97 to 00> / SMDA<98 to 00>
Support both direct
Yes
connection to SolMan & SLD No No Yes
(Support offline mode)
registration @ installation
SSL & SAPRouter Support
No No Yes (3) Yes
@ installation
Yes (manual install) Yes (auto installed /
SAP Host Agent needed Except for SolMan prior to 7.0EhP1 Yes (manual install) Yes (auto install)
SP20 using local saposcol binary updated) (4)

Installation SAP note 1357812 1234387 1368413 1448655

Agent start / stop / control smdstart/stop/admin Standard Standard Standard

(1) No separate (standalone) Diagnostics Agent installation package provided (reduced size)
(2) Server Name could be provided. Do not confuse “server name” and host name.
(3) IAIK libraries need to be provided manually Installer recommended
(4) Also allows to configure automatically the trusted connection @ SAP Host Agent level when new installations required
© 2011 SAP AG. All rights reserved. 17
Diagnostics Agent and SLD registration

Following Diagnostics Agent connectivity options should be adopted, depending on

the installation scenario:
 Diagnostics Agent is installed already silently with a Managed System
– The Agent is registered in the System Landscape Directory that has been specified during the
Managed system installation
o Therefore the Agent could be connected to Solution Manager using for example solman_setup ->
Managed System Configuration. This will configure remotely the Agent to connect to Solution
Manager via the Message Server.
– No System Landscape Directory is specified during the Managed system installation
o To connect the Agent to Solution Manager via the Message Server using the smdsetup script as
documented in the Diagnostics Agent troubleshooting guide (http://service.sap.com/diagnostics ->
Media Library).
 Agent is installed using a Diagnostics Agent Installation package (see previous slide)
– During the Agent installation choose to connect it to Solution Manager (via the Message Server)
instead of (only) registering it in a System Landscape Directory. This will reduce the amount of
activities to be performed in solman_setup.
– New Solution Manager connectivity data could be pushed to running Diagnostics Agents (useful in
case of operational issues) when choosing to also register the Agent in a (central) System Landscape
Directory.

© 2011 SAP AG. All rights reserved. 18

Diagnostics Agent mass installation

Use the SAPInst unattended mode in case Diagnostics Agents need to be installed
consistently over a wide landscape
 The unattended mode allows the Diagnostics Agent installer package to be used in silent
mode to automate the installation of a higher number of Agents
 Installation template available for Diagnostics Agents 7.20 in SAP note 1294713
 Installation template available for Diagnostics Agents 7.30 in SAP note 1486330

© 2011 SAP AG. All rights reserved. 19

Diagnostics Agent upgrade

Rule #5:
Generally for Diagnostics Agents do not worry about upgrades (versus SAP Host
Agent)
 Diagnostics Agents are taking their business logic (software) from the Solution Manager
system to which they are connected
– Therefore all Diagnostics Agents in the landscape (that are running and connected) could be patched
centrally, by applying an LM-SERVICE Java Software Component Archive on the Solution Manager
System
 In case some issues have to be resolved (support of cryptography, …) an associated
manual procedure is generally described within the SAP note corresponding to the
Diagnostics Agent installation guide of the Agent associated release. Alternatively, consider
applying the procedure described on the next slide.

© 2011 SAP AG. All rights reserved. 20

Diagnostics Agent upgrade

Rule #5 (continued):
In case a Diagnostics Agent has to be nevertheless upgraded, perform a uninstall of
the old release and do a fresh installation by paying attention to the following steps
 Login to the Solution Manager system to which, the Agent to be upgraded, is connected
– Navigate to the Agent Administration to write down the
“Server name” that was used by the old Agent
– Perform also a “Reset server name” using the contextual
menu of that Agent and finally stop the Agent
 Install the new Diagnostics Agent release using a different SID (no upgrade tool available)
 Assign the same “Server Name” to the newly installed Agent using the smdsetup script (see
details in the Agent troubleshooting guide). Do not confuse “server name” and host name.
 For Java Managed systems run again the “Configure Wily Introscope Agent” (a.k.a. “Byte
Code Adapter Installation”) in solman_setup transaction / “Managed System Configuration”
– This updates the Managed system JVM parameters so that the Introscope Agent binaries will be taken
from the directory structure of the new Diagnostics Agent (instead of the old Diagnostics Agent).
 Restart the Java Managed system
 Finally, uninstall the Diagnostics Agent using sapinst

© 2011 SAP AG. All rights reserved. 21

Diagnostics Agent removal

Rule #6:
Use the Diagnostics Agent installer to remove / uninstall a Diagnostics Agent
instance
 IMPORTANT: Comply with following remark in case the Diagnostics Agent to be
uninstalled has been used (for Java Managed systems) at some point in time during the
execution of “Configure Wily Introscope Agent” (a.k.a. “Byte Code Adapter Installation”) in
solman_setup / “Managed system configuration”
 In case you plan to simply remove the Diagnostics Agent (independently from the
Diagnostics Agent upgrade-process indicated on the previous slide), you need to also:
– Remove the JVM parameters on the Java Managed system that are used to start/run the Introscope
Byte Code Agent. To have the list of parameters refer to SAP note: 797147. In general the parameters
are like: -Xbootclasspath and -Dcom.wily….
– Especially the JVM parameter makes you understand that there is an interdependence between the
Introscope Byte Code Agent (run by the Managed system) and the Diagnostics Agent directory
structure you are planning to remove:
Xbootclasspath/p:D:/usr/sap/DAA/SMDA77/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.3.5-2011-01-
14/wily/connectors/AutoProbeConnector.jar;D:/usr/sap/DAA/SMDA77/SMDAgent/applications.config/com.sap.smd.agent.application.wily/BytecodeAgent/ISAGENT.8.2.
3.5-2011-01-14/wily/Agent.jar

– Restart the Java Managed system to no longer run the Introscope Byte Code Agent
– Run the Diagnostics Agent installer SAPInst to start the Diagnostics Agent uninstall option
© 2011 SAP AG. All rights reserved. 22