701SR1 Diag Agent Setup Guide

SAP Solution Manager 7.0

End-to-End Root Cause Analysis

Diagnostics Agent 7.0 EHP1 SR1 -

Setup Guide

Document Version 4.0 – August 2010

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted

in any form or for any purpose without the express

permission of SAP AG. The information contained herein

may be changed without prior notice.

Some software products marketed by SAP AG and its

distributors contain proprietary software components of other

software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,

WebSphere, Netfinity, Tivoli, and Informix are trademarks

or registered trademarks of IBM Corporation in the United

States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks

of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or

registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems,

Inc., used under license for technology invented and

implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP

NetWeaver, and other SAP products and services mentioned

herein as well as their respective logos are trademarks or

registered trademarks of SAP AG in Germany and in several

other countries all over the world. All other product and

service names mentioned are the trademarks of their

respective companies. Data contained in this document

serves informational purposes only. National product

specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes

only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with

respect to the materials. The only warranties for SAP

Group products and services are those that are set forth in the

express warranty statements accompanying such products

and services, if any. Nothing herein should be construed as

constituting an additional warranty.

Disclaimer

Some components of this product are based on Java™. Any

code change in these components may cause unpredictable

and severe malfunctions and is therefore expressively

prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only

to be used by SAP’s Support Services and may not be

modified or altered in any way.

Documentation on SAP Service Marketplace

You can find this documentation at

service.sap.com/instguidesNW04

SAP AG

Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20

www.sap.com

T yp o g r a p h i c C o n ve n t i o n s

Type Style Represents

Example Text

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

Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

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

Example

text

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example

text

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

<Example

text>

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

EXAMPLE

TEXT

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

I c o ns

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Contents August 2010

Setup Guide Diagnostics Agent 7.0 EHP1 SR1 I

Contents

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

1.1 Planning checklist .................................................................................................... 1 1.2 New Features ............................................................................................................ 1 1.3 Required Documentation ......................................................................................... 2

1.3.1 Information in the SAP Service Marketplace .................................................. 2 1.3.2 SAP Notes....................................................................................................... 2

1.4 Components for Problem Messages ...................................................................... 3 1.5 Terminology and variables ...................................................................................... 3 1.6 Installation planning ................................................................................................. 3

2 PREPARATION ................................................................................................................... 4

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

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

2.4 Download Installation DVDs from SAP Service Marketplace............................... 5 2.5 Hardware Requirements .......................................................................................... 8 2.6 Install the Java Development Kit ............................................................................ 8 2.7 Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 only).............................................................................................................. 9 2.8 Set DISPLAY (UNIX only) ......................................................................................... 9 2.9 Set limits on system resource (UNIX only) ............................................................ 9

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

3.1 Installation Checklist .............................................................................................. 11 3.2 Running SAPinst .................................................................................................... 11

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

3.3 Install the Diagnostics Agent Using SAPinst ...................................................... 12 3.4 Diagnostics Agent Parameters ............................................................................. 12

3.4.1 Diagnostics Agent parameters: SID, Number, Host, drive (Windows only) 13 3.4.2 Diagnostics Agent parameters: JDK, drive (Windows only), Server name 14 3.4.3 Operation System Users (<smdsid>adm) .................................................... 14

3.4.4 Connectivity for the Diagnostics Agent to System Landscape Directory (SLD) 15 3.4.5 Connectivity for the Diagnostics Agent to Solution Manager ........................ 16 3.4.6 IBM DB2 UDB for iSeries > Kernel Load Parameters .................................. 17

4 ADDITIONAL INFORMATION .......................................................................................... 18

4.1 Performing a Remote installation with SAPinst .................................................. 18 4.2 Starting SAPinst GUI Separately ........................................................................... 19 4.3 Starting and Stopping the Diagnostics Agent ..................................................... 20 4.4 Mass Deployment of the Diagnostics Agent ....................................................... 21

Contents August 2010

Setup Guide Diagnostics Agent 7.0 EHP1 SR1 II

4.5 Deleting a Diagnostics Agent ................................................................................ 22 4.6 Post installation steps............................................................................................ 22

4.6.1 Change the Managing System of the Diagnostics Agent ............................. 23 4.6.2 Change the Diagnostics Agent credentials ................................................... 23 4.6.3 Change the Diagnostics Agent connectivity type.......................................... 24

4.7 Troubleshoot ........................................................................................................... 25 4.7.1 Troubleshooting with SAPinst ....................................................................... 25 4.7.2 Diagnostics Agent does not start .................................................................. 26

