solution manager diagnostic setup

SAP NetWeaver Guide

Supportability Setup Guide for Solution Manager Diagnostics SAP NetWeaver 04S SP Stack 06

Document Version 1 – January 23, 2006

SAP AG Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

© Copyright 2004 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. SAP Library document classification: PUBLIC 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 in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides

SAP Library document classification: PUBLIC

Typographic Conventions Icons

Type Style Represents

Example Text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as 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. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04S SP Stack 06

Supportability Setup Guide – Solution Manager Diagnostics SAP NetWeaver 04S SP Stack 06......................................................................... 6

1 Introduction....................................................................................................... 6 1.1 Naming Conventions.............................................................................................7

2 Installation – Step by Step............................................................................... 9 2.1 Matrix for Solution Manager Diagnostics Setup ...............................................10

Installation Matrix for a new SMD.......................................................................................................... 10 2.2 Matrix for Setup of Monitored Systems.............................................................10

Setup Matrix .......................................................................................................................................... 10 2.3 Matrix for Connection of Monitored Systems to SMD......................................11

Setup Matrix .......................................................................................................................................... 11 3 Installation Planning ......................................................................................12

3.1 Required Documentation....................................................................................12 3.1.1 SAP Installation Notes.................................................................................................................. 12 3.1.2 Information in the SAP Service Marketplace................................................................................ 13 3.1.3 Components for Problem Messages............................................................................................ 14

3.2 Hardware and Software Requirements for SMD ...............................................14 3.3 Software Requirements for Monitored Systems...............................................15

4 Installation Process........................................................................................16 4.1 Installation and Setup of SMD Server................................................................16

4.1.1 Roles for SMD User on Monitoring System ................................................................................. 16 4.1.2 SMD User on Monitoring System................................................................................................. 16 4.1.3 Applying Solution Manager Diagnostics Package ....................................................................... 16 4.1.4 Disabling SMD Maintenance Mode.............................................................................................. 17 4.1.5 SMD Upgrader ............................................................................................................................. 17 4.1.6 Monitoring System (SMD) Setup Wizard ..................................................................................... 19 4.1.7 ABAP Connectivity Setup............................................................................................................. 21 4.1.8 Solution Manager setup to connect to SMD server ..................................................................... 23 4.1.9 Import SSO Certificate to the ABAP Stack................................................................................... 24 4.1.10 Configuration of Remote Database Monitoring .......................................................................... 25 4.1.11 Setup of J2EE Server Analysis (Wily Introscope) ...................................................................... 25 4.1.12 Setup of Mercury Load Generator.............................................................................................. 26 4.1.13 Configuration of Remote Connection for SAP Support.............................................................. 26

4.2 Setup of Monitored Systems ..............................................................................28 4.2.1 Installation of SMD Agent............................................................................................................. 28 4.2.3 Installation of CCMS Agent SAPCCMSR..................................................................................... 33 4.2.4 Installation of OS Collector SAPOSCOL...................................................................................... 34 4.2.5 Roles for SMD User on Monitored System .................................................................................. 34 4.2.6 SMD User for J2EE Engine on Monitored System ...................................................................... 35 4.2.7 Installation of Introscope Agent.................................................................................................... 35 4.2.8 Setup of Portal Activity Reporting ................................................................................................ 35 4.2.9 Setup of Software Change Reporting for Enterprise Portals ....................................................... 36 4.2.10 Setup of Session Tracing for SAP J2EE Engines...................................................................... 36 4.2.11 Steps for xMII 11.5 as Monitored System .................................................................................. 37 4.2.12 Setup of SMD Keystore / SSL Application ................................................................................. 37

4.3 Define landscape in Solution Manager..............................................................37 4.3.1 Landscape definition in SMSY ..................................................................................................... 37 4.3.2 Landscape publication to SMD server ......................................................................................... 37

4.4 Connect Monitored Systems to SMD Server.....................................................38 4.4.1 Monitored Systems Setup Wizard................................................................................................ 38 4.4.2 Initial Setup of SMD Agent Applications....................................................................................... 40 4.4.3 Configuration of SMD Agent Applications .................................................................................... 41

January 2006 4


5 Additional Information ...................................................................................46 5.1 Used TCP/IP Ports ...............................................................................................46

January 2006 5


Supportability Setup Guide – Solution Manager Diagnostics SAP NetWeaver 04S SP Stack 06

1 Introduction Support Infrastructure with Solution Manager 4.0 – Solution Manager Diagnostics As part of Solution Manager 4.0, Solution Manager Diagnostics (SMD) provides essential functions for efficient and safe root cause analysis of customer solutions based on SAP NetWeaver 04 and SAP NetWeaver 04S.

It especially provides functionality to support Java based components – it runs on the Java side of your Solution Manager 4.0 system. The abap stack of Solution Manager system has also to be used as central system for collecting and handling alerts (CCMS alert handling) as done for the previous Solution Manager releases – therefore we recommend setting up SMD for any SAP NetWeaver landscape.

For measuring performance as well as to troubleshoot problems of the J2EE Engine and its applications, Wily Introscope is integrated into the SMD. The Introscope tool consists of a display, a server part (Introscope Enterprise Server) and a client part (Introscope agent).

Finally, SMD contains the Mercury Interactive load generator tool that enables remote load testing by SAP Support (e.g. during Going Live checks) in order to detect performance bottlenecks.

It is mandatory to install one complete Solution Manager 4.0 including SMD within your SAP NetWeaver solution landscape. One SMD system can monitor any number of SAP NetWeaver solutions.

High-level overview of the support infrastructure:

For detailed information about Solution Manager Diagnostics including end user documentation, see Solution Manager Diagnostics [page 13].

6 January 2006


Solution Manager Diagnostics Landscape To monitor a NetWeaver solution landscape, Solution Manager Diagnostics relies on five components:

− SMD Server SAP J2EE Engine service running on SMD, waiting for SMD Agents to register.

− SMD Navigation Java Web Dynpro component providing access to all tools related to monitor a NetWeaver system. The list of monitoring tools is depending on the type of the monitored NetWeaver system.

− SMD Monitoring Tools Java Web Dynpro applications offering monitoring capabilities.

− SMD Agent Java application running on the monitored systems and gathering information for the SMD Server.

− Solution Manager – landscape definition Standard Solution Manager landscape definition (transaction SMSY). Provide to SMD the Netweaver components to monitor, publish the configuration and monitoring information used by the SMD Server through the agent

Implementation This guide explains in detail the setup of Solution Manager Diagnostics and connected systems.

1.1 Naming Conventions In this documentation, the following naming conventions apply:

Terminology − The term NWA is the same as NetWeaver Administrator

− The term SMD is the same as Solution Manager Diagnostics

SAP S

anD

olMiag

SMD Navigation

SAP SolM

anDiag

SMD Navigation

SMD Monitoring Tools

SMD Agent

NetW

eaver

Solution Landscape

Psh

ubli

Solution M

Solution Manager 4.0

Java stack

Abap stack

Landscape definition

(SMSY)

Publish

Publish

SMD wizard

(SMDIAG_WIZARD)

January 2006 7


− Monitoring System is a general term for the central entry point of system analysis & monitoring. In a

