Diagnostic Agent

Installation and Setup GuideDocument version: 7.0 2014-10-31

Diagnostics Agent: WindowsUsing Software Provisioning Manager 1.0 SP7

CUSTOMER

About this Guide

SAP System InstallationSAP systems should only be installed by SAP Technical Consultants certified for your operating system, your database, and the SAP system that you are installing.

SAP Installation ToolUse the SAP installation tools according to the instructions and for the purposes described in the SAP installation document. Improper use of the SAP installation tools can damage files and systems already installed.

2

CUSTOMER Copyright 2014 SAP AG.All rights reserved.

Diagnostics Agent: WindowsAbout this Guide

Typographic Conventions

Table 1Example Description Angle brackets indicate that you replace these words or characters with appropriate entries

to make entries in the system, for example, Enter your .

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

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

Cross-references to other documentation or published worksExample Output on the screen following a user action, for example, messages

Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

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

EXAMPLE Keys on the keyboard

Diagnostics Agent: WindowsTypographic Conventions

CUSTOMER Copyright 2014 SAP AG.

All rights reserved. 3

Document History

The following table provides an overview of the most important document changes.

Table 2Version Date Description1.0 2013-04-09 Release covering the Diagnostics Agent 7.3 SP3 Standalone Installer.2.0 2013-07-15 Release covering the Software Provisioning Manager 1.0 SP3 Installer.4.0 2013-10-28 Release covering the Software Provisioning Manager 1.0 SP4 Installer.4.1 2013-12-04 Section on Product Availability Matrix [page 15] added.4.2 2013-12-04 Section on Differences between SWPM and 70SWPM Installers [page 16] added.4.3 2013-12-06 Sections on Using the SMD Setup Script [page 59] and SAP Router [page 68] added.

Both sections were moved to this guide from the Diagnostics Agent Trouble Shooting Guide.4.4 2013-12-10 Section on Changing the Log Level [page 62] added. The section was moved to this guide

from the Diagnostics Agent Trouble Shooting Guide.4.5 2013-12-19 Section on Kernel for the Diagnostics Agent [page 18] added. The section was moved to

this guide from SAP Note 1858920.4.6 2013-12-19 Document reference improved, see Online Information from SAP [page 77]. Small fix in

section Diagnostics Agent System ID and Instance Number [page 21].5.0 2014-03-10 Release covering the Software Provisioning Manager 1.0 SP5 Installer. This Diagnostics

Agent Installation and Setup Guide is completely rewritten and released for the following operating system families: IBM i, Linux and UNIX, Windows, z/OS.

5.1 2014-04-10 Changes and corrections in following sections: Diagnostics Agent Download Paths [page 32] Kernel for the Diagnostics Agent [page 18] Patching the Installation Media [page 32] Direct SAP Solution Manager Connection [page 20] SAP Solution Manager Connectivity Parameters [page 25] Using the SMD Setup Script [page 59]

6.0 2014-07-07 Release covering the Software Provisioning Manager 1.0 SP6 Installer. Changes and corrections in the sections listed in Service Pack Specific

Documentation [page 11] Added section Unsupported Features [page 68]

6.1 2014-08-31 Document adjusted to reflect support for the SAP Kernel 7.42. Changes and corrections in the sections listed in Service Pack Specific Documentation [page 11].

7.0 2014-10-31 Release covering the Software Provisioning Manager 1.0 SP7 Installer.

4


Diagnostics Agent: WindowsDocument History

Version Date Description Changes and corrections in the sections listed in Service Pack Specific

Documentation [page 11] Changes in section SAP Solution Manager Connectivity Parameters [page 25] Added section Unattended Installation [page 46]

Diagnostics Agent: WindowsDocument History



Content

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.2 Service Pack Specific Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.4 Components for Reporting an Incident . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.5 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 Installation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3 Product Availability Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.4 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.5 Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.6 Differences between SWPM and 70SWPM Installers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.7 Kernel for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.8 JVM for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.9 Connection Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.10 Direct SAP Solution Manager Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.11 System Landscape Directory Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.12 Basic Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

General Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Diagnostics Agent System ID and Instance Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Operating System Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Diagnostics Agent SLD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 SAP Solution Manager Connectivity Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.3 Required User Authorization for Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283.4 Using Logical Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.5 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.6 Patching the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.7 Diagnostics Agent Download Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.3 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 How to Avoid Automatic Logoff by the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6


Diagnostics Agent: WindowsContent

Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

5 Unattended Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.1 Unattended Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465.2 Preparing an Unattended Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.3 Running an Unattended Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.4 Running an Unattended Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.5 Troubleshooting an Unattended Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556.2 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556.3 Complying with SAP Solution Manager Security Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

7 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.1 Installation Guidance for Experienced Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577.2 Installing the Diagnostics Agent Optionally with the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . 587.3 Using the SMD Setup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597.4 Changing the Log Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627.5 Starting and Stopping the SAP System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647.6 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657.7 Troubleshooting the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.8 Installer and Diagnostics Agent Version Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677.9 Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687.10 SAP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687.11 SAP System Security on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697.12 Automatic Creation of Accounts and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707.13 Summary of Diagnostics Agent Users and Groups on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727.14 Performing a Domain Installation Without Being a Domain Administrator . . . . . . . . . . . . . . . . . . . . . 72

A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77A.2 Using PowerShell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Diagnostics Agent: WindowsContent



1 Introduction

This guide explains how to install a Diagnostics Agent for SAP Solution Manager 7.10 releases. Older SAP Solution Manager releases that are out of extended maintenance are not covered by this guide.This guide is part of a global installation and configuration procedure which is described in the document How to Use SAP Solution Manager Configuration (SOLMAN_SETUP) (reference is provided at Online Information from SAP [page 77]).

RecommendationSoftware provisioning manager 1.0 is the recommended successor of the previously distributed Diagnostics Agent standalone installers 7.3 SP3, 7.3 SP2, 7.2, etc.

CautionBefore you start the implementation: Make sure you have the latest version of this document, which can be downloaded from:

service.sap.com/sltoolset Software Logistics Toolset 1.0 Documentation System ProvisioningInstallation: Diagnostics Agent .

Check SAP Note 1858920: Diagnostics Agent installation with SWPM, for issues that may exist with this version of the installer, and for corresponding solutions.

Naming Conventions Diagnostics Agent

SAP Solution Manager Diagnostics Agent is the remote component of End-to-End Root Cause Analysis. It allows having a connection between SAP Solution Manager and the Managed System(s), and then to collect information from the Managed Systems for reporting purposes.

FQNAbbreviation for Fully Qualified Name (e.g. sldhost.domain.corp and not the short host name sldhost).

InstallerRefers to software provisioning manager 1.0.

Managed SystemTerm for a satellite system (for example, an SAP NetWeaver ABAP or SAP NetWeaver Java system) managed by SAP Solution Manager.

SWPM or 70SWPMAbbreviations for different installer versions. For details refer to Differences between SWPM and 70SWPM Installers [page 16].

VariablesTable 3Variables Description

Diagnostics Agent system ID in uppercase letters.

Diagnostics Agent: WindowsIntroduction



Variables Description

Diagnostics Agent system ID in lowercase letters.

Fully Qualified Name (sldhost.domain.corp and not the short host name sldhost).

Instance Number of a Diagnostics Agent.

Operating System name.