4.8 Installation of OS Collector SAPOSCOL .............................................................. 27

SAP Solution Manager - End-to-End Root Cause Analysis August 2010

Setup Guide Diagnostics Agent 7.0 EHP1 SR1 1

1 Introduction This guide explains how to install Diagnostics Agents for SAP Solution Manager 7.0 - End to End - Root Cause Analysis. This guide is part of a global installation and configuration which is described in the document Root Cause Analysis Installation and Upgrade with SOLMAN SETUP Guide.

Solution Manager Diagnostics Agent

The Solution Manager Diagnostics Agent (Diagnostics Agent) is the remote component of the E2E Root Cause Analysis. It allows to perform a connection between SAP Solution Manager as the managing system and the managed system(s) and then to gather information from the managed systems and reports them to the Solution Manager system.

You will need to install a Diagnostics Agent on each server (virtual hostname) to be managed. Please note that in case the SAP or Third Party Systems - to be managed - have been setup using virtual hostnames, it is essential to install one Diagnostics Agent instance per virtual hostname.

Since Support Release 3 (7.00 SR3), the Diagnostics Agent is deployed at the end of every installation requiring the SAP Installation Master Support Release 3 DVD: SAP NetWeaver 7.0 SR3, SAP Business Suite SR3 (SAP ERP, SAP CRM, SAP SCM, SAP SRM) based on AS Java. If the Diagnostics Agent is installed on your Managed System, the following folders should exist:

* /usr/sap/SMD/J<00-98>/SMDAgent or

* /usr/sap/DA<A-Z>/J<00-98>/SMDAgent.

1.1 Planning checklist

This section includes the planning steps for your installation. Detailed information about the steps is available in the relevant chapter.

Description

You identify Diagnostics Agent version to install [page 4]

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

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

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

You Install the Diagnostics Agent Using SAPinst [page 12]

1.2 New Features

Regarding the Diagnostics Agent itself, there are no new features compared to 7.0 SR3.

Here you can find the new features in this release.

Area Description

Documentation Checklists have been introduced for all phases of the installation process:



Planning checklist [page 1]

Preparation Checklist [page 4]

Installation Checklist [page 11]

The goal of these checklists is to provide a quick step reference of activities to be done for each phase of the installation.

1.3 Required Documentation

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

1.3.1 Information in the SAP Service Marketplace

Information on the following areas is available in the SAP Service Marketplace.

Root Cause Analysis Installation and Upgrade with SOLMAN SETUP Guide

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

Solution Manager (Installation Guides)

The current release of the SAP Solution Manager is SAP Enhancement Package 1 for SAP Solution Manager 7.0.

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

Select:

Release 7.0 EPH1 for Solution Manager 7.1

Release 7.0 for Solution Manager 7.0.

Wily Introscope

You will find the current version of Wily Introscope installation guide at https://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0.

FAQ list

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

OS Collector

Documentation for SAPOSCOL: start SAP Service Marketplace, and go to the System Managing and Alert Management area (https://service.sap.com/monitoring). Choose Monitoring in Detail, and then choose the document SAPOSCOL: Properties, Installation, and Operation.

1.3.2 SAP Notes

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



SAP Note Title

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

1234387 Inst. 7.1 EhP1 - Diagnostics Agent installation

1365123 Installation strategy of Root Cause Analysis Agents

1.4 Components for Problem Messages

In case of problems, contact SAP Support by creating a message in Service Marketplace, components:

SV-SMG-DIA: issues related to Solution Manager Diagnostics

SV-SMG-DIA-SRV-AGT: issues related to Diagnostics Agent

XX-PART-WILY: issues related to Wily Introscope

1.5 Terminology and variables

Managing System is a term for the central entry point of system analysis & monitoring. SAP Solution Manager is the managing system.

Managed System (also called monitored system) is a term for a satellite system (e.g. Enterprise Portal) connected to SAP Solution Manager.

Variables

Variables Description

<SMDSID> Diagnostics Agent system ID in uppercase letters

<smdsid> Diagnostics Agent system ID in lowercase letters

<Instance_Number> Number of a Diagnostics Agent

<INSTDIR> Installation directory of the SAP system

<J2EE_HOME> Installation directory of the J2EE Engine

<JAVA_HOME> Installation directory of the JDK (Java Development Kit)

<OS> Operating system name within a path

1.6 Installation planning

On each server (machine) of a managed system for Root Cause Analysis, some configuration tasks have to be performed. Please follow the table below for step-by-step processing of the setup tasks:

Installation Action on Managed System Remarks

Installation of Diagnostics Agent

Installation of SAP Os Collector Only for non SAP products

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





2 Preparation

2.1 Preparation Checklist

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

Detailed information about the steps is available in the relevant section.

Point Description

2.2 You identify Diagnostics Agent version to install [page 4]

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

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

2.5 Your machine meets the Hardware Requirements [page 8]

2.6 You Install the Java Development Kit [page 8]

2.7 You Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 SR1 only) [page 9]

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

