Supp. Setup Guide - Solution Manager Diagnostics NW04 SPS 14

SAP NetWeaver Guide

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

Document Version 4 – December 5, 2005

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 04 SP Stack 14

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

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

2 Installation – Step by Step............................................................................... 8 2.1 Matrix for Solution Manager Diagnostics Installation and Setup......................9 2.2 Matrix for Setup of Monitored Systems...............................................................9 2.3 Matrix for Connection of Monitored Systems to SMD......................................10

3 Installation Planning ......................................................................................11 3.1 Required Documentation....................................................................................11

3.1.1 SAP Installation Notes.................................................................................................................. 11 3.1.2 Information in the SAP Service Marketplace................................................................................ 11 3.1.3 Components for Problem Messages............................................................................................ 12

3.2 Hardware and Software Requirements for SMD ...............................................13 3.3 Software Requirements for Monitored Systems...............................................13

4 Installation Process........................................................................................14 4.1 Installation and Setup of SMD............................................................................14

4.1.1 Applying Solution Manager Diagnostics Package ....................................................................... 14 4.1.2 Monitoring System (SMD) Setup Wizard ..................................................................................... 14 4.1.3 Import SSO Certificate to the ABAP Stack................................................................................... 19 4.1.4 Roles for SMD User on Monitoring System ................................................................................. 20 4.1.5 SMD User on Monitoring System................................................................................................. 21 4.1.6 Configuration of Remote Database Monitoring............................................................................ 22 4.1.7 Setup of J2EE Server Analysis (Wily Introscope) ........................................................................ 22 4.1.8 Setup of Mercury Load Generator................................................................................................ 23 4.1.9 Configuration of Remote Connection for SAP Support................................................................ 23

4.2 Setup of Monitored Systems ..............................................................................25 4.2.1 Installation of SMD Agent............................................................................................................. 25 4.2.2 Installation of Component Analyzer ............................................................................................. 28 4.2.3 Installation of CCMS Agent SAPCCMSR..................................................................................... 29 4.2.4 Installation of OS Collector SAPOSCOL...................................................................................... 30 4.2.5 Roles for SMD User on Monitored System .................................................................................. 31 4.2.6 SMD User for J2EE Engine on Monitored System ...................................................................... 31 4.2.7 Installation of Introscope Agent.................................................................................................... 31 4.2.8 Setup of Portal Activity Reporting ................................................................................................ 31 4.2.9 Setup of Software Change Reporting for Enterprise Portals ....................................................... 32 4.2.10 Setup of Session Tracing for SAP J2EE Engines...................................................................... 32 4.2.11 Steps for xMII 11.5 as Monitored System .................................................................................. 33

4.3 Connect Monitored Systems to SMD.................................................................33 4.3.1 SMD Upgrader ............................................................................................................................. 33 4.3.2 Monitored Systems Setup Wizard................................................................................................ 34 4.3.3 SMD Agent Configuration............................................................................................................. 41

5 Upgrade ...........................................................................................................46 6 Installation Check...........................................................................................47 7 Additional Information ...................................................................................48

7.1 Used TCP/IP Ports ...............................................................................................48 7.2 Detailed Description of Automated Setup Tasks..............................................48

7.2.1 Java Parameter Settings on SMD Server .................................................................................... 48 7.2.2 Configuration of ITS ..................................................................................................................... 49 7.2.3 Configuration of IGS..................................................................................................................... 52

December 2005 4


7.2.4 Connectivity to CCMS on Local ABAP Stack............................................................................... 53 7.2.5 Setup of Single Sign-On on SMD Server ..................................................................................... 53 7.2.6 Creation of Role for ABAP User................................................................................................... 57 7.2.7 Creation of UME Role for J2EE Engine ....................................................................................... 58 7.2.8 Connection to SLD ....................................................................................................................... 60 7.2.9 Connection to NWA...................................................................................................................... 60 7.2.10 Java Parameter Settings on Monitored System......................................................................... 61 7.2.11 Setup of HTTP Analysis ............................................................................................................. 62 7.2.12 Setup of Thread Dump and GC Analysis ................................................................................... 63 7.2.13 Setup of Single Sign-On on Monitored System ......................................................................... 63 7.2.14 Creation of HTTP Destinations .................................................................................................. 65 7.2.15 Setup of DB Connectivity to Monitored Systems ....................................................................... 67 7.2.16 Manual Setup of SMD Agent...................................................................................................... 71 7.2.17 Download & Setup of CCMS Agent ........................................................................................... 72 7.2.18 Creation of Drivers & Data Sources ........................................................................................... 78 7.2.19 Mapping of Solution Landscape to DB Alias.............................................................................. 81

December 2005 5


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

1 Introduction Purpose Solution Manager Diagnostics (SMD) provides essential functions for efficient and safe root cause analysis of customer solutions based on SAP NetWeaver 04.

It especially provides functionality to support Java based components – therefore an active Java stack is required on your central SMD system. This system should also be used as central system for collecting and handling alerts (CCMS alert handling) – therefore we also 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 Solution Manager Diagnostics 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 12].

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

6 December 2005


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

Terminology − The term CA is the same as Component Analyzer

− The term SMD is the same as Solution Manager Diagnostics

− 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

December 2005 7


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.

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

- To install and setup SMD, see table Matrix for Solution Manager Diagnostics Installation and Setup [page 9].

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

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

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.

8 December 2005


2.1 Matrix for Solution Manager Diagnostics Installation and Setup Installation Process For the 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. Applying Solution Manager Diagnostics Package [page 14]

2. Monitoring System (SMD) Setup Wizard [page 14]

3. Import SSO Certificate to the ABAP Stack [page 19]

4. Roles for SMD User on Monitoring System [page 20]

5. SMD User on Monitoring System [page 21]

6. Configuration of Remote Database Monitoring [page 22]

7. Setup of J2EE Server Analysis (Wily Introscope) [page 22]

8. Setup of Mercury Load Generator [page 23]

9. Configuration of Remote Connection for SAP Support [page 23]

2.2 Matrix for Setup of Monitored Systems Installation Process 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:


1. Installation of SMD Agent [page 25] the SMD monitoring instance has to be up and running

2. Installation of Component Analyzer [page 28]

3. Installation of CCMS Agent SAPCCMSR [page 29]

4. Installation of OS Collector SAPOSCOL [page 30]

5. Roles for SMD User on Monitored System [page 31]

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

7. Installation of Introscope Agent [page 31]

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

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

for monitored SAP Enterprise Portals only

10. Setup of Session Tracing for SAP J2EE Engines [page 32] optional

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