The system ID of an arbitrary SAP system in uppercase letters, possibly, but not necessarily a Diagnostics Agent system ID. In this guide is only used in situations where also non Diagnostics Agent system IDs are meant, for example in section Diagnostics Agent System ID and Instance Number [page 21].

The system ID of an arbitrary SAP system in lowercase letters, possibly, but not necessarily a Diagnostics Agent system ID. In this guide is only used in situations where also non Diagnostics Agent system IDs are meant.

Windows Operating SystemIn this document, Windows Server 2008 (R2) or Windows Server 2012 (R2) with (R2) written in parentheses means that the information applies to both Windows Server 2008 and Windows Server 2008 R2, or Windows Server 2012 and Windows Server 2012 R2.

1.1 New FeaturesThe table below provides an overview of the new features.Make sure that you also read the release notes at service.sap.com/releasenotes.Table 4Area 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 or system copy, we recommend that you always download the latest version of the software provisioning manager [page 30] 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

10



Area Description Naming of executables, for example sapinst.exe Naming of command line parameters, for example

SAPINST_USE_HOSTNAME New option Verify Signed Media:

The digital signature ensures that the signatory of a digital document can be identified unambiguously and signatorys name is documented together with the signed document, the date, and the time.For more information, see SAP Note 1979965

Windows Server 2012 (R2) For Windows Server 2012 (R2), we only use PowerShell commands to describe Windows commands. You need to open the Power Shell in administrative mode. For more information about PowerShell, see Using PowerShell [page 77].

1.2 Service Pack Specific Documentation

This guide is updated with each software provisioning manager 1.0 service pack (SP). Following sections hold SP-specific details and should be read extra careful: Differences between SWPM and 70SWPM Installers [page 16] Kernel for the Diagnostics Agent [page 18] JVM for the Diagnostics Agent [page 19] Patching the Installation Media [page 32] Diagnostics Agent Download Paths [page 32] Installing the Diagnostics Agent Optionally with the SAP System [page 58] Installer and Diagnostics Agent Version Information [page 67] Unsupported Features [page 68]

1.3 SAP Notes for the Installation

You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation.Make sure that you have the up-to-date version of each SAP Note, which you can find at service.sap.com/notes.Table 5: SAP Notes for the InstallationSAP Note Number Title Description

1680045 Release Note for Software Provisioning Manager 1.0

Software provisioning manager 1.0 with installation and system copy for SAP NetWeaver-based systems




SAP Note Number Title Description

1710950 Inst. SAP Systems Based on NW 7.1 and higher: Windows

Windows-specific information about the SAP system installation and corrections to this documentation

1732161 SAP Systems on Windows Server 2012 (R2) Windows Server 2012 (R2)-specific information for the SAP system installation

1365123 Installation of Diagnostics Agents Overview of the Diagnostics Agent installation strategies

1833501 Diagnostics Agent Installer Versions More information about available Diagnostics Agent installer versions

1858920 Diagnostics Agent installation with SWPM Installation and Post-installation steps for installers based on software provisioning manager 1.0 (SWPM)

855498 Installation Prerequisite Checker SAP Software on UNIX, Windows, and IBM i: Checking OS Dependencies

1.4 Components for Reporting an Incident

In case of problems, contact SAP Support by reporting an incident on one of the following components:Table 6Components Description

SV-SMG-INS Issues related to Installation, Configuration and Upgrade of SAP Solution Manager

SV-SMG-INS-AGT Issues related to Diagnostics Agent Installation

BC-OP-AIX OS specific issues related to Diagnostics Agent Installations on IBM AIX

BC-OP-AS4 OS specific issues related to Diagnostics Agent Installations on IBM i

BC-OP-LNX OS specific issues related to Diagnostics Agent Installations on Linux

BC-OP-NT OS specific issues related to Diagnostics Agent Installations on Windows

BC-OP-SUN OS specific issues related to Diagnostics Agent Installations on Solaris

BC-OP-S390 OS specific issues related to Diagnostics Agent Installations on z/OS

SV-SMG-DIA Issues related to SAP Solution Manager Diagnostics

12



Components Description

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

BC-CCM-HAG Issues related to SAP Host Agent

XX-PART-WILY Issues related to Introscope

1.5 Accessing the SAP LibraryThe references to SAP NetWeaver Library documentation in this installation guide always refer to the following on SAP Help Portal:Table 7Product and Release SAP Library Path

SAP systems based on SAP NetWeaver 7.3 help.sap.com/nw73 Application Help Function-Oriented View: English

SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1

help.sap.com/nw731 Application Help Function-Oriented View: English

SAP systems based on SAP NetWeaver 7.4 help.sap.com/nw74 Application Help Function-Oriented View: English




2 Planning

2.1 Planning Checklist

Before starting the installation you must perform the following planning steps:1. Follow the Pre-Installation Guidance in section Complying with SAP Solution Manager Security

Guidelines [page 56].2. Make sure you have understood the terminology with regard to Logical Host Names [page 29] and Virtual

Host Names [page 30].3. Select your Installation Strategy [page 14].4. Check the Product Availability Matrix [page 15] and ensure that your operating system release is

supported.5. Make sure the Hardware Requirements [page 15] for the Diagnostics Agent are met.6. Make sure you have read the sections listed in Service Pack Specific Documentation [page 11].7. Read the section on Differences between SWPM and 70SWPM Installers [page 16] and select the installer

version you want to use.8. Consider Running the Prerequisites Check in Standalone Mode (Optional) [page 15].9. Select a Kernel for the Diagnostics Agent [page 18].10. Understand the situation with regard to the JVM for the Diagnostics Agent [page 19].11. Decide on the Connection Selection [page 19] for the Diagnostics Agent.12. Collect the Basic Installation Parameters [page 20].13. Continue with the Preparation [page 27] section.

2.2 Installation Strategy

Follow the Diagnostics Agent installation guidance in the documentation attached to SAP Note 1365123. It is important that you decide if you want to install one or more Diagnostics Agents on your system, or if you want to use the Agents On-the-fly feature.In general, you will need one Diagnostics Agent on each host to be managed. In case the SAP or third party systems to be managed have been set up using logical host names, it is essential to have one Diagnostics Agent instance per logical host. For further details refer to section Using Logical Host Names [page 29].If a Diagnostics Agent is already installed on your system, the folder /usr/sap//SMDA/SMDAgent should exist. For further details refer to sections Diagnostics Agent System ID and Instance Number [page 21] and SAP Directories [page 27].

14


Diagnostics Agent: WindowsPlanning

2.3 Product Availability MatrixProduct Availability Matrix (PAM) information for installing a Diagnostics Agent with software provisioning manager 1.0 based installers can be found at:

service.sap.com/sltoolset SL Toolset Software Logistics Toolset 1.0 PAMor:

service.sap.com/sltoolset SL Toolset Software Logistics Toolset 1.0 Product Availability Matrix (PAM)Then open the provided PDF file and search for Diagnostics Agent.

General PAM InformationThe central PAM entry page for all SAP products can be found at: service.sap.com/pam

Platform Compatibility Matrix for EEM RobotsFor a Platform Compatibility Matrix for EEM Robots (that require a Diagnostics Agent installation) refer to following SCN Wiki page: wiki.scn.sap.com/wiki/x/goCKEw

2.4 Hardware RequirementsTable 8: Diagnostics Agent Hardware RequirementsCategory Requirement