2.9 You Set limits on system resource (UNIX only) [page 9]

2.2 Diagnostics Agent version to install

Before starting the installation you need to identify the Diagnostics Agent version that complies with the version of the Solution Manager system.

Solution Manager Managed Version Diagnostics Agent Version / SAP Note

Versions 7.00 (prior to EhP1) 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1

7.01 SR1

SAP Note 1357812

Versions 7.0 EhP1 >= SP 18 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1

7.01 SR1

SAP Note 1357812

Versions 7.0 EhP1 >= SP 20 6.40, 7.0, 7.0 EhP1 & 2, 7.1 EhP1

7.11

SAP Note 1234387

If you already installed 6.40 agents on this Managed System or for more details see SAP Note 1365123.

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

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







SLD Registration: In this scenario, the SMD Agent registers itself into the production SLD assigned to the managed system on which the SMD Agent will be installed. This scenario should be used if Solution Manager is not yet installed. This is the mode implemented by default in the SAP NetWeaver 7.0 SR3 SAPinst and in the SAP NetWeaver 7.01 SAPinst.

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

2.3.1 System Landscape Directory (SLD) Registration

SLD Landscape Directory (SLD) is designed for registering the systems (along with the installed software) of your whole system landscape.

The usual case is to configure one SLD for your complete system landscape.

If you choose to register the Diagnostics Agent in existing SLD, it registers itself in the SLD Server and is assigned afterwards to the SMD Server using the Agent Admin tools (Managing System). This allows to install all the Diagnostics Agents even if the Solution Manager is either not installed or running. Moreover even if the credentials of the J2EE user used to connect the Diagnostics Agent are not valid, the agent is still available in the SLD and therefore can be assigned later to the Managing system.

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

2.3.2 Direct Solution Manager Registration

The Diagnostics Agent connects directly to the Managing system which must be up and running. There are two ways to connect the Diagnostics Agent to the managing box:

Lookup HTTP Connection via Message Server: we rely on the Java EE engine to dispatch to one of the dispatcher nodes.

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

2.4 Download Installation DVDs from SAP Service Marketplace

Prerequisites

As of 7.0 SR3 you need three DVDs to install the Diagnostics Agent:

Installation Master DVD

Kernel DVD

Java DVD

Note that these DVDs are required during other SAP NW System installations so you might have already downloaded them.



These products are available as follows:

You normally obtain the installation DVDs as part of the installation package.

You can also download installation DVDs from SAP Service Marketplace at:

http://service.sap.com/swdc Download Installations and Upgrades Entry by

Application Group SAP NetWeaver and complementary products SAP

NETWEAVER SAP EHP1 FOR SAP NETWEAVER 7.0 Installation <choose

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

If you download installation DVDs, note that the DVDs are split into several files. You have to reassemble the required files after the download.

Procedure

1. Create a download directory on the host where you want to run SAPinst.

2. Identify all download objects that belong to one installation DVD:

Platform Media Name Number Nb of files

AIX

BS 7 SR1 Installation Master AIX 64bit 51038620 1

BS 7 SR1 UC-Kernel 7.01 AIX 64bit 51036767 1

NW 7.0 EHP1 SR1 Java based SW Comp.s 51037093 4

HP-UX

Depending on your platform:

BS 7 SR1 Installation Master HP-UX on IA64 64bit

BS 7 SR1 Installation Master HP-UX on PA-RISC 64bit

51038620 1


BS 7 SR1 UC-Kernel 7.01 HP-UX on IA64 64bit

BS 7 SR1 UC-Kernel 7.01 HP-UX on PA-RISC 64bit

51036767 1


LINUX


BS 7 SR1 Installation Master Linux on IA32 32bit

BS 7 SR1 Installation Master Linux on IA64 64bit

BS 7 SR1 Installation Master Linux on x86_64 64bit

51038620 1


BS 7 SR1 UC-Kernel 7.01 Linux on IA32 32bit

BS 7 SR1 UC-Kernel 7.01 Linux on IA64 64bit

51036769 1



BS 7 SR1 UC-Kernel 7.01 Linux on x86_64 64bit


SOLARIS


BS 7 SR1 Installation Master Solaris on SPARC 64bit

