730SP3 Diag Agent Setup Guide

8/10/2019 730SP3 Diag Agent Setup Guide

http://slidepdf.com/reader/full/730sp3-diag-agent-setup-guide 1/42

Installation Guide

SAP Solution Manager - End-to-End Root Cause AnalysisDocument Version: 1.0 – 11-Apr-13

CUSTOMER

Diagnostics Agent 7.3 SP3 - Setup Guide Valid for Standalone Diagnostics Agent installations based on SAPinst



2

Customer

© 2013 SAP AG. All rights reserved.

Diagnostics Agent 7.3 SP3 - Setup Guide

Typographic Conventions

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,

pushbuttons labels, menu names, menu paths, and menu options.

Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,

transaction codes, table names, and key concepts of a programming language when theyare surrounded by body text, for example, SELECT and INCLUDE.

Exampl e Output on the screen. This includes file and directory names and their paths, messages,

names of variables and parameters, source text, and names of installation, upgrade and

database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as they

appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters

with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F2 or ENTER .




Document History © 2013 SAP AG. All rights reserved. 3

Document History

Version Date Change

1.0 9-APRIL-2013 First release of this guide



4

Diagnostics Agent 7.3 SP3 - Setup Guide Customer



Table of Contents

Table of Contents

1

Introduction .................................................................................................................................................... 6

1.1

About this Document .............................................................................................................................................. 6

1.2 Before You Start ...................................................................................................................................................... 7

1.2.1 SAP Notes for the Installation ................................................................................................................ 7

1.2.2 Information Available on SAP Service Marketplace ............................................................................ 7

1.2.3 Naming Conventions .............................................................................................................................. 8

1.2.4

Components for Problem Messages .......................... ............................. .............................. ................ 8

2

Planning ......................................................................................................................................................... 10

2.1

Planning Checklist ................................................................................................................................................. 10

2.2 Diagnostics Agent Version to Install .................................................................................................................... 10

2.3 Hardware Requirements ....................................................................................................................................... 10

2.4 SAP Kernel Requirements ..................................................................................................................................... 11

2.5 Set DISPLAY (Unix only) ........................................................................................................................................ 11

2.6 Set Limits on System Resources (Unix only) ...................................................................................................... 12

3

Preparation ................................................................................................................................................... 13

3.1

Preparation Checklist ............................................................................................................................................ 13

3.2 Installation Strategy (SLD Registration, Direct Solution Manager Registration) ............................................ 13

3.2.1 System Landscape Directory (SLD) Registration .............................................................................. 14

3.2.2

Direct Solution Manager Connection .................................................................................................. 14 3.3 Prepare the Installation Media ............................................................................................................................. 14

3.3.1 Download the Standalone Diagnostics Agent 7.3 .............................................................................. 15

4

Installation .................................................................................................................................................... 16

4.1

Installation Checklist ............................................................................................................................................. 16

4.2 Running SAPinst .................................................................................................................................................... 16

4.2.1 Running SAPinst on Unix ...................................................................................................................... 16

4.2.2 Running SAPinst on Windows .............................................................................................................. 17

4.2.3 Running SAPinst on IBM i ..................................................................................................................... 17

4.3 Install the Diagnostics Agent Using SAPinst ....................................................................................................... 18

4.4

Diagnostics Agent Parameters ............................................................................................................................ 18

4.4.1

Diagnostics Agent parameters: SID, Number, Host, drive (Windows only) .................................... 19

4.4.2 Operating System Users on Unix (<dasid>adm , sapadm ) ...............................................................20

4.4.3 Operating System Users on Windows (<dasid>adm , SAPService<DASID> and

sapadm ) ................................................................................................................................................. 21

4.4.4 Connectivity for the Diagnostics Agent to System Landscape Directory (SLD) ............................ 21

4.4.5 Connectivity for the Diagnostics Agent to Solution Manager (Standalone installation

only)........................................................................................................................................................ 22

5

Additional Information ................................................................................................................................ 25

5.1 Performing a Remote Installation with SAPinst ................................................................................................. 25

5.2 Starting SAPinst GUI Separately ..........................................................................................................................26

5.3

How to Avoid Automatic Logoff by SAPinst (Windows) .................................................................................... 28




Table of Contents © 2013 SAP AG. All rights reserved. 5

5.4

Operating System Limits for the Diagnostics Agent ......................................................................................... 29

5.5 Users and Groups of the Diagnostics Agent ...................................................................................................... 30

5.6 Directories of the Diagnostics Agent ................................................................................................................... 31

5.7

Starting, Stopping and Managing the Diagnostics Agent ................................................................................. 32

5.7.1 Using Scripts ......................................................................................................................................... 32

5.7.2 Using the SAP Management Console ................................................................................................. 34

5.7.3

Using the SAP Microsoft Management Console (SAP MMC) on Windows..................................... 35

5.7.4

IBM i ....................................................................................................................................................... 35

5.8 Mass Deployment of the Diagnostics Agent ...................................................................................................... 35

5.9 Deleting a Diagnostics Agent ............................................................................................................................... 36

5.10 Post installation steps ...........................................................................................................................................37

5.11 Troubleshoot ..........................................................................................................................................................37

5.11.1

Troubleshooting with SAPinst ..............................................................................................................37

5.11.2

Troubleshoot the Diagnostics Agent .................................................................................................. 38

6

Appendix ....................................................................................................................................................... 39

6.1 Terms for Included Open Source Software ........................................................................................................ 39



6

Customer



Introduction

1 Introduction

1.1 About this Document

Use

This guide explains how to install Diagnostics Agents for:

•

SAP Enhancement Package 1 for SAP Solution Manager 7.0

•

SAP Solution Manager 7.1This guide is part of a global installation and configuration which is described in the document Root Cause

Analysis Installation and Upgrade Guide.

Solution Manager Diagnostics Agent

The Solution Manager Diagnostics Agent (Diagnostics Agent) is the remote component of the E2E Root Cause

Analysis. It allows to have a connection between SAP Solution Manager as the Managing System and the

