Agent installation strategy

Solution Manager 7.1 and 7.0 EhP1(SP20 and higher)

July 2011 December 2013

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

Diagnostics Agent File Structure

Diagnostics Agent Releases information

Latest Diagnostics Agent Releases
Diagnostics Agent Release Constraints / PAM
Diagnostics Agent Release Characteristics

2013 SAP AG. All rights reserved.

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

2013 SAP AG. All rights reserved.

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.

2013 SAP AG. All rights reserved.

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.

2013 SAP AG. All rights reserved.

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.

2013 SAP AG. All rights reserved.

What is needed and where? (Diagnostics Agents)

Rule #1 (details):
Install required number of Diagnostics Agents

LogicalHost1

LogicalHost3
C1

C2

Diagnostics
Agent 1

SAP Host
Agent

C7

(not applicable in context of Agents On-the-fly)

C8

C3

Diagnostics
Agent 2

LogicalHost2
C4

C5

Diagnostics
Agent 3

Diagnostics
Agent 4

PhyHost2
or VMware

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
2013 SAP AG. All rights reserved.

C6

PhyHost3
or VMware

SAP Solution Manager

SAP Host
Agent

Diagnostics
Agent 5

SAP Host
Agent

.
.

DA

Diagnostics Agent

HA

SAP Host Agent

Managed Component
(see following slides)

PhyHost1 or VMware

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:

2013 SAP AG. All rights reserved.

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 latest Diagnostics Agent installation package. See SAP note 1833501.

2013 SAP AG. All rights reserved.

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

2013 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

ABAP Central Instance

+ ABAP Central Services

Java Central Instance

Java Central Services

DB

Diagnostics Agent

2013 SAP AG. All rights reserved.

Enterprise Portal

ERP / ECC Server

ABAP stack on 1 Host

Dual stack on 1 Host

Solution Manager

Java stack on 1 Host

Example where all components run with one hostname (physical, virtual or logical)

Central Instance

Dialog Instance

Central Services

DB

Diagnostics Agent

Central Instance
+ ABAP Central Services

Dialog Instance

DB

Diagnostics Agent

11

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

Number of Diagnostics Agents depends on managed component distribution

Solution Manager

Enterprise Portal

ERP / ECC Server

Distributed Dual stack

Distributed Java stack

Distributed ABAP stack

Example where each component runs with different hostnames (physical, virtual or logical)

ABAP Central Instance

+ ABAP Central Services

Java Central Instance

Diagnostics Agent
Java Central Services

DB
Diagnostics Agent

(1) Agent required in the scope

of Solution Manager 7.1
(1)

Central Instance
Diagnostics Agent
Dialog Instance
Diagnostics Agent

Java Central Services

Diagnostics Agent
Possible since Solution
Manager 7.1 SP08

DB

Diagnostics Agent
(1) Agent required in the
scope of Solution Manager 7.1

Central Instance
Diagnostics Agent
Dialog Instance
Diagnostics Agent

ABAP Central Services

Diagnostics Agent
Possible since Solution
Manager 7.1 SP08

DB

Diagnostics Agent
(1) Agent required in the scope
of Solution Manager 7.1

In the context of High Availability environments consider to use the Agents On-the-fly feature available since Solution Manager 7.1 SP05

2013 SAP AG. All rights reserved.

12

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

Use Prod IS EM to
retrieve perf. data of
QA Managed systems

2013 SAP AG. All rights reserved.

managed systems
Dev & QA
Comparison possible

Dev Enterprise Portal Introscope

Adapters

Diagnostics Agent
Dev Introscope
Enterprise Manager

Solution Manager

QA Enterprise Portal Introscope

Adapters

Diagnostics Agent
Collected config. of
managed systems
QA & Prod

Diagnostics Agent
Introscope
Adapter

Comparison possible
Prod Introscope
Enterprise Manager

Prod Enterprise Portal Introscope

Adapters