BS 7 SR1 Installation Master Solaris on x64 64bit

51038620 1


BS 7 SR1 UC-Kernel 7.01 Solaris on SPARC 64bit

BS 7 SR1 UC-Kernel 7.01 Solaris on x64 64bit

51036767 1


Windows Server


BS 7 SR1 Installation Master Windows Server on IA32 32bit

BS 7 SR1 Installation Master Windows Server on IA64 64bit

BS 7 SR1 Installation Master Windows Server on x64 64bit

51038620 1


BS 7 SR1 UC-Kernel 7.01 Windows Server on IA32 32bit

BS 7 SR1 UC-Kernel 7.01 Windows Server on IA64 64bit

BS 7 SR1 UC-Kernel 7.01 Windows Server on x64 64bit

51036767 1


3. Download the objects to the download directory (see examples hereunder).

4. Extract the individual download objects using SAPCAR, starting with the lowest sequence

number (for instance: 51037093_1, then 51037093_2, and so on).

Before starting the installation you need to make these DVDs available on the installation host; you can copy them locally or mount them locally.

Examples

Windows Server on IA64 64bit, you have to download:



the media with name BS 7 SR1 Installation Master Windows Server on IA64 64bit

the media with name BS 7 SR1 UC-Kernel 7.01 Windows Server on IA64 bit

the 4 medias NW 7.0 EHP1 SR1 Java based SW Comp.s

AIX, you have to download:

the media with name BS 7 SR1 Installation Master AIX 64 bit

the media with name BS 7 SR1 UC-Kernel 7.01 AIX 64 bit

the 4 medias NW 7.0 EHP1 SR1 Java based SW Comp.s

2.5 Hardware Requirements

Hardware Requirement Requirement

Minimum disk space 200 MB for common libraries

150 MB by Diagnostics Agent

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

Minimum RAM 256 MB

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

2.6 Install the Java Development Kit

You need to prepare the system for the Diagnostics Agent by installing the Java Development Kit (JDK). It includes the Java Runtime Environment (JRE), which is required for SAPinst and a Java Development Kit (Java™ 2 SDK, Standard Edition = JDK), which is required for the Diagnostics Agent. JDK 1.4 (at least 1.4.2_09) is a prerequisite for the Diagnostics Agent installation.

If you want to perform a remote installation (this means using a standalone SAPinst GUI on a separate Windows or UNIX host), you need at least a JRE on the local host to start the SAPinst GUI there.

If JDK 1.4 is not installed, do not replace the existing JDK version, but install another JDK folder.

For not overwriting the JAVA_HOME environment variable value system-wide, it

is recommended to open a separate shell or command prompt, set

<JAVA_HOME> to point to the JDK1.4 install folder, and run SAPinst from there.

On AIX and x86_64 platform all recommendations are available in SAP Note 1093831



2.7 Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 SR1 only)

As of SAPinst 7.0 Enhancement package 1, the behavior of SAPinst has changed compared to previous versions. SAP no longer delivers any JCE policy archives within the SAP JVM. If you want to perform a remote installation, you have to download the required JCE policy zip file from SAP on the remote host. For more information, see SAP Note 1238121.

UNIX

Shell Used Command

Bourne shell (sh) JCE_POLICY_ZIP=<policy zip archive>

export JCE_POLICY_ZIP

C shell (csh) setenv JCE_POLICY_ZIP <policy zip archive>

Korn shell (ksh) export JCE_POLICY_ZIP=<policy zip archive>

WINDOWS

set JCE_POLICY_ZIP=<policy zip archive>

For more details about Performing a Remote installation with SAPinst see page 18.

2.8 Set DISPLAY (UNIX only)

Make sure that your DISPLAY environment variable is set to <host_name>:0.0, where

<host_name> is the host on which you want to display the SAPinst GUI.

Shell Used Command

Bourne shell (sh) DISPLAY=<host_name>:0.0

export DISPLAY

C shell (csh) setenv DISPLAY <host_name>:0.0

Korn shell (ksh) export DISPLAY=<host_name>:0.0

2.9 Set limits on system resource (UNIX only)

On AIX the limits are described in SAP Note 323816

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

In csh execute limit

Output Properties





cputime unlimited

filesize unlimited

datasize 2097148 KB

stacksize 8192 KB

coredumpsize unlimited

descriptors 8192

memorysize unlimited

In sh or ksh execute ulimit -a

Output Properties

time(seconds) unlimited

file(blocks) unlimited

data(kbytes) 2097148

stack(kbytes) 8192

coredump(blocks) unlimited

