SAP NetWeaver Guide

Supportability Setup Guide Solution Manager Diagnostics
SAP NetWeaver 04 SP Stack 14
Document Version 4 – December 5, 2005

for

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.

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.

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.

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 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. Any Java™ Source Code delivered with this product is 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. Documentation in the SAP Service Marketplace 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 Library document classification: PUBLIC You can find this documentation at the following Internet address:
service.sap.com/instguides

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.

only to be used by SAP’s Support Services and may not be modified or altered in any way.

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

Typographic Conventions
Type Style Example Text Represents 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 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. 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. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icons
Icon Meaning Caution Example Note Recommendation Syntax

EXAMPLE TEXT

Example text

Example text

<Example text>

EXAMPLE TEXT

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

..........................................18 Creation of Drivers & Data Sources ................................... 78 7........................ 60 7.......... 53 7.......................................................5 Setup of Single Sign-On on SMD Server ................. 53 7...................6 Creation of Role for ABAP User...................................................................... 63 7.......19 Mapping of Solution Landscape to DB Alias ....2.................................................................................................................................13 Setup of Single Sign-On on Monitored System ..... 71 7.. 63 7............................... 62 7..................10 Java Parameter Settings on Monitored System..........................................2................. 57 7...........................................2.............................................9 Connection to NWA.............2..2................................ 58 7..2................2............................... 65 7...........................................................................................................12 Setup of Thread Dump and GC Analysis .....................................17 Download & Setup of CCMS Agent .............................................................................................2...................................................4 Connectivity to CCMS on Local ABAP Stack..............2......2...... 81 December 2005 5 ............................2............Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 7....2..............2..........7 Creation of UME Role for J2EE Engine ........... 60 7............... 67 7...11 Setup of HTTP Analysis ..............................14 Creation of HTTP Destinations .........................................................15 Setup of DB Connectivity to Monitored Systems ................................2..............................................2........................... 61 7................................8 Connection to SLD ..................................2.................................16 Manual Setup of SMD Agent................................... 72 7.........................................

High-level overview of the support infrastructure: For detailed information about Solution Manager Diagnostics including end user documentation. Wily Introscope is integrated into the SMD. 6 December 2005 . Implementation This guide explains in detail the setup of Solution Manager Diagnostics and connected systems. see Solution Manager Diagnostics [page 12]. 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. a server part (Introscope Enterprise Server) and a client part (Introscope agent). SMD contains the Mercury Interactive load generator tool that enables remote load testing by SAP Support (e. during Going Live checks) in order to detect performance bottlenecks.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 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. The Introscope tool consists of a display. 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. It especially provides functionality to support Java based components – therefore an active Java stack is required on your central SMD system.g. Finally. For measuring performance as well as to troubleshoot problems of the J2EE Engine and its applications.

g. 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. Enterprise Portal) Variables Variables <SID> <DBSID> <INSTDIR> <JAVA_HOME> <OS> Description SAP system ID Database system ID Installation directory for the SAP system Installation directory for the JDK (Java Development Kit) Operating system name within a path December 2005 7 .1 Naming Conventions In this documentation.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 1. Monitoring System is the SMD system. Monitored System is a general term for a satellite system connected to SMD (e. In a SMD scenario.

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

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

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

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

Remarks

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

Action on Solution Manager Diagnostics 1. Installation of SMD Agent [page 25] 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] 9. Setup of Software Change Reporting for Enterprise Portals [page 32] 10. Setup of Session Tracing for SAP J2EE Engines [page 32] 11. Steps for xMII 11.5 as Monitored System [page 33]

Remarks the SMD monitoring instance has to be up and running

for monitored SAP Enterprise Portals only for monitored SAP Enterprise Portals only optional for monitored xMII 11.5 systems only

December 2005

9

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

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

Action on Solution Manager Diagnostics 1. SMD Upgrader [page 33] 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]

Remarks all monitored systems have to be up and running

10

December 2005

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

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 592085 608533 723909 730629 780177 797147 807951 815252 834568 850886

Title Installing the HTTP Connect service How to get debug output from UNIX Daemon or service.exe Java VM settings for J2EE 6.30/6.40 CCMS agents: Java interface for registration Setup of Solution Manager Diagnostics Wily Introscope Installation for SAP Customers GoingLive Check Optimization - Remote Load Testing Installation of Component Analyzer HTTP analysis with IE plugin Enable Remote Connection for NetWeaver usage EP

Description

J2EE 6.20 only

up-to-date setup information for SMD up-to-date setup information for Wily Introscope up-to-date setup information for Mercury LoadGenerator up-to-date setup information for CA up-to-date setup information for Mercury LoadGenerator 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

Solution Manager Diagnostics You will find the current version of the Solution Manager Diagnostics setup guide at Cross-NW Supp. General documentation for Solution Manager Diagnostics: start SAP Service Marketplace. service. Choose Monitoring in Detail. Installation. Setup Guide Solution Manager Diagnostics NW04 service.sap. Setup Guide Component Analyzer NW04 SPS 14.com/nw04operation End user documentation & FAQ list You will find the end user documentation and a FAQ list for Solution Manager Diagnostics at service. and Operation.sap.com/monitoring). and Usage. contact SAP Support by creating a message in Service Marketplace. CCMS Agents Simplified setup steps of the CCMS Agent are explained in this guide.sap.com/diagnostics. and then choose the document SAPOSCOL: Properties.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 We recommend that you read this documentation before starting the installation. Installation. you can find the documentation for the CCMS Agents on SAP Service Marketplace at the System Monitoring and Alert Management area (service.3 Components for Problem Messages In case of problems. Component Analyzer You will find the current version of the Component Analyzer setup guide at Cross-NW Supp. and go to the Solution Manager Diagnostics area (service.com/diagnostics). OS Collector Documentation for SAPOSCOL: start SAP Service Marketplace. and choose the document CCMS Agents: Features.1. and go to the System Monitoring and Alert Management area (service. components: • • • • BC-JAS-ADM-CEN-AIN BC-CCM-MON-CAN XX-PART-MIC XX-PART-WILY issues related to Solution Manager Diagnostics issues related to Component Analyzer Issues related to Mercury LoadGenerator issues related to Wily Introscope 12 December 2005 .com/monitoring). 3. Otherwise.sap.com/nw04operation SPS 14.sap.sap. Choose Monitoring in Detail.

The following table lists the requirements: Requirement Type Hardware Requirements Requirement 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. refer to for SAP Web AS 6. make sure to apply the mentioned program versions or newer versions. All packages can be downloaded from SAP Service Marketplace.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 3. SP Stack 14 ABAP Kernel patch 80 Platform-dependent information is available on service.com/pam.30/6.40 Java Add-In.20 SP Stack 25 Startup Framework 6.sap. 3.40 SP Stack 10 SP Stack 10 December 2005 13 . Build 2 J2EE Engine 6.40. All packages can be downloaded from SAP Service Marketplace.40 J2EE Engine 6.The following table lists the requirements: Software Component SAP Enterprise Portal EP 6 SP 2 SAP NetWeaver 04 Portal other NetWeaver 04 systems Requirement Portal Patch 5.3 Software Requirements for Monitored Systems For systems monitored by Solution Manager Diagnostics.2 Hardware and Software Requirements for SMD Make sure to apply the mentioned program versions or newer versions.

• • If this information is available. 14 December 2005 . Check IGS Port Number Determination [see page 16]. 4. some technical informations have to be provided: • • • • • Hostname where the ABAP Stack is installed. In a standard (Java Add-In) installation. SLD Bridge information. Deploy file LMSERVICE14_1-<version>. the export file will be transferred to the monitored hosts by the SMD Setup Wizard.2 Monitoring System (SMD) Setup Wizard Prerequisites Before running the Setup Wizard. IGS port. it can be deployed to the J2EE Engine of Solution Manager Diagnostics.sap.1.1 Installation and Setup of SMD This sections contains detailed information for installation & setup of Solution Manager Diagnostics. Note: this is not the ABAP login client! SSO certificate export location (file name and directory). Afterwards. It contains the http(s) host. ITS Client number. This information should be set only if SLD is part of the solution landscape.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 4 Installation Process This chapter contains detailed information for installation & setup of Solution Manager Diagnostics. Check ITS Port Number Determination [see page14].sca by using the SDM tool RemoteGui 4. This is normally the productive client. for http(s) connection (optional). It is recommended to save this SSO certificate in a shared location as it has to be imported into the ABAP stack. ITS port.1. Navigate to service.1 Applying Solution Manager Diagnostics Package As of NetWeaver 04 SP Stack 12. Login Ticket Client: This is a 3 digit number that must be chosen and re-used throughout the system (including the monitored systems). setup of monitored systems and establishing the connection between Solution Manager Diagnostics and monitored systems. port. In addition.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. continue with the SMD Administration Application (SMD Wizard) [page 14]. Solution Manager Diagnostics has to be downloaded from SAP Service Marketplace. ITS Port Number Determination SAP ITS (Internet Transaction Server) enables the access to ABAP based transactions via web browser. this is the same host as the SAP J2EE Engine. 4. General information for the setup of SAP ITS is available in the SAP Library. 1. user and password required to connect to SLD.

Right-click on webgui and choose Test Service. In the next screen. column Service Name/Port: December 2005 15 . 8000) in line HTTP. start ABAP transaction SMICM and navigate to Goto → Services.g. you will find the HTTP port (e. start ABAP transaction SICF and navigate within the tree on the left side to default_host → sap → bc → gui → sap → its. On success. a new window will be opened within the web browser.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 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. To find out the HTTP port for ITS.

Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 This is the port number that you will need to provide to the SMD Setup Wizard. If example graphics are displayed. IGS.g. use as IGS RFC destination IGS_RFC_DEST. start ABAP transaction SA38 and run program GRAPHICS_IGS_ADMIN.SMD.make sure that field Program ID contains IGS.<SID>. the IGS service is running properly. IGS Port Number Determination SAP IGS (Internet Graphics Server) enables the output of graphics within ABAP based transactions. e. 16 December 2005 . • • GFW_ITS_RFC_DEST IGS_RFC_DEST Test IGS To test the IGS service. 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 .

Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 To find out the IGS port. row Parameter (e. You will find the port number in table CONNECTED_LISTENER. Example screenshot of the SMD Setup Wizard (tab Monitoring System Setup Wizard). choose the pushbutton Status. line Http.g. what is part of the SMD Administration application: December 2005 17 . 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. 40080): SMD Administration Application (SMD Wizard) After gathering all afore-mentioned information.

Per default. they are copied to the enabled input fields. The following operations were performed automatically by the SMD Setup Wizard: • • Java Parameter Settings on SMD Server Configuration of ITS [see page 48] [see page 49] 18 December 2005 .Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Disabled input fields represent values that are set in the SAP J2EE Engine. Once you have entered the required information on this page. This enables to start the SMD Setup Wizard as often as required. select the Example screenshot of the Monitoring Host Setup Summary screen: pushbutton.

1. choose Binary as file format c) Choose the pushbutton Add to Certificate List to apply certificate d) To save the configuration. 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.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • • • • Configuration of IGS Setup of Single Sign-On on SMD Server Connection to SLD Connection to NWA [see page 52] [see page 63] [see page 60] [see page 60] The Detailed Messages tab reports in detail the performed operations. 4. delete the old one with STRUSTSSO2. right-click on System PSE. choose the pushbutton e) Choose the pushbutton Add to ACL to apply ACL (Save) December 2005 19 . 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. error messages will be listed additionally. In case of a problem. In this case.3 Import SSO Certificate to the ABAP Stack a) Start transaction STRUSTSSO2. the default certificates will be the same. choose the pushbutton Delete and create a new one as explained in b) – d) below. (Import Certificate) in the Certificate section of the screen to b) Choose the pushbutton import a certificate from file system.

