advanced diagnostics setup guide as of sp09

SAP Solution Manager 4.0 (SP9) SAP Solution Manager 4.0 (SP9) SAP Solution Manager 4.0 (SP9) SAP Solution Manager 4.0 (SP9)

End to End diagnosticsEnd to End diagnosticsEnd to End diagnosticsEnd to End diagnostics

Powered by SAP netWeaver 04s SPS 10

Advanced Diagnostics Advanced Diagnostics Advanced Diagnostics Advanced Diagnostics

Setup GuideSetup GuideSetup GuideSetup Guide

Document Version 1.00 – November 2006

© 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/instguidesNW04service.sap.com/instguidesNW04service.sap.com/instguidesNW04service.sap.com/instguidesNW04

SAP AGSAP AGSAP AGSAP AG

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

www.sap.comwww.sap.comwww.sap.comwww.sap.com

T yp o gr a ph 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 November 2006

SAP Solution Manager 4.0 (SP9) End to End diagnostics I

Contents

1 INTRODUCTION .................................................................................................................1 2 MANUAL INSTALLATION STEPS FOR DIAGNOSTICS ..................................................1

2.1 Creation of Support User in ABAP User store ......................................................2 2.2 Disabling SMD Maintenance Mode .........................................................................2 2.3 Upgrader execution ..................................................................................................2 2.4 Creation of the RFC destination on J2EE side ......................................................3 2.5 Creation of the RFC destinations on ABAP side...................................................4 2.6 Storing IGS URL in SMD configuration ..................................................................5 2.7 Setup of Single Sign-On on SMD Server................................................................8 2.8 Creation of Role for ABAP User............................................................................11 2.9 Creation of Support Roles for J2EE Engine ........................................................12 2.10 Connection to NWA................................................................................................14 2.11 Storing Introscope Webview parameters in SMD configuration .......................16 2.12 Storing Introscope Enterprise Manager parameters in SMD configuration .....16

3 MANUAL SETUP TASKS ON MONITORED SYSTEMS .................................................17 3.1 Introduction.............................................................................................................17 3.2 Java Parameter Settings on Monitored J2EE Engines .......................................17 3.3 Setup of Single Sign-On on Monitored Systems.................................................17 3.4 Assignment of J2EE Server Roles to the Support User .....................................20 3.5 Setup of HTTP Analysis .........................................................................................21 3.6 Initialization of the Scheduler................................................................................22 3.7 Setup of Tasks ........................................................................................................22

4 MANUAL SETUP OF SMD AGENT..................................................................................24 4.1 Command Line Execution......................................................................................24 4.2 SMD Agent Setup Steps.........................................................................................24 4.3 SMD Agent Start Profile .........................................................................................25

5 AGENT CONFIGURATION AND ADMINISTRATION......................................................25 5.1 Change Credentials of SMD Agent .......................................................................25 5.2 SSL Setup for SMD Agent......................................................................................26

6 CONFIGURATION OF SMD AGENT APPLICATIONS....................................................27 6.1 J2EE Command Console Configuration ..............................................................30 6.2 File System Access Configuration .......................................................................31 6.3 SQL Command Console Configuration................................................................32 6.4 OS Command Console Configuration ..................................................................34 6.5 Log Viewer Configuration......................................................................................35 6.6 LDAP Browser Configuration................................................................................35

7 CONFIGURATION OF INTROSCOPE AGENTS .............................................................36 7.1 ISAdmin ...................................................................................................................36

7.1.1 Enterprise Manager Settings ........................................................................36 7.1.2 Introscope Agent Settings.............................................................................36 7.1.3 J2ee Node Information Details......................................................................37 7.1.4 Introscope Agent Setup ................................................................................37 7.1.5 Last Operation Results .................................................................................38 7.1.6 ISAgent Setup Prerequites ...........................................................................38

Contents November 2006

SAP Solution Manager 4.0 (SP9) End to End diagnostics II

7.1.7 ISAgent Settings Restrictions .......................................................................39 7.1.8 ISAgent Troubleshooting ..............................................................................39 7.1.9 ISAgent Known Issues..................................................................................40 7.1.10 ISAgent Upgrade ..........................................................................................40

7.2 Configuration of EP Agents...................................................................................41 7.2.1 EPAdmin .......................................................................................................41 7.2.2 Enterprise Manager Settings ........................................................................41 7.2.3 EPAgent Settings..........................................................................................41 7.2.4 Host Information Details................................................................................43 7.2.5 EPAgent ToolBar ..........................................................................................43 7.2.6 EPAgent Setup .............................................................................................43 7.2.7 Last Operation Results .................................................................................43 7.2.8 EPAgent Setup Prerequites ..........................................................................44 7.2.9 EPAgent Options ..........................................................................................44 7.2.10 EPAgent Settings Restrictions ......................................................................44 7.2.11 EPAgent Troubleshooting .............................................................................45

Introduction November 2006

Creation of Support User in ABAP User store

SAP Solution Manager 4.0 (SP9) End to End diagnostics 1

1 Introduction This document describes advanced setup and configuration procedures on Diagnostics.

It gives a list of manual steps covered by the setup Wizard of Diagnostics.

It explains also how to use some of the administration tools of SMD.

This guide is intended to be used by Solution Manager Administrators to:

• Support and troubleshoot a E2E diagnostics installation

• Perform advanced administrative tasks.

2 Manual Installation Steps for Diagnostics This chapter contains the manual procedure description for the installation & the setup of Solution Manager Diagnostics.

The general approach for E2E setup is to cover ALL setup steps automatically by the Diagnostics setup wizard.

However, some of the steps can be performed by using the SMD Advanced setup applications of Diagnostics or by using manual operation.

Step Description Manual Description

Creation of the RFC destination on J2EE side Chapter 2.4

Creation of the RFC destinations on ABAP side Chapter 2.5

Creation of Support User in ABAP User store chapter 2.1

Assignment of UME roles to the Support User Chapter 2.9

Assignment of ABAP roles to the Support User Chapter 2.8

Setup of Single Sign-On on SMD Server Chapter 2.7

Upgrader execution Chapter 2.3

Disabling Maintenance Mode Chapter 2.2

Storing NetWeaver Administrator access parameters Chapter 2.10

Storing Introscope Webview parameters in SMD configuration Chapter 2.11

Storing Introscope Enterprise Manager parameters in SMD configuration

Chapter 2.12

Storing IGS URL in SMD configuration Chapter 2.6

Storing LDAP Server parameters in SMD configuration

Generation of SAP Router template

Manual Installation Steps for Diagnostics November 2006

Creation of Support User in ABAP User store


2.1 Creation of Support User in ABAP User store The recommended name of the user for Solution Manager Diagnostics is SAPSUPPORT.

For the Web AS Java Add-In (Dual-Stack), the default user store is the ABAP database, thus users have to be created within SU01 only.

UME roles have to be assigned via the User Management application of the SAP J2EE Engine whereas ABAP roles have to be assigned via transaction PFCG.

2.2 Disabling SMD Maintenance Mode The maintenance is used to isolate the Monitoring System from the SMD Agents in case of an upgrade.

It has to be disabled after deploying the file LMSERVICE<version>.sca.

