Agent installation strategy Solution Manager 7.1
July 2011 – December 2014 Public
© 2014 SAP AG. All rights reserved. 2
Agenda
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
Latest Diagnostics Agent Releases
Diagnostics Agent Release Characteristics
Diagnostics Agent and SLD Registration
Diagnostics Agent Mass Installation
Diagnostics Agent Maintenance Procedures
Diagnostics Agent Upgrade/Replacement/Removal
© 2014 SAP AG. All rights reserved. 3
Introduction
Scope
The following rules apply to Solution Manager 7.1.
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.
© 2014 SAP AG. All rights reserved. 4
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
Agent installations
Install Diagnostics Agents as usual, using the SWPM.
Decide to operate either classic Diagnostics Agents or Agents On-the-fly, depending on each
host topology. Agents On-the-fly enabling is done with SOLMAN_SETUP (See above doc).
Note: It is not necessary to replace existing Diagnostics Agents, that were installed using a
“logical hostname”, except in the logical hostname is subject to move (specifically in High
Availability environments).
© 2014 SAP AG. All rights reserved. 5
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 one
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 which systems/components are supported
– 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 12)
For landscapes with logical host names and in case Agents On-the-fly are not used,
specify the the logical host name during Diagnostics Agent installations.
When installing an (additional) Agent for a logical host, using the Diagnostics Agent installation
package, provide the short host name in the Software Provisioning Manager step "Diagnostics Agent
Host".
© 2014 SAP AG. All rights reserved. 6
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 host name
Each Diagnostics Agent is uniquely identifiable in
Solution Manager via that (short) host name
Have one SAP Host Agent per physical or virtual
host
C7 C8
Managed Component
(see following slides)
SAP Solution Manager
SAP Host
Agent
Diagnostics
Agent 1
SAP Host
Agent
Diagnostics
Agent 2
Diagnostics
Agent 4
Diagnostics
Agent 3
SAP Host
Agent
Diagnostics
Agent 5
© 2014 SAP AG. All rights reserved. 7
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:
© 2014 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)
Preparation
Diagnostics Agent landscape preparation:
– Remove existing Diagnostics Agents at Physical, virtual and logical host level (in affected landscape).
Pay attention to recommendations for Diagnostics Agents Removal, to avoid potential Java managed
system startup failures (see rule #6).
– Install Diagnostics Agents only at Physical or virtual host level, without specifying any logical host
name, using latest Diagnostics Agent installation package. See SAP note 1833501.
© 2014 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)
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 pressing save 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 Agents On-the-fly for the managed system logical hosts are visible within the step “Assign
Diagnostics Agents” (similar to Diagnostics Agents), double check above pre-requisite items.
Online documentation available: Click here
© 2014 SAP AG. All rights reserved. 10
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 host name (physical, virtual or logical)
Solution Manager
ABAP Instance + ABAP Central Services
Java Instance
DB
Java Central Services
Enterprise Portal
Java Instance
Java Dialog Instance
DB
Java Central Services
Diagnostics Agent
ERP / ECC Server
ABAP Instance + ABAP Central Services
ABAP 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
© 2014 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 each component runs with different host names (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 Instance + ABAP Central Services
Java Instance
DB
Java Central Services
Enterprise Portal
Java Instance
Java Dialog Instance
DB
Java Central Services
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
ERP / ECC Server
Dis
trib
ute
d D
ual
sta
ck
Dis
trib
ute
d J
ava s
tack
Dis
trib
ute
d A
BA
P s
tack
ABAP Instance
ABAP Dialog Instance
DB
ABAP Central Services
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent
Diagnostics Agent Diagnostics Agent
Possible since Solution
Manager 7.1 SP08
Possible since Solution
Manager 7.1 SP08
Diagnostics Agent
Possible since Solution
Manager 7.1 SP08
© 2014 SAP AG. All rights reserved. 12
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
Covering 3-system landscape: Enable full RCA of QA Portal managed system on both SolMans,
by installing an additional Diagnostics Agent
and extracting QA Portal performance data
from Prod IS Enterprise Manager (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 Prod IS EM to
retrieve performance
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
lMan
IMPORTANT
On the Dev SolMan, when
running SOLMAN_SETUP /
“Managed System
Configuration” for the QA
Portal managed system,
mark the activities “Byte
Code Adapter Installation”
and “Introscope Host
Adapter” as “Postponed”.
(Otherwise the Introscope Adapters
of the QA Portal would report their
data to the Dev IS EM, what is not
expected here.)
Diagnostics Agent
Diagnostics Agent
Introscope
Adapters
Introscope
Adapter
© 2014 SAP AG. All rights reserved. 13
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
3-system landscape requires a 2nd Diagnostics Agent (Prod 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
lMan
Diagnostics Agent
Diagnostics Agent
Solution Manager
Collected config. of
managed systems
QA & Prod
Solution Manager
Collected config. of
managed systems
Dev & QA
3-S
yste
m l
an
dscap
e
Diagnostics Agent
IMPORTANT
On the Prod IS EM host, install a
second Diagnostics Agent, using
a distinct System ID (SID). Also
pay attention to potential file
permission conflicts. For
instance, the Prod Agent OS user
will at one point in time update the
Prod IS EM config files (via
SOLMAN_SETUP transaction).
So, inappropriate file access
permissions prevent the second
Dev Agent OS user from creating
new files, or reading the file during
the Prod IS EM configuration
import.
The OS user group (sapsys on
Unix, or SAP_LocalAdmin
on Windows) must have write
permissions on the IS EM install
path and content. On Unix, OS
users need at least umask 027.
Note: Windows OS users are like
SAPService<AgentSID>.
On Unix <AgentSID>adm.
© 2014 SAP AG. All rights reserved. 14
What is needed and where? (Diagnostics Agent/Agents On-the-fly)
3-system landscape
(continued)
Managed systems
in a given E2E solution
(Per Dev, QA or Prod type)
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
© 2014 SAP AG. All rights reserved. 15
What is needed and where? (SAP Host Agent)
Rule #2:
Have up-to-date SAP Host Agents
See details in SAP SCN wiki:
http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Maintenance+Procedures
© 2014 SAP AG. All rights reserved. 16
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
© 2014 SAP AG. All rights reserved. 17
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 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.
© 2014 SAP AG. All rights reserved. 18
Latest Diagnostics Agent Release
Rule #4:
Use the latest SWPM 1.0 version, when installing a new or an additional
Diagnostics Agent.
See details in SAP SCN wiki:
http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Maintenance+Procedures
© 2014 SAP AG. All rights reserved. 19
(1) Also allows to configure the trusted connection @ SAP Host Agent level, automatically.
(2) For more information refer to SAP Note 1833501.
Diagnostics Agent Release Characteristics
Agent Releases 7.20 7.30 SP03 Latest Agent Release
Installed with NW products
based on …
Old SAPInst based CE 7.20 &
NW 7.0 EhP2 NW Java, ABAP
or dual stacks (silently)
Standalone installation SWPM 1.0 SP04 and higher (2)
JVM SAPJVM 6 SAPJVM 6 SAPJVM 6
Default System ID
/ Instance Number
DAA
/ SMDA<97 to 00>
DAA
/ SMDA<97 to 00>
DAA
/ SMDA<98 to 00>
Support both direct connection
to SolMan & SLD registration @
installation
Yes Yes (support offline mode)
Yes (support offline mode)
SSL & SAPRouter Support @
installation Yes (manually)
Yes (via installer option)
Yes (via installer option)
SAP Host Agent installation Auto-installed Auto-installed/updated (1) Auto-installed/updated (1)
Installation SAP Note 1368413 1829024 1858920
© 2014 SAP AG. All rights reserved. 20
Diagnostics Agent and SLD Registration
New strategy concerning SLD registration:
It is mandatory to connect the Diagnostics Agent to the SAP Solution Manager system,
using SWPM installer.
It is recommended to register the Diagnostics Agent with the System Landscape Directory
(SLD) related to the SAP Solution Manager system, to ensure landscape management
compliance.
Note: Since Solution Manager 7.1 SP05 it is no longer recommended to use the “Agent
Candidate Management” functionality. To repair Diagnostics Agent connectivity, use the
“Non-authenticated Agents” list, available in the Agent Administration UI.
© 2014 SAP AG. All rights reserved. 21
Diagnostics Agent Mass Installation
Use the “mass/unattended mode” to silently install Diagnostics Agents
consistently for large landscapes
Per Software Provisioning Manager 1.0 SP7 (November 2014), a new, simpler version is
available. (see SAP note 1858920 / SWPM 1.0 SP7).
For the former inifile.xml based installation see SAP Note 1833501 / “Mass Deployment
Notes”.
© 2014 SAP AG. All rights reserved. 22
Diagnostics Agent Maintenance Procedures
Rule #5:
For upgrade/replacement of Diagnostics Agents see details in SAP SCN wiki: http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Maintenance+Procedures
Rule #6:
For removal of Diagnostics Agents see details in SAP SCN wiki: http://wiki.scn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Maintenance+Procedures
Top Related