SMD scenario, Monitoring System is the SMD system.

− Monitored System is a general term for a satellite system connected to SMD (e.g. Enterprise Portal)

Variables

Variables Description

<SID> SAP system ID

<DBSID> Database system ID

<INSTDIR> Installation directory for the SAP system

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

<OS> Operating system name within a path

8 January 2006


2 Installation – Step by Step Purpose You use the tables in the following sections as checklists to navigate through the installation when you install your SAP system.

All necessary installation phases (planning, preparation, installation, and post-installation) are listed in these tables.

Use the links to the general descriptions of the actions and to any additional information to help you perform the actions. This prevents you missing important information.

Installation Strategy The setup of Solution Manager Diagnostic is divided into two major parts:

• Installing and configuring the Solution Manager Diagnostic system (monitoring system). This step has to be performed once for the SAP NetWeaver solution landscape.

o Attaching the remote server to the solution landscape monitored by SMD.

• Installing and attaching the monitored systems of the SAP NetWeaver solution landscape. This step has to be performed for each server (machine) that has to be attached to SMD. This step is always divided into two parts:

o Attaching the remote server to the solution landscape monitored by SMD.

This step has to be performed once per monitored server.

o Downloading the configuration information of the monitored system to SMD.

This step can be performed either for each monitored system or for a set of monitored systems.

For of each those steps, a Setup Wizard is provided to minimize manual activities.

Process Flow 1. You print out the relevant checklist:

- Depending if it is a new installation or an upgrade to an already existing SMD, choose one of the following startegies:

- To install and setup a new SMD, see table Installation Matrix for a new SMD [page 10].

- To setup monitored systems, see table Matrix for Setup of Monitored Systems [page 10].

- To connect monitored systems to SMD, see table Matrix for Connection of Monitored Systems to SMD [page 11].

2. You follow the installation sequence exactly as shown in the tables.

− If a step is required for your installation, you follow the link for that step to the corresponding section.

− You perform the procedure described there.

− After you have successfully completed the installation step, you mark the corresponding entry in the printed table with ! to log the progress of your installation.

− You proceed with the next step listed in the table.

January 2006 9


2.1 Matrix for Solution Manager Diagnostics Setup Installation Matrix for a new SMD To install a new Solution Manager Diagnostics system, some configuration tasks have to be performed. Please follow the table below for step-by-step processing of the setup tasks:

! Action on Solution Manager Diagnostics Remarks

1. 4.1.1 Roles for SMD User on Monitoring System [page 16]

2. 4.1.2 SMD User on Monitoring System [page 16]

3. 4.1.3 Applying Solution Manager Diagnostics Package [page 16]

4. 4.1.4 Disabling SMD Maintenance Mode [page 17]

5. 4.1.5 SMD Upgrader [page 17]

6. 4.1.6 Monitoring System (SMD) Setup Wizard [page 19]

7. 4.1.8 Solution Manager setup to connect to SMD server [page 23]

8. 4.1.9 Import SSO Certificate to the ABAP Stack[page 24] optional

9. 4.1.10 Configuration of Remote Database Monitoring [page 25]

10. 4.1.11 Setup of J2EE Server Analysis (Wily Introscope) [page 25]

11. 4.1.12 Setup of Mercury Load Generator [page 26] optional

12. 4.1.13 Configuration of Remote Connection for SAP Support [page 26]

2.2 Matrix for Setup of Monitored Systems Setup Matrix On each server (machine) of a monitored system for Solution Manager Diagnostics, some configuration tasks have to be performed. Please follow the table below for step-by-step processing of the setup tasks:

! Action on Monitored System Remarks

1. 4.2.1 Installation of SMD Agent [page 28] the SMD monitoring system has to be up and running

3. 4.2.3 Installation of CCMS Agent SAPCCMSR [page 33]

4. 4.2.4 Installation of OS Collector SAPOSCOL [page 34]

5. 4.2.5 Roles for SMD User on Monitored System [page34]

6. 4.2.6 SMD User for J2EE Engine on Monitored System [page 35]

10 January 2006


7. 4.2.7 Installation of Introscope Agent [page 35]

8. 4.2.8 Setup of Portal Activity Reporting [page 35] for monitored SAP Enterprise Portals only

9. 4.2.9 Setup of Software Change Reporting for Enterprise Portals [page 36]

for monitored SAP Enterprise Portals only

10. 4.2.10 Setup of Session Tracing for SAP J2EE Engines [page 36]

optional

11. 4.2.11 Steps for xMII 11.5 as Monitored System [page 37] for monitored xMII 11.5 systems only

12. 4.2.12 Setup of SMD Keystore / SSL Application [page 37]

2.3 Matrix for Connection of Monitored Systems to SMD Setup Matrix Finally, to attach monitored systems to SMD, please follow the table below for step-by-step processing of the setup tasks – these steps have to be repeated:

• each time a monitored host is added to a solution/landscape

• the SMD Server is upgraded (requires configuration update of the monitored systems)

! Action on Solution Manager Diagnostics Remarks

1. 4.3.1 Landscape definition in SMSY [page 37]

2. 4.3.2 Landscape publication to SMD server [page 37]

3. 4.4.1 Monitored Systems Setup Wizard [page 38]

4. 4.4.2 Initial Setup of SMD Agent Application [page 40]

5. 4.4.3 Configuration of SMD Agent Applications [page 41] optional – except LDAP configuration

January 2006 11


3 Installation Planning Make sure that the prerequisites mentioned in this chapter are fulfilled before starting with SMD setup.

3.1 Required Documentation The following sections describe the documentation you require for the installation.

• SAP Installation Notes

• Information in the SAP Service Marketplace

• Components for problem messages

3.1.1 SAP Installation Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service Marketplace at the Internet address:

service.sap.com/notes.

SAP Note Number

Title Remarks

592085 Installing the HTTP Connect service

723909 Java VM settings for J2EE 6.30/6.40

730629 CCMS agents: Java interface for registration

780177 Setup of Solution Manager Diagnostics up-to-date setup information for SMD

797147 Wily Introscope Installation for SAP Customers

up-to-date setup information for Wily Introscope

807951 GoingLive Check Optimization - Remote Load Testing

up-to-date setup information for Mercury LoadGenerator

815252 Installation of Component Analyzer up-to-date setup information for CA

826671 How do I get Solution Manager Diagnostics?

use cases for SMD

829218 Composite Note for Solution Manager Diagnostics

834568 HTTP analysis with IE plugin up-to-date setup information for Mercury LoadGenerator

850886 Enable Remote Connection for NetWeaver usage EP

up-to-date setup information for Mercury LoadGenerator

893101 Portal Activity Report Web Service Security Issue

configure web service for PAR (for SAP NW Portals only)

834534 Role definition for Solution Manager 4.0

12 January 2006


902620 Bug in Solution Manager Depending on the version of Solution Manager, you might need to apply this note or you will not see any solutions in the wizard to publish.

904721 Bug in Solution Manager Depending on the version of Solution Manager, you might need to apply this note or you will always see in SMD the solution Id instead of the Solution name.

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

We recommend that you read this documentation before starting the installation.

