Diagnostics Agent 7.3 - Setup Guide

SAP Solution Manager

End-to-End Root Cause Analysis

Diagnostics Agent 7.3 -

Setup Guide

Valid for installations using Software Provisioning

Manager 1.0

Document Version 1.0 – October 2012

© 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

Error! No text of specified style in document. October 2012

Diagnostics Agent Setup Guide I

C o n t e nt s

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

1.1 Planning checklist .................................................................................................... 1 1.2 New Features ............................................................................................................ 2 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 ................................................................................................................... 5

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

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

2.4 Download Installation DVDs from SAP Service Marketplace............................... 8 2.4.1 Download the Standalone Diagnostics Agent 7.3 DVD .................................. 8 2.4.2 Download the standard SAP NetWeaver DVDs ............................................. 9

2.5 Hardware Requirements .......................................................................................... 9 2.6 Set DISPLAY (UNIX only) ......................................................................................... 9 2.7 Set limits on system resource (UNIX only) .......................................................... 10

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

3.1 Installation Checklist .............................................................................................. 11 3.2 Running the Installer .............................................................................................. 11

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

3.3 Install the Diagnostics Agent Using the Installer ................................................ 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 Connectivity for the Diagnostics Agent to System Landscape Directory (SLD) 16 3.4.5 Connectivity for the Diagnostics Agent to Solution Manager (Standalone installation only) ................................................................................... 17 3.4.6 Secure Sockets Layer Archive for the Diagnostics Agent ............................ 19

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

4.1 Performing a Remote installation with the Installer ............................................ 20 4.2 Starting the Installer GUI Separately .................................................................... 21

SAP Solution Manager - End-to-End Root Cause Analysis October 2012

Diagnostics Agent Setup Guide 1

1 Introduction

This guide is only valid for installations using Software Provisioning Manager. For installations using Standalone Diagnostics Agent DVD based on SAPinst see 7.30 Diagnostics Agent Setup Guide (SAP Note 1448655).

This guide explains how to install Diagnostics Agents for:

SAP Enhancement Package 1 for SAP Solution Manager 7.0 (check the Diagnostics Agent version to install [page 5] for more details).

SAP Solution Manager 7.1

For SAP Solution Manager 7.0, see the Diagnostics Agent version to install [page 5].

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.3 DVD. If the Diagnostics Agent is installed on your

Managed System, the folder /usr/sap/<DASID>/SMDA<00-98>/SMDAgent

should exist. By default <DASID> is set to DAA.

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

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

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

You Check the Hardware Requirements, Set DISPLAY (UNIX only) and Set limits on system resource (UNIX only) [page 9]

You Install the Diagnostics Agent Using the Installer [page 12]

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



1.2 New Features

Here you can find the new features in this release.

Area Description

Software Provisioning Manager

Software provisioning manager is the successor of the product-and-release-specific delivery of provisioning tools, such as SAPinst. Before you perform an installation, we recommend that you always download the latest version of the software provisioning manager [page 9] which is part of the Software Logistics Toolset (SL Toolset for short). This way, you automatically get the latest SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note 1680045.

As a result, SAPinst has been renamed to software provisioning manager (installer for short) in this documentation.

However, the term “SAPinst” is still used in:

Texts and screen elements in the software provisioning manager GUI

Naming of executables, for example sapinst.exe

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

Size on File System The Diagnostics Agent Size on the File System is now lower than 600 MB at the end of the installation.

Connectivity for the Diagnostics Agent

The connection to the Solution Manager system based on SSL is no more proposed by default.

If you want to setup a connection based on SSL, you have to specify NEED_SSL=true in the command to start The installer.

JCE Policy Zip File The Java(TM) Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files is no more required during 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 Solution Manager 7.1.




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

Select:

Release 7.0 EPH1.

Release 7.1.

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

1448655 Inst. 7.30 - Diagnostics Agent installation

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

1031096 Installing Package SAPHOSTAGENT

1680045 Software provisioning manager 1.0

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

Installer Software provisioning manager 1.0

<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 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 the Diagnostics Agent version to install [page 5]

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

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

2.5 Your machine meets the Hardware Requirements [page 9]

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