the J2EE server role sap. To create this role manually. use the Add pushbutton to add the SAPSUPPORT user to this role 20 December 2005 . refer to Creation of Role for ABAP User [see page 57]. J2EE Server Roles To execute the SystemInfo application.g. It is delivered within SAP standard as of NetWeaver 04 SP Stack 13 (see SAP note 828533). navigate to tab Security Roles 4.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 f) In the popup. J2EE UME Role The SMD User on the Monitoring System requires the UME roles SAP_JAVA_NWADMIN_CENTRAL_READONLY.4 Roles for SMD User on Monitoring System This section explains the required roles for the SMD user on the monitoring system. select security role SystemInfo_Support_Role 5. SAP_JAVA_SUPPORT (successor of role SAPSUPPORT) is delivered within SAP standard as of NetWeaver 04 SP Stack 13. WA1 • Client: client of the login ticket.g. navigate to Server → Services → Security Provider 2. i) Save and activate the profile 4. select component sap. e.1. e. 169 Note: This client is not related to the login client known from ABAP systems! g) To save the configuration. start the J2EE Engine Visual Administrator tool: 1. ABAP Role The SMD User on the Monitoring System requires the ABAP role SAP_SOLMANDIAG_SAPSUPPORT. To create this role manually. enter: • System ID: SID of the system where the certificate has been created. 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).com/tc~monitoring~systeminfo*sap_monitoring 3. refer to Creation of UME Role for J2EE Engine [see page 58].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.

1. in order to access the SQL*Trace application.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Similarly.com/SQLTrace*OpenSQLMonitors component: 4. the J2EE role OpenSQLMonitorLogonRole has to be granted for the sap.5 SMD User on Monitoring System The recommended name of the user for Solution Manager Diagnostics is SAPSUPPORT. December 2005 21 . It has to be available in both ABAP and J2EE Engine.

Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: .installation of MaxDB client: SAP Note 649814 .sap. the default user store is the ABAP database.configuration of ST04M: see SAP Note 780891 .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.htm Oracle MaxDB DB2 UDB for AIX and Windows 4.configuration of DB59: see SAP Note 588515 .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. To access database-specific transactions in SMD.For the Web AS Java Add-In (Dual-Stack).transaction for remote db monitoring: DB59 .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: Wily Introscope Webview 6: Wily Introscope Agent 6: to be installed on Solution Manager Diagnostics server to be deployed on Solution Manager Diagnostics server to be installed on the monitored system You will find the current version of this Introscope installation guide at service. Note: . thus users have to be created within SU01 only.1.documentation: http://help. it is recommended to apply the updates from SAP Service Marketplace: service. The following database connections are supported: DBMS on monitored system (remote DB) MS SQL Server Remarks . 22 December 2005 .sap. In addition.com/nw04operation Cross-NW Installation Guide Wily Introscope 6.installation of Oracle client on MS SQL Server: see SAP Note 339092 .transaction for remote db monitoring: DB6COCKPIT .7 Setup of J2EE Server Analysis (Wily Introscope) Wily Introscope Enterprise Manager should be installed on the SMD server. 4.1.transaction for remote db monitoring: ST04_MSS .1. .0. The tool is delivered separately by additional CDs.secondary db connection: see SAP Note 323151 .setup of db multi-connect: see SAP Note 178949 . the ITS service of the SAP Web AS has to be configured. Introscope WebView should be installed on the same server as SMD.com/saphelp_nw04/helpdata /en/c4/b5f88a4252e24e8aab40a956d571c8/frameset.transaction for remote db monitoring: ST04M .sap. However. SAP Note 797147 contains up-to-date setup information.Note: remote MS SQL Servers can be monitored only on a SMD running on Windows .

Refer to SAP Note 807951 for platform-dependent information. sapserv> <ip addr.2.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: Platforms supported for Wily Introscope: .9 Configuration of Remote Connection for SAP Support SAProuter Configuration Adjust the SAProuter configuration file saprouttab.204. e.2.Windows 2000.1. .P * * * entries are not sufficient because these only tag all SAP ABAP ports (3200 … 3299) and no ports outside of this area.1 2040 (example for ITS server) P 147.PDF that can be found on the root level of the Windows installation CD.URL Access service connection using SAP Service Marketplace: December 2005 23 . Server 2003 on IA 32-bit 4.5 192.5 192.g.2. Setting up the HTTP Connect .5 192. 850886 for up-to-date information. For installation on Windows. Select Load Generator for the component to be installed.8 Setup of Mercury Load Generator The Load Generator for Mercury Load Runner is delivered on separate CDs.HP-UX on PA-RISC .PDF that can be found on the root level of the Windows installation CD.168.Solaris . during a Going Live session.1.AIX .168. After saving saprouttab. Refer to SAP Notes 592085.1. SAP recommends to install the Load Generator on a Windows server.204. proceed as follows: 1. Refer to the instructions for your operating system and follow the default settings and recommendations.168. follow the instructions starting on page 7 in the document INSTALL.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.1 50000 (example for Solution Manager Diagnostics) P 147. 4.1. the remote connection type HTTP Connect URL Access has to be configured. To configure a remote connection. follow the instructions starting on page 55 in the document NSTALL.2 58000 (example for monitored Enterprise Portal) Note: . Accept all default settings during the installation process. 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. Refer to Used TCP/IP Ports [see page 48] for port information related to SMD. Syntax: P <ip addr.204.Linux on IA 32-bit . of server> <port> Example for connection via sapserv3: P 147. For installation on UNIX platforms.2. It allows SAP Support to trigger a load test remotely.

40 will be listed e) After maintaining the Software Component for Solution Manager Diagnostics.com/system-data and choose the pushbutton Start Application to start the system data maintenance application b) Select installation no.sap. for example: p135809.click pushbutton Maintain Connections and choose HTTP Connect – URLAccess . . and system id where Solution Manager Diagnostics is installed c) Click pushbutton Service Connection in the area SAP-Router .Use only full-qualified host names for both services. tab Monitored Systems appears – here you can maintain the systems that are connected to SMD 24 December 2005 . the entry SOLMANDIAG 6. go back and choose the pushbutton Show System Data a) Navigate to Software components and choose the pushbutton b) Add Software Component Version SOLMANDIAG 04 (Add) c) Choose the Save pushbutton d) In the Software Components tab.Using IP addresses instead of host names is not allowed! .click pushbutton Add URL and enter the URL for the SMD server Note: .Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 a) Navigate to service.sap.wdf. That is.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.corp instead of p135809. Choose pushbutton URL save.

4 install folder. The file cdsmdtools14_0-<version>. 2. it can be deployed to the J2EE Engine of Solution Manager Diagnostics. do not replace the existing JDK version – but install another JDK folder. it is recommended to open a separate shell or command prompt. The <JAVA_HOME> environment variable ($JAVA_HOME on UNIX. 1. Since SP Stack 14. the main installation screen appears: December 2005 25 .40 → <choose OS>. copy it to any location on the server. SAPinst needs the <JAVA_HOME> environment variable to point to the JDK1.zip and start SAPinst afterwards. The SMD agent should be installed on each monitored server (machine) running a SAP J2EE Engine.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 4. navigate to <JAVA_HOME> and verify the version by executing java -version If JDK 1.2. the installation of SMD Agent and Component Analyzer are done by SAPinst.4. %JAVA_HOME% on Windows) points to the location of the default JVM (Java Virtual Machine) installed on the server.4 install folder.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. For not overwriting the <JAVA_HOME> value system-wide. If JDK 1. 4. Unzip cdsmdtools14_0-<version>. and run SAPinst from there. Moreover. Installation The SMD Agent is an independent Java program that is running in background and communicates with the SMD system.zip contains the SAPinst package. Navigate to service.4 is not installed. Afterwards. set <JAVA_HOME> to point to the JDK1. Note: The correct JDK version is vital for a SAP J2EE Engine. To check the installed Java version.sap. The SAPinst package for Component Analyzer and SMD Agent has to be downloaded from SAP Service Marketplace. this path has to be provided during setup of SMD Agent.2 Setup of Monitored Systems This sections contains detailed information for setup of monitored systems for Solution Manager Diagnostics.1 Installation of SMD Agent Prerequisites SMD Agent and Component Analyzer require JDK 1.4 is missing. After running SAPinst.

For installing SMD Agent and Component Analyzer. .The Windows service for SMD Agent is only available when installing via SAPinst. The root user on UNIX platforms should not be used for running SAPinst. the connection to the SMD server is lost after logging off Windows (because in this case no service is available).Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: . it is highly recommended to run SAPinst using the <SID>adm user created during the installation of Web AS. 26 December 2005 . regardless if started with the start or daemon option. If the SMD Agent is installed manually.

