720 Diag Agent Setup Guide

SAP Solution Manager 7.0

End-to-End Root Cause Analysis

Diagnostics Agent 7.20 -

Setup Guide

Document Version 1.4 – July 2011

© Copyright 2006 SAP AG. All rights reserved.

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, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,

WebSphere, Netfinity, Tivoli, and Informix are trademarks

or registered trademarks of IBM Corporation 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 or 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products 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 document

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 Group") for informational purposes

only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the

express warranty statements accompanying such products

and services, if any. Nothing herein should be construed as

constituting an additional warranty.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

Documentation on SAP Service Marketplace

You can find this documentation at

service.sap.com/instguidesNW04

SAP AG

Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20

www.sap.com

T yp o g r a p h i c C o n ve n t i o n s

Type Style Represents

Example Text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example

text

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

text

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

<Example

text>

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE

TEXT

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

I c o ns

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents July 2011

Diagnostics Agent Setup Guide I

Contents

1 INTRODUCTION ................................................................................................................. 1

1.1 Planning checklist .................................................................................................... 1 1.2 New Features ............................................................................................................ 1 1.3 Required Documentation ......................................................................................... 2

1.3.1 Information in the SAP Service Marketplace .................................................. 2 1.3.2 SAP Notes....................................................................................................... 3

1.4 Components for Problem Messages ...................................................................... 3 1.5 Terminology and variables ...................................................................................... 3

2 PREPARATION ................................................................................................................... 4

2.1 Preparation Checklist ............................................................................................... 4 2.2 Diagnostics Agent version to install ...................................................................... 4 2.3 Installation Strategy (SLD Registration, Direct Solution Manager Registration) ....................................................................................................................... 4

2.3.1 System Landscape Directory (SLD) Registration ........................................... 5 2.3.2 Direct Solution Manager Registration ............................................................. 5

2.4 Download Installation DVDs from SAP Service Marketplace............................... 6 2.4.1 Download the Standalone Diagnostics Agent 7.20 DVD ................................ 6 2.4.2 Download the standard SAP NetWeaver 7.20 DVDs ..................................... 7

2.5 Hardware Requirements .......................................................................................... 8 2.6 Download the JCE Policy Zip File ........................................................................... 8 2.7 Set DISPLAY (UNIX only) ......................................................................................... 9 2.8 Set limits on system resource (UNIX only) ............................................................ 9

3 INSTALLATION ................................................................................................................. 11

3.1 Installation Checklist .............................................................................................. 11 3.2 Running SAPinst .................................................................................................... 11

3.2.1 Running SAPinst on Unix .............................................................................. 11 3.2.2 Running SAPinst on Windows ...................................................................... 12 3.2.3 Running SAPinst on System I (I5/OS) .......................................................... 12

3.3 Install the Diagnostics Agent Using SAPinst ...................................................... 12 3.4 Diagnostics Agent Parameters ............................................................................. 13

3.4.1 Diagnostics Agent parameters: SID, Number, Host, drive (Windows only) 13 3.4.2 Operating System Users on Unix (<dasid>adm, sapadm) ........................... 15 3.4.3 Operating System Users on Windows (<dasid>adm, SAPService<DASID> and sapadm) ......................................................................... 15 3.4.4 JCE Unlimited Strength Jurisdiction Policy Files Archive ............................. 16 3.4.5 Connectivity for the Diagnostics Agent to System Landscape Directory (SLD) 16 3.4.6 Connectivity for the Diagnostics Agent to Solution Manager (Standalone installation only) ................................................................................... 17

4 ADDITIONAL INFORMATION .......................................................................................... 20

4.1 Performing a Remote installation with SAPinst .................................................. 20 4.2 Starting SAPinst GUI Separately ........................................................................... 21 4.3 How to Avoid Automatic Logoff by SAPinst (windows) ..................................... 23 4.4 Operating system limits for the Diagnostics Agent ............................................ 24

Contents July 2011

