SWPM10SP7 Diag Agent Unattended

7/21/2019 SWPM10SP7 Diag Agent Unattended

http://slidepdf.com/reader/full/swpm10sp7-diag-agent-unattended 1/16

SAP Solution Manager

End-to-End Root Cause Analysis

Diagnostics Agent

Installation in Unattended Mode

with SWPM 1.0 SP7

for NetWeaver higher than 7.0x

Document Version 7.0 – 31-October-2014



© Copyright 2014 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.

SAP AG

Neurottstraße 1669190 Walldorf GermanyT +49/18 05/34 34 24F +49/18 05/34 34 20

www.sap.com



T y p o g r ap h i c C o n v en t i o n s

Type Style Represents

ExampleText

Words or charactersquoted from the screen.These include field names,screen titles, pushbuttonslabels, menu names, menupaths, and menu options.

Cross-references to other documentation.

Exampletext

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

EXAMPLETEXT

Technical names of systemobjects. These includereport names, programnames, transaction codes,table names, and keyconcepts of a programming

language when they aresurrounded by body text,for example, SELECT andINCLUDE.

Exampl et ext

Output on the screen. Thisincludes file and directorynames and their paths,messages, names of variables and parameters,source text, and names of installation, upgrade anddatabase tools.

Exampletext Exact user entry. These arewords or characters that

you enter in the systemexactly as they appear inthe documentation.

<Exampletext>

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries inthe system.

EXAMPLE

TEXT

Keys on the keyboard, for

example, F2 or ENTER.

I c o n s

Icon Meaning

Caution

Example

Note

Recommendation

Syntax



Contents October 2014

Diagnostics Agent Installation in Unattended Mode I

Contents

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

1.1 Installation and Installation Strategy .................................................................. 1

1.2 SAP Solution Manager Diagnosti cs Agent ......................................................... 1

1.3 SAP Notes for the Installation ............................................................................. 1

2 PREPARATION.............................................................................................................. 1

2.1 Preparation Checkl ist .......................................................................................... 1

2.2 Prepare the Installation Environment ................................................................. 2

2.3 Modify the Input Parameters (inifile.xml) ..................................................... 3

2.4 Create start_dir.cd File .................................................................................. 3

2.5 Identify Product ID for Installation ...................................................................... 4

3 INSTALLATION ............................................................................................................. 5

3.1 Process Steps ...................................................................................................... 5

3.2 Examples .............................................................................................................. 5

3.3 Installation Parameters ........................................................................................ 5

3.3.1 Diagnostics Agent Parameters .................................................................... 6

3.3.2 Operating System Users for the Diagnostics Agent ..................................... 6

3.3.3 Operating System User for the SAP Host Agent .......................................... 7

3.3.4 Connectivity for the Diagnostics Agent to System Landscape Directory ....... 8

3.3.5 Connectivity for the Diagnostics Agent to Solution Manager ........................ 8

4 UNINSTALLATION ...................................................................................................... 10

4.1 Prepare the Installation Environment ............................................................... 10

4.2 Modify the Input Parameters (inifile.xml) ................................................... 10

4.3 Create start_dir.cd File ................................................................................ 10

4.4 Identify Product ID for Uninstallation ................................................................ 11

4.5 Process Steps .................................................................................................... 11

5 ADDITIONAL INFORMATION ...................................................................................... 12

5.1 How to Avoid Aut omatic Logoff by SAPinst (Windows) .................................. 12

5.2 Troubleshooting with SAPinst .......................................................................... 12



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

Diagnostics Agent Installation in Unattended Mode 1

1 IntroductionIt is possible to install the Diagnostics Agent in an unattended mode. This means you recordall input parameters for an installation scenario, which you can then reuse for further installations. This guide describes how to perform for such installation or uninstallation.

1.1 Installation and Installation Strategy

Before you continue with the unattended mode installation of Diagnostics Agents, you musthave defined your installation strategy, and you must have made a decision on whether youwant to use the Agents On-the-fly feature or not.

Use the latest installer and read the following sections from the corresponding Diagnostics Agent Installation and Setup Guide, before continuing:

a. Installation Strategy

b. Using Logical Host Names

c. Using Virtual Host Names

1.2 SAP Solution Manager Diagnostics Agent

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

1.3 SAP Notes for the Installation

Before planning the installation of the Diagnostics Agents make sure to read SAP Note

1858920: Diagnostics Agent installation with SWPM. The corresponding Diagnostics AgentInstallation and Setup Guide contains relevant installation and post-installation information.