December 2005 9


2.3 Matrix for Connection of Monitored Systems to SMD Installation Process 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 for all servers (machines) defined in the solution landscape:


1. SMD Upgrader [page 33] all monitored systems have to be up and running

2. Monitored Systems Setup Wizard [page 34] 2.1 Create HTTP Destinations [page 34] 2.2 Create Data Sources [page 37] 2.3 ABAP Connectivity Setup [page 38] 2.4 Scheduler Setup [page 39]

3. SMD Agent Configuration [page 41] 3.1 J2EE Command Console (Telnet) Configuration [page 43] 3.2 Configuration of File System Access [page 44] 3.3 Configuration of Database Access [page 44] 3.4 OS Command Console Configuration [page 45]

10 December 2005


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 Description

592085 Installing the HTTP Connect service

608533 How to get debug output from UNIX Daemon or service.exe

J2EE 6.20 only

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

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

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

December 2005 11


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

Solution Manager Diagnostics You will find the current version of the Solution Manager Diagnostics setup guide at service.sap.com/nw04operation Cross-NW Supp. Setup Guide Solution Manager Diagnostics NW04 SPS 14.

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

Component Analyzer You will find the current version of the Component Analyzer setup guide at service.sap.com/nw04operation Cross-NW Supp. Setup Guide Component Analyzer NW04 SPS 14.

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.

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

• BC-JAS-ADM-CEN-AIN issues related to Solution Manager Diagnostics

• BC-CCM-MON-CAN issues related to Component Analyzer

• XX-PART-MIC Issues related to Mercury LoadGenerator

• XX-PART-WILY issues related to Wily Introscope

12 December 2005


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 6.40 Java Add-In, SP Stack 14

ABAP Kernel patch 80

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

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

December 2005 13


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 This sections contains detailed information for installation & setup of Solution Manager Diagnostics.

4.1.1 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 NetWeaver → SAP NetWeaver → SAP NetWeaver 04 → Entry by Component → Application Server Java → SOLMANDIAG04 → OS independent

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

4.1.2 Monitoring System (SMD) Setup Wizard Prerequisites Before running the Setup Wizard, some technical informations 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. Check ITS Port Number Determination [see page14].

• IGS port. Check IGS Port Number Determination [see page 16].

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

• SLD Bridge information, for http(s) connection (optional). This information should 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.

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

ITS Port Number Determination SAP ITS (Internet Transaction Server) enables the access to ABAP based transactions via web browser. General information for the setup of SAP ITS is available in the SAP Library.

14 December 2005


Prerequisites The following services have to be activated by using transaction SICF on the ABAP stack:

• default_host → sap → bc → gui → sap → its → webgui

• default_host → sap → public → bc → ur

• default_host → sap → public → bc → its → mimes

Test ITS To test the ITS Webgui service, start ABAP transaction SICF and navigate within the tree on the left side to default_host → sap → bc → gui → sap → its. Right-click on webgui and choose Test Service.

On success, a new window will be opened within the web browser.

To find out the HTTP port for ITS, start ABAP transaction SMICM and navigate to Goto → Services. In the next screen, you will find the HTTP port (e.g. 8000) in line HTTP, column Service Name/Port:

December 2005 15


This is the port number that you will need to provide to the SMD Setup Wizard.

IGS Port Number Determination 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.

Prerequisites 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

Test IGS 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.

16 December 2005


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

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

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

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

December 2005 17


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.

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

Example screenshot of the Monitoring Host Setup Summary screen:

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

• Java Parameter Settings on SMD Server [see page 48]

• Configuration of ITS [see page 49]

18 December 2005


• Configuration of IGS [see page 52]

• Setup of Single Sign-On on SMD Server [see page 63]

• Connection to SLD [see page 60]

• Connection to NWA [see page 60]

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

December 2005 19


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: • 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.4 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 Creation of Role for ABAP User [see page 57].

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) is delivered within SAP standard as of NetWeaver 04 SP Stack 13. To create this role manually, refer to Creation of UME Role for J2EE Engine [see page 58].

J2EE Server Roles To execute the SystemInfo application, the J2EE server role sap.com/tc~monitoring~systeminfo*sap_monitoring/SystemInfo_Support_Role must also be granted to the SAPSUPPORT user on the monitoring system.

To grant this role, start the J2EE Engine Visual Administrator tool:

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

20 December 2005


Similarly, in order to access the SQL*Trace application, the J2EE role OpenSQLMonitorLogonRole has to be granted for the sap.com/SQLTrace*OpenSQLMonitors component:

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

December 2005 21


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.6 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.7 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 same server as SMD.

.

22 December 2005


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.8 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.9 Configuration of Remote Connection for SAP Support SAProuter Configuration

Adjust the SAProuter configuration file saprouttab. Refer to Used TCP/IP Ports [see page 48] 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:

December 2005 23


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 Connections and choose HTTP Connect – URLAccess - click pushbutton Add URL and enter the URL for the SMD server

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. Choose pushbutton URL save, 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

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

24 December 2005


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

4.2.1 Installation of SMD Agent Prerequisites 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

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.

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

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.

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 cdsmdtools14_0-<version>.zip contains the SAPinst package.

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

After running SAPinst, the main installation screen appears:

December 2005 25


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.

26 December 2005


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

Parameter Example Description 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 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.

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

password Password of the SMD user. OS User mydomain\admin

.\SAPServiceP01 Administrator user of the system where the SMD agent is installed, including the user’s domain.

OS Password Password of the local system administrator.

December 2005 27


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

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

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 [see page 71]

- Managing the SMD Agent process is platform-dependent:

Windows platforms UNIX platforms

- 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.2 Installation of Component Analyzer The Component Analyzer is an independent Java program that collects configuration data and other information from the monitored system and stores the gathered data as XML files. Solution Manager Diagnostics triggers Component Analyzer by usaging the CCMS Agent.

For more detailed information about Component Analyzer, refer to Component Analyzer [see page 12].

Since SP Stack 14, the installation of SMD Agent and Component Analyzer are done by SAPinst (refer to Installation of SMD Agent [see page 25]).

Note: If Component Analyzer is not installed on default path /usr/sap/ccms/component_analyzer (UNIX) or <SMD Agent drive>:\usr\sap\ccms\component_analyzer (Windows), then the path of Component Analyzer has to be adapted (refer to Configuration of File System Access [see page 44].

28 December 2005


On Windows systems, the target drive has to be selected before starting deployment.

The Component Analyzer is installed in the directory /usr/sap/ccms/component_analyzer

Note: In order to complete the installation, refer to Component Analyzer [see page 12].

4.2.3 Installation of CCMS Agent SAPCCMSR The CCMS Agent SAPCCMSR is an 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 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 12] 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 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. Refer to Setup of CCMS Agent on a NetWeaver Java Instance [see page 72].