Diagnostics Agent Setup Guide II

4.5 Users and Groups of the Diagnostics Agent ....................................................... 25 4.6 Directories of the Diagnostics Agent ................................................................... 26 4.7 Starting, Stopping and Managing the Diagnostics Agent .................................. 27

4.7.1 Using Scripts ................................................................................................. 27 4.7.2 Using the SAP Management Console .......................................................... 28 4.7.3 Using the SAP Microsoft Management Console (SAP MMC) on Windows ................................................................................................................... 29 4.7.4 IBM System I(I5/OS) ..................................................................................... 29

4.8 Mass Deployment of the Diagnostics Agent ....................................................... 30 4.9 Deleting a Diagnostics Agent ................................................................................ 30 4.10 Post installation steps............................................................................................ 30 4.11 Troubleshoot ........................................................................................................... 31

4.11.1 Troubleshooting with SAPinst ....................................................................... 31 4.11.2 Troubleshoot the Diagnostics Agent ............................................................. 31

SAP Solution Manager - End-to-End Root Cause Analysis July 2011

Diagnostics Agent Setup Guide 1

1 Introduction This guide explains how to install Diagnostics Agents for:

SAP Solution Manager 7.0 - End to End - Root Cause Analysis.

SAP Enhancement Package 1 for SAP Solution Manager 7.0 - End to End - Root Cause Analysis.

This 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 perform a connection between SAP Solution Manager as the managing system and the managed system(s) and then to gather information from the managed systems and reports them to the Solution Manager system.

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.

The Diagnostics Agent is deployed at the end of every installation requiring the SAP Installation Master 7.20 DVD. If the Diagnostics Agent is installed on your Managed System, the following folders should exist:

* /usr/sap/<DASID>/SMDA<00-97>/SMDAgent. By default <DASID> is

set to DAA.

1.1 Planning checklist

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

Description

You identify the Diagnostics Agent version to install [page 4]

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

You Download Installation DVDs from SAP Service Marketplace [page 6]

You Check the Hardware Requirements, Download the JCE Policy Zip File , Set DISPLAY (UNIX only) and Set limits on system resource (UNIX only) [page 8]

You Install the Diagnostics Agent Using SAPinst [page 12]

1.2 New Features

Here you can find the new features in this release.

Area Description

SAP Java Virtual Machine (SAP JVM)

The SAP JVM 6 is installed automatically by SAPinst when you install the Diagnostics Agent.



Diagnostics Agent OS Users on Windows

Performance Monitor Users group is added to the

SAPService<DASID> user membership.

SAP Host Agent The SAP Host Agent is installed automatically if required.

Connectivity for the Diagnostics Agent

Installation Scenarios combinations:

Supports installation with SLD registration or SOLMAN connection

Supports installation with SLD registration and SOLMAN connection

Supports installation with no SLD registration and no SOLMAN connection (offline support)

The connection to the Solution Manager system can be based on SSL.

You can specify the Route between the Diagnostics Agent and Solution Manager.

Documentation Checklists have been introduced for all phases of the installation process:

Planning checklist [page 1]

Preparation Checklist [page 4]

Installation Checklist [page 11]

The goal of these checklists is to provide a quick step reference of activities to be done for each phase of the installation.

1.3 Required Documentation

The following sections describe the documentation you require for the installation.

1.3.1 Information in the SAP Service Marketplace

Information on the following areas is available in the SAP Service Marketplace.

Root Cause Analysis Installation and Upgrade with SOLMAN SETUP Guide

The current version of this document is available https://service.sap.com/diagnostics Installation and Configuration

Solution Manager (Installation Guides)

The current release of the SAP Solution Manager is SAP Enhancement Package 1 for SAP Solution Manager 7.0.

You will find the Solution Manager Installation guides at https://service.sap.com/instguides SAP Components SAP Solution Manager.

Select:

Release 7.0 EPH1 for Solution Manager 7.01