Managed System(s) and then to collect information from the Managed Systems for reporting purposes.

You will need to install a Diagnostics Agent on each server (virtual hostname) to be managed. Please note that in

case the SAP or Third Party Systems to be managed have been setup using virtual hostnames, it is essential to

install one Diagnostics Agent instance per virtual hostname.

Note

The Diagnostics Agent is deployed at the end of every installation requiring the SAP Installation Master

for 7.3 . If the Diagnostics Agent is installed on your Managed System, the folder

/usr/sap/<DASID>/SMDA<00-98>/SMDAgent should exist. By default <DASID> is set to DAA .

Constraints

This guide is only valid for installations using Standalone Diagnostics Agent Installer 730 SP3 based on

SAPinst.




Introduction

Customer

© 2013 SAP AG. All rights reserved. 7

1.2

Before You Start

1.2.1 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the most

recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find at:

http://service.sap.com/notes

S P Note Number Title Description

1365123 Installation strategy of Root

Cause Analysis Agents

Information about the adequate software and

procedure to install Diagnostics Agents or Agents On-

the-fly on the Managed Systems

1833501 Diagnostics Agent - Installer

Versions

Information about the different released installer

versions. Includes some general, version independent

information, relevant for all installers.

1829024 Inst. 7.30 SP3 - Diagnostics

Agent installation

Installation and Post-installation steps for the

Diagnostics Agent 7.30 SP3

1486330 Mass Deployment of SAP

Diagnostics Agent 7.30

Information about procedure to massively deploy the

Diagnostics Agent on a customer system landscape

1031096 Installing Package

SAPHOSTAGENT

How to install the Host Agent from the package

SAPHOSTAGENT.SAR

1.2.2 Information Available on SAP Service Marketplace

The following section describes the documentation you require for the installation.

Documentation

Title Internet ddress Description

Root Cause Analysis

Installation and Upgrade with

SOLMAN SETUP Guide

https://service.sap.com/diagnostics

Installation and Configuration

Information about Root Cause Analysis

Installation and Upgrade with SOLMAN

SETUP Guide

Frequently Asked Questions https://service.sap.com/diagnostics


Frequently Asked Questions

FAQ list for Diagnostics Agent

installation and upgrade

Inst. SAP Solution Manager

7.0 incl. EHP1

https://service.sap.com/instguides

SAP Components SAP Solution

Manager Release 7.0 EHP 1

Installation Guide for SAP Solution

Manager 7.0 including SAP

Enhancement Package 1


https://service.sap.com/sap/support/notes/1365123



http://service.sap.com/sap/support/notes/1829024















http://service.sap.com/sap/support/notes/1829024






8

Customer



Introduction

Title Internet ddress Description

Wily Introscope https://service.sap.com/diagnostics


Wily Introscope installation guide

General Quick Links

Title Internet ddress

SAP Notes http://service.sap.com/notes

End-To-End Root Cause Analysis http://service.sap.com/diagnostics

Diagnostics Installation and Configuration http://service.sap.com/diagnostics

Product Availability Matrix http://service.sap.com/pam

SAP Help Portal http://help.sap.com

1.2.3 Naming Conventions

In this documentation, the following naming conventions apply:

Terminology

• Managing System is a term for the central entry point of system analysis & monitoring. SAP Solution Manager

is the Managing System.

• Managed System is a term for a satellite system (e.g. Enterprise Portal) managed by SAP Solution Manager.

Variables

Variables Description

<DASID> Diagnostics Agent system ID in uppercase letters

<dasid> Diagnostics Agent system ID in lowercase letters

<Instance_Number> Instance Number of a Diagnostics Agent

<OS> Operating System name

1.2.4 Components for Problem Messages

In case of problems, contact SAP Support by creating a message on the following components:



http://help.sap.com/

http://help.sap.com/





Introduction

Customer


Components

Components Description

SV-SMG-DIA Issues related to Solution Manager Diagnostics

SV-SMG-DIA-SRV-AGT Issues related to Diagnostics Agent

XX-PART-WILY Issues related to Wily Introscope



10

Customer



Planning

2 Planning

2.1 Planning Checklist

This section includes the planning steps for your installation. Detailed information about the steps is available in

the relevant chapter.

1. You identify the Diagnostics Agent Version to Install [page 10]

2. You Check the Hardware Requirements, Set DISPLAY (Unix only) and Set Limits on System Resources (Unix

only) [page 10]

3.

You can now continue with Preparation [page 13]

2.2

Diagnostics Agent Version to Install

Before starting the installation you need to identify the Diagnostics Agent version that complies with the version of

the Solution Manager system. You also need to check if your operating system release is supported.

Note

The Product Availability Matrix (PAM) is attached to SAP Note 1365123.

Make sure to also respect the “General Installation and Uninstallation Remarks” described in SAP Note 1833501.

2.3 Hardware Requirements

Hardware Requirements

Hardware Requirement Requirement

Minimum disk space • 500 MB for common libraries

• 500 MB by Diagnostics Agent

So for an installation with only one agent, 1 GB is required.

•

300 MB of free space in the installation directory

See Running [page 16] for more details about installation directory location.

Minimum RAM 256 MB

IBM i Sizing recommendations are made by the IBM Competency Center. We

recommend that auxiliary storage pool (ASP) usage in SAP production

systems is 70% or less.












Planning

Customer


2.4

SAP Kernel Requirements

On the ´Unpack Archives´ dialog, the below statement about SAP HANA is made. This statement does not apply

to Diagnostics Agent Standalone Installer 730 SP3, which is shipped with the 720 SAP Kernel.

The Diagnostics Agent Standalone Installer uses the Prerequisites Checker that is normally used in combination

with SAPinst for installing NetWeaver 7.30 and later. The Prerequisites Checker may generate warnings for the

Operating System version that you are installing on. As long as you comply with the Product Availability Matrix

(PAM) information that is attached to SAP Note 1365123, you can ignore these warnings.

The Prerequisites Checker may also generate warnings (as shown below for Linux) informing you about the

