Installation and Setup GuideDiagnostics Agent: Linux and UNIXUsing Software Provisioning Manager 1.0

Target Audience Technology consultants System administrators

CUSTOMERDocument version: 5.1 2014-04-10

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/70 CUSTOMER 2014-04-10

Typographic Conventions

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

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

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

Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the

documentationhttp://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 Web123456 Hyperlink to an SAP Note, for example, SAP Note 123456Example 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 works

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

2014-04-10 CUSTOMER 3/70

Document History

The following table provides an overview of the most important document changes.Version Date Description1.0 2013-04-09 Release covering the Diagnostics Agent 7.30 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 12] added.4.2 2013-12-04 Section on Differences between SWPM and 70SWPM Installers [page 14] added.4.3 2013-12-06 Sections on Using the SMD Setup Script [page 51] and SAP Router [page 62] 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 55] 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 15] 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 63]. Small fix in section Diagnostics Agent System ID and Instance Number [page 18].

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 15] Patching the Installation Media [page 31] Direct SAP Solution Manager Connection [page 17] SAP Solution Manager Connectivity Parameters [page 21] Using the SMD Setup Script [page 51] Starting and Stopping SAP System Instances Using the SAP Management Console [page

56]

4/70 CUSTOMER 2014-04-10

Table of Contents

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 Service Pack specific Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 SAP Notes for the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.4 Components for Problem Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.5 Accessing the SAP Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2 Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.1 Planning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.2 Installation Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Product Availability Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.5 Running the Prerequisites Check in Standalone Mode (Optional) . . . . . . . . . . 122.6 Differences between SWPM and 70SWPM Installers . . . . . . . . . . . . . . . . . . . . . 142.7 Kernel for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.8 JVM for the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.9 Connection Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.10 Direct SAP Solution Manager Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.11 System Landscape Directory Registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.12 Basic Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.12.1 General Installation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.12.2 Diagnostics Agent System ID and Instance Number . . . . . . . . . . . . . . . . . . . . 182.12.3 Operating System Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.12.4 Diagnostics Agent SLD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.12.5 SAP Solution Manager Connectivity Parameters . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.1 Preparation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.2 Creating Operating System Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . 253.3 SAP Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.4 Using Logical Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2014-04-10 CUSTOMER 5/70

3.4.1 Using Virtual Host Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.5 Preparing the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6 Patching the Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313.7 Diagnostics Agent Download Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 4 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.1 Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.2 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.3 Additional Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.3.1 Useful Information About the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.3.2 Interrupted Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.3.3 Performing a Remote Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.3.4 Starting the Installer GUI Separately . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.3.5 Running the Installer in Accessibility Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.3.6 Troubleshooting with the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Chapter 5 Post-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.1 Post-Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.2 Ensuring User Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.3 Complying with SAP Solution Manager Security Guidelines . . . . . . . . . . . . . . 48

Chapter 6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496.1 Installation Guidance for Experienced Administrators . . . . . . . . . . . . . . . . . . 496.2 Installing the Diagnostics Agent Optionally with the SAP System . . . . . . . . . . 506.3 Mass Deployment of the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . 516.4 Using the SMD Setup Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516.5 Changing the Log Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556.6 Starting and Stopping SAP System Instances Using the SAP Management

Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566.7 Starting and Stopping the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . 586.8 Deleting an SAP System or Single Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . 586.9 Setting Operating System Limits for the Diagnostics Agent . . . . . . . . . . . . . . . 606.10 Troubleshooting the Diagnostics Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616.11 Installer and Diagnostics Agent Version Information . . . . . . . . . . . . . . . . . . . 616.12 SAP Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63A.1 Online Information from SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

6/70 CUSTOMER 2014-04-10

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

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. You can find the latest version attached to SAP Note 1858920: Diagnostics Agent installation with SWPM.

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

1 Introduction

2014-04-10 CUSTOMER 7/70

VariablesVariables Description Diagnostics Agent system ID in uppercase letters. 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 18].

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.

1.1 New FeaturesThe table below provides an overview of the new features.Make sure that you also read the release notes at http://service.sap.com/releasenotes.Area DescriptionSoftware 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 29] which is part of the Software Logistics Toolset (SL Toolset for short). This way, you automatically get the latest SAPinst version including latest fixes in the tool and supported processes. For more information about software provisioning manager as well as products and releases supported by it, see SAP Note 1680045.As a result, SAPinst has been renamed to software provisioning manager (installer for short) in this documentation.However, the term SAPinst is still used in: Texts and screen elements in the software provisioning manager GUI Naming of executables, for example sapinst Naming of command line parameters, for example

