SWPM10SP4 Diag Agent Setup Guide

Installation GuideSAP Solution Manager End-to-End Root Cause AnalysisDocument Version: 4.7 17-February-2014

CUSTOMER

Diagnostics Agent Setup GuideValid for Software Provisioning Manager 1.0 SP4

2Customer 2014 SAP AG. All rights reserved.

Diagnostics Agent Setup GuideTypographic Conventions

Typographic Conventions

Type Style Description

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

Textual cross-references to other documents.

Example Emphasized words or expressions.

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

Example 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 anddatabase tools.

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

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

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

Diagnostics Agent Setup GuideDocument History

Customer 2014 SAP AG. All rights reserved. 3

Document History

Version Date Change

1.0 09-APR-2013 Release covering the Diagnostics Agent 7.30 SP3 Standalone Installer.

2.0 15-JUL-2013 Release covering the Software Provisioning Manager 1.0 SP3 Installer.

4.0 28-OCT-2013 Release covering the Software Provisioning Manager 1.0 SP4 Installer.

4.1 04-DEC-2013 Product Availability Matrix (PAM) information added.

4.2 04-DEC-2013 Information on SWPM/70SWPM differences added.

4.3 06-DEC-2013 Sections on Using the SMD Setup Script and SAP Router added. Both sectionswere moved to this Setup Guide from the Diagnostics Agent Trouble ShootingGuide.

4.4 10-DEC-2013 Section on Changing the Log Level added. The section was moved to this SetupGuide from the Diagnostics Agent Trouble Shooting Guide.

4.5 19-DEC-2013 Section on Kernel Details added. The section was moved to this Setup Guide fromSAP Note 1858920.

4.6 08-JAN-2014 Limits improved, see Set Limits on System Resources (Unix only). Documentreference improved, see Information Available on SAP Service Marketplace. Smallfix in section Diagnostics Agent Parameters.

4.7 17-FEB-2014 Renamed section Download the Installation Media into Preparing the InstallationMedia. Added section Patching the Installation Media.


Diagnostics Agent Setup GuideTable of Contents

Table of Contents

1 Introduction ..............................................................................................................................................61.1 About this Document .............................................................................................................................................. 61.2 Before You Start ...................................................................................................................................................... 6

1.2.1 SAP Notes for the Installation ................................................................................................................ 61.2.2 Information Available on SAP Service Marketplace ............................................................................ 71.2.3 Product Availability Matrix (PAM) ......................................................................................................... 81.2.4 SAP NetWeaver Library .......................................................................................................................... 81.2.5 Naming Conventions .............................................................................................................................. 81.2.6 Components for Problem Messages ..................................................................................................... 9

2 Planning .................................................................................................................................................. 102.1 Diagnostics Agent Version to Install .................................................................................................................... 102.2 Differences between SWPM and 70SWPM Installers ........................................................................................ 102.3 Hardware Requirements ........................................................................................................................................ 112.4 Kernel Details .......................................................................................................................................................... 112.5 SAP Kernel Requirements .................................................................................................................................... 122.6 Set DISPLAY (Unix only) ....................................................................................................................................... 122.7 Set Limits on System Resources (Unix only) ...................................................................................................... 13

3 Preparation ............................................................................................................................................. 143.1 Installation Strategy .............................................................................................................................................. 14

3.1.1 System Landscape Directory Registration ......................................................................................... 143.1.2 Direct Solution Manager Connection .................................................................................................. 15

3.2 Preparing the Installation Media .......................................................................................................................... 163.3 Patching the Installation Media ............................................................................................................................ 16

4 Installation.............................................................................................................................................. 184.1 Performing the Installation ................................................................................................................................... 18

4.1.1 Installing on Unix ................................................................................................................................... 184.1.2 Installing on Windows ........................................................................................................................... 194.1.3 Installing on IBM i .................................................................................................................................. 19

4.2 Starting the Installer .............................................................................................................................................. 194.3 Diagnostics Agent Parameters.............................................................................................................................20

4.3.1 Diagnostics Agent Parameters ............................................................................................................204.3.2 Operating System Users on Unix ......................................................................................................... 224.3.3 Operating System Users on Windows ................................................................................................. 224.3.4 Connectivity for the Diagnostics Agent to System Landscape Directory........................................ 234.3.5 Connectivity for the Diagnostics Agent to Solution Manager ........................................................... 24

5 Additional Information........................................................................................................................... 275.1 Performing a Remote Installation ........................................................................................................................ 275.2 Starting SAPinst GUI Separately .......................................................................................................................... 285.3 How to Avoid Automatic Logoff by SAPinst (Windows) ................................................................................... 305.4 Operating System Limits for the Diagnostics Agent ......................................................................................... 30

Diagnostics Agent Setup GuideTable of Contents


5.5 Users and Groups of the Diagnostics Agent ........................................................................................................ 315.6 Directories of the Diagnostics Agent .................................................................................................................. 335.7 Starting and Stopping the Diagnostics Agent .................................................................................................... 34

5.7.1 Using Scripts ......................................................................................................................................... 345.7.2 Using the SAP Management Console ................................................................................................. 355.7.3 Using the SAP Microsoft Management Console on Windows .......................................................... 355.7.4 IBM i ....................................................................................................................................................... 36

5.8 Mass Deployment of the Diagnostics Agent ...................................................................................................... 365.9 Deleting a Diagnostics Agent ............................................................................................................................... 365.10 Using the SMD Setup Script .................................................................................................................................375.11 SAP Router ............................................................................................................................................................ 405.12 Changing the Log Level ......................................................................................................................................... 415.13 Post Installation Steps .......................................................................................................................................... 425.14 Troubleshooting .................................................................................................................................................... 42

5.14.1 Troubleshooting with SAPinst ............................................................................................................. 425.14.2 Troubleshoot the Diagnostics Agent .................................................................................................. 43

6 Appendix ................................................................................................................................................ 446.1 Terms for Included Open Source Software ........................................................................................................ 44


Diagnostics Agent Setup GuideIntroduction

1 Introduction

1.1 About this Document

Use

This guide explains how to install Diagnostics Agents for SAP Solution Manager >= 7.0 EHP1 SP20. The guide ispart of a global installation and configuration procedure which is described in the document How to Use SAPSolution Manager Configuration (SOLMAN_SETUP).

Solution Manager Diagnostics Agent

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

You will need to install a Diagnostics Agent on each server to be managed. Please note that in case the SAP orthird party systems to be managed have been setup using virtual host names, it is essential to install oneDiagnostics Agent instance per virtual host name.