Solution Manager Diagnostics (Standard Guide) You will find the current version of the Solution Manager Diagnostics setup guide at

service.sap.com/operationsnw2004s -> Monitoring and Supportability

General documentation for Solution Manager Diagnostics: start SAP Service Marketplace, and go to the Solution Manager Diagnostics area (service.sap.com/diagnostics).

Solution Manager Diagnostics (Advanced Guide) In addition to the standard guide, the advanced guide provides more detailed information on the setup procedure of automated tasks, plus some information for non-standard SMD scenarios.

You will find the current version of the Solution Manager Diagnostics advanced setup guide at service.sap.com/operationsnw2004s -> Monitoring and Supportability

End user documentation & FAQ list You will find the end user documentation and a FAQ list for Solution Manager Diagnostics at service.sap.com/diagnostics.

CCMS Agents Simplified setup steps of the CCMS Agent are explained in this guide. Otherwise, you can find the documentation for the CCMS Agents on SAP Service Marketplace at the System Monitoring and Alert Management area (service.sap.com/monitoring). Choose Monitoring in Detail, and choose the document CCMS Agents: Features, Installation, and Usage.

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

January 2006 13

http://service.sap.com/operationsnw2004s



Solution Manager Implementation guide (IMG) This documentation is available online on the Abap system with the transaction SPRO.

Press the button 'SAP Reference IMG' and navigate to:

SAP Solution Manager Implementation Guide->SAP Solution Manager->Basic Settings->SAP Solution Manager System->Operations->Solution Manager Diagnostics

Solution Manager Integration This documentation provides details on how to define the solutions in Solution Manager using SLD and transaction SMSY. You will find the current version of the Solution Manager integration guide at service.sap.com/operationsnw2004s -> Monitoring and Supportability

3.1.3 Components for Problem Messages In case of problems, contact SAP Support by creating a message in Service Marketplace, components:

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

• SV-SMG-DIA-AGT issues related to SMD Agent

• SV-SMG-DIA-IC issues related to Integration Content for SMD

o SV-SMG-DIA-IC-CRM issues related to CRM Integration Content for SMD

o SV-SMG-DIA-IC-EP issues related to EP Integration Content for SMD

o SV-SMG-DIA-IC-ERP issues related to ERP Integration Content for SMD

o SV-SMG-DIA-IC-MDM issues related to MDM Integration Content for SMD

o SV-SMG-DIA-IC-XI issues related to XI Integration Content for SMD

• SV-SMG-DIA-SRV issues related to SMD Server Infrastructure / Framework

• XX-PART-MIC Issues related to Mercury LoadGenerator

• XX-PART-WILY issues related to Wily Introscope

3.2 Hardware and Software Requirements for SMD Make sure to apply the mentioned program versions or newer versions. All packages can be downloaded from SAP Service Marketplace. The following table lists the requirements:

Requirement Type Requirement

Hardware Requirements

Disk Space: 40 GB

RAM: 4 GB

Virtual Memory: 3 x size of physical memory

Number of CPU: 2

Software Requirements SAP Web AS 7.00 Java Add-In, SP Stack 06

ABAP Kernel patch 80

14 January 2006



Platform-dependent information is available on service.sap.com/pam, refer to for SAP Web AS 7.00.

3.3 Software Requirements for Monitored Systems For systems monitored by Solution Manager Diagnostics, make sure to apply the mentioned program versions or newer versions.

Monitored system can run either NW04 or NW04S products, so the list below contains supported versions for both cases. All packages can be downloaded from SAP Service Marketplace. The following table lists the requirements:

Software Component Requirement

SAP Enterprise Portal EP 6 SP 2

Portal Patch 5, Build 2 J2EE Engine 6.20 SP Stack 25 Startup Framework 6.30/6.40

SAP NetWeaver 04 Portal

J2EE Engine 6.40 SP Stack 10

other NetWeaver 04 systems

SP Stack 10

Netweaver 04S systems

SP Stack 5

ABAP kernel Kernel Patch ?? (700)

ABAP Basis SP5 (SAPKB70005)

January 2006 15


4 Installation Process This chapter contains detailed information for installation & setup of Solution Manager Diagnostics, setup of monitored systems and establishing the connection between Solution Manager Diagnostics and monitored systems.

4.1 Installation and Setup of SMD Server The following sections contain detailed information for installation & setup of the SMD Server.

4.1.1 Roles for SMD User on Monitoring System This section explains the required roles for the SMD user on the monitoring system.

ABAP Role The SMD User on the Monitoring System requires the ABAP role SAP_SOLMANDIAG_SAPSUPPORT. It is delivered within SAP standard as of NetWeaver 04 SP Stack 13 (see SAP note 828533). To create this role manually, refer to Solution Manager Diagnostics (advanced guide), chapter Creation of Role for ABAP User.

J2EE UME Role The SMD User on the Monitoring System requires the UME roles SAP_JAVA_NWADMIN_CENTRAL_READONLY, SAP_JAVA_SUPPORT (successor of role SAPSUPPORT). They are delivered within SAP standard as of NetWeaver 04 SP Stack 13. To create this role manually, refer to Solution Manager Diagnostics (advanced guide), chapter Creation of Support Roles for J2EE Engine.

4.1.2 SMD User on Monitoring System The recommended name of the user for Solution Manager Diagnostics is SAPSUPPORT. It has to be available in both ABAP and J2EE Engine.

For required roles, refer to 4.1.1 Roles for SMD User on Monitoring System.

Note: - 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.

4.1.3 Applying Solution Manager Diagnostics Package As of NetWeaver 04 SP Stack 12, Solution Manager Diagnostics has to be downloaded from SAP Service Marketplace. Afterwards, it can be deployed to the J2EE Engine of Solution Manager Diagnostics.

1. Navigate to service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → SAP Technology Components→ SAP Solution Manager → SAP Solution Manager 4.0 → Entry by Component → Solution Manager Diagnostics → SolManDiag 7.0 →OS independent

2. Deploy file LMSERVICE06_0-<version>.sca by using the SDM tool RemoteGui

16 January 2006


4.1.4 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 LMSERVICE06_0-<version>.sca:

• after deployment in case of a new SMD Server installation

• after deployment in case of a SMD Server upgrade

Start the SMD Administration application by launching URL: http://<host>:<port>/smd/admin

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

Navigate to tab Agent Administration and choose pushbutton Disable Maintenance Mode.

Example screenshot of the Agent Administration screen:

4.1.5 SMD Upgrader 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 LMSERVICE06_0-<version>.sca:

• after deployment in case of a new SMD Server installation

• after deployment in case of a SMD Server upgrade

January 2006 17


Note: After attaching a new monitored system, the SMD Upgrader is not required!

Prerequisites All SMD Agents have to be started on all the monitored systems.

Note: Directly after the first installation of the SMD Server, no SMD Agents are registered.