SAPINST_USE_HOSTNAME Operating system user groups, for example additional group sapinst

1.2 Service Pack specific DocumentationThis 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 14]

1 Introduction1.1 New Features

8/70 CUSTOMER 2014-04-10

Kernel for the Diagnostics Agent [page 15] JVM for the Diagnostics Agent [page 16] Patching the Installation Media [page 31] Diagnostics Agent Download Paths [page 32] Installing the Diagnostics Agent Optionally with the SAP System [page 50]

1.3 SAP Notes for the InstallationYou 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 http://service.sap.com/notes.SAP Notes for the InstallationSAP Note Number Title Description1680045 Release Note for Software Provisioning

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

1704753 Inst.Systems based on NetWeaver 7.1 and higher: UNIX

UNIX-specific information about the installation for SAP systems and corrections to this documentation

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 SWPM based installers

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

1075118 SAP on HP-UX: FAQ This SAP Note contains information that is specific to the SAP system installation on HP-UX

171356 Linux only: SAP software on Linux: Essential comments

This SAP Note contains Linux-specific information about the SAP system installation

1.4 Components for Problem MessagesIn case of problems, contact SAP Support by creating a message on the following components:Components DescriptionSV-SMG-INS Issues related to Installation, Configuration and Upgrade of SAP Solution Manager

1 Introduction1.3 SAP Notes for the Installation

2014-04-10 CUSTOMER 9/70

Components DescriptionSV-SMG-INS-AGT Issues related to Diagnostics Agent InstallationBC-OP-AIX OS specific issues related to Diagnostics Agent Installations on IBM AIXBC-OP-AS4 OS specific issues related to Diagnostics Agent Installations on IBM iBC-OP-LNX OS specific issues related to Diagnostics Agent Installations on LinuxBC-OP-NT OS specific issues related to Diagnostics Agent Installations on WindowsBC-OP-SUN OS specific issues related to Diagnostics Agent Installations on SolarisBC-OP-S390 OS specific issues related to Diagnostics Agent Installations on z/OSSV-SMG-DIA Issues related to SAP Solution Manager DiagnosticsSV-SMG-DIA-SRV-AGT Issues related to Diagnostics AgentBC-CCM-HAG Issues related to SAP Host AgentXX-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: SAP systems based on SAP NetWeaver 7.3:

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

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

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

1 Introduction1.5 Accessing the SAP Library

10/70 CUSTOMER 2014-04-10

2 Planning

2.1 Planning ChecklistBefore 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

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

Virtual Host Names [page 29].3. Select your Installation Strategy [page 11].4. Check the Product Availability Matrix [page 12] and ensure that your operating system release is

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

version you want to use.8. Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Consider Running the Prerequisites Check in Standalone Mode (Optional) [page 12].End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

9. Select a Kernel for the Diagnostics Agent [page 15].10. Understand the situation with regard to the JVM for the Diagnostics Agent [page 16].11. Decide on the Connection Selection [page 16] for the Diagnostics Agent.12. Collect the Basic Installation Parameters [page 17].13. Continue with the Preparation [page 25] section.

2.2 Installation StrategyFollow 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].

2 Planning2.1 Planning Checklist

2014-04-10 CUSTOMER 11/70

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 18] and SAP Directories [page 27].

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:

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

http://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: http://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: http://wiki.scn.sap.com/wiki/x/goCKEw

2.4 Hardware RequirementsDiagnostics Agent Hardware RequirementsCategory RequirementMinimum 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

2 Planning2.3 Product Availability Matrix

12/70 CUSTOMER 2014-04-10

as you comply with the Diagnostics Agent Product Availability Matrix [page 12] 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 both the prerequisites check and the requirements tables for reference.

Procedure1. 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 fromhttp://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

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

ResultThe 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 Planning2.5 Running the Prerequisites Check in Standalone Mode (Optional)

2014-04-10 CUSTOMER 13/70

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).Both versions offer the Diagnostics Agent installation option via the 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 29].

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

SWPM 70SWPMBased on the newest SWPM libraries. Based on older SWPM libraries.Brings the newest Diagnostics Agent installation feature set, e.g.: HTTPS/SSL support Username/password are optional when connecting

against SAP Solution Manager 7.10 SP10 or higher releases

Brings an older Diagnostics Agent installation feature set.

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

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

Offers installation option Install - Diagnostics Agent with 741 kernel, see Kernel for the Diagnostics Agent [page 15].

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.Marker DescriptionFeature 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 Planning2.6 Differences between SWPM and 70SWPM Installers