Minimum disk space Depending on your platform: Up to 6 GB for installation media (packed and unpacked versions of SWPM SAR-file and

kernel ZIP-file) Up to 1.5 GB for the installed Diagnostics Agent Up to 1 GB of free space in the installation directory

Minimum RAM 256 MB

2.5 Running the Prerequisites Check in Standalone Mode (Optional)

CautionThe Diagnostics Agent Platform Availability Matrix supports a wide range of operating systems, operating system versions, hardware architectures, and kernel versions. The prerequisites checker integrated in the software provisioning manager may generate warnings for the operating system version that you are installing on, or for the kernel version that you are installing with. As long as you comply with the Diagnostics Agent Product Availability Matrix [page 15] you can ignore these prerequisites checker warnings.

When you install an SAP system, the installer automatically starts the prerequisites check and checks the hardware and software requirements in the background. As an optional step during planning, you can also run the




prerequisites check in standalone mode to check the hardware and software requirements for your operating system and the SAP instances before the actual installation.

RecommendationWe recommend that you use the prerequisites check, and the Product Availability Matrix [page 15], and the Hardware Requirements [page 15] table for reference.

Procedure

1. Copy the installer to the host where you want to run the prerequisites check as follows:1. Download the latest version of the software provisioning manager 1.0 archive

SWPM10SP_.SAR fromservice.sap.com/swdc Support Packages and Patches A - Z Index S SL Toolset SL Toolset

Entry by Component Software Provisioning Manager Software Provisioning Mgr 1.0

2. Unpack the software provisioning manager 1.0 archive to a local directory using the following command:SAPCAR -xvf \.SAR -R

2. Start the installer as described in Running the Installer [page 34].3. On the Welcome screen, choose Preparations Prerequisites Check .4. Follow the instructions in the installer dialogs and enter the required parameters.

NoteFor more information about each parameter, position the cursor on the parameter field and choose F1 in the installer.

After you have finished, the Parameter Summary screen appears. This screen summarizes all parameters that you have entered and that you want to have checked. If you want to make a change, select the relevant parameters and choose Revise.

5. To start the prerequisites check, choose Next.

Result

The Prerequisite Checker Results screen displays the results found. If required, you can also check the results in file prerequisite_checker_results.html, which you can find in the installation directory.

2.6 Differences between SWPM and 70SWPM InstallersThe below table lists the differences between the two available software provisioning manager versions SWPM (SWPM10SP_.SAR) and 70SWPM (70SWPM10SP_.SAR).

16



Both versions offer the Diagnostics Agent installation option via Generic Installation Options. These installation options do not have a dependency on the SAP NetWeaver product or SAP NetWeaver product version that you are installing.See also section Preparing the Installation Media [page 30].

RecommendationDownloading and using the recommended SWPM (SWPM10SP_.SAR) will give you more installation options.

Table 9SWPM 70SWPM

Per SWPM 1.0 SP7, the SWPM and 70SWPM installers have the same code base and have the same feature set.

Per SWPM 1.0 SP7, the SWPM and 70SWPM installers have the same code base and have the same feature set.

File installationinfo.properties (generated during the installation) contains sapinst_version property with value: SWPM10SP.

File installationinfo.properties (generated during the installation) contains sapinst_version property with value: 70SWPM10SP.

Offers installation option Install - Diagnostics Agent with 7.41/7.42 Kernel, see Kernel for the Diagnostics Agent [page 18].

Feature not offered.

MarkersThis document holds descriptions that may be specific to one of the two software provisioning manager 1.0 versions that exist. In such cases respective text parts are marked with one of the below marker text strings.Table 10Marker Description

Feature is 71X SWPM ONLY Only applies to: software provisioning manager 1.0 for systems based on SAP NetWeaver 7.1x or higher. On the SAP Service Marketplace these are Download Objects with Title: SW Prov. Mgr. 1.0 SP for systems based on NW7.1x or higher

Unless explicitly stated otherwise, the documentation refers to this installer. Sometimes the abbreviation SWPM or (in bold) SWPM is used to refer to this installer.

Feature is 70X SWPM ONLY Only applies to: software provisioning manager 1.0 for systems based on SAP NetWeaver 7.0x. On the SAP Service Marketplace these are Download Objects with Title: SW Prov. Mgr. 1.0 SP for systems based on NW7.0x

Only if explicitly stated, the documentation refers to this installer. Sometimes the abbreviation 70SWPM or (in bold) 70SWPM is used to refer to this installer.




2.7 Kernel for the Diagnostics AgentDependency to Kernel of Managed SystemThe Diagnostics Agent is an SAP System just like any other SAP System (SAP NetWeaver ABAP, SAP NetWeaver Java, etc.). The Diagnostics Agent has its own kernel, that is completely independent of the kernel of the Managed System(s) available on the host where the Diagnostics Agent is installed.A Diagnostics Agent can be installed with (e.g.) a 7.21 EXT or 7.21 kernel, while the Managed System has a 7.41 or a 7.42 kernel. It is also possible and supported, that a Diagnostics Agent and a Managed System have the same kernel version, but have different patch levels.

General InformationDiagnostics Agent installations are supported with one of the below listed kernels. The Product Availability Matrix (PAM) [page 15] provides information on which kernel versions are supported on which platform versions.

CautionIf you want to use a 7.21 EXT or 7.21 kernel, you will have to download the respective kernel archive that has been released for software provisioning manager 1.0 SP7.If you want to use a 7.20 EXT or 7.20 kernel, you will have to download the respective kernel archive that has been released for software provisioning manager 1.0 SP4.

For download instructions refer to Diagnostics Agent Download Paths [page 32].

Install Diagnostics AgentThe installation option Install - Diagnostics Agent will ask for kernel media in the following way: Kernel 7.20/7.21 [EXT] for Installation / SWPM

The below listed kernel versions are supported: 7.20 EXT kernel, Unicode, 64-bit 7.20 kernel, Unicode, 64-bit 7.20 kernel, Unicode, 32-bit 7.21 EXT kernel, Unicode, 64-bit 7.21 kernel, Unicode, 64-bit 7.21 kernel, Unicode, 32-bit

Install Diagnostics Agent with 7.41/7.42 Kernel

NoteFeature is 71X SWPM ONLY, see also Differences between SWPM and 70SWPM Installers [page 16].

The installation option Install - Diagnostics Agent with 7.41/7.42 Kernel will ask for kernel media in the following way: UC Kernel NW740

The below listed kernel versions are supported: 7.41 kernel, Unicode, 64-bit 7.42 kernel, Unicode, 64-bit

18



Kernel SelectionThis software provisioning manager 1.0 SP supports the above mentioned kernel flavors. This section provides some guidance in selecting a kernel for your Diagnostics Agent installation.

RecommendationFor a comparison of 7.21 and 7.20 kernels, we strongly recommend you to read SAP Note 1728283 and SAP Note 1975687.If next to the normal kernel versions (e.g. 7.21), also EXT kernel versions are provided (e.g. 7.21 EXT), these EXT kernel versions are meant to ensure that you can operate a fully supported environment at all times. For more information, see SAP Note 1553300.We also recommend you to check SAP Note 1680045 Release Note for Software Provisioning Manager 1.0, for any last minute updates, and for information on current kernel material numbers.

If you do not have a kernel selection strategy defined, we suggest to consider kernels in the below given order:1. 7.21 EXT or 7.41/7.42 (depending on the kind of SAP NetWeaver (based) systems you normally install)2. 7.213. 7.20 EXT4. 7.20