The fully-qualified host name of the SMD server.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 During the installation. including the user’s domain.\SAPServiceP01 Administrator user of the system where the SMD agent is installed. Password of the local system administrator. Password of the SMD user.4 Example Description Location of the Java VM. By default. Valid values: 90-98. p135809. An instance number is always associated to a unique SMD monitoring system.wdf. the following parameters have to be specified: Parameter JDK 1.corp 50004 J2EE_ADMIN mydomain\admin . P4 Port of the SAP J2EE Engine running on the SMD server. December 2005 27 . the installation will try to use the <JAVA_HOME> variable. User for the SAP J2EE Engine of the SMD server. 97 The instance number of the SMD Agent. the user has to be member of the group Administrators. sap. Installation Drive (for Windows only) SMD Agent Instance Number SMDServer SMD Server P4 Port SMD Server User password OS User OS Password C: The drive the SMD Agent will be installed.

Since SP Stack 14.SMD Agent is started after the installation has finished .add smdstart.sh (located in /usr/sap/SMD/J<SMD SID>/exe) to start and stop the SMD Agent process . 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]. refer to Component Analyzer [see page 12]. For more detailed information about Component Analyzer.Use smdstart. 28 December 2005 .2.sh and smdstop. Refer to Used TCP/IP Ports [page 48] for details.SMD Agent is registered in SAP MMC . Solution Manager Diagnostics triggers Component Analyzer by usaging the CCMS Agent.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.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: P4 Port is 5xx04 (where xx is the instance no of SMD).Use SAP MMC to start and stop the SMD Agent UNIX platforms . 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 . the installation of SMD Agent and Component Analyzer are done by SAPinst (refer to Installation of SMD Agent [see page 25]).SMD Agent is installed as a Windows service.sh to the boot sequence if you want SMD Agent to be started automatically 4. with startup mode Automatic .

refer to Component Analyzer [see page 12]. SAPCCMSR triggers SAPOSCOL on the monitored system. the target drive has to be selected before starting deployment. SAPCCMSR is only required for CCMS alert monitoring and remote OS monitoring. For more information.2. 734247. Refer to Setup of CCMS Agent on a NetWeaver Java Instance [see page 72]. You only need to register the agent once for each Java system with CEN. add an entry in sapccmsr.ini. no more for tasks related to the SMD scheduler. and to start the agent. The Component Analyzer is installed in the directory /usr/sap/ccms/component_analyzer Note: In order to complete the installation. 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. the version can be verified by executing sapccmsr –version Note: As of SP Stack 14. SAPCCMSR Patch 67 is required. December 2005 29 .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. refer to CCMS Agents [see page 12] and SAP Notes 730629.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 On Windows systems. 4.

Afterwards.ini.sap. SAPOSCOL Patch 67 is required. it has to be installed and configured manually as explained below: Install and Configure SAPOSCOL on a Non-SAP System 1. Extract the OS Collector with SAPCAR. exactly once per monitored host.40 or on a non-SAP system 3. you need to register the agent twice for each Java system with CEN.2. sapccmsr has to be updated with a newer version available on SAP Service Marketplace. Afterwards. To configure the CCMS agent.40 32-bit → <choose OS> → Database independent → saposcol. and to start the agent. refer to Setup of CCMS Agent on a Double-Stack System [see page 73]. 2. you need to register the agent once for each Java system with CEN. and to start the agent. Download the current version of SAPOSCOL from the SAP Service Marketplace: service. Java instance only The agent is part of the installation package of the J2EE Engine. It works independently from SAP instances.ini. Refer toDownload CCMS Agent from SAP Service Marketplace [see page 72]. The OS CollectorL will be installed and configured automatically by SAPinst during the installation of any SAP product. Afterwards. add an entry in sapccmsr. SAPOSCOL collects data about operating system related data. 4. refer to OS Collector [see page 12]. Refer to Download CCMS Agent from SAP Service Marketplace [see page 72]. Refer to SAP Note 212876 how to operate SAPCAR. Installing on SAP NetWeaver 04 Web AS Java Add-In (Double-Stack) The agent is part of the installation package of the Engine. this has to be done only on engine release < 6. Refer to Setup of CCMS Agent on a J2EE 6. refer to Setup of CCMS Agent on a Non-SAP System [see page 77]. If the SP Stack is < 10. Installing on SAP Solution with Release 6. Copy the collector’s executable to the following directory. refer to Download CCMS Agent from SAP Service Marketplace [see page 72]. For more detailed information about SAPOSCOL. Refer to Download CCMS Agent from SAP Service Marketplace [see page 72].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.4 Installation of OS Collector SAPOSCOL The operating system collector SAPOSCOL is a program running on OS level. add an entry in sapccmsr. However.20 System [see page 75]. you need to register the agent once for each Java system with CEN. it has to be updated with a newer version available on SAP Service Marketplace. The file saposcol<version>.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Installing on SAP NetWeaver 04 < SP Stack 10. As mentioned above.20 The agent is part of the installation package of the Engine. it has to be updated with a newer version available on SAP Service Marketplace. the version can be verified by executing saposcol –version. if the directory does not exist. For non-SAP software solutions. Installing on Non-SAP Solutions The CCMS agent has to be installed and configured manually. For downloading the CCMS agent. create it: • Windows: • UNIX: \\host\saploc\prfclog /usr/sap/ccms/bin 30 December 2005 . However. Refer to Setup of CCMS Agent on a NetWeaver Java Instance [see page 72].sar contains the OS Collector archived.

December 2005 31 . It is important that there is a share available with the name saploc. SAP_JAVA_NWADMIN_CENTRAL_READONLY. In addition. One Introscope agent per machine with active J2EE server node is sufficient for standard monitoring scenarios. refer to J2EE Server Roles [see page 20] for a step-by-step description. Start SAPOSCOL with administrator privileges: • Windows: • UNIX: register SAPOSCOL as service under under local system account or user sapservice<SID> refer to SAP Note 436186 start SAPOSCOL with root permissions.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.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 SAP Note 19227 contains detailed information how to obtain SAPOSCOL. 4. a user is required that is assigned to the J2EE user role Administrator and is member of the J2EE user group Administrators. the Introscope Agent has to be installed.2.sap. J2EE Server Roles To execute the SystemInfo application. Note: The saploc directory can also have another name. SAP Note 797147 contains up-to-date setup information. OpenSQLMonitorLogonRole must also be granted to the SAPSUPPORT user on the monitored system. SAP_SLD_GUEST. If this share does not exist.6 SMD User for J2EE Engine on Monitored System For monitored SAP NetWeaver (6. SAPSUPPORT) as the user for Solution Manager Diagnostics. 4. Additionally. by default. this user has to have the same name (e. the SMD User on the Monitoring System requires the ABAP roles SAP_XI_DISPLAY_USER. This is explained in the Introscope Cross-NW Installation Guide Wily Introscope Installation Guide at service. 4.5 Roles for SMD User on Monitored System This section explains the required roles for the SMD user on the monitoring system.g. it is the directory <drive:>\usr\sap.2. refer to SAP Note 19227 4. J2EE UME Role The SMD User on the Monitoring System requires the UME roles SAP_JAVA_SUPPORT. the J2EE server roles sap.com/tc~monitoring~systeminfo*sap_monitoring/SystemInfo_Support_Role. for XI on the monitored system.40) systems. To enable Single Sign-On.2. SAP_XI_MONITOR.7 Installation of Introscope Agent To communicate with the Introscope Enterprise Manager (refer to Setup of J2EE Server Analysis (Wily Introscope) [see page 22]) . 4.3. create it manually. Note: It is not required to install the Introscope Agent on every server node.2.2.com/nw04operation 5.