December 2005 29


Installing on SAP NetWeaver 04 < SP Stack 10, Java instance only The 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. Refer to Download CCMS Agent from SAP Service Marketplace [see page 72]. 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. Refer to Setup of CCMS Agent on a NetWeaver Java Instance [see page 72].

Installing on SAP NetWeaver 04 Web AS Java Add-In (Double-Stack) The 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. Refer toDownload CCMS Agent from SAP Service Marketplace [see page 72]. Afterwards, you need to register the agent twice for each Java system with CEN, refer to Setup of CCMS Agent on a Double-Stack System [see page 73].

Installing on SAP Solution with Release 6.20 The 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. Refer to Download CCMS Agent from SAP Service Marketplace [see page 72]. 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. Refer to Setup of CCMS Agent on a J2EE 6.20 System [see page 75].

Installing on Non-SAP Solutions The CCMS agent has to be installed and configured manually. For downloading the CCMS agent, refer to Download CCMS Agent from SAP Service Marketplace [see page 72]. To configure the CCMS agent, refer to Setup of CCMS Agent on a Non-SAP System [see page 77].

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

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 as explained below:

Install and Configure SAPOSCOL on a Non-SAP System

1. Download the current version of SAPOSCOL from the 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 → SAP Kernel 6.40 32-bit → <choose OS> → Database independent → saposcol. The file saposcol<version>.sar contains the OS Collector archived.

2. Extract the OS Collector with SAPCAR. Refer to SAP Note 212876 how to operate SAPCAR. As mentioned above, this has to be done only on engine release < 6.40 or on a non-SAP system

3. Copy the collector’s executable to the following directory; if the directory does not exist, create it:

• Windows: \\host\saploc\prfclog

• UNIX: /usr/sap/ccms/bin

30 December 2005


SAP Note 19227 contains detailed information how to obtain SAPOSCOL.

Note: The saploc directory can also have another name. It is important that there is a share available with the name saploc; by default, it is the directory <drive:>\usr\sap. If this share does not exist, create it manually.

4. Start SAPOSCOL with administrator privileges:

• Windows: register SAPOSCOL as service under under local system account or user sapservice<SID> refer to SAP Note 436186

• UNIX: start SAPOSCOL with root permissions, refer to SAP Note 19227

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

J2EE UME Role The SMD User on the Monitoring System requires the UME roles SAP_JAVA_SUPPORT, SAP_JAVA_NWADMIN_CENTRAL_READONLY, SAP_SLD_GUEST.

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 To execute the SystemInfo application, the J2EE server roles sap.com/tc~monitoring~systeminfo*sap_monitoring/SystemInfo_Support_Role, OpenSQLMonitorLogonRole must also be granted to the SAPSUPPORT user on the monitored system, refer to J2EE Server Roles [see page 20] for a step-by-step description.

4.2.6 SMD User for J2EE Engine on Monitored System For monitored SAP NetWeaver (6.40) systems, a user is required that is assigned to the J2EE user role Administrator and is member of the J2EE user group Administrators. To enable Single Sign-On, this user has to have the same name (e.g. SAPSUPPORT) as the user for Solution Manager Diagnostics.

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 22]) , 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 5.3.2. 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.

December 2005 31


Portal Activity Reporting is intended to access Enterprise Portal performance information. 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

For enabling PAR reports within SMD, refer to Mapping of Solution Landscape to DB Alias [see page 81].

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 follwing 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 Session Trace Settings screen that appears, choose Enable session trace to enable the function

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

32 December 2005


4.2.11 Steps for xMII 11.5 as Monitored System The xMII 11.5 and related components are usually 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 44].

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.3 Connect Monitored Systems to SMD This sections contains detailed information for the connection of monitored systems to the SMD system.

4.3.1 SMD Upgrader General The SMD Upgrader performs all steps to complete the upgrade of the SMD to SP14:

1. SMD DB upgrade: db updates are performed if necessary

2. Agent infrastructure upgrade: new versions of SMD Agent applications are published to the monitored systems. This ensures that a newly connected SMD Agent gets all ist applications.

3. Agent application configuration: configuration of SMD Agent applications are upgraded if necessary

Note: The SMD upgrader has to be executed: - once after SMD installation

- after a new monitored system is connected to SMD

Prerequisites The SMD Agent has to be started on all the monitored systems.

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 succesfull connection between SMD and SMD Agent.

December 2005 33


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:

4.3.2 Monitored Systems Setup Wizard After performing the upgrade, the next step is to configure the monitored system(s).

The following operations were performed automatically by the Monitored System Setup Wizard:

• Create HTTP Destinations (for monitored J2EE systems only) [see page 34]

• Create Data Sources [see page 37]

• ABAP Connectivity Setup [see page 38]