Before proceeding, it is important to wait for the reconnection of the entire agent landscape (what will be indicated by a green status icon) before processing further setup steps.

2.3 Upgrader execution

General

The SMD Upgrader performs all steps to complete the setup of the SMD Server and SMD Agents.

It has to be executed after deploying the file LMSERVICE09<version>.sca:

• after deployment in case of a new SMD Server installation

• after deployment in case of a SMD Server upgrade

Prerequisites

All SMD Agents have to be running on each monitored system.

To verify that all agents are running on the monitored systems, start the SMD Administration console

Choose tab Agent Administration

1. Select sub-tab Agents to show all SMD Agents connected to the SMD system

a. Status (started) indicates a successful connection between SMD and SMD Agent.

b. If a SMD Agent has status (stopped), the SMD Agent is running, but the agent infrastructure will not accept any requests from the SMD monitoring machine. In this case, click pushbutton Start or Restart.


Creation of the RFC destination on J2EE side


Start the SMD Upgrader

2. Start the SMD Administration console

3. Select tab Upgrader, afterwards a list of required upgrade steps will be shown

4. Choose pushbutton Upgrade Now

5. Once you have entered the required information on this page, select the Next pushbutton

2.4 Creation of the RFC destination on J2EE side To connect the Java-based part of the SMD Server to its ABAP stack (running Solution Manager), some settings have to be done: start the SMD Administration application (http://<host>:<port>/smd � Diagnostics Administration � Setup And Configuration � ABAP Connectivity setup)

Example screenshot of the ABAP Connectivity Setup screen:

Configuration

These steps need to be performed only once per SMD system. If the connectivity is already established, they can be skipped.

1. If the SMD system is installed on a J2EE Engine only (i.e. without ABAP stack), you have to setup an additional ABAP system (CEN), where your solution Manager is running. The following steps are required to establish SolMan/SMD connectivity.

a. Either choose the pushbutton Add a new system if you want to add an additional ABAP system or the pushbutton Edit system if you want to modify an existing one.

b. Enter the appropriate values.

2. To Setup the local connectivity between Java and ABAP system

Choose the pushbutton Setup Local Connectivity. If you get the message ”No connection available”, choose the pushbutton Start Connection and enter user and password of your ABAP system.


Creation of the RFC destinations on ABAP side


3. Return to the Agent configuration menu with the pushbutton Home.

The WEBADMIN connection can be checked within Visual Administrator (navigate to Server → Services → Jco RFC Provider).

Check if the proposed values are correct for the ABAP system parameters. If not, either modify the current values (e.g. client number or system number are wrong) or delete it and add a new system with the correct parameters afterwards.

2.5 Creation of the RFC destinations on ABAP side This step has to be done on the Solution Manager side in order to connect the ABAP side of solution manger 4.0 to the java side (SMD server).

Define RFC to connect to SMD

In the solution manager 4.0 ABAP stack, create an RFC connection (Transaction SM59) with the following values:

• RFC Destination = SOLMANDIAG

• Connection type = T

• Description = Solution Manager Diagnostics

In the Technical Settings tab:

• Activity type = Registered server program

• Registered server program = WEBADMIN

• External program call type = Gateway default value

• CPIC Timeout = Gateway default value

Define direct connection to SMD server

The function Solution Manager Diagnostics is installed on the Java instance of the Solution Manager system by default.

• If the default values are correct, save the settings.

• To run the Solution Manager Diagnostics in another system, enter the required data and save.

Assign necessary role

In order to run the wizard to publish solutions to Solution Manager Diagnostics completely, you need to assign to your ABAP user the following role: SAP_SMDIAG_WIZARD. For detailed information on Solution Manager roles, please refer to the following note 834534.


Storing IGS URL in SMD configuration


2.6 Storing IGS URL in SMD configuration SAP IGS (Internet Graphics Server) enables the output of graphics within ABAP based transactions. General information for the setup of SAP IGS is available in the SAP Library.

IGS Port Number Determination

SMD uses by default the SAP IGS installed on the same stack as it is running (the Java Stack). The default port is predefined, but if it as been customized you will need to change it in SMD configuration.

Under Java Stack

To find out the IGS port, open file /usr/sap/<SID>/<INSTANCE>/igs/conf/igs.xml, you will find the port used by IGS by getting the value of element LISTENERHTTP, attribute port (e.g. <LISTENERHTTP port="40080" />)

To test the IGS service, start your browser and launch the following URL:

http://<host>:<igs_port> (e.g. http://localhost:40080)

If example graphics are displayed, the IGS service is running properly.

Under ABAP Stack

The following RFC destinations have to be updated by using transaction SM59 on the ABAP stack. Make sure that field Program ID contains IGS.<SID>, e.g. IGS.SMD.

• GFW_ITS_RFC_DEST

• IGS_RFC_DEST

To test the IGS service, start ABAP transaction SA38 and run program GRAPHICS_IGS_ADMIN, use as IGS RFC destination IGS_RFC_DEST.




If example graphics are displayed, the IGS service is running properly.

To find out the IGS port, choose the pushbutton Status. You will find the port number in table CONNECTED_LISTENER, line Http, row Parameter (e.g. 40080):

Configuration of IGS

This operation is performed automatically by the Monitoring System Setup Wizard but can be performed manually as well.

Get the IGS Port as described in chapter IGS Port Number Determination [on page 5].

To adapt the settings for Solution Manager Diagnostics, proceed as follows:

1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running




2. Navigate to Server → Services → Configuration Adapter

3. In the Display configuration tab, open the branch for webdynpro → sap.com → tc~wd~dispwda

4. To switch to edit mode, choose the pushbutton (Display/Change); you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton

5. To modify data, choose the pushbutton (Change) or just double-click on Propertysheet default

6. Now you can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter

7. A single mouse click will open a new window where you can change the configuration data.

Change parameter IGSUrl to URL & port of the IGS, e.g. http://p135809.wdf.sap.corp:40080

Example screenshot for changing settings:

You can verify IGSUrl by entering this URL directly into your web browser

8. To save the data, choose the Apply custom pushbutton


Setup of Single Sign-On on SMD Server


2.7 Setup of Single Sign-On on SMD Server This operation is performed automatically by the Monitoring System Setup Wizard but can be performed manually as well.

The J2EE Engine of the Solution Manager Diagnostics server creates and issues a user ticket (SSO2 ticket) which enables authentication on all monitored SAP systems. The setup has to be performed in two steps. First the preparation of the Solution Manager Diagnostics’ J2EE Server and the export of a self-signed certificate and second the import into the monitored systems.

As the Solution Manager Diagnostics contains both Java and ABAP components, you have to import the certificate created by the Visual Administrator in the same way as explained in Setup of Single Sign-On on Monitored Systems [on page 17] – even if both Java and ABAP parts are installed on the same machine.

Always use full-qualified hostnames, e.g. p135809.wdf.sap.corp

For SSO scenarios, the Solution Manager Diagnostics system has to be in the same network domain as the monitored systems

Configuration

1. Preparation of the J2EE server of Solution Manager Diagnostics. The Client ID of the J2EE system has to be changed. This ID will be stored in every ticket and has to be unique. If the SSO module logs on the client with the ticket it uses this Client ID

a. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running

b. Navigate to Server → Services → Configuration Adapter

c. In the Display configuration tab, open the branch for cluster_data → server → cfg → services

d. Choose the pushbutton (Display/Change) to switch to the edit mode; you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton

e. Choose the pushbutton (Change) or just double-click on Propertysheet com.sapsecurity.core.ume.service

f. You can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter

g. A single mouse click will open a new window where you can change the configuration data:




Change parameter login.ticket_client to a number <> 000, e.g. 169

h. To save the data, choose the pushbutton Apply custom.

i. Restart the J2EE Engine of SMD.

2. Exporting certificates from the J2EE server


b. Navigate to Server → Services → Key Storage

c. In the Runtime tab, first select the view TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window)