The default name of the parameter is SAP-SAT.ContentMigrationLogDirectory=${Pcd.properties: # Directory for temporary transport files Pcd. certain flags have to be activated.sap.Migration. General information for the setup of Portal Activity Reporting can be obtained: • EP 6.2.0 SP 2 o • www.Home (<J2EE home directory>\SYS\global\pcd).Share variable points to Pcd. choose the Save pushbutton 32 December 2005 .properties has to be adapted on each monitored Enterprise Portal server. Make sure the follwing lines are present in pcdStartup.Share} # Directory in which the content migration logs should be stored Pcd.2.XmlLogger = true 4. Open the Trace Config tab and choose the pushbutton (Properties) 4.Share}/reports/Migration # Log into an Xml file (true= Xml.sap.com → Downloads→ Developer or Administrator Tool → Portal Activity Reporting NW Portal o help.sdn. by entering a value in the URL Parameter field. choose Enable session trace to enable the function 5.10 Setup of Session Tracing for SAP J2EE Engines To enable J2EE session tracing.9 Setup of Software Change Reporting for Enterprise Portals Prerequisites The PCD configuration file <J2EE home directory>\SYS\global\pcd\pcdStartup. 1. Navigate to Server → Services → Performance Tracing 3. Per default the Pcd. Start the Visual Administrator and log on to the J2EE Engine of the monitored system 2. 7. In the Session Trace Settings screen that appears. default value false) Pcd. false=HTML. Configure the maximum number of activities to be traced by entering a value in the Tracked Activities field (e. 4.g.TempDir = ${Pcd. refer to Mapping of Solution Landscape to DB Alias [see page 81].Migration.com → Documentation → SAP NetWeaver → People Integration → Portal → Administration Guide → System Administration → Monitoring Technology and Logging → Portal Activity Report For enabling PAR reports within SMD. 100) 6.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Portal Activity Reporting is intended to access Enterprise Portal performance information. Configure the name of the URL Parameter that is used in the request URL to activate the session tracing mechanism. To save your settings.TransportApplication.

To verify that all agents are running on the monitored systems. You have to add the absolute installation paths for the xMII server. you have to add explicitly the absolute path to the /usr/sap directory where the SMD Agent is installed. Select sub-tab Agents to show all SMD Agents connected to the SMD system a. Agent infrastructure upgrade: new versions of SMD Agent applications are published to the monitored systems.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]. In addition. 3.5 as Monitored System The xMII 11. 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.C:/Inetpub Note: There must be no spaces before or after the commas! 4.3.11 Steps for xMII 11. SMD DB upgrade: db updates are performed if necessary 2. Agent application configuration: configuration of SMD Agent applications are upgraded if necessary Note: The SMD upgrader has to be executed: . Status (started) indicates a succesfull connection between SMD and SMD Agent.C:/Lighthammer. start the SMD Administration console (http://<SMD server>:<port>/smd/admin) 1. December 2005 33 . For example this could look like: C:/usr/sap. Choose tab Agent Administration 2.3 Connect Monitored Systems to SMD This sections contains detailed information for the connection of monitored systems to the SMD system.once after SMD installation .2.1 SMD Upgrader General The SMD Upgrader performs all steps to complete the upgrade of the SMD to SP14: 1.after a new monitored system is connected to SMD Prerequisites The SMD Agent has to be started on all the monitored systems. This ensures that a newly connected SMD Agent gets all ist applications.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 4.D:/ServletExec AS. 4.

select the Next pushbutton Example screenshot of the Upgrader screen: 4. the SMD Agent is running.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 b. Choose tab Upgrader. the next step is to configure the monitored system(s). If a SMD Agent has status (stopped). Select pushbutton Upgrade now 4. 34 December 2005 . but the agent infrastructure will not accept any requests from the SMD monitoring machine. In this case. Create HTTP Destinations The HTTP Destination Setup lists existing HTTP destinations and helps to create new ones.2 Monitored Systems Setup Wizard After performing the upgrade.3. The following operations were performed automatically by the Monitored System Setup Wizard: • • • • Create HTTP Destinations (for monitored J2EE systems only) Create Data Sources ABAP Connectivity Setup Scheduler Setup [see page 34] [see page 37] [see page 38] [see page 39] Start the SMD Administration application (http://<SMD server>:<port>/smd/admin) and choose tab Monitored Systems Setup Wizard. click pushbutton Start or Restart. Once you have entered the required information on this page. afterwards a list of required upgrade steps will be shown 3. Start the SMD Upgrader 1. Start the SMD Administration console (http://<SMD server>:<port>/smd/admin) 2.

choose the Add New Destination pushbutton and the new destination should appear in the table.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: HTTP Destinations have to be created for 6. It does not have to be the Administrator account. In order to create a HTTP destination. but it requires administrative privileges Password of the previously entered user ID • • HTTP port of monitored host: Administrator User: • User password: Once you have entered this information. refer to Manual Setup for Monitored 6. Format: HTTP:CCR:<host w/o domain>:<msg. For 6. 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.20 based J2EE systems. Select the host from the list. HTTP port of the SAP J2EE Engine of the monitored host User ID that has administrative privileges on the monitored SAP J2EE Engine. Choose pushbutton Refresh to update the list.40 based J2EE system only.20 Systems [see page 36]. Note: The host name of the destination has to be in lower case format and without domain name. port> Example: HTTP:CCR:p79588:3601 December 2005 35 .

the steps below are performed automatically.20 systems. In addition. Example screenshot of the Monitored Hosts Setup screen: 36 December 2005 . The Monitored Hosts Setup wizard screen is displayed afterwards.40 or higher. thus the SMD Agent has to active on each monitored system.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 If a problem occurs with these operations and you need to perform them manually with Visual Administrator. Once all the destinations appear in the table. Manual Setup for Monitored 6. refer to the links below to set up the monitored system manually. choose the Next pushbutton. a list of all connected SMD Agents with HTTP destination will bes shown.20 Systems The following operations have to be performed manually for 6.40 After choosing the Next pushbutton button on the Monitored Systems Setup Wizard. For monitored 6. otherwise the pushbutton will be inactive. refer to Creation of HTTP Destinations [see page 65]. The remote setup is based on SMD Agent. or if you want to double check the settings. the HTTP destination has to be maintained.40) monitored systems. Repeat this operation for all the newly added (6. Setup Monitored Systems remotely For monitored SAP J2EE Engines 6.20 based monitored systems only: • • • • Java Parameter Settings on Monitored System [see page 61] Setup of HTTP Analysis Setup of Thread Dump and GC Analysis Setup of Single Sign-On on Monitored System [see page 62] [see page 63] [see page 63] Automatic Remote Setup for Monitored Systems as of 6.

or started for a particular system by choosing the pushbutton. This wizard will perform the setup actions on the remote system. Portal Activity Reporting is intended to access Enterprise Portal performance information. before attempting to setup Single Sign-On for any monitored system. the Component Analyzer installation of the remote host is also checked: these checks are just basic checks on the file system. General information for the setup of Portal Activity Reporting can be obtained: • EP 6. but they just indicate that the setup of the Component Analyzer might not be done properly or at least not in a standard way. Note: The Monitoring System Setup Wizard must have been executed to export the SSO certificate file. 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.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 On this page. 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. The SSO certificate file has to be available for the Monitored System Setup.0 SP 2 December 2005 37 . the remote setup for all known monitored systems can be started by choosing the pushbutton. They do not prevent from continuing with the setup process.

without ABAP stack). you have to setup an additional ABAP system (CEN): Choose the pushbutton Add a new system and enter the appropriate values. If the connectivity is already established. 1. use the pushbutton Edit system. If the SMD system is installed on a J2EE Engine only (i.e. Choose the pushbutton Setup Local Connectivity. the Next pushbutton will take you to the appropriate screen. The next step is to setup the local connectivity between Java and ABAP system.sap. choose the pushbutton Start Connection and enter a user and password of your ABAP system.sdn.sap. Configuration This step needs to be performed only once per SMD system. If you get the message ”No connection available”. Proceed with Creation of Drivers & Data Sources [see page 78]. this step is no more necessary. 38 December 2005 . it can be skipped. 2. use hostname and client number as entered in ITS Port Number Determination [see page 14].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. To change an existing system. ABAP Connectivity Setup • • Within the SMD Setup Wizard. otherwise: Start the Agent Configuration user interface by navigating to the Solution Manager Diagnostics menu Configuration → Task → Agent Configuration.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 www.com → Downloads→ Developer or Administrator Tool → Portal Activity Reporting o • NW Portal o help.

Setup of Scheduler Press the Host List tab to get the list of monitored hosts from Solution Manager Diagnostics. If the default setup has been already performed. Within the SMD Setup wizard.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 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). client number or system number are wrong) or delete it and add a new system with the correct parameters afterwards. This will trigger all required tasks. the Next pushbutton will take you to the appropriate screen. • • Within the SMD Setup Wizard. It will create a set of default scheduler tasks for all the monitored systems that have a running SMD Agent.g. the tasks have to be added manually for every new monitored system. otherwise: Start the Agent Configuration user interface by navigating to the Solution Manager Diagnostics menu Configuration → Tasks → Scheduler. choose the Next pushbutton to perform the Scheduler setup. First Initialization of the Scheduler Choose the pushbutton Default Setup in the Scheduler window. If not. a special setup is performed. December 2005 39 . If the scheduler is started for the first time. Scheduler Setup The scheduler’s purpose is to retrieve data from your system landscape on a regular base. Note: Check if the proposed values are correct for the ABAP system parameters. either modify the current values (e.

Press the Host List Tab to get the list of monitored hosts from Solution Manager Diagnostics.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • • Select the host to monitor Press the Add All Tasks button.Software Gather Task .Software Download 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. 40 December 2005 . deactivate some following tasks by choosing the Disable Task pushbutton: . you should see the following screen: Note: For monitored hosts that do not contain a SAP J2EE Engine. Afterwards.EWA GCA Task .

before starting the corresponding Download Task manually. you have to refresh the screen within your web browser to get the SMD navigation bar updated.3.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • • 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. After successful download of a new solution / landscape. Thus wait 5 – 10 min. run the Agent Administration application using the following URL: http://<SMD server>:<port>/smd/admin December 2005 41 . The existing configuration of the agents is preserved during the upgrade to SP14. 4. The log display can confirm triggering of the Gather Task only. • Select the Configuration Download Task and choose the Execute Task button.3 SMD Agent Configuration Each agent application used by SMD to retrieve and collect monitoring and reporting information should be configured. To execute Agent administrative tasks.

agent.sap.smd.application.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Choose tab Agent Application Configuration and sub-tab Agent Administration.configuration com.global. the following agent applications can be configured: Application name com.agent. and the Gather/Upload functionality 42 December 2005 . 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. Overview of the Agent Application Configuration Each application running in the SMD Agent has its own configuration stored centrally in the SMD system.application.telnet com.configuration is available for all agent applications and is maintained by the SMD infrastructure.application.smd.agent. For SP14.sap. Furthermore. Therefore.global. its configuration is the merger of the values defined for the Global and the Host scope.smd. a global configuration named com.smd. When an agent application gets its configuration from the SMD server.agent. The screen below is displayed: Prerequisites The SMD Agent has to be started on all the monitored systems.filesystem SMD use case Provides remote access to the J2EE telnet console for the SMD J2EE command console application Global configuration of the SMD agents Provide access to the remote file system for the SMD File System Browser application. a remote agent application has access to its own configuration or the global configuration.sap.application.sap.

The default value delivered by the agent application is always displayed in the Default Value column. December 2005 43 . false otherwise. Note: Don’t use the button Publish configuration to all online agents after saving the configuration for a particular agent. telnet Global <command name> Cluster Consideration: In a cluster.configuration Scope host Name <sid>/sapj2ee/admin/user Description The SAP J2EE admin user with telnet execution rights.smd. you can change the property values in the Custom Value field. 50008 True if the command is allowed. This chapter describes how to setup the telnet application of SMD.application. Application global. e.sap.configuration telnet host host <sid>/sapj2ee/admin/pwd <sid>/sapj2ee/telnet/port J2EE telnet port 5<instance no>08. J2EE Command Console (Telnet) Configuration Note: This section is only relevant for monitored systems running a database. global. choose pushbutton Reset Property or Reset All. the value is not displayed in the screen. comment Choose the Save pushbutton to store the configuration and send it to the selected SMD Agent. The Add Property pushbutton will open a popup window where the following fields can be entered: Field Property Name Property Value Property Attribute Description The name of the property The value of the property Indicates if the property is secure or not In the case of a secure property.agent. only the SMD Agent running on a host with dispatcher node needs to be configured.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. This application provides access to a read-only set of J2EE commands on the monitored hosts used by the J2EE command console application. To change a property to its default value. This option is only used to force publishing the configuration to all connected SMD Agents. After choosing the Edit pushbutton.g.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 com.

This agent application is used by the SQL Command Console application. filesystem host smd. it allows the access to the usr/sap folder. etc. The DataBase agent application is used to connect to the DBMS of a monitored system. D:/usr/sap. Thread Dump Analyzer) on the monitored host. e.g.component_ analyzer_directory Path of Component Analyzer Note: to be set only if different from default (<SMD Agent drive>: \usr\sap\ccms\component_analyzer). The following parameters have to be configured to setup the configuration of the database agent application on a specific host: Application Database Scope host Name driverclass Description The class of the JDBC driver to use to connect from the SMD agent to the remote DB The jar files containing the JDBC driver to use for the connection from the SMD agent to the remote DB The user to use for the DB connection The password of the user The URL of the DB. at least the SAP root directory (X:/usr/sap. F:\component_analyzer Note: If root directories are modified.). where X: is the installation drive on Windows systems) must be part of the list. If the value of this property is empty. File System Browser. all SAP directories must be part of the list (e. C:/usr/sap. For multi drive installations. Configuration of Database Access Note: This section is only relevant for monitored systems with a SAP J2EE Engine.alias.g.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Configuration of File System Access This chapter describes how to setup the File System Access on the monitored hosts. Database host driverjars Database Database Database host Host Host user password url 44 December 2005 . only the SMD Agent of the main instance has to be configured.file.g. Set up the following parameters: Application filesystem Scope host Name root_directories Description A comma separator list of root folders accessible by SMD applications (e. In a cluster installation.

On your monitored systems this user may not have rights to execute all commands. December 2005 45 . 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.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 OS Command Console Configuration Commands are launched by SMD Agent user. Before using OS Command Console.

Installation of SMD Agent [see page 25] 4. You can verify the connection states of the agents by starting the Agent Administration application from the SMD administration Console. In addition. select all listed applications.publish most recent version of the agent infrastructure to the monitored systems The following agent applications must be configured: telnet. . This step could also be performed directly within the SMD setup wizard. Upgrade Matrix Solution Manager Diagnostics 1.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 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. Monitored System Remarks 6. Applying Solution Manager Diagnostics Package [see page 14] 2. SMD Upgrader [see page 33] This step should be repeated on all monitored systems. the versions of all connected SMD Agents will be checked.agent application configuration upgrade .SMD database upgrade. This step will migrate the cca files to the SP14 format. database. This step will perform: . 3. The SMD database and the existing SMD Agent configurations will be updated afterwards. the Component Analyzer package and the SMD Agent must be installed on all monitored systems. In addition. file system. After applying the SMD package. the Upgrader has to be started within the SMD Administration console: http://<host>:<port>/smd/admin Navigate to tab Upgrade. The first step is to connect all SMD Agents to the SMD system. and choose pushbutton Upgrade Now. Then. Connection to SLD [see page 60] To be done only if SLD is configured in the solution landscape. the SMD application must be started. SMD Agent Configuration [see page 41] 46 December 2005 . Installation of Component Analyzer [see page 28] 5.

Within SMD. choose the Start Self Check pushbutton. refer to Components for Problem Messages [see page 12]. search for SAP Notes or create a problem messages in SAP Service Marketplace. it is recommended to perform the self check for every solution / landscape.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 6 Installation Check To find out. The Self Check application can be used. Thus. December 2005 47 . navigate to tab Configuration. to get a report of SMD-related setup information: If problems arise. Check the information tree afterwards. Note: The installation check depends on the servers attached to the current solution / landscape. if Solution Manager Diagnostics has been installed and configured properly. and click on Self Check. To start the application.

For performance analysis of the Solution Manager Diagnostics. 50200 X (only for connection type ‘R/3 Support’) ABAP Gateway Message Server HTTP Port of J2EE Engine HTTP Port of ITS P4 Port X X Database port Introscope LoadRunner 7.g. e. 3601 5nn00 (nn: Instance no. e. configuration steps can be also performed manually – what is explained in this chapter. 50100 default: 8000 5nn04 (nn: Instance no.g. For each server node. of SMD). of SMD). proceed as follows: 1.g. 50104 depends on DBMS. e. 7.g. navigate to cluster-data → Instance_<ID> → Server_<ID> 48 December 2005 . 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.2 Detailed Description of Automated Setup Tasks Most configuration is eprformed automatically by the SMD Administration application. System Ports used on SMD Ports used on each monitored system open in saprouttab ABAP Dispatcher 32nn (nn: Instance no. but can be performed manually as well.g.2. Start the J2EE Configtool where the Solution Manager Diagnostics is running 2. e. 1433 on MS SQL Server 6001 (Listener port) 5001 (Load Generator) 6001 5nn00 (nn: Instance no. To adapt the settings for Solution Manager Diagnostics. e.).1 Java Parameter Settings on SMD Server This operation is now performed by the SMD Setup Wizard. 3201 33nn (nn: Instance no.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 7 Additional Information 7. of monitored system). In case of problems. e.g.g.). 3301 36nn (nn: Instance no.). e.1 Used TCP/IP Ports The table below shows the default ports used by Solution Manager Diagnostics and monitored systems. the output of garbage collections is required.

apply the Java parameters • -verbose:gc • -XX:+PrintGCTimeStamps (except on IBM JVM-based systems.cs. Navigate to Server → Services → Configuration Adapter 3.css by choosing the Set pushbutton after every change 6. apply the parameters by entering into the Value field: • CompressedOthers: true • MinimumGzipLength: 1024 • NeverCompressed: remove entries for *. To persist all customized settings.js. choose the pushbutton (Save) 7.2 Configuration of ITS This operation is now performed by the SMD Setup Wizard. Get the ITS Port as described in chapter ITS Port Number Determination [see page 14]. proceed as follows: 1. To adapt the settings for Solution Manager Diagnostics.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 3. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. open the branch for apps → sap. In the Global properties tab. *. but can be performed manually as well.com → tc~webadministrator~navigation~ejb → appcfg December 2005 49 .2. In the Display configuration tab. In the General tab. see SAP Note 723909) 4. Navigate to cluster-data → Instance_<ID> → Server_<ID> → Services → http 5. *.

To switch to edit mode. A single mouse click will open a new window where you can change the configuration data • • • • • Description: Name: Datatype: Default: Custom: text information for the selected item (cannot be changed) name of the property (cannot be changed) data type of the property item (cannot be changed) SAP-delivered value (cannot be changed) if this field contains a value. you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton 5.global. the default value will be overwritten Example screenshot for changing settings: 50 December 2005 . choose the pushbutton application. To modify data.properties (Change) or just double-click on Propertysheet 6.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 4. choose the pushbutton (Display/Change). 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.

http:// will be added by SMD Note: use fully-qualified host names wahost protocol://host:port http://p135809.wdf.corp:50000 https://p135809.wdf.sap. For installation details.sap. To save modified parameters.corp:50001 Server & port where the Wily Introscope Webview has been installed. If no protocol is specified. choose the Apply custom pushbutton Parameters that can be customized: Name itsclient itshost SAP default 066 protocol://host:port Example 100 http://p135809. If no protocol is specified.wdf.corp:2040 Description logon client of the SAP ITS system Server & port where the ITS is running The protocol can be https or http.sap.corp:2040 https://p135809.corp:50000 Server & port where the Netweaver Administrator application has been December 2005 51 .wdf.server can differ from itshost nwahost Protocol://host:port http://p135809.the port depends on the protocol used .sap. http will be used. refer to Setup of J2EE Server Analysis (Wily Introscope) [see page 22] The protocol can be https or http.sap. Note: .wdf.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 8.

In the Display configuration tab.sap. To adapt the settings for Solution Manager Diagnostics. http://p135809. To modify data. A single mouse click will open a new window where you can change the configuration data. but can be performed manually as well. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. e.com → tc~wd~dispwda 4. Change parameter IGSUrl to URL & port of the IGS. proceed as follows: 1. Now you can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter 7.3 Configuration of IGS This operation is now performed by the SMD Setup Wizard.g.corp:40080 Example screenshot for changing settings: (Change) or just double-click on 52 December 2005 . choose the pushbutton Propertysheet.2. choose the pushbutton (Display/Change). you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton 5. Navigate to Server → Services → Configuration Adapter 3.default 6. open the branch for webdynpro → sap. 8. To switch to edit mode. Password is provided separately in the SMD Setup Wizard. 7.wdf.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 installed nwauser Administrator UserId used by SMD for accessing the Netweaver Administrator application.

2.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: you can verify IGSUrl by entering this URL directly into your web browser 9. refer to Installation of CCMS Agent SAPCCMSR [see page 29]. choose the Apply custom pushbutton 7. 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.4 Connectivity to CCMS on Local ABAP Stack This operation is now performed by the SMD Setup Wizard. Prerequisites The CCMS agents of all connected systems have to be registered at the CEN. but can be performed manually as well. but can be performed manually as well. To save the data.5 Setup of Single Sign-On on SMD Server This operation is now performed by the SMD Setup Wizard. The setup has to be performed in two steps.2. Setup Refer to ABAP Connectivity Setup [see page 38] for instruction details. December 2005 53 . 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. 7. Per default this is the local ABAP stack of the SMD server.

e. Note: . 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. the Solution Manager Diagnostics system has to be in the same network domain as the monitored systems Configuration 1.Always use full-qualified hostnames.ticket_client to a number <> 000.sap. 169 54 December 2005 .For SSO scenarios. open the branch for cluster_data → server → cfg → services d) Choose the pushbutton (Display/Change) to switch to the edit mode.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. 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.wdf. e.g.sapsecurity.g.corp .Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 As the Solution Manager Diagnostics contains both Java and ABAP components. 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. This ID will be stored in every ticket and has to be unique. Preparation of the J2EE server of Solution Manager Diagnostics.ume.core. The Client ID of the J2EE system has to be changed. p135809.

2. choose the pushbutton Apply custom.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 i) To save the data. first select the view TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window) December 2005 55 . Exporting certificates from the J2EE server a) Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running b) Navigate to Server → Services → Key Storage c) In the Runtime tab. j) Restart the J2EE Engine of SMD.