To verify that all agents are running on the monitored systems, start the SMD Administration console (http://<SMD Server>:<port>/smd/admin)

1. Choose tab Agent Administration

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

Start the SMD Upgrader 1. Start the SMD Administration console (http://<SMD Server>:<port>/smd/admin)

2. Choose tab Upgrader, afterwards a list of required upgrade steps will be shown

3. Select pushbutton Upgrade now

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

Example screenshot of the Upgrader screen:

18 January 2006


4.1.6 Monitoring System (SMD) Setup Wizard

Note: In case of an SMD Server upgrade, this step is not required. However, new features of an upgraded SMD system may need additional parameters what can be configured / verified here.

Prerequisites Before running the Setup Wizard, some technical information have to be provided:

• Hostname where the ABAP Stack is installed. In a standard (Java Add-In) installation, this is the same host as the SAP J2EE Engine.

• ITS Client number. This is normally the productive client.

• ITS port. For details, refer to Solution Manager Diagnostics (advanced guide).

• IGS host & port. For details, refer to Solution Manager Diagnostics (advanced guide).

• Support User ID. For details, refer to Solution Manager Diagnostics (advanced guide).

• Login Ticket Client: This is a 3 digit number that must be chosen and re-used throughout the system (including the monitored systems). Note: this is not the ABAP login client!

• SSO certificate export location (file name and directory). It is recommended to save this SSO certificate in a shared location as it has to be imported into the ABAP stack. In addition, the export file will be transferred to the monitored hosts by the SMD Setup Wizard.

January 2006 19


• SLD Bridge information. This information has to be set only if SLD is part of the solution

landscape. It contains the http(s) host, port, user and password required to connect to SLD.

• SAP NetWeaver Administrator information. This information has to be set only if a SAP NetWeaver Administrator (NWA) is part of the solution landscape. It contains the http(s) host, port, user and password required to connect to NWA.

If this information is available, continue with the SMD Administration Application (SMD Wizard) [page 19].

SMD Administration Application (SMD Wizard) After gathering all afore-mentioned information, the SMD Administration application can be started by URL: http://<host>:<port>/smd/admin

Note: - You have to log on as J2EE administrator to the SMD Administration application. - Certificate export path will not be saved, i.e. each time you enter the SMD Wizard,

this field has to be populated.

Example screenshot of the SMD Setup Wizard (tab Monitoring System Setup Wizard), what is part of the SMD Administration application:

Disabled input fields represent values that are set in the SAP J2EE Engine. Per default, they are copied to the enabled input fields. This enables to start the SMD Setup Wizard as often as required.

The Support User ID field should contain the ID of an already existing support user (e.g. SAPSUPPORT). For security reasons, the Setup Wizard will not create any user.

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

Example screenshot of the Monitoring Host Setup Summary screen:

20 January 2006


The following operations were performed automatically by the SMD Setup Wizard:

• Java parameter settings on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• ITS settings on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• IGS settings on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• HTTP provider settings on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• Single Sign-On configuration on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• Login module configuration on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• SLD settings on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

• NWA settings on SMD Server. For details, refer to Solution Manager Diagnostics (advanced guide).

The Detailed Messages tab reports in detail the performed operations. In case of a problem, error messages will be listed additionally. Refer to the related section (hyperlinks in the bulleted list) to get detailed information on the operation that failed and perform the erroneous step manually.

4.1.7 ABAP Connectivity Setup 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 by launching URL: http://<host>:<port>/smd/admin

January 2006 21



Navigate to tab Agent Administration and choose pushbutton Disable Maintenance Mode.

Example screenshot of the ABAP Connectivity Setup screen:

Configuration This step needs to be performed only once per SMD system. If the connectivity is already established, it 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: Choose the pushbutton Add a new system and enter the appropriate values, use hostname and client number as entered in chapter ITS settings on SMD Server, refer to Solution Manager Diagnostics (advanced guide). To change an existing system, use the pushbutton Edit system.

2. The next step is 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 a user and password of your ABAP system.

22 January 2006


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

Note: 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.

4.1.8 Solution Manager setup to connect to SMD server 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). For more details, please refer to the Solution Manager Implementation guide (IMG) .

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.

January 2006 23


4.1.9 Import SSO Certificate to the ABAP Stack a) Start transaction STRUSTSSO2, navigate to System PSE → <server>_<SID>_<instance no>

Note: If both ABAP kernel and J2EE server are running on the same host within the same

landscape, the default certificates will be the same. In this case, delete the old one with STRUSTSSO2, right-click on System PSE, choose the pushbutton Delete and create a new one as explained in b) – d) below.

b) Choose the pushbutton (Import Certificate) in the Certificate section of the screen to import a certificate from file system, choose Binary as file format

c) Choose the pushbutton Add to Certificate List to apply certificate

d) To save the configuration, choose the pushbutton (Save)

e) Choose the pushbutton Add to ACL to apply ACL

f) In the popup, enter:

• System ID: SID of the system where the certificate has been created, e.g. WA1

• Client: client of the login ticket, e.g. 169

Note: This client is not related to the login client known from ABAP systems!

g) To save the configuration, choose the pushbutton (Save)

h) Start transaction RZ10 and add the following parameters to the Instance profile <SID>_DVEBMGS<instance number>_<hostname> of the SMD Server:

24 January 2006


• login/accept_sso2_ticket: set to 1 (mandatory for accepting certificate) • login/create_sso2_ticket: set to 0 (recommended setting). i) Save and activate the profile

4.1.10 Configuration of Remote Database Monitoring The database multiconnect technology of the SAP kernel enables the SAP Web AS to open a database connection to a second database system and run SQL commands on this remote database. To access database-specific transactions in SMD, the ITS service of the SAP Web AS has to be configured. The following database connections are supported:

DBMS on monitored system (remote DB)

Remarks

MS SQL Server - transaction for remote db monitoring: ST04_MSS - setup of db multi-connect: see SAP Note 178949 - Note: remote MS SQL Servers can be monitored only on a SMD running on Windows

Oracle - transaction for remote db monitoring: ST04M - configuration of ST04M: see SAP Note 780891 - secondary db connection: see SAP Note 323151 - installation of Oracle client on MS SQL Server: see SAP Note 339092

MaxDB - transaction for remote db monitoring: DB59 - installation of MaxDB client: SAP Note 649814 - configuration of DB59: see SAP Note 588515

DB2 UDB for AIX and Windows - transaction for remote db monitoring: DB6COCKPIT - documentation: http://help.sap.com/saphelp_nw04/helpdata /en/c4/b5f88a4252e24e8aab40a956d571c8/frameset.htm

4.1.11 Setup of J2EE Server Analysis (Wily Introscope) Wily Introscope Enterprise Manager should be installed on the SMD Server. The tool is delivered separately by additional CDs. However, it is recommended to apply the updates from SAP Service Marketplace: service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → SAP NetWeaver → SAP NetWeaver → SAP NetWeaver 04 → Entry by Component → Central Admin

Content of the sub-folders:

• Wily Introscope Entpr Mgr 6: to be installed on Solution Manager Diagnostics server

• Wily Introscope Webview 6: to be deployed on Solution Manager Diagnostics server

• Wily Introscope Agent 6: to be installed on the monitored system

You will find the current version of this Introscope installation guide at service.sap.com/nw04operation Cross-NW Installation Guide Wily Introscope 6.0.1. In addition, SAP Note 797147 contains up-to-date setup information.

Note: Introscope WebView should be installed on the SMD Server.

January 2006 25


