711 Diag Agent Setup Guide

SAP Solution Manager 7.0

End-to-End Root Cause Analysis

Diagnostics Agent 7.11

Setup Guide

Document Version 3.12 – July 2009

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

Diagnostics Agent Setup Guide I

Contents

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

2 INSTALLATION PLANNING ............................................................................................... 2

2.1 Required Documentation ......................................................................................... 2 2.1.1 Information in the SAP Service Marketplace .................................................. 2 2.1.2 SAP Notes for SAPinst 7.11 (7.1 EhP1) ......................................................... 2

2.2 Components for Problem Messages ...................................................................... 2

3 INSTALLATION PROCESS ................................................................................................ 3

3.1 Installation of Diagnostics Agent ............................................................................ 3 3.1.1 Installation Strategy (SLD Registration or Direct Solution Manager Registration) ............................................................................................................... 4 3.1.2 Prerequisites before starting SAPinst ............................................................. 5 3.1.3 Download Installation DVDs from SAP Service Marketplace ......................... 7 3.1.4 Install a Diagnostics Agent Using SAPinst ..................................................... 9 3.1.5 Diagnostics Agent Parameters ..................................................................... 12 3.1.6 Deleting a Diagnostics Agent ........................................................................ 16

3.2 Additional Information ........................................................................................... 17 3.2.1 Users and Groups of the Diagnostics Agent ................................................. 17 3.2.2 Directories of the Diagnostics Agent ............................................................. 18 3.2.3 How to Avoid Automatic Logoff by SAPinst (windows) ................................. 19 3.2.4 Install SAP Host Agent .................................................................................. 19 3.2.5 Starting and Stopping the Diagnostics Agent ............................................... 20 3.2.6 Mass Deployment of the Diagnostics Agent ................................................. 21 3.2.7 Change the Managing System of the Diagnostics Agent ............................. 21 3.2.8 Change the Diagnostics Agent credentials ................................................... 22 3.2.9 Change the Diagnostics Agent connectivity type.......................................... 22 3.2.10 Troubleshooting with SAPinst ....................................................................... 23 3.2.11 Diagnostics Agent does not start .................................................................. 24

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

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. This guide is part of a global installation and configuration which is described in the document Root Cause Analysis Installation and Upgrade Guide.

Terminology

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

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



2 Installation Planning Make sure that the prerequisites mentioned in the Root Cause Analysis Installation and Upgrade Guide, are fulfilled before starting with Installation.

2.1 Required Documentation

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

Information in the SAP Service Marketplace

Components for problem messages

2.1.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 Guide

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

Solution Manager (Installation Guides)

You will find the current version of all Solution Manager installation guides at https://service.sap.com/instguides SAP Components SAP Solution Manager Release 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

FAQ list

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

2.1.2 SAP Notes for SAPinst 7.11 (7.1 EhP1)

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

SAP Note 1234387: this SAP Note contains information relevant for Diagnostics Agent installation and post-installation.

2.2 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

XX-PART-WILY: issues related to Wily Introscope

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



3 Installation Process The following sections provide detailed information about installation & setup of Solution Manager Diagnostics. There is also a section providing additional information about post-installation tasks.

Installation of Diagnostics Agent

Identify the Installation Strategy (SLD Registration or Direct Solution Manager Registration) [page 4]

Check the Prerequisites before starting SAPinst [page 5]

Download Installation DVDs from SAP Service Marketplace [page 7]

Install a Diagnostics Agent Using SAPinst [page 9]

Diagnostics Agent Parameters [page 12]

Deleting a Diagnostics Agent [page 16]

Additional Information

Users and Groups of the Diagnostics Agent [page 17]

Install SAP Host Agent [page 19]

Starting and Stopping the Diagnostics Agent [page 20]

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

Change the Managing System of the Diagnostics Agent [page 21]

Change the Diagnostics Agent credentials [page 22]

Change the Diagnostics Agent connectivity type [page 22]

Troubleshooting with SAPinst [page 23]

Diagnostics Agent does not start [page 24]

3.1 Installation of Diagnostics Agent

Introduction

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.11 DVD: SAP NetWeaver Process Integration 7.11, SAP Composition Environment 7.11. 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.



Process Flow

To install your Diagnostics Agent, you have to perform the following steps, which are detailed in the linked sections:

Point Description