2 Preparation

2.1 Preparation ChecklistThis section includes the preparation steps that you have to perform. Detailed informationabout the steps is available in the respective sections.

Prerequisites

Read SAP Notes for the Installation [page 1]1. Identify the Installation Strategy (Direct Solution Manager Registration, SLD Registration or 2.

None)

Check the Hardware Requirements3.

Download the Installation DVDs4.

Read How to Avoid Automatic Logoff by SAPinst (Windows) [page 12]5.

Process Steps

Prepare the Installation [page]1.

Modify the Input Parameters (inifile.xml) according to your needs [page 3]2.





Create start_dir.cd File [page 3]3.

Identify Product ID for Installation [page 4]4.

Start the Installation [page 5]5.

2.2 Prepare the Installation Environment

Download the inifile.xml, keydb.dtd and doc.dtd files (attached to this SAP Note)and save them in a common directory ${COMMON_FOLDER}

Windows: c:\unattended\common

Unix/IBM i: /unattended/common

The keydb.dtd and doc.dtd files are required for parsing inifile.xml.

Create an installation directory on the host on which you want to run SAPinst inunattended mode.

On Unix, make sure that:a) a user group "sapinst" is available.b) "sapinst" is assigned as an additional user group to user root.c) the installation directory is owned by user group "sapinst" and has at least

permissions 775. To change the group value, proceed as follows:

chgrp –R sapinst <directory where the installation isexecuted and the location of the DVD folders>

On IBM i, make sure that:a) a user group "sapinst" is available.If a user profile "sapinst" already exists, you have nothing to do.If no user profile "sapinst" exists, do the following command:CRTUSRPRF USRPRF(SAPINST) GID(*GEN)

b) "sapinst" is assigned as an user group to your installation user:CHGUSRPRF USRPRF(<inst_user>) GRPPRF(SAPINST)

c) the installation directory is owned by user group "sapinst" and has at leastpermissions 775:CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/chmod''-R' '775' '<directory where the installation is executed

and the location of the DVD folders>') (press F3 to exit thesession)