14/70 CUSTOMER 2014-04-10

2.7 Kernel for the Diagnostics AgentInstallations are supported with one of the below listed kernels. The Product Availability Matrix (PAM) [page 12] 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 SP5.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 / SWPMThe 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-bitInstall Diagnostics Agent with 741 kernel

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

The installation option Install - Diagnostics Agent with 741 kernel will ask for kernel media in the following way: UC Kernel NW740 SR1The below listed kernel version is supported: 7.41 kernel, Unicode, 64-bitKernel 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. We also recommend you to check SAP Note 1680045 Release Note for Software Provisioning Manager 1.0, for any last minute updates.

2 Planning2.7 Kernel for the Diagnostics Agent

2014-04-10 CUSTOMER 15/70

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 (depending on the kind of SAP NetWeaver (based) systems you normally install)2. 7.213. 7.20 EXT4. 7.20

2.8 JVM for the Diagnostics AgentOnly valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |Diagnostics 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 15].End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

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

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

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.Refer to Using the SMD Setup Script [page 51] for details.

2 Planning2.8 JVM for the Diagnostics Agent

16/70 CUSTOMER 2014-04-10

2.10 Direct SAP Solution Manager ConnectionCAUTIONFor productive usage the Diagnostics Agent must be connected to the SCS message server of the SAP Solution Manager system. The connection via a Java EE dispatcher node should only be used for testing and debugging purposes.

Connect the Diagnostics Agent directly to the SAP Solution Manager system. The below connection types are available.See also SAP Solution Manager Connectivity Parameters [page 21]. 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. Direct P4 connection via Java EE dispatcher node: the Diagnostics Agent connects to the selected Java EE

dispatcher node. Direct P4 SSL connection via Java EE dispatcher node: the same as Direct P4 connection via Java EE dispatcher node,

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

2.12 Basic Installation Parameters2.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 50].

2 Planning2.10 Direct SAP Solution Manager Connection

2014-04-10 CUSTOMER 17/70

General Installation ParametersParameters DescriptionHost 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 29] and Kernel for the Diagnostics Agent [page 15] for guidance.

2.12.2 Diagnostics Agent System ID and Instance NumberDiagnostics Agent System ID and Instance NumberParameters DescriptionDiagnostics 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 Contains only uppercase letters Has a letter for the first character Does not include any of the following, which are reserved IDs:

ADD ADM ALL AMD AND ANY ARE ASC AUX AVG BIN BIT CDC COM CON DBA DTD END EPS EXE FOR GET GID IBM INT KEY LIB LOG LPT MAP MAX MEM MIG MIN MON NIX NOT NUL OFF OLD OMS OUT PAD PRN RAW REF ROW SAP SET SGA SHG SID SQL SUM SYS TMP TOP TRC UID USE USR VAR

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.

2 Planning2.12 Basic Installation Parameters

18/70 CUSTOMER 2014-04-10

Parameters DescriptionThe 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 (not mounted) /usr/sap/ directories.The value is the number assigned to the instance.Only valid for: AIX |

CAUTIONIf you are using NIM Service Handler (NIMSH), do not use 01 or 02 for the instance number. The installer uses the instance number for the internal message server port 39. The NIM client daemon uses reserved ports 3901 and 3902.

End of: AIX |Only valid for: HP-UX |

CAUTIONDo not use 75 for the instance number because this number is already used by the operating system. For more information, see SAP Note 29972.

End of: HP-UX |Only valid for: HP-UX |

CAUTIONDo not use 02 as the instance number because this number is used to determine the port number for report RSLGCOLL, which is 14 by default. However, port 1402 is already used by the OS process rstlisten. If you still decide to use 02 as the instance number, the instance fails to start during the installation process. You then have to manually change the port number for report RSLGCOLL to continue with the installation. For more information, see Running the Installer [page 33].

End of: HP-UX |

2.12.3 Operating System UsersOperating System UsersParameters DescriptionSAP 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.If you did not create user adm manually before the installation, the installer creates it automatically on every application server instance host

2 Planning2.12 Basic Installation Parameters

2014-04-10 CUSTOMER 19/70

Parameters Descriptionduring the installation. Make sure that the user ID and group ID of adm are unique and the same on each application server instance host.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 (a-z, A-Z)

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: Creating Operating System Users and Groups [page 25] Ensuring User Security [page 47]

2.12.4 Diagnostics Agent SLD ParametersRECOMMENDATIONPerforming an SLD registration is no longer recommended, see Connection Selection [page 16] and System Landscape Directory Registration [page 17].

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.

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