d. To export the certificate on file system, choose pushbutton Export and enter any file name. This certificate has to be imported into the monitored systems, refer to Setup of Single Sign-On on Monitored Systems [on page 17].

Login Modules

1. Allow J2EE Engine to create and accept SSO tickets


b. Navigate to Server → Services → Security Provider

c. Choose SAP-J2EE-Engine (Components window) and open the Authentication tab

d. Choose the pushbutton Add New to add the following login modules (if not already available), for Flag choose ‘SUFFICIENT’:

� ClientCertLoginModule

� CreateTicketLoginModule

� CredentialsMappingLoginModule

� EvaluateAssertionTicketLoginModule

� EvaluateTicketLoginModule

� SecuritySessionLoginModule


Creation of Role for ABAP User


2.8 Creation of Role for ABAP User As of NetWeaver 2004 SP Stack 13, the according role SAP_SOLMANDIAG_SAPSUPPORT is part of SAP standard delivery. If required, the role can be created (name: Z_SAPSUPPORT) or verified manually as explained here.

In addition to the J2EE role, the SMD user needs an ABAP role on the monitoring system. Role name Z_SAPSUPPORT is recommended.

1. Call transaction PFCG

2. Enter Z_SAPSUPPORT in field Role

3. Choose pushbutton (Create Role)

4. In the next screen, click the Authorizations tab and choose pushbutton (Profile Generator expert mode)

5. By choosing pushbutton (Manual entry of authorization objects) and enter the following authorizations sequentially:

� S_ADMI_FCD authorization object that has to contain:

ACTVT: NADM, ST0R

� S_RZL_ADM authorization object that has to contain:

ACTVT: 01, 03

� S_RFC authorization object that has to contain:


Creation of Support Roles for J2EE Engine


ACTVT: 16 RFC_NAME: RFC1, SAL_RFC, SALF, SALS, SCSMROUTE, SDIFRUNTIME, SYFU, SYST RFC_TYPE: FUGR

� S_TCODE authorization object that has to contain:

TCD: DB59, DB6COCKPIT, ST04M, ST04_MSS,OS07, RZ20, ST03G

6. Choose pushbutton (Generate), as a result you will get the technical name of the generated profile

7. Return with the F3 key and choose the Users tab

8. Assign the SMD user (e.g. SAPSUPPORT) to the generated profile by choosing the User comparison pushbutton

For enabling Single Sign-On, the user names for SMD (refer to Setup of Single Sign-On on Monitored Systems [on page 17]) and the monitored systems have to be identical. SAPSUPPORT is the recommended user name.

2.9 Creation of Support Roles for J2EE Engine As of NetWeaver 2004 SP Stack 13, the according role SAP_JAVA_SUPPORT is part of SAP standard delivery. SAP_JAVA_NWADMIN_CENTRAL_READONLY is part of SAP standard delivery as of SP Stack 12. If required, these roles can be created or verified manually as explained here.


Creation of Support Roles for J2EE Engine


All users for Solution Manager Diagnostics have to be assigned to the role SAP_JAVA_SUPPORT.

1. Open the User Management menu within the local J2EE Engine: http://<host>:5<instance no.>00, navigate to User Management

2. Login as J2EE administrator

Navigate to Search and choose Get role.

3. Create role SAP_JAVA_SUPPORT, go to the tab Assigned Actions and in Available Actions choose the role action sap.com_com~sap~tc~webdynpro.Administrate. Choose the Add pushbutton. SAPSUPPORT is recommended as user name:

4. Create role SAP_JAVA_NWADMIN_CENTRAL_READONLY within user management, add the role actions

� UME.Read_All

� tc~lm~webadmin~permissions.Applications_Display

� tc~lm~webadmin~permissions.LocalSLD.Display

� tc~lm~webadmin~permissions.Log_Display

� tc~lm~webadmin~permissions.Monitoring_Display


Connection to NWA


� tc~lm~webadmin~permissions.Performance_Display

� tc~lm~webadmin~permissions.SystemInfo_Display

� tc~lm~webadmin~permissions.User_Access_All

� tc~lm~webadmin~permissions.WebAdmin_Central

and apply the roles to the user created for SMD. SAPSUPPORT is recommended as user name:

5. Verify that the Solution Manager Diagnostics users are member of both roles SAP_JAVA_SUPPORT and SAP_JAVA_NWADMIN_CENTRAL_READONLY:

2.10 Connection to NWA This operation is performed automatically by the Monitoring System Setup Wizard but can be performed manually as well.

If a SAP NWA (NetWeaver Administrator) system is installed in your solution landscape, the Solution Manager Diagnostic should be connected to this system to integrate the NWA monitoring capabilities into SMD. Proceed as follows:

1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running

2. Navigate to Server → Services → Configuration Adapter


Connection to NWA


3. In the Display configuration tab, open the branch for apps → sap.com → tc~webadministrator~navigation~ejb → appcfg

4. To switch to edit mode, choose the pushbutton (Display/Change); you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton.

5. To modify data, choose the pushbutton (Change) or just double-click on Propertysheet application.global.properties

6. Now you can change customizing entries by positioning the mouse pointer to the line where you find the information that has to be adapted

7. A single mouse click will open a new window where you can change the configuration data

� Description: text information for the selected item (cannot be changed)

� Name: name of the property (cannot be changed)

� Datatype: data type of the property item (cannot be changed)

� Default: SAP-delivered value (cannot be changed)

� Custom: if this field contains a value, the default value

8. The following parameters should be modified to match the NetWeaver Administration Console:

Name SAP default Example Description

nwahost protocol://host:port http://p135809.wdf.sap.corp:2040

By default the nwahost will be setup to http://<smdserver>:<smdport>

Server & port where the NWA is running

The protocol can be https or http. If no protocol is specified, http:// will be added by SMD

Use fully-qualified host names

nwaadmin Administrator The administrator of the SAP NetWeaver administration server

nwauser Password The administrator of the SAP NetWeaver Administration server

9. To save modified parameters, choose the Apply custom pushbutton


Storing Introscope Webview parameters in SMD configuration


2.11 Storing Introscope Webview parameters in SMD configuration

a. Start the Visual Administrator on the SMD Server

b. Navigate to Configuration Adapter → apps/sap.com/tc~webadministrator~navigation~ejb/appcfg/application.global.properties

