Upload
kufor
View
97
Download
0
Embed Size (px)
DESCRIPTION
Installation Strategy for SAP Diagnostics Agents
Citation preview
Agent installation strategy Solution Manager 7.1 and 7.0 EhP1(SP20 and higher)
July 2011 October 2012 Public
2012 SAP AG. All rights reserved. 2
Agenda 1/2
Introduction
What is needed and where ?
Choose Diagnostics Agent or Agents On-the-fly
Diagnostics Agents
Agents On-the-fly
Landscape Examples
SAP Host Agent
Diagnostics Agent Characteristics
Diagnostics Agents are SAP Systems
Diagnostics Agent File Structure
Diagnostics Agent Releases information
Latest Diagnostics Agent Releases
Diagnostics Agent Release Constraints
Diagnostics Agent PAM
Diagnostics Agent Release Characteristics
2012 SAP AG. All rights reserved. 3
Agenda 2/2
Diagnostics Agent and SLD Registration
Diagnostics Agent Mass Installation
Diagnostics Agent Maintenance
Diagnostics Agent Upgrade
Diagnostics Agent Replacement
Diagnostics Agent Removal
2012 SAP AG. All rights reserved. 4
Introduction
Scope
The following rules apply to both Solution Manager 7.0 EhP1 and 7.1, unless they are
tagged [7.0 EhP1 only] or [7.1 only]
Terminology
The term host in this slide set does not designate network alias. Hosts must have their own IP addresses.
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 more additional host names and dedicated IP addresses. This is
used, for example, to move systems from one physical host to another.
N.B.: To find the host name of an ABAP system, use transaction sm51, and for Java
systems refer to the System Info Web page.
2012 SAP AG. All rights reserved. 5
What is needed and where? (Diagnostics Agent or Agents On-the-fly)
New feature available
Solution Manager 7.1 SP05 provides a new feature named Agents On-the-fly
Agents On-the-fly concept introduces automatic Agent instantiations to address specifically the following use cases:
Managed systems in High Availability environments
Physical or Virtual hosts running a high number of Logical hosts (outside High Availability environments)
Further details on Agents On-the-fly available in online documentation : Click here
Existing installations
Previous Diagnostics Agent installation process is still valid.
Operate either classic Diagnostics Agents or Agents On-the-fly, depending on each Managed system environment.
Diagnostics Agent installations already in place are still valid and do not necessarily need to be replaced by the Agent On-the-fly feature. Nevertheless in High Availability environments it
could be of interest to put Agent On-the-fly in place.
2012 SAP AG. All rights reserved. 6
What is needed and where? (Diagnostics Agents)
Rule #1:
Install the required number of Diagnostics Agents
In the context of each Solution Manager System use only one Diagnostics Agent or Agent On-the-fly per Managed host. Managed hosts are primarily logical hosts, or if not applicable
physical/virtual hosts (as shown on the next slides)
Each Diagnostics Agent or Agent On-the-fly manages, on behalf of one Solution Manager, the systems/components running on the host on which it is running (and represents that host)
following slides explain what is a supported systems/components
repeat the Managed System configuration (solman_setup) on each Solution Manager for each Technical System running on these hosts (logical host, or if not applicable physical/virtual host).
Activities Byte Code Adapter Installation and Introscope Host Adapter have to be performed only in one leading Solution Manager system (see page 10)
For landscapes with logical host names and in case Agents On-the-fly are not used, specify, during the Diagnostics Agent installation, each time the logical host name
When installing an (additional) Agent for a logical host, using the Diagnostics Agent installation
package, provide the short hostname, in the SAPInst step requesting a Virtual host name.
2012 SAP AG. All rights reserved. 7
What is needed and where? (Diagnostics Agents)
Rule #1 (details):
Install required number of Diagnostics Agents (not applicable in context of Agents On-the-fly)
PhyHost2
or VMware
PhyHost3 .
or VMware .
LogicalHost1 LogicalHost2 LogicalHost3
PhyHost1 or VMware
C1 C2 C3 C4 C5 C6
Only one Diagnostics Agent for each Solution
Manager must exist per physical, virtual or logical
host running a managed component
A Diagnostics Agent will support the managed
components installed/operated with that hostname
Each Diagnostics Agent is uniquely identifiable in
Solution Manager via that (short) hostname
Own one SAP Host Agent per physical or virtual
host
C7 C8
Diagnostics Agent
Managed Component
(see following slides)
SAP Solution Manager SAP Host Agent
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 5 HA
DA
2012 SAP AG. All rights reserved. 8
What is needed and where? (Agents On-the-fly)
Rule #1 (continued):
How to use Agents On-the-fly (available with Solution Manager 7.1 SP05)
Mandatory context:
Managed systems in High Availability environments
Physical or Virtual hosts running a high number of Logical hosts (outside High Availability environments)
Use case:
2012 SAP AG. All rights reserved. 9
What is needed and where? (Agents On-the-fly)
Rule #1 (continued):
How to use Agents On-the-fly (available with Solution Manager 7.1 SP05)
Preparation
Diagnostics Agent landscape preparation:
Remove existing Diagnostics Agents at Physical, Virtual and Logical host level (in concerned landscape)
Pay attention to recommendations for Diagnostics Agents Removal, to avoid potential Java Managed
System startup failures (see page 29)
Install Diagnostics Agents only at Physical or Virtual host level, without specifying any Logical hostname, using the Diagnostics Agent standalone installation package 7.30 SP02 (SAPInst )
2012 SAP AG. All rights reserved. 10
What is needed and where? (Agents On-the-fly)
Rule #1 (continued):
How to use Agents On-the-fly (available with Solution Manager 7.1 SP05)
Configuration
Diagnostics Agent Configuration:
Start the Host configuration for each Physical or Virtual host
Available under solman_setup / Managed System Configuration / Hosts
Especially enable the Agents On-the-fly feature within step Enter System Parameters
Adjust exclusion filters to have only relevant logical hosts, before saving press button.
Logical host filtering-impact simulation is available via Display resulting host list button. Defining appropriate filters will avoid having irrelevant Agents On-the-fly instantiated.
Agents On-the-fly get instantiated by the Diagnostics Agent running on the Physical or Virtual Host,
as soon as the Enter System Parameters step is saved.
Using Agents On-the-fly:
Simply run as usual solman_setup / Managed System Configuration for implied Managed Systems
In case no Agent On-the-fly for the Managed System logical hosts is visible within the step Assign Diagnostics Agents (similar to Diagnostics Agents), double check above pre-requisite items.
Online documentation available: Click here
2012 SAP AG. All rights reserved. 11
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
Number of Diagnostics Agents depends on managed component distribution
Example where all components run with one hostname (physical, virtual or logical)
Solution Manager
ABAP Central Instance + ABAP Central Services
Java Central Instance
DB
Java Central Services
Enterprise Portal
Central Instance
Dialog Instance
DB
Central Services
Diagnostics Agent
ERP / ECC Server
Central Instance + ABAP Central Services
Dialog Instance
Diagnostics Agent Diagnostics Agent
DB
Du
al
sta
ck o
n 1
Ho
st
Ja
va
sta
ck o
n 1
Ho
st
AB
AP
sta
ck o
n 1
Ho
st
2012 SAP AG. All rights reserved. 12
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
Number of Diagnostics Agents depends on managed component distribution
Example where each component runs with different hostnames (physical, virtual or logical)
(1) In the context of High Availability environments consider to use the Agents On-the-fly feature available since Solution Manager 7.1 SP05
Solution Manager
ABAP Central Instance + ABAP Central Services
Java Central Instance
DB
Java Central Services
Enterprise Portal
Central Instance
Dialog Instance
DB
Java Central Services
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
ERP / ECC Server
Dis
trib
ute
d D
ua
l sta
ck
Dis
trib
ute
d J
ava
sta
ck
Dis
trib
ute
d A
BA
P s
tack
(1) Agent required in the scope
of Solution Manager 7.1
(1) Agent required in the
scope of Solution Manager 7.1
Central Instance
Dialog Instance
DB
ABAP Central Services
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
(1) Agent required in the scope
of Solution Manager 7.1
Diagnostics Agent Diagnostics Agent
Possible since Solution
Manager 7.1 SP08
Possible since Solution
Manager 7.1 SP08
2012 SAP AG. All rights reserved. 13
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
Covering 3-system landscape by installing an additional Diagnostics Agent (QA Portal)
and extracting QA Portal perf. data
from Dev IS EM
Dev Introscope
Enterprise Manager
3-S
ys
tem
lan
dscap
e
Prod Introscope
Enterprise Manager
Dev Enterprise Portal
Diagnostics Agent
Introscope
Adapters
QA Enterprise Portal
Prod Enterprise Portal
Diagnostics Agent
Introscope
Adapters
Use Dev IS EM to
retrieve perf. data of
QA Managed systems
Solution Manager
Collected config. of
managed systems
Dev & QA
Comparison possible
Solution Manager
Collected config. of
managed systems
QA & Prod
Comparison possible
Dev S
olM
an
P
rod
So
lMa
n
IMPORTANT
Mark the activities Byte Code Adapter Installation and Introscope Host Adapter as Postponed on the prod. SolMan, for the QA
Portal Managed system,
when running solman_setup /
Managed system configuration. (Otherwise the Introscope Adapters
of the QA Portal would report their
data to the prod. IS EM, what is not
expected here.)
Diagnostics Agent
Diagnostics Agent
Introscope
Adapters
Introscope
Adapter
2012 SAP AG. All rights reserved. 14
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
[7.1 only] 3-system landscape requires a 2nd Diagnostics Agent (Dev IS EM)
Dev Introscope
Enterprise Manager
Prod. Introscope
Enterprise Manager
Dev Enterprise Portal
QA Enterprise Portal
Prod Enterprise Portal
Dev S
olM
an
P
rod
So
lMa
n
Diagnostics Agent
Diagnostics Agent
Solution Manager
Collected config. of
managed systems
QA & Prod
Solution Manager
Collected config. of
managed systems
Dev & QA
3-S
ys
tem
lan
dscap
e
Diagnostics Agent
IMPORTANT
Install a second Diagnostics
Agent instance, re-using the
System ID (SID) of the
Diagnostics Agent installed
initially on the dev. IS EM
host. (Otherwise two Diagnostics Agent
OS users would access the dev. IS
EM files. In case one OS user
updates via solman_setup some
files, the other OS user would
therefore encounter access denied
errors, especially if the umask is not
set to 007.)
2012 SAP AG. All rights reserved. 15
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
3-system landscape
(continued)
Managed systems
in a given E2E solution
(Dev, QA or Prod)
must be connected to the
same Solution Manager
system
Prod Introscope
Enterprise Manager
Dev Enterprise Portal
Diagnostics Agent
Introscope
Adapters
QA Enterprise Portal
Diagnostics Agent
Introscope
Adapters
Prod Enterprise Portal
Diagnostics Agent
Introscope
Adapters
Dev ECC Server
Diagnostics
Agent
Introscope
Adapter
QA ECC Server
Diagnostics
Agent
Introscope
Adapter
Prod ECC Server
Diagnostics
Agent
Introscope
Adapter
Pro
d S
olM
an
Dev System landscape
QA System landscape
Prod System landscape
Solution Manager
Prod Managed
Systems data
EP & ECC
E2E Trace Analysis
2012 SAP AG. All rights reserved. 16
What is needed and where? (SAP Host Agent)
Rule #2:
Have up-to-date SAP Host Agents
See SAP note 1365123 for the current minimum version
This note also confirms whether the installation/upgrade of the SAP Host Agent, performed by the installation of a Diagnostics Agent (installer 7.30 SPxx) covers currently known defects.
Install a SAP Host Agent if none has yet been installed (one per physical host)
Check whether there is a SAP Host Agent using the following path:
o For Windows look under: "%ProgramFiles%"\SAP\hostctrl
o For Unix, under: /usr/sap/hostctrl/
Update the SAP Host Agent according to SAP note 1031096, if the version is not sufficient
Check version at OS level (looking in the output at SAPHOSTAGENT Information):
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 the host browsing, if 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 -> -> Host Status
2012 SAP AG. All rights reserved. 17
What is needed and where? (SAP Host Agent)
Rule #2 (continued):
Have up-to-date SAP Host Agents
Implement automatic upgrade process (especially if you plan an update)
SAP note 1473974 describes ways to upgrade centrally and automatically, running SAP Host Agents.
2012 SAP AG. All rights reserved. 18
Diagnostics Agents are SAP Systems
Rule #3:
The Diagnostics Agent is a standard SAP system
The same rules apply as for any standard SAP system
Do not install an Agent in the directory structure of another SAP system (or copy or move the files)
Agents must be independent of any other system installation
Several Diagnostics Agents can be installed using the same SID, but different instance numbers, in case they use the same kernel.
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)
2012 SAP AG. All rights reserved. 19
Diagnostics Agents are SAP Systems
Rule #3 (details):
Alternatives for installing multiple Diagnostics Agents on the same host
These Agents have to be connected to different Solution Manager systems
Use the same dedicated System ID (and different instance numbers)
Exception: Do not use a same SID for Diagnostics Agents with different kernel releases (this is prevented by the latest installers).
Using different System IDs (and different instance numbers)
Allows independent installations, but requires internal distinct SID allocation rules in case the file system is mounted. It is indeed strictly forbidden to share the same Agent binaries/configuration files
for multiple Agent instances. In particular, a same Diagnostics Agent file system installation must NOT
be mounted and executed on several hosts at the same time.
2012 SAP AG. All rights reserved. 20
Diagnostics Agent File Structure
Description 7.0 / 7.01 SR1 7.11 / 7.20 / 7.30 SP02
Global exe /usr/sap//exe /usr/sap//SYS/exe
SAPJVM No SAPJVM (using separately installed JDK) /usr/sap//SYS/exe/jvm
global directory /usr/sap//SYS/global /usr/sap//SYS/global
profile directory /usr/sap//SYS/profile /usr/sap//SYS/profile
Instance directory /usr/sap//J /usr/sap//SMDA
script directory /usr/sap//J/script /usr/sap//SMDA/script
work directory /usr/sap//J/work /usr/sap//SMDA/work
Local exe No local exe directory /usr/sap//SMDA/exe (1)
Local SAPJVM No SAPJVM /usr/sap//SMDA/exe/sapjvm_xx (1)
Agent software and
properties files
/usr/sap//J/SMDAgent /usr/sap//SMDA/SMDAgent
Agent logs /usr/sap//J/SMDAgent/log /usr/sap//SMDA/SMDAgent/log
(1) Contains executable kernel programs that are replicated (files moved for the SAPJVM) from SYS/exe
every time the agent instance is started.
2012 SAP AG. All rights reserved. 21
Latest Diagnostics Agent Release
Rule #4:
Use the standalone Diagnostics Agent installation package 7.30 SP02, when
installing a Diagnostics Agent to comply with rule #3.
A summary of Diagnostics Agents releases and characteristics is on the next slide
With Solution Manager release lower than 7.0 EhP1 SP20 only use older Diagnostics Agent release 7.01 SR1.
This Diagnostics Agent release is installable with the help of the SAP EhP1 for SAP
NetWeaver 7.0 Installation Master, Kernel & Java DVDs. A separately installed JDK 1.4.2 is
also required.
2012 SAP AG. All rights reserved. 22
Diagnostics Agent Release Constraints
Agent releases 7.0 / 7.01 SR1 7.20 7.30 SP02
Compatible with Solution
Manager
Solution Manager
lower than 7.0 EhP1 SP 20
(1)
Solution Manager
since 7.0 EHP1 SP20 (included)
(1)(2)
Solution Manager
since 7.0 EHP1 SP20 (included)
(1)(2)
Support Managed system
NW releases 6.40, 7.00 and higher 6.40, 7.00 and higher 6.40, 7.00 and higher
Installation SAP note 1357812 1368413 1448655
(1) When a Solution Manager system is upgraded, the Diagnostics Agents do not generally need to be upgraded manually.
See next slide and rule #5. IMPORTANT: Rule #2 must be followed.
(2) N.B.: This Diagnostics Agent release is also applicable to Solution Manager 7.1.
Installer recommended
when new installation required
(See OS platform support on next slide)
Installer recommended
when new installation required
(See OS platform support on next slide)
2012 SAP AG. All rights reserved. 23
Diagnostics Agent OS platform support (PAM) 1/2
Platform family Platform release Installer to be used
Windows
Server 2003 - IA32 / IA64 / X64
Server 2003 R2 - IA32 / X64
Server 2008 - IA32 / IA64 / X64
Server 2008 R2 - IA64 / X64
Diagnostics Agent (Standalone) installer 7.30 SP2
AIX 5.3 - Power 64-bit Diagnostics Agent (Standalone) installer 7.20
6.1, 7.1 - Power 64-bit Diagnostics Agent (Standalone) installer 7.30 SP2
HP-UX 11.23 - IA64 Diagnostics Agent (Standalone) installer 7.20
11.31 - IA64 Diagnostics Agent (Standalone) installer 7.30 SP2
IBM i 5.4 - Power 64-bit Diagnostics Agent (Standalone) installer 7.20
6.1, 7.1 - Power 64-bit Diagnostics Agent (Standalone) installer 7.30 SP2
Linux REDHAT (RHEL)
EL4 - IA64 / X64 / Power 64-bit Diagnostics Agent (Standalone) installer 7.20
EL5 - IA64 / X64 / Power 64-bit Diagnostics Agent (Standalone) installer 7.30 SP2
EL6 - X64 / Power 64-bit (3) Diagnostics Agent (Standalone) installer 7.30 SP2
EL5 - System z 64-bit NW CE 7.20 (1) (section z/OS (OS/390))
EL6 - System z 64-bit NW 7.30 EHP1 (1) (section z/OS (OS/390))
z/OS 1.10, 1.11, 1.12, 1.13 - System z 64-bit Planned availability Q2/2013
Using some of the above listed combinations might lead to a warning in the Prerequisite Checker Results step while installing the
Diagnostics Agent. This warning could be ignored in case the above mentioned Diagnostics Agent (Standalone) installer release for
the respective OS platform has been used.
Legend: IA32 means x86 32-bit, IA64 means Itanium 64-bit, X64 means x86 64-bit.
2012 SAP AG. All rights reserved. 24
Diagnostics Agent OS platform support (PAM) 2/2
Platform family Platform release Installer to be used
Solaris
9 - SPARC 64-bit
10 - SPARC 64-bit / X64
11 - SPARC 64-bit / X64 (2)
Diagnostics Agent (Standalone) installer 7.30 SP2
Linux SUSE
SLES 9 - IA32 / IA64 / X64 / Power 64-bit Diagnostics Agent (Standalone) installer 7.20
SLES 10, 11 SP1 - IA32 / IA64 / X64 / Power 64-bit Diagnostics Agent (Standalone) installer 7.30 SP2
SLES 11 SP2 (Kernel 3.x) (3) - Diagnostics Agent (Standalone) installer 7.30 SP2
SLES 9, 10, 11 SP1 - System z 64-bit NW CE 7.20 (1) (section z/OS (OS/390))
SLES 11 SP2 - System z 64-bit NW 7.30 EHP1 (1) (section z/OS (OS/390))
Oracle Linux 5 - X64 Diagnostics Agent (Standalone) installer 7.30 SP2
6 - X64 Diagnostics Agent (Standalone) installer 7.30 SP2
(1) Download from http://service.sap.com/swdc -> Installations & Upgrades -> Browse our Download Catalog -> SAP Netweaver and
complementary products -> -> -> Installation & Upgrade -> z/OS (OS/390) ->
NW 7.31 Kernel, Inst.Mast., UP Master Linux zSeries 64-bit
or NW CE 7.2 LINUX IA64, zSeries Inst.master, Kernel + additionally download NW CE 7.2 Application, Dev. WP 32-bit
(2) Follow procedure of SAP Note 1707141 to upgrade Diagnostics Agent Kernel to 720_EXT (See also Kernel SAP note 1563102).
Concerning general Solaris 11 recommendations see SAP note 1643799.
(3) Follow procedure of SAP Note 1707141 to upgrade Diagnostics Agent Kernel to 720_EXT (See also Kernel SAP note 1563102).
Concerning general SLES 11 SP2 recommendations see SAP note 1629558.
Using some of the above listed combinations might lead to a warning in the Prerequisite Checker Results step while installing the
Diagnostics Agent. This warning could be ignored in case the above mentioned Diagnostics Agent (Standalone) installer release for
the respective OS platform has been used.
2012 SAP AG. All rights reserved. 25
(1) No separate (stand-alone) Diagnostics Agent installation package (reduced size)
(2) Server Name could be provided. Server name is a unique key, based on the Managed short host name.
(3) IAIK libraries need to be provided manually
(4) Also allows to configure the trusted connection @ SAP Host Agent level, automatically
Diagnostics Agent Release Characteristics
Agent releases 7.0 - 7.01 SR1 (1)(2) 7.11 7.20 7.30 SP02 (4)
Already installed silently,
with products based on 7.0 & EhP1 NW
Java or dual stacks PI & CE 7.1 EhP1
CE 7.20 & NW 7.0
EhP2 NW Java,
ABAP or dual stacks
NW 7.3x (and 7.0
EhP3) Java, ABAP or
dual stacks
Kernel release (SAP Products) / Patch level with standalone installer
7.0 - 7.01 7.11 7.20 /
patch 36
7.20(_EXT) /
patch 105
JVM JDK 1.4.2 (installed separately/out of maint.)
SAPJVM 5 SAPJVM 6 SAPJVM 6
Default System ID / Instance SMD
/ J
DAA
/ SMDA
DAA
/ SMDA
DAA
/ SMDA
Support both direct
connection to SolMan & SLD
registration @ installation
No No Yes Yes (Support offline mode)
SSL & SAPRouter Support
@ installation No No Yes (3) Yes
SAP Host Agent needed Yes (install manually) Except for SolMan prior to 7.0EhP1
SP20 using local saposcol binary
Yes (install
manually) Yes (auto-install)
Yes (auto-installed/
updated) (4)
Installation SAP note 1357812 1234387 1368413 1448655
Agent start/stop/control smdstart/stop/admin Standard Standard Standard
2012 SAP AG. All rights reserved. 26
Diagnostics Agent and SLD Registration
Available Diagnostics Agent connectivity options per installation scenario:
1. Diagnostics Agent is already installed silently with a managed system
The agent is registered in the System Landscape Directory specified during the managed system installation
o The agent could be connected to Solution Manager using, for example, solman_setup -> Managed
System Configuration. This will configure the agent remotely, to connect to Solution Manager via the
Message Server.
No System Landscape Directory is specified during the managed system installation
o 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).
2012 SAP AG. All rights reserved. 27
Diagnostics Agent and SLD Registration
2. Agent is installed using a Diagnostics Agent standalone installation package
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 number of activities
to be performed in solman_setup.
Solution Manager connectivity data can be re-pushed to running Diagnostics Agents (useful in case of operational issues), in case the agent was also registered in a central System Landscape Directory.
NEW: Operational issues concerning Diagnostics Agents to Solution Manager connectivity can be
easily resolved via the Non-authenticated Agents list, available with Solution Manager 7.1 SP05.
Prerequisite: Diagnostics Agent was connected to a Solution Manager 7.1 SP05 system at least once.
2012 SAP AG. All rights reserved. 28
Diagnostics Agent Mass Installation
Use the SAPInst unattended mode to install Diagnostics Agents rapidly over a
wide consistent landscape
Unattended mode allows the Diagnostics Agent standalone installation package to install a number of agents in silent mode
Installation template available for Diagnostics Agents 7.20 in SAP note 1294713
Installation template available for Diagnostics Agents 7.30 in SAP note 1486330
2012 SAP AG. All rights reserved. 29
Diagnostics Agent Upgrade
Rule #5:
No need to upgrade Diagnostics Agents (in contrast to SAP Host Agent)
Diagnostics Agents take their business logic (software) from the Solution Manager system
to which they are connected
All Diagnostics Agents running and connected in the landscape are centrally patched by applying an LM-
SERVICE Java Software Component Archive on the Solution Manager system
Diagnostics Agent Installation SAP notes include a guide and simple manual procedures needed to resolve known punctual issues (support of cryptography, ). Alternatively, use the later described Agent replacement procedure.
Some OS platform constraints might require a Diagnostics Agent Kernel upgrade. See SAP note 1707141.
2012 SAP AG. All rights reserved. 30
Diagnostics Agent Replacement
Rule #5 (continued):
To replace a Diagnostics Agent uninstall the previous Agent and install the
new required release:
Reset server name
Login to the Solution Manager system to which the agent to be upgraded is connected
Navigate to the Agent Administration and note the server name of the old agent
Reset server name using the context menu of the agent, and stop the agent
Install new Diagnostics Agent release using a different SID (no upgrade tool available)
Assign the same Server Name to the new Agent using the smdsetup script (see details in the Diagnostics Agent troubleshooting guide).
Java based Managed systems require to take some specific actions (see next slide)
Uninstall the previous Diagnostics Agent using SAPInst
2012 SAP AG. All rights reserved. 31
Diagnostics Agent Replacement
Rule #5 (In context of Java Managed System):
In case the Ensure HA virtualization compatibility option was not used in the past:
Configure again the Wily Introscope Agent (Byte Code Adapter Installation) using transaction solman_setup -> Managed System Configuration -> Configure Automatically
Pre-requisite since Solution Manager 7.1 SP05:
Mark additionally the option "Ensure HA virtualization compatibility" within step "Enter System
Parameters". Also ideally provide only a relative path name like ByteCodeAdapter for the "Introscope
BC Adapter deployment path" field, in order to locate the Byte Code Adapter binaries and configuration
files inside the Managed system directory structure (/usr/sap//).
The Diagnostics Agent OS user (members of the SAPSYS OS group) must therefore also have write
permissions at this Managed System path location. See SAP note 1163751
Restart the Java managed system
This procedure updates the Managed System JVM parameters so that the Introscope Byte Code Adapter
binaries are no longer taken from the previous old Diagnostics Agent directory structure.
2012 SAP AG. All rights reserved. 32
Diagnostics Agent Removal
Rule #6:
To remove a Diagnostics Agent instance installed for a specific hostname:
In case the solman_setup Ensure HA virtualization compatibility option was used in the past to setup the Byte Code Adapter of the Java Managed System(s) running on that host
Optionally: Uninstall also the Byte Code Adapter by removing the JVM parameters listed in SAP note
797147
Else, take the following actions (in case the Ensure HA virtualization compatibility option was not used in the past during the solman_setup Managed System Configurations):
IMPORTANT: Remove JVM parameters listed in SAP note 797147 on the Java Managed System
used to start/run the Introscope Byte Code Adapter.
Finally restart the Java Managed system to no longer run the Introscope Byte Code Agent
The Managed System JVM parameters (to be removed) show that the Introscope Byte Code Adapter executed inside the Managed System uses files from Diagnostics Agent directory structure:
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
Run the Diagnostics Agent installer SAPInst, to uninstall the Diagnostics Agent