3-System landscape

(Otherwise the Introscope Adapters

of the QA Portal would report their
data to the Dev. IS EM, what is not
expected here.)

Prod SolMan

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.

Dev SolMan

Covering 3-system landscape: Enable full RCA of QA Portal Managed System on both SolMans,
by installing an additional Diagnostics Agent
Solution Manager
and extracting QA Portal perf. data
from Prod. IS Enterprise Manager
IMPORTANT
Collected config. of

Diagnostics Agent

13

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

Solution Manager
Collected config. of
managed systems
Dev & QA

Dev Enterprise Portal

Dev Introscope
Enterprise Manager
Diagnostics Agent
QA Enterprise Portal

(Otherwise two Diagnostics Agent

OS users would access the Prod. IS
EM files. In case one Agent OS user
updates via solman_setup some
files, the other Agent OS user would
else encounter access denied
errors, especially if the umask is not
set to 007.)

2013 SAP AG. All rights reserved.

Solution Manager

Prod SolMan

IMPORTANT
On the Prod. IS EM host,
install a second Diagnostics
Agent instance, re-using the
System ID (SID) of the
Diagnostics Agent installed
initially.

Collected config. of
managed systems
QA & Prod

Prod. Introscope
Enterprise Manager

Prod Enterprise Portal

3-System landscape

Dev SolMan

[7.1 only] 3-system landscape requires a 2nd Diagnostics Agent (Prod. IS EM)

Diagnostics Agent
Diagnostics Agent
14

What is needed and where? (Diagnostics Agent/Agents On-the-fly)

3-system landscape
(continued)

Prod SolMan

Managed systems
in a given E2E solution
(Per Dev, QA or Prod type)
must be connected to the
same Solution Manager
system

Dev System landscape

Dev Enterprise Portal Introscope

Dev ECC Server

Adapters

Diagnostics Agent

Diagnostics Introscope
Adapter
Agent

QA System landscape
QA Enterprise Portal Introscope

QA ECC Server

Adapters

Diagnostics Agent

Diagnostics Introscope
Adapter
Agent

Solution Manager
Prod Managed
Systems data
EP & ECC
E2E Trace Analysis
Prod Introscope
Enterprise Manager

2013 SAP AG. All rights reserved.

Prod System landscape

Prod Enterprise Portal Introscope

Prod ECC Server

Adapters

Diagnostics Agent

Diagnostics Introscope
Adapter
Agent

15

What is needed and where? (SAP Host Agent)

Rule #2:
Have up-to-date SAP Host Agents
See SAP note 1365123 text for the current minimum version
This note also confirms whether the SAP Host Agent version installed or updated during the installation
of the Diagnostics Agent covers has 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 -> <search for your host> -> Host Status
2013 SAP AG. All rights reserved.

16

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.

2013 SAP AG. All rights reserved.

17

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)

2013 SAP AG. All rights reserved.

18

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.

2013 SAP AG. All rights reserved.

19

Diagnostics Agent File Structure

Description

7.0 / 7.01 SR1

7.11 / 7.20 / 7.30 SP03 /

SWPM 1.0 SP03 and higher

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

Local SAPJVM

No SAPJVM

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

Agent software and

properties files

/usr/sap/<SMDSID>/J<XX>/SMDAgent

/usr/sap/<DASID>/SMDA<XX>/SMDAgent

Agent logs

/usr/sap/<SMDSID>/J<XX>/SMDAgent/log

/usr/sap/<DASID>/SMDA<XX>/SMDAgent/log

(1)

(1)

Contains executable kernel programs that are replicated (files moved for the SAPJVM) from SYS/exe at
the time the Diagnostics Agent instance is started, in case the files have been updated.

2013 SAP AG. All rights reserved.

20

Latest Diagnostics Agent Release