• Scheduler Setup [see page 39] Start the SMD Administration application (http://<SMD server>:<port>/smd/admin) and choose tab Monitored Systems Setup Wizard.

Create HTTP Destinations The HTTP Destination Setup lists existing HTTP destinations and helps to create new ones.

34 December 2005


Note: HTTP Destinations have to be created for 6.40 based J2EE system only. For 6.20 based J2EE systems, refer to Manual Setup for Monitored 6.20 Systems [see page 36].

In order to create a HTTP destination, the following information has to be provided:

• Host to monitor: Fully qualified hostname (including domain name) of a new monitored host that has just been set up. Select the host from the list. Choose pushbutton Refresh to update the list.

• HTTP port of monitored host: HTTP port of the SAP J2EE Engine of the monitored host

• Administrator User: User ID that has administrative privileges on the monitored SAP J2EE Engine. It does not have to be the Administrator account, but it requires administrative privileges

• User password: Password of the previously entered user ID Once you have entered this information, choose the Add New Destination pushbutton and the new destination should appear in the table.

Note: The host name of the destination has to be in lower case format and without

domain name. Format: HTTP:CCR:<host w/o domain>:<msg. port> Example: HTTP:CCR:p79588:3601

December 2005 35


If a problem occurs with these operations and you need to perform them manually with Visual Administrator, or if you want to double check the settings, refer to Creation of HTTP Destinations [see page 65].

Repeat this operation for all the newly added (6.40) monitored systems. Once all the destinations appear in the table, choose the Next pushbutton. The Monitored Hosts Setup wizard screen is displayed afterwards.

Setup Monitored Systems remotely For monitored SAP J2EE Engines 6.40 or higher, the steps below are performed automatically.

The remote setup is based on SMD Agent, thus the SMD Agent has to active on each monitored system. In addition, the HTTP destination has to be maintained, otherwise the pushbutton will be inactive.

For monitored 6.20 systems, refer to the links below to set up the monitored system manually.

Manual Setup for Monitored 6.20 Systems The following operations have to be performed manually for 6.20 based monitored systems only:

• Java Parameter Settings on Monitored System [see page 61]

• Setup of HTTP Analysis [see page 62]

• Setup of Thread Dump and GC Analysis [see page 63]

• Setup of Single Sign-On on Monitored System [see page 63]

Automatic Remote Setup for Monitored Systems as of 6.40

After choosing the Next pushbutton button on the Monitored Systems Setup Wizard, a list of all connected SMD Agents with HTTP destination will bes shown.

Example screenshot of the Monitored Hosts Setup screen:

36 December 2005


On this page, the remote setup for all known monitored systems can be started by choosing the pushbutton, or started for a particular system by choosing the pushbutton.

Note: The Monitoring System Setup Wizard must have been executed to export the SSO

certificate file, before attempting to setup Single Sign-On for any monitored system. The SSO certificate file has to be available for the Monitored System Setup.

This wizard will perform the setup actions on the remote system. Selecting the Status link will display a summary screen of the setup actions performed for the monitored system

Example screenshot of the Setup Summary screen:

In addition to the setup actions, the Component Analyzer installation of the remote host is also checked: these checks are just basic checks on the file system. They do not prevent from continuing with the setup process, but they just indicate that the setup of the Component Analyzer might not be done properly or at least not in a standard way.

Create Data Sources Purpose A direct connection to the database of the monitoring system must be established to configure the Portal Activity Reporting for Enterprise Portal versions of EP 6 SP 2 or less than NW04 SP 13.

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

• EP 6.0 SP 2

December 2005 37


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

Note: As of NetWeaver 04 Portal SP 14, this step is no more necessary.

Proceed with Creation of Drivers & Data Sources [see page 78].

ABAP Connectivity Setup • Within the SMD Setup Wizard, the Next pushbutton will take you to the appropriate screen;

otherwise:

• Start the Agent Configuration user interface by navigating to the Solution Manager Diagnostics menu Configuration → Task → Agent Configuration.

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): Choose the pushbutton Add a new system and enter the appropriate values, use hostname and client number as entered in ITS Port Number Determination [see page 14]. 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.

38 December 2005


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.

Within the SMD Setup wizard, choose the Next pushbutton to perform the Scheduler setup.

Scheduler Setup The scheduler’s purpose is to retrieve data from your system landscape on a regular base.

• Within the SMD Setup Wizard, the Next pushbutton will take you to the appropriate screen; otherwise:

• Start the Agent Configuration user interface by navigating to the Solution Manager Diagnostics menu Configuration → Tasks → Scheduler.

If the scheduler is started for the first time, a special setup is performed. It will create a set of default scheduler tasks for all the monitored systems that have a running SMD Agent.

If the default setup has been already performed, the tasks have to be added manually for every new monitored system.

First Initialization of the Scheduler

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

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

December 2005 39


• Select the host to monitor

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

Note: For monitored hosts that do not contain a SAP J2EE Engine, deactivate some following tasks by choosing the Disable Task pushbutton: - Software Gather Task - Software Download Task - EWA GCA Task - Remote Thread Dump Task

Configuration Download of Monitored System

• Start the Scheduler’s user interface by navigating to the Solution Manager Diagnostics menu Configuration → Task → Scheduler.

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

40 December 2005


• Select the host to monitor

• Navigate to screen Task Viewer

• Select the Configuration Gather Task and choose the Execute Task button

Note: The scheduler cannot determine the end of a Gather Task. The log display can confirm triggering of the Gather Task only. Thus wait 5 – 10 min. before starting the corresponding Download Task manually.

• Select the Configuration Download Task and choose the Execute Task button.

After successful download of a new solution / landscape, you have to refresh the screen within your web browser to get the SMD navigation bar updated.

4.3.3 SMD Agent Configuration Each agent application used by SMD to retrieve and collect monitoring and reporting information should be configured. The existing configuration of the agents is preserved during the upgrade to SP14.

To execute Agent administrative tasks, run the Agent Administration application using the following URL: http://<SMD server>:<port>/smd/admin

December 2005 41


Choose tab Agent Application Configuration and sub-tab Agent Administration. The screen below is displayed:

Prerequisites The SMD Agent has to be started on all the monitored systems.

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

Application name SMD use case

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.global.configuration Global configuration of the SMD agents

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

42 December 2005


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

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.

Note: Don’t use the button Publish configuration to all online agents after saving the configuration for a particular agent. This option is only used to force publishing the configuration to all connected SMD Agents.

J2EE Command Console (Telnet) Configuration

Note: This section is only relevant for monitored systems running a database.

This chapter describes how to setup the telnet application of SMD. This application provides access to a read-only set of J2EE commands on the monitored hosts used by the J2EE command console application.

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

December 2005 43


Configuration of File System Access This chapter describes how to setup the File System Access on the monitored hosts.

Set up the following parameters:


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

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

filesystem host smd.file.alias.component_analyzer_directory

Path of Component Analyzer Note: to be set only if different from default (<SMD Agent drive>: \usr\sap\ccms\component_analyzer), e.g. F:\component_analyzer

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

Configuration of Database Access

Note: This section is only relevant for monitored systems with a SAP J2EE Engine.

The DataBase agent application is used to connect to the DBMS of a monitored system. This agent application is used by the SQL Command Console application.

In a cluster installation, only the SMD Agent of the main instance has to be configured.

The following parameters have to be configured to setup the configuration of the database agent application on a specific host:


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

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

Database host user The user to use for the DB connection

Database Host password The password of the user

Database Host url The URL of the DB.

44 December 2005


OS Command Console Configuration Commands are launched by SMD Agent user. On your monitored systems this 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.

Note: Each command defined in file <component_analyzer>/cca_oscommand.xml should be in the SMD Agent user path and should be accessible by this user only.

December 2005 45


5 Upgrade The following steps have to be performed to configure a solution landscape already installed with a SMD version prior to SP Stack 14 to the SP Stack 14 version.

After applying the SMD package, the SMD application must be started.

In addition, the Component Analyzer package and the SMD Agent must be installed on all monitored systems.