Note: Platforms supported for Wily Introscope:

- AIX - HP-UX on PA-RISC - Linux on IA 32-bit - Solaris - Windows 2000, Server 2003 on IA 32-bit

4.1.12 Setup of Mercury Load Generator The Load Generator for Mercury Load Runner is delivered on separate CDs. It allows SAP Support to trigger a load test remotely, e.g. during a Going Live session.

SAP recommends to install the Load Generator on a Windows server. Refer to SAP Note 807951 for platform-dependent information.

For installation on Windows, follow the instructions starting on page 7 in the document INSTALL.PDF that can be found on the root level of the Windows installation CD. Select Load Generator for the component to be installed. Accept all default settings during the installation process.

For installation on UNIX platforms, follow the instructions starting on page 55 in the document NSTALL.PDF that can be found on the root level of the Windows installation CD. Refer to the instructions for your operating system and follow the default settings and recommendations.

4.1.13 Configuration of Remote Connection for SAP Support SAProuter Configuration

Adjust the SAProuter configuration file saprouttab. Refer to Used TCP/IP Ports [see page 46] for port information related to SMD.

Syntax: P <ip addr. sapserv> <ip addr. of server> <port>

Example for connection via sapserv3: P 147.204.2.5 192.168.1.1 50000 (example for Solution Manager Diagnostics) P 147.204.2.5 192.168.1.1 2040 (example for ITS server) P 147.204.2.5 192.168.2.2 58000 (example for monitored Enterprise Portal)

Note: - P * * * entries are not sufficient because these only tag all SAP ABAP ports

(3200 … 3299) and no ports outside of this area. - P * * <http port> entries are allowed but allow connections from any one host to

any other host and thus are not recommended for security reasons.

After saving saprouttab, you can import it again by executing saprouter –n

Maintain System Data in SAP Service Marketplace To establish a web-based connection between the Solution Manager Diagnostics at customer site and SAP Support, the remote connection type HTTP Connect URL Access has to be configured. Refer to SAP Notes 592085, 850886 for up-to-date information. To configure a remote connection, proceed as follows:

1. Setting up the HTTP Connect - URL Access service connection using SAP Service Marketplace:

26 January 2006


a) Navigate to service.sap.com/system-data and choose the pushbutton Start Application to start the system data maintenance application

b) Select installation no. and system id where Solution Manager Diagnostics is installed

c) Click pushbutton Service Connection in the area SAP-Router

- click pushbutton Maintain Services and choose HTTP Connect – URLAccess - select contact person(s) and click pushbutton Save - click pushbutton Back - click pushbutton Add URL , • select HTTP Connect – URL access as service • enter “Solution Manager Diagnostics” as description • enter the full-qualified start address for SMD, e.g. p135809.wdf.sap.corp/smd - click pushbutton URL save

Note: - Use only full-qualified host names for both services.

That is, for example: p135809.wdf.sap.corp instead of p135809. - Using IP addresses instead of host names is not allowed!

- click pushbutton Maintain Connections to open a service connection for SAP Support

In addition, software component SolManDiag has to be added, proceed as follows:

2. After saving the URL, go back and choose the pushbutton Show System Data

a) Navigate to Software components and choose the pushbutton (Add)

b) Add Software Component Version SOLMANDIAG 04

January 2006 27


Note: Software Component SAP J2EE ENGINE 6.40 is prerequisite for SOLMANDIAG 04.

c) Choose the Save pushbutton

d) In the Software Components tab, the entry SOLMANDIAG 6.40 will be listed

e) After maintaining the Software Component for Solution Manager Diagnostics, tab Monitored Systems appears – here you can maintain the systems that are connected to SMD

4.2 Setup of Monitored Systems This section contains detailed information for setup of monitored systems for Solution Manager Diagnostics.

4.2.1 Installation of SMD Agent The SMD Agent is an independent Java program that is running in background and communicates with the SMD system. The SMD Agent should be installed on each monitored server (machine) running a SAP J2EE Engine. Since SP Stack 14, the installation of SMD Agent and Component Analyzer are done by SAPinst.

Prerequisite: Monitoring System Make sure that the SMD Server is up and running and the maintenance mode is disabled (refer to 4.1.4 Disabling SMD Maintenance Mode).

Prerequisite: Java Development Kit (JDK) 1.4 SMD Agent and Component Analyzer require JDK 1.4.

The <JAVA_HOME> environment variable ($JAVA_HOME on UNIX, %JAVA_HOME% on Windows) points to the location of the default JVM (Java Virtual Machine) installed on the server.

To check the installed Java version, navigate to <JAVA_HOME> and verify the version by executing java -version

28 January 2006


If JDK 1.4 is missing, copy it to any location on the server, this path has to be provided during setup of SMD Agent.

Note: The correct JDK version is vital for a SAP J2EE Engine. If JDK 1.4 is not installed, do not replace the existing JDK version – but install another JDK folder. Moreover, SAPinst needs the <JAVA_HOME> environment variable to point to the JDK1.4 install folder. For not overwriting the <JAVA_HOME> value system-wide, it is recommended to open a separate shell or command prompt, set <JAVA_HOME> to point to the JDK1.4 install folder, and run SAPinst from there.

Applying Installation Package for CA & SMD Agent The SAPinst package for Component Analyzer and SMD Agent has to be downloaded from SAP Service Marketplace. Afterwards, it can be deployed to the J2EE Engine of Solution Manager Diagnostics.

The version of SMD agent you have to take depends on the version of the monitored system.

• In case your monitored system is running a NW04 engine:

1. Navigate to service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → SAP NetWeaver → SAP NetWeaver → SAP NetWeaver 04 → Entry by Component → Central Admin → COMPONENT ANALYZER 6.40 → <choose OS>. The file cdsmdtools15_0-<version>.zip contains the SAPinst package.

2. Unzip cdsmdtools15_0-<version>.zip and start SAPinst afterwards.

• In case your monitored system is running a NW04S engine:

1. Navigate to service.sap.com/swdc → Download → Support Packages and Patches → Entry by Application Group → SAP Technology Components → SAP SOLUTION MANAGER →SOLUTION MANAGER 4.0→ Entry by Component → Agents for Satellite Systems → SMD AGENT 7.00 → <choose OS>. The file smdagent06_0-<version>.sar contains the SAPinst package.

2. Extract the files of cdsmdtools16_0-<version>.sar using sapcar and start SAPinst afterwards.

Note: - For installing SMD Agent and Component Analyzer, it is highly recommended to run SAPinst using the <SID>adm user created during the installation of Web AS. The root user on UNIX platforms should not be used for running SAPinst. - The Windows service for SMD Agent is only available when installing via SAPinst. If the SMD Agent is installed manually, the connection to the SMD Server is lost after logging off Windows (because in this case no service is available), regardless if started with the start or daemon option. - Make sure that the SAPinst user has write permissions for the Component Analyzer folder.

January 2006 29


Note: It is recommended to use a dedicated J2EE Administrator account for the SMD Agent connection. For SMD Agents already connected, the SMD administration application enables changing the user credentials without reinstalling the agent. For details, refer to Solution Manager Diagnostics (advanced guide), chapter Change Credentials of SMD Agent.