Background InformationFollowing document provides further background information on SAP Kernels: Understanding Kernel Releases for the SAP NetWeaver AS ABAP at scn.sap.com/docs/DOC-54170

2.8 JVM for the Diagnostics AgentDiagnostics Agent installations are only supported with SAP JVM 6. This JVM version is available with all the supported kernels. See also Kernel for the Diagnostics Agent [page 18].

2.9 Connection SelectionBefore starting the installation make sure that you have identified which installation strategy you want to use. The below two scenarios are compatible, you can configure both connections, or only one of them, or none of them.

RecommendationWe recommend that you choose Direct SAP Solution Manager Connection.

Direct SAP Solution Manager Connection: In this scenario, the Diagnostics Agent establishes a direct connection to the SAP Solution Manager system. If you select Do not configure connection the Diagnostics Agent is not connected to the SAP Solution Manager system. For details see section Direct SAP Solution Manager Connection [page 20].

System Landscape Directory Registration: In this scenario the Diagnostics Agent is registered into the specified System Landscape Directory (SLD). This scenario may be used if SAP Solution Manager is not yet




installed. If you select No SLD destination the Diagnostics Agent is not registered into the SLD. For details see section System Landscape Directory Registration [page 20].

CautionIf you select neither Direct SAP Solution Manager Connection nor System Landscape Directory Registration you will have to configure the Diagnostics Agent connectivity via the smdsetup script after the installation is finished.For more information, see Using the SMD Setup Script [page 59].

2.10 Direct SAP Solution Manager ConnectionConnect the Diagnostics Agent directly to the SAP Solution Manager system. The below connection types are available.See also SAP Solution Manager Connectivity Parameters [page 25]. P4 connection via SCS message server: the Diagnostics Agent connects to the SCS message server and is

redirected to one of the dispatcher nodes of the Java EE engine. P4 SSL connection via SCS message server: the same as P4 connection via SCS message server, but with SSL

support.

2.11 System Landscape Directory RegistrationThe System Landscape Directory (SLD) is designed for registering the systems and installed software of your landscape. If you choose to register the Diagnostics Agent in an SLD, it must be assigned to the SAP Solution Manager system afterwards ( Transaction: SOLMAN_SETUP Scenario: System Preparation Step: Connect Diagnostics Agents to Solution Manager ). This allows installing a Diagnostics Agent even if the SAP Solution Manager system is not available.See also Diagnostics Agent SLD Parameters [page 23].

2.12 Basic Installation Parameters

2.12.1 General Installation ParametersThe parameters in the below table must be provided when installing a Diagnostics Agent via Generic Installation Options.

NoteWith Diagnostics Agent installations that take place at the end of an SAP NetWeaver installation the below parameters must not be provided, see also Installing the Diagnostics Agent Optionally with the SAP System [page 58].

20



Table 11: General Installation ParametersParameters Description

Host Name Change Host Name if you plan to manage systems running on a logical host. This scenario lets the Diagnostics Agent take part in a switchover environment.

CautionThe Host Name is the short host name and not the FQN.

Package Location of the kernel medium Refer to Preparing the Installation Media [page 30] and Kernel for the Diagnostics Agent [page 18] for guidance.

Destination Drive Base directory for the Diagnostics Agent. You cannot select the Destination Drive if: The saploc share already exists (an SAP System or a Diagnostics

Agent has already been installed on this machine). The installer sets the Destination Drive to where the saploc share points to.

The saploc share does not exist and there is only one hard disk on this machine.

2.12.2 Diagnostics Agent System ID and Instance NumberTable 12: Diagnostics Agent System ID and Instance NumberParameters Description

Diagnostics Agent System ID (DASID)

By default the installer sets the Diagnostics Agent System ID (DASID) to DAA.If a Diagnostics Agent with the same kernel version as the one you are currently installing is already present on the local installation host, the installer sets to the system ID of this already installed agent.If the kernel version you have selected for your installation is different from the kernel versions of already installed Diagnostics Agents, the installer assigns another default system ID, starting from DA1 to DA9.You can overwrite the proposed system ID as required.Diagnostics Agents installed on different logical hosts (but on the same physical or virtual host) can use the same .

CautionChoose the carefully. Renaming is difficult and requires you to reinstall the Diagnostics Agent.

Make sure that the : Either does not yet exist on the local installation host, or does already exist but was only

used for a Diagnostics Agent installation in the exact same version Consists of exactly three alphanumeric characters




Parameters Description Contains only uppercase letters Has a letter for the first character Is allowed according to SAP Note 1979280

Instance Number of the Diagnostics Agent

Technical identifier for internal processes for the Diagnostics Agent. It consists of a two-digit number from 98 to 00. Default is 98.If instance number 98 is already used, the Diagnostics Agent instance number is automatically set to the next free, lower, valid instance number.The instance number must be unique on a host. That is, if more than one SAP instance is running on the same host, these instances must be assigned different numbers.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.For more information, see SAP Directories [page 27].To find out the instance numbers of SAP systems that already exist on the installation host, look for subdirectories ending with of local \usr\sap\ directories.The value is the number assigned to the instance.

CautionDo not use 43, and 89 for the instance number because: 43 is part of the port number for high availability 89 is part of the port number for Windows Terminal Server

2.12.3 Operating System UsersTable 13: Operating System UsersParameters Description

Domain Model The Windows Domain for the Diagnostics Agent operating system users adm and SAPService.

CautionSAP strongly recommends creating the Diagnostics Agent users in the Local Domain.

SAP System Administrator:adm

Administrator for the Diagnostics Agent.This user is dedicated to the Diagnostics Agent installation and has the authorization to manage the Diagnostics Agent.This user is created on every application server instance host. For security reasons, the installer by default creates this user 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.

22



Parameters DescriptionMake sure to respect the password guidance at the end of this table.

SAP System Service User:SAPService

User to run the Diagnostics Agent.Make sure to respect the password guidance at the end of this table.

SAP System Administrator:sapadm

SAP Host Agent administrator is the user for central monitoring services.This user is created only if the SAP Host Agent is automatically installed during the installation of the Diagnostics Agent.Make sure to respect the password guidance at the end of this table.

Password guidance Make sure that the password that you choose for a user meets the requirements of your operating system. In addition the password must meet the following requirements: It must be 8 to 14 characters long It must not contain \ (backslash) and " (double quote) It must contain at least one digit (0-9) It must contain at least one letter in uppercase (A-Z) It must contain at least one letter in lowercase (a-z) Depending on the configuration of the password policy, additional restrictions may apply.

Related SectionsThis guide holds several sections that are closely related to the above described operating system users. You may want to read these sections before performing the installation: SAP System Security on Windows [page 69] Automatic Creation of Accounts and Groups [page 70] Ensuring User Security [page 55]

2.12.4 Diagnostics Agent SLD Parameters

RecommendationPerforming an SLD registration is no longer recommended, see Connection Selection [page 19] and System Landscape Directory Registration [page 20].

After the Diagnostics Agent SLD parameters have been entered and Next is pressed, the credentials and the connection are tested. In case of an error a message pops up.

RecommendationIt is recommended to use the credentials and connection test facilities integrated in the installer, and to not continue the installation as long as the check fails.

Table 14: Diagnostics Agent SLD ParametersParameters Description