NoteIf a Diagnostics Agent is installed on your Managed System, the folder /usr/sap//SMDA/SMDAgent should exist. By default is set to DAA.

1.2 Before You Start

1.2.1 SAP Notes for the Installation

You must read following SAP Notes before you start the installation. These SAP Notes contain the most recentinformation on the installation, as well as corrections to the installation documentation. Make sure that you havean up-to-date version of each SAP Note, which you can find at: http://service.sap.com/notes

SAP Note Number Title Description

1365123 Diagnostics Agent InstallationStrategy

Information about the adequate software andprocedure to install Diagnostics Agents or Agents On-



SAP Note Number Title Description

the-fly on the Managed Systems.

1833501 Diagnostics Agent InstallerVersions

Information about the different released installerversions. Includes some general, version independentinformation, relevant for all installers.

1858920 Diagnostics Agent installationwith SWPM

Installation and Post-installation steps for SWPM basedinstallers. Attached is the Diagnostics Agent SetupGuide.

1031096 Installing PackageSAPHOSTAGENT

How to install SAP Host Agent.

1.2.2 Information Available on SAP Service Marketplace

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

Documentation

Title Internet Address Description

How to Use SAPSolution ManagerConfiguration(SOLMAN_SETUP)

http://wiki.scn.sap.com/wiki/display/SMSETUP/Home Information on How to UseSAP Solution ManagerConfiguration(SOLMAN_SETUP)

Installation UsingSW Prov. Mgr.

https://service.sap.com/instguides SAP SolutionManager Release 7.1

Installation Guides for SAPSolution Manager 7.1

Introscope https://service.sap.com/diagnostics Installation andConfiguration

Introscope installation guide

Diagnostics AgentTroubleshootingGuide

Diagnostics Agent Troubleshooting Guide Diagnostics AgentTroubleshooting Guide

General Quick Links

Title Internet Address

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

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

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

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



1.2.3 Product Availability Matrix (PAM)

Product Availability Matrix (PAM) information for installing a Diagnostics Agent with Software ProvisioningManager (SWPM) based installers can be found at:

http://service.sap.com/sltoolseto SL Toolseto Software Logistics Toolset 1.0o PAMor

o Product Availability Matrix (PAM)

Then open the provided PDF file and search for Diagnostics Agent.

1.2.3.1 General PAM Information

The central PAM entry page for all SAP products can be found at:

http://service.sap.com/pam

1.2.3.2 Platform Compatibility Matrix for EEM Robots

For a Platform Compatibility Matrix for EEM Robots (that require a Diagnostics Agent installation) refer tofollowing SCN Wiki page:

http://wiki.sdn.sap.com/wiki/x/goCKEw

1.2.4 SAP NetWeaver Library

References to SAP NetWeaver Library documentation in this installation guide always refer to the following onSAP Help Portal:

x SAP systems based on SAP NetWeaver 7.3 including Enhancement Package 1o http://help.sap.com/nw731 Application Help Function-Oriented View English

From there on, either use the navigation, or use the search option to Search within this release.

1.2.5 Naming Conventions

In this documentation, the following naming conventions apply:

Diagnostics Agent Setup Guide Customer 2014 SAP AG. All rights reserved. 9

Terminology

x Managing System is a term for the central entry point of system analysis & monitoring. SAP SolutionManager is the Managing System.

x Managed System is a term for a satellite system (e.g. SAP NetWeaver ABAP or Java System) managed bySAP Solution Manager.

Variables

Variables Description

Diagnostics Agent system ID in uppercase letters

Diagnostics Agent system ID in lowercase letters

Instance Number of a Diagnostics Agent

Operating System name

1.2.6 Components for Problem Messages

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

Components

Components Description

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

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

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

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 Solution Manager Diagnostics

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

XX-PART-WILY Issues related to Introscope


Diagnostics Agent Setup GuidePlanning

2 Planning

This section includes the planning steps for your installation.

2.1 Diagnostics Agent Version to Install

Software Provisioning Manager 1.0 is the recommended successor of the Diagnostics Agent Standalone Installer7.20 and 7.30 SP3.

Before starting the installation you need to identify the Diagnostics Agent version that complies with the version ofthe Solution Manager system. For this, refer to the information attached to SAP Note 1365123.

You also need to check if your operating system release is supported. For this, refer to the Product AvailabilityMatrix (PAM).

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

2.2 Differences between SWPM and 70SWPM Installers

The below table lists the differences between SWPM (SWPM10**.SAR) and 70SWPM (70SWPM10**.SAR). Seealso chapter Preparing the Installation Media.

SWPM 70SWPM

Based on the newest SWPM libraries Based on older SWPM libraries

Brings the newest Diagnostics Agentinstallation feature set, e.g.:

x HTTPS/SSL support

Brings an older Diagnostics Agent installation feature set, e.g.:

x No HTTPS/SSL support

File installationinfo.properties(generated during installation) containssapinst_version property with value:7.30SP3

File installationinfo.properties (generated duringinstallation) contains sapinst_version property with value:70SWPM10SP4

Installation via:

Generic Installation Optionso Diagnostics inSAP Solution Managero Install - DiagnosticsAgent

Installation, start via one of:x {SAP NetWeaver Version}x {SAP Solution Manager Version}x {SAP Business Suite Version}o {SAP Product}

And then select:o Standalone Engineso Diagnostics in SAP Solution Managero Diagnostics Agent Installation



SWPM 70SWPM

Uninstallation via:

Generic Installation Optionso Diagnostics inSAP Solution Managero Uninstall -Diagnostics Agent

Uninstallation, start via one of:x {SAP NetWeaver Version}x {SAP Solution Manager Version}x {SAP Business Suite Version}o {SAP Product}

And then select:

o Software Life-Cycle Optionso Uninstallo Uninstall -System / Standalone Engine / Optional Standalone Unit

2.3 Hardware Requirements

Hardware Requirements

Category Requirement

Minimum disk space Depending on your platform:

x Up to 6 GB for installation media (packed and unpacked versions ofSWPM SAR and KERNEL ZIP files)

x Up to 1.5 GB for the installed Diagnostics Agentx Up to 1 GB of free space in the installation directory

See Performing the Installation [page 18] for more details about installationdirectory location.

Minimum RAM 256 MB

2.4 Kernel Details

Installations are only supported with one of the following kernels (SWPM Kernel version must match your SWPMversion):