Rule #4:
Use the latest SWPM 1.0 (SP04 Patch 2 or higher),
when installing a Diagnostics Agent to comply with rule #3. See SAP note 1858920.
A summary of Diagnostics Agents releases and characteristics is available 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.

2013 SAP AG. All rights reserved.

21

Diagnostics Agent Release Constraints / PAM

Agent releases

7.0 / 7.01 SR1

7.20

7.30 SP03

SWPM 1.0 SP04 P2 & higher

Compatible with
Solution Manager

Solution Manager
lower than 7.0 EhP1
SP20 (1)

Solution Manager
since 7.0 EHP1 SP20
(included) (1)(2)

Solution Manager
since 7.0 EHP1 SP20
(included) (1)(2)

Solution Manager
since 7.0 EHP1 SP20 (included)
(1)(2)

Supported NW
Managed system
releases

6.40, 7.00 and

higher

6.40, 7.00 and

higher

6.40, 7.00 and

higher

See SAP note 1680045

1858920

Installation
SAP note

1357812

1368413

1833501

PAM documentation:
https://service.sap.com/sltoolset
/ Software Logistics Toolset 1.0
/ PAM
In PAM document, navigate to
Software Provisioning Manager
1.0 / SAP Solution Manager
Diagnostics Agent

Installer recommended
when new installation required
(See OS platform support on next slide)
(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.

2013 SAP AG. All rights reserved.

22

Diagnostics Agent Release Characteristics

Agent releases

7.11

7.20

7.30 SP03
Standalone (2)

Latest Agent
release (2)

Already silently installed with

products based on

Old SAPInst based

PI & CE 7.1 EhP1

Old SAPInst based

CE 7.20 & NW 7.0
EhP2 NW Java,
ABAP or dual stacks

Old SAPinst based

installers (3)

SWPM 1.0 SP04

Patch 2 and higher
based
NW installers (3)

Kernel Release (SAP products)

7.11

7.20 / patch 36

7.20 / patch 401

7.20 & 7.20 EXT

JVM

SAPJVM 5

SAPJVM 6

SAPJVM 6

SAPJVM 6

Default System ID
/ Instance Number

DAA
/ SMDA<97 to 00>

DAA
/ SMDA<97 to 00>

DAA
/ SMDA<97 to 00>

DAA
/ SMDA<98 to 00>

Support both direct connection

to SolMan & SLD registration @
installation

No

Yes

Yes

Yes

(support offline mode)

(support offline mode)

SSL & SAPRouter Support @

installation

No

Yes (1)

Yes

Yes

(via installer option)

(via installer option)

SAP Host Agent installation

Install manually

Auto-installed

Auto-installed/updated
(2)

Auto-installed/updated
(2)

Installation SAP Note

1234387

1368413

1829024

1858920

Agent start/stop/control

Standard

Standard

Standard

Standard

/ patch level with standalone installer

(1)
(2)
(3)

IAIK libraries need to be provided manually.

Also allows to configure the trusted connection @ SAP Host Agent level, automatically.
For more information refer to SAP Note 1833501.

2013 SAP AG. All rights reserved.

23

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://wiki.sdn.sap.com/wiki/display/SMSETUP/Diagnostics+Agent+Troubleshooting).

2013 SAP AG. All rights reserved.

24

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.

2013 SAP AG. All rights reserved.

25

Diagnostics Agent Mass Installation

Use the unattended mode to silently install Diagnostics Agents for large
consistent landscapes
For Diagnostics Agent releases specific details
see SAP note 1833501 / Mass Deployment Notes

2013 SAP AG. All rights reserved.

26

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 LMSERVICE 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.

2013 SAP AG. All rights reserved.

27

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 IMPORTANT actions (see next slides)
Uninstall the previous Diagnostics Agent using SAPInst
2013 SAP AG. All rights reserved.

28

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/<ManagedSID>/<InstanceID>).
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.
2013 SAP AG. All rights reserved.

29

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-0114/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
2013 SAP AG. All rights reserved.

30