nofiles(descriptors) 8192

memory(kbytes) unlimited

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

Example

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

In csh execute:

limit descriptors 8192

In sh or ksh execute:

ulimit -n 8192



3 Installation The following sections provide detailed information about installation & setup of Solution Manager Diagnostics.

3.1 Installation Checklist

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

Detailed information about the steps is available in the relevant section.

Point Description

3.2 You run SAPinst [page 11]

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

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

3.2 Running SAPinst

This section describes an installation where SAPinst, SAPinst GUI, and the GUI server are running on the same host and on the local display.

If necessary, you can:

perform a remote installation with SAPinst [page 18], where SAPinst GUI is running on a separate host from SAPinst and the GUI server

Start SAPinst GUI separately [page 19]

3.2.1 Running SAPinst on Unix

1. Log on to your host as user root.

2. Mount the DVDs.

Mount the DVDs locally. We do not recommend using Network File System (NFS).

3. Change to the directory:

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

4. Run the command:

./sapinst

The SAPinst GUI starts and the Welcome screen appears.

3.2.2 Running SAPinst on Windows

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

2. Map a network drive pointing to the DVD location



3. Open the command line in the installation directory, or double-click the executable in the Windows Explorer, and run the command:

<DVD drive>:\<SMD Agent DVD>\IM_<OS>_<platform>\sapinst.exe

The Welcome screen appears, and the installation begins.

3.2.3 Running SAPinst on System I (I5/OS)

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

3.3 Install the Diagnostics Agent Using SAPinst

Process Flow

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

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

3. On the Welcome screen, choose < Your SAP product > Standalone Engines Solution

Manager Diagnostics Agent Solution Manager Diagnostics Agent Installation

4. To start the installation, choose Next.

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

For more information about the input parameters, place the cursor on the relevant field and press F1 in SAPinst.

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

If you change a parameter with the Revise button on the Parameter Summary screen, the installer takes you to the screen where you can change the parameter. Depending on the changes, the installer might guide you through other screens with default parameters that it has so far processed.

3.4 Diagnostics Agent Parameters

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

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

Diagnostics Agent parameters: JDK, drive (Windows only), Server name

Operation System Users (<smdsid>adm)

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

Connectivity for the Diagnostics Agent to Solution Manager

IBM DB2 UDB for iSeries > Kernel Load Parameters



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

Parameters Description

System ID <SMDSID> of

SAP Solution Manager

Diagnostics Agent

SAPinst sets the system ID of SAP Solution Manager

Diagnostics Agent, <SMDSID> to SMD by default.

If a Diagnostics Agent 7.0X is already installed on this machine,

SAPinst sets <SMDSID> to its SID.

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

Diagnostics Agent, SAPinst assigns another default system ID:

starting from DAA to DAZ. You can overwrite the default system

ID as required.

Make sure that the <SMDSID>

Either does not yet exist on the local installation host, or does already exist but exclusively contains some Diagnostics Agent installation

Consists of exactly three alphanumeric characters

Contains only uppercase letters

Has a letter for the first character

Does not include any of the following, which are reserved IDs:

ADD ALL AND ANY ASC AUX COM CON DBA END

EPS FOR GID IBM INT KEY LOG LPT MON NIX

NOT NUL OFF OMS PRN RAW ROW SAP SET SGA

SHG SID SQL SYS TMP UID USR VAR

An error message pops up if the SAP System Name is not a dedicated agent one or if the System ID is already used.

Instance Number of the Diagnostics Agent

Technical identifier for internal processes for the Diagnostics Agent, consisting of a two-digit number from 98 to 00.

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

Windows: Forbidden instance numbers: 43, 60, 89

Virtual Host Name You can choose a Virtual Host installation type if you plan to manage systems running on a virtual host. This scenario lets the Diagnostics Agent take part in a switchover environment.

If the checkbox is selected SAPinst checks whether the virtual host name field is not empty. However the rightness of the input is not checked. So a bad value could make an error



occur during the action phase.

3.4.2 Diagnostics Agent parameters: JDK, drive (Windows only), Server name


Java Development Kit SAPinst sets the Java Development Kit (JDK) directory to the

JAVA_HOME environment variable value if it is set and points to

a valid JDK home directory.

If the JAVA_HOME environment variable is not set or does not

point to a valid JDK the file system is browsed to find the JDK directories. The one with highest release number between 1.4.2_09 and 1.5 (excluded) is returned.

Installation drive

On windows only

Base directory for the Diagnostics Agent.

You cannot select the installation drive if:

the saploc share already exists (a SAP System or a

Diagnostics Agent has already been installed on this machine), SAPinst sets the installation drive where the

saploc share points to.

the saploc share does not exist but there is only one

hard disk on this machine

Server Name Key The text field has to be filled with the key declared in SMSY ABAP transaction of Solution Manager allowing to identify each host bound to a solution.

We strongly recommend you to leave it empty if you do not know it. In this case the assignment is postponed and will be done using the Diagnostics Managed Setup Wizard.

3.4.3 Operation System Users (<smdsid>adm)


Operating System User: <smdsid>adm

If you have no user dedicated to the Diagnostics Agent (user with sufficient authorization to manage the agent), SAPinst

creates the user <smdsid>adm

Unless this user already exists and is not a user dedicated to the Diagnostics Agent, we recommend you keep

<smdsid>adm as username.

WINDOWS

OS User and Password are checked. The password has to be confirmed. It the user does not exist, SAPinst asks to confirm the creation. The domain is asked (local, this of current user,



different domain).

UNIX AND IBM SYSTEM I (I5/OS)

OS User and Group used to deploy the Diagnostics Agent and to start it are checked. If the user does not exist, SAPinst asks to confirm its creation and another dialog is displayed. It allows to specify the password, user ID, login shell and home directory used to create the new user. User ID and Home Directory should be left empty. If you specify a user ID make sure that it is

not already used by another user. The group is set to sapsys

on Unix platform and to r3group on IBM System i(i5/OS)

platform.

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

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


SLD Destination

You can choose between the following options:

Register in existing central SLD

SAPinst only prompts you for the parameters listed below in this table if you select this option.

We recommend that you select this option.

No SLD Destination

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

If it is installed as a standalone engine, the Agent connects directly to the Managing system which must be up and running. See Connectivity for the Diagnostics Agent to Solution Manager [page 16] for more details about Solution Manager Connection parameters.

SLD HTTP Host The fully-qualified host name of the System Landscape

Directory (SLD), e.g. p135809.wdf.sap.corp

Server Hostname is checked. It is highly recommended to input the full qualified Hostname.

SLD HTTP Port The HTTP port of the Java system where the SLD is installed. The following naming convention applies:

5<Instance_Number>00.

SLD Data Supplier User Enter the existing SLD Data Supplier User and password of the



and password central SLD e.g. SLDDSUSER.

3.4.5 Connectivity for the Diagnostics Agent to Solution Manager

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

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


Connection Type

You can choose between the following options:

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

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

Host The fully-qualified host name of the SMD Server, e.g. p135809.wdf.sap.corp

Server Hostname is checked. It is highly recommended to input the full qualified Hostname.

Port Depending on the connection type you have to specify either the Java EE P4 Port of the SAP Java EE Engine running on the Diagnostics Server or the HTTP Message Server Port.

P4 Port is 5xx04 (where xx is the instance number of Java EE engine:

/usr/sap/<SMDSID>/J<Instance_Number>).

Java EE Message Server HTTP Port is 81xx (where xx is the SCS instance number:

/usr/sap/<SMDSID>/SCS<xx>).

User and password We recommend that you use the SMD_ADMIN user created

during the SMD Setup Wizard step in the Managing System.

Diagnostics Server Hostname is checked. It is highly recommended to input the full qualified Hostname.

Then all the steps executed during Setup phase are tested. If something wrong occurs an error message pops up. It is recommended not to begin agent installation as long as



setup check failed.

3.4.6 IBM DB2 UDB for iSeries > Kernel Load Parameters

Choose the name of the kernel library. SMDEXEU is the default. It is possible to use an existing kernel library or (re-) load a kernel library.

If you already have installed an SAP system based on kernel release 7.00, the most convenient way is to use (a copy of) its kernel and to specify it in this dialog with selecting "Use existing library".

Otherwise, if a kernel library shall be loaded, the installer will ask for a Unicode Kernel DVD.



4 Additional Information

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

Performing a Remote installation with SAPinst [page 18]

Starting SAPinst GUI Separately [page 19]

Starting and Stopping the Diagnostics Agent [page 20]

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

Deleting a Diagnostics Agent [page 22]

Post installation steps [page 22]

Troubleshoot SAPinst and the Diagnostics Agent [page 25]

Installation of OS Collector SAPOSCOL [page 27]

4.1 Performing a Remote installation with SAPinst

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

UNIX

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

2. Log on as user root.

3. Mount the DVD

4. SAP NetWeaver 7.01 only: download the JCE policy zip file from SAP as described in SAP Note 1240081.

5. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive. See Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 SR1 only) [page 9].

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