x SWPM 1.0 SP4 720 Kernel, unicode, 32-bitx SWPM 1.0 SP4 720 Kernel, unicode, 64-bitx SWPM 1.0 SP4 720_EXT Kernel, unicode, 64-bit

When performing installations as described here, SWPM will ask for a kernel with following label: UC KernelNW731. The mentioned kernels are compatible with the requested one.



2.5 SAP Kernel Requirements

On the Unpack Archives dialog, a statement like the below about SAP HANA is made. When using the SoftwareProvisioning Manager to just install a Diagnostics Agent the Product Availability Matrix (PAM) must be respected.

The Prerequisites Checker may generate warnings for the Operating System version that you are installing on.The Prerequisites Checker may also generate warnings (as shown below for Linux) informing you about thesupported versions for 7.20ext kernels. As long as you comply with the Product Availability Matrix (PAM) you canignore these warnings.

For Diagnostics Agent SAP Kernel details see SAP Note 1707141.

2.6 Set DISPLAY (Unix only)

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

Display

Shell Used Command

Bourne shell (sh) DISPLAY=:0.0export DISPLAY

C shell (csh) setenv DISPLAY :0.0Korn shell (ksh) export DISPLAY=:0.0



2.7 Set Limits on System Resources (Unix only)

CautionOn AIX the limits are described in SAP Note 323816

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

Syntax

In csh execute limitIn sh or ksh execute ulimit -a

Limits

Csh Ksh Properties

cputime time(seconds) unlimited

filesize file(blocks) unlimited

datasize data(kbytes) unlimited

stacksize stack(kbytes) 8192 KB

coredumpsize coredump(blocks) unlimited

descriptors nofiles(descriptors) 8192

memorysize memory(kbytes) unlimited

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

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

In csh execute:limit descriptors 8192In sh or ksh execute:ulimit -n 8192

CautionAn SAP instance does not run with the operating system limits that were set therefore you have to set thelimits for the adm user at the end of the installation. For more details see Operating SystemLimits for the Diagnostics Agent [page 30].


Diagnostics Agent Setup GuidePreparation

3 Preparation

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

3.1 Installation Strategy

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

As of the Diagnostics Agent Standalone Installer 7.20, the below two scenarios are compatible: this means thatyou can choose either both scenarios or only one of them or neither of them.

CautionIf possible we recommend that you choose a direct Solution Manager connection instead of SLDregistration.

x System Landscape Directory Registration: In this scenario, the Diagnostics Agent registers itself into theSLD assigned to the Managed System on which the Diagnostics Agent will be installed. This scenario shouldbe used if Solution Manager is not yet installed. If you select No SLD Destination the Diagnostics Agent is notregistered into the SLD.

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

CautionIf you select neither SLD Registration nor Direct Solution Manager Connection, you will have to configurethe Diagnostics Agent connectivity manually after the installation is finished. For details refer to Using theSMD Setup Script.

3.1.1 System Landscape Directory Registration

The System Landscape Directory (SLD) is designed for registering the systems and installed software of yourlandscape. If you choose to register the Diagnostics Agent in an SLD, it is assigned to the Managing Systemafterwards, using the Agent Administration tools. This allows installing Diagnostics Agents even if the SolutionManager is not available. If the credentials of the J2EE user used to connect the Diagnostics Agent are not valid,the Diagnostics Agent is still available in the SLD and therefore can be assigned to the Managing System later.



CautionThe CIM Model of the SLD must be 1.5.26 or higher. In case you are not able to upgrade your CIM Model,the Diagnostics Agent will be installed but it won't be registered in the SLD. The registration willautomatically be done when the CIM model of the SLD is updated.

3.1.2 Direct Solution Manager Connection

Connect the Diagnostics Agent directly to the Managing System. The following connection types are available:

x P4 Connection via SCS Message Server: the Diagnostics Agent connects to the SCS Message Server and isredirected to one of the dispatcher nodes by the Java EE engine.

RecommendationWe recommend that you select this option

x Direct P4 Connection via Java EE Dispatcher Node: the Diagnostics Agent connects to the selected Java EEDispatcher Node.

x P4 SSL Connection via SCS Message Server: same as P4 Connection via SCS Message Server, but with SSLsupport.

x Direct P4 SSL Connection via Java EE Dispatcher Node: same as Direct P4 Connection via Java EE DispatcherNode, but with SSL support.



3.2 Preparing the Installation Media

For the installation you need the Software Provisioning Manager (SWPM) 1.0 SP4, and a corresponding SWPMKernel.

With regard to SWPM Kernel selection the Product Availability Matrix (PAM) must be respected.

1. Download for your operating system from http://service.sap.com/sltoolseto SoftwareLogistics Toolset 1.0o Software Provisioning Manager 1.0 SP4o download

2. Download the corresponding UNICODE/UC from http://service.sap.com/sltoolseto SoftwareLogistics Toolset 1.0o Software Provisioning Manager 1.0 SP4o corresponding kerneloKernel forinstallation/SWPM

3. Unpack the downloaded archives:

Unpack , e.g. SAPCAR xvf SWPM.SAR -R

CautionOn Unix operating systems you must make sure that all users have read permissions for the directorywhere you want to unpack the installer.

Unzip to e.g. If required, you can download the latest version of SAPCAR from http://service.sap.com/swdco SupportPackages and PatchesoA Z Indexo So SAPCAR.

3.3 Patching the Installation Media

CautionYou must only patch your kernel media, if you are explicitly instructed to do so through a SAP Note orthrough a Customer Message.

SAP support personnel will instruct you on the version of the file that you must use for patching.

SAR-File

As of Diagnostics Agent 7.4 there are operating system independent DIAGAGT74.SAR Download Object'savailable on the SAP Service Marketplace. These SAR-files are the successor of the operating system specificstandalone 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 SAP kernelmedia. The SAR-files are named like:

DIAGAGTSP_-.SAR(e.g. DIAGAGT74SP00_0-123456.SAR)

Downloading

Diagnostics Agent Setup Guide Customer 2014 SAP AG. All rights reserved. 17

The SAR-files can be downloaded from:

http://service.sap.com/swdco Support Packages and Patcheso A Z Indexo So SAP SOLUTIONMANAGERo SAP SOLUTION MANAGER 7.1o Entry by Componento Agents for managed systemsoDIAGNOSTICS AGENT 7.4o # OS independent

Patching

Once you have downloaded and unpacked the software provisioning manager 1.0 archive and the kernel mediathat you have selected, you must replace the SAPDIAGNOSTICSAGENT.SAR file on the unpacked kernel mediawith the DIAGAGT74.SAR file that you have downloaded.The SAPDIAGNOSTICSAGENT.SAR file can be found at the following location on the unpacked kernel media:Windows:

:\\DBINDEP\SAPDIAGNOSTICSAGENT.SARLinux/Unix:

//DBINDEP/SAPDIAGNOSTICSAGENT.SAR


Diagnostics Agent Setup GuideInstallation

4 Installation

The following sections provide detailed information and instructions for the installation and setup of a DiagnosticsAgent.

4.1 Performing the Installation

This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running on the samehost and on the local display. If necessary, you can:

x Perform a remote installation with SAPinst [page 27], where SAPinst GUI is running on a separate host fromSAPinst and the GUI server

x Start SAPinst GUI separately [page 28]

4.1.1 Installing on Unix

1. Log on to your host as user root.

2. Mount the installation media.

Note

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

3. Change to the directory:

cd /Run the command:

./sapinstThe SAPinst GUI starts and the Welcome screen is displayed.

CautionSAPinst creates the installation directory sapinst_instdir directly below the temporary directory.SAPinst finds the temporary directory by checking the value of the TEMP, TMP, or TMPDIR environmentvariable. If no value is set for these variables, SAPinst uses/tmp as default installation directory.If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIRto the required directory before you start SAPinst.



CautionMake sure that the temporary directory has the permissions 1777

4.1.2 Installing 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 directoryand run the command:

:\\sapinst.exe

The Welcome screen is displayed, and the installation begins.

CautionSAPinst creates the installation directory sapinst_instdir, where it keeps its log files, and which islocated directly in the %ProgramFiles% directory. If SAPinst is not able to create sapinst_instdirthere, it tries to create sapinst_instdir in the directory defined by the environment variable TEMP.

4.1.3 Installing on IBM i

Do all the preparations and start the installer as described in the Installing SAP Systems Based on SAP NetWeaver7.1 and Higher - Using Software Provisioning Manager 1.0 installation guide.

4.2 Starting the Installer

Process Flow

1. Make sure that you have read the chapter "Preparation " [page 14] and have identified the Diagnostics AgentVersion to Install [page 10] and defined the Installation Strategy [page 14]

2. Start SAPinst

3. For SWPM, on the Welcome screen, choose Generic Installation Optionso Diagnostics in SAP SolutionManagero Install - Diagnostics Agent. For 70SWPM refer to Differences between SWPM and 70SWPMInstallers.

4. To start the installation, choose Next .



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

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

NoteFor more information about the input parameters, place the cursor on the relevant field and press F1 inSAPinst.

At the end of the Define Parameters phase you can still change any of these parameters thanks to the Revisebutton on Parameter Summary screen.

NoteIf you change a parameter with the Revise button on the Parameter Summary screen, SAPinst takesyou to the screen where you can change the parameter. Depending on the changes, SAPinst might guideyou through other screens with default parameters that it has so far processed.

4.3 Diagnostics Agent Parameters

The sections below lists the parameters that you need to specify before installing your Diagnostics Agent:

x Diagnostics Agent Parametersx Operating System Users on Unixx Operating System Users on Windowsx Connectivity for the Diagnostics Agent to System Landscape Directoryx Connectivity for the Diagnostics Agent to Solution Manager

4.3.1 Diagnostics Agent Parameters

Parameters Description

System ID ofthe Diagnostics Agent

SAPinst sets the system ID of a Diagnostics Agent () to DAA by default.If a Diagnostics Agent 7.30 is already installed on this machine, SAPinst sets to its SID.If DAA is already used by another product that is not a Diagnostics Agent, SAPinstassigns another default system ID: starting from DA1 to DA9. You can overwrite thedefault system ID as required.

Make sure that the :




x Either does not yet exist on the local installation host, or does already exist butexclusively contains some Diagnostics Agent installation in the exact sameversion

x Consists of exactly three alphanumeric charactersx Contains only uppercase lettersx Has a letter for the first characterx 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 INTKEY LOG LPT MON NIX NOT NUL OFF OMS PRN RAW ROW SAP SET SGASHG SID SQL SYS TMP UID USR VAR

CautionAn error message pops up if the SAP System Name is not a dedicatedDiagnostics Agent SAP System or if the System ID is already used.

NoteDiagnostics Agents installed on different logical hosts (but same physicalor virtual host) can use the same .

Instance Number of theDiagnostics Agent

Technical identifier for internal processes for the Diagnostics Agent, consisting of atwo-digit number from 98 to 00.The instance number is set automatically to the next free and valid instancenumber that has not yet been assigned to the SAP system.

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

The directory of the Diagnostics Agent instance is calledSMDA.

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

You can change the Logical Host name if you plan to manage systems running on alogical host. This scenario lets the Diagnostics Agent take part in a switchoverenvironment.

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

Installation Drive

On Windows only

Base directory for the Diagnostics Agent.

You cannot select the installation drive if:

x The saploc share already exists (a SAP System or a Diagnostics Agent hasalready been installed on this machine) SAPinst sets the installation drivewhere the saploc share points to.




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

4.3.2Operating System Users on Unix


adm User adm is dedicated to the Diagnostics Agent installation and has theauthorization to manage the agent.

If you did not create user adm manually before the installation, SAPinstcreates it automatically on every application server instance host during theinstallation. In this case, make sure that the user password you choose meets therequirements of your operating system.

Make sure that the user ID and group ID of adm are unique and the sameon each application server instance host.

sapadm The Host Agent user sapadm is used for central monitoring services.This user is created only if the Host Agent is automatically installed during theinstallation of the Diagnostics Agent. In this case, make sure that the userpassword you choose meets the requirements of your operating system.

4.3.3Operating System Users on Windows


Operating System User:adm

The Diagnostics Agent user adm is used to manage the DiagnosticsAgent. It is created on the primary application server instance host and onevery additional application server instance host.

For security reasons, SAPinst creates this user by default as a local userwithout being a member of the local Administrators group. If required, youcan change this user to become a domain user on the Parameter Summaryscreen.

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

Operating System User:SAPService

This is the Windows account to run the Diagnostics Agent.

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

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




This user is created only if the Host Agent is automatically installed during theinstallation of the Diagnostics Agent.

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

Windows Domain Windows Domain for the Diagnostics Agent Operating System Usersadm and SAPService.

CautionSAP strongly recommends creating the Diagnostics Agent users aslocal users.

4.3.4Connectivity for the Diagnostics Agent to System LandscapeDirectory