To change the group value, proceed as follows:CALL PGM(QP2TERM) PARM('/QOpenSys/usr/bin/chgrp''-R' 'sapinst' '<directory where the installation is

executed and the location of the DVD folders>') (press F3 toexit the session)

2.3 Modify the Input Parameters (i ni f i l e. xml )

The file named inifile.xml is a template document which has to contain all requiredparameters to run SAPinst in unattended mode. Edit inifile.xml and modify theparameters according to your needs.

Only the parameters with value TO_BE_DEFINED are required to be modified.The other ones can be left as they are.

You can enter passwords in plain text. At the first SAPinst execution, your current inifile.xml will be replaced by a version with the encryptedpassword. For that reason please do not forget to make a copy of your originalinifile.xml if you need it later.

For details refer to chapter Installation Parameters [page 5].

After you have made the required changes, you should check the changes youhave made using a "diff tool". Most problems that occur with this procedure are

due to accidental changes that are made to the inifile.xml file. Doublechecking your changes against the originally distributed template document willprotect you against problems due to accidental changes.

2.4 Create st ar t _di r . cd File

Create an installation directory on the host on which you want to run SAPinst in unattended1.

mode: ${EXEC_DIR}

Windows: c:\unattended\install

Unix/IBM i: /unattended/install

Create a file named start_dir.cd . It contains the paths to the Installation DVDs (Kernel2.

DVD and Installation Master DVD) required for the unattended installation (To identify anddownload the Installation DVDs see section 1.2).

Save the file start_dir.cd in the installation directory that you created in step 1.3.

Edit the file start_dir.cd .4.

Enter the paths to the Installation Master and Kernel DVDs. A separate line is required for 5.each DVD path.





For each DVD you have to browse until the main LABEL.ASC file to identify the paths toadd to start_dir.cd .

The table below lists the lines to add to start_dir.cd depending on the product and theDVD.

Path

[Installation Master]

${DVD_LOCATI ON}/ i nst al l at i on_mast er

[Kernel]

${DVD_LOCATI ON}/ ker nel _dvd

Save start_dir.cd .6.

2.5 Identify Product ID for Installation

You need to identify the Product ID for the installation service that is required for your 1. installation scenario.

Before starting SAPinst you may want to backup/delete/rename an already existing2.sapinst_instdir directory.

Start SAPinst as described in the Diagnostics Agent Installation and Setup Guide. See3.section 1.2.

a. On the "Welcome to SAP Installation" screen, choose: SAP Installation Master

Generic Installation Options Diagnostics in SAP Solution Manager Install -Diagnostics Agent.

b. Then press "Next".

c. Stop SAPinst as soon as the next screen has appeared.

SAPinst has now created a new sapinst_instdir directory structure. Go to the directory4.

and locate and open the sapinst_dev.log file.

In the sapinst_dev.log file search for the string product-id . You should find a line5.

like: Runni ng wi t h cont r ol f i l e XXX ver si on=XXX changel i st =XXXproduct - i d=XXX

For SWPM 1.0 SP7 (for NetWeaver higher than 7.0x) the product-id should be:NW_Di agnost i csAgent: GENERI C. I ND. PD

This value is required to run the installation in unattended mode. This ID represents theSAP Installation Product ID parameter ( SAPI NST_EXECUTE_PRODUCT_I D="NW_Di agnost i csAgent : GENERI C. I ND. PD" )

For the "Install - Diagnostics Agent with 7.41/7.42 Kernel" installation option,the product-id you need to identify and use below, should be:NW_Di agnost i csAgent : NW740. I ND. PD

Before continuing you may want to backup/delete/rename the just created6.sapinst_instdir directory.





3 Installation

3.1 Process Steps

On the host on which you want to run SAPinst in unattended mode, proceed as follows:

Change to the installation directory1.

cd ${EXEC_DI R}

Start SAPinst with the following parameters (you get an overview of all SAPinst parameters2.by execution sapi nst - p)

SAPI NST_PARAMETER_CONTAI NER_URL=${COMMON_FOLDER}/inifile.xml

SAPI NST_EXECUTE_PRODUCT_I D=<Product ID>

SAPI NST_SKI P_DI ALOGS=true

The command line to execute is as the following one:${EXEC_DIR} # ${DVD_LOCATI ON}/ i nst al l at i on_mast er / sapi nstSAPI NST_PARAMETER_CONTAI NER_URL=${COMMON_FOLDER}/ i ni f i l e. xmlSAPI NST_EXECUTE_PRODUCT_I D=<Pr oduct I D> SAPI NST_SKI P_DI ALOGS=t r ue

Result:3.

SAPinst installs your agent in unattended mode. You may check the result of theinstallation by opening the sapinst_dev.log file within the ${EXEC_DIR}.

If you need to start SAPinst with SAPinst GUI, do not specify theSAPI NST_SKI P_DI ALOGS option.

3.2 Examples

Windows

C: \ unat t ended\ i nst al l > c: \ i nst al l at i on_mast er \ sapi nst . exeSAPI NST_PARAMETER_CONTAI NER_URL=c: \ unat t ended\ common\ i ni f i l e. xmlSAPI NST_EXECUTE_PRODUCT_I D="NW_Di agnost i csAgent : GENERI C. I ND. PD"SAPI NST_SKI P_DI ALOGS=t r ue

Unix / IBM i

/ unat t ended/ i nst al l > / i nst al l at i on_mast er / sapi nst

SAPI NST_PARAMETER_CONTAI NER_URL=/ unat t ended/ common/ i ni f i l e. xmlSAPI NST_EXECUTE_PRODUCT_I D="NW_Di agnost i csAgent : GENERI C. I ND. PD"SAPI NST_SKI P_DI ALOGS=t r ue

3.3 Installation Parameters

The following tables list all the mandatory or optional parameters needed for the installation.For parameters that are not mandatory, you can leave their value empty: SAPinst will set thevalue to a default value.

Diagnostics Agent Parameters [page 6]

Operating System Users for the Diagnostics Agent [page 6]

Operating System User for the SAP Host Agent [page 7]





Connectivity for the Diagnostics Agent to System Landscape Directory [page 8]

Connectivity for the Diagnostics Agent to Solution Manager [page 8]

For more details, please refer to the Diagnostics Agent Installation and Setup Guide (See

section 1.2).

3.3.1 Diagnostics Agent Parameters

Name Description Mandatory

sid System ID <DASID> of Diagnostics Agent

SAPinst sets the system ID of Diagnostics Agent, <DASID>, to DAA by default.

NO

instanceNumber Instance Number of the Diagnostics Agent

The instance number is set automatically tothe next free and valid instance number (from

98 down to 00) that has not yet beenassigned to the SAP system.

NO

virtualHost Logical Host Name

By default the installer sets the host name tothe physical host name.

If you want to install a Diagnostics Agent onthe physical host, you can leave thevirtualHost parameter empty. This is alsothe recommended way to install a Diagnostics Agent to be used with the Agents On-the-flyfeature.

You can set the host name to a logical hostname if you plan to manage systems runningon a logical host.

Do not use the FQDN, use the short hostname.

NO

3.3.2 Operating System Users for the Diagnostics Agent

The Diagnostics Agent user <dasid>adm is used to manage the Diagnostics Agent system.

Before starting to modify the parameters, make sure that you are modifying the

correct element: the attribute name of its parent element t abl e must notcontain the string NW_SAPHost Agent in its value.

Unix/IBM i


SIDAdm_Password OS User password for user <dasid>adm YES if user does not exist

SIDAdm_ID User ID for user <dasid>adm NO

SIDAdm_Home Home directory for user <dasid>adm NO

SIDAdm_Shell Login shell for user <dasid>adm NO





SAPSys_ID Group ID for group sapsys

On IBM i the group sapsys isconverted to the group R3GROUP.

NO

Windows


sapDomain Domain for the Diagnostics Agent OSUsers. SAPinst sets the domain to local bydefault.

NO

sidAdmPassword OS User password for user <dasid>adm YES

sapServiceSIDPassword OS User password for user SAPService<DASID> YES

sapdrive Base directory for the Diagnostics Agent

Modifiable only if the saploc share doesnot exist but there are several hard disks onthis machine.

NO butrecommended

3.3.3 Operating System User for the SAP Host Agent

If the SAP Host Agent is already installed on the host, this part is skipped.

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

Before starting to modify the parameters, make sure that you are modifying thecorrect element: the attribute name of its parent element t abl e must containthe string NW_SAPHost Agent in its value.

Unix/IBM i


SIDAdm_Password OS User password for user sapadm YES if SAP Host Agent notalready installed

SIDAdm_ID User ID for user sapadm NO

SIDAdm_Home Home Directory for user sapadm NO

SIDAdm_Shell Login Shell for user sapadm NO

SAPSys_ID Group ID for group sapsys

On IBM i the group sapsys isconverted to the group R3GROUP.

NO





Windows


sapDomain Domain for the SAP Host Agent OS User

SAPinst set the domain to local by default.

NO

sidAdmPassword OS User password for user sapadm YES if SAP Host Agent notalready installed

3.3.4 Connectivity for the Diagnostics Agent to SystemLandscape Directory

You have identified your Installation Strategy and want to register your Diagnostics Agent inan existing System Landscape Directory (SLD).


connection_sld SLD Registration Type

To register your Diagnostics Agent in an SLDyou have to set this parameter to: sld

YES put sld or no

host_sld Managing Host

HTTP host of the SAP system with the SLD thatis assigned to the managed system on whichthe Diagnostics Agent is being installed

YES if connection_sld!= no

port_sld Port

HTTP port of the SAP system with the SLD thatis assigned to the managed system on which

the Diagnostics Agent is being installed


user_sld User YES if connection_sld!= no

passwd_sld Password YES if connection_sld!= no

needHTTPS_sld If SSL is used for the SLD connection: true

Otherwise: false


3.3.5 Connectivity for the Diagnostics Agent to SolutionManager

You have identified your Installation Strategy and want to do a direct Solution Manager registration. You can choose to directly connect to the Solution Manager system even if youregistered it into the SLD during the previous step.


connection_solman Connection of the Diagnostics Agent to SolutionManager

You can choose between the following options:

solman (Configure connection: the

YES





Diagnostics Agent is connected to theSolution Manager system)

none (Do not configure connection: theDiagnostics Agent is not connected to the

Solution Manager system)

If you choose none, the values of theparameters below are not taken into account.

host_smd Managing Host

The fully-qualified host name of the SMD Server

YES if connection_solman != none

port_smd Depending on the connection type you have tospecify either the HTTP SCS Message Server Port or the HTTP SCS SSL Message Server Port of the Java stack of your SAP SolutionManager system.


user_smd User

As of SAP Solution Manager 7.10 SP10 werecommend to use the SMD_AGT user of your

SAP Solution Manager system.

For earlier releases the SMD_ADMIN user is still

recommended.


passwd_smd Password YES if connection_solman != none

useSSL_solman If SSL is used: true

Otherwise: false


route Route string describing the stations of aconnection required between the Diagnostics Agent and Solution Manager.

The route string contains a substring for eachSAProuter 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 is3299

/W/ indicates the password for the

connection between the predecessor andsuccessor on the route and is also optional(default is "", no password)

The route between the Diagnostics Agent andSolution Manager can be such as:/H/hostname.sap.com/S/3199

NO

passwd_route Password NO





4 UninstallationOn the host on which you want to run SAPinst in unattended mode, proceed as follows:

Prepare the Installation [page 10]1.

Modify the Input Parameters (inifile.xml) according to your needs [page 10]2.

Create start_dir.cd [page 10]3.

Identify Product ID for Uninstallation [page 11]4.

Execute the Process Steps [page 11]5.

4.1 Prepare the Installation Environment

For the uninstallation the inifile.xml is not provided. You need to create it as follows:

Start SAPinst as described in the Diagnostics Agent Installation and Setup Guide. See1.section 1.2.

a. On the "Welcome to SAP Installation" screen, choose: Generic Installation Options

Diagnostics in SAP Solution Manager Uninstall - Diagnostics Agent

b. On the screen "General SAP System Parameters", select the profile directory of theDiagnostics Agent that you want to uninstall:

/ usr / sap/ <DASI D>/ SYS/ pr of i l e

c. Follow the instructions in the SAPinst input dialogs.

Stop SAPinst after the "Parameter Summary" screen has appeared.2.

SAPinst creates the inifile.xml in the installation directory.

Copy the inifile.xml, keydb.dtd and doc.dtd files from the installation directory of the

"original" installation and save them in ${COMMON_FOLDER}.

4.2 Modify the Input Parameters (i ni f i l e. xml )

Edit inifile.xml and modify the parameters according to your needs.

Note that you can only modify the parameters which were covered by the inputdialogs you went through in step 4.1.

4.3 Create st ar t _di r . cd File

Create an installation directory on the host on which you want to run SAPinst in unattended1.

mode: ${EXEC_DIR}

Windows: c:\unattended\uninstall

Unix/IBM i: /unattended/uninstall

Create a file named start_dir.cd . It contains the path to the Installation Master DVD2.





Save the file start_dir.cd in the installation directory that you created in step 1:3.${EXEC_DIR}.

Edit the file start_dir.cd .4.

Enter the path to the Installation Master DVD.5. The table below lists the line to add to start_dir.cd .6.

Path

[Installation Master]

${DVD_LOCATI ON}/ i nst al l at i on_mast er

Save start_dir.cd .7.

4.4 Identify Product ID for Uninstallation

You need to identify the Product ID for the installation service that is required for your

uninstallation. Open the file sapinst_dev.log which is available in the installation directory where you1.

created the file inifile.xml in step 4.1.

Get the value of the Product ID which is named: pr oduct - i d=2.

4.5 Process Steps

On the host on which you want to run SAPinst in unattended mode, proceed as follows:

Change to the installation directory1.

cd ${EXEC_DI R}

For Unix and IBM i systems these directories need to belong to the sapinstgroup and have at least permissions 775.

Start SAPinst with the following parameters2.

SAPI NST_PARAMETER_CONTAI NER_URL=${COMMON_FOLDER}/inifile.xml

SAPI NST_EXECUTE_PRODUCT_I D=<Product ID>

SAPI NST_SKI P_DI ALOGS=true

The command line to execute is as the following one:3.

${EXEC_DIR}# ${DVD_LOCATI ON}/ i nst al l at i on_mast er / sapi nstSAPI NST_PARAMETER_CONTAI NER_URL=${COMMON_FOLDER}/ i ni f i l e. xmlSAPI NST_EXECUTE_PRODUCT_I D=<Pr oduct I D> SAPI NST_SKI P_DI ALOGS=t r ue

Result:4.

SAPinst uninstalls your agent in unattended mode. You may check the result of theuninstallation by opening the sapinst_dev.log file within the ${EXEC_DIR} directory.




Di ti A t I t ll ti i U tt d d M d 12

5 Addit ional Information

5.1 How to Avoid Automatic Logoff by SAPinst

(Windows)Please refer to the respective section in the Diagnostics Agent Installation and Setup Guidefor matching Software Provisioning Manager 1.0 Service Pack.

5.2 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

Check the log files of SAPinst in the installation directory ${EXEC_DIR}.

SWPM10SP7 Diag Agent Unattended

Documents

Transcript of SWPM10SP7 Diag Agent Unattended