supported versions for 7.20ext kernels. These warnings can be ignored for installations based on the Diagnostics

Agent Standalone Installer 730 SP3.

For Diagnostics Agent SAP Kernel details see SAP Note 1707141.

2.5 Set DISPLAY (Unix only)

Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where <host_name> is the hoston which you want to display SAPinst GUI.

Display

Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0

export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0











12

Customer



Planning

2.6

Set Limits on System Resources (Unix only)

Caution

On AIX the limits are described in SAP Note 323816

For the other Unix platforms, check the following values for user root:

Syntax

In csh execute limit

In sh or ksh execute ulimit -a

Limits

csh Ksh Properties

cputime time(seconds) unl i mi t ed

filesize file(blocks) unl i mi t ed

datasize data(kbytes) 2097148 KB

stacksize stack(kbytes)8192 KB

coredumpsize coredump(blocks) unl i mi t ed

descriptors nofiles(descriptors) 8192

memorysize memory(KBytes) unl i mi t ed

If your parameter settings differ from the settings above, change these values accordingly.

Example

If you have to change the value for descriptors to 8192, proceed as follows:

In csh execute:

limit descriptors 8192

In sh or ksh execute:

ulimit -n 8192

Caution

An SAP instance does not run with the operating system limits that were set therefore you have to set the

limits for the <dasid>adm user at the end of the installation. For more details see Operating System

Limits for the Diagnostics Agent [page 29].








Preparation

Customer


3 Preparation

3.1 Preparation Checklist

This section includes the preparation steps that you have to perform before starting the installation.

Detailed information about the steps is available in the relevant section.

1. You define the Installation Strategy (SLD Registration, Direct Solution Manager Registration) [page 13]

2.

You Prepare the Installation Media [page 14]

3.

You Install the Diagnostics Agent Using SAPinst [page 18]

3.2 Installation Strategy (SLD Registration, Direct SolutionManager Registration)

Before starting the installation make sure that you have identified which installation strategy you want to use. As

of Release 7.20 the two following scenarios are compatible: this means that you can choose either both scenarios

or only one of them or neither of them (Agnostics scenario).

Caution

If possible we recommend that you choose a direct Solution Manager connection instead of SLD

registration.

• System Landscape Directory (SLD) Registration: In this scenario, the Diagnostics Agent registers itself into

the production SLD assigned to the Managed System on which the Diagnostics Agent will be installed. This

scenario should be used if Solution Manager is not yet installed. If you select No SLD Destination the

Diagnostics Agent is not registered into the SLD.

•

Direct Solution Manager Connection (only possible during standalone installation): In this scenario, theDiagnostics agent establishes a direct connection to the Solution Manager system. If you select Do not

configure connection the Diagnostics Agent is not connected to the Solution Manager system.

Caution

If you select neither SLD registration nor Solution Manager connection, you will have to configure the

Diagnostics Agent connectivity manually after the installation with SAPinst has finished. This scenario is

used in case of Agnostics case.

For more details, read the Diagnostics Agent Troubleshooting guide.

https://service.sap.com/~sapidb/002007974700000409092009E/DiagAgent_TroubleShooting.pdf






14

Customer



Preparation

3.2.1

System Landscape Directory (SLD) Registration

SLD Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of yourwhole system landscape. The usual case is to configure one SLD for your complete system landscape.

If you choose to register the Diagnostics Agent in existing SLD, it registers itself in the SLD Server and is assigned

afterwards to the SMD Server using the Agent Admin tools (Managing System). This allows to install all the

Diagnostics Agents even if the Solution Manager is either not installed or not running. Even if the credentials of the

J2EE user used to connect the Diagnostics Agent are not valid, the agent is still available in the SLD and therefore

can be assigned to the Managing System later.

Caution

The CIM Model of SLD Server must be 1.5.26 or higher. In case, you are not able to upgrade your CIM

model, the Diagnostics Agent will be installed on your system, but it won't be registered in the centralSLD. The registration will automatically be done when the CIM model of the Central SLD is updated.

3.2.2

Direct Solution Manager Connection

The Diagnostics Agent connects directly to the Managing System which must be up and running. There are four

ways to connect the Diagnostics Agent to the managing box:

•

P4 Connection via SCS message server (recommended): the Diagnostics Agent connects to the SCS messageserver and is redirected to one of the dispatcher nodes by the Java EE engine.

Recommendation

We recommend that you select this option

• Direct P4 Connection via Java EE Dispatcher Node: the Diagnostics Agent connects to the selected Java EE

dispatcher node. But this implies that the node is running.

• P4 SSL Connection via SCS message server: same as P4 Connection via SCS message server with SSL

support.

• Direct P4 SSL Connection via Java EE Dispatcher Node: same as Direct P4 Connection via Java EE Dispatcher

Node with SSL support.

3.3 Prepare the Installation Media

This section explains how to download the Installation media necessary for your installation.




Preparation

Customer


3.3.1

Download the Standalone Diagnostics Agent 7.3

For your installation you need the latest version of the Standalone Diagnostics Agent 7.3 which is delivered as aSAR archive on Service Marketplace.

This media is available as follows:

•

You normally obtain the physical installation media as part of the installation package.

•

You can also download the installation media from SAP Service Marketplace.

Standalone Diagnostics Agent 7.3

1.

Download the latest version of this archive from http://service.sap.com/swdc → Support Packages and

Patches → Browse our Download Catalog→ SAP Technology Components → SAP SOLUTION MANAGER →

SAP SOLUTION MANAGER 7.1 → Entry by Component → Agents for Managed Systems → DIAGNOSTICS

AGENT 7.3→ <choose operating system of managed>

2.

Download the SAR (DIAGAGT73SP03_<XX>.SAR ), pertaining to your operating system, to the download

directory

3.

Unpack the archive to a local directory using the following command:

SAPCAR –xvf <download directory>/<path>/DIAGAGT73SP03_<XX>.SAR -R <unpack

directory>

If required, you can download the latest version of SAPCAR from http://service.sap.com/swdc → Support