Release 7.0 for Solution Manager 7.0.



Wily Introscope

You will find the current version of Wily Introscope installation guide at https://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0 EPH1.

FAQ list

You will find the FAQ list for Solution Manager Diagnostics at https://service.sap.com/diagnostics.

1.3.2 SAP Notes

Please review the following notes before planning the installation of the Diagnostics Agents in your systems.

SAP Note Title

1365123 Installation strategy of Root Cause Analysis Agents

1368413 Inst. 7.20 - Diagnostics Agent installation

1357812 Inst. NW 7.01 SR1/Business Suite 7 SR1 - Diagnostics Agent installation

1424472 Diagnostics Agent - How to reduce disk space on file system

1.4 Components for Problem Messages

In case of problems, contact SAP Support by creating a message in Service Marketplace, components:

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

1.5 Terminology and variables

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

Managed System (also called monitored system) is a term for a satellite system (e.g. Enterprise Portal) connected to SAP Solution Manager.

Variables Description

<DASID> Diagnostics Agent system ID in uppercase letters

<dasid> Diagnostics Agent system ID in lowercase letters

<Instance_Number> Number of a Diagnostics Agent

<OS> Operating system name within a path

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






2 Preparation

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

Point Description

2.2 You identify Diagnostics Agent version to install [page 4]

2.3 You define the Installation Strategy (SLD Registration, Direct Solution Manager Registration) [page 4]

2.4 Your Download Installation DVDs from SAP Service Marketplace [page 6]

2.5 Your machine meets the Hardware Requirements [page 8]

2.6 You Download the JCE Policy Zip File [page 8]

2.7 You Set DISPLAY (UNIX only) [page 9]

2.8 You Set limits on system resource (UNIX only) [page 9]

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.

Agent releases 7.0 SR3/ 7.01 SR1 7.20 7.30 SP02

Compatible with Solution Manager

Solution Manager lower than 7.0 EhP1 SP 20

Solution Manager since 7.0 EHP1 SP20 (included)

Solution Manager since 7.0 EHP1 SP20 (included)

Support Managed system

6.40, 7.00 and higher 6.40, 7.00 and higher 6.40, 7.00 and higher

Supported OS SAP NetWeaver 7.0 Product Availability Matrix (PAM)

SAP NetWeaver CE 7.2 Product Availability Matrix (PAM)

SAP NetWeaver 7.3 Product Availability Matrix (PAM)

For more details see SAP Note 1365123.