c. Change the value of the wahost key to the value of the WebView URL. ex: http://NCED60137394A.ncel.sap.corp:53000

2.12 Storing Introscope Enterprise Manager parameters in SMD configuration

The introscope Enterprise Manager parameters are stored in the configuration of the agent application com.sap.smd.agent.application.global.configuration, with scope 'global'.

• wily/em/host: host of the introscope Enterprise Manager.

• wily/em/port: port of the introscope Enterprise Manager.

• wily/em/user: administrator user of introscope Enterprise Manager.

• wily/em/password: password of administrator user of introscope Enterprise Manager.

Manual Setup Tasks on Monitored Systems November 2006

Introduction


3 Manual Setup Tasks on Monitored Systems

3.1 Introduction The Managed setup wizard performs automatically ALL setup and configuration steps as described in the E2E diagnostics setup guide. This chapter describes the corresponding manual procedures.

The information contained in this chapter is intended for Solution Manager administrators to perform manually the setup procedure.

Step Description Manual Description

Java Parameter Settings on Monitored J2EE Engines

Chapter 3.2

Setup of Single Sign-On on Monitored Systems

Chapter 3.3

Assignment of J2EE Server Roles to the Support User

Chapter 3.4

Setup of HTTP Analysis

Chapter 3.5

Initialization of the Scheduler Chapter 3.6

Setup of Tasks

Chapter 3.7

3.2 Java Parameter Settings on Monitored J2EE Engines

For performance analysis of monitored J2EE Engine, the output of garbage collections is required. Proceed as follows:

1. Start the J2EE Configtool where the monitored system is running

2. For each server node, navigate to cluster-data → Instance_<ID> → Server_<ID>

3. In the General tab, apply the Java parameters

� -verbose:gc

� -XX:+PrintGCTimeStamps

4. Choose the Save pushbutton to save the configuration, restart the server node(s)

3.3 Setup of Single Sign-On on Monitored Systems The certificates created within the J2EE Engine of the Solution Manager Diagnostics server (refer to Setup of Single Sign-On on SMD Server [on page 8]) have to be imported into the monitored SAP systems. The procedure is different for ABAP systems and systems with active J2EE Engines.




- Use full-qualified host names, e.g. p135809.wdf.sap.corp - If you are running a Web AS with both active ABAP and J2EE components, you have to import the certificate for both components - This procedure is valid for 6.40 J2EE Engines

Configuration

1. Importing the certificate on J2EE system:

a. Start the Visual Administrator and log on to the J2EE Engine of the monitored system (e.g. Enterprise Portal)

b. Navigate to Server → Services → Key Storage

c. In the Runtime tab, first select TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window)

d. To import the certificate from file system, choose the pushbutton Load. For exporting certifcates from SMD, refer to refer to Setup of Single Sign-On on SMD Server [on page 8]

e. Restart the J2EE Engine of the monitored system

2. Allow J2EE application (e.g. Enterprise Portal) to accept SSO tickets:

a. Start the Visual Administrator and log on to the J2EE Engine of your monitored system

b. Navigate to Server → Services → Security Provider

c. Choose SAP-J2EE-Engine (Components window) and open the Authentication tab

d. Choose the pushbutton Add New to add the following login module:

� EvaluateTicketLoginModule

e. Choose ticket in window Components

f. In the Authentication tab, choose Login Module:

� com.sap.security.core.server.jaas.EvaluateTicketLoginModule

g. To add properties, choose the pushbutton Modify




� ume.configuration.active: true

� trustediss1: CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1

O=<company>,C=<country> are optional

� trusteddn1: CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1

O=<company>,C=<country> are optional

� trustedsys1: <SID of Solution Manager Diagnostics>,<client ID> e.g. WA1,169

Confirm settings with the OK pushbutton.

Now change the Authentication Template for the following applications in the Components window to ticket (drop-down box):

� sap.com/SQL_Trace*OpenSQLMonitors (SQL Trace)

� sap.com/SQL_Trace*OpenSQLTrace (SQL Trace)

� sap.com/tc~monitoring~systeminfo*sap_monitoring (Systeminfo)

� sap.com/tc~wd~dispwda*webdynpro_dispatcher (Web Dynpro Console)


Assignment of J2EE Server Roles to the Support User


� sap.com/tc~wd~dispwda*webdynpro_welcome (Web Dynpro Console)

3.4 Assignment of J2EE Server Roles to the Support User

To enable access to the J2EE applications for SQL Trace, System Info and SAP XI, J2EE Server Roles have to be assigned.

Component Overview

For monitored SAP J2EE Engines 6.40 up to SP Stack 14:

Component Role

sap.com/ tc~monitoring~systeminfo*sap_monitoring

SystemInfo_Support_Role

sap.com/ SQLTrace*OpenSQLMonitors component

OpenSQLMonitorLogonRole

For monitored SAP J2EE Engines 6.40 as of SP Stack 15:

Component Role

SAP-J2EE-ENGINE SAP_JAVA_SUPPORT

For monitored SAP J2EE engines running on XI:

Component Role

sap.com/com.sap.xi.repository*rep display

sap.com/com.sap.xi.directory*dir display

sap.com/ com.sap.rprof.remoteProfile* exchangeProfile

display

sap.com/com.sap.xi.rwb*rwb display

sap.com/com.sap.xi.mdt*mdt display

sap.com/com.sap.aii.af.cpa.app*CPACache xi_af_cpa_monitor

sap.com/ com.sap.aii.af.app*AdapterFramework

xi_af_adapter_monitor

sap.com/ tc~TechSrv~XML_DAS*DataArchivingService

XMLDASSecurityRole

Example for Role Assignment

To grant the role SystemInfo_Support_Role, start the J2EE Engine Visual Administrator tool on the monitored J2EE system:

1. navigate to Server → Services → Security Provider

2. select component sap.com/tc~monitoring~systeminfo*sap_monitoring

3. navigate to tab Security Roles

4. select security role SystemInfo_Support_Role

5. use the Add pushbutton to add the SAPSUPPORT user to this role


Setup of HTTP Analysis


3.5 Setup of HTTP Analysis The SMD application HTTP Analysis uses a plug-in (can be downloaded within the application, updates are available in SAP Note 834568) for the web browser to log the requests and responses between the browser and the SAP Enterprise Portal. The user interface of HTTP Analysis displays detailed performance-related information graphically.

The SAP Note 943708 contains all information related to the manual setup of the HTTP trace activation.

Activating HTTP log information on J2EE Engine 6.40 (all SP Stacks)

1. Start the Visual Administrator and log on to the J2EE Engine of the Enterprise Portal

2. Navigate to Server → Services → Log Configurator

3. In the Categories tab, open Log Controller Root Category → System → HTTPAccess → Access

4. Set Severity to Info and apply this setting to all cluster nodes by choosing the Save pushbutton

5. Start the J2EE Configtool of the Enterprise Portal

6. Navigate to cluster-data → Instance_<ID> → Server_<ID> → Services → http

7. Apply the following parameters by entering into the Value field:

� LogHeaderValue: X-CorrelationID

� LogResponseTime: true by choosing the Set pushbutton after every change


Initialization of the Scheduler