The first step is to connect all SMD Agents to the SMD system. You can verify the connection states of the agents by starting the Agent Administration application from the SMD administration Console.

Then, the Upgrader has to be started within the SMD Administration console: http://<host>:<port>/smd/admin

Navigate to tab Upgrade, select all listed applications, and choose pushbutton Upgrade Now.

The SMD database and the existing SMD Agent configurations will be updated afterwards. In addition, the versions of all connected SMD Agents will be checked.

Upgrade Matrix Solution Manager Diagnostics Monitored System Remarks

1. Applying Solution Manager Diagnostics Package [see page 14]

2. Connection to SLD [see page 60]

To be done only if SLD is configured in the solution landscape.

This step could also be performed directly within the SMD setup wizard.

3. Installation of SMD Agent [see page 25]

This step should be repeated on all monitored systems.

4. Installation of Component Analyzer [see page 28]

This step will migrate the cca files to the SP14 format.

5. SMD Upgrader [see page 33] This step will perform: - SMD database upgrade. - agent application configuration upgrade - publish most recent version of the agent infrastructure to the monitored systems

6. SMD Agent Configuration [see page 41]

The following agent applications must be configured: telnet, database, file system.

46 December 2005


6 Installation Check To find out, if Solution Manager Diagnostics has been installed and configured properly. The Self Check application can be used.

Within SMD, navigate to tab Configuration, and click on Self Check. To start the application, choose the Start Self Check pushbutton.

Check the information tree afterwards, to get a report of SMD-related setup information:

If problems arise, search for SAP Notes or create a problem messages in SAP Service Marketplace, refer to Components for Problem Messages [see page 12].

Note: The installation check depends on the servers attached to the current solution /

landscape. Thus, it is recommended to perform the self check for every solution / landscape.

December 2005 47


7 Additional Information

7.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 23]) to enable read-only access by SAP Support.

System Ports used on SMD 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)

7.2 Detailed Description of Automated Setup Tasks Most configuration is eprformed automatically by the SMD Administration application. In case of problems, configuration steps can be also performed manually – what is explained in this chapter.

7.2.1 Java Parameter Settings on SMD Server This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

For performance analysis of the Solution Manager Diagnostics, the output of garbage collections is required.

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

1. Start the J2EE Configtool where the Solution Manager Diagnostics is running

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

48 December 2005


3. In the General tab, apply the Java parameters • -verbose:gc • -XX:+PrintGCTimeStamps (except on IBM JVM-based systems, see SAP Note 723909)

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

5. In the Global properties tab, apply the parameters by entering into the Value field: • CompressedOthers: true • MinimumGzipLength: 1024 • NeverCompressed: remove entries for *.js, *.cs, *.css by choosing the Set pushbutton after every change

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

7.2.2 Configuration of ITS This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

Get the ITS Port as described in chapter ITS Port Number Determination [see page 14].


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 apps → sap.com → tc~webadministrator~navigation~ejb → appcfg

December 2005 49


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 will be overwritten

Example screenshot for changing settings:

50 December 2005


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

Parameters that can be customized:

Name SAP default Example Description itsclient 066 100 logon client of the SAP ITS system

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

https://p135809.wdf.sap.corp:2040

Server & port where the ITS is running

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

Note: use fully-qualified host names

wahost protocol://host:port http://p135809.wdf.sap.corp:50000

https://p135809.wdf.sap.corp:50001

Server & port where the Wily Introscope Webview has been installed. For installation details, refer to Setup of J2EE Server Analysis (Wily Introscope) [see page 22]

The protocol can be https or http. If no protocol is specified, http will be used.

Note: - the port depends on the protocol used

- server can differ from itshost

nwahost Protocol://host:port http://p135809.wdf.sap.corp:50000 Server & port where the Netweaver Administrator application has been

December 2005 51


installed

nwauser Administrator UserId used by SMD for accessing the Netweaver Administrator application. Password is provided separately in the SMD Setup Wizard.

7.2.3 Configuration of IGS This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.




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.

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

Example screenshot for changing settings:

52 December 2005


Note: you can verify IGSUrl by entering this URL directly into your web browser

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

7.2.4 Connectivity to CCMS on Local ABAP Stack This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

Prerequisites The CCMS agents of all connected systems have to be registered at the CEN. Per default this is the local ABAP stack of the SMD server, refer to Installation of CCMS Agent SAPCCMSR [see page 29].

Setup Refer to ABAP Connectivity Setup [see page 38] for instruction details.

7.2.5 Setup of Single Sign-On on SMD Server This operation is now performed by the SMD 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.

December 2005 53


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 System [see page 63] – even if both Java and ABAP parts are installed on the same machine.

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

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

54 December 2005


i) To save the data, choose the pushbutton Apply custom.

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

December 2005 55


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 System [see page 63].

3. Importing the certificate on SAP ABAP system: refer to Import SSO Certificate to the ABAP Stack [see page 19].

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

56 December 2005


7.2.6 Creation of Role for ABAP User Note: as of NetWeaver 04 SP Stack 13, the according role SAP_SOLMANDIAG_SAPSUPPORT is part of SAP standard delivery.

In addition to the J2EE role, the SMD user needs an ABAP role. 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: ACTVT: 16

RFC_NAME: RFC1, SAL_RFC, SALF, SALS, SCSMROUTE,

December 2005 57


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

Note: For enabling Single Sign-On, the user names for SMD (refer to Setup of Single

Sign-On on SMD Server [see page 53]) and the monitored systems have to be identical. SAPSUPPORT is the recommended user name.

7.2.7 Creation of UME Role for J2EE Engine Note: as of NetWeaver 04 SP Stack 13, the role SAP_JAVA_SUPPORT is part of SAP standard delivery.

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

58 December 2005


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

3. Navigate to Roles

4. Create role SAP_JAVA_SUPPORT within user management, add the role action com~sap~tc~webdynpro.Administrate, and apply the role to the user for Solution Manager Diagnostics. SAPSUPPORT is recommended as user name

5. Verify that the Solution Manager Diagnostics users are member of SAP_JAVA_SUPPORT role

December 2005 59


7.2.8 Connection to SLD If a SLD (SAP System Landscape Directory) system is installed in your solution landscape, the Solution Manager Diagnostic should be connected to this system.


2. Navigate to Server → Services → SLD Data Supplier

3. In the Runtime tab, select the HTTP Settings tab

4. Enter the connection information to the SLD server of your solution landscape.

7.2.9 Connection to NWA If a NWA (SAP NetWeaver Administrator) system is installed in your solution landscape, the Solution Manager Diagnostic should be connected to this system.



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