Packages and Patches → A – Z Index → S → SAPCAR.

http://service.sap.com/swdc





16

Customer



Installation

4 Installation

4.1 Installation Checklist

The following sections provide detailed information about installation & setup of Solution Manager Diagnostics.

Detailed information about the steps is available in the relevant section.

1. You run SAPinst [page 16]

2.

You Install the Diagnostics Agent Using SAPinst [page 18]

3.

Follow the instructions in SAPinst dialogs and enter the required Diagnostics Agent Parameters [page 18]

4.2 Running SAPinst

This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running on the same

host and on the local display.

If necessary, you can:

• perform a remote installation with SAPinst [page 25], where SAPinst GUI is running on a separate host from

SAPinst and the GUI server

• Start SAPinst GUI separately [page 26]

4.2.1 Running SAPinst on Unix

1.

Log on to your host as user root.

2.

Mount the installation media.

Note

Make the installation media locally available. For example, if you use Network File System (NFS), reading

from media mounted with NFS might fail.

3. Change to the directory:

cd <SMD Agent DVD>/DATA_UNITS/<product>_IM_<OS>_<platform>[_<DB>]

4. Run the command:

./sapinst

The SAPinst GUI starts and the Welcome screen is displayed.




Installation

Customer


Caution

SAPinst creates the installation directory sapinst_instdir directly below the temporary directory.

SAPinst finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environmentvariable. If no value is set for these variables, SAPinst uses /tmp as default installation directory.

If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR

to the required directory before you start SAPinst.

Caution

Make sure that the temporary directory has the permissions 1777

4.2.2

Running SAPinst on Windows

1. Log on to your host as a user who is member of a local Administrators group of the machine involved.

2. Make the installation media available on the installation host.

3.

Double-click the executable in the Windows Explorer or open a command prompt in the installation directory

and run the command:

<DVD drive>:\<SMD Agent

DVD>\DATA_UNITS\<product>_IM_<OS>_<platform>[_<DB>]\sapinst.exe

The Welcome screen is displayed, and the installation begins.

Caution

SAPinst creates the installation directory sapinst_instdir, where it keeps its log files, and which is

located directly in the %ProgramFiles% directory. If SAPinst is not able to create sapinst_instdir

there, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP.

4.2.3

Running SAPinst on IBM i

Do all the preparations and start the installer as described in the Installing SAP Systems based on SAP NetWeaver

7.3/7.3 EHP1 Using Software Provisioning Manager 1.0 SP00 installation guide.

http://service.sap.com/~sapidb/011000358700000828172012E








18

Customer



Installation

4.3

Install the Diagnostics Agent Using SAPinst

Process Flow

1.

Make sure that you have read the chapter "Preparation " [page 13] and have identified the Diagnostics Agent

Version to Install [page 10] and defined the Installation Strategy (SLD Registration, Direct Solution Manager

Registration) [page 13]

2. Start SAPinst

3.

On the Welcome screen, choose < Your SAP product > → Standalone Engines→ Solution Manager Diagnostics

Agent→ Solution Manager Diagnostics Agent Installation

4.

To start the installation, choose Next .

5.

Follow the instructions in the SAPinst dialogs and enter the required Diagnostics Agent Parameters.

6.

SAPinst prompts for input parameters during the Define Parameters phase of installation.

Note

For more information about the input parameters, place the cursor on the relevant field and press F1 in

SAPinst.

At the end of the Define Parameters phase you can still change any of these parameters thanks to the Re vi s e

button on Parameter Summary screen.

Note

If you change a parameter with the Re vi s e button on the Parameter Summary screen, SAPinst takes

you to the screen where you can change the parameter. Depending on the changes, SAPinst might guide

you through other screens with default parameters that it has so far processed.

4.4

Diagnostics Agent Parameters

The sections below list the agent parameters that you need to specify before installing your Diagnostics agent:

•

Diagnostics Agent parameters: SID, Number, Host

•

Operating System Users on Unix (<dasid>adm , sapadm)

• Operating System Users on Windows (<dasid>adm , SAPService<DASID> and sapadm)

• Connectivity for the Diagnostics Agent to System Landscape Directory (SLD)

• Connectivity for the Diagnostics Agent to Solution Manager (Standalone installation only)




Installation

Customer


4.4.1

Diagnostics Agent parameters: SID, Number, Host, drive(Windows only)

Parameters Description

System ID <DASID> of

SAP Solution Manager

Diagnostics Agent

SAPinst sets the system ID of SAP Solution Manager Diagnostics Agent, <DASID>,

to DAA by default.

If a Diagnostics Agent 7.30 is already installed on this machine, SAPinst sets

<DASID> to its SID.

If DAA is already used by another product that is not a Diagnostics Agent, SAPinst

assigns another default system ID: starting from DA1 to DA9. You can overwrite the

default system ID as required.

Make sure that the <DASID>:

•

Either does not yet exist on the local installation host, or does already exist but

exclusively contains some Diagnostics Agent installation in the exact same

version

•

Consists of exactly three alphanumeric characters

•

Contains only uppercase letters

•

Has a letter for the first character

•

Does not include any of the following, which are reserved IDs:

ADD ALL AND ANY ASC AUX COM CON DBA END EPS FOR GID IBM INT

KEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGA

SHG SID SQL SYS TMP UID USR VAR

Caution

An error message pops up if the SAP System Name is not a dedicated

agent one or if the System ID is already used.

Note

Agents installed on different virtual hosts (but same physical host) can use

the same <DASID>.

Instance Number of the

Diagnostics Agent

Technical identifier for internal processes for the Diagnostics Agent, consisting of a

two-digit number from 98 to 00.

The instance number is set automatically to the next free and valid instance

number that has not yet been assigned to the SAP system.

The instance number is used to specify the name of the Diagnostics Agent instance

directory that SAPinst automatically creates during the installation.

The directory of the Diagnostics Agent instance is called

SMDA<Instance_Number>.

Logical Host Name You are installing the Diagnostics Agent as a Standalone engine.