In case you want to compare the HTTP message headers between client and server (e.g. to find out if proxy servers, IIS, or firewalls modify HTTP headers), then you have to switch on parameter LogRequestResponseHeaders in addition: LogRequestResponseHeaders = true

8. To persist all customized settings, choose the pushbutton (Save)

9. Navigate to Server → Services → HTTP Provider

10. In the Runtime tab, open tab Virtual Hosts → General

11. Make sure that parameter Log Responses is checked

12. To persist all customized settings, choose the Save properties pushbutton

3.6 Initialization of the Scheduler The SMD Scheduler’s purpose is to retrieve data from system landscapes connected to the SMD Server. The tasks are scheduled on a regular basis.

To open the SMD Scheduler, start the SMD application (http://<host>:<port>/smd � Diagnostics Administration � Managed Systems � Scheduler)

You have to log on as J2EE administrator to the SMD Administration application.

• Choose the pushbutton Default Setup in the Scheduler window. This will trigger all required tasks.

This button is available only if no task is created in Scheduler.

3.7 Setup of Tasks After a new system is connected to the SMD Server, tasks have to be configured.

Press the Host List tab to get the list of monitored hosts from Solution Manager Diagnostics.


Setup of Tasks


• Select the host to monitor

• Press the Add All Tasks button. Afterwards, you should see the following screen:

The next step is to schedule these tasks.

Manual Setup of SMD Agent November 2006

Command Line Execution


4 Manual Setup of SMD Agent The SMD Agent is configured by SAPinst as described in the Diagnostics setup guide but can be re-configured manually as well.

The SMD Agent is a Java application running on the monitored systems and gathering information for the SMD Server.

This chapter contains detailed information for setup of applications running within the SMD Agent.

4.1 Command Line Execution smdsetup <path of JVM 1.4> <host name or ip adr. of SMD Server> <P4 port> <admin. user> <pwd.>

c: cd \usr\sap\SMD\J97\SMDAgent smdsetup.bat C:\j2sdk1.4.2 p135809.wdf.sap.corp 50004 SMD_ADMIN pwd

4.2 SMD Agent Setup Steps When running properly, the SMD Agent setup output looks like the example below: --------------------------------------------------------------------- SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG --------------------------------------------------------------------- SMD Agent Setup is in process --------------------------------------------------------------------- - STEP 1: checking JDK location JDK location is consistent: C:\j2sdk1.4.2_04\bin - STEP 2: checking JDK Version JDK Version is correct: 1.4.2_04-er - STEP 3: checking Connection to SMD Server SMD Server check completed successfully - STEP 4: generating Runtime Properties runtime.properties has been created. - STEP 5: generating Launcher smdagent.bat has been created. smdagent.sh has been created. - STEP 6: generating SecStore secstore.properties: has been created. secstore.properties: user has been set. secstore.properties generation completed successfully. - STEP 7: checking P4 Connection and SMD Agent Registration SMD Agent Registration succeeded --------------------------------------------------------------------- SMD Agent Setup completed successfully ---------------------------------------------------------------------

The different operations performed are the following:

• Step 1: checks the location of the Java Virtual machine 1.4.

Agent configuration and Administration November 2006

SMD Agent Start Profile


• Step 2: makes sure the Java Virtual machine is compliant with the SAP J2EE Security libraries.

• Step 3: makes sure the SMD Server machine (host name) is visible and waiting on the P4 port specified.

• Step 4: generates a runtime.properties file to persist the parameters specified.

• Step 5: generates the scripts used to start the SMD Agent. As of SMD Agent SP 15 these scripts are obsolete, as the JStartup Framework is used for the startup.

• Step 6: generates SecStore file required for establishing a secure connection to the SMD Server.

• Step 7: checks the generated runtime environment and clearly shows whether the SMD agent registration to the SMD Server can be done. This registration relies on the SAP J2EE P4 protocol.

4.3 SMD Agent Start Profile It is possible to modify the startup parameters of the SMD Agent, to change memory setting, etc. The startup profile is located under /usr/sap/SMD/J<NN>/profile/smd.properties.

Example Profile

#-------------------------------------------------------------------- # SMD AGENT instance properties # Created on Tue Oct 25 13:21:54 CEST 2005 #-------------------------------------------------------------------- smdagent.name=SMDAgent smdagent.type=server smdagent.rootPath= ../SMDAgent smdagent.classPath =lib/launcher/smdagentlauncher.jar:lib/launcher/logging.jar smdagent.mainClass = com.sap.smd.agent.launcher.SMDAgentLauncher smdagent.parameters = run jcontrol smdagent.javaParameters = -Xmx128m -Xms128m smdagent.ShutdownTimeout=10000 smdagent.Id=1 smdagent.DebugMode=no smdagent.DebugPort=58021 smdagent.Debuggable=yes

After changing its profile, the SMD Agent has to be restarted.

5 Agent configuration and Administration

5.1 Change Credentials of SMD Agent To change the logon credentials used by the SMD Agent to logon to the Monitoring System (SMD Server), access the SMD Administration application (http://<host>:<port>/smd � Diagnostics Administration � Managed Systems � Agent administration)

Agent configuration and Administration November 2006

SSL Setup for SMD Agent



Navigate to tab Agent Administration � Agent Credentials.

Enter the current user and the password used by the SMD Agent, and enters the new user and password. The new J2EE user must have an Administrator role or to be a member of the group Administrators.

Before applying the change, it is important that all SMD Agents are online and connected to the Monitoring System. All agents that are not connected during the password change have to be changed manually as explained in Command Line Execution [on page 24]. It is recommended to create a dedicated J2EE administrator on the SMD Server, used by SMD Agents (e.g. SMD_ADMIN). Otherwise you risk locking the ‘main’ J2EE administrator by unsuccessful login attempts (if wrong password provided) of SMD Agents.

5.2 SSL Setup for SMD Agent

Prerequisites

Configure the SAP J2EE Engine of the SMD Server to receive P4 SSL calls. Refer to the SAP Help Portal (http://help.sap.com/saphelp_nw04s/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm) for detailed information

Setup

By default, the communication between the SMD Agents and the Monitoring System (SMD Server) is established via the P4 protocol (unsecured).

To enable secure communication, the SSL transport must be configured between the SMD Agent and the SMD Server. Two types of installation are possible:

1. The SMD Agent has a separate JDK (used by the SMD Agent exclusively)

a. Configure the JDK to use SSL libraries: Add the iaik libs in the JRE\lib\ext folder of the JDK of the SMD Agent: iaik_jce.jar iaik_jsse.jar iaik_ssl.jar

Configuration of SMD Agent Applications November 2006



The jre\lib\security folder might contain local_policy.jar and US_export_policy.jar

b. Configure the SMD agent to use SSL: Add the property smd.agent.connection.transport=ssl in \usr\sap\SMD\JXX\SMDAgent\configuration\runtime.properties and modify the property smdserver.port to match the P4 SSL port. (5xxx6 by default)

c. Restart the SMD Agent

2. The SMD Agent uses a common JDK (used by other components as well)

a. Configure the SMD Agent profile to use SSL libraries:

� the SAP installations uses the same JDK that is already configured for SSL:

• if the server hosts a central (main) instance: - location of the iaik libs: /usr/sap/<SID>/sys/global/security/lib/tools - add the path to the iaik files to property smdagent.classPath in the SMD Agent profile at /usr/sap/SMD/J<instance no.>/profile/smd.properties

• if the server hosts a dialog instance: - location of the iaik libs: <J2EE_HOME>/sys/global/security/lib/tools - add the path to the iaik files to property smdagent.classPath in the SMD Agent profile at /usr/sap/SMD/J<instance no.>/profile/smd.properties

� the SAP installations is not configured for SSL:

• you can use either the first point in option 2.a or configure the JDK exclusively for the SMD Agent.

Make sure that you don’t run into combatibility problems when the SSL configured JDK is used by other applications as well!

b. Configure the SMD agent to use SSL: Add the property smd.agent.connection.transport=ssl in \usr\sap\SMD\JXX\SMDAgent\configuration\runtime.properties and modify the property smdserver.port to match the P4 SSL port. (5xxx6 by default)

c. Restart the SMD Agent

6 Configuration of SMD Agent Applications This section explains the individual setup of applications that are running within the SMD Agent.

All SMD Agent applications are configured automatically during the step initial Setup of SMD Agent Applications.




The following setup steps have to be performed only when the automatic configuration failed or has to be customized.

Prerequisites

Initial Setup of SMD Agent Applications has to be executed before. The SMD Agents have to

be in status (started) – what can be verified in tab Agent Administration, sub-tab Agents of the SMD Administration application.

Setup Steps

Start the SMD Administration application (http://<host>:<port>/smd � Diagnostics Administration � Managed Systems � Agent administration)


Navigate to tab Application Configuration.

Example screenshot of the Application Configuration screen:

Overview of the Agent Application Configuration

Each application running in the SMD Agent has its own configuration stored centrally in the SMD system.

The configuration can have two different scopes:

• Global: The configuration is common and shared by all SMD Agents connected to SMD

• Host: The configuration is available for a specific host only

The SMD Agent infrastructure stores the configuration of the remote agent applications secured and publishes this configuration to the connected SMD Agents. When an agent application gets its configuration from the SMD Server, its configuration is the merger of the values defined for the Global and the Host scope.




Furthermore, a global configuration named com.sap.smd.agent.application.global.configuration is available for all agent applications and is maintained by the SMD infrastructure. Therefore, a remote agent application has access to its own configuration or the global configuration.

For SMD SP Stack 09, the following agent applications can be configured:

Application Name SMD Use Case

com.sap.smd.agent.application.connectors Provide P4 or JMX connection to the monitored SAP J2EE engine

com.sap.smd.agent.application.telnet Provides remote access to the J2EE telnet console for the SMD J2EE command console application

com.sap.smd.agent.application.remoteos Provides remote access of J2EE standalone logviewer to log files for SMD application Log Display

com.sap.smd.agent.application.database Access to the DB of the remote system to return table information to the SMD SQL Command Console application

com.sap.smd.agent.application.global.configuration Global configuration of the SMD Agents

com.sap.smd.agent.application.logviewer Provides an access to the file system of a monitored system. Files can be displayed or downloaded

com.sap.smd.agent.application.ldap

Manual configuration is required.

Provides remote access to connect to a LDAP server for the SMD LDAP browser application

com.sap.smd.agent.application.datacollector Collects XML based data from monitored systems (replaces the Component Analyzer download feature)

com.sap.smd.agent.application.filesystem Provides access to the remote file system for the SMD File System Browser application, and the Gather/Upload functionality

com.sap.smd.agent.application.switch Used for the migration between SAP NetWeaver 2004 to 2004s

com.sap.smd.agent.application.portalactivityreport Retrieves data for Portal Activity Reporting (PAR) from monitored SAP Enterprise Portals

com.sap.smd.agent.application.remotesetup Enables to setup the J2EE engine of a monitored system


J2EE Command Console Configuration


for SMD usage, from the smd/admin application

A property editor is used to change the configuration for SMD Agent applications.

After choosing the Edit pushbutton, you can change the property values in the Custom Value field. The default value delivered by the agent application is always displayed in the Default Value column. To change a property to its default value, choose pushbutton Reset Property or Reset All.

The Add Property pushbutton will open a popup window where the following fields can be entered:

Field Description Comment

Property Name The name of the property

Property Value The value of the property

Property Attribute Indicates if the property is secure or not

In the case of a secure property, the value is not displayed in the screen.

Choose the Save pushbutton to store the configuration and send it to the selected SMD Agent.

6.1 J2EE Command Console Configuration This application provides access to a read-only set of J2EE commands on the monitored hosts used by the J2EE command console application. The telnet protocol is used for this application.

Configuration

Configure the following parameters:

Application Scope Name Description

global.configuration host <sid>/sapj2ee/admin/user The SAP J2EE admin user with telnet execution rights

global.configuration host <sid>/sapj2ee/admin/pwd

telnet host <sid>/sapj2ee/telnet/port J2EE telnet port 5<instance no.>08, e.g. 50008

telnet Global or by host

<command name> True if the command is allowed, false otherwise

Cluster Consideration: In a cluster, only the SMD Agent running on a host with dispatcher node needs to be configured.

Commands

By default, all J2EE telnet commands are allowed except the following ones (they are set to false):

• APPLICATION_ALIAS


File System Access Configuration


• ATTR

• CACHE [-l]|[-list] [-r]|[-hitrate]

• CLEAR_HTTP_CACHE

• HOST

• HTTP_ALIAS

• INTERNAL_LOCKS [-l]|[-list]

• MENV

• SET

• TEST_DS

Since SMD SP 15, it is possible to disable particular parameters of a telnet command with the syntax: /-<parameter>/

Enabling command CLEAR_HTTP_CACHE and disabling the parameters /-l/ /-list/ /-r/ /-hitrate/ for command CACHE:

6.2 File System Access Configuration With this application the file system of a monitored system can be browsed. Files can be displayed or downloaded.

Configuration



filesystem host root_directories A comma separator list of root folders accessible by SMD applications (e.g. File System Browser, Thread Dump


SQL Command Console Configuration


Analyzer) on the monitored host.

If the value of this property is empty, access is restricted to folder usr/sap.

If root directories are modified, at least the SAP root directory (X:/usr/sap, where X: is the installation drive on Windows systems) must be part of the list. For multi drive installations, all SAP directories must be part of the list (e.g. C:/usr/sap, D:/usr/sap, etc.).

6.3 SQL Command Console Configuration To enable the execution of queries by the SQL Command Console, the database application has to be configured.

Configuration



database host <SID>|config.db.driverclass

The class of the JDBC driver to use to connect from the SMD agent to the remote DB

database host <SID>|config.db.driverjars

The jar files containing the JDBC driver to use for the connection from the SMD agent to the remote DB

- the location of the files refers to the server where SMD Agent runs (monitored system) - separate files by semicolon ( ; ), e.g. E:\jars\base.jar; E:\jars\sqlserver.jar

database host <SID>|config.db.user

The user to use for the DB connection

database Host <SID>|config.db.password

The password of the user

database Host <SID>|config.db.url

The URL of the DB.

<SID>|config.db.driverclass

MS SQL SERVER com.ddtek.jdbc.sqlserver.SQLServerDriver


SQL Command Console Configuration


Oracle oracle.jdbc.driver.OracleDriver

MAX DB com.sap.dbtech.jdbc.DriverSapDB

DB2 com.ibm.db2.jcc.DB2Driver

If the database running on 6.20, you will find the corresponding Java files (extension: .jar) at: <J2EE_HOME>/cluster/server/additional-lib/com/sap/data_direct_driver_references

If the database running on 6.40, you will find the corresponding Java files (extension: .jar) at: <J2EE_HOME>/cluster/server<n>/bin/ext/com.sap.datadirect (MS SQL Server) or <MaxDB home directory>/programs/runtime/jar (MaxDB). The driver for Oracle is part of the Oracle client (db-dependent part of the ABAP kernel).

<SID>|config.db.driverjars

MS SQL SERVER base.jar, sqlserver.jar, util.jar

Oracle classes12.jar

MAX DB SAPDBC.JAR

DB2 db2jcc.jar, db2jcc_license_cu.jar

<SID>|config.db.user/password

Enter User and Password of the database schema owner SAP<SID>DB, e.g. SAPP62DB

<SID>|config.db.url

MS SQL SERVER jdbc:datadirect:sqlserver://<host>:<port>;DatabaseName=<SID> e.g. jdbc:datadirect:sqlserver://p78293:1433;DatabaseName=P62

Oracle jdbc:oracle:thin:@<host>:<port>:<SID> e.g. jdbc:oracle:thin:@us7201:1527:EP0

MAX DB jdbc:sapdb://<host>/<SID> e.g. jdbc:sapdb://P114280/TYR

DB2 jdbc:db2://<host>:<port>/<SID> e.g. jdbc:db2://P114280:5912/TYR

Starting from SP17 the old format properties (user, url, driverclass, driverjars, password) is not supported anymore. The database configuration task is migrating each of the old properties to the new format <SID>|config.db.<oldpropertyname>.


OS Command Console Configuration


As the configuration task is not available in 620 the migration is not performed and the new properties have to be created manually and filled with the correct values.

6.4 OS Command Console Configuration OS Commands Console allows to execute operating system commands by the SMD Agent user.

On the monitored system, the user may not have rights to execute all commands. Before using OS Command Console, you should configure correctly SMD Agent user on each monitored system.

Configuration



remoteos host oscommand.unix.shell.command

The shell used by Os Command Console on an UNIX monitored system

All commands are describe in resource oscommand.xml delivered with application com.sap.smd.agent.application.remoteos. To configure the following parameters please download the file, edit parameters and then upload it again in your Application Configuration.

Tag Description Example

Cmd name

Name of the command available in the OS Command Console application

IP Config

Cmd desc Explanation of the command Displays all current TCP/IP network configuration values.

OsCmd ostype

Valid Operating System for the command

WINDOWS

OsCmd exec

Execution string for the command on OS level

ipconfig

OsCmd path

Location of the command (if not in standard search path)

c:\Windows\system32

OsCmd param

“true”: parameters are allowed

“false”: parameters are not allowed

true

OsCmd runtime

Timeout value in seconds 5

Exclude param

If parameters are allowed in general (see tag param), particular parameters can be excluded

^(/|-)(renew|release)$

Help ref Reference the command which need to be executed to get help content

You can put the help content directly under tag Help (remove attribute ref) If this tag is not available the help content would be the Cmd desc value

IOStatHelp


Log Viewer Configuration


Each command defined in file oscommand.xml should be in the SMD Agent user path and has to be accessible by this user only.

6.5 Log Viewer Configuration The Log Viewer application of the SMD Agent will start the J2EE Standalone Logviewer on the monitored system (if available).

Configuration



logviewer host Logviewer_MonitorablePath This parameter has no meaning for SMD Agent SP 15 (reserved for future usage)

logviewer host Logviewer_NI_Port NI port of the Standalone Logviewer

logviewer host default.log.pattern Specifies which log file extendsion the logviewer server can read, separate by using a comma,

e.g. *.log, *.trc

6.6 LDAP Browser Configuration

This step has to be performed when a LDAP system should be connected to Solution Manager Diagnostics. It allows browsing the LDAP only.

Navigate to tab Agent Administration and then sub-tab Application Configuration and click on com.sap.smd.agent.application.ldap. The system where LDAP is running and a SMD Agent is installed can be selected from drop-down box Scope.

Enter the following data:

Name Description

ldap.hostname Full qualified name of LDAP Server

ldap.port LDAP server port

ldap.user Use which have credentials to read the data in LDAP Server

ldap.pwd Password, can be hidden by choosing the Secure Property option

Configuration of Introscope Agents November 2006

ISAdmin


7 Configuration of Introscope Agents This section explains the setup of the introscope agents

7.1 ISAdmin The application used to setup the ISAgent is started from the Administrator SMD menu: (http://<host>:<port>/smd � Setup And Configuration �� Managed Systems � Introscope Agent)

This application only performs the ISAgent Setup on the Managed Systems. The Diagnostics Setup still needs to be done manually.

7.1.1 Enterprise Manager Settings The setup of the Wily Enterprise Manager (EM) is a prerequisite. This step is not in the scope of this document.

ISAgent connects to the EM Host to report metrics.

EM Settings are normally specified during the SMD Monitoring Setup.

If the EM settings have not been set properly the ISAdmin UI let the chance to change them.

7.1.2 Introscope Agent Settings The ISAdmin UI let the administrator check the current settings of the Monitored Systems. The dropdown listbox let the user select the Solution/Landscape/SID. The corresponding J2ee Server nodes are then displayed in the table.

The third column (green flag) informs whether the SMD Agent is up and running.

The ISAgent settings displayed are:

The ISAgent Profile

The ISAgent Name


ISAdmin


The ISAgent Version which is not the version of the Wily binaries but the version of the SAP Instrumentation (*)

The ISAgent state (**)

(*) The ISAgent Version is decorated with a ”≠” icon to inform that the current version differs from the one delivered with SMD.

Please keep in mind that installing a new SMD Version preserves the previous settings. It is necessary to perform the ISAgent setup again to switch to the new version!

(**) The ISAgent state informs whether the setup is already in use by the Monitored System. It is important to understand that the whole j2ee engine must be restarted to take the latest settings into account.

7.1.3 J2ee Node Information Details The ISAdmin UI can display more information details about the j2ee server nodes.

Remarks:

The JDK Location is used to generate Wily Connectors. Changing the JDK may require to perform the setup again!

EM Settings are displayed to make sure they match the one specified during the SMD Setup.

Wily Version is the version of the Wily binaries. The information is extracted from the manifest shipped in the Agent.jar File.

The Introscope Agent Version is SAP-specific since the SAP-specific Instrumentation may change while using the same Wily binaries.

7.1.4 Introscope Agent Setup The administrator can change or disable the current settings.


ISAdmin


Pressing the Setup button opens a additional form where the admin has the ability to select:

The ISAgent Version

The ISAgent Profile

The Setup can be applied to several j2ee Server Nodes in one shot. The Admin must to select the relevant nodes by checking the checkbox in the table.

7.1.5 Last Operation Results Each time the user performs an operation the ISAdmin UI displays the result in a Table Tree control. The user can drill-down the Tree to check each step and make sure the setup has been properly performed.

7.1.6 ISAgent Setup Prerequites The ISAgent Setup prerequisites are:

SMD Agent matching the selected J2ee Node must be up and running.

The J2ee Dispatcher Node must be running as well (for P4 connection)


ISAdmin


In the screenshot below the “Red Flag” denotes that the SMD Agent (or the remote Wily Admin Agent Application) is stopped.

In such situation the “Last Operation Results” may provides more details.

7.1.7 ISAgent Settings Restrictions The ISAgent Setup has some restrictions.

The ISAgent Setup can not be done against Monitored Systems running SAPJ2EE 6.20. ISAdmin only supoprts NW04 and NW04s components.

It is necessary to manually install an additional application on the Monitored System to enable the report of some additional metrics via JMX. The application is shipped with SMD and can be found (after the Setup) on the monitored file system at:

\usr\sap\SMD\J<##>\SMDAgent\applications.config\com.sap.smd.agent.application.wily\ISAgent\ <ISAgent Version>\jmx\JmxService7.0NetWeaver.ear

The Setup of IPC Server Nodes is not yet supported.

7.1.8 ISAgent Troubleshooting In case of problem please check the ISAgent log file at:

\usr\sap\<SID>\J<##>\j2ee\cluster\server<#>\IntroscopeAgent.<SolutionName> _<SID>_server<#>.log

For instance:

C:\usr\sap\J2E\J02\j2ee\cluster\server0\IntroscopeAgent.ZEUS_J2E_server0.log

This log file only exists if the SAPJ2EE Engine has been restarted.

To make sure ISAgent Setup has been properly done please start the Wily WebView and check whether metrics coming from the Monitored Systems are available.


ISAdmin


7.1.9 ISAgent Known Issues The JDK used to start the SAPJ2EE Engine must be specified in the J2EE Engine Configuration. This can be checked using the Offline Config Tool.

Please select the Instance:

Make sure the “Java Home” field is not empty in the “Bootstrap Java Settings” group.

When the JDK Version is not set the ISAgent Setup cannot complete. It will fail because it won’t be able to generate the “Wily Introscope Agent Connector”.

7.1.10 ISAgent Upgrade The Screenshot below shows an upgrade use-case. ISAgent was already setup on the NXI Monitored System. We can see here that the setup has been done manually (using the SAP Note 797147).

The ISAgent has been deployed at:

/usr/sap/ccms/wily7.0_official

The ISAdmin UI informs the user that the current running version is not the one delivered by SMD. The Administrator tried to setup ISAgent with the latest version but the setup failed during the “Introscope Agent Connector Generation”. The feedback shows that the location of the JDK used by the Engine is not set:

CreateProcess: <unspecified>\bin\java -jar CreateAutoProbeConnector.jar


Configuration of EP Agents


7.2 Configuration of EP Agents This section explains the setup of the EP agents

7.2.1 EPAdmin The application used to setup the EPAgent can be started using the diagnostics administrator menu: (http://<host>:<port>/smd � Setup And Configuration �� Managed Systems � EP Agent)

This application only performs the EPAgent Setup on the Managed Systems. The diagnostics Setup still needs to be done manually.

7.2.2 Enterprise Manager Settings The setup of the Wily Enterprise Manager (EM) is a prerequisite. This step is not in the scope of this document.

EPAgent connects to the EM Host to report metrics.

EM Settings are normally specified during the SMD Monitoring Setup.

If the EM settings have not been set properly the ISAdmin UI let the chance to change them.

7.2.3 EPAgent Settings The EPAdmin UI let the administrator check the current settings of the Monitored Systems. The dropdown listbox let the user select the Solution/Landscape/SID. The corresponding Hosts are then displayed in the table.




The third column (green flag) informs whether the SMD Agent is up and running.

The EPAgent settings displayed are:

The Startup Type

The EPAgent Version (*)

The EPAgent state (**)

(*) The Running EPAgent Version is decorated with a ”≠” icon to inform that the running version differs from the one delivered with SMD.

Please keep in mind that the installing a new SMD perserves the previous settings. It is necessary to perform the EPAgent setup again to switch to the new version!

(**) The EPAgent state informs whether the setup has already performed and thus whether EPAgent is running. Unlike the Wily Introscope Agent is is NOT NECESSARY to restart the monitored system after applying new settings.




7.2.4 Host Information Details The EPAdmin UI can display more information details about the Monitored Hosts.

Remarks:

EM Settings are displayed to make sure they match the one specified during the SMD Setup.

Wily Version is the version of the Wily binaries. The information is extracted from the manifest shipped in the Agent.jar File.

The EPAgent Version is SAP-specific and informs about the version of SAP Plugins.

NetWeaver04s SP9 includes to SAP Plugins:

SAP_GC: a Garbage Collection Output Scanner)

SAPOSCOL: a plugin relying on saposcol.exe to retrieve system information

7.2.5 EPAgent ToolBar The toolbar let the admin perform operation against the selected hosts.

If the EPAgent setup has already been done the admin can then Start, Stop and Retart the EPAgent.

7.2.6 EPAgent Setup Pressing the “Setup…” button opens a additional form where the admin has the ability to select the EPAgent Version he/she wants to deploy.

7.2.7 Last Operation Results Each time the user performs an operation the EPAdmin UI displays the result in a Table Tree control. The user can drill-down the Tree to check each steps and make sure the operation has been properly performed.




7.2.8 EPAgent Setup Prerequites The EPAgent Setup prerequisites are:

SMD Agents matching the selected Hosts must be up and running.

In such situation the “Last Operation Results” may provides more details.

7.2.9 EPAgent Options Like Windows NT Services the EPAgent “Startup Type” can be set to:

Automatic … EPAgent is automatically started by SMD Agent

Manual … EPAgent has to be started (and stopped) by the Administrator

Disabled … EPAgent cannot be started (to protect critical production systems).

Note that by default all hosts are inheriting their “Startup Type” from the global configuration of the “Wily Agent Application”. Selecting the “<default>” value restaure the inheritance!

7.2.10 EPAgent Settings Restrictions The EPAgent Setup has some restrictions.




The EPAgent Setup can not be done against Monitored Systems running SAPJ2EE 6.20. EPAdmin only supoprts NW04 and NW04s components.

7.2.11 EPAgent Troubleshooting In case of problem please check the EPAgent log file at:

\usr\sap\<SID>\J<##>\j2ee\cluster\server<#>\IntroscopeAgent.<SolutionName> _<SID>_server<#>.log

For instance:

C:\usr\sap\SMD\J90\SMDAgent\.\applications.config\com.sap.smd.agent.application.wily\EPAgent\7.0-200607061706

You should find at this location:

IntroscopeEPA.log This log let you check whether SAP-specific Plugin have been started

IntroscopeEPA.out The EPAgent output (stdout) is redirected to this file

IntroscopeEPA.err The EPAgent errors (stderr) are redirected to this file

advanced diagnostics setup guide as of sp09

Documents