60 December 2005


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 parametes 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

Note: use fully-qualified host names

nwaadmin Administrator The administrator of the SAP NetWeaver administration server

nwauser Password The administrator of the SAP NetWaever administration server

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

7.2.10 Java Parameter Settings on Monitored System This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

For performance analysis of the 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 (Note: set this parameter for both 6.20 and 6.40 J2EE Engines, refer to SAP Note 608533 for J2EE Engine 6.20)

• -XX:+PrintGCTimeStamps (Note: for 6.40 J2EE Engines only)

• -XX:+JavaMonitorsInStackTrace (Note: for 6.20 J2EE Engines only, but not for Java VMs from IBM or HP, refer to SAP Note 696410 for details)

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

December 2005 61


7.2.11 Setup of HTTP Analysis For SAP J2EE Engines 6.40, these operations are now performed by the Monitored System Setup Wizard, but can be performed manually as well.

This application uses a plug-in (can be downloaded within SMD’s HTTP Analysis 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.

Prerequisites The J2EE Engine has to run with activated log mode. Details see below.

Activating J2EE log information on J2EE Engine 6.20

1. Start the J2EE Configtool of the Enterprise Portal


3. Apply the following settings:

• LogType: notCLF • LogRequestTime: enableall • EnableLoging: true • LogHeaderValue: X-CorrelationID

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

5. Navigate to Server → Managers → Log Managers

6. In the Properties tab, change the value of LogLevel to 6 and apply it by choosing pushbutton Add

7. Navigate to Server → Services → Log

8. In the Properties tab, change the value of LogLevel to 6 and apply it by choosing pushbutton Add

Activating J2EE log information on J2EE Engine 6.40

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


7. Apply the following parameters by entering into the Value field: • LogHeaderValue: X-CorrelationID • LogResponseTime: true by choosing the Set pushbutton after every change

62 December 2005


Note: 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 also have to switch on parameter LogRequestResponseHeaders maually:

LogRequestResponseHeaders = true

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

7.2.12 Setup of Thread Dump and GC Analysis All Java VMs used for SAP Enterprise Portal provide a built-in mechanism to dump a snapshot of the states of all Java threads. This dump is called full thread dump.

Analysis of Garbage Collections (GC) provides information about the memory usage of a J2EE cluster node.

Prerequisites Startup Framework 6.30/6.40 has to be installed, even on J2EE Engines 6.20.

7.2.13 Setup of Single Sign-On on Monitored System This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

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

Note: - 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 both 6.20 & 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 [see page 53].

e) Restart the J2EE Engine of the monitored system

2. Allow J2EE Engine to create and accept SSO tickets


December 2005 63




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

• ClientCertLoginModule • CreateTicketLoginModule • CredentialsMappingLoginModule • EvaluateAssertionTicketLoginModule • EvaluateTicketLoginModule • SecuritySessionLoginModule

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



d) Choose the pushbutton Add New to add the following login modules:

• CreateTicketLoginModule • 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

64 December 2005


• ume.configuration.active: true

• trustediss1: CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1 Note: O=<company>,C=<country> are optional

• trusteddn1: CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1 Note: 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) • sap.com/tc~wd~dispwda*webdynpro_welcome (Web Dynpro Console)

7.2.14 Creation of HTTP Destinations This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

Note: HTTP(S) Destinations have to be created for 6.40 based monitored system only.

Proceed as follows:


2. Navigate to Server → Services → Destinations

3. In the Runtime tab, open the branch for HTTP

4. Create destination HTTP:CCR:<msg. server host>:<msg. server port> • <msg. server host>: Hostname of the 6.40 system you want to monitor • <msg. server port>: Port of the message server from the monitored system

Note: There is a naming convention to follow if you create the HTTP destinations

manually. The reason behind this naming convention is that the Component Analyzer of the monitored hosts will try to read the HTTP Destinations and it expects them to be in a certain format.

The host name of the destination has to be in lower case format and without domain name.

Example: HTTP:CCR:p79588:3601

December 2005 65


5. In the URL field, enter http://<host name>:<J2EE port>/sap/monitoring/

SystemConfigurationDownloadServlet

Note: The URL of the download servlet has to be specified with full-qualified domain

name. Example: http://p79588.wdf.sap.corp:50000/sap/monitoring/

SystemConfigurationDownloadServlet

6. Select BASIC as authentication

Note: For HTTPS scenarios, procedd as follows:

- enter https instead of http in the URL - now, in the Server Certificates section, activate Accept certificates in keystore view and choose service_ssl - depending on your security policy, select BASIC or Logon Ticket as authentication

7. Enter user name and password of the J2EE administrator from the 6.40 system you want to monitor

8. Choose the Save pushbutton to store your settings

66 December 2005


7.2.15 Setup of DB Connectivity to Monitored Systems Configuration steps Portal Activity Reporting require a database connection from the Solution Manager Diagnostics to the database of the monitored system. If the database type or version is different from the Solution Manager Diagnostics db, you have to install the corresponding JDBC driver within the SMD system. Otherwise you can use the driver SYSTEM_DRIVER.

If no driver for the database running on 6.20 has been installed yet, you will find the corresponding Java files (extension: .jar) at: <J2EE home dir>/cluster/server/additional-lib/com/sap/data_direct_driver_references

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

Configuration of JDBC Connector

1. Login to the Visual Administrator of SMD and navigate to Server → Services → JDBC Connector

2. Setup the Database Driver & Data source, depending on the database of the Portal server

Note: - You have to create a DataSource for each Portal instance within your solution /

landscape. - Depending on the DBMS, different values have to be entered during the setup

a) Select Drivers and choose the pushbutton (Create New Driver or Data Source) in the toolbar, name it according to the table below and choose the Ok pushbutton:

December 2005 67


MS SQL SERVER Wcr_SAP_SQLServer

Oracle Wcr_Oracle

MAX DB Wcr_Maxdb

DB2 Wcr_Db2

b) Choose the files below depending on the type of DB:

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

Oracle classes12.jar

MAX DB sapdbc.jar

DB2 db2jcc.jar, db2jcc_license_cu.jar

Note: If the SMD is also running on the same type of DBMS, the default SAP J2EE

Engine JDBC driver (SYSTEM_DRIVER) can be used instead.

c) Select DataSources and choose the pushbutton (Create New Driver or Data Source) in the toolbar

d) Go to tab Main

e) Enter Name, e.g. WCR, and Description (optionally), don’t enter Application Name

f) In the dropdown box Driver Name choose the name created in step a)