choose pushbutton Export and enter any file name. refer to Setup of Single Sign-On on Monitored System [see page 63]. Importing the certificate on SAP ABAP system: refer to Import SSO Certificate to the ABAP Stack [see page 19]. Allow J2EE Engine to create and accept SSO tickets a) Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 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). 3.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 d) To export the certificate on file system. Login Modules 1. This certificate has to be imported into the monitored systems. for Flag choose ‘SUFFICIENT’: • • • • • • ClientCertLoginModule CreateTicketLoginModule CredentialsMappingLoginModule EvaluateAssertionTicketLoginModule EvaluateTicketLoginModule SecuritySessionLoginModule 56 December 2005 .

Choose pushbutton (Create Role) (Profile Generator 4. the according role SAP_SOLMANDIAG_SAPSUPPORT is part of SAP standard delivery. Call transaction PFCG 2. By choosing pushbutton following authorizations sequentially: • S_ADMI_FCD • S_RZL_ADM • S_RFC authorization object that has to contain: ACTVT: NADM. 1. click the Authorizations tab and choose pushbutton expert mode) 5. In addition to the J2EE role. SAL_RFC. Role name Z_SAPSUPPORT is recommended.6 Creation of Role for ABAP User Note: as of NetWeaver 04 SP Stack 13. In the next screen.2. SALF. SALS. the SMD user needs an ABAP role. 03 (Manual entry of authorization objects) and enter the authorization object that has to contain: ACTVT: 16 RFC_NAME: RFC1. December 2005 57 . ST0R authorization object that has to contain: ACTVT: 01. Enter Z_SAPSUPPORT in field Role 3.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 7. SCSMROUTE.

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. RZ20. SYST FUGR authorization object that has to contain: TCD: DB59.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 RFC_TYPE: • S_TCODE SDIFRUNTIME.7 Creation of UME Role for J2EE Engine Note: as of NetWeaver 04 SP Stack 13. ST04M. Choose pushbutton profile 7. ST04_MSS. as a result you will get the technical name of the generated 6. Assign the SMD user (e. 58 December 2005 . Return with the F3 key and choose the Users tab 8. All users for Solution Manager Diagnostics have to be assigned to the role SAP_JAVA_SUPPORT.g. ST03G (Generate). SAPSUPPORT is the recommended user name. OS07. the role SAP_JAVA_SUPPORT is part of SAP standard delivery. 7. SAPSUPPORT) to the generated profile by choosing the User comparison pushbutton Note: For enabling Single Sign-On. DB6COCKPIT.2. SYFU.