3.1.1 You Identify the Installation Strategy (SLD Registration or Direct Solution Manager Registration) [page 4]

3.1.2 You Check the Prerequisites before starting SAPinst [page 5]

3.1.3 You Download Installation DVDs from SAP Service Marketplace [page 7]

3.1.4 You Install a Diagnostics Agent Using SAPinst [page 9]

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

3.1.1 Installation Strategy (SLD Registration or Direct Solution Manager Registration)

Before starting the installation make sure that you have identified which installation strategy you want to use. This means that you need to choose between the two following scenarios:

SLD Registration: In this scenario, the SMD Agent registers itself into the production SLD assigned to the managed system on which the SMD Agent will be installed. This scenario should be used if Solution Manager is not yet installed.

Direct Solution Manager Registration: In this scenario, the Diagnostics agent establishes a direct connection to the Solution Manager system.

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

Direct Solution Manager Registration

The Diagnostics Agent connects directly to the Managing system which must be up and running. There are two ways to connect the Diagnostics Agent to the managing box. By default the connection is done via the message server (recommended). That means that we rely on the Java EE engine to dispatch to one of the dispatcher nodes. Nevertheless the



connection can be done via the Java EE dispatcher node. But this implies that the node is running.

3.1.2 Prerequisites before starting SAPinst

This section provides information on all the preparation steps required prior to installing.

Process Flow

Point Description

1 Your machine meets the Hardware Requirements [page 5]

2 You Download the JCE Policy Zip File [page 5]

3 You Set DISPLAY (UNIX only) [page 6]

4 You Set limits on system resource (UNIX only) [page 6]

5 You Install SAP Host Agent [page 19]

Hardware Requirements

Hardware Requirement Requirement

Minimum disk space 300 MB for common libraries

200 MB by Diagnostics Agent

So for an installation with only one agent, 500 MB is required.

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

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 Remote installation with SAPinst see page 10.




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

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

3.1.3 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 standard SAP NetWeaver 7.1 EHP1 DVDs (SAP NetWeaver Composition Environment 7.1 EHP1 or SAP NetWeaver Process Integration 7.1 EHP1) [page 7]

Download the Standalone Diagnostics Agent 7.1 EHP1 DVD [page 9]

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

Download the standard SAP NetWeaver 7.1 EHP1 DVDs

Prerequisites

For your installation you need the Installation Master DVD plus the Kernel DVD, which are delivered with the two following SAP products: SAP NetWeaver Composition Environment 7.1 EHP1 and SAP NetWeaver Process Integration 7.1 EHP1.

You can choose one or the other of these SAP products since this has no impact on the Diagnostics Agent installation.

These products are 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 Download Installations and Upgrades Entry by

Application Group SAP Netweaver SAP NETWEAVER <SAP product>

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

<SAP product> is equal to SAP EHP1 FOR SAP NW PI 7.1 or to SAP EHP1 FOR SAP NW CE 7.1 depending on the SAP product you chose to download

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:

<SAP product> is equal to SAP EHP1 FOR SAP NW PI 7.1



Platform Media Name Number Nb of files

AIX NW 7.11 IM/Kernel AIX,z/OS,OS/400 51036472 7

HP-UX NW 7.11 Inst.Mst./Kernel HP-UX 51036471 8

LINUX NW 7.11 IM/Kernel/TREX LNXx86, PPC64 51036474 8

SOLARIS

NW 7.11 Inst.Mst./Kernel SOLARIS 51036473 6

Windows Server

NW 7.11 IM/Kernel/TREX WIN x64, IA64 51036476 8

OS/400 NW 7.11 IM/Kernel AIX,z/OS,OS/400

NW 7.11 IM/Kernel/TREX LNXx86, PPC64

NW 7.11 IM/Kernel/TREX WIN x64, IA64

51036472

51036474

51036476

7

8

8

<SAP product> is equal to SAP EHP1 FOR SAP NW CE 7.1

Platform Media Name Number Nb of files

AIX NW CE 7.1 EHP1 AIX Kernel, Install. (incl. MaxDB RDBMS)

51036017 1

HP-UX NW CE 7.1 EHP1 HP/IA64 Kernel, Inst. (incl. MaxDB RDBMS)

51036016 3

LINUX NW CE 7.1 EHP1 LNX, OS400 Krnl,Inst. (incl. MaxDB RDBMS)