Register in existing central SLDChoose this option to register the Diagnostics Agent you are installing in an SLD by specifying the SLD connection parameters listed below.

2 Planning2.12 Basic Installation Parameters

20/70 CUSTOMER 2014-04-10

Parameters DescriptionCAUTIONYou 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 select this option, the installer does not prompt you for further SLD connection parameters.You may configure the SLD destination for the Diagnostics Agent via the smdsetup script after the installation has finished.Refer to Using the SMD Setup Script [page 51] for details.

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

NOTEThe Use HTTPS feature is 71X SWPM ONLY, see also Differences between SWPM and 70SWPM Installers [page 14].

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.

2.12.5 SAP Solution Manager Connectivity ParametersRECOMMENDATIONSpecifying a direct SAP Solution Manager connection is recommended, see Connection Selection [page 16] and Direct SAP Solution Manager Connection [page 17].

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.

2 Planning2.12 Basic Installation Parameters

2014-04-10 CUSTOMER 21/70

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.

SAP Solution Manager Connectivity ParametersParameters DescriptionConnection of the Diagnostics Agent to SAP Solution Manager

You can choose between the following connection options: Configure standard connection: the Diagnostics Agent is connected to the SAP Solution

Manager system.The installer only prompts you for the connection type listed below in this table if you select this option.

Do not configure connection: the Diagnostics Agent is not connected to the SAP Solution Manager system.If you select this option, the installer does not prompt you for further 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.Refer to Using the SMD Setup Script [page 51] for details.

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

NOTEThe Use SSL connectivity feature is 71X SWPM ONLY, see also Differences between SWPM and 70SWPM Installers [page 14].

Connection Type for the Diagnostics Agent

CAUTIONFor productive usage the Diagnostics Agent must be connected to the SCS message server of the SAP Solution Manager system. The connection via a Java EE dispatcher node should only be used for testing and debugging purposes.

You can choose between the following options: P4 connection via SCS message server Direct P4 connection via Java EE dispatcher nodeIf you select the check box Use SSL connectivity you can choose between the following options: P4 SSL connection via SCS message server Direct P4 SSL connection via Java EE dispatcher node

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 443 or 444, where is the instance

number of the SAP Solution Manager Java Central Services (SCS).

2 Planning2.12 Basic Installation Parameters

22/70 CUSTOMER 2014-04-10

Parameters Description Dispatcher P4 Port is 504, where is the instance number of the SAP Solution

Manager Java central instance. Dispatcher P4 SSL Port is 506, where is the instance number of the SAP

Solution Manager Java central instance.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.The route string contains a substring for each SAP router without the target server such as: /H/host/S/service/W/pass /H/ indicates the host name /S/ is used for specifying the service (port); it is an optional entry, the default value

is 3299 /W/ indicates the password for the connection between the predecessor and

successor on the route and is also optional (default is "", no password)

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.

2 Planning2.12 Basic Installation Parameters

2014-04-10 CUSTOMER 23/70

This page is left blank for documents that are printed on both sides.

3 Preparation

3.1 Preparation ChecklistBefore starting the installation you must perform the following preparation steps:1. Prepare the Installation Media [page 29].2. Only valid for: AIX;HP-UX;Linux;Solaris |

If applicable, Create Operating System Users and Groups [page 25].End of: AIX;HP-UX;Linux;Solaris |

3. Continue with the Installation [page 33] section.

3.2 Creating Operating System Users and GroupsDuring the installation, the installer checks all required accounts (users, groups) and services on the local machine. The installer checks whether the required users and groups already exist. If not, it creates new users and groups as necessary.If you do not want the installer to create operating systems users, groups, and services automatically, you can optionally create them before the installation is started. This might be the case if you use central user management such as Network Information System (NIS).The installer checks if the required services are available on the host and creates them if necessary. See the log messages about the service entries and adapt the network-wide (NIS) entries accordingly.The installer checks the NIS users, groups, and services using NIS commands. However, the installer does not change NIS configurations.If you want to use global accounts that are configured on a separate host, you can do this in one of the following ways: You start the installer and choose Generic Installation Options Preparation Operating

System Users and Groups . For more information, see Running the Installer [page 33]. You create operating system users and groups manually. Check the settings for these operating

system users.

Constraints Only valid for: AIX |

You have to set the limits for operating system users as described in SAP Note 323816.End of: AIX |

Only valid for: HP-UX;Linux;Solaris |You have to set the limits for operating system users as follows:

3 Preparation3.1 Preparation Checklist

2014-04-10 CUSTOMER 25/70

Using csh shell, the output of command limit needs to be as follows:Output Propertiescputime unlimitedfilesize unlimiteddatasize unlimitedstacksize 8192 KBcoredumpsize unlimiteddescriptors 8192memorysize unlimited

Using sh or ksh shell, the output of command ulimit -a needs to be as follows:Output Propertiestime(seconds) unlimitedfile(blocks) unlimiteddata(kbytes) unlimitedstack(kbytes) 8192coredump(blocks) unlimitednofiles(descriptors) 8192memory(KBytes) unlimited

End of: HP-UX;Linux;Solaris | All users must have identical environment settings. Any change to the environment such as

variables, or paths is at your own responsibility. Do not delete any shell initialization scripts in the home directory of the operating system users.

This applies even if you do not intend to use the shells that these scripts are for. If operating system users already exist, make sure that they are assigned to group sapinst. If you create operating system users manually or use already existing operating system users, make

sure that the home directory for each of these users is not the root directory ( / ) . Make sure that the home directory of user adm is not critical for recursive changes on

permissions.When operating system users are created by the installer, the permissions on the home directories of these users are changed recursively. This can cause unpredictable errors if you define a critical home directory.For example, the home directory must not be / or /usr/sap.