7. Start SAPinst by executing the following command:

./sapinst -nogui

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt:

guiengine: no GUI connected; waiting for a connection on host

<host_name>, port <port_number> to continue with the installation.

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

WINDOWS

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

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

group.



3. Map a network drive pointing to the DVD location on your remote host


5. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive. See Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 SR1 only) [page 9].

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

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

7. Enter the following commands:

sapinst.exe -nogui

SAPinst now starts and waits for the connection to the SAPinst GUI. You see the following at the command prompt:

guiengine: no GUI connected; waiting for a connection on host

<host_name>, port <port_number> to continue with the installation

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

4.2 Starting SAPinst GUI Separately

You use this procedure to start SAPinst GUI separately.

UNIX

1. Log on as user root.


3. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive. See Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 SR1 only)[page 9].

4. Mount the DVD

5. Change to the directory:


6. Run the command

./sapinstgui

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

WINDOWS

1. Log on as a member of the local Administrators group.

2. SAP NetWeaver 7.01 only: the JCE policy zip file from SAP as described in SAP Note 1240081.

3. Set the environment variable JCE_POLICY_ZIP to the location of the downloaded policy zip archive. See Download the JCE Policy Zip File (in case of remote installation with SAPinst 7.01 SR1 only)[page 9].

4. Map a network drive pointing to the DVD location on your remote host



5. Change to the directory of the sapinst executables:

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

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

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

4.3 Starting and Stopping the Diagnostics Agent

UNIX

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

You can start and stop the Diagnostics Agent by running the smdstart and smdstop

scripts.

The local versions of these scripts are located in /usr/sap/<SMDSID>/J<Instance_Number>/script.

The global versions of these scripts are located in /usr/sap/<SMDSID>/exe.

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

Prerequisites

You have logged on to the host as user <smdsid>adm.

Procedure

Starting a Diagnostics Agent Locally

1. Change to the following directory:

/usr/sap/<SMDSID>/J<Instance_Number>/script

2. To start the Diagnostics Agent locally, enter this command:

./smdstart.sh

Starting Diagnostics Agent(s) Globally

To start Diagnostics Agent(s) globally, enter this command:

smdstart <SMDSID> <Instance_Number>

Example

smdstart SMD 98

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

Agent system on this host.

Stopping a Diagnostics Agent Locally

1. Change to the following directory:



/usr/sap/<SMDSID>/J<Instance_Number>/script

2. To stop the Diagnostics Agent locally, enter this command:

./smdstop.sh

Stopping Diagnostics Agent(s) Globally

To stop Diagnostics Agent(s) globally, enter this command:

smdstop <SMDSID> <Instance_Number>

Example

smdstop SMD 98

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

Agent system on this host.

Update your system boot sequence to include the two Diagnostics Agents

scripts smdstart.sh and smdstop.sh (located in

/usr/sap/<SMDSID>/exe) to start and stop the Diagnostics Agent process.

WINDOWS

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

It is installed as a Windows service.