>00.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 1.Administrate. navigate to User Management 2. Open the User Management menu within the local J2EE Engine: http://<host>:5<instance no. and apply the role to the user for Solution Manager Diagnostics. Navigate to Roles 4. Verify that the Solution Manager Diagnostics users are member of SAP_JAVA_SUPPORT role December 2005 59 . add the role action com~sap~tc~webdynpro. SAPSUPPORT is recommended as user name 5. Create role SAP_JAVA_SUPPORT within user management. Login as J2EE administrator 3.

1. In the Runtime tab. To modify data. To switch to edit mode.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 7. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running Navigate to Server → Services → Configuration Adapter In the Display configuration tab. 4.properties (Change) or just double-click on Propertysheet 60 December 2005 . 3. choose the pushbutton application.com → tc~webadministrator~navigation~ejb → appcfg 2.global. open the branch for apps → sap.8 Connection to SLD If a SLD (SAP System Landscape Directory) system is installed in your solution landscape. 5. the Solution Manager Diagnostic should be connected to this system. Navigate to Server → Services → SLD Data Supplier 3. choose the pushbutton (Display/Change). 1. select the HTTP Settings tab 4.2. 7. the Solution Manager Diagnostic should be connected to this system. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2.9 Connection to NWA If a NWA (SAP NetWeaver Administrator) system is installed in your solution landscape. Enter the connection information to the SLD server of your solution landscape.2. you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton.

To save modified parameters. For performance analysis of the J2EE Engine. refer to SAP Note 608533 for J2EE Engine 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 A single mouse click will open a new window where you can change the configuration data • • • • • Description: Name: Datatype: Default: Custom: text information for the selected item (cannot be changed) name of the property (cannot be changed) data type of the property item (cannot be changed) SAP-delivered value (cannot be changed) if this field contains a value.wdf. http:// will be added by SMD Note: use fully-qualified host names nwaadmin nwauser Administrator Password The administrator of the SAP NetWeaver administration server The administrator of the SAP NetWaever administration server 9. restart the server node(s) December 2005 61 .20) • -XX:+PrintGCTimeStamps • -XX:+JavaMonitorsInStackTrace (Note: for 6. 8. navigate to cluster-data → Instance_<ID> → Server_<ID> 3.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 6.sap.10 Java Parameter Settings on Monitored System This operation is now performed by the SMD Setup Wizard.40 J2EE Engines. the default value 7. In the General tab.20 and 6.40 J2EE Engines only) (Note: for 6. The following parametes should be modified to match the NetWeaver Administration Console: Name nwahost SAP default protocol://host:port Example http://p135809. the output of garbage collections is required. If no protocol is specified. choose the Apply custom pushbutton 7. refer to SAP Note 696410 for details) 4. apply the Java parameters • -verbose:gc (Note: set this parameter for both 6. but can be performed manually as well.corp:2040 By default the nwahost will be setup to http://<smdserver>:<smdport> Description Server & port where the NWA is running The protocol can be https or http. Start the J2EE Configtool where the monitored system is running 2. but not for Java VMs from IBM or HP.2. Choose the Save pushbutton to save the configuration. For each server node.20 J2EE Engines only. Proceed as follows: 1.

40. open Log Controller Root Category → System → HTTPAccess → Access 4.20 1. these operations are now performed by the Monitored System Setup Wizard. change the value of LogLevel to 6 and apply it by choosing pushbutton Add Activating J2EE log information on J2EE Engine 6. Set Severity to Info and apply this setting to all cluster nodes by choosing the Save pushbutton 5. In the Categories tab. Activating J2EE log information on J2EE Engine 6.11 Setup of HTTP Analysis For SAP J2EE Engines 6. change the value of LogLevel to 6 and apply it by choosing pushbutton Add 7.2. Start the J2EE Configtool of the Enterprise Portal 2. Navigate to Server → Managers → Log Managers 6. In the Properties tab. Navigate to cluster-data → Instance_<ID> → Server_<ID> → Services → http 7.40 1. 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. 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 . but can be performed manually as well. Prerequisites The J2EE Engine has to run with activated log mode. Start the Visual Administrator and log on to the J2EE Engine of the Enterprise Portal 5. Details see below.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 7. Navigate to Server → Services → Log Configurator 3. Start the Visual Administrator and log on to the J2EE Engine of the Enterprise Portal 2. In the Properties tab. This application uses a plug-in (can be downloaded within SMD’s HTTP Analysis application. The user interface of HTTP Analysis displays detailed performance-related information graphically. Start the J2EE Configtool of the Enterprise Portal 6. Navigate to Server → Services → Log 8. Navigate to cluster-data → Instance_<ID> → Server_<ID> → Services → http 3. Apply the following settings: • • • • LogType: LogRequestTime: EnableLoging: LogHeaderValue: notCLF enableall true X-CorrelationID 4.

even on J2EE Engines 6.2.g. The procedure is different for ABAP systems and systems with active J2EE Engines.wdf.40 J2EE Engines Configuration 1. you have to import the certificate for both components . Enterprise Portal) b) Navigate to Server → Services → Key Storage c) In the Runtime tab. to find out if proxy servers.g. or firewalls modify HTTP headers). first select TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window) d) To import the certificate from file system.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Note: In case you want to compare the HTTP message headers between client and server (e.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. e.g. then you also have to switch on parameter LogRequestResponseHeaders maually: LogRequestResponseHeaders = true (Save) 8. 7. For exporting certifcates from SMD. 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. Allow J2EE Engine to create and accept SSO tickets a) Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running December 2005 63 . Note: .Use full-qualified host names. e) Restart the J2EE Engine of the monitored system 2. p135809. but can be performed manually as well.13 Setup of Single Sign-On on Monitored System This operation is now performed by the SMD Setup Wizard.This procedure is valid for both 6.40 has to be installed.sap.If you are running a Web AS with both active ABAP and J2EE components. IIS. Analysis of Garbage Collections (GC) provides information about the memory usage of a J2EE cluster node. To persist all customized settings. Prerequisites Startup Framework 6. Importing the certificate on J2EE system: a) Start the Visual Administrator and log on to the J2EE Engine of the monitored system (e.corp . choose the pushbutton 7.2.20 & 6.20. refer to refer to Setup of Single Sign-On on SMD Server [see page 53]. choose the pushbutton Load.30/6.

Enterprise Portal) to accept SSO tickets: a) Start the Visual Administrator and log on to the J2EE Engine of your monitored system b) Navigate to Server → Services → Security Provider c) Choose SAP-J2EE-Engine (Components window) and open the Authentication tab d) Choose the pushbutton Add New to add the following login modules: • CreateTicketLoginModule • EvaluateTicketLoginModule e) Choose ticket in window Components f) In the Authentication tab.g.jaas.core.server.EvaluateTicketLoginModule g) To add properties. choose the pushbutton Modify 64 December 2005 .security.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 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) or Flag choose ‘SUFFICIENT’: • • • • • • ClientCertLoginModule CreateTicketLoginModule CredentialsMappingLoginModule EvaluateAssertionTicketLoginModule EvaluateTicketLoginModule SecuritySessionLoginModule 3. Allow J2EE application (e.sap. choose Login Module com.

server host>:<msg.configuration.g.C=<country> are optional <SID of Solution Manager Diagnostics>. Note: There is a naming convention to follow if you create the HTTP destinations manually. Navigate to Server → Services → Destinations 3.com/tc~wd~dispwda*webdynpro_welcome (Web Dynpro Console) 7.40 system you want to monitor • <msg. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2.C=<country> e. In the Runtime tab. CN=WA1 Note: O=<company>.40 based monitored system only.active: • trustediss1: true CN=<SID of SMD>.com/tc~wd~dispwda*webdynpro_dispatcher (Web Dynpro Console) sap. Note: Proceed as follows: 1.<client ID> e.g.com/tc~monitoring~systeminfo*sap_monitoring (Systeminfo) sap. Now change the Authentication Template for the following applications in the Components window to ticket (drop-down box): • • • • • sap.O=<company>. Example: HTTP:CCR:p79588:3601 December 2005 65 .169 • trusteddn1: • trustedsys1: Confirm settings with the OK pushbutton.O=<company>.C=<country> e.g. Create destination HTTP:CCR:<msg.com/SQL_Trace*OpenSQLMonitors (SQL Trace) sap. server host>: Hostname of the 6. WA1. CN=WA1 Note: O=<company>. The host name of the destination has to be in lower case format and without domain name. server port>: Port of the message server from the monitored system HTTP(S) Destinations have to be created for 6. server port> • <msg. open the branch for HTTP 4.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • ume.14 Creation of HTTP Destinations This operation is now performed by the SMD Setup Wizard.2.C=<country> are optional CN=<SID of SMD>. 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.com/SQL_Trace*OpenSQLTrace (SQL Trace) sap. but can be performed manually as well.

wdf. 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.depending on your security policy. activate Accept certificates in keystore view and choose service_ssl . Choose the Save pushbutton to store your settings 66 December 2005 . Example: http://p79588.corp:50000/sap/monitoring/ SystemConfigurationDownloadServlet 6. Select BASIC as authentication Note: For HTTPS scenarios. In the URL field.now.enter https instead of http in the URL . Enter user name and password of the J2EE administrator from the 6.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 5. procedd as follows: . in the Server Certificates section.40 system you want to monitor 8.sap. select BASIC or Logon Ticket as authentication 7.

you have to install the corresponding JDBC driver within the SMD system. If the database type or version is different from the Solution Manager Diagnostics db.jar) at: <J2EE home dir>/cluster/server<n>/bin/ext/com. name it according to the table below and choose the Ok pushbutton: December 2005 67 . . Login to the Visual Administrator of SMD and navigate to Server → Services → JDBC Connector 2.sap.You have to create a DataSource for each Portal instance within your solution / landscape. you will find the corresponding Java files (extension: . you will find the corresponding Java files (extension: .20 has been installed yet.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 7. different values have to be entered during the setup (Create New Driver or Data Source) in the a) Select Drivers and choose the pushbutton toolbar.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.jar) at: <J2EE home dir>/cluster/server/additional-lib/com/sap/data_direct_driver_references If no driver for the database running on 6. Configuration of JDBC Connector 1.2.datadirect (MS SQL Server) or <MaxDB home dir>/programs/runtime/jar (MaxDB). Otherwise you can use the driver SYSTEM_DRIVER. Setup the Database Driver & Data source. The driver for Oracle is part of the Oracle client (dbdependent part of the ABAP kernel). depending on the database of the Portal server Note: .40 has been installed yet. If no driver for the database running on 6.Depending on the DBMS.