After running SAPinst, the main installation screen appears. To perform the installation, choose Full installation of SMD Agent and Component Analyzer:

On each machine, more than one Component Analyzer can be installed. Each Component Analyzer is attached to a specific SMD Agent on the same machine.

Choose the current location of Component Analyzer and select if the target location installation should be shared or local.

- Shared: Component Analyzer it will be installed into /usr/sap/SMD/component_analyzer. In this case, only one Component Analyzer will be installed on the server and thus, only one solution/landscape is available. The CA can be shared by multiple SMD Agents.

- Local: Component Analyzer it will be installed into /usr/sap/SMD/J<SMD ID>/component_analyzer. In that case, multiple Component Analyzers can be installed on the server and therefore, multiple solutions/landscapes are available. Each CA is connected to a different SMD Agent.

30 January 2006


Note: As the landscape definition comes from solution manager 4.0 for this version of

SMD server, this will not make any difference, this information will stored in the datacollector configuration anyway. So, to make it simple, please select Local.

During the installation, the following parameters have to be specified:

Parameter Example Description SMD Agent Instance Number

97 The instance number of the SMD Agent. An instance number is always associated to a unique SMD monitoring system. Valid values: 90-98.

JDK 1.4 Location of the Java VM. By default, the installation will try to use the <JAVA_HOME> variable.

Installation Drive

(for Windows only)

C: The drive the SMD Agent will be installed.

SMD Server Host Name

p135809.wdf. sap.corp

The fully-qualified host name of the SMD Server.

SMD Server P4 Port 50004 P4 Port of the SAP J2EE Engine running on the SMD Server.

SMD Server User J2EE_ADMIN User for the SAP J2EE Engine of the SMD Server, the user has to be member of the group Administrators.

January 2006 31


password Password of the SMD user. OS User .\SAPServiceJ2E Administrator user of the system where the SMD

Agent is installed, including the user’s domain. OS Password Password of the local system administrator. Virtual Host Name v_portalserver Only if virtual host names are used, e.g. in a high-

availability environment

Note: P4 Port is 5xx04 (where xx is the instance no of SMD).

Refer to Used TCP/IP Ports [page 46] for details.

Example screenshot of parameterization for SAPinst:

The SAPinst module for SMD Agent will perform the following steps:

- Extracting the SMD Agent to the directory /usr/sap/SMD/J<SMD SID>/smdagent (UNIX) or <drive>:\usr\sap\SMD\J<SMD SID>\smdagent (Windows)

- Starting the smdsetup script (refer to Solution Manager Diagnostics (Advanced Guide), chapter Manual Setup of SMD Agent)

- Managing the SMD Agent process is platform-dependent:

Windows platforms UNIX platforms

32 January 2006


- SMD Agent is installed as a Windows service, with startup mode Automatic - SMD Agent is registered in SAP MMC - Use SAP MMC to start and stop the SMD Agent

- SMD Agent is started after the installation has finished - use smdstart.sh and smdstop.sh (located in /usr/sap/SMD/J<SMD SID>/exe) to start and stop the SMD Agent process - add smdstart.sh to the boot sequence if you want SMD Agent to be started automatically

4.2.3 Installation of CCMS Agent SAPCCMSR The CCMS Agent SAPCCMSR is a program running on OS level with a RFC interface to a central monitoring system and an interface to the shared memory. SAPCCMSR triggers SAPOSCOL on the monitored system.

SAPCCMSR Patch 67 is required, the version can be verified by executing sapccmsr –version

Note: As of SMD SP Stack 14, SAPCCMSR is only required for CCMS alert monitoring

and remote OS monitoring, no more for tasks related to the SMD scheduler. For more information, refer to CCMS Agents [see page 13] and SAP Notes 730629, 734247

The setup procedure of SAPCCMSR depends on the version of the monitored systems:

Installing on SAP NetWeaver 04 SP Stack 10 or higher The CCMS Agent is part of the installation package of the J2EE Engine. You only need to register the agent once for each Java system with CEN, add an entry in sapccmsr.ini, and to start the agent.

For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Setup of CCMS Agent on a NetWeaver Java Instance.

Installing on SAP NetWeaver 04 < SP Stack 10, Java instance only The CCMS Agent is part of the installation package of the J2EE Engine. However, it has to be updated with a newer version available on SAP Service Marketplace. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Download CCMS Agent from SAP Service Marketplace.

Afterwards, you need to register the agent once for each Java system with CEN, add an entry in sapccmsr.ini, and to start the agent. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Setup of CCMS Agent on a NetWeaver Java Instance.

Installing on SAP NetWeaver 04 Web AS Java Add-In (Double-Stack) The CCMS Agent is part of the installation package of the Engine. If the SP Stack is < 10, sapccmsr has to be updated with a newer version available on SAP Service Marketplace. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Download CCMS Agent from SAP Service Marketplace.

Afterwards, you need to register the agent twice for each Java system with CEN. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Setup of CCMS Agent on a Double-Stack System.

January 2006 33


Installing on SAP Solution with Release 6.20 The CCMS Agent is part of the installation package of the Engine. However, it has to be updated with a newer version available on SAP Service Marketplace. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Download CCMS Agent from SAP Service Marketplace.

Afterwards, you need to register the agent once for each Java system with CEN, add an entry in sapccmsr.ini, and to start the agent. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Setup of CCMS Agent on a J2EE 6.20.

Installing on Non-SAP Solutions The CCMS Agent has to be downloaded, then installed and configured manually. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Download CCMS Agent from SAP Service Marketplace.

To configure the CCMS agent, refer to Solution Manager Diagnostics (Advanced Guide) chapter Setup of CCMS Agent on a Non-SAP System.

4.2.4 Installation of OS Collector SAPOSCOL The operating system collector SAPOSCOL is a program running on OS level. It works independently from SAP instances, exactly once per monitored host. SAPOSCOL collects data about operating system related data. For more detailed information about SAPOSCOL, refer to OS Collector [see page 13].

SAPOSCOL Patch 67 is required, the version can be verified by executing saposcol –version. The OS CollectorL will be installed and configured automatically by SAPinst during the installation of any SAP product. For non-SAP software solutions, it has to be installed and configured manually. For details, refer to Solution Manager Diagnostics (Advanced Guide) chapter Setup Install and Configure SAPOSCOL on a Non-SAP System.

4.2.5 Roles for SMD User on Monitored System This section explains the required roles for the SMD user on the monitoring system.

For SMD user requirements, refer to 4.3.6 SMD User for J2EE Engine on Monitored System.

Required J2EE UME Roles for SAP J2EE The SMD User on the monitored system requires the UME roles SAP_JAVA_SUPPORT, SAP_JAVA_NWADMIN_CENTRAL_READONLY, SAP_SLD_GUEST.

For read-only access to the SLD application, the Support user must belong to the group having the LcrUser J2EE server role. (E.g. a group named SAP_SLD_GUEST).

Additional J2EE UME Roles for SAP XI Additionally, for XI on the monitored system, the SMD User on the Monitoring System requires the ABAP roles SAP_XI_DISPLAY_USER, SAP_XI_MONITOR.