68 December 2005


g) As Driver Class enter:

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

Oracle oracle.jdbc.driver.OracleDriver

MAX DB com.sap.dbtech.jdbc.DriverSapDB

DB2 com.ibm.db2.jcc.DB2Driver

h) As Database URL enter:

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

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

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

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

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

j) Choose pushbutton Add Alias to create an unique Alias for the landscape: SAP/BC_WA_WCR<nn> (<nn>=01 .. 10) e.g. SAP/BC_WA_WCR01 Note: for mapping the alias, only the last 5 characters are used, e.g. WCR01

k) Go to tab Additional

l) Change the number of Initial Connections to 1, Max Connections to 5, and choose as SQL Engine

- 6.20 Portal: Native SQL (for Portals running on J2EE 6.0) - 6.40 Portal: Open SQL

m) Choose the pushbutton (Save) to save the configuration, afterwards you should see a new data source named WcrDataSource

December 2005 69


n) To check if the database connection is working, click at the Monitoring tab - you should see at least one horizontal line for one db connection

70 December 2005


If not, you may restart the sap.com/JDBCConnector_<name>.xml service by choosing the

pushbutton (Stop Service) and afterwards the pushbutton (Start Service)

7.2.16 Manual Setup of SMD Agent The steps below are now executed by the SMD SAPinst module, but still can be performed manually.

Command Line Example on Windows cd \usr\sap\SMD/J<Inst Nr>/SMDAgent/ smdsetup.bat C:\j2sdk1.4.2_07 smdserver.wdf.sap.corp 50004 adminuser adminpassword

SMD Agent Setup Steps When running properly, the SMD Agent setup output looks like 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

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

o smdagent.bat for Windows OS

o smdagent.sh for Unix OS

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

December 2005 71


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

7.2.17 Download & Setup of CCMS Agent Download CCMS Agent from SAP Service Marketplace For a SAP solution with release < 6.40, a SAP solution without ABAP and Java components (e.g. TREX) or a non-SAP solution, the CCMS agents delivered with the installation have to be exchanged. Proceed as follows:

1.Download the current version of SAPOSCOL from the 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 → SAP Kernel 6.40 32-bit → <choose OS> → Database independent → ccm agent. The file ccmagent<version>.sar contains the CCMS Agent archived.

2.Extract the CCMS Agent with SAPCAR. Refer to SAP Note 212876 how to operate SAPCAR.

Setup of CCMS Agent on a NetWeaver Java Instance Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent:

• You have a Solution Manager Diagnostics systems that contains the central monitoring system (CEN).

• There is a CSMREG user in CEN. If this is not yet the case, create the user by proceeding as follows:

1. In CEN, call transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User.

2. Enter any password for this user, and confirm your entries by choosing the Create CSMREG pushbutton.

• During the registration of the agent, you require the connection data from the agent to CEN. We recommend that you generate this data in a CSMCONF file in CEN before the registration. To do this, proceed as follows:

1. In CEN, call transaction RZ21, and choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents.

2. Save the file CSMCONF at a location that is centrally available, since you require the file for all agent registrations.

Refer to SAP Note 734247 for additional information.

Configuration

1. Log on to the host of a J2EE Engine of the system as <SID>adm.

72 December 2005


2. Copy the start file CSMCONF to the following directory:

• Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\sapccmsr

• UNIX: /usr/sap/ccms/<SysID>_<Inst. No.>/sapccmsr

3. Start the Visual Administrator by calling the start script go (UNIX) or go.bat (Microsoft Windows), and log on with your user as the J2EE Engine administrator.

4. In the navigation bar, choose Cluster → <SysID> → Dispatcher → Services → Monitoring, and choose the CCMS Agent Configuration tab page. Choose the agent configuration file: CCMSCONF

5. If you want to monitor multiple systems with the same system ID, select the Long SID indicator, and enter in this input field an identifier for the system that is unique in your monitored system landscape. This “long system ID” must fulfill the following conditions:

• The first three characters must be the system ID.

• The name can be a maximum of eight characters long.

• The name must not contain an underscore (_).

6. In the Password for Administration User input field, enter the password for the user in CEN, recommendation: user SAPSUPPORT.

7. In the Password for CSMREG User input field, enter the password for the CSMREG user in CEN. Click on the register button.

8. To enable log file monitoring, the CCMS agent’s configuration file sapccmsr.ini has to be modified. Location of sapccmsr.ini:



9. Restart the CCMS agent

Setup of CCMS Agent on a Double-Stack System Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent for double-stack systems (Java Add-In)





December 2005 73





Configuration

1. Follow steps 1 – 9 of Setup of CCMS Agent on a NetWeaver Java Instance [see page 72]

Note: During this step, the CCMS agent has to be registered on the ABAP gateway of the

same system (e.g. SAP XI) – not on the CEN.

2. You must now manually register the relevant agent for each Java instance to the CEN. To do this, on the host of the monitored instance, switch to the directory in which the executable for the CCMS agent SAPCCMSR is located:

• Windows: <J2EE home directory>\SYS\exe\runU

• UNIX: <J2EE home directory>/SYS/exe/runU

3. To register the agent manually, enter the following command:

sapccmsr –R –j2ee pf=<path of the instance profile>

Note: The complete path of the instance profile is (here, for example, for Windows): <J2EE home directory>\SYS\exe\profile\<SysID>_<Inst. Dir.>_<Host> In the case of a dialog instance, this path does not exist; in this case, Visual Admin created a profile for the agent in its working directory during registration: • Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\ sapccmsr\SAPCCMSR_<SysID>_<Inst. No.>.PFL • UNIX: /usr/sap/ccms/<SysID>_<Inst. Nr.>/ sapccmsr/SAPCCMSR_<SysID>_<Inst. No.>.PFL

4. In this manual registration, you next enter that there is exactly one additional central system, and specify the system ID of the system:

additional CENTRAL system y/[n] ? : y

R/3 system ID: <CEN>

additional CENTRAL system y/[n] ? : n

5. You must now also enter the connection data for the secondary central system. In this case, this is CEN. If you do not have the data, you can find it in the CSMCONF file that you created in CEN.

74 December 2005


6. Confirm additional details, such as system groups to which the monitored system belongs, or details about setting up the service with the ENTER key.

7. To enable log file monitoring, the CCMS agent’s configuration file sapccmsr.ini has to be modifed. Location of sapccmsr.ini:




Setup of CCMS Agent on a J2EE 6.20 System Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent:








Configuration

1. Copy the agent’s executable to the following directory; if the directory does not exist, create it:





December 2005 75


• Windows: \\saploc\prfclog\sapccmsr

• UNIX: /usr/sap/tmp/sapccmsr

3. Call SAP Note 730629 (CCMS agents: Java interface for registration). Copy the file csmagent.jar from the Note’s attachment to a temporary directory on the host to be monitored.

4. Start the Java tool by entering the following command at the operating system prompt in the above temporary directory:

java -jar csmagent.jar

5. Select the radio button Standalone/TREX/SAP J2EE Engine 6.20. The input fields Agent Configuration File and Agent Executable should be filled with the correct values.

6. In the Password for Administration User input field, enter the password for the user in CEN, recommendation: user SAPSUPPORT.

7. In the Password for CSMREG User input field, enter the password for the CSMREG user in CEN.

8. Choose the Register button. The registration log is displayed; errors are highlighted in red.

Note: • For Microsoft Windows, the SMD Agent is entered as a service during the registration, and is automatically started during a restart of the host. Under UNIX, the agent is automatically ‘ started by the script startsap when you start the J2EE Engine. • For UNIX, you must ensure yourself that the agent is automatically started when you restart the host. To do this, enter the following command in the inittab: su - <SID>adm -c '/usr/sap/ccms/bin/sapccmsr -DCCMS'

76 December 2005






Note: For SAP CRM and SAP XI systems, sapccm4x has to be installed in addition.

Setup of CCMS Agent on a Non-SAP System Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent:








Configuration

1. Copy the agent’s executable to the following directory; if the directory does not exist, create it:





December 2005 77


• Windows: \\saploc\prfclog\sapccmsr

• UNIX: /usr/sap/tmp/sapccmsr

3. You have to register the agent manually, enter the following command:

sapccmsr –R f=<path and filename of CSMCONF>, e.g.

sapccmsr –R f=c:\usr\sap\prfclog\CSMCONF

3. In this manual registration, you have to enter passwords for the administration user and the user CSMREG.

4. Confirm additional details, such as system groups to which the monitored system belongs, or details about setting up the service with the ENTER key.





7.2.18 Creation of Drivers & Data Sources The screen Creation of Drivers and Data Sources dor Monitored Systems consists of 2 tabs:

o Data Sources

o Database Drivers

A data source is used to connect to a Monitored System database. It is technically based on a database driver.

Database Driver Creation From the SAP J2EE Engine point of view, the database driver is just a set of JAR files that will be used when the data source attempts to establish the connection. Required information:

o db driver name

o jar files of the db driver

Example screenshot:

78 December 2005


The top table shows the already existing database drivers. Please note that the SYSTEM_DRIVER entry represents the driver dedicated to the SAP J2EE Engine itself, it is always delivered and should not be deleted (the UI will not let you do so anyway) but can be re-used.

If a driver relies on more than one jar file (and this is most of the time the case) they have to be entered one by one in field New Jar File Path. After entering, add them by choosing the Add Jar button. The provided files have to be accessible from the called server (check URL in web browser), as these files will be read and used by the server to create the driver.

This step has to be performed for each different db system, e.g. if you wish to monitor one system running with an Oracle DB and another one running with MS_SQL, 2 db drivers have to be created.

Note: If the monitored system runs on the same database type as your monitoring system,

you do not need to create a driver; you can just use the SYSTEM_DRIVER. A driver can be re-used by several data sources. You do not have to create one

driver per data source. So if all monitored systems run on the same database type as the monitoring system, the SYSTEM_DRIVER can be used for all the data sources.

Once all the necessary drivers have been created, the associated data sources can be created. Go to the Data Sources tab.

December 2005 79


Data Source Creation Example screenshot:

The top table shows the already existing Data Sources and their aliases.

The bottom part allows the user to enter the necessary information to create a new Data Source. Keep in mind that this information is for the database of the monitored system. Required information:

o Data Source name: User’s choice.

o Database type: Once you have selected a type the fields about the driver and the JDBC URL will be updated with templates.

o Monitored System Version: either 6.40 or 6.20. It will change the way the database is accessed (Open SQL or Native SQL).

o Database Driver: You need to select it from the drop-down list. If there is no driver that fits your need you will need to create one manually (refer to the previous section for more details).

o JDBC Driver Class: It depends on the type of database that you have selected. It is only a template value, so you can change it if it is not conform to your driver. This needs to be a Java class name that represents a valid JDBC driver that can be loaded by the db driver that you have selected from the drop-down list.

o JDBC URL: Once again by default a template is displayed; it can be changed. You need to enter the information related to the remote DB:

o host

80 December 2005


o port

o instance ID (according to its type)

o Data source Alias Number: This is a value from 01 to 10; you need to select it from the drop-down list. Only 10 remote databases can be monitored, this restriction is explained in the section Mapping of Solution Landscape to DB Alias [see page 81].

Once you have entered the information, choose the Create Data Source button, if everything was correct, the new Data Source will appear in the top table, otherwise an error message will be displayed; in this case the data source might still appear in the table but it means that the connection could not be established with the remote database. Most likely there is a problem with some of the parameters or the remote database is not available. You will need to remove the Data Source and re-create it.

If a problem occurs with these operations and you need to perform them manually, or if you want to double check the settings, or if you want to get more details on this, please refer to the section Setup of DB Connectivity to Monitored Systems [see page 67].

Once all the necessary Data Sources have been created, choose the Next pushbutton.

7.2.19 Mapping of Solution Landscape to DB Alias This operation is now performed by the SMD Setup Wizard, but can be performed manually as well.

1. Within Visual Administrator navigate to Server → Services → Configuration Adapter

2. Open Propertysheet.application.global.properties in edit mode within tree Configurations → apps → sap.com → tc~webadministrator~wcrep~ws → appcfg

3. Make an entry for each database alias

December 2005 81


Description: information for the database alias, cannot be changed

• Name: WCR01…WCR10 (database alias, cannot be changed). The database aliases are created in the SMD Setup Wizard. For detailed information refer to the section Setup of DB Connectivity to Monitored Systems [see page 67].

• Datatype: java.lang.String, cannot be changed

• Default: default value, cannot be changed

• Custom: name of the monitored product within the solution: <Solution name><SID><Installation number> e.g. WAS640_SINGLE_HOSTJ2E47110815

Note: There must be no spaces in the name.

82 December 2005

Date post:	20-Apr-2015
Category:	Documents
Upload:	elisarull
View:	105 times
Download:	2 times

Supp. Setup Guide - Solution Manager Diagnostics NW04 SPS 14

Documents