This SAP Service (SAP_<SMDSID>_<Instance_Number> is always automatically started

when you boot your Windows system.

Procedure

Starting/Stopping Diagnostics Agent(s)

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

1. Start the SAP MMC on the SAP system host by choosing Start Programs SAP Management Console.

2. Right-click the Diagnostics Agent node and choose Start or Stop.

IBM SYSTEM I(I5/OS)

The Diagnostics Agent is installed like a standard SAP instance.

Procedure

Starting/Stopping Diagnostics Agent(s)

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

4.4 Mass Deployment of the Diagnostics Agent

If you want to massively deploy the Diagnostics Agent on a customer system landscape you can use the Diagnostics Agent SAPinst in unattended mode. This means you record all input parameters for one installation scenario, which you can then reuse for further installations.



Please refer to SAP Note 1172764: Mass Deployment of SAP Diagnostics Agent for more details. This SAP Note describes the additional steps you have to perform for an installation in unattended mode beyond the "standard" installation procedure that is described in this installation guide.

4.5 Deleting a Diagnostics Agent

This procedure tells you how to delete the Diagnostics Agent with SAPinst.

You must delete a Diagnostics Agent instance only using SAPinst, otherwise you might have problems with further installations on this host.

Prerequisites

UNIX

You are logged on as user root.

We recommend that you delete a Diagnostics Agent with SAPinst. However, you can also delete a Diagnostics Agent manually. For more information, see SAP Note1229586.

WINDOWS

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

Do not use the user <smdsid>adm to delete the Diagnostics Agent.

Procedure

3. Start SAPinst [page12].

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

Uninstall Uninstall - Solution Manager Diagnostics Agent

5. Follow the instructions in the SAPinst input dialogs.

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

4.6 Post installation steps

The sections hereunder describe the following Post installation tasks:

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

Change the Diagnostics Agent credentials [page 23]

Change the Diagnostics Agent connectivity type [page 24]




4.6.1 Change the Managing System of the Diagnostics Agent

If the Diagnostics Agent is already installed on your system with some wrong parameters, you

can change the Diagnostics Agent configuration by running the smdsetup script.

Prerequisites

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

Procedure

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

1. Stop the Diagnostics agent

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

3. The command to execute depends on the connection type and on the SAPinst release.

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

SAPinst SR3

The command to execute does not depend on the connection type (Direct connection to the Managing System or SLD Registration )

smdsetup managingconf

hostname:"sapms://<J2ee_Message_server_hostname>"

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

SAPinst 7.01

The command to execute depends on the connection type

In case of Direct connection to the Managing System:




In case of SLD Registration:

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

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

4. Start the Diagnostics agent

4.6.2 Change the Diagnostics Agent credentials

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

Prerequisites

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



Procedure

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

2. Open Diagnostics Administration -> Managed Systems -> Agent Administration

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

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

4.6.3 Change the Diagnostics Agent connectivity type

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

Connectivity types

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

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

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

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

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

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

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

Prerequisites

The Diagnostics Agent is already installed.



Procedure

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

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

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

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

4.7 Troubleshoot

This section provides additional information troubleshooting:

Troubleshooting with SAPinst [page 25]

Diagnostics Agent does not start [page 26]

4.7.1 Troubleshooting with SAPinst

This section tells you how to proceed when errors occur during the installation with SAPinst.

If an error occurs, SAPinst:

Stops the installation

Displays a dialog informing you about the error

Procedure

1. To view the log file, choose View Logs.

2. If an error occurs during the dialog or processing phase, do either of the following:

Try to solve the problem

Abort the installation with Exit

Continue the installation by choosing Retry.

3. Check the log files of SAPinst in the installation directory sapinst_instdir SAPinst

normally creates this installation directory directly below the temporary directory. SAPinst

finds the temporary directory by checking the value of the environment variables TEMP,

TMP, or TMPDIR. The logs relevant for the Diagnostics Agent are sapinst_dev.log and

smd*.log.

If no value is set for these variables, SAPinst uses /tmp/sapinst_instdir

as default installation directory on UNIX platforms and

%ProgramFiles%\sapinst_instdir on windows platforms. If you want to

use an alternative installation directory, set the environment variable TEMP,

TMP, or TMPDIR to the required directory.



4.7.2 Diagnostics Agent does not start

Prerequisites

The Diagnostics Agent was installed automatically at the end of a central/dialog instance installation.

The Diagnostics Agent does not come up at the end of the installation although the installation was succeeded.

Two kinds of scenarios can involve such an issue:

Bad CIM model [page 26]

Diagnostics Agent not registered in SLD [page 26]

Procedure for Bad CIM model

During the installation you chose to register the Diagnostics Agent in the SLD Server. The Diagnostics Agent does not come up at the end of the installation although the installation was succeeded.

The smd.log file (/usr/sap/<SMDSID>/JXX/sapinst/log) mentions that the CIM

model is not correct.

1. Update the CIM model to 1.5.26 or +

2. Open a shell (command prompt on windows platforms) on

/usr/sap/<SMDSID>/J<Instance_Number>/script and log on as

<smdsid>adm user.

3. Execute the command:



Procedure for Diagnostics Agent not registered in SLD

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

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

are missing.

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


/usr/sap/<SMDSID>/J<Instance_Number>/script and log on as <smdsid>adm

user.





Nevertheless if you choose to register the agent in an existing Central you have to proceed as follows:

1. Make sure that the CIM model version is 1.5.26 or +


/usr/sap/<SMDSID>/J<Instance_Number>/script and log on as

<smdsid>adm user.






4.8 Installation of OS Collector SAPOSCOL

The operating system collector SAPOSCOL is a program running on OS level. It works independently from SAP instances, exactly once per managed host. SAPOSCOL collects data about operating system related data. For more detailed information about SAPOSCOL, refer to OS Collector.

SAPOSCOL Patch 67 is required, the version can be verified by executing saposcol -

version. The OS Collector will be installed and configured automatically by SAPInst during

the installation of any SAP product. For non-SAP software solutions, it has to be installed and configured manually.

Documents

701SR1 Diag Agent Setup Guide