J2EE Server Roles for SAP J2EE To execute the SystemInfo application, the J2EE server roles sap.com/tc~monitoring~systeminfo*sap_monitoring/SystemInfo_Support_Role,

34 January 2006


OpenSQLMonitorLogonRole must also be granted to the SMD user on the monitored system, what will be done by the Monitored System Setup Wizard (refer to 4.4.1 Monitored Systems Setup Wizard).

To enable the SMD application Java Web Dynpro Monitoring, the user for SMD on the monitored system has to be assigned to the J2EE user role Administrator and has to be member of the J2EE user group Administrators.

For details, refer to Solution Manager Diagnostics (Advanced Guide), chapter Assignment of J2EE Server Roles to the Support User.

4.2.6 SMD User for J2EE Engine on Monitored System To enable Single Sign-On, the user for SMD on the monitored system has to have the same name as the user on the SMD Server.

The recommended name of the user for Solution Manager Diagnostics is SAPSUPPORT. It has to be available in both ABAP and J2EE Engine.

For required roles, refer to 4.3.5 Roles for SMD User on Monitored System.

4.2.7 Installation of Introscope Agent To communicate with the Introscope Enterprise Manager (refer to Setup of J2EE Server Analysis (Wily Introscope) [see page 25]), the Introscope Agent has to be installed. This is explained in the Introscope Installation Guide at service.sap.com/nw04operation Cross-NW Installation Guide Wily Introscope 6.0.1. In addition, SAP Note 797147 contains up-to-date setup information.

Note: It is not required to install the Introscope Agent on every server node.

One Introscope agent per machine with active J2EE server node is sufficient for standard monitoring scenarios.

4.2.8 Setup of Portal Activity Reporting The Solution Manager Diagnostic should be configured for the Portal Activity Reporting (PAR) for Enterprise Portal versions of EP 6 SP 2 or less than NW04 SP 14.

Portal Activity Reporting is intended to access Enterprise Portal performance statistics. General information for the setup of Portal Activity Reporting can be obtained:

• EP 6.0 SP 2

o www.sdn.sap.com → Downloads→ Developer or Administrator Tool → Portal Activity Reporting

• NW Portal

o help.sap.com → Documentation → SAP NetWeaver → People Integration → Portal → Administration Guide → System Administration → Monitoring Technology and Logging → Portal Activity Report

January 2006 35


PAR Setup for NW Portals as of SP Stack 13 For enabling PAR reports within SMD, a web service is used what will be configured automatically. As a prerequisite, the security zone of this web service has to be configured. For details, refer to SAP Note 893101.

PAR Setup for NW Portals < SP Stack 13, EP 6 SP 2 Portals For enabling PAR reports within SMD, a JDBC connection from the SMD Server to the monitored Portal has to be configured. For details, refer to Solution Manager Diagnostics (Advanced Guide), chapter Setup of Portal Activity Reporting.

4.2.9 Setup of Software Change Reporting for Enterprise Portals Prerequisites The PCD configuration file <J2EE home directory>\SYS\global\pcd\pcdStartup.properties has to be adapted on each monitored Enterprise Portal server. Per default, the Pcd.Share variable points to Pcd.Home (<J2EE home directory>\SYS\global\pcd).

Make sure the following lines are present in pcdStartup.properties:

# Directory for temporary transport files Pcd.TransportApplication.TempDir = ${Pcd.Share}

# Directory in which the content migration logs should be stored Pcd.Migration.ContentMigrationLogDirectory=${Pcd.Share}/reports/Migration

# Log into an Xml file (true= Xml, false=HTML, default value false) Pcd.Migration.XmlLogger = true

4.2.10 Setup of Session Tracing for SAP J2EE Engines To enable J2EE session tracing, certain flags have to be activated.

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

2. Navigate to Server → Services → Performance Tracing

3. Open the Trace Config tab and choose the pushbutton (Properties)

4. In the appearing popup screen Session Trace Settings, check Enable session trace

5. Configure the maximum number of activities to be traced by entering a value in the Tracked Activities field (e.g. 100)

6. Configure the name of the URL Parameter that is used in the request URL to activate the session tracing mechanism, by entering a value in the URL Parameter field. The default name of the parameter is SAP-SAT.

7. To save your settings, choose the Save pushbutton

36 January 2006


4.2.11 Steps for xMII 11.5 as Monitored System The xMII 11.5 and related components usually are not installed under the SAP default installation path /usr/sap/…

Therefore the installation directories of these components have to be added manually as described in chapter Configuration of File System Access [see page Error! Bookmark not defined.].

You have to add the absolute installation paths for the xMII server, the New Atlanta ServletExec and the Microsoft Internet Information Server (IIS) as a comma separated list into the root_directories parameter for the monitored xMII host. In addition, you have to add explicitly the absolute path to the /usr/sap directory where the SMD Agent is installed.

For example this could look like:

C:/usr/sap,C:/Lighthammer,D:/ServletExec AS,C:/Inetpub

Note: There must be no spaces before or after the commas!

4.2.12 Setup of SMD Keystore / SSL Application Within SMD, keystore information can be viewed for each monitored J2EE instance.

SSL information can be viewed for each monitored J2EE dispatcher node, too.

In order to get the SSL data for a dispatcher, the SSL Porvider service has to be activated:

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

2. Navigate to Dispatcher → Services → SSL Provider

3. Move the mouse cursor to the service and choose (Start service)

4.3 Define landscape in Solution Manager This section contains an overview of the steps you have to do on the solution manager side for each monitored system. To have the detail information, please refer to Solution Manager Integration documentation.

4.3.1 Landscape definition in SMSY This step has to be performed to define your complete monitored landscape in Solution manager. This can be done with the transaction SMSY.

In case there is a SLD connected, it is possible to transfer your installation definition from it to Solution Manager directly (see solution manager documentation). It is then available in SMSY, otherwise this step has to be done manually in the SMSY transaction itself.

Each monitored hosts needs to be defined as server. Each installed database needs to be defined and for each system, the right software components should be assigned.

All the monitored solution and system roles have to be created and should contain the necessary monitored server.

4.3.2 Landscape publication to SMD server This step has to be performed to publish the landscape information to each monitored system.

January 2006 37


Go to the solution manager diagnostic wizard (transaction SMDIAG_WIZARD). Select all the solutions to be monitored from SMD. For each host, adapt the installation path and when all the lights are green, finish the wizard.

4.4 Connect Monitored Systems to SMD Server This section contains detailed information for the connection of monitored systems to the SMD Server.

4.4.1 Monitored Systems Setup Wizard Configuring the monitored system(s) will be done by the Monitored System Setup Wizard.

For SAP J2EE Engines as of 6.40, all steps are performed automatically. SAP J2EE Engines 6.20 and other systems have to be configured manually.

Manual Setup for Monitored Systems The following operations have to be performed manually for monitored systems based on SAP J2EE Engine 6.20 or other systems that are not based on SAP J2EE Engine 6.40:

1. Java parameter settings

2. Setup of HTTP Analysis

3. Setup of Thread Dump and Garbage Collection Analysis (only for systems that are using the Java Virtual Machine)

4. Setup of Single Sign-On

5. Planning tasks in the SMD scheduler