Only valid for: HP-UX |To prevent terminal query errors in the adm environment, comment out the line eval `tset -s -Q -m ':?hp' in the /etc/skel/.login script. For more information, see SAP Note 1038842.End of: HP-UX |

Operating System Users and GroupsThe installer chooses available operating system user IDs and group IDs.

3 Preparation3.2 Creating Operating System Users and Groups

26/70 CUSTOMER 2014-04-10

If you want to specify them or to change the home directory, you have to create the users and groups before the installation.User and Groups of the Diagnostics AgentUser Primary Group Additional Group Commentadm sapsys sapinst Administrator for the Diagnostics Agent.

User and Groups of the SAP Host AgentUser Primary Group Additional Group Commentsapadm sapsys SAP Host Agent administrator

NOTEIf sapadm does not exist, it is created during the SAP Host Agent installation using /bin/false shell.Make sure that /bin/false can be used as a login shell.Only valid for: AIX |Add /bin/false to the list of valid login shells (attribute shells) in /etc/security/login.cfg.End of: AIX |

Groups and Members of the Diagnostics Agent UserGroups Memberssapsys admsapinst adm

Groups and Members of the SAP Host Agent UserGroups Memberssapsys sapadmsapinst sapadm

3.3 SAP DirectoriesDirectories of the Diagnostics AgentFor the Diagnostics Agent the installer creates the following types of directories: Logically shared directories Local directoriesDetails are shown in the following figure.

3 Preparation3.3 SAP Directories

2014-04-10 CUSTOMER 27/70

Figure 1: Directory Structure for the Diagnostics Agent

The Diagnostics Agent directory /usr/sap/ contains the following subdirectories: SYS, which is a logically shared directory SMDA, which is a local directory

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

Logically Shared DirectoriesThe logically shared directory SYS contains the following subdirectories: exe

Contains executable kernel programs global

Contains globally shared data profile

Contains the profiles of the Diagnostics Agent instanceLocal DirectoriesThe (local) instance directory of the Diagnostics Agent instance is called SMDA. It contains the instance-specific data of the Diagnostics Agent and has following subdirectories: script

Contains the smdsetup script SMDAgent

Contains the Diagnostics Agent software and properties files

3 Preparation3.3 SAP Directories

28/70 CUSTOMER 2014-04-10

exeContains executable kernel programs

workContains log files

3.4 Using Logical Host NamesSAP 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 29] 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 NamesCAUTIONMake 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.

PrerequisitesMake sure that the virtual host name can be correctly resolved in your Domain Name System (DNS) setup.

ProcedureProceed as described in SAP Note 962955.

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. For details see the description at the end of this section.

3 Preparation3.4 Using Logical Host Names

2014-04-10 CUSTOMER 29/70

For more information about the required media, see SAP Note 1680045.

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

Installation Installation MediaDiagnostics Agent Software provisioning manager 1.0 archive

SWPM10SP_.SAR (recommended) or 70SWPM10SP_.SAR

NOTEThis section explains the Differences between SWPM and 70SWPM Installers [page 14].

UC Kernel (folder K__U_) where U means Unicode.

NOTEFor information about supported kernel versions see Kernel for the Diagnostics Agent [page 15].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:

http://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:

3 Preparation3.5 Preparing the Installation Media

30/70 CUSTOMER 2014-04-10

SAPCAR -xvf /.SAR -R NOTEMake sure that all users have read permissions for the directory where you want to unpack the installer.

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.

CAUTIONIf you copy the media to disk, make sure that the paths to the destination location of the copied media do not contain any blanks.

3.6 Patching the Installation MediaCAUTIONYou 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 a customer message. 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:

http://service.sap.com/swdc Support Packages and Patches A - Z Index S SAP SOLUTION MANAGERSAP 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 61].

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.

3 Preparation3.6 Patching the Installation Media

2014-04-10 CUSTOMER 31/70

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

Download Paths via SL Toolset PagesSL Toolset download path for installer archive: http://service.sap.com/sltoolset Software Logistics Toolset 1.0 System Provisioning Software Provisioning Manager 1.0 SP download .

SL Toolset download path for kernel archive: http://service.sap.com/sltoolset Software Logistics Toolset 1.0 System Provisioning Software Provisioning Manager 1.0 SP 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: http://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: http://service.sap.com/swdc

Installations and Upgrades A-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. 720 and 741 kernels) can be downloaded via: http://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 12] Differences between SWPM and 70SWPM Installers [page 14] Kernel for the Diagnostics Agent [page 15]

3 Preparation3.7 Diagnostics Agent Download Paths

32/70 CUSTOMER 2014-04-10

4 Installation

4.1 Installation ChecklistIn order to execute the installation you have to perform the following steps:1. Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Follow the instructions in Running the Installer [page 33].End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

2. For alternative installation scenarios refer to Additional Information About the Installer [page 36].3. Continue with the Post-Installation [page 47] section.

4.2 Running the InstallerCAUTIONThe 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 12] 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.If you need to see the installation on a remote display, we recommend that you perform a remote installation [page 40], where the installer GUI is running on a separate host from the installer.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809.

Prerequisites We recommend that you use the csh shell for the installation with the installer. If you want to use

another shell, make sure that you have read SAP Note 202227.The installer uses csh scripts during the installation to obtain the environment for user adm. This is also true if user adm already exists from an earlier SAP system

4 Installation4.1 Installation Checklist

2014-04-10 CUSTOMER 33/70

installation, and the shell of this user is not csh. Before you start the installer, execute the following command as user adm to make sure that the csh scripts are up-to-date:/bin/csh -c "source /home/adm/.cshrc;env"

Make sure that your operating system does not delete the contents of the temporary directory /tmp or the contents of the directories to which the variables TEMP, TMP, or TMPDIR point, for example by using a crontab entry.Make sure that the temporary directory has the permissions 777.

Make sure that you have 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. If you cannot provide 300 MB free space in the temporary directory, you can set one of the environment variables TEMP, TMP, or TMPDIR to another directory with 300 MB free space for the installer executables.You can set values for the TEMP, TMP, or TMPDIR environment variable to an alternative installation directory as described in section Useful Information About the Installer [page 36].

Make sure that your DISPLAY environment variable is set to :0.0, where is the host on which you want to display the installer GUI.You can set values for the DISPLAY environment variables as follows:Shell Used CommandBourne shell (sh) DISPLAY=:0.0

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

Make sure that umask is set to 022 for user root.As user root, enter the following command: umask 022

Make sure that you have checked the following values for user root: In csh, execute limit

Output Propertiescputime unlimitedfilesize unlimiteddatasize unlimitedstacksize 8192 KBcoredumpsize unlimiteddescriptors 8192memorysize unlimited

In sh or ksh execute ulimit -aOutput Propertiestime(seconds) unlimitedfile(blocks) unlimiteddata(kbytes) unlimitedstack(kbytes) 8192

4 Installation4.2 Running the Installer

34/70 CUSTOMER 2014-04-10

Output Propertiescoredump(blocks) unlimitednofiles(descriptors) 8192memory(KBytes) unlimited

If your parameters have values lower than the settings recommended above, change these values accordingly.

EXAMPLEIf you have to change the value for descriptors to 8192, proceed as follows: In csh execute:

limit descriptors 8192 In sh or ksh execute:

ulimit -n 8192 Make sure that you have defined the most important SAP system parameters as described in Basic

Installation Parameters [page 17] before you start the installation. Check that your installation host meets the requirements for the installation options that you

want to install.Only valid for: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |For more information, see Running the Prerequisite Checker [page 12].End of: AIX;HP-UX;IBM i5/OS;Linux;Solaris;Windows |

Procedure1. Log on to the installation host as user root.

CAUTIONDo not use an existing adm user.CAUTIONMake sure that the root user has not set any environment variables for a different SAP system or database.

2. Start the installer from the directory to which you unpacked the software provisioning manager 1.0 archive by executing the following command:/sapinst

NOTEIf you want to use a logical host name, start the installer with the SAPINST_USE_HOSTNAME property as follows:/sapinst SAPINST_USE_HOSTNAME=For more information, see Using Logical Host Names [page 29].CAUTIONMake sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

3. On the Welcome screen, choose the required installation option:

4 Installation4.2 Running the Installer

2014-04-10 CUSTOMER 35/70

Choose your product and then choose Generic Installation Options Diagnostics in SAP Solution Manager Install - Diagnostics Agent

4. Choose Next.5. 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.

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

7. If required, delete directories with the name sapinst_exe.xxxxxx.xxxx after the installer has finished. Sometimes these remain in the temporary directory.

NOTEIf there are errors with the extraction process of the installer, you can find the log file dev_selfex.out in the temporary directory.

8. We recommend that you delete all files in the directory /.sdtgui/.9. 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] 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 directly below the temporary

directory. The installer finds the temporary directory by checking the value of the TEMP, TMP, or

4 Installation4.3 Additional Information About the Installer

36/70 CUSTOMER 2014-04-10

TMPDIR environment variable. If no value is set for these variables, the installer uses /tmp as default installation directory.If you want to use an alternative installation directory, set the environment variable TEMP, TMP, or TMPDIR to the required directory before you start the installer.Shell Used CommandBourne shell (sh) TEMP=

export TEMPC shell (csh) setenv TEMP Korn shell (ksh) export TEMP=

CAUTIONMake sure that the installation directory is not mounted with NFS, otherwise there might be problems when the Java Virtual Machine is started.

For each option, the installer creates a subdirectory located in the sapinst_instdir directory. The installer extracts itself to the temporary directory. These executables are deleted again 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.

During the installation, 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 the sapinst executable with the following command line parameter:GUISERVER_DIALOG_PORT=

To see a list of all available installer properties, start the installer as described above with the option -p:./sapinst -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 Cancel in the installer GUI menu.NOTEIf you need to terminate the installer, you can do this by pressing Ctrl + C .

If you want to install an SAP system in unattended mode, see SAP Note 950619.

4 Installation4.3 Additional Information About the Installer

2014-04-10 CUSTOMER 37/70

4.3.2 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 Cancel in the SAPinst menu.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:Option DefinitionRetry 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.

NOTEYou can also terminate the installer by choosing Ctrl + C but we do not recommend this because it kills the process immediately.

ProcedureThis 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 local UNIX host as user root.

CAUTIONMake sure that the root user has not set any environment variables for a different SAP system or database.

2. Make sure that the installation media are still available on the installation host.

4 Installation4.3 Additional Information About the Installer

38/70 CUSTOMER 2014-04-10

For more information, see Preparing the Installation Media [page 29].RECOMMENDATIONMake installation media locally available. For example, if you use Network File System (NFS), reading from media mounted with NFS might fail.

Only valid for: Solaris |NOTEIf you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |3. Restart the installer from the directory to which you unpacked the software provisioning manager

1.0 archive by executing the following command:/sapinst

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:

Alternative BehaviorRun 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 backup 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 Installation4.3 Additional Information About the Installer

2014-04-10 CUSTOMER 39/70

4.3.3 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 root credentials on the remote host, you can specify another operating system user for authentication purposes. You do this using the SAPINST_REMOTE_ACCESS_USER parameter when starting the sapinst executable from the command line. You have to confirm that the user is a trusted one. For more information, see SAP Note 1745524.Alternatively you can use an X server for Microsoft Windows or other remote desktop tools for remote access to the installer GUI on Windows workstations. For more information, see SAP Note 1170809.Only valid for: Linux;Windows |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].End of: Linux;Windows |

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

Installer [page 33]. 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

Make sure that the sapinst executable on the remote host and the sapinstgui executable 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.

Procedure1. Log on to your remote host as user root.

CAUTIONMake sure that the root user has not set any environment variables for a different SAP system or database.

2. Make the installation media available on the remote host.For more information, see Preparing the Installation Media [page 29].

4 Installation4.3 Additional Information About the Installer

40/70 CUSTOMER 2014-04-10

RECOMMENDATIONMake installation media locally available. For example, reading from media mounted with Network File System (NFS) might fail.

Only valid for: Solaris |NOTEIf you mount installation media, make sure that you do this with option nomaplcase.

End of: Solaris |3. Check the version of the sapinst executable by entering the following command:

/sapinst -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]).

4. Start the installer from the directory to which you unpacked the software provisioning manager 1.0 archive by executing the following command:/sapinst -nogui

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

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

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

4.3.4 Starting the Installer GUI SeparatelyYou use this procedure to start the installer GUI separately. You might need to start the installer GUI separately in the following cases: You closed the installer GUI using File Exit from the installer menu while the installer is still

running. You want to perform a remote installation, where the installer GUI runs on a different host from

the installer. For more information, see Performing a Remote Installation [page 40]. You want to run the installer in accessibility mode. In this case, you have to start the installer GUI

separately on a Windows host as described below with the additional command line parameter -accessible.For more information, see Running the Installer in Accessibility Mode [page 44].

4 Installation4.3 Additional Information About the Installer

2014-04-10 CUSTOMER 41/70

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 33].NOTEIf you want to run the installer on a Windows host, make sure that you meet the prerequisites for the installer listed in the relevant Windows guide.

Make sure that the sapinst executable on the remote host and the sapinstgui executable 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].

ProcedureNOTEIf 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 Cancel 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 29].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

where is the name of the remote host, and is the port the GUI server uses to communicate with the GUI client (21212 by default).

4 Installation4.3 Additional Information About the Installer

42/70 CUSTOMER 2014-04-10

If you closed the installer GUI using File Exit 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

where is the port the GUI server uses to communicate with the GUI client (21212 by default).

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

where is the name of the remote host, and is the port the GUI server uses to communicate with the GUI client (21212 by default).

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

where is the name of the remote host, and is the port the GUI server uses to communicate with the GUI client (21212 by default).

If you closed the installer GUI using File Exit and want to reconnect to the installer, proceed as follows:

4 Installation4.3 Additional Information About the Installer

2014-04-10 CUSTOMER 43/70

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

where is the port the GUI server uses to communicate with the GUI client (21212 by default).

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

where is the name of the remote host, and is the port the GUI server uses to communicate with the GUI client (21212 by default).

The installer GUI starts and connects to the installer.

4.3.5 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. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

Custom font setting:This feature is derived from the Windows display properties. Therefore, to enable this feature, perform a remote installation with the installer GUI running on a Windows host.

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.

4 Installation4.3 Additional Information About the Installer

44/70 CUSTOMER 2014-04-10

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 perform a remote installation as follows:1. Start the installer on the remote host by executing the following command from the command

line as described in Performing a Remote Installation [page 40]:./sapinst -nogui

2. Start the installer GUI on a local Windows host by executing the following command from the command line as described in Starting the Installer GUI Separately [page 41]:sapinstgui.exe -accessible -host -port

4.3.6 Troubleshooting with the InstallerThis section tells you how to proceed when errors occur during the installation with the installer.If an error occurs, the installer: Stops the installation Displays a dialog informing you about the errorProcedure1. Check SAP Note 1548438 for known installer issues.2. To view the log file, choose View Logs.3. If an error occurs during the dialog or processing phase, do one of the following:

Try to solve the problem. Abort the installation with Exit.

For more information, see Interrupted Installation [page 38]. Continue the installation by choosing Retry.

4. Check the log and trace files of the GUI server and the installer GUI in the directory /.sdtgui/ for errors. If the GUI server or the installer GUI do not start, check the file sdtstart.err in the current

directory. If the installer GUI aborts during the installation without an error message, restart the installer

GUI as described in Starting the Installer GUI Separately [page 41]. If you use an X Server for Microsoft Windows or other remote desktop tools for the Remote

Access of the installer GUI on Windows Workstations and you experience display problems such as missing repaints or refreshes, contact your X Server vendor. The vendor can give you

4 Installation4.3 Additional Information About the Installer

2014-04-10 CUSTOMER 45/70

information about whether this X Server supports Java Swing-based GUIs and also tell you about further requirements and restrictions. See also SAP Note 1170809.

5. If you cannot resolve the problem, create a customer message using component BC-INS.For more information about using subcomponents of BC-INS, see SAP Note 1669327.

4 Installation4.3 Additional Information About the Installer

46/70 CUSTOMER 2014-04-10

5 Post-Installation

5.1 Post-Installation ChecklistAfter the installation of the Diagnostics Agent and before the Diagnostics Agent goes into production, you have to perform the following steps:1. Check