2.3 Installation Strategy (SLD Registration, Direct Solution Manager 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

https://websmp107.sap-ag.de/~sapidb/011000358700001225132009E

https://service.sap.com/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200615320900004494








that you can choose either both scenarios or only one of them or neither of them (Agnostics scenario).

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 register into the SLD.

Direct Solution Manager Registration (only possible during Standalone installation): In this scenario, the Diagnostics agent establishes a direct connection to the Solution Manager system. If you select None the Diagnostics Agent is not connected to the Solution Manager system.

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.

2.3.1 System Landscape Directory (SLD) Registration

SLD Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of your whole 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 running. Moreover 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 later to the Managing system.

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 central SLD. The registration will automatically be done when the CIM model of the Central SLD is updated.

2.3.2 Direct Solution Manager Registration

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 message server and is redirected to one of the dispatcher nodes by the Java EE engine.

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



We recommend that you select this option

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

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.

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

Choose None if you do not want to connect the Diagnostics Agent to the Solution Manager System.

2.4 Download Installation DVDs from SAP Service Marketplace

This section explains how to download the Installation DVDs necessary for your installation. You can choose between the two options:

Download the Standalone Diagnostics Agent 7.20 DVD [page 6]

Download the standard SAP NetWeaver 7.20 DVDs (SAP NetWeaver Composition Environment 7.2) [page 7]

If you have not already downloaded the standard DVDs, we recommend that you choose the first option.

2.4.1 Download the Standalone Diagnostics Agent 7.20 DVD

Prerequisites

For your installation you need the Standalone Diagnostics Agent 7.20 DVD, which is delivered as a SAR archive on Service Marketplace

This DVD is available as follows:

You can download Diagnostics Agent installation DVDs from SAP Service Marketplace at:

http://service.sap.com/swdc SAP Software Download Center Support Packages and

Patches Browse our Download Catalog SAP Technology Components SAP

SOLUTION MANAGER SAP SOLUTION MANAGER 7.0 EHP1 Entry by Component

Agents for Managed systems DIAGNOSTICS AGENT 7.2 <choose operating system of managed>

Procedure

1. Create a download directory on the host where you want to run SAPinst.

2. Download the OS SAR (DIAGAGT72SP00_<XX>.SAR) to the download directory

3. Extract the download object using SAPCAR



2.4.2 Download the standard SAP NetWeaver 7.20 DVDs

Prerequisites

For your installation you need the Installation Master DVD plus the Kernel DVD, which are delivered with the following SAP product: SAP NetWeaver Composition Environment (CE) 7.2.

This product is available as follows:

You normally obtain the installation DVDs as part of the installation package.

You can also download installation DVDs from SAP Service Marketplace at:

http://service.sap.com/swdc SAP Software Download Center Installations and

Upgrades Browse our Download Catalog SAP Netweaver and complementary

products SAP NETWEAVER CE SAP NETWEAVER CE 7.2 Installation

<choose operating system of managed> <choose database type (whatever you want since the Diagnostics Agent is not database dependent)>.

If you download installation DVDs, note that the DVDs are split into several files. You have to reassemble the required files after the download.

Procedure

1. Create a download directory on the host where you want to run SAPinst.

2. Identify all download objects that belong to one installation DVD:

Platform Media Name Number Nb of files

AIX, z/OS, OS/400 NW CE 7.2 AIX, z/OS, OS/400 51040417 3

HP-UX IA64 NW CE 7.2 HPUX IA64 Inst.master, Kernel

51038234 3

LINUX X86_64, PPC64

NW CE 7.2 LINUX x86_64, PPC64 Inst.master, Kernel

51038236 4

LINUX IA64 NW CE 7.2 LINUX IA64, zSeries Inst.master, Kernel

51038032 3

WIN IA64, x64 NW CE 7.2 Windows IA64, x64 Inst.master, Kernel

51038237 4

SOLARIS NW CE 7.2 SOLARIS Sparc 64, x64 Inst.master, kernel

51038030 3

For CE, the following download object is required as well whatever the platform is:

Platform Media Name Number Nb of files

Any NW CE 7.2 Application, Dev. WP 32bit

51038266 7

3. Download the objects to the download directory (see examples hereunder).

4. Extract the individual download objects using SAPCAR, starting with the lowest sequence

number (for instance: 51031387_1, then 51031387_2, and so on).



Before starting the installation you need to make these DVDs available on the installation host; you can copy them locally or mount them locally.

Examples

<SAP product> is equal to SAP NETWEAVER CE 7.2 and you are on AIX, you have

to select the 3 Medias with name NW CE 7.2 AIX, z/OS, OS/400 (number:

51040417) plus the 7 Medias with the name NW CE 7.2 Application, Dev. WP

32b, Doc (number: 51038066).

2.5 Hardware Requirements

Hardware Requirement Requirement

Minimum disk space 1 GB for common libraries

500 MB by Diagnostics Agent

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

300 MB of free space in the installation directory

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

Minimum RAM 256 MB

IBM System i (i5/OS): We recommend that ASP (auxiliary storage pool) usage in SAP production systems should not exceed 70%.

2.6 Download the JCE Policy Zip File

The SAP Java Virtual Machine (SAP JVM) is not delivered with Java Cryptography Extension (JCE) jurisdiction policy files. The delivery of these is subject to import restrictions in some countries. The JCE jurisdiction policy files must be available beforehand so that SAPinst can install them.

Download the JCE jurisdiction policy files as described in SAP Note 1240081.

UNIX

Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>

export JCE_POLICY_ZIP

C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>

Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>

WINDOWS

set JCE_POLICY_ZIP=<policy zip archive>

For more details about Performing a Remote installation with SAPinst see page 20.




2.7 Set DISPLAY (UNIX only)

Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where

<host_name> is the host on which you want to display the SAPinst GUI.

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

2.8 Set limits on system resource (UNIX only)

On AIX the limits are described in SAP Note 323816

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

In csh execute limit

Output Properties

cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited

In sh or ksh execute ulimit -a

Output Properties

time(seconds) unlimited

file(blocks) unlimited

data(kbytes) 2097148

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(KBytes) unlimited

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

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: Operating system limits for the Diagnostics Agent [page 24].



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

3.1 Installation Checklist

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

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

Point Description

3.2 You run SAPinst [page 11]

3.3 You Install the Diagnostics Agent Using SAPinst [page 12]

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

3.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 20], where SAPinst GUI is running on a separate host from SAPinst and the GUI server