20

Customer



Installation


You can change the Logical Host name if you plan to manage systems running on a

logical host. This scenario lets the Diagnostics Agent take part in a switchover

environment.

Caution

The Logical Host name is the short host name and not the FQDN.

Installation drive

On Windows only

Base directory for the Diagnostics Agent.

You cannot select the installation drive if:

•

The saploc share already exists (a SAP System or a Diagnostics Agent has

already been installed on this machine) SAPinst sets the installation drivewhere the saploc share points to.

•

The saploc share does not exist but there is only one hard disk on this

machine

4.4.2 Operating System Users on Unix (<dasid>adm , sapadm )


<dasid>adm User <dasid>adm is dedicated to the Diagnostics Agent installation and has the

authorization to manage the agent.

If you did not create user <dasid>adm manually before the installation, SAPinst

creates it automatically on every application server instance host during the

installation. In this case, make sure that the user password you choose meets the

requirements of your operating system.

Make sure that the user ID and group ID of <dasid>adm are unique and the same

on each application server instance host.

sapadm The Host Agent user sapadm is used for central monitoring services.

This user is created only if the Host Agent is automatically installed during the

installation of the Diagnostics Agent. In this case, make sure that the user

password you choose meets the requirements of your operating system.





22

Customer



Installation


select this option.

Caution

You cannot specify the route during the Solution Manager system

connection if you chose to register the Diagnostics Agent into SLD.

•

No SLD Destination

Note

If the Diagnostics Agent is going to be installed automatically with aprimary/additional application server instance and if you choose No SLD

Destination, you have to configure the connection for the Diagnostics

Agent manually after the installation with SAPinst has finished.

You can select the check box Use HTTPS if you choose Register in existing central

SLD.

See Connectivity for the Diagnostics Agent to Solution Manager (Standalone

installation only) [page 22] for more details about Solution Manager Connection

parameters.

SLD HTTP Host The fully-qualified host name of the System Landscape Directory (SLD), e.g.abc.xyz.corp

Caution

Server Hostname is checked. It is highly recommended to input the fully-

qualified Hostname.

SLD HTTP Port (SLD

HTTPS Port if Use HTTPS

selected)

The HTTP port of the Java system where the SLD is installed. The following

convention applies: 5<Instance_Number>00.

SLD Data Supplier User

and password

Enter the existing SLD Data Supplier User and password of the central SLD e.g.

SLDDSUSER .

4.4.5 Connectivity for the Diagnostics Agent to SolutionManager (Standalone installation only)

Connection to Solution Manager is possible only if you are installing the Diagnostics Agent as a standalone engine.




Installation

Customer


You identified your Installation Strategy (SLD Registration, Direct Solution Manager Registration) [page 13].

Caution

As of Release 7.20 you can choose to connect the Diagnostics Agent directly to the Solution Manager

system even if you registered it into the SLD during the previous step.


Connection of the

Diagnostics Agent to SAP

Solution Manager

You can choose between the following options:

• Configure standard connection: the Diagnostics Agent is connected to the

Solution Manager system.

SAPinst only prompts you for the Connection Type listed below in this table if

you select this option.• Do not configure connection: the Diagnostics Agent is not connected to the

Solution Manager system.

You can select the check box Use SSL connectivity if you choose Configure

standard connection.

Connection Type You can choose between the following options:

• P4 Connection via SCS message server: select this option to connect the agent

to the Managing System via the Message Server. In that case we rely on the

Java EE engine to dispatch to one of the dispatchers

•

Direct P4 Connection via Java EE Dispatcher Node: In that case, the Agentconnects directly to the Managing System via the Java EE dispatcher node

which must be up and running.

If you select Use SSL connectivity you can choose between the following options:

• P4 SSL Connection via SCS message server: same with SSL support.

• Direct P4 SSL Connection via Java EE Dispatcher Node: same with SSL support.

Host The fully-qualified host name of the SMD Server, e.g. abc.xyz.corp

Caution

Server Hostname is checked. It is highly recommended to input the fully-

qualified Hostname.

Port Depending on the connection type you have to specify either the HTTP SCS

Message Server Port, or the HTTP SCS SSL Message Server Port, or the Dispatcher

P4 Port, or the Dispatcher P4 SSL Port of the Java Stack of your SAP Solution

Manager system.

Note



24

Customer



Installation


HTTP SCS Message Server Port is 81xx (where xx is the Central Services

(SCS) instance number of the Java Stack of your SAP Solution Managersystem).

HTTP SCS SSL Message Server Port is 43xxx or 44xxx (where xx is the

Central Services (SCS) instance number of the Java Stack of your SAP

Solution Manager system).

Dispatcher P4 Port is 5xx04 and Dispatcher P4 SSL Port is 5xx06 (where

xx is the central instance number of the Java Stack of your SAP Solution

Manager system).

User and password We recommend that you use the SMD_ADMIN user created during the SMD Setup

Wizard step in the Managing System.

Caution

Diagnostics Server Hostname is checked. It is highly recommended to

input the fully-qualified Hostname.

Then all the steps executed during Setup phase are tested. In case of an error a

message pops up. It is not recommended to begin the installation as long as the

check fails.

SAP Router The route string describes the stations of a connection required between the

Diagnostics Agent and Solution Manager.

The route string contains a substring for each SAP router without the target server

such as: /H/host/S/service/W/pass

• /H/ indicates the host name

•

/S/ is used for specifying the service (port); it is an optional entry, the default

value is 3299

•

/W/ indicates the password for the connection between the predecessor and

successor on the route and is also optional (default is "", no password)

Example

The route between the Diagnostics Agent and Solution Manager can be

such as: /H/hostname.sap.com/S/3199

Caution

You cannot specify the route if you chose to register the Diagnostics Agent

into SLD during the previous step.




Additional Information

Customer


5 Additional Information

This section provides additional information about the Diagnostics Agent, post-installation steps and

troubleshooting tasks.

•

Performing a Remote Installation with SAPinst [page 25]

•

Starting SAPinst GUI Separately [page 26]