SLD Destination for the Diagnostics Agent You can choose between the following options:




Parameters Description Register in existing central SLD

The Diagnostics Agent will be registered in an existing central SLD.If you choose this option you will be able to select Use HTTPS.The installer will prompt you for the SLD connection parameters listed below.

CautionYou cannot specify an SAP router route string for the SAP Solution Manager connection if you register the Diagnostics Agent into an SLD.

No SLD destinationIf you choose this option, the installer does not prompt you for any SLD connection parameters.You may configure the SLD destination for the Diagnostics Agent via the smdsetup script after the installation has finished.For more information, see Using the SMD Setup Script [page 59] .

SLD HTTP Host (SLD Host if Use HTTPS was selected)

The fully qualified host name of the SAP NetWeaver Java system with the SLD, e.g. sldhost.domain.corp.

RecommendationThe host name will be checked. It is recommended to input the fully qualified host name.

SLD HTTP Port (SLD HTTPS Port if Use HTTPS was selected)

The HTTP or HTTPS port of the SAP NetWeaver Java system with the SLD.For HTTP the following naming convention applies:500.For HTTPS the following naming convention applies:501.

ExampleIf the instance number of your SAP NetWeaver Java system is 01, the SLD HTTP Port is 50100 and the SLD HTTPS Port is 50101.

SLD Data Supplier User The SLD Data Supplier user (e.g. SLDDSUSER) for the specified SLD.

Password of SLD Data Supplier User The password of the specified SLD Data Supplier user.

24



2.12.5 SAP Solution Manager Connectivity Parameters

RecommendationSpecifying a direct SAP Solution Manager connection is recommended, see Connection Selection [page 19] and Direct SAP Solution Manager Connection [page 20].

After the SAP Solution Manager connection parameters have been entered and Next is pressed, the credentials and the connection are tested. In case of an error a message pops up.

RecommendationIt is recommended to use the credentials and connection test facilities integrated in the installer, and to not continue the installation as long as the check fails.

Table 15: SAP Solution Manager Connectivity ParametersParameters Description

Connection of the Diagnostics Agent to SAP Solution Manager

You can choose between the following options: Configure connection via Java SCS Message Server

The Diagnostics Agent will be connected to the SAP Solution Manager system.If you choose this option you will be able to select Use SSL connectivity.The installer will prompt you for the SAP Solution Manager connection parameters listed below.

Do not configure connectionIf you choose this option, the installer does not prompt you for any SAP Solution Manager connection parameters.You may configure the SAP Solution Manager connection for the Diagnostics Agent via the smdsetup script after the installation has finished.For more information, see Using the SMD Setup Script [page 59].

Host (FQN) The fully qualified host name of the SAP Solution Manager system, e.g. host.domain.corp

RecommendationThe host name will be checked. It is recommended to input the fully qualified host name.

Port Depending on the Connection Type, you have to specify one of the following ports of the Java Stack of your SAP Solution Manager system: HTTP SCS Message Server Port is 81, where is the instance number of the SAP

Solution Manager Java Central Services (SCS). HTTP SCS SSL Message Server Port is 444, where is the instance number of

the SAP Solution Manager Java Central Services (SCS).

User (Administrator role) and Password

As of SAP Solution Manager 7.10 SP10 we recommend to use the SMD_AGT user of your SAP Solution Manager system. For earlier releases the SMD_ADMIN user is still recommended.

SAP Router (optional) Route and Password

The route string describes the stations of a connection required between the Diagnostics Agent and SAP Solution Manager.




Parameters DescriptionThe 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)

ExampleThe route between the Diagnostics Agent and SAP Solution Manager can look like: /H/host.domain.corp/S/3299

CautionYou cannot specify a route string if you registered the Diagnostics Agent into SLD during the previous step.

26



3 Preparation

3.1 Preparation ChecklistBefore starting the installation you must perform the following preparation steps:1. Prepare the Installation Media [page 30].2. Check the Required User Authorization for Running the Installer [page 28].3. Continue with the Installation [page 34] or the Unattended Installation [page 46] section.

3.2 SAP DirectoriesDirectories of the Diagnostics AgentThe installer creates the \usr\sap\ directory during the installation. Below this directory following directories are created: Diagnostics Agent system directory: \usr\sap\\SYS Diagnostics Agent instance directory: \usr\sap\\SMDA

CautionSince traces for the instance are created in this directory, sufficient space must be available in this directory.

Executables are replicated from the \usr\sap\\SYS to the \usr\sap\\SMDA directory every time the instance is started. The SAP copy program sapcpe compares the binaries in the system directory and the binaries in the instance directory. If the binaries in the instance directory are older than those in the system directory, sapcpe replaces them with the newer version from the system directory.The following figure shows the directory structure of the Diagnostics Agent.

Diagnostics Agent: WindowsPreparation



Figure 1: Directory Structure of the Diagnostics Agent

3.3 Required User Authorization for Running the InstallerAlthough the installer automatically grants the rights required for the installation to the user account used for the installation, you have to check whether this account has the required authorization to perform the installation. The authorization required depends on whether you intend to perform a domain or local installation. If necessary, you have to ask the system administrator to grant the account the necessary authorization before you start the installation. If you attempt the installation with an account that does not have the required authorization, the installation aborts.This section informs you about the authorization required for a domain and a local installation.

Procedure

CautionDo not use the user adm for the installation of the SAP system.

Domain InstallationFor a domain installation the account used for the installation needs to be a member of the local Administrators and the domain Admins group of the relevant domain. All machines in the system must belong to the same domain. In a domain installation, the user information is stored centrally on the domain controller and is accessible to all hosts in the system.If the SAP system is to be distributed across more than one machine, SAP strongly recommends you to perform a domain installation to avoid authorization problems.

Caution For performance and security reasons, SAP does not support an SAP system installation on a domain

controller.

28



If for any reason, the account used for the installation is not a member of the domain Admins group, you can perform the installation with a domain user who is a member of the local Administrators group. However, the domain administrator has to prepare the system appropriately for you.For more information, see Performing a Domain Installation without being a Domain Administrator [page 72].

For a domain installation, you need to:1. Check that the account used for the installation is a member of the domain Admins group.2. If required, obtain these rights by asking the system administrator to enter the account as a member of the

domain Admins group.

Local InstallationFor a local installation the account used for the installation needs to be a member of the local Administrators group of the machine involved. In a local installation, all Windows account information is stored locally on one host and is not visible to any other hosts in the system.If the SAP system is to run on a single machine, you can perform a local installation.

CautionDo not use the Windows built-in account Administrator or the renamed built-in account to install your SAP system. The built-in account only has restricted network access rights that are required by the installer. If you renamed the built-in account Administrator, do not create a new account named Administrator.

For a local installation, you need to:1. Check that the account used for the installation is a member of the local Administrators group.2. If required, obtain these rights by asking the system administrator to enter the account as a member of the

local Administrators group.

More Information

Performing a Domain Installation Without Being a Domain Administrator [page 72]

3.4 Using Logical Host Names

SAP Solution Manager has introduced the term logical host name, as an alternative to the term virtual host name that is generally used in the context of software provisioning manager and SAP NetWeaver based installations. Refer to section Using Virtual Host Names [page 30] from the standard software provisioning manager and SAP NetWeaver based installation guides (section is included below) for details.For a detailed description on logical hosts, logical host names, virtual hosts, virtual host names, physical hosts and physical host names, and how they are defined in the context of SAP Solution Manager and Diagnostics Agent installations, refer to SAP Note 1365123 - Installation of Diagnostics Agents.




