Byte Code Adapter

Agent installation strategy
Solution Manager 7.1 and 7.0 EhP1(SP20 and higher)
July 2011 – October 2012

Public

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

 DiagnosticsAgent 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.

2

Agenda 2/2
Diagnostics Agent and SLD Registration
Diagnostics Agent Mass Installation
Diagnostics Agent Maintenance
 Diagnostics AgentUpgrade
 Diagnostics Agent Replacement
 Diagnostics Agent Removal

© 2012 SAP AG. All rights reserved.

3

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 „Virtualhost‟ 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 Javasystems refer to the System Info Web page.

© 2012 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 inHigh 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 oneach 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.

5

What is needed and where? (Diagnostics Agents)

Rule #1:
Installthe 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 runningon 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...