You identified your Installation Strategy [page 14].


SLD Destination You can choose between the following options:

x Register in existing central SLDSAPinst only prompts you for the parameters listed below in this table if youselect this option.

CautionYou cannot specify a SAP Router route for the Solution Manager systemconnection if you chose to register the Diagnostics Agent into SLD.

x No SLD Destination

NoteIf the Diagnostics Agent is going to be installed automatically with aprimary/additional application server instance and if you choose No SLDDestination, you have to configure the connection for the DiagnosticsAgent manually after the installation with SAPinst has finished.

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




SLD.

See Connectivity for the Diagnostics Agent to Solution Manager [page 24] for moredetails about Solution Manager connection parameters.

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

Caution

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

SLD HTTP Port (SLDHTTPS Port if Use HTTPSselected)

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

For HTTP the following convention applies: 500(HTTPS: 501).

SLD Data Supplier Userand password

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

4.3.5Connectivity for the Diagnostics Agent to Solution Manager

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

You identified your Installation Strategy [page 14].

CautionAs of release 7.20 you can choose to connect the Diagnostics Agent directly to the Solution Managersystem even if you registered it in the SLD during the previous step.


Connection of theDiagnostics Agent to SAPSolution Manager

You can choose between the following options:

x Configure standard connection: the Diagnostics Agent is connected to theSolution Manager system.

SAPinst only prompts you for the Connection Type listed below in this table ifyou select this option.

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

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




standard connection.

Connection Type You can choose between the already mentioned options:

x P4 Connection via SCS Message Serverx Direct P4 Connection via Java EE Dispatcher Node

If you select Use SSL connectivity you can choose between:

x P4 SSL Connection via SCS Message Serverx Direct P4 SSL Connection via Java EE Dispatcher Node

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

CautionThe 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 ofthe Java Stack of your SAP Solution Manager system.

x HTTP SCS Message Server Port is 81xx (where xx is the Central Services(SCS) instance number).

x HTTP SCS SSL Message Server Port is 43xxx or 44xxx (where xx is theCentral Services (SCS) instance number).

x Dispatcher P4 Port is 5xx04 (where xx is the central instance number).x Dispatcher P4 SSL Port is 5xx06 (where xx is the central instance

number).

User and password We recommend that you use the SMD_ADMIN user created during the SMD SetupWizard step in the Managing System.

Caution

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

Then all the steps executed during setup phase are tested. In case of an error amessage pops up. It is not recommended to begin the installation as long as thecheck fails.

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

The route string contains a substring for each SAP router without the target serversuch as: /H/host/S/service/W/passx /H/ indicates the host namex /S/ is used for specifying the service (port); it is an optional entry, the default

value is 3299x /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 Solution Manager can besuch as: /H/hostname.sap.com/S/3199

CautionYou cannot specify a route if you chose to register the Diagnostics Agentinto SLD during the previous step.

Diagnostics Agent Setup GuideAdditional Information


5 Additional Information

This section provides additional information about the Diagnostics Agent, post-installation steps andtroubleshooting tasks.

x Performing a Remote Installation [page 27]x Starting SAPinst GUI Separately [page 28]x How to Avoid Automatic Logoff by SAPinst (Windows) [page 30]x Operating System Limits for the Diagnostics Agent [page 30]x Directories of the Diagnostics Agent [page 33]x Starting and Stopping the Diagnostics Agent [page 34]x Mass Deployment of the Diagnostics Agent (Unattended mode) [page 36]x Deleting a Diagnostics Agent [page 36]x Post Installation [page 42]x Troubleshoot SAPinst and the Diagnostics Agent [page 42]

5.1 Performing a Remote Installation

Use this procedure to install your Diagnostics Agent on a remote host. In this case, SAPinst and the GUI server runon the remote host, and SAPinst GUI runs on the local host. The local host is the host from which you control theinstallation with SAPinst GUI.

If your security policy requires that the person performing the installation by running SAPinst GUI on the localhost is not allowed to know root (Unix) or administrator (Windows) credentials on the remote host, you canspecify another operating system user for authentication purposes. You do this using theSAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. Youhave 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 other2. Log on as user root.3. Mount the installation media

4. Change to the directory of the sapinst executable by entering the following command:cd /Start SAPinst by executing the following command:

./sapinst -noguiSAPinst now starts and waits for the connection to SAPinst GUI. You see the following at the commandprompt:



guiengine: no GUI connected; waiting for a connection on host , port to continue with the installation.

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

Windows

1. Both computers are in the same network and can "ping" each other2. Log on to your host as a user who is member of a local Administrators group of the machine involved.3. Make the installation media available on the installation host.

4. Change to the directory of the sapinst executable by entering the following command:cd :\\Enter the following commands:

sapinst.exe -noguiSAPinst now starts and waits for the connection to SAPinst GUI. You see the following at the commandprompt:

guiengine: no GUI connected; waiting for a connection on host , port to continue with the installation

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

5.2 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately.

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

x You closed SAPinst GUI using File o Exit from SAPinst menu while SAPinst is still running.x You want to perform a remote installation, where SAPinst GUI runs on a different host from SAPinst. For

more information, see Performing a Remote Installation [page 27].

Unix

1. Log on as user root.2. Make SAPinst software available on the host on which you want to start SAPinst GUI.

3. Change to the directory of the sapinst executable by entering the following command:cd /Start SAPinst GUI by executing./sapinstgui with the relevant command line parameters:o If you want to perform a remote installation, execute the following command:

./sapinstgui -host -port



Note

is the name of the remote host; is the port the GUI server uses tocommunicate with the GUI client (21212 by default).

o If you closed SAPinst GUI using File o Exit from SAPinst menu and want to reconnect to SAPinst,o If you are performing a local installation with SAPinst and SAPinst GUI running on the same host:

./sapinstgui -standalone -port o If you are performing a remote installation with SAPinst and SAPinst GUI running on different hosts:

./sapinstgui -host -port

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

Windows

1. Log on as a member of the local Administrators group.2. Make the installation media available on the installation host.

3. Change to the directory of the sapinst executable:cd :\\Start SAPinst GUI by executing sapinstgui.exe with the relevant command line parameters:o If you want to perform a remote installation, execute the following command:

sapinstgui.exe -host -port

Note is the name of the remote host; is the port the GUI server uses tocommunicate with the GUI client (21212 by default).

o If you closed SAPinst GUI using File o Exit from SAPinst menu and want to reconnect to SAPinst,o If you are performing a local installation with SAPinst and SAPinst GUI running on the same host:

sapinstgui.exe -standalone -port o If you are performing a remote installation with SAPinst and SAPinst GUI running on different hosts:

sapinstgui.exe -host -port

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



5.3 How to Avoid Automatic Logoff by SAPinst (Windows)

When you install the SAP system with SAPinst, the SAPinst installation tool checks whether the user account usedfor the installation has the required privileges and authorization.

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

x Act as part of the operating systemx Adjust memory quotas for a processx Replace a process level token

If the user account does not have these rights assigned, SAPinst assigns them and automatically logs the accountoff to activate them. To avoid SAPinst logging the account off, you can set these rights manually before you startthe installation.

Procedure

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

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

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

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

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

The selected user appears in the box below.

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

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

5.4 Operating System Limits for the Diagnostics Agent

Certain operating systems limit operating system resources (such as the maximum number of open files) toostrictly in the default settings; as a result, some SAP instance types (such as the Diagnostics Agent instances) donot work correctly. Therefore, the operating system settings must be adjusted.

Depending on how the Diagnostics Agent is started, limits have to be set either for the specific adm useror in such a way that they also take effect for the sapstartsrv that was started either as a daemon at the time ofthe operating system boot process or using a Web service client (sapcontrol, SAP MMC, SAP MC, and so on).



Procedure

If sapstartsrv was started as adm in a shell running commands likex /usr/sap/sapservicesx sapstartsrv pf=.x sapcontrol nr -function StartService (this command simply extract the relevant

command line from /usr/sap/services and executes it)x startsap (startsap tries to start sapstartsrv by itself if not yet running)you need to set the limits in the shell before doing so.

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

NoteOn AIX the mechanisms are described in SAP Note 323816

To set the limits for all sapstartsrv daemons that were started at OS boot via sapinit script, you can set thelimits in /usr/sap/sapservices.limit.descriptors=limit.stacksize=

NotePlease follow SAP Note 1437105

To take into account the new limits, you have to restart sapstartsrv and therefore to stop the agent (stopsap)and kill the process: kill .Indeed restarting sapstartsrv using the following command is not enough since the above command just sendsa restart request to sapstartsrv.sapcontrol -nr -function RestartServicesapstartsrv restarts itself so the new sapstartsrv inherits the limits of the actual running one.At the end, restart the agent (startsap) and the service is restarted as well.

5.5 Users and Groups of the Diagnostics Agent

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

If you do not want SAPinst to create operating systems users and groups automatically, you can optionally createthem before the installation. This might be the case if you use central user management such as NetworkInformation System (NIS).



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

x You start SAPinst and choose Software Life-Cycle Tasks Additional Preparation TasksOperating SystemUsers and Groups.

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

CautionThe administration user sapadm is created only if the Host Agent is automatically installed during theinstallation of the Diagnostics Agent. It is used for central monitoring services. On AIX, follow thedirections under section 4 Installation in SAP Note 1704753.

CautionIf SAPinst creates this user, make sure that the user password you choose meets the requirements ofyour operating system. The password:

- Must be 8 to 9 characters long- May contain the following characters: @, _, #, $, a-z, A-Z, 0-9- Must contain at least one letter (a-z, A-Z)- Must contain at least one digit (0-9), but must not begin with a digit- Must not contain \ (backslash) and " (double quote)

Users and Groups on Unix

SAPinst chooses available operating system user IDs and group IDs. If you want to specify them or to change theHome directory, you have to create the OS Users and groups before the installation.

User Primary Group Additional Group Description

adm sapsys sapinst Diagnostics Agent administratorsapadm sapsys sapinst Host Agent administrator

Users and Groups on Windows

User Local Installation Domain Installation

adm SAP__LocalAdminSAP_LocalAdminUsers

SAP__GlobalAdminSAP_LocalAdminDomain Users

SAPService SAP__LocalAdminSAP_LocalAdminUsers

SAP__GlobalAdminSAP_LocalAdminDomain Users



User Local Installation Domain Installation

Performance Monitor Users Performance Monitor UsersSapadm SAP_SAP_LocalAdmin

SAP_LocalAdminUsers

SAP_SAP_GlobalAdminSAP_LocalAdminDomain Users

5.6 Directories of the Diagnostics Agent

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

/usr/sap/ contains the following subdirectories:x SYS

o exe - Contains executable kernel programso global - Contains globally shared datao profile - Contains the profiles of the Diagnostics Agent instance

x SMDA - Instance directory of the Diagnostics Agent instance. It contains the instance-specific data of the Diagnostics Agent. It contains the following subdirectories:

o script - Contains the smdsetup scripto SMDAgent - Contains the Diagnostics Agent software and properties files

o exe - Contains executable kernel programs that are replicated from SYS/exe host every time the instanceis started.

The SAP copy program sapcpe compares the binaries in the directory and the binaries inthe SMDA/exe directory. If the binaries in the exe directory are elder than those inthe directory, sapcpe replaces them with the newer version.

o work - Contains log files



5.7 Starting and Stopping the Diagnostics Agent

5.7.1 Using Scripts

The Diagnostics Agent is started at the end of the installation. You can start and stop the Diagnostics Agent byrunning sapcontrol.

CautionYou can only start or stop the Diagnostics Agent separately. It is not started or stopped automatically withthe SAP system.

Prerequisites

You have logged on to the host as user adm.



Procedure (all platforms)

To manage the Diagnostics Agent, enter this command:

sapcontrol -prot PIPE -nr -function

Where is one of: Start, Stop, StartSystem, StopSystem

5.7.2 Using the SAP Management Console

The Diagnostics Agent is started at the end of the installation. You can start and stop the Diagnostics Agent usingthe SAP Management Console (SAP MC).

Prerequisites

The SAP MC prerequisites are documented in the SAP NetWeaver Library. You will need to search for Startingthe SAP Management Console.

Procedure

Starting/Stopping Diagnostics Agent(s)

1. Log on to the host as user adm2. Start a Web browser and enter the following URL http://:513

This starts the SAP MC Java applet.

NoteIf your browser displays a security warning message, choose the option that indicates that you trust theapplet.

3. Choose Start. The SAP Management Console appears.

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

5.7.3Using the SAP Microsoft Management Console on Windows

The Diagnostics Agent is started at the end of the installation. You can start and stop all your Diagnostics Agentsusing the SAP Management Console (SAP MMC) on Windows.



Procedure


1. Start the SAP MMC on the SAP system host by choosing StartoAll Programso SAP Management Console.2. Right-click the Diagnostics Agent node and choose Start or Stop.