3.4.1 Using Virtual Host Names

CautionMake sure to read the section on Using Logical Host Names [page 29] first.

You can use one or more virtual TCP/IP host names for SAP servers within an SAP server landscape to hide their physical network identities from each other. This can be useful when quickly moving SAP servers or complete server landscapes to alternative hardware without having to reinstall or reconfigure.

Prerequisites Make sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup. Make sure that you configured the Windows operating system properly to use virtual host names. For more

information, see SAP Note 1564275.

ProcedureTo install a non-high-availability system, proceed as described in SAP Note 1282975.

3.5 Preparing the Installation MediaThis section describes how to prepare the installation media, which are available as follows: The software provisioning manager 1.0 archive containing the installer.

You always have to download the latest version of the software provisioning manager 1.0 archive. Required kernel media. See also Kernel for the Diagnostics Agent [page 18].

PrerequisitesMake sure the latest version of the SAPCAR archiving tool is available on each installation host.You require the SAPCAR archiving tool to be able to unpack software component archives (*.SAR files) which is the format of software life-cycle media and tools that you can download from the SAP software distribution center.If required, you can download the latest version of SAPCAR from:

service.sap.com/swdc Support Packages and Patches A - Z Index S SAPCAR .For more information about SAPCAR, see SAP Note 212876.

Procedure1. Identify the required media for your installation as listed below.

30



Table 16Installation Installation Media

Diagnostics Agent Software provisioning manager 1.0 archive SWPM10SP_.SAR (recommended) or 70SWPM10SP_.SAR

NoteThis section explains the Differences between SWPM and 70SWPM Installers [page 16].

UC Kernel (folder K__U_) where U means Unicode.

NoteFor information about supported kernel versions see Kernel for the Diagnostics Agent [page 18].

NoteEvery new Diagnostics Agent installation must be Unicode.

2. Make the installation media available on the installation host as follows:1. Download the latest version of the software provisioning manager 1.0 archive from:

service.sap.com/swdc Support Packages and Patches A - Z Index S SL Toolset SL Toolset Entry by Component Software Provisioning Manager Software Provisioning Mgr 1.0

RecommendationFor Diagnostics Agent installations you only require an installer archive and a kernel archive. Alternative download paths that you may be more familiar with are documented in Diagnostics Agent Download Paths [page 32].

2. Unpack the software provisioning manager 1.0 archive to a local directory using the following command:SAPCAR -xvf \.SAR -R

3. Download and unpack the kernel ZIP-file to a dedicated directory. For details see Diagnostics Agent Download Paths [page 32]. The unpacked kernel can be made available on a local drive or on a network drive.

Caution If you copy the media to disk, make sure that the paths to the destination location of the copied

media do not contain any blanks. If you perform a domain installation and do not want to copy the media but use network drives for

mapping the installation media, make sure that the adm user has access to the UNC paths of the network drives.




If the user does not yet exist, you have to create the user manually before you install the SAP system.

3.6 Patching the Installation Media

CautionYou must only patch the SAPDIAGNOSTICSAGENT.SAR file on your kernel media, if you are explicitly instructed to do so through an SAP Note or through an incident that you have reported. SAP support personnel will instruct you on the version of the file that you must use for patching.

SAR-FileAs of Diagnostics Agent 7.4 there are operating system independent DIAGAGT*.SAR Download Objects available on the SAP Service Marketplace. These SAR-files are the successor of the operating system specific standalone installer packages that where available for the Diagnostics Agent releases 7.11, 7.2 and 7.3.The SAR-files can be used for patching Diagnostics Agents that are initially shipped via standard kernel media. The SAR-files are named like:DIAGAGTSP_-.SAR

DownloadingThe SAR-files can be downloaded from:

service.sap.com/swdc Support Packages and Patches A - Z Index S SAP SOLUTION MANAGER SAP SOLUTION MANAGER 7.1 Entry by Component Agents for managed systems DIAGNOSTICS AGENT # OS independentFor a mapping of software provisioning manager version to Diagnostics Agent version refer to Installer and Diagnostics Agent Version Information [page 67].

PatchingOnce you have downloaded and unpacked the software provisioning manager 1.0 archive and the kernel media that you have selected, you must replace the SAPDIAGNOSTICSAGENT.SAR file on the unpacked kernel media with the DIAGAGT*.SAR file that you have downloaded.The SAPDIAGNOSTICSAGENT.SAR file can be found at the following location on the unpacked kernel media:\DBINDEP\SAPDIAGNOSTICSAGENT.SAR

3.7 Diagnostics Agent Download PathsMore general download instructions are provided in Preparing the Installation Media [page 30]. Alternatively the below download paths can be used to download installer and kernel archives that are needed for Diagnostics Agent installations. All of the below download paths lead to the same installer and kernel archives.

32



Download Paths via SL Toolset PagesSL Toolset download path for installer archive: service.sap.com/sltoolset Software Logistics Toolset 1.0System Provisioning Software Provisioning Manager 1.0 SP download tool .SL Toolset download path for kernel archive: service.sap.com/sltoolset Software Logistics Toolset 1.0System Provisioning Software Provisioning Manager 1.0 SP download Kernel releases delivered for SL Toolset Kernel for installation/SWPM Installation .

Download Paths via SAP Solution Manager PagesSAP Solution Manager download path for installer archive: service.sap.com/swdc Installations and Upgrades A-Z Index S SAP Solution Manager SAP Solution Manager 7.1 SOFTWARE PROVISIONING MGR 1.0 .SAP Solution Manager download path for kernel archive: service.sap.com/swdc Installations and UpgradesA-Z Index S SAP Solution Manager SAP Solution Manager 7.1 Kernel for installation/SWPM Installation .

Download Paths for Additional SAP KernelsAdditional SAP kernels that are not available via the before mentioned paths (e.g. 7.20 and 7.42 kernels) can be downloaded via: service.sap.com/swdc Installations and Upgrades A-Z Index K SAP KERNEL -BIT UNICODE Installation .

Related DocumentationFollowing chapters contain information to support you in your decision on which installer and kernel archive to download: Product Availability Matrix [page 15] Differences between SWPM and 70SWPM Installers [page 16] Kernel for the Diagnostics Agent [page 18]




4 Installation

4.1 Installation ChecklistIn order to execute the installation you have to perform the following steps:1. Follow the instructions in Running the Installer [page 34].2. For alternative installation scenarios refer to Additional Information About the Installer [page 36].3. Continue with the Post-Installation [page 55] section.

4.2 Running the Installer

CautionThe Diagnostics Agent Platform Availability Matrix supports a wide range of operating systems, operating system versions, hardware architectures, and kernel versions. The prerequisites checker integrated in the software provisioning manager may generate warnings for the operating system version that you are installing on, or for the kernel version that you are installing with. As long as you comply with the Diagnostics Agent Product Availability Matrix [page 15] you can ignore these prerequisites checker warnings.

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.

Prerequisites You need at least 300 MB of free space in the installation directory for each installation option. In addition,

you need 300 MB free space for the installer executables. Make sure that you have defined the most important SAP system parameters as described in Basic

Installation Parameters [page 20] before you start the installation.