Start SAPinst GUI separately [page 21]

3.2.1 Running SAPinst on Unix

1. Log on to your host as user root.

2. Mount the DVDs.

Mount the DVDs locally. We do not recommend using Network File System (NFS).

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

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 environment variable. 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

3.2.2 Running SAPinst on Windows

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

2. Map a network drive pointing to the DVD location

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

If you want to setup a connection to the Solution Manager system based on

SSL, execute sapinst.exe in a command prompt and specify

NEED_SSL=true (sapinst.exe -NEED_SSL=true)

The Welcome screen appears, and the installation begins.

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.

3.2.3 Running SAPinst on System I (I5/OS)

Do all the preparations and start SAPinst as described in the SAP NetWeaver 2007 SR3 installation guide.

3.3 Install the Diagnostics Agent Using SAPinst

Process Flow

1. Make sure that you have read the chapter "Preparation " [page 4] and have identified the Diagnostics Agent version to install [page 4] and defined the Installation Strategy (SLD Registration, Direct Solution Manager Registration) [page 4]

2. Start SAPinst [page 12] on the dedicated machine

If you want to setup a connection to the Solution Manager system based on

SSL, specify NEED_SSL=true in the command to 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.



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 Revise button on Parameter Summary screen.

If you change a parameter with the Revise button on the Parameter Summary screen, the installer takes you to the screen where you can change the parameter. Depending on the changes, the installer might guide you through other screens with default parameters that it has so far processed.

3.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)

JCE Unlimited Strength Jurisdiction Policy Files Archive

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

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

3.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.20 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

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

An error message pops up if the SAP System Name is not a dedicated agent one or if the System ID is already used.

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

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

You can change the Virtual Host name if you plan to manage systems running on a virtual host. This scenario lets the Diagnostics Agent take part in a switchover environment.

SAPinst checks the rightness of the input.

The Virtual 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 drive where the

saploc share points to.

The saploc share does not exist but there is only one

hard disk on this machine



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

See Users and Groups of the Diagnostics Agent [page 25] for more details.

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.


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


Operating System User: <dasid>adm

The diagnostic agent user <dasid>adm is used to manage

the Diagnostics Agent system. It is created on the primary application server instance host and on every additional application server instance host.

For security reasons, SAPinst creates this user by default as a local user without being a member of the local

Administrators group. If required, you can change this

user to become a domain user on the parameter summary screen.

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


Operating System User: SAPService<DASID>

This user is the Windows account to run the Diagnostic Agent system.

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


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.


Windows Domain Windows Domain for the Diagnostics Agent Operating System

Users <dasid>adm and SAPService<DASID>.

SAP strongly recommends to create the Diagnostics Agent users as local users.

3.4.4 JCE Unlimited Strength Jurisdiction Policy Files Archive


JCE Unlimited Strength Jurisdiction Policy Files Archive