2.7 You Set limits on system resource (UNIX only) [page 10]

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

SAP Note 1357812 1368413 1448655

Supported OS See Product Availability Matrix (PAM) [page 6].

See Product Availability Matrix (PAM) [page 6].

See Product Availability Matrix (PAM) [page 6].

For more details see SAP Note 1365123.







Product Availability Matrix (PAM)

OS Hardware SOLMAN since 7.01 SP20 (included)

SOLMAN lower than 7.01 SP 20

Windows Server 2003(R2) - IA32 / IA64 / X64 7.30 SP2 NW 7.01 SR1

Server 2008 (R2) - IA32 7.30 SP2 N.A

Server 2008 (R2) - IA64 / X64 7.30 SP2 NW 7.01 SR1

AIX 5.3 7.20 NW 7.01 SR1

6.1 7.30 SP2 NW 7.01 SR1

7.1 7.30 SP2 NW 7.01 SR1

HP-UX 11.23 - IA64 64bit 7.20 NW 7.01 SR1

11.31 - IA64 64bit 7.30 SP2 NW 7.01 SR1

11.23, 11.31 - PA-RISC 64 bit N.A NW 7.01 SR1

Solaris 9, 10 - SPARC 64bit / x64 64bit 7.30 SP2 NW 7.01 SR1

11 - SPARC 64bit / x64 64bit (*1) 7.30 SP2 NW 7.01 SR1

Linux SUSE SLES 9 - IA32 / IA64 / x64 64bit / Power 64 bit

7.20 NW 7.01 SR1

SLES 9 - System z 64 bit CE 7.20 NW 7.01 SR1

SLES 10 - IA32 / IA64 / x64 64bit / Power 64 bit

7.30 SP2 NW 7.01 SR1

SLES 11 - IA32 / IA64 / x64 64bit / Power 64 bit

7.30 SP2 NW 7.01 SR1

SLES 11 SP2 - IA32 / IA64 / x64 64bit / Power 64 bit (*1)

7.30 SP2 NW 7.01 SR1

SLES 10, 11 - System z 64 bit NW 7.30 (EHP1)

NW 7.01 SR1

Linux REDHAT

EL4 - IA64 / x64 64bit / Power 64 bit

7.20 NW 7.01 SR1

EL5, 6 - IA64 / x64 64bit / Power 64 bit

7.30 SP2 NW 7.01 SR1

EL5, 6 - System z 64 bit NW 7.30 (EHP1)

NW 7.01 SR1

Oracle Linux

5 - x86_64 64bit 7.30 SP2 NW 7.01 SR1

6 - x86_64 64bit 7.30 SP2 N.A

IBM i 5.4 - Power 64bit 7.20 NW 7.01 SR1

6.1 , 7.1 - Power 64bit 7.30 SP2 NW 7.01 SR1

z/OS 1.9, 1.10, 1.11, 1.12, 1.13 - System z 64bit

Scheduled 01.2013

N.A

(*1) Upgrade Kernel to 720_EXT afterwards. For more details see SAP Note 1707141.




During the installation if the Prerequisite Checker Results screen complains about your Operating System Version and if your OS is listed in the table above, you can go ahead with the installation.

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 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 Do not configure connection 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 the installer 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.

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



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.

We recommend that you select this option

Direct P4 Connection via Java EE Dispatcher Node: the Diagnostics Agent connects to the selected Java EE dispatcher node. But this implies that the node is running.

The two following ways are possible only if you specify NEED_SSL=true in the

command to start the installer.

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

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

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.3 DVD [page 8]

Download the standard SAP NetWeaver DVDs (SAP NetWeaver 7.3) [page 9]

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

This guide is only valid for installations using Software Provisioning Manager 1.0. For installations using the Standalone Diagnostics Agent 7.31 DVD see the 730_Diag_Agent_Setup_Guide.pdf file attached to the SAP Note 1448655.




2.4.2 Download the standard SAP NetWeaver DVDs

For your installation you need the latest version of the software provisioning manager 1.0 archive plus the UC Kernel (folder K_U_<Version>_<OS>) where U means Unicode.

These media are available as follows:

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

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

SWPM: http://service.sap.com/swdc Support Packages and Patches A – Z

