AgentInstallationStrategy
22 pág.

AgentInstallationStrategy


DisciplinaGeometria Analítica13.059 materiais367.856 seguidores
Pré-visualização3 páginas
Agent installation strategy 
Solution Manager 7.1 
 
July 2011 \u2013 December 2014 Public 
© 2014 SAP AG. All rights reserved. 2 
Agenda 
Introduction 
What is needed and where ? 
\uf09f Choose Diagnostics Agent or Agents On-the-fly 
\uf09f Diagnostics Agents 
\uf09f Agents On-the-fly 
\uf09f Landscape Examples 
\uf09f SAP Host Agent 
Diagnostics Agent Characteristics 
\uf09f Diagnostics Agents are SAP Systems 
\uf09f Latest Diagnostics Agent Releases 
\uf09f Diagnostics Agent Release Characteristics 
Diagnostics Agent and SLD Registration 
Diagnostics Agent Mass Installation 
Diagnostics Agent Maintenance Procedures 
\uf09f 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 \u2018host\u2019 in this slide set does not designate network alias. Hosts must have 
their own IP addresses. 
A \u2018virtual host\u2019 designates a simulated host running for example on top of a VMware. 
A \u2018logical host\u2019 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 
\uf09f Solution Manager 7.1 SP05 provides a new feature named Agents On-the-fly 
\uf09f Agents On-the-fly concept introduces automatic Agent instantiations to address specifically 
the following use cases: 
\u2013 Managed systems in High Availability environments 
\u2013 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 
\uf09f Install Diagnostics Agents as usual, using the SWPM. 
\uf09f 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 
\u201clogical hostname\u201d, 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 
\uf09f 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) 
\uf09f 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) 
\u2013 following slides explain which systems/components are supported 
\u2013 repeat the \u201cManaged System Configuration\u201d (solman_setup) on each Solution Manager for each 
Technical System running on these hosts (logical host, or if not applicable physical/virtual host). 
Activities \u201cByte Code Adapter Installation\u201d and \u201cIntroscope Host Adapter\u201d have to be performed only in 
one \u201cleading\u201d Solution Manager system (see page 12) 
\uf09f 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 
\uf06e Only one Diagnostics Agent for each Solution 
Manager must exist per physical, virtual or logical 
host running a managed component 
\uf06e A Diagnostics Agent will support the managed 
components installed/operated with that host name 
\uf06e Each Diagnostics Agent is uniquely identifiable in 
Solution Manager via that (short) host name 
\uf06e 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) 
\uf09f Mandatory context: 
\u2013 Managed systems in High Availability environments 
\u2013 Physical or virtual hosts running a high number of logical hosts (outside High Availability environments) 
\uf09f 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 
 
\uf09f Diagnostics Agent landscape preparation: 
 
\u2013 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). 
 
\u2013 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 
\uf09f Diagnostics Agent Configuration: 
\u2013 Start the \u201cHost configuration\u201d for each Physical or virtual host 
Available under solman_setup / Managed System Configuration / Hosts 
\u2013 Especially enable the \u201cAgents On-the-fly\u201d feature within step \u201cEnter System Parameters\u201d 
Adjust exclusion filters to have only relevant logical hosts, before pressing save button. 
Logical host filtering-impact simulation is available via \u201cDisplay resulting host list\u201d button. 
Defining appropriate filters will avoid having \u201cirrelevant\u201d 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 \u201cEnter System Parameters\u201d step is saved. 
 
\uf09f Using Agents On-the-fly: 
\u2013 Simply run as usual solman_setup / \u201cManaged System Configuration\u201d for implied managed systems 
In case no Agents On-the-fly for the managed system logical hosts are visible within the step \u201cAssign 
Diagnostics Agents\u201d (similar to Diagnostics Agents), double check above pre-requisite items. 
 
\uf09f 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 
\uf09f 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