All manual steps are explained in Solution Manager Diagnostics (Advanced Guide), chapter Java Parameter Settings on Monitored System.

Automatic Setup for Monitored Systems For monitored SAP J2EE Engines 6.40 or higher, the following steps are performed automatically:

1. Setup them SMD connectivity

2. Automatic configuration of some SMD applications (e.g. J2EE Command Console)

3. Creation of HTTP destinations

4. Planning tasks in the SMD scheduler

Prerequisites 4.1.6 Monitoring System (SMD) Setup Wizard has to be executed before, because the SSO certificate has to be exported from the monitoring and available on the monitored system to enable Single Sign-On.

4.3.2 Installation of Component Analyzer has to be finished, a solution/landscape has been configured.

Setup Steps Start the SMD Administration application by launching URL: http://<host>:<port>/smd/admin


38 January 2006


Navigate to tab Monitored System Setup and then sub-tab Setup Monitored Systems.

Example screenshot of the Setup Monitored Systems screen:

In this screen, P4 port and login credentials for the administrator of the monitored system have to be entered. The connection between SMD Agent and SMD Server is based on the P4 port and will use this data. To check the entered port and user, choose the pushbutton.

Note: After using a wrong password 3 times with the Ping J2EE feature, the

corresponding user will be locked! It is recommended to use a dedicated administration user for the SMD Agent

to avoid locking the ‘main’ administrator.

To start the automatic setup procedure,

• choose the pushbutton for configuration of a particular monitored system

• choose the pushbutton for configuration of all listed monitored systems together Afterwards, status information will be displayed in the upper left corner of the screen:

To persist the entered data, choose the pushbutton.

January 2006 39


Note: Java parameters that will be changed by the Monitored System Setup Wizard need

a restart of the monitored system before becoming active.

After adding a new monitored system, use the pushbutton to get the new solution/landscape information from the SMD Agent.

4.4.2 Initial Setup of SMD Agent Applications This section explains the initial setup of applications that are running within the SMD Agent. For SAP J2EE Engines as of 6.40, all steps are performed automatically. SAP J2EE Engines 6.20 and other systems have to be configured manually.

Prerequisites 4.4.1 Monitored Systems Setup Wizard has to be executed before, the monitored system has to be in status Ready.

Manual Setup for Monitored Systems The following operations have to be performed manually for monitored systems based on SAP J2EE Engine 6.20 or other systems that are not based on SAP J2EE Engine 6.40:

1. Execution of task Collect Configuration Data

2. Database configuration (agent application database, used by SQL Command Console)

3. Telnet agent configuration (agent application telnet, used by J2EE Command Console)

4. Scheduler setup (schedule all tasks in SMD scheduler)

All manual steps are explained in Solution Manager Diagnostics (Advanced Guide).

Automatic Setup for Monitored Systems For monitored SAP J2EE Engines 6.40 or higher, the following steps are performed automatically:

1. Setup of HTTP destinations Note: for https based configuration, refer to Solution Manager Diagnostics (Advanced Guide)

2. Execution of task Collect Configuration Data

3. Database configuration (agent application database, used by SQL Command Console)

4. Telnet agent configuration (agent application telnet, used by J2EE Command Console)

5. Scheduler setup (schedule all tasks in SMD scheduler)



40 January 2006


Navigate to tab Monitored System Setup and then sub-tab SMD Application Configuration.

Example screenshot of the SMD Application Configuration screen:

In this screen, it can be chosen what SMD applications will be configured. For new monitored systems, it is recommended to select all. To configure the selected applications, choose the pushbutton. When adding a new host to an existing solution/landscape, only the corresponding tasks of the new host have to be selected. To rebuild the list of monitored systems, choose the pushbutton. Afterwards, a new screen with status information will be displayed:

Meaning of Symbols:

Task not executed (disabled by the user)

Task executed successfully

Task executed, but failed

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

January 2006 41


Prerequisites 4.4.2 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.

Note: With exception of the LDAP browser application, all SMD Agent applications are

configured automatically during the step 4.4.2 Initial Setup of SMD Agent Applications.

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



Navigate to tab Agent Administration and then sub-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

42 January 2006


• 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 SP 15, the following agent applications can be configured:

Application name SMD use case Manual config. req.

com.sap.smd.agent.application.telnet → Solution Manager Diagnostics (Advanced Guide)

Provides remote access to the J2EE telnet console for the SMD J2EE command console application

No

com.sap.smd.agent.application.global.configuration → Solution Manager Diagnostics (Advanced Guide)

Global configuration of the SMD Agents No

com.sap.smd.agent.application.filesystem → Solution Manager Diagnostics (Advanced Guide)

Provides access to the remote file system for the SMD File System Browser application, and the Gather/Upload functionality

No

com.sap.smd.agent.application.database → Solution Manager Diagnostics (Advanced Guide)

Access to the DB of the remote system to return table information to the SMD SQL Command Console application

No

com.sap.smd.agent.application.ldap → LDAP Browser Configuration

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

Yes

com.sap.smd.agent.application.remoteos → Solution Manager Diagnostics (Advanced Guide)

Provides remote access of J2EE standalone logviewer to log files for SMD application Log Display

No

com.sap.smd.agent.application.datacollector → Solution Manager Diagnostics (Advanced Guide)

Collects XML based data from monitored systems (replaces the Component Analyzer download feature)

No

com.sap.smd.agent.application.portalactivityreport → Solution Manager Diagnostics (Advanced Guide)

Retrieves data for Portal Activity Reporting (PAR) from monitored SAP Enterprise Portals

No

com.sap.smd.agent.application.connectors → Solution Manager Diagnostics (Advanced Guide)

Provide P4 or JMX connection to the monitored SAP J2EE engine

No

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 In the case of a secure property,

January 2006 43


or not the value is not displayed in the

screen.

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

LDAP Browser Configuration

Note: 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

Example screenshot for LDAP browser configuration:

44 January 2006


January 2006 45


5 Additional Information

5.1 Used TCP/IP Ports The table below shows the default ports used by Solution Manager Diagnostics and monitored systems. The column open in saprouttab indicates ports that have to be opened for SAProuter connections (refer to Configuration of Remote Connection for SAP Support [see page 26]) to enable read-only access by SAP Support.

System Ports used on SMD Server Ports used on each monitored system

open in saprouttab

ABAP Dispatcher 32nn (nn: Instance no.), e.g. 3201

X (only for connection type R/3 Support)

ABAP Gateway 33nn (nn: Instance no.), e.g. 3301

Message Server 36nn (nn: Instance no.), e.g. 3601

HTTP Port of J2EE Engine

5nn00 (nn: Instance no. of SMD), e.g. 50100

5nn00 (nn: Instance no. of monitored system), e.g. 50200

X

HTTP Port of ITS default: 8000 X

P4 Port 5nn04 (nn: Instance no. of SMD), e.g. 50104

Database port depends on DBMS, e.g. 1433 on MS SQL Server

Introscope 6001 (Listener port) 6001

LoadRunner 5001 (Load Generator)

J2EE standalone logviewer

26000 For details, refer to Solution Manager Diagnostics (Advanced Guide)

46 January 2006

solution manager diagnostic setup

Documents