Procedure1. Log on to the installation host using an account with the required user authorization to run the

Installer [page 28].

CautionDo not use an existing adm user.

34


Diagnostics Agent: WindowsInstallation

2. Make the installation media available.For more information, see Preparing the Installation Media [page 30].

3. Start the installer by double-clicking sapinst.exe from the directory to which you unpacked the software provisioning manager 1.0 archive.The installer GUI starts automatically by displaying the Welcome screen.

NoteIf you need to assign a logical host name and you do not want to assign it by entering it as a parameter using the installer screens (see Basic Installation Parameters [page 20]), you can alternatively assign it as follows:1. Open a command prompt or PowerShell window in elevated mode and change to the directory to

which you unpacked the software provisioning manager 1.0 archive.2. Start the installer with the following command:

sapinst.exe SAPINST_USE_HOSTNAME= (in a command prompt).\sapinst.exe SAPINST_USE_HOSTNAME= (in PowerShell)

Before using this option, you should have read and understood the sections Installation Strategy [page 14] (especially the Agents On-the-fly feature) and Using Logical Host Names [page 29].

4. On the Welcome screen: Perform the following recommended preparations:

Go to Generic Installation Options and choose:Table 17Generic Installation Options Remarks

Verify Signed Media The digital signature ensures that the signatory of a digital document can be identified unambiguously and signatory's name is documented together with the signed document, the date, and the time. It is recommended to check the software integrity by performing a digital signature check for downloaded media and packages before using it with software provisioning manager.For more information, see SAP Note 1979965.

Go to Preparations and choose:Table 18Preparations Remarks

Prerequisites Check Checks your hardware and software requirements before you start the installation. For more information, see Running the Prerequisites Checker in Standalone Mode [page 15].

Go to Generic Installation Options Diagnostics in SAP Solution Manager and choose one of:Table 19Diagnostics in SAP Solution Manager

Remarks

Install - Diagnostics Agent Choose this option to install a Diagnostics Agent instance.

Uninstall - Diagnostics Agent Choose this option to uninstall a Diagnostics Agent instance.




Diagnostics in SAP Solution Manager

Remarks

For more information, see Deleting an SAP System or Single Instances [page 65].

5. Choose Next.6. If the installer prompts you to log off from your system, log off and log on again.

The installer restarts automatically.7. Follow the instructions on the installer screens and enter the required parameters.

NoteTo find more information on each parameter during the input phase of the installation, position the cursor on the required parameter and press F1 .

After you have entered all requested input parameters, the installer displays the Parameter Summary screen. This screen shows both the parameters that you entered and those that the installer set by default. If required, you can revise the parameters before starting the installation.

8. To start the installation, choose Start.The installer starts the installation and displays the progress of the installation. When the installation has finished, the installer shows the message: Execution of has completed.

9. We recommend deleting all files in the directory %userprofile%\.sdtgui\.10. If you copied the installer software to your hard disk, you can delete these files when the installation has

successfully completed.

4.3 Additional Information About the InstallerThe following sections provide additional information about the installer: Useful Information About the Installer [page 36] How to Avoid Automatic Logoff by the installer [page 37] Interrupted Installation [page 38] Performing a Remote Installation [page 40] Starting the Installer GUI Separately [page 41] Running the Installer in Accessibility Mode [page 44] Troubleshooting with the Installer [page 45]

4.3.1 Useful Information About the Installer 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.

For each option, the installer creates a subdirectory located in the sapinst_instdir directory.

36



The installer extracts itself to a temporary directory (TEMP, TMP, TMPDIR, or SystemRoot). These executables are deleted after the installer has stopped running.Directories called sapinst_exe.xxxxxx.xxxx sometimes remain in the temporary directory. You can safely delete them.The temporary directory also contains the log file dev_selfex.out from the extraction process, which might be useful if an error occurs.

CautionIf the installer cannot find a temporary directory, the installation terminates with the error FCO-00058.

While the installer is running, the default port 21212 is used for communication between the installer GUI server and the installer GUI client. If this port is already in use, you see an error message.In this case or if you want the installer to use a specific port, open a command prompt and change to the required directory to which you unpacked the software provisioning manager 1.0 archive.Execute sapinst.exe with the following command line parameter:GUISERVER_DIALOG_PORT=

To see a list of all available installer properties, go to the directory %TEMP%\sapinst_exe.xxxxxx.xxxx after you have started the installer, and enter the following command:sapinst.exe -p

If you need to run the installer in accessibility mode, proceed as described in Running the Installer in Accessibility Mode [page 44].

If required, you can stop the installer by choosing SAPinst Exit Process in the installer GUI menu.

NoteIf you need to terminate the installer, you can do this by choosing File Close GUI only in the menu of the Program Starter window.

If you want to install or uninstall a Diagnostics Agent in unattended mode, see the Unattended Installation [page 46] chapter.

4.3.2 How to Avoid Automatic Logoff by the InstallerWhen you install the SAP system, the installation tool checks whether the user account used for the installation has the required privileges and authorization.For a domain installation, the account needs to be both a member of the local Administrators group and the domain Admins group. For a local installation, the account needs to be a member of the local Administrators group.In both cases, 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, the installer assigns them and automatically logs the account off to activate them. To avoid the installer logging the account off, you can set these rights manually before you start the installation.

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

CautionBe aware that domain policies override locally defined policies. This means that if you want to grant domain administrator rights to a user who belongs to the local Administrators group, make sure that you have also defined domain administrator rights for this user on domain level.

1. Windows Server 2012 (R2): Press Ctrl + Esc and choose Administrative Tools Local Security Policy .

NoteServer Core for Windows Server 2012 (R2): To use and perform this task in a PowerShell, you can copy ntrights.exe from a Windows Server 2003 server to your Windows Server 2012 (R2) system.

2. Windows Server 2003 and Windows Server 2008 (R2): Choose Start Control Panel Administrative Tools Local Security Policy .

3. In the Local Security Settings window, choose Local Policies User Rights Assignment. .4. Double-click the required right under Policy and choose Add User or Group.5. In the Select Users and Groups window, choose the required user and choose Add.

The selected user appears in the box below.6. Confirm your entry and then repeat the steps for each remaining policy that the user requires for the

installation.7. Log off and log on again to apply the changes.

More InformationRequired User Authorization for Running the Installer [page 28]

4.3.3 Interrupted InstallationThe SAP system installation might be interrupted for one of the following reasons: An error occurred during the Define Parameters or Execute phase:

The installer does not abort the installation in error situations. If an error occurs, the installation pauses and a dialog box appears. The dialog box contains a short description of the choices listed in the table below as well as a path to a log file that contains detailed information about the error.

You interrupted the installation by choosing Exit Process in the SAPinst menu.

38



CautionIf you stop an option in the Execute phase, any system or component installed by this option is incomplete and not ready to be used. Any system or component uninstalled by this option is not completely uninstalled.

The following table describes the options in the dialog box:Table 20Option Definition

Retry The installer retries the installation from the point of failure without repeating any of the previous steps.This is possible because the installer records the installation progress in the keydb.xml file.We recommend that you view the entries in the log files, try to solve the problem, and then choose Retry.If the same or a different error occurs, the installer displays the same dialog box again.

Stop The installer stops the installation, closing the dialog box, the installer GUI, and the GUI server.The installer records the installation progress in the keydb.xml file. Therefore, you can continue the installation from the point of failure without repeating any of the previous steps. See the procedure below.