• How to Avoid Automatic Logoff by SAPinst (Windows) [page 28]

• Operating System Limits for the Diagnostics Agent [page 29]

• Directories of the Diagnostics Agent [page 31]

•

Starting, Stopping and Managing the Diagnostics Agent [page 32]

•

Mass Deployment of the Diagnostics Agent (Unattended mode) [page 35]

•

Deleting a Diagnostics Agent [page 36]

•

Post installation steps [page 37]

•

Troubleshoot SAPinst and the Diagnostics Agent [page 37]

5.1 Performing a Remote Installation with SAPinst

You use this procedure to install your Diagnostics Agent on a remote host. In this case, SAPinst and the GUI

server run on the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you

control the installation with SAPinst GUI.

If your security policy requires that the person performing the installation by running SAPinst GUI on the local

host is not allowed to know root (Unix) or administrator (Windows) credentials on the remote host, you can

specify another operating system user for authentication purposes. You do this using the

SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You

have to confirm that the user is a trusted one. For more information, see SAP Note 1745524.

Unix

1.

Both computers are in the same network and can " ping" each other

2.

Log on as user root.

3. Mount the installation media

4. Change to the directory of the sapinst executable by entering the following command:


5.

Start SAPinst by executing the following command:

./sapinst -nogui







26

Customer




SAPinst now starts and waits for the connection to SAPinst GUI. You see the following at the command

prompt:

guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation.

6.

Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 26].

Windows

1.

Both computers are in the same network and can " ping" each other

2.

Log on to your host as a user who is member of a local Administrators group of the machine involved.

3.

Make the installation media available on the installation host.

4. Change to the directory of the sapinst executable by entering the following command:

cd <DVD drive>:\<SMD Agent DVD>\DATA_UNITS\<product>_IM_<OS>_<platform>[_<DB>]

5. Enter the following commands:

sapinst.exe -nogui

SAPinst now starts and waits for the connection to SAPinst GUI. You see the following at the command

prompt:

guiengine: no GUI connected; waiting for a connection on host <host_name>, port

<port_number> to continue with the installation

6.

Start SAPinst GUI on your local host as described in Starting SAPinst GUI Separately [page 26].

5.2

Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately.

You might need to start SAPinst GUI separately in the following cases:

•

You closed SAPinst GUI using F i l e → Exi t from SAPinst menu while SAPinst is still running.

• You want to perform a remote installation, where SAPinst GUI runs on a different host from SAPinst. For more

information, see Performing a Remote Installation with SAPinst [page 25].

Unix

1. Log on as user root.

2.

Make SAPinst software available on the host on which you want to start SAPinst GUI.

3.

Change to the directory of the sapinst executable by entering the following command:


4.

Start SAPinst GUI by executing./sapinstgui with the relevant command line parameters:

o

If you want to perform a remote installation, execute the following command:

./sapinstgui -host <remote_host> -port <port_number>





Customer


Note<remote_host> is the name of the remote host the name of the remote host <port_number> is the

port the GUI server uses to communicate with the GUI client (21212 by default).

o

If you closed SAPinst GUI using F i l e → Exi t from SAPinst menu and want to reconnect to SAPinst,

o

If you are performing a local installation with SAPinst and SAPinst GUI running on the same host:

./sapinstgui -standalone -port <port_number>

o If you are performing a remote installation with SAPinst and SAPinst GUI running on different hosts:

./sapinstgui -host <remote_host> -port <port_number>

Note

<remote_host> is the name of the remote host the name of the remote host <port_number> is the


SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as default. If SAPinst

and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI

Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log

on. The first dialog of the installation appears and you can perform the remote installation from your local host.

Windows

1.

Log on as a member of the local Administrators group.

2.

Make the installation media available on the installation host.

3.

Change to the directory of the sapinst executables:

cd <DVD drive>:\<SMD Agent DVD>\DATA_UNITS/<product>_IM_<OS>_<platform>[_<DB>]

4.

Start SAPinst GUI by executing sapinstgui.exe with the relevant command line parameters:

o If you want to perform a remote installation, execute the following command:

sapinstgui.exe -host <remote_host> -port <port_number>

Note



o

If you closed SAPinst GUI using F i l e → Exi t from SAPinst menu and want to reconnect to SAPinst,

o

If you are performing a local installation with SAPinst and SAPinst GUI running on the same host:

sapinstgui.exe -standalone -port <port_number>

o If you are performing a remote installation with SAPinst and SAPinst GUI running on different hosts:

sapinstgui.exe -host <remote_host> -port <port_number>



28

Customer




Note



SAPinst GUI starts and tries to connect to the GUI server and SAPinst, using the local host as default. If SAPinst

and the GUI server are running on another host, SAPinst GUI cannot connect and the SAP Installation GUI

Connection dialog appears. In this case, enter the name of the host on which SAPinst is running and choose Log

on. The first dialog of the installation appears and you can perform the remote installation from your local host.

5.3

How to Avoid Automatic Logoff by SAPinst (Windows)

When you install the SAP system with SAPinst, the SAPinst installation tool checks whether the user account used

for the installation has the required privileges and authorization.

The account needs to be a member of the local Administrators group and the user account must be authorized to

do the following:

•

Act as part of the operating system

•

Adjust memory quotas for a process

• Replace a process level token

If the user account does not have these rights assigned, SAPinst assigns them and automatically logs the account

off to activate them. To avoid SAPinst logging the account off, you can set these rights manually before you start

the installation.

Procedure

You perform the following steps to assign these rights to the user account used for the installation.

1.

Choose Start > Control Panel > Administrative Tools > Local Security Policy

2.

In the Local Security Settings window, choose Local Policies > User Rights Assignment.

3.

Double-click the required right under Policy and choose Add User or Group.

4.

In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.

5. Confirm your entry and then repeat the steps for each remaining policy that the user requires for the

installation.

6. Log off and log on again to apply the changes.





Customer


5.4

Operating System Limits for the Diagnostics Agent