You need to obtain the Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for the JDK you are using beforehand so that SAPinst can install them.

For more information, see Download the JCE Policy Zip File [page 8]

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

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


SLD Destination

You can choose between the following options:

Register in existing central SLD

SAPinst only prompts you for the parameters listed below in this table if you select this option.

We recommend that you select this option.

You cannot specify the route during the Solution Manager system connection if you chose to register the Diagnostics Agent into SLD.

No SLD Destination

If the Diagnostics Agent is going to be installed automatically with a primary/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.

See Connectivity for the Diagnostics Agent to Solution Manager (Standalone installation only) [page 17] for more details about Solution Manager Connection parameters.

SLD HTTP Host The fully-qualified host name of the System Landscape

Directory (SLD), e.g. p135809.wdf.sap.corp

Server Hostname is checked. It is highly recommended to input the full qualified Hostname.

SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following naming 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.

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

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

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

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

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

Direct P4 Connection via Java EE Dispatcher Node: In that case, the Agent connects directly to the Managing system via the Java EE dispatcher node which must be up and running.

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

None: the Diagnostics Agent is not connected to the Solution Manager system.

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



p135809.wdf.sap.corp

Server Hostname is checked. It is highly recommended to input the full qualified Hostname.

Port Depending on the connection type you have to specify either the HTTP SCS Message Port, or the Dispatcher P4 Port, or the Dispatcher P4 SSL Port of the Java stack in your SAP Solution Manager system.

HTTP SCS Message Server HTTP Port is 81xx (where xx is the Central Services (SCS) instance number of the Java Stack in 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 in 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.

Diagnostics Server Hostname is checked. It is highly recommended to input the full qualified Hostname.

Then all the steps executed during Setup phase are tested. If something wrong occurs an error message pops up. It is recommended not to begin agent installation as long as setup check failed.

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)

The route between the Diagnostics Agent and Solution Manager can be such as: /H/hostname.sap.com/S/3199

You cannot specify the route if you chose to register the



Diagnostics Agent into SLD during the previous step.



4 Additional Information This section provides additional information about the Diagnostics Agent, post-installation steps and troubleshooting tasks.

Performing a Remote installation with SAPinst [page 20]

Starting SAPinst GUI Separately [page 21]

How to Avoid Automatic Logoff by SAPinst (windows) [page 23]

Operating system limits for the Diagnostics Agent [page 24]

Users and Groups of the Diagnostics Agent [page 25]

Directories of the Diagnostics Agent [page 26]

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

Mass Deployment of the Diagnostics Agent (SAPinst in unattended mode) [page 30]

Deleting a Diagnostics Agent [page 30]

Post installation steps [page 30]

Troubleshoot SAPinst and the Diagnostics Agent [page 31]

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

UNIX

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

2. Log on as user root.

3. Mount the DVD

4. SAP no longer delivers any JCE policy archives within the SAP JVM. You have to download the required JCE policy zip file from SAP on the remote host.

Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive. See Download the JCE Policy Zip File [page 8].

5. Execute the following command:

chmod +x <jce_policy_zip_file>

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


7. Start SAPinst by executing the following command:

./sapinst -nogui

SAPinst now starts and waits for the connection to the 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.



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

WINDOWS

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

2. Log on to your remote host as a user who is a member of the local Administrators

group.

3. Map a network drive pointing to the DVD location on your remote host




cd <DVD drive>:\<SMD Agent

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

6. Enter the following commands:

sapinst.exe -nogui

SAPinst now starts and waits for the connection to the 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

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

4.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 File Exit from the SAPinst menu while SAPinst is still running.

You want to perform a remote installation, where the SAPinst GUI runs on a different host from SAPinst. For more information, see Performing a Remote installation with SAPinst [page 20].

UNIX

1. Log on as user root.



3. Mount the DVD

4. Execute the following command:

chmod +x <jce_policy_zip_file>





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

parameters:

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

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

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