jar classes12. WCR.jar. sqlserver. don’t enter Application Name f) In the dropdown box Driver Name choose the name created in step a) 68 December 2005 . and Description (optionally).jar db2jcc. (Create New Driver or Data Source) in c) Select DataSources and choose the pushbutton the toolbar d) Go to tab Main e) Enter Name. util.jar.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.g. db2jcc_license_cu.jar.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 MS SQL SERVER Oracle MAX DB DB2 Wcr_SAP_SQLServer Wcr_Oracle Wcr_Maxdb Wcr_Db2 b) Choose the files below depending on the type of DB: MS SQL SERVER Oracle MAX DB DB2 base.jar sapdbc. e.

db2. and choose as SQL Engine .DatabaseName=<DBSID> e. jdbc:sapdb://P114280/TYR jdbc:db2://<host>:<port>/<DBSID> e. only the last 5 characters are used.g.OracleDriver com.driver.jcc. jdbc:oracle:thin:@us7201:1527:EP0 jdbc:sapdb://<host>/<DBSID> e.sap.g. SAP/BC_WA_WCR01 Note: for mapping the alias. Max Connections to 5. SAPP62DB j) Choose pushbutton Add Alias to create an unique Alias for the landscape: SAP/BC_WA_WCR<nn> (<nn>=01 . e..20 Portal: Native SQL (for Portals running on J2EE 6. jdbc:db2://P114280:5912/TYR com.DriverSapDB com.g.ibm.g. afterwards you should see a new data source named WcrDataSource December 2005 69 .jdbc.sqlserver.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 g) As Driver Class enter: MS SQL SERVER Oracle MAX DB DB2 h) As Database URL enter: MS SQL SERVER jdbc:datadirect:sqlserver://<host>:<port>.6. jdbc:datadirect:sqlserver://p78293:1433. e.DB2Driver Oracle MAX DB DB2 i) Enter User and Password of the database schema owner SAP<SID>DB.DatabaseName=P62 jdbc:oracle:thin:@<host>:<port>:<DBSID> e.0) . WCR01 k) Go to tab Additional l) Change the number of Initial Connections to 1.SQLServerDriver oracle.ddtek.jdbc.40 Portal: Open SQL m) Choose the pushbutton (Save) to save the configuration. 10) e.g.g.jdbc.g.dbtech.6.

Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 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 .

smdagent.properties: user has been set.STEP 6: generating SecStore secstore.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 If not.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.2_07 smdserver.bat for Windows OS smdagent.2_04-er .2.STEP 2: checking JDK Version JDK Version is correct: 1. secstore..2_04\bin .properties: has been created.SMD Agent Setup ..com/JDBCConnector_<name>. you may restart the sap.bat has been created.bat C:\j2sdk1.4. Step 3: makes sure the SMD Server machine (host name) is visible and waiting on the P4 port specified.sap.STEP 3: checking Connection to SMD Server SMD Server check completed successfully .properties has been created. ----------------------------------------------------------------------------.16 Manual Setup of SMD Agent The steps below are now executed by the SMD SAPinst module.wdf.xml service by choosing the pushbutton (Stop Service) and afterwards the pushbutton (Start Service) 7.corp 50004 adminuser adminpassword SMD Agent Setup Steps When running properly. o o smdagent.4.properties file to persist the parameters specified. secstore. .sh for Unix OS Step 6: generates SecStore file required for establishing a secure connection to the SMD Server. but still can be performed manually.STEP 4: generating Runtime Properties runtime. .STEP 5: generating Launcher smdagent.sh has been created.STEP 1: checking JDK location JDK location is consistent: C:\j2sdk1. Command Line Example on Windows cd \usr\sap\SMD/J<Inst Nr>/SMDAgent/ smdsetup.properties generation completed successfully. Step 4: generates a runtime.4. .Copyright (c) 2005 SAP AG ----------------------------------------------------------------------------SMD Agent Setup is in process . December 2005 71 . the SMD Agent setup output looks like below: ----------------------------------------------------------------------------SAP Solution Manager Diagnostic . Step 5: generates the scripts used to start the SMD Agent.

Refer to SAP Note 212876 how to operate SAPCAR. a SAP solution without ABAP and Java components (e. create the user by proceeding as follows: 1. 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). the CCMS agents delivered with the installation have to be exchanged. There is a CSMREG user in CEN. In CEN. Configuration 1. Log on to the host of a J2EE Engine of the system as <SID>adm. 2. In CEN. This registration relies on the SAP J2EE P4 protocol.40. you require the connection data from the agent to CEN. Enter any password for this user.Download the current version of SAPOSCOL from the SAP Service Marketplace: service. • During the registration of the agent. 7. call transaction RZ21. since you require the file for all agent registrations. call transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User. If this is not yet the case.sar contains the CCMS Agent archived.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. and confirm your entries by choosing the Create CSMREG pushbutton.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Step 7: checks the generated runtime environment and clearly shows whether the SMD agent registration to the SMD Server can be done.17 Download & Setup of CCMS Agent Download CCMS Agent from SAP Service Marketplace For a SAP solution with release < 6. and choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents.g. To do this. We recommend that you generate this data in a CSMCONF file in CEN before the registration. Refer to SAP Note 734247 for additional information.Extract the CCMS Agent with SAPCAR. proceed as follows: 1. Proceed as follows: 1.40 32-bit → <choose OS> → Database independent → ccm agent. 2.sap. 72 December 2005 .2. TREX) or a non-SAP solution. Save the file CSMCONF at a location that is centrally available. 2. The file ccmagent<version>.

select the Long SID indicator. 6. In the navigation bar.bat (Microsoft Windows). enter the password for the user in CEN. 2. Choose the agent configuration file: CCMSCONF 5. There is a CSMREG user in CEN. Enter any password for this user.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 2. No. and choose the CCMS Agent Configuration tab page. Location of sapccmsr. and log on with your user as the J2EE Engine administrator. To enable log file monitoring. No.ini: • Windows: • UNIX: [drive]:\usr\sap\ccms\<SysID>_<Inst. Click on the register button. recommendation: user SAPSUPPORT. 7. December 2005 73 . No. create the user by proceeding as follows: 1.>/sapccmsr 3. Start the Visual Administrator by calling the start script go (UNIX) or go. If this is not yet the case. • The name must not contain an underscore (_). If you want to monitor multiple systems with the same system ID.>\sapccmsr /usr/sap/ccms/<SysID>_<Inst. In the Password for Administration User input field. and enter in this input field an identifier for the system that is unique in your monitored system landscape.ini has to be modified. Copy the start file CSMCONF to the following directory: • Windows: • UNIX: [drive]:\usr\sap\ccms\<SysID>_<Inst. No. call transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User. In CEN. In the Password for CSMREG User input field.>/sapccmsr 9. the CCMS agent’s configuration file sapccmsr. enter the password for the CSMREG user in CEN. and confirm your entries by choosing the Create CSMREG pushbutton. 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) • • You have a Solution Manager Diagnostics systems that contains the central monitoring system (CEN). 4. 8. • The name can be a maximum of eight characters long. choose Cluster → <SysID> → Dispatcher → Services → Monitoring. This “long system ID” must fulfill the following conditions: • The first three characters must be the system ID.>\sapccmsr /usr/sap/ccms/<SysID>_<Inst.