Index S SL Toolset SL Toolset <release> Entry by Component Software

Provisioning Manager Software Provisioning Manager 1.0 <Operating System> UC Kernel: check SAP Note 1680045

2.5 Hardware Requirements

Hardware Requirement Requirement

Minimum disk space 500 MB for common libraries

500 MB by Diagnostics Agent

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

300 MB of free space in the installation directory

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

Minimum RAM 256 MB

Operating system releases For supported operating system releases check the Product Availability Matrix at http://service.sap.com/pam.

The Diagnostics Agent 7.3 PAM is extended to all the Windows operating systems (as of Windows Server 2003). Therefore messages displayed in the Prerequisite Checker Results screen regarding Windows operating system compatibility are not relevant.

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

2.6 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 the installer 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


https://websmp201.sap-ag.de/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900002540



2.7 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 see 730_Diag_Agent_Setup_Guide.pdf file attached to the SAP Note 1448655.





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 the installer [page 11]

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

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

3.2 Running the Installer

This section describes how to run the installation tool software provisioning manager 1.0 (the “installer” for short). Software provisioning manager 1.0 includes a GUI client and a GUI server, which both use Java. In the following, GUI client and GUI server are called the “installer GUI”.

This procedure describes an installation where the installer and the installer GUI are running on the same host.

If necessary, you can:

perform a remote installation with the installer [page 20], where installer GUI is running on a separate host from the installer

Start the installer GUI separately [page 21]

3.2.1 Running the installer on Unix

1. Log on to your host as user root.

2. Mount the DVDs.

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

3. Change to the directory:

cd <SMD Agent DVD>/SWPM10_IM_<OS>_<platform>

4. Run the command:

./sapinst

The installer GUI starts and the Welcome screen is displayed.



The installer creates the installation directory sapinst_instdir directly

below the temporary directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environment variable. If no

value is set for these variables, the installer 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 the

installer.

3.2.2 Running the Installer on Windows

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

machine involved.

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

3. Double-click the executable in the Windows Explorer or open a command prompt in the installation directory and run the command:

<DVD drive>:\<SMD Agent DVD>\SWPM10_IM_<OS>_<platform>\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 is displayed, and the installation begins.

The installer creates the installation directory sapinst_instdir, where it

keeps its log files, and which is located directly in the %ProgramFiles%

directory. If the installer 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 the installer on System I (I5/OS)

Do all the preparations and start the installer as described in the Installing SAP Systems based on SAP NetWeaver 7.3/7.3 EHP1 Using Software Provisioning Manager 1.0 SP00 installation guide.

3.3 Install the Diagnostics Agent Using the Installer

Process Flow

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

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

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

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



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

SSL, specify NEED_SSL=true in the command to start the installer.

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 installer dialogs and enter the required Diagnostics Agent Parameters.

6. The installer 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 the installer.

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)

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

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

Secure Sockets Layer Archive for the Diagnostics Agent

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

Parameters Description

System ID <DASID> of

SAP Solution Manager

Diagnostics Agent

The installer sets the system ID of SAP Solution Manager

Diagnostics Agent, <DASID>, to DAA by default.

If a Diagnostics Agent 7.3 is already installed on this

machine, the installer sets <DASID> to its SID.

If DAA is already used by another product that is not a



Diagnostics Agent, the installer 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 98 to 00.

The instance number is set automatically to the next free and valid instance number that has not yet been assigned to the SAP system.

The instance number is used to specify the name of the Diagnostics Agent instance directory that the installer automatically creates during the installation.

The directory of the Diagnostics Agent instance is called SMDA<Instance_Number>.

Virtual Host Name ( also called Logical 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.

The installer checks the rightness of the input.

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

Installation drive Base directory for the Diagnostics Agent.



On windows only 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) the installer 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, the installer 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 730_Diag_Agent_Setup_Guide.pdf file attached to the SAP Note 1448655 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, the installer 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 the installer creates this user, make sure that the user password you choose meets the requirements of your operating system.

See 730_Diag_Agent_Setup_Guide.pdf file attached to the





SAP Note 1448655 for more details.

Operating System User: SAPService<DASID>

This user is the Windows account to run the Diagnostic Agent 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.