Certain operating systems limit operating system resources (such as the maximum number of open files) toostrictly in the default settings; as a result, some SAP instance types (such as the Diagnostics Agent instances) do

not work correctly. Therefore, the operating system settings must be adjusted.

Depending on how the Diagnostics Agent is started, limits have to be set either for the specific <dasid>adm user

or in such a way that they also take effect for the sapstartsrv that was started either as a daemon at the time of

the operating system boot process or using a Web service client (sapcontrol, SAP MMC, SAP MC, and so on).

Procedure

If sapstartsrv was started as <dasid>adm in a shell running commands like

•

/usr/sap/sapservices

•

sapstartsrv pf=….

•

sapcontrol –nr <XX> -function StartService <DASID> (this command simply extract the relevant

command line from /usr/sap/services and executes it)

•

startsap (startsap tries to start sapstartsrv by itself if not yet running)

you need to set the limits in the shell before doing so.

To do this, the individual platforms provide various mechanisms to set these globally or for individual processes

or users.

Note

On AIX the mechanisms are described in SAP Note 323816

To set the limits for all sapstartsrv daemons that were started at OS boot via sapinit script, you can set the

limits in /usr/sap/sapservices.

limit.descriptors=<value>

limit.stacksize=<value>

NotePlease follow SAP Note 1437105.

To take into account the new limits, you have to restart sapstartsrv and therefore to stop the agent (stopsap)

and kill the process: kill <sapstartsrv_pid>.

Indeed restarting sapstartsrv using the following command is not enough since the above command just sends

a restart request to sapstartsrv.

sapcontrol -nr <XX> -function RestartService

sapstartsrv restarts itself so the new sapstartsrv inherits the limits of the actual running one.

At the end, restart the agent (startsap) and the service is restarted as well.



30

Customer




5.5

Users and Groups of the Diagnostics Agent

During the installation, SAPinst checks all required accounts (users, groups) on the local machine. SAPinst checkswhether the required users and groups already exist. If not, it creates new users and groups as necessary.

If you do not want SAPinst to create operating systems users and groups automatically, you can optionally create

them before the installation. This might be the case if you use central user management such as Network

Information System (NIS).

If you want to create the users and groups before the installation you choose one of the following ways:

•

You start SAPinst and choose Software Life-Cycle Tasks Additional Preparation Tasks Operating System

Users and Groups.

•

You create operating system users and groups manually. Make sure that you also check the settings for these

operating system users.

Caution

The administration user sapadm is created only if the Host Agent is automatically installed during the

installation of the Diagnostics Agent. It is used for central monitoring services. OnIX

, follow the

directions under section 4 Installation in SAP Note 1704753.

Caution

If SAPinst creates this user, make sure that the user password you choose meets the requirements of

your operating system. The password:

- Must be 8 to 9 characters long

- May contain the following characters: @, _, #, $, a-z, A-Z, 0-9

- Must contain at least one letter (a-z, A-Z)

- Must contain at least one digit (0-9), but must not begin with a digit

- Must not contain \ (backslash) and " (double quote)

Users and Groups on Unix

SAPinst chooses available operating system user IDs and group IDs. If you want to specify them or to change the

Home directory, you have to create the OS Users and groups before the installation.

User Primary Group dditional Group Description

<dasid>adm sapsys sapinst Diagnostics Agent administrator

sapadm sapsys sapinst Host Agent administrator









Customer


Users and Groups on Windows

User Local Installation Domain Installation

<dasid>adm SAP_<DASID>_LocalAdmin

SAP_LocalAdmin

Users

SAP_<DASID>_GlobalAdmin

SAP_LocalAdmin

Domain Users

SAPService<DASID> SAP_<DASID>_LocalAdmin

SAP_LocalAdmin

Users

Performance Monitor Users

SAP_<DASID>_GlobalAdmin

SAP_LocalAdmin

Domain Users

Performance Monitor Users

Sapadm SAP_SAP_LocalAdmin

SAP_LocalAdmin

Users

SAP_SAP_GlobalAdmin

SAP_LocalAdmin

Domain Users

5.6

Directories of the Diagnostics Agent

This section describes the SAP directories that SAPinst creates during the installation.

/usr/sap/<DASID> contains the following subdirectories:

•

SYS

o exe - Contains executable kernel programs

o global - Contains globally shared data

o profile - Contains the profiles of the Diagnostics Agent instance

•

SMDA<Instance_Number> - Instance directory of the Diagnostics Agent instance. It contains the instance-

specific data of the Diagnostics Agent. It contains the following subdirectories:

o

script - Contains the smdsetup script

o

SMDAgent - Contains the Diagnostics Agent software and properties files

o

exe - Contains executable kernel programs that are replicated from SYS/exe host every time theinstance is started.

The SAP copy program sapcpe compares the binaries in the <platform> directory and the binaries in

the SMDA<Instance_Number> /exe directory. If the binaries in the exe directory are elder than those in

the <platform> directory, sapcpe replaces them with the newer version.

o

work - Contains log files



32

Customer




5.7 Starting, Stopping and Managing the Diagnostics Agent

5.7.1 Using Scripts

The Diagnostics Agent is started at the end of the installation.

You can start and stop the Diagnostics Agent by running the startsap and stopsap scripts.

Caution

You can only start or stop the Diagnostics Agent separately. It is not started or stopped automatically with

the SAP system.

Prerequisites

You have logged on to the host as user <dasid>adm .





34

Customer




Example

C:\usr\sap\DAA\SMDA97\exe\sapcontrol.exe -prot PIPE -nr 97 -function

GetProcessList

5.7.2 Using the SAP Management Console


You can start and stop the Diagnostics Agent using the SAP Management Console (SAP MC).

Prerequisites

Make sure that the host on which you start SAP MC meets the following requirements:

•

Java Runtime Environment (JRE) 5.0 is installed.

•

The browser supports Java.

•

The browser's Java plug-in is installed and activated.

•

You have logged on to the host as user <dasid>adm .

Procedure

Starting/Stopping Diagnostics Agent(s)