You must now also enter the connection data for the secondary central system. No. enter the following command: sapccmsr –R –j2ee pf=<path of the instance profile> Note: The complete path of the instance profile is (here.>_<Host> In the case of a dialog instance. Save the file CSMCONF at a location that is centrally available. To do this. Nr. in this case. SAP XI) – not on the CEN. In this manual registration. No. this is CEN.>\ sapccmsr\SAPCCMSR_<SysID>_<Inst. 2.PFL 4.>. on the host of the monitored instance.>. you can find it in the CSMCONF file that you created in CEN. You must now manually register the relevant agent for each Java instance to the CEN.g. In this case. 74 December 2005 . the CCMS agent has to be registered on the ABAP gateway of the same system (e. Visual Admin created a profile for the agent in its working directory during registration: • Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. for example. call transaction RZ21. Dir. In CEN. switch to the directory in which the executable for the CCMS agent SAPCCMSR is located: • Windows: • UNIX: <J2EE home directory>\SYS\exe\runU <J2EE home directory>/SYS/exe/runU 3. for Windows): <J2EE home directory>\SYS\exe\profile\<SysID>_<Inst. We recommend that you generate this data in a CSMCONF file in CEN before the registration.PFL • UNIX: /usr/sap/ccms/<SysID>_<Inst. Follow steps 1 – 9 of Setup of CCMS Agent on a NetWeaver Java Instance [see page 72] Note: During this step. No. 2.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • During the registration of the agent. To do this. proceed as follows: 1. and choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents. and specify the system ID of the system: additional CENTRAL system y/[n] ? : R/3 system ID: additional CENTRAL system y/[n] ? : y <CEN> n 5.>/ sapccmsr/SAPCCMSR_<SysID>_<Inst. To register the agent manually. you require the connection data from the agent to CEN. since you require the file for all agent registrations. Configuration 1. this path does not exist. you next enter that there is exactly one additional central system. If you do not have the data.

Save the file CSMCONF at a location that is centrally available. you require the connection data from the agent to CEN. if the directory does not exist. create the user by proceeding as follows: 1. If this is not yet the case. Configuration 1.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 6. 2. 2. Location of sapccmsr. To enable log file monitoring.ini has to be modifed.>/sapccmsr 8. No. • During the registration of the agent. such as system groups to which the monitored system belongs. Confirm additional details. since you require the file for all agent registrations. It is important that there is a share available with the name saploc. To do this. There is a CSMREG user in CEN. proceed as follows: 1. call transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User. Enter any password for this user. and confirm your entries by choosing the Create CSMREG pushbutton. create it manually. 7. call transaction RZ21.>\sapccmsr /usr/sap/ccms/<SysID>_<Inst. and choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents. We recommend that you generate this data in a CSMCONF file in CEN before the registration. Copy the agent’s executable to the following directory. 2. Restart the CCMS agent Setup of CCMS Agent on a J2EE 6. Copy the start file CSMCONF to the following directory: December 2005 75 . create it: • Windows: • UNIX: \\host\saploc\prfclog /usr/sap/ccms/bin Note: The saploc directory can also have another name.20 System 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). or details about setting up the service with the ENTER key. the CCMS agent’s configuration file sapccmsr. In CEN. by default. In CEN. If this share does not exist.ini: • Windows: • UNIX: [drive]:\usr\sap\ccms\<SysID>_<Inst. No. it is the directory <drive:>\usr\sap.

and is automatically started during a restart of the host. • For UNIX. you must ensure yourself that the agent is automatically started when you restart the host. Start the Java tool by entering the following command at the operating system prompt in the above temporary directory: java -jar csmagent. The input fields Agent Configuration File and Agent Executable should be filled with the correct values. Choose the Register button. Call SAP Note 730629 (CCMS agents: Java interface for registration). The registration log is displayed. Copy the file csmagent.jar from the Note’s attachment to a temporary directory on the host to be monitored. Note: • For Microsoft Windows. errors are highlighted in red. Under UNIX. 4. recommendation: user SAPSUPPORT.jar 5. enter the following command in the inittab: su . In the Password for CSMREG User input field. Select the radio button Standalone/TREX/SAP J2EE Engine 6. the SMD Agent is entered as a service during the registration. In the Password for Administration User input field.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • Windows: • UNIX: \\saploc\prfclog\sapccmsr /usr/sap/tmp/sapccmsr 3. 6.<SID>adm -c '/usr/sap/ccms/bin/sapccmsr -DCCMS' 76 December 2005 . 8.20. To do this. enter the password for the user in CEN. 7. the agent is automatically ‘ started by the script startsap when you start the J2EE Engine. enter the password for the CSMREG user in CEN.

It is important that there is a share available with the name saploc. Copy the agent’s executable to the following directory. In CEN. Configuration 1. Restart the CCMS agent Note: For SAP CRM and SAP XI systems. sapccm4x has to be installed in addition. There is a CSMREG user in CEN. the CCMS agent’s configuration file sapccmsr. proceed as follows: 1.>\sapccmsr /usr/sap/ccms/<SysID>_<Inst. create the user by proceeding as follows: 1. 2. by default. create it: • Windows: • UNIX: \\host\saploc\prfclog /usr/sap/ccms/bin Note: The saploc directory can also have another name. call transaction RZ21. Save the file CSMCONF at a location that is centrally available.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 9. No. Enter any password for this user. To enable log file monitoring. if the directory does not exist. If this share does not exist.ini: • Windows: • UNIX: [drive]:\usr\sap\ccms\<SysID>_<Inst. To do this. If this is not yet the case. 2. since you require the file for all agent registrations. and confirm your entries by choosing the Create CSMREG pushbutton. and choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents. you require the connection data from the agent to CEN.>/sapccmsr 10. 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: • • You have a Solution Manager Diagnostics systems that contains the central monitoring system (CEN). No. create it manually. Copy the start file CSMCONF to the following directory: December 2005 77 . In CEN. Location of sapccmsr.ini has to be modifed. We recommend that you generate this data in a CSMCONF file in CEN before the registration. 2. call transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User. it is the directory <drive:>\usr\sap. • During the registration of the agent.

It is technically based on a database driver.18 Creation of Drivers & Data Sources The screen Creation of Drivers and Data Sources dor Monitored Systems consists of 2 tabs: o o Data Sources Database Drivers A data source is used to connect to a Monitored System database. To enable log file monitoring.ini: • Windows: • UNIX: [drive]:\usr\sap\ccms\<SysID>_<Inst. 5. Required information: o o db driver name jar files of the db driver Example screenshot: 78 December 2005 .2. Location of sapccmsr.g. the database driver is just a set of JAR files that will be used when the data source attempts to establish the connection. the CCMS agent’s configuration file sapccmsr.>\sapccmsr /usr/sap/ccms/<SysID>_<Inst. You have to register the agent manually. or details about setting up the service with the ENTER key. e. you have to enter passwords for the administration user and the user CSMREG. Restart the CCMS agent 7. sapccmsr –R f=c:\usr\sap\prfclog\CSMCONF 3.>/sapccmsr 6. In this manual registration.ini has to be modifed.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 • Windows: • UNIX: \\saploc\prfclog\sapccmsr /usr/sap/tmp/sapccmsr 3. No. Confirm additional details. enter the following command: sapccmsr –R f=<path and filename of CSMCONF>. 4. Database Driver Creation From the SAP J2EE Engine point of view. No. such as system groups to which the monitored system belongs.

add them by choosing the Add Jar button. as these files will be read and used by the server to create the driver. e. You do not have to create one driver per data source. 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. Once all the necessary drivers have been created. December 2005 79 . A driver can be re-used by several data sources. This step has to be performed for each different db system.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 The top table shows the already existing database drivers. the associated data sources can be created. Please note that the SYSTEM_DRIVER entry represents the driver dedicated to the SAP J2EE Engine itself. After entering. Note: If the monitored system runs on the same database type as your monitoring system.g. if you wish to monitor one system running with an Oracle DB and another one running with MS_SQL. you can just use the SYSTEM_DRIVER. So if all monitored systems run on the same database type as the monitoring system. you do not need to create a driver. it is always delivered and should not be deleted (the UI will not let you do so anyway) but can be re-used. Go to the Data Sources tab. 2 db drivers have to be created. the SYSTEM_DRIVER can be used for all the data sources. The provided files have to be accessible from the called server (check URL in web browser).

Keep in mind that this information is for the database of the monitored system.40 or 6.20. Required information: o o o o o Data Source name: User’s choice. The bottom part allows the user to enter the necessary information to create a new Data Source. it can be changed. It will change the way the database is accessed (Open SQL or Native SQL). You need to enter the information related to the remote DB: o host o 80 December 2005 . 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. so you can change it if it is not conform to your driver. Database Driver: You need to select it from the drop-down list. Monitored System Version: either 6. It is only a template value. Database type: Once you have selected a type the fields about the driver and the JDBC URL will be updated with templates. JDBC URL: Once again by default a template is displayed. JDBC Driver Class: It depends on the type of database that you have selected.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Data Source Creation Example screenshot: The top table shows the already existing Data Sources and their aliases. If there is no driver that fits your need you will need to create one manually (refer to the previous section for more details).

1. choose the Next pushbutton. Most likely there is a problem with some of the parameters or the remote database is not available. if everything was correct. otherwise an error message will be displayed. you need to select it from the drop-down list.properties in edit mode within tree Configurations → apps → sap.19 Mapping of Solution Landscape to DB Alias This operation is now performed by the SMD Setup Wizard.Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 o o o port instance ID (according to its type) Data source Alias Number: This is a value from 01 to 10. please refer to the section Setup of DB Connectivity to Monitored Systems [see page 67]. but can be performed manually as well. If a problem occurs with these operations and you need to perform them manually. or if you want to double check the settings. choose the Create Data Source button. Only 10 remote databases can be monitored. Once you have entered the information. or if you want to get more details on this. Once all the necessary Data Sources have been created. You will need to remove the Data Source and re-create it. 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.com → tc~webadministrator~wcrep~ws → appcfg 3. Within Visual Administrator navigate to Server → Services → Configuration Adapter 2.application. 7. Make an entry for each database alias December 2005 81 . the new Data Source will appear in the top table.global. Open Propertysheet. this restriction is explained in the section Mapping of Solution Landscape to DB Alias [see page 81].2.

Supportability Setup Guide: Solution Manager Diagnostics SAP NetWeaver 04 SP Stack 14 Description: • Name: information for the database alias.g. cannot be changed default value.lang. java. 82 December 2005 . cannot be changed name of the monitored product within the solution: <Solution name><SID><Installation number> e. WAS640_SINGLE_HOSTJ2E47110815 • Datatype: • Default: • Custom: Note: There must be no spaces in the name. cannot be changed WCR01…WCR10 (database alias. For detailed information refer to the section Setup of DB Connectivity to Monitored Systems [see page 67].String. cannot be changed). The database aliases are created in the SMD Setup Wizard.

Sign up to vote on this title
UsefulNot useful