Continue The installer continues the installation from the current point.

View Log Access installation log files.

Procedure

This procedure describes the steps to restart an installation, which you stopped by choosing Stop, or to continue an interrupted installation after an error situation.1. Log on to your remote host as a user who is a member of the local administrators group.2. Make the medium for the installation master (folder _IM__) available on the

installation host.3. Restart the installer by double-clicking sapinst.exe from the directory to which you unpacked the software

provisioning manager 1.0 archive.4. From the tree structure on the Welcome screen, select the installation option that you want to continue and

choose Next.The What do you want to do? screen appears.

5. On the What do you want to do? screen, decide between the following alternatives and continue with Next:Table 21Alternative Behavior

Run a new option The installer does not continue the interrupted installation option. Instead, it moves the content of the old installation directory and all installation-specific files to a




Alternative Behaviorbackup directory. Afterwards, you can no longer continue the old installation option.For the backup directory, the following naming convention is used:log______

Examplelog_01_Oct_2008_13_47_56

NoteAll actions taken by the installation before you stopped it (like creating directories, or users) will not be revoked.

CautionThe installer moves all the files and folders to a new log directory, even if these files and folders are owned by other users. If there are any processes currently running on these files and folders, they might no longer function properly.

Continue with the old option The installer continues the interrupted installation from the point of failure.

4.3.4 Performing a Remote InstallationYou use this procedure to install your SAP system on a remote host. In this case, the installer and the GUI server run on the remote host, and the installer GUI client (the installer GUI for short) 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 administrator 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 sapinst.exe from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524.You can run the installer GUI on a PC with 32-bit while the installer is running on a 64-bit installation host. For more information, see Starting the Installer GUI Separately [page 41].

Prerequisites The remote host meets the prerequisites for starting the installer as described in Running the

Installer [page 34]. Both computers are in the same network and can ping each other.

To test this:1. Log on to your remote host and enter the command: ping 2. Log on to the local host and enter the command: ping

40



Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host have exactly the same version. You can check this by using the option -sfxver as described in the procedure below and in the procedure in Starting the Installer GUI Separately [page 41].

If you need to specify another operating system user with the SAPINST_REMOTE_ACCESS_USER command line parameter, make sure that this user exists on the remote host.

Procedure

1. Log on to your remote host as a user that is a member of the local administrators group.2. Make the installation media available on your remote host.

For more information, see Preparing the Installation Media [page 30].3. Open a command prompt and change to the directory to which you unpacked the software provisioning

manager 1.0 archive.4. Check the version of the sapinst executable by entering the following command:

sapinst.exe -sfxverThe version of the sapinst executable must be exactly the same as the version of the sapinstgui executable on the local host (see also Starting the Installer GUI Separately [page 41]).

5. Start the installer by executing the following command:sapinst.exe -nogui

NoteIf you need to specify another operating system user for authentication purposes, enter the following command:sapinst.exe -nogui SAPINST_REMOTE_ACCESS_USER=

The installer now starts and waits for the connection to the installer GUI. You see the following in the Program Starter window:guiengine: no GUI connected; waiting for a connection on host , port to continue with the installation

6. Start the installer GUI on your local host as described in Starting the Installer GUI Separately [page 41].

4.3.5 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 Close GUI only 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 [page 40].




Prerequisites The host on which you want to start the installer GUI meets the prerequisites for starting the installer as

described in Running the Installer [page 34].

NoteIf you want to run the installer on a UNIX host, make sure that you meet the prerequisites for the installer listed in the relevant UNIX guide.

Make sure that the sapinst.exe on the remote host and the sapinstgui.exe on the local host have exactly the same version. You can check this by using the option -sfxver as described in the procedure below and in the procedure in Performing a Remote Installation [page 40].

ProcedureIn this procedure, the following variables are used: is the name of the remote host, and is the port the GUI server uses to communicate with the GUI client (21212 by default).

NoteIf you want to run the installer GUI on a remote host, it is mandatory to start the installer using the -nogui property. If you have already started the installer without the -nogui property and want to run the GUI on a different host, you have to exit the installation process by choosing SAPinst Exit Process and then follow the steps described in Interrupted Installation [page 38]. Use the - nogui property to restart the installer and start the installer GUI on the intended host.

Starting the Installer GUI on Windows1. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the Installation Media [page 30].

NoteIf you want to start the installer GUI on a Windows operating system that is able to run 32- bit programs, you can use the software provisioning manager 1.0 archive for Windows I386.

2. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters: If you want to perform a remote installation, proceed as follows:

1. Check the version of sapinstgui.exe by entering the following command:\sapinstgui.exe -sfxverThe version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 40]).

2. Start the installer GUI by entering the following command:\sapinstgui.exe -host -port

42



If you closed the installer GUI using File Close GUI only and want to reconnect to the installer, proceed as follows:1. If you are performing a local installation with the installer and the installer GUI running on the same

host, execute the following command:\sapinstgui.exe -port

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:\sapinstgui.exe -host -port

3. The installer GUI starts and connects to the installer.

Starting the Installer GUI on UNIX1. Make the installer software available on the host on which you want to start the installer GUI.

For more information, see Preparing the Installation Media [page 30].

NoteIf you want to start the installer GUI on a Linux 32-bit operating system, make the software provisioning manager 1.0 archive for Linux I386 available.

2. Start the installer GUI by executing the sapinstgui executable with the appropriate command line parameters: If you want to perform a remote installation, proceed as follows:

1. Check the version of the sapinstgui executable by entering the following command:/sapinstgui -sfxverThe version of the sapinstgui executable must be exactly the same as the version of the sapinst executable on the remote host (see also Performing a Remote Installation [page 40]).

2. Start the installer GUI by entering the following command:/sapinstgui -host -port

If you closed the installer GUI using File Close GUI only and want to reconnect to the installer, proceed as follows:1. If you are performing a local installation with the installer and the installer GUI running on the same

host, execute the following command:/sapinstgui -port

2. If you are performing a remote installation with the installer and the installer GUI running on different hosts, execute the following command:/sapinstgui -host -port

3. The installer GUI starts and connects to the installer.




4.3.6 Running the Installer in Accessibility ModeYou can also run the installer in accessibility mode. The following features are available: Keyboard access:

This feature is available for all operating systems. High-contrast color:

This feature is derived from the Windows display properties. You can use it either for a local installation or for a remote installation.

Custom font setting:This feature is derived from the Windows display properties. You can use it either for a local installation or for a remote installation.

ProcedureActivating and Adjusting Accessibility Settings on WindowsYou first have to activate and adjust the relevant settings for the font size and color schemes before you start the installer or the installer GUI.

NoteThe following procedure applies for Windows Server 2008 and might be different when using another Windows operating system.

1. Right click on your Windows desktop and choose Personalize.2. Choose Adjust font size (DPI) and choose Larger scale (120 DPI).

To define other font size schemes, choose Custom DPI.3. In the right-hand pane, select Window Color and Appearance.

Select a color scheme from the Color scheme dropdown box.To define your own color schemes, choose Advanced.

Running the Installer in Accessibility ModeYou can either perform a local installation, where the installer and the installer GUI are running on the same host, or a remote installation, where the

Diagnostic Agent

Documents

names of installation

sap installation document

sap note

sap ag

example example arrows

sap installation tools

diagnostics agent page

sap router page