51036019 6

SOLARIS

NW CE 7.1 EHP1 SOLARIS Kernel, Inst. (incl. MaxDB RDBMS)

51036018 3

Windows Server

NW CE 7.1 EHP1 Windows Kernel, Inst. (incl. MaxDB RDBMS)

51036020 3

OS/400 NW CE 7.1 EHP1 LNX, OS400 Krnl,Inst. (incl. MaxDB RDBMS) NW CE 7.1 EHP1 Windows Kernel, Inst. (incl. MaxDB RDBMS)

51036019

51036020

6

3

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 EHP1 FOR SAP NW PI 7.1 and you are on AIX, you

have to select either the 7 Medias with name NW 7.11 IM/Kernel

AIX,z/OS,OS/400 or with number: 51036472.

<SAP product> is equal to SAP EHP1 FOR SAP NW CE 7.1 and you are on Windows

Server, you have either to select the 3 Medias with name NW CE 7.1 EHP1

Windows Kernel, Inst. (incl. MaxDB RDBMS) or with number: 51036020.



Download the Standalone Diagnostics Agent 7.1 EHP1 DVD

Prerequisites

For your installation you need the Standalone Diagnostics Agent 7.1 EHP1 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 Download SAP Support Packages Entry by

Application Group SAP Technology Components SAP SOLUTION MANAGER

SAP SOLUTION MANAGER 7.0 EHP1 Entry by Component Agents for

Managed systems DIAGNOSTICS AGENT 7.11 <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 (SMD711_INST_<OS>.SAR) to the download directory

3. Extract the download object using SAPCAR

3.1.4 Install a Diagnostics Agent Using SAPinst

The following sections explain you how to install the agent:

Running SAPinst [page 9]

Remote installation with SAPinst [page 10]

Starting SAPinst GUI Separately [page 11]

Running SAPinst

This procedure tells you how to install a Diagnostics Agent with 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 10], where SAPinst GUI is running on a separate host from SAPinst and the GUI server.

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/NW711_0_IM_<OS>_<platform>

4. Run the command:

./sapinst

The SAPinst GUI starts and the Welcome screen appears.

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. Open the command line in the installation directory, or double-click the executable in the Windows Explorer, and run the command:

<DVD drive>:\<SMD Agent

DVD>\DATA_UNITS\NW711_0_IM_<OS>_<platform>\sapinst.exe

The Welcome screen appears, and the installation begins.

SYSTEM I (I5/OS)

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

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 5].

5. Enter the following commands:

cd <SMD Agent DVD>/DATA_UNITS/NW711_0_IM_<OS>_<platform>

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

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

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



5. Enter the following commands:

cd <DVD drive>:\DATA_UNITS\NW711_0_IM_<OS>_<platform>



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

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

Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately.

UNIX

1. Log on as user root.



3. Mount the DVD

4. Change to the directory:

cd <SMD Agent DVD>/DATA_UNITS/SAPINSTGUI_710_<OS>_<platform>

5. Run the command

./sapinstgui

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:

<DVD drive>:\DATA_UNITS\SAPINSTGUI_710_<OS>_<platform>

5. Start SAPinst GUI by double-clicking sapinstgui.exe

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.



3.1.5 Diagnostics Agent Parameters

Procedure

1. Make sure that you have read the chapter "Prerequisites before starting SAPinst " [page 5] and have identified your Installation Strategy (SLD Registration or Direct Solution Manager Registration) [page 4]

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

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.

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

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

Diagnostics Agent parameters: SID, Number, Host

Diagnostics Agent user on Unix (<dasid>adm)

Diagnostics Agent user on Windows (<dasid>adm and SAPService<DASID>)

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

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

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.

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

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.

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



Diagnostics Agent user on Unix (<dasid>adm)


Operating System User: <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.

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 17] for more details.

Diagnostics Agent user on Windows (<dasid>adm and SAPService<DASID>)


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.


Operating System User: SAPService<DASID>

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





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

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