1. Start a Web browser and enter the following URL:

http://<hostname>:5<Instance_Number>13

Example

ht t p: / / host : 59713

This starts the SAP MC Java applet.

Note

If your browser displays a security warning message, choose the option that indicates that you trust the

applet.

2.

Choose Start. The SAP Management Console appears.

3.

In the navigation pane, open the tree structure and navigate to the system node that you want to start/stop.

http://host:59713/

http://host:59713/





Customer


5.7.3

Using the SAP Microsoft Management Console (SAP MMC)on Windows


You can start and stop all your Diagnostics Agents using the SAP Management Console (SAP MMC) on Windows.

Procedure


1.

Start the SAP MMC on the SAP system host by choosing Start → All Programs → SAP Management Console.

2.

Right-click the Diagnostics Agent node and choose Start or Stop.

5.7.4 IBM i

The Diagnostics Agent is installed like a standard SAP instance.

Procedure


Use STARTSAP/STOPSAP to start and stop your Diagnostics Agents.

5.8 Mass Deployment of the Diagnostics Agent

If you want to massively deploy the Diagnostics Agent on a customer system landscape you can use the

Diagnostics Agent SAPinst in unattended mode. This means you record all input parameters for one installation

scenario, which you can then reuse for further installations.

Note



36

Customer




For more details, please refer to SAP Note 1486330: Mass Deployment of SAP Diagnostics Agent 7.3.

This SAP Note describes the additional steps you have to perform for an installation in unattended mode

beyond the "standard" installation procedure that is described in this installation guide.

5.9 Deleting a Diagnostics Agent

This procedure tells you how to uninstall a Diagnostics Agent using SAPinst.

Make sure to also respect the “General Installation and Uninstallation Remarks” described in SAP Note 1833501.

CautionYou must delete a Diagnostics Agent instance only using SAPinst; otherwise you might have problems

with further installations on this host.

Prerequisites

Unix

You are logged on as user root.

Windows

You are logged on with a user account that has the required authorization to run the SAPinst tool and the

Diagnostics Agent.

Caution

Do not use the user <dasid>adm to delete the Diagnostics Agent.

Procedure

1.

Start SAPinst [page18].

2.

On the Welcome screen, choose <Your SAP product> → Software Life-Cycle Options → Uninstall → Uninstall -

SAP Systems or Single Instances

3.

On the screen General SAP System Parameters, enter the location of the profile directory of the Diagnostics

Agent that you want to uninstall:

/usr/sap/<DASID>/SYS/profile

4.

Follow the instructions in the SAPinst input dialogs.













Customer


Note

For more details, use the F1 help in SAPinst screens.

5.10 Post installation steps

If you want to change some configuration parameters such as the connectivity type, the Diagnostics Agent

credentials, the Managing System the Diagnostics Agent is connected to and so on read the Diagnostics Agent

Troubleshooting guide.

5.11 Troubleshoot

5.11.1 Troubleshooting with SAPinst

If an error occurs, SAPinst:

• Stops the installation

•

Displays a dialog informing you about the error

Procedure

1.

To view the log file, choose Vi ew Logs .

2.

If an error occurs during the dialog or processing phase, do either of the following:

• Try to solve the problem

• Abort the installation with Ex i t

• Continue the installation by choosing Re t r y .

3.

Check the log files of SAPinst in the installation directory sapinst_instdir SAPinst normally creates this

installation directory directly below the temporary directory. SAPinst finds the temporary directory by

checking the value of the environment variables TEMP, TMP, or TMPDIR .

Note

If no value is set for these variables, SAPinst uses /tmp/sapinst_instdir as default installation

directory on Unix platforms and %ProgramFiles%\sapinst_instdir on Windows platforms. If you

want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the

required directory.









38

Customer




5.11.2

Troubleshoot the Diagnostics Agent

Check the Diagnostics Agent Troubleshooting guide for more details.








Appendix

Customer


6 Appendix

6.1 Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Please note that for

these third party products the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C)

2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED

WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND

FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR

ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,

BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR

PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER

IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft

Systems, Applications, Products in Data Processing Neurottstrasse 16 69190 Walldorf, Germany (hereinafter:

SAP) and you (hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++

library (STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual

property laws, and to all of the terms and conditions of this Agreement.

C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any

royalties or restrictions.

D) Customer shall maintain the following copyright and permissions notices on STLport sources and its

documentation unchanged:

Copyright 2001 SAP AG

E) The Customer may distribute original or modified STLport sources, provided that:

o The conditions indicated in the above permissions notice are met;

o The following copyright notices are retained when present, and conditions provided in accompanying

permission notices are met:

Coypright 1994 Hewlett-Packard

Company

Copyright 1996,97 Silicon Graphics

Computer Systems Inc.

Copyright 1997 Moscow Center for






Appendix

Customer


depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due

to the circumstances known to it at that point in time representing a typical transfer of the software.

C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a

defect or lost profit.

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances

exceed EUR 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by making

backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its

recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by

observing this obligation.

F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against

employees or agents of SAP.

4. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered

trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. Forinformation on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see

SAP Note 854621.



www.sap.com/contactsap


No part of this publication may be reproduced or transmitted in any

form or for any purpose without the express permission of SAP AG.

The information contained herein may be changed without prior

notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System ads, System i5, System

p, System p5, System x, System z, System z10, System z9, z10, z9,

iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,

S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise

Server, PowerVM, Power Architecture, POWER6+, POWER6,

POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2

Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are

trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and

other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

trademarks or registered trademarks of Adobe Systems

Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks o r registered trademarks

of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C®, World Wide Web Consortium, Massachusetts

Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,

ByDesign, SAP Business ByDesign, and other SAP p roducts and

services mentioned herein as well as their respective logos are

trademarks or registered trademarks of SAP AG in Germany and in

several other countries all over the world. All other product and

service names mentioned are the trademarks of their respective

companies. Data contained in this do cument serves informational

purposes only. National product specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated companies ("SAP

Documents

730SP3 Diag Agent Setup Guide