5.7.4IBM i

The Diagnostics Agent is installed like a standard SAP instance.

Procedure


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

5.8 Mass Deployment of the Diagnostics Agent

If you want to deploy the Diagnostics Agent on multiple systems you can use the Diagnostics Agent installer inunattended mode. This means you record all input parameters for one installation scenario, which you can thenreuse for further installations.

Note

For more details, please refer to SAP Note 1486330: Mass Deployment of SAP Diagnostics Agent 7.30.This SAP Note describes the additional steps you have to perform for an unattended installation.

5.9 Deleting a Diagnostics Agent

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

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

CautionYou must delete a Diagnostics Agent instance only using SAPinst; otherwise you might have problemswith further installations on this host.



Prerequisites

Unix

You are logged on as user root.

Windows

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

CautionDo not use the user adm to delete the Diagnostics Agent.

Procedure

1. Starting the Installer [page 19].

2. For SWPM, on the Welcome screen, choose Generic Installation Optionso Diagnostics in SAP SolutionManagero Uninstall - Diagnostics Agent. For 70SWPM refer to Differences between SWPM and 70SWPMInstallers.

3. On the General SAP System Parameters screen, enter the location of the profile directory of the DiagnosticsAgent that you want to uninstall:

/usr/sap//SYS/profile4. Follow the instructions in the SAPinst input dialogs.

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

5.10 Using the SMD Setup Script

The smdsetup script allows to update configuration parameters for the Diagnostics Agent. Some options of thescript only exist since Solution Manager 7.0 EHP1.

Note that this script is automatically patched at the time the Diagnostics Agent connects to the Solution Managerserver. This feature has been implemented since Solution Manager 7.0 SP15.

To determine the options supported by the smdsetup script, just execute the command smdsetup.sh orsmdsetup.bat, without any parameters.

Example of smdsetup 7.01 or higher output:

>> Help Information----------------------



Script which allows to update some diagnostics agent configuration.

smdsetup

List of actions:

* smdsetup secstorej2ee user:"" pwd:""

* smdsetup secstoresld user:"" pwd:""

* smdsetup sldconf hostname:"" port:"" [optional user:"" pwd:""]

* smdsetup managingconf hostname:"sapms://" port:"" [optional user:"" pwd:"" servername:""]

* smdsetup managingconf hostname:"" port:"" [optional user:"" pwd:"" servername:""]

Script Location

In 7.0 SR3 and 7.0x the smdsetup script is located at:/usr/sap//J/script

In 7.1x and higher the smdsetup script is located at:/usr/sap//SMDA/script

Script Options

Action Description Availability

managingconf Changes the Solution Manager System (also known asmanaging system) used by the Diagnostics Agent toconnect to. Specify the host and port.

SAP Solution Manager7.0 SP14 or higher

sldconf Changes the SLD server where the Agent will perform itsregistration. Provide the SLD host and port.

secstorej2ee Changes only the J2EE user used to connect to theSolution Manager system. (restart after the changes).

secstoresld Changes only the J2EE user used to register the Agent inthe configured SLD system. (restart after the changes).

changeservername Change the server name of the agent. (restart after thechanges).

addsaprouter



Action Description Availability

saprouterpass Full implementation in SAP Solution Manager 7.10. Alsosee the section on SAP Router.

SAP Solution Manager7.01 or higher

removesaprouter

supportlogs Execute some agent checks and generate a zip with allagent logs (including an agent check report).

SAP Solution Manager7.0 SP17 patch 3 or higher

managingconf syntax

The command updates the connection settings to the Solution Manager system:

x To connect the agent via J2EE Message server http port:N.B.:

- Do not confuse the message server HTTP port with the message server internal port (which is like 36xx)

- Do not forget to prefix the hostname with sapms://smdsetup managingconf hostname:sapms://myhost.domain.corp port:8101

x (In rare circumstances) To connect the agent with a P4 direct connection:smdsetup managingconf hostname:myhost port:53004

Optionally, you can add the j2ee user information in the command line to update also the agent secure store:

smdsetup managingconf hostname:sapms://myhost.domain.corp port:8101user:SMD_ADMIN pwd:init1234

sldconf syntax

The command updates the connection settings to the SLD system of the agent registration:

x Register/connect the Agent to the SLD system (http port of SLD java stack):smdsetup sldconf hostname:mySLDhost.domain.corp port:50000

Optionally, you can add the SLD user information in the command line to update the agent secure store:

smdsetup sldconf hostname:mySLDhost.domain.corp port:50000 user:slddsuserpwd:xxxxx

secstorej2ee syntax

The command updates the credentials of the connection to the Solution Manager system:

x Update the agent secstore file:smdsetup secstorej2ee user:SMD_ADMIN pwd:init1234



secstoresld syntax

The command updates the credentials of the connection to the SLD system:

x Update the agent secstore file:smdsetup secstoresld user:slddsuser pwd:xxxxxx

changeservername syntax

The command updates the servername attribute of the agent:

x Update the agent configuration file:smdsetup changeservername servername:"myservername"

supportlogs syntax

This command retrieves all agent log files and executes basic agent pre-requisite checks like:

x JDK version checkx JVM parameters checkx hostname resolution checkx TCP port checkx P4 protocol checkx message server connectivity check

Execute the command as follows:

smdsetup supportlogs

The command generates a ZIP file at the following location:/usr/sap//SMDA/SMDAgent/supportLogs_.zip

The generated ZIP file contains:x Check results (AgentSupportToolReport.log in SMDAgent/log folder)x Diagnostics Agent log filesx Diagnostics Agent profilex SAPinst logsx work directory contentx All properties files contained in the SMDAgent folder

5.11 SAP Router

The Diagnostics Agent can be connected to the Managing System via a SAP Router. The 7.30 standaloneinstallers and SWPM based installers support configuring the Diagnostics Agent connection via a SAP Router.

Alternatively the SAP route can be maintained after the Diagnostics Agent installation using the smdsetup script.(See Using the SMD Setup Script).



This feature is supported as of SAP Solution Manager 7.10. The automatic activities Introscope Host Adapterand Introscope Byte Code Adapter Installation in SAP Solution Manager scenario Managed SystemConfiguration will also use the provided SAP route.

With SAP Solution Manager 7.01 this type of connectivity is not supported. You may create a support ticket oncomponent SV-SMG-DIA-SRV-AGT and request an evaluation of alternative setup possibilities.

5.12Changing the Log Level