You have identified your Installation Strategy (SLD Registration or 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.

No SLD Destination

If the Diagnostics Agent is going to be installed automatically with a primary/additional application server instance, you have to configure the connection for the Diagnostics Agent manually after the installation with SAPinst has finished.

If it is installed as a standalone engine, a direct connection to the Managing system (which must be up and running) will be asked. See Connectivity for the Diagnostics Agent to Solution Manager [page 15] 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.

Connectivity for the Diagnostics Agent to Solution Manager

This is possible only if you are installing the Diagnostics Agent as a standalone engine.

You have identified your Installation Strategy (SLD Registration or Direct Solution Manager Registration) [page 4] and selected No SLD Destination.


Connection Type

You can choose between the following options:

Lookup HTTP Connection via 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 Agent connects directly to the Managing system via the Java EE dispatcher node which must be up and running.

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 Java EE P4 Port of the SAP Java EE Engine running on the Diagnostics Server or the HTTP Message Server Port.

P4 Port is 5xx04 (where xx is the instance number of Java EE engine: /usr/sap/<DASID>/SMDA<Instance_Number>).

Java EE Message Server HTTP Port is 81xx (where xx is the SCS instance number: /usr/sap/<DASID>/SCS<xx>).

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.

3.1.6 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 [page9].

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

Uninstall Uninstall - SAP Systems or Single

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.

3.2 Additional Information

This section describes the following topics.

General information

Users and Groups of the Diagnostics Agent [page 17]

Directories of the Diagnostics Agent [page 18]

How to Avoid Automatic Logoff by SAPinst [page 19]

Install SAP Host Agent [page 19]

Starting and Stopping the Diagnostics Agent [page 20]

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

Post installation steps

Change the Managing System of the Diagnostics Agent [page 21]

Change the Diagnostics Agent credentials [page 22]

Change the Diagnostics Agent connectivity type [page 22]

Troubleshoot

Troubleshooting with SAPinst [page 23]

Diagnostics Agent does not start [page 24]

3.2.1 Users and Groups of the Diagnostics Agent

SAPinst creates the following accounts and groups for Diagnostics Agent administration:

UNIX

User Primary Group Additional Group Description

<dasid>adm sapsys sapinst Diagnostics Agent administrator

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

SAP_<DASID>_GlobalAdmin

SAP_LocalAdmin

Domain Users



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

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. The sapcpe

work - Contains log files



3.2.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 Settings 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.

3.2.4 Install SAP Host Agent

You need to install a standalone host agent if it was not previously installed on the host.

The host agent is automatically installed during the installation of all SAP NetWeaver instances and components.

For that purpose you have to use the dedicated entry in SAPinst or to apply SAP Note 1031096:

1. Start SAPinst [page 9] on the dedicated machine

2. On the Welcome screen, choose < Your SAP product > Additional Preparations Host

Agent Host Agent

3. If the Host Agent entry cannot be found, you have to skip the next two steps and apply SAP Note 1031096.

4. To start the installation, choose Next.

5. Follow the instructions in the SAPinst dialogs and enter the required Host Agent parameters.





This procedure is detailed in the Installation Guide SAP NetWeaver Process Integration 7.1 including Enhancement Package 1

3.2.5 Starting and Stopping the Diagnostics Agent

UNIX

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>

Example

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>

Example

stopsap SMDA97

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

system on this host.

WINDOWS

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

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



Procedure

Starting/Stopping Diagnostics Agent(s)

1. Start the SAP MC 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.

IBM SYSTEM I(I5/OS)

The Diagnostics Agent is installed like a standard SAP instance.

Procedure

Starting/Stopping Diagnostics Agent(s)

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

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

Please refer to SAP Note 1294713: Mass Deployment of SAP Diagnostics Agent 7.11 for more details. 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.

3.2.7 Change the Managing System of the Diagnostics Agent

If the Diagnostics Agent is already installed on your system you can change the Diagnostics Agent configuration by running the smdsetup script. You can execute this procedure if for

instance the Agent is installed with some wrong parameters or if it was deployed at the end of an SAP System installation and you selected not to register your Agent in any SLD.

Prerequisites

The Diagnostics Agent is already installed on your system with some wrong parameters.

Procedure

If you want to change the Managing System the Diagnostics Agent is connected to, you have to execute the following steps:

1. Stop the Diagnostics agent

2. Open a shell (command prompt on windows platforms) on /usr/sap/<DASID>/SMDA<Instance_Number>/script

3. The command to execute depends on the connection type

We recommend you to connect the agent directly to the Managing System.

In case of Direct connection to the Managing System:




smdsetup managingconf

hostname:"sapms://<J2ee_Message_server_hostname>"

port:"<http_port_message_server>" user:"SMD_ADMIN" pwd:"xxxxxx"

In case of SLD registration:

smdsetup sldconf hostname:"<SLD_HOSTNAME>" port:"<SLD_PORT>"

user:"<SLDDSUSER>" pwd:"<SLDDSUSER_PWD>"

4. Start the Diagnostics agent

3.2.8 Change the Diagnostics Agent credentials

This section provides information about how to change the credentials (login and/or password) of the J2EE user used to connect the Diagnostics Agent to the Managing System.

Prerequisites

All the Diagnostics Agents must be connected to the Managing System before updating the password of the J2EE user used by these Diagnostics Agents

Procedure

1. You can either change the password of the J2EE user used by the agents or create a new J2EE user in User Management.

2. Open the Agent Administration application

In the Agent Credentials panel, fill the previous login of the Diagnostics Agents and enter the new one (or enter the same login with a new password). Click on the Update all agents button.

3. All the agents are disconnected and reconnected with the new credentials.

3.2.9 Change the Diagnostics Agent connectivity type

This section describes how to change the way the Diagnostics Agent is connected to the Solution Manager system.

Connectivity types

There are different types of connection to connect the Diagnostics agent to the Managing System such as:

Direct connection to the Java EE Dispatcher node: the Diagnostics agent tries to establish a direct connection to the P4 port (5xx04) of the Java EE dispatcher node of the Managing system.

Direct SSL connection to the Java EE Dispatcher node: the Diagnostics agent tries to establish a direct connection to the P4S port (5xx06) of the Java EE dispatcher node of the Managing system. All the data transferred by this channel are encrypted.

P4 Connection via the Java EE Message server: the Diagnostics agent contacts the Java EE message server of the Managing system on the HTTP port (81xx) to retrieve the P4 port (5xx04) of one of the Dispatcher nodes running in the Java EE cluster (use a load balancing mechanism). This kind of connection supports High Availability Managing systems.

P4 SSL connection via the Java EE Message server: the Diagnostics agent contacts the Java EE message server of the Managing system on the HTTP port (81xx) to retrieve the P4S port(5xx06) of one of the Dispatcher nodes running in the Java EE cluster (use a load balancing mechanism). This kind of connection supports High Availability Managing systems.



HTTP support connection via the Java EE Message server: the Diagnostics agent contacts the Java EE message server of the Managing system on the HTTP port (81xx) to retrieve the P4HTTP port (5xx05) of one of the Dispatcher nodes running in the Java EE cluster (use a load balancing mechanism). This kind of connection supports High Availability Managing systems. The protocol used between the Diagnostics agent and the Managing System is HTTP.

We recommend you to connect the Diagnostics Agent to the Managing System via the Java EE Message server instead of the Direct connection to the Dispatcher node.

Prerequisites

The Diagnostics Agent is already installed.

Procedure

To change the connectivity type you have to proceed as follows:

1. On the Managing system, go to Diagnostics Administration -> Managed Systems -> Agent Administration

2. In the Agent Connectivity panel, select the new connection type for the Diagnostics agent selected and apply the change. The Diagnostics agent is then reconnected with the new connection channel.

SSL connection can only be configured from the Managing System and not during the SAPinst sequence. Obviously this implies that the Managing System supports SSL connections.

3.2.10 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation 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.

3.2.11 Diagnostics Agent does not start

Prerequisites

The Diagnostics Agent was installed automatically at the end of a primary/additional application server instance installation.

During the installation you chose not to register the Diagnostics Agent in the SLD Server.

The agent does not start since runtime.properties and secstore.properties files

are missing.

Procedure

We recommend that you connect directly the agent to the Managing System

1. Open a shell (command prompt on windows platforms) on /usr/sap/<DASID>/SMDA<Instance_Number>/script and log on as <dasid>adm

user .

2. Execute the command:

smdsetup managingconf

hostname:"sapms://<J2ee_Message_server_hostname>"

port:"<http_port_message_server>" user:"SMD_ADMIN" pwd:"xxxxxx"

3. Nevertheless if you choose to register the agent in an existing Central you have to execute the command:

smdsetup sldconf hostname:"<SLD_HOSTNAME>" port:"<SLD_PORT>"

user:"<SLDDSUSER>" pwd:"<SLDDSUSER_PWD>"

Documents

711 Diag Agent Setup Guide