If you closed SAPinst Gui using File Exit from the SAPinst menu and want to reconnect to SAPinst,

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

./sapinstgui -standalone -port <port_number>

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

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




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.



3. Map a network drive pointing to the DVD location on your remote host

4. Change to the directory of the sapinst executables:

cd <DVD drive>:\<SMD Agent

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

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

parameters:

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

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






If you closed SAPinst Gui using File Exit from the SAPinst menu and want to reconnect to SAPinst,

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

sapinstgui.exe -standalone -port <port_number>

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

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




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.

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

4.4 Operating system limits for the Diagnostics Agent

Certain operating systems limit operating system resources (such as the maximum number of open files) too strictly 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 has 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 daemon at the time of the OS boot 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.

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>

Please 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

sapcontrol -nr <XX> -function RestartService

is not enough since the above command just sends a restart request to sapstartsrv.

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.

4.5 Users and Groups of the Diagnostics Agent

During the installation, SAPinst checks all required accounts (users, groups) on the local machine. SAPinst checks whether 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.

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.

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 Additional Group Description

<dasid>adm sapsys sapinst Diagnostics Agent administrator

sapadm sapsys sapinst Host Agent administrator

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_<DASID>_GlobalAdmin



SAP_LocalAdmin

Users

Performance Monitor

Users

SAP_LocalAdmin

Domain Users

Performance Monitor

Users

sapadm SAP_SAP_LocalAdmin

SAP_LocalAdmin

Users

SAP_SAP_ GlobalAdmin

SAP_LocalAdmin

Domain Users

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

exe - Contains executable kernel programs

global - Contains globally shared data

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:

script - Contains the smdsetup script

SMDAgent - Contains the Diagnostics Agent software and properties files

exe - Contains executable kernel programs that are replicated from SYS/exe

host every time the instance 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.

work - Contains log files



4.7 Starting, Stopping and Managing the Diagnostics Agent

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

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.

Procedure

Starting a Diagnostics Agent

To start the Diagnostics Agent, enter this command:

startsap SMDA<Instance_Number> [-vhost <virtual hostname>]



startsap SMDA97

You do not have to specify the <DASID> if there is only one Diagnostics Agent

system on this host.

Stopping a Diagnostics Agent

To stop the Diagnostics Agent, enter this command:

stopsap SMDA<Instance_Number> [-vhost <virtual hostname>]

stopsap SMDA97

You do not have to specify the <DASID> if there is only one Diagnostics Agent

system on this host.

Managing a Diagnostics Agent on Unix

To manage the Diagnostics Agent, enter this command:

/usr/sap/<DASID>/SMDA<Instance_Number>/exe/sapcontrol -prot NI_HTTP -

nr <Instance_Number> [-host <hostname>] -function GetProcessList

/usr/sap/DAA/SMDA97/exe/sapcontrol -prot NI_HTTP -nr 97 -

function GetProcessList

Managing a Diagnostics Agent on Windows

To manage the Diagnostics Agent, enter this command:

<drive>:\usr\sap\<DASID>\SMDA<Instance_Number>\exe\sapcontrol -prot

PIPE -nr <Instance_Number> [-host <hostname>] -function

GetProcessList

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

-function GetProcessList

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

http://host:59713

This starts the SAP MC Java applet.

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.

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

4.7.4 IBM System I(I5/OS)

The Diagnostics Agent is installed like a standard SAP instance.

Procedure


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



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

For more details, please refer to SAP Note 1376933: Mass Deployment of SAP Diagnostics Agent 7.20. 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.

4.9 Deleting a Diagnostics Agent

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

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

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

Procedure

1. Start SAPinst [page12].

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.

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

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





4.11 Troubleshoot

4.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 View 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 Exit

Continue the installation by choosing Retry.

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.

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.

4.11.2 Troubleshoot the Diagnostics Agent

Check the Diagnostics Agent Troubleshooting guide for more details.


Documents

720 Diag Agent Setup Guide