The main Diagnostics Agent log files are stored in folder/usr/sap//SMDA/SMDAgent/log and they are organized as follows:

Filename DefaultSettings

DefaultLevel

Description

SMDSystem.log 10 files of 1 MB INFO This file reports all informationabout the agent framework (likeconnection to Managing System),SLD report, agelets loading andpatch sequence.

SMDAgentApplication.log 10 files of 1 MB WARNING This file reports all informationabout the agelets used by RCAapplications, Setup Wizards andWily IS setup.

P4.log 10 files of 1 MB NONE This file reports all informationabout agent connections with theManaging System.

In case the Diagnostic Agent is connected to the SAP Solution Manager system, the procedure to change the loglevel is:

1. Go to the agent administration UI2. Select the tab Agent Log Viewer3. Select the relevant agent from the dropdown list4. Configure the required level

In case the Diagnostics Agent is not connected to the SAP Solution Manager System, the procedure to change thelog level is:

1. At OS level login as adm user2. Stop the agent3. Go to folder /usr/sap//SMDA/SMDAgent/configuration4. Open file log-configuration.xml5. Adapt the level for the respective filenames and indicated lines, according the below given table

a. Attribute: effective-severityb. Possible values: ALL, DEBUG, INFO, WARNING, ERROR, NONE

6. Save the file and restart the agent



Filename

SMDSystem.log

SMDAgentApplication.log

P4.log

5.13Post Installation Steps

If you want to change configuration parameters such as the connectivity type, the Diagnostics Agent credentials,the Managing System the Diagnostics Agent is connected to, refer to section Using the SMD Setup Script.

5.14Troubleshooting

5.14.1 Troubleshooting with SAPinst

If an error occurs, SAPinst:

x Stops the installationx Displays a dialog informing you about the error

Procedure

1. To view the log file, choose View Logs .2. If an error occurs during the dialog or processing phase, do either of the following:

x Try to solve the problemx Abort the installation with Exitx Continue the installation by choosing Retry .

3. Check the log files of SAPinst in the installation directory sapinst_instdir SAPinst normally creates thisinstallation directory directly below the temporary directory. SAPinst finds the temporary directory bychecking the value of the environment variables TEMP, TMP, or TMPDIR.



Note

If no value is set for these variables, SAPinst uses /tmp/sapinst_instdir as default installationdirectory on Unix platforms and %ProgramFiles%\sapinst_instdir on Windows platforms. If youwant to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to therequired directory.

5.14.2 Troubleshoot the Diagnostics Agent

Check the Diagnostics Agent Troubleshooting Guide for more details.


Diagnostics Agent Setup GuideAppendix

6 Appendix

6.1 Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Please note that forthese third party products the following special terms and conditions shall apply.

1. This software was developed using ANTLR.

2. gSOAP

Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C)2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, ORPROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHERIN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAYOUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP AktiengesellschaftSystems, Applications, Products in Data Processing Neurottstrasse 16 69190 Walldorf, Germany (hereinafter:SAP) and you (hereinafter: Customer)

a) Subject Matter of the Agreement

A) SAP grants Customer a non-exclusive, non-transferrable, royalty-free license to use the STLport.org C++library (STLport) and its documentation without fee.

B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectualproperty laws, and to all of the terms and conditions of this Agreement.

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

D) Customer shall maintain the following copyright and permissions notices on STLport sources and itsdocumentation unchanged:

Copyright 2001 SAP AG

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

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

o The following copyright notices are retained when present, and conditions provided in accompanyingpermission notices are met:

Coypright 1994 Hewlett-Packard

Company

Copyright 1996,97 Silicon Graphics

Computer Systems Inc.

Copyright 1997 Moscow Center for



SPARC Technology.

Copyright 1999,2000 Boris Fomitchev

Copyright 2001 SAP AG

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Companymakes no representations about the suitability of this software for any purpose.

It is provided as is without express or implied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is herebygranted without fee, provided that the above copyright notice appear in all copies and that both that copyrightnotice and this permission notice appear in supporting documentation. Silicon Graphics makes norepresentations about the suitability of this software for any purpose. It is provided as is without express orimplied warranty.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. Moscow Center for SPARCmakes no representations about the suitability of this software for any purpose. It is provided as is withoutexpress or implied warranty.

Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material isprovided "as is", with absolutely no warranty expressed or implied.

Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee,provided the above notices are retained on all copies.

Permission to modify the code and to distribute modified code is granted, provided the above notices areretained, and a notice that the code was modified is included with the above copyright notice.

Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes ishereby granted without fee, provided that the above copyright notice appear in all copies and that both thatcopyright notice and this permission notice appear in supporting documentation. SAP makes no representationsabout the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forthin the License Agreement distributed with this copy.

SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications.

b) Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenanceof the STLport therefore shall be not included.

All other services shall be charged according to the rates for services quoted in the SAP List of Prices andConditions and shall be subject to a separate contract.

c) Exclusion of warranty

As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that theSTLport is error-free, without material defects or suitable for a specific application under third-party rights.Technical data, sales brochures, advertising text and quality descriptions produced by SAP do not indicate anyassurance of particular attributes.

d) Limited Liability

A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this(i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or(iii) if based on the failure of a guaranteed attribute.

B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerialemployees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall



depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, dueto the circumstances known to it at that point in time representing a typical transfer of the software.

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

D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstancesexceed EUR 5,000.

E) The Customer shall take adequate measures for the protection of data and programs, in particular by makingbackup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and itsrecovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided byobserving this obligation.

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

4. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. Forinformation on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, seeSAP Note 854621.

www.sap.com/contactsap

2014 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.Some software products marketed by SAP AG and its distributorscontain proprietary software components of other softwarevendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System ads, System i5, Systemp, System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS,S/390, OS/390, OS/400, AS/400, S/390 Parallel EnterpriseServer, PowerVM, Power Architecture, POWER6+, POWER6,POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix aretrademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. andother countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are eithertrademarks or registered trademarks of Adobe SystemsIncorporated 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 theOpen Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarksof Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C, World Wide Web Consortium, MassachusettsInstitute 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 byNetscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge,ByDesign, SAP Business ByDesign, and other SAP products andservices mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and inseveral other countries all over the world. All other product andservice names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informationalpurposes only. National product specifications may vary.These materials are subject to change without notice. Thesematerials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation orwarranty of any kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in theexpress warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constitutingan additional warranty.

SWPM10SP4 Diag Agent Setup Guide

Documents

Transcript of SWPM10SP4 Diag Agent Setup Guide