See 730_Diag_Agent_Setup_Guide.pdf file attached to the SAP Note 1448655] for more details.

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 Connectivity for the Diagnostics Agent to System Landscape Directory (SLD)

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


SLD Destination

You can choose between the following options:

Register in existing central SLD

The installer 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 the installer 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.5 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 7].

As of Release 7.20 you can choose to connect the Diagnostics Agent directly to the Solution Manager system even if you registered it into the SLD during the previous step.


Connection of the Diagnostics Agent to SAP Solution Manager


Configure connection: the Diagnostics Agent is connected to the Solution Manager system.

The installer only prompts you for the Connection Type listed below in this table if you select this option.

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

Connection Type


P4 Connection via SCS message server: select this option to connect the agent to the Managing system via the Message Server. In that case we rely on the Java EE engine to dispatch to one of the dispatchers

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



up and running.

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

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

The last two options are available only if you specify

NEED_SSL=true in the command to start the installer.

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.

3.4.6 Secure Sockets Layer Archive for the Diagnostics Agent

The SSL Libraries location is asked if you choose a connection to the Solution Manager

system based on SSL (you specified NEED_SSL=true in the command to start the installer).


SSL libraries path Absolute path to the folder for the SSL libraries.



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

Performing a Remote installation with the Installer [page 20]

Starting the Installer GUI Separately [page 21]

The following topics are described in the 730_Diag_Agent_Setup_Guide.pdf file attached to the SAP Note 1448655.

How to Avoid Automatic Logoff by the Installer (windows)

Operating system limits for the Diagnostics Agent

Directories of the Diagnostics Agent

Starting, Stopping and Managing the Diagnostics Agent

Mass Deployment of the Diagnostics Agent (Unattended mode)

Deleting a Diagnostics Agent

Post installation steps

Troubleshoot the installer and the Diagnostics Agent

4.1 Performing a Remote installation with the Installer

You use this procedure to install your Diagnostics Agent on a remote host. In this case, the installer and the GUI server run on the remote host, and the installer GUI runs on the local host. The local host is the host from which you control the installation with the installer GUI.

If your security policy requires that the person performing the installation by running the installer GUI on the local host is not allowed to know root (UNIX) or administrator (Windows) credentials on the remote host, you can specify another operating system user for

authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter

when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524.

UNIX

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

2. Log on as user root.

3. Mount the DVD

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


5. Start the installer by executing the following command:

./sapinst -nogui

The installer now starts and waits for the connection to the installer 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 the installer GUI on your local host as described in Starting the Installer GUI Separately [page 21].





WINDOWS

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

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

machine involved.



cd <DVD drive>:\<SMD Agent DVD>\SWPM10_IM_<OS>_<platform>

5. Enter the following commands:

sapinst.exe -nogui

The installer now starts and waits for the connection to the installer 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 the installer GUI on your local host as described in Starting the Installer GUI Separately [page 21].

4.2 Starting the Installer GUI Separately

You use this procedure to start the installer GUI separately.

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

You closed the installer GUI using File Exit from the installer menu while the installer is still running.

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

UNIX

1. Log on as user root.

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



4. Start the installer 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 the installer GUI using File Exit from the installer menu and want to reconnect to the installer,



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

./sapinstgui -standalone -port <port_number>

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

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




The installer GUI starts and tries to connect to the GUI server and the installer, using the local host as default. If the installer and the GUI server are running on another host, the installer GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which the installer 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. Change to the directory of the sapinst executables:

cd <DVD drive>:\<SMD Agent DVD>\SWPM10_IM_<OS>_<platform>

4. Start the installer 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 the Installer GUI using File Exit from the Installer menu and want to reconnect to the Installer,

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

sapinstgui.exe -standalone -port <port_number>

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

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






The Installer GUI starts and tries to connect to the GUI server and the Installer, using the local host as default. If the Installer and the GUI server are running on another host, the Installer GUI cannot connect and the SAP Installation GUI Connection dialog appears. In this case, enter the name of the host on which the Installer is running and choose Log on. The first dialog of the installation appears and you can perform the remote installation from your local host.

Documents

Diagnostics Agent 7.3 - Setup Guide