SAP NetWeaver Guide. Advanced Supportability Setup Guide. for. Solution Manager Diagnostics. SAP NetWeaver 04

Transcription

1 SAP NetWeaver Guide Advanced Supportability Setup Guide for Solution Manager Diagnostics SAP NetWeaver 04 Document Version 3 February 24, 2006

2 SAP AG Neurottstraße Walldorf Germany T +49/18 05/ F +49/18 05/ Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP Library document classification: PUBLIC Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. Documentation in the SAP Service Marketplace You can find this documentation at the following Internet address: service.sap.com/instguides SAP Library document classification: PUBLIC 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

3 Typographic Conventions Icons Type Style Example Text Example text EXAMPLE TEXT Example text 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 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. <Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Icon Meaning Caution Example Note Recommendation Syntax

4 Advanced Supportability Setup Guide Solution Manager Diagnostics SAP NetWeaver Introduction Naming Conventions Installation Step by Step Installation Planning Required Documentation SAP Installation Notes Information in the SAP Service Marketplace Components for Problem Messages Hardware and Software Requirements for SMD Server Software Requirements for Monitored Systems Installation Process Deatailed Descritption of Automated Setup Tasks on SMD Server Java Parameter Settings on SMD Server SAP ITS SAP IGS Creation of HTTP Destinations Setup of Single Sign-On on SMD Server Import Single Sign-On Certificate into the ABAP Stack Creation of Role for ABAP User Creation of Support Roles for J2EE Engine Connection to SLD Connection to NWA Deatailed Descritption of Automated Setup Tasks on Monitored Systems Java Parameter Settings on Monitored J2EE Engines Setup of Single Sign-On on Monitored Systems Assignment of J2EE Server Roles to the Support User Setup of HTTP Analysis Setup of Thread Dump and GC Analysis Setup of Software Change Reporting for SAP Enterprise Portals Setup of Session Tracing for SAP J2EE Engines Setup of ICM Logging Setup of SMD Keystore / SSL Application Setup of Portal Activity Reporting Manual Setup of Portal Activity Reporting Create the DB Connectivity to the Monitored Systems Configuration Steps Mapping of Solution Landscape to DB Alias Setup of SMD Scheduler First Initialization of the Scheduler Setup of Tasks Data Collection from Monitored System Setup of SMD Agent Manual Setup of SMD Agent Command Line Execution SMD Agent Setup Steps SMD Agent Start Profile Change Credentials of SMD Agent SSL Setup for SMD Agent February

5 7.2 Configuration of SMD Agent Applications J2EE Command Console Configuration File System Access Configuration SQL Command Console Configuration OS Command Console Configuration Log Viewer Configuration Setup of CCMS Agent Download CCMS Agent from SAP Service Marketplace Setup of CCMS Agent on a NetWeaver Java Instance Setup of CCMS Agent on a Double-Stack System Setup of CCMS Agent on a J2EE 6.20 System Setup of CCMS Agent on a Non-SAP System...64 February

6 Advanced Supportability Setup Guide Solution Manager Diagnostics SAP NetWeaver 04 1 Introduction Support Infrastructure with Solution Manager Diagnostics Solution Manager Diagnostics (SMD) provides essential functions for efficient and safe root cause analysis of customer solutions based on SAP NetWeaver 04. It especially provides functionality to support Java based components therefore an active Java stack is required on your central SMD system. This system should also be used as central system for collecting and handling alerts (CCMS alert handling) therefore we also recommend setting up SMD for any SAP NetWeaver landscape. For measuring performance as well as to troubleshoot problems of the J2EE Engine and its applications, Wily Introscope is integrated into the SMD. The Introscope tool consists of a display, a server part (Introscope Enterprise Server) and a client part (Introscope agent). Finally, SMD contains the Mercury Interactive load generator tool that enables remote load testing by SAP Support (e.g. during Going Live checks) in order to detect performance bottlenecks. It is mandatory to install one Solution Manager Diagnostics within your SAP NetWeaver solution landscape. One SMD system can monitor any number of SAP NetWeaver solutions. High-level overview of the support infrastructure: For detailed information about Solution Manager Diagnostics including end user documentation, see Solution Manager Diagnostics [page 11]. 6 February 2006

7 Solution Manager Diagnostics Landscape To monitor a NetWeaver solution landscape, Solution Manager Diagnostics relies on five components: SMD Server SAP J2EE Engine service running on SMD, waiting for SMD Agents to register. SMD Navigation Java Web Dynpro component providing access to all tools related to monitor a NetWeaver system. The list of monitoring tools is depending on the type of the monitored NetWeaver system. SMD Monitoring Tools Java Web Dynpro applications offering monitoring capabilities. SMD Agent Java application running on the monitored systems and gathering information for the SMD Server. Component Analyzer Java Application defining the type of the NetWeaver component to monitor, started by the SMD Agent to retrieve the configuration and monitoring information used by the SMD Server. SAP SolManDiag SMD Navigation SMD Monitoring Tools Component Analyzer SMD Agent NetWeaver Solution Landscape Implementation This guide explains in detail the setup of Solution Manager Diagnostics and connected systems. 1.1 Naming Conventions In this documentation, the following naming conventions apply: Terminology The term CA is the same as Component Analyzer The term NWA is the same as NetWeaver Administrator The term SMD is the same as Solution Manager Diagnostics Monitoring System is a general term for the central entry point of system analysis & monitoring. In a SMD scenario, Monitoring System is the SMD system. Monitored System is a general term for a satellite system connected to SMD (e.g. Enterprise Portal) February

8 Variables Variables <SID> <DBSID> <INSTDIR> <J2EE_HOME> <JAVA_HOME> <OS> Description SAP system ID Database system ID Installation directory of the SAP system Installation directory of the J2EE Engine Installation directory of the JDK (Java Development Kit) Operating system name within a path 8 February 2006

9 2 Installation Step by Step Advanced (Non-Standard) Installation This guide contains all information to perform a Solution Manager Diagnostics installation on systems that need additional manual configuration steps, e.g. setup of a monitored Enterprise Portal EP 6 SP 2. Standard Installation Refer to Solution Manager Diagnostics (Standard Guide) for a standard installation step list, e.g. wizardbased setup of a monitored SAP J2EE Engine February

10 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 SAP Installation Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find in the SAP Service Marketplace at the Internet address: service.sap.com/notes. SAP Note Number Title Installing the HTTP Connect service Java VM settings for J2EE 6.30/ CCMS agents: Java interface for registration Remarks Setup of Solution Manager Diagnostics up-to-date setup information for SMD Wily Introscope Installation for SAP Customers GoingLive Check Optimization - Remote Load Testing up-to-date setup information for Wily Introscope up-to-date setup information for Mercury LoadGenerator Installation of Component Analyzer up-to-date setup information for CA How do I get Solution Manager Diagnostics? Composite Note for Solution Manager Diagnostics use cases for SMD HTTP analysis with IE plugin up-to-date setup information for Mercury LoadGenerator Enable Remote Connection for NetWeaver usage EP Portal Activity Report Web Service Security Issue Sizing of Solution Manager Diagnostics up-to-date setup information for Mercury LoadGenerator configure web service for PAR (for SAP NW Portals only) 10 February 2006

11 3.1.2 Information in the SAP Service Marketplace Information on the following areas is available in the SAP Service Marketplace. We recommend that you read this documentation before starting the installation. Solution Manager Diagnostics (Standard Guide) You will find the current version of the Solution Manager Diagnostics setup guide at service.sap.com/nw04operation Supportability Supp. Setup Guide Solution Manager Diagnostics NW04 SPS 15. General documentation for Solution Manager Diagnostics: start SAP Service Marketplace, and go to the Solution Manager Diagnostics area (service.sap.com/diagnostics). Solution Manager Diagnostics (Advanced Guide) In addition to the standard guide, the advanced guide provides more detailed information on the setup procedure of automated tasks, plus some information for non-standard SMD scenarios. You will find the current version of the Solution Manager Diagnostics advanced setup guide at service.sap.com/nw04operation Supportability Supp. Setup Guide - SoManDiag NW04 advanced. Component Analyzer You will find the current version of the Component Analyzer setup guide at service.sap.com/nw04operation Supportability Supp. Setup Guide - Component Analyzer NW04 SPS 15. End user documentation & FAQ list You will find the end user documentation and a FAQ list for Solution Manager Diagnostics at service.sap.com/diagnostics. CCMS Agents Simplified setup steps of the CCMS Agent are explained in this guide. Otherwise, you can find the documentation for the CCMS Agents on SAP Service Marketplace at the System Monitoring and Alert Management area (service.sap.com/monitoring). Choose Monitoring in Detail, and choose the document CCMS Agents: Features, Installation, and Usage. OS Collector Documentation for SAPOSCOL: start SAP Service Marketplace, and go to the System Monitoring and Alert Management area (service.sap.com/monitoring). Choose Monitoring in Detail, and then choose the document SAPOSCOL: Properties, Installation, and Operation. February

12 3.1.3 Components for Problem Messages In case of problems, contact SAP Support by creating a message in Service Marketplace, components: BC-JAS-ADM-CEN-AIN issues related to Solution Manager Diagnostics BC-CCM-MON-CAN issues related to Component Analyzer XX-PART-MIC issues related to Mercury LoadGenerator XX-PART-WILY issues related to Wily Introscope 3.2 Hardware and Software Requirements for SMD Server Make sure to apply the mentioned program versions or newer versions. All packages can be downloaded from SAP Service Marketplace.The following table lists the requirements: Requirement Type Hardware Requirements Requirement Disk Space: 40 GB RAM: 4 GB Virtual Memory: 3 x size of physical memory Number of CPUs: 2 Software Requirements SAP Web AS 6.40 Java Add-In, SP Stack 15 ABAP Kernel patch 80 Platform-dependent information is available on service.sap.com/pam, refer to for SAP Web AS For detailed sizing information, refer to SAP Note Software Requirements for Monitored Systems For systems monitored by Solution Manager Diagnostics, make sure to apply the mentioned program versions or newer versions. All packages can be downloaded from SAP Service Marketplace.The following table lists the requirements: Software Component SAP Enterprise Portal EP 6 SP 2 SAP NetWeaver 04 Portal other NetWeaver 04 systems Requirement Portal Patch 5, Build 2 J2EE Engine 6.20 SP Stack 25 Startup Framework 6.30/6.40 J2EE Engine 6.40 SP Stack 10 SP Stack February 2006

13 4 Installation Process This chapter contains detailed information for installation & setup of Solution Manager Diagnostics, setup of monitored systems and establishing the connection between Solution Manager Diagnostics and monitored systems. Most of these steps are performed by the Monitoring (SMD) or Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. 4.1 Deatailed Descritption of Automated Setup Tasks on SMD Server The following sections contain detailed information for installation & setup of the SMD Server. Here you can find the description of automated actions for the Monitoring System (SMD Server) performed by the SMD Administration application. The SMD Administration application can be launched by URL: Note: You have to log on as J2EE administrator to the SMD Administration application. In case of problems, these configuration steps can be performed manually as well what is explained here in detail Java Parameter Settings on SMD Server This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. For performance analysis of the SMD Server itself, the output of garbage collections is required. To adapt the settings for the SMD Server, proceed as follows: 1. Start the J2EE Configtool where the Solution Manager Diagnostics is running 2. For each server node, navigate to cluster-data Instance_<ID> Server_<ID> 3. In the General tab, apply the Java parameters -verbose:gc -XX:+PrintGCTimeStamps (except on IBM JVM-based systems, see SAP Note ) February

14 4. Navigate to cluster-data Instance_<ID> Server_<ID> Services http 5. In the Global properties tab, apply the parameters by entering into the Value field: CompressedOthers: true MinimumGzipLength: 1024 NeverCompressed: by choosing the Set pushbutton after every change remove entries for *.js, *.cs, *.css 6. To persist all customized settings, choose the pushbutton (Save) SAP ITS ITS Port Number Determination SAP ITS (Internet Transaction Server) enables the access to ABAP based transactions via web browser. General information for the setup of SAP ITS is available in the SAP Library. 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 14 February 2006

15 Test ITS To test the ITS Webgui service, start ABAP transaction SICF and navigate within the tree on the left side to default_host sap bc gui sap its. Right-click on webgui and choose Test Service. On success, a new window will be opened within the web browser. To find out the HTTP port for ITS, start ABAP transaction SMICM and navigate to Goto Services. In the next screen, you will find the HTTP port (e.g. 8000) in line HTTP, column Service Name/Port: This is the port number that you will need to provide to the SMD Setup Wizard. Configuration of ITS This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Get the ITS Port as described in chapter ITS Port Number Determination [see page 14]. February

16 To adapt the settings for Solution Manager Diagnostics, proceed as follows: 1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. Navigate to Server Services Configuration Adapter 3. In the Display configuration tab, open the branch for apps sap.com tc~webadministrator~navigation~ejb appcfg 4. To switch to edit mode, choose the pushbutton (Display/Change); you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton 5. To modify data, choose the pushbutton (Change) or just double-click on Propertysheet application.global.properties 6. Now you can change customizing entries by positioning the mouse pointer to the line where you find the information that has to be adapted 7. A single mouse click will open a new window where you can change the configuration data Description: 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, the default value will be overwritten Example screenshot for changing settings: 16 February 2006

17 8. To save modified parameters, choose the Apply custom pushbutton Parameters that can be customized: Name SAP default Example Description itsclient logon client of the SAP ITS system itshost protocol://host:port wahost protocol://host:port Server & port where the ITS is running The protocol can be https or http. If no protocol is specified, will be added by SMD Note: use fully-qualified host names Server & port where the Wily Introscope Webview has been installed. For installation details, refer to Solution Manager Diagnostics (Standard Guide). The protocol can be https or http. If no protocol is specified, http will be used. Note: - the port depends on the protocol used - server can differ from itshost February

18 nwahost Protocol://host:port Server & port where the Netweaver Administrator application has been installed nwauser Administrator UserId used by SMD for accessing the Netweaver Administrator application. Password is provided separately in the SMD Setup Wizard SAP IGS IGS Port Number Determination SAP IGS (Internet Graphics Server) enables the output of graphics within ABAP based transactions. General information for the setup of SAP IGS is available in the SAP Library. Prerequisites The following RFC destinations have to be updated by using transaction SM59 on the ABAP stack - make sure that field Program ID contains IGS.<SID>, e.g. IGS.SMD. GFW_ITS_RFC_DEST IGS_RFC_DEST Test IGS To test the IGS service, start ABAP transaction SA38 and run program GRAPHICS_IGS_ADMIN, use as IGS RFC destination IGS_RFC_DEST. If example graphics are displayed, the IGS service is running properly. To find out the IGS port, choose the pushbutton Status. You will find the port number in table CONNECTED_LISTENER, line Http, row Parameter (e.g ): 18 February 2006

19 Configuration of IGS This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Get the ITS Port as described in chapter IGS Port Number Determination [see page 18]. To adapt the settings for Solution Manager Diagnostics, proceed as follows: 1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. Navigate to Server Services Configuration Adapter 3. In the Display configuration tab, open the branch for webdynpro sap.com tc~wd~dispwda 4. To switch to edit mode, choose the pushbutton (Display/Change); you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton 5. To modify data, choose the pushbutton (Change) or just double-click on Propertysheet.default 6. Now you can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter 7. A single mouse click will open a new window where you can change the configuration data. 8. Change parameter IGSUrl to URL & port of the IGS, e.g. Example screenshot for changing settings: February

20 Note: you can verify IGSUrl by entering this URL directly into your web browser 9. To save the data, choose the Apply custom pushbutton Creation of HTTP Destinations This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Note: HTTP(S) Destinations have to be created for 6.40 based monitored system only. Proceed as follows: 1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. Navigate to Server Services Destinations 3. In the Runtime tab, open the branch for HTTP 4. Create destination server host>:<msg. server port> <msg. server host>: Hostname of the 6.40 system you want to monitor <msg. server port>: Port of the message server from the monitored system 20 February 2006

21 Note: There is a naming convention to follow if you create the HTTP destinations manually. The reason behind this naming convention is that the Component Analyzer of the monitored hosts will try to read the HTTP Destinations and it expects them to be in a certain format. The host name of the destination has to be in lower case format and without domain name. Example: 5. In the URL field, enter name>:<j2ee port>/sap/monitoring/ SystemConfigurationDownloadServlet Note: The URL of the download servlet has to be specified with full-qualified domain name. Example: SystemConfigurationDownloadServlet 6. Select BASIC as authentication Note: For HTTPS scenarios, procedd as follows: - enter https instead of http in the URL - now, in the Server Certificates section, activate Accept certificates in keystore view and choose service_ssl - depending on your security policy, select BASIC or Logon Ticket as authentication 7. Enter user name and password of the J2EE administrator from the 6.40 system you want to monitor February

22 8. Choose the Save pushbutton to store your settings Setup of Single Sign-On on SMD Server This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. The J2EE Engine of the Solution Manager Diagnostics server creates and issues a user ticket (SSO2 ticket) which enables authentication on all monitored SAP systems. The setup has to be performed in two steps. First the preparation of the Solution Manager Diagnostics J2EE Server and the export of a self-signed certificate and second the import into the monitored systems. As the Solution Manager Diagnostics contains both Java and ABAP components, you have to import the certificate created by the Visual Administrator in the same way as explained in Setup of Single Sign-On on Monitored Systems [page 32] even if both Java and ABAP parts are installed on the same machine. Note: - Always use full-qualified hostnames, e.g. p wdf.sap.corp - For SSO scenarios, the Solution Manager Diagnostics system has to be in the same network domain as the monitored systems Configuration 1. Preparation of the J2EE server of Solution Manager Diagnostics. The Client ID of the J2EE system has to be changed. This ID will be stored in every ticket and has to be unique. If the SSO module logs on the client with the ticket it uses this Client ID 22 February 2006

23 a) Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running b) Navigate to Server Services Configuration Adapter c) In the Display configuration tab, open the branch for cluster_data server cfg services d) Choose the pushbutton (Display/Change) to switch to the edit mode; you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton e) Choose the pushbutton (Change) or just double-click on Propertysheet com.sapsecurity.core.ume.service f) You can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter g) A single mouse click will open a new window where you can change the configuration data: h) Change parameter login.ticket_client to a number <> 000, e.g. 169 i) To save the data, choose the pushbutton Apply custom. j) Restart the J2EE Engine of SMD. 2. 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 February

24 b) Navigate to Server Services Key Storage c) In the Runtime tab, first select the view TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window) d) To export the certificate on file system, choose pushbutton Export and enter any file name. This certificate has to be imported into the monitored systems, refer to Setup of Single Sign-On on Monitored Systems [page 32]. 3. Importing the certificate on SAP ABAP system: refer to Import Single Sign-On Certificate into the ABAP Stack [page 25]. Login Modules 1. 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), for Flag choose SUFFICIENT : ClientCertLoginModule CreateTicketLoginModule CredentialsMappingLoginModule 24 February 2006

25 EvaluateAssertionTicketLoginModule EvaluateTicketLoginModule SecuritySessionLoginModule Import Single Sign-On Certificate into the ABAP Stack This manual operation is part of Solution Manager Diagnostics (Standard Guide). To have all SSO related information in one document, it is available here, too. a) Log in to the ABAP envoronment of the SMD Server (use Webgui or SAP GUI) b) Start transaction STRUSTSSO2, navigate to System PSE <server>_<sid>_<instance no.>: February

26 Note: If both ABAP kernel and J2EE server are running on the same host within the same landscape, the default certificates will be the same. In this case, delete the old one with STRUSTSSO2, right-click on System PSE, choose the pushbutton Delete and create a new one as explained in c) e) below. c) Choose the pushbutton (Import Certificate) in the Certificate section of the screen to import a certificate from file system, choose Binary as file format d) Choose the pushbutton Add to Certificate List to apply certificate e) To save the configuration, choose the pushbutton (Save) f) Choose the pushbutton Add to ACL to apply ACL g) In the popup, enter: System ID: SID of the system where the certificate has been created, e.g. WA1 Client: client of the login ticket, e.g. 169 Note: This client is not related to the login client known from ABAP systems! h) To save the configuration, choose the pushbutton (Save) i) Start transaction RZ10 and add the following parameters to the instance profile <SID>_DVEBMGS<instance no.>_<hostname> of the SMD Server: login/accept_sso2_ticket: set to 1 (mandatory for accepting certificate) 26 February 2006

27 login/create_sso2_ticket: set to 0 (recommended setting) j) Save and activate the profile, restart the system Creation of Role for ABAP User As of NetWeaver 04 SP Stack 13, the according role SAP_SOLMANDIAG_SAPSUPPORT is part of SAP standard delivery. If required, the role can be created (name: Z_SAPSUPPORT) or verified manually as explained here. In addition to the J2EE role, the SMD user needs an ABAP role on the monitoring system. Role name Z_SAPSUPPORT is recommended. 1. Call transaction PFCG 2. Enter Z_SAPSUPPORT in field Role 3. Choose pushbutton (Create Role) 4. In the next screen, click the Authorizations tab and choose pushbutton (Profile Generator expert mode) 5. By choosing pushbutton (Manual entry of authorization objects) and enter the following authorizations sequentially: S_ADMI_FCD S_RZL_ADM S_RFC S_TCODE authorization object that has to contain: ACTVT: NADM, ST0R authorization object that has to contain: ACTVT: 01, 03 authorization object that has to contain: ACTVT: 16 RFC_NAME: RFC_TYPE: RFC1, SAL_RFC, SALF, SALS, SCSMROUTE, SDIFRUNTIME, SYFU, SYST FUGR authorization object that has to contain: TCD: DB59, DB6COCKPIT, ST04M, ST04_MSS, OS07, RZ20, ST03G 6. Choose pushbutton (Generate), as a result you will get the technical name of the generated profile 7. Return with the F3 key and choose the Users tab 8. Assign the SMD user (e.g. SAPSUPPORT) to the generated profile by choosing the User comparison pushbutton February

28 Note: For enabling Single Sign-On, the user names for SMD (refer to Setup of Single Sign-On on SMD Server) and the monitored systems have to be identical. SAPSUPPORT is the recommended user name Creation of Support Roles for J2EE Engine As of NetWeaver 04 SP Stack 13, the according role SAP_JAVA_SUPPORT is part of SAP standard delivery. SAP_JAVA_NWADMIN_CENTRAL_READONLY is part of SAP standard delivery as of SP Stack 12. If required, these role can be created or verified manually as explained here. All users for Solution Manager Diagnostics have to be assigned to the role SAP_JAVA_SUPPORT. 1. Open the User Management menu within the local J2EE Engine: no.>00, navigate to User Management 2. Login as J2EE administrator 3. Navigate to Roles 4. Create role SAP_JAVA_SUPPORT within user management, add the role action com~sap~tc~webdynpro.administrate, and apply the role to the user for SMD. SAPSUPPORT is recommended as user name: 28 February 2006

29 5. Create role SAP_JAVA_NWADMIN_CENTRAL_READONLY within user management, add the role actions - UME.Read_All - tc~lm~webadmin~permissions.applications_display - tc~lm~webadmin~permissions.localsld.display - tc~lm~webadmin~permissions.log_display - tc~lm~webadmin~permissions.monitoring_display - tc~lm~webadmin~permissions.performance_display - tc~lm~webadmin~permissions.systeminfo_display - tc~lm~webadmin~permissions.user_access_all - tc~lm~webadmin~permissions.webadmin_central and apply the roles to the user for SMD. SAPSUPPORT is recommended as user name: February

30 6. Verify that the Solution Manager Diagnostics users are member of both roles SAP_JAVA_SUPPORT and SAP_JAVA_NWADMIN_CENTRAL_READONLY: Connection to SLD This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. If a SAP SLD (System Landscape Directory) system is installed in your solution landscape, the Solution Manager Diagnostic should be connected to this system. Proceed as follows: 30 February 2006

31 1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. Navigate to Server Services SLD Data Supplier 3. In the Runtime tab, select the HTTP Settings tab 4. Enter the connection information to the SLD server of your solution landscape Connection to NWA This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. If a SAP NWA (NetWeaver Administrator) system is installed in your solution landscape, the Solution Manager Diagnostic should be connected to this system to integrate the NWA monitoring capabilities into SMD. Proceed as follows: 1. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running 2. Navigate to Server Services Configuration Adapter 3. In the Display configuration tab, open the branch for apps sap.com tc~webadministrator~navigation~ejb appcfg 4. To switch to edit mode, choose the pushbutton (Display/Change); you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton. 5. To modify data, choose the pushbutton (Change) or just double-click on Propertysheet application.global.properties 6. Now you can change customizing entries by positioning the mouse pointer to the line where you find the information that has to be adapted 7. A single mouse click will open a new window where you can change the configuration data Description: 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, the default value 8. The following parametes should be modified to match the NetWeaver Administration Console: Name SAP default Example Description nwahost protocol://host:port By default the nwahost will be setup to Server & port where the NWA is running The protocol can be https or http. If no protocol is specified, will be added by SMD Note: use fully-qualified host names nwaadmin Administrator The administrator of the SAP February

32 NetWeaver administration server nwauser Password The administrator of the SAP NetWeaver Administration server 9. To save modified parameters, choose the Apply custom pushbutton 4.2 Deatailed Descritption of Automated Setup Tasks on Monitored Systems The following sections contain detailed information for installation & setup of the systems monitored by the SMD Server. Here you can find the description of automated actions for the Monitored Systems performed by the SMD Administration application. The SMD Administration application can be launched by URL: Note: You have to log on as J2EE administrator to the SMD Administration application. In case of problems, these configuration steps can be performed manually as well what is explained here in detail Java Parameter Settings on Monitored J2EE Engines This operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. For performance analysis of monitored J2EE Enginea, the output of garbage collections is required. Proceed as follows: 1. Start the J2EE Configtool where the monitored system is running 2. For each server node, navigate to cluster-data Instance_<ID> Server_<ID> 3. In the General tab, apply the Java parameters -verbose:gc (Note: set this parameter for both 6.20 and 6.40 J2EE Engines, refer to SAP Note for J2EE Engine 6.20) -XX:+PrintGCTimeStamps -XX:+JavaMonitorsInStackTrace (Note: for 6.40 J2EE Engines only) (Note: for 6.20 J2EE Engines only, but not for Java VMs from IBM or HP, refer to SAP Note for details) 4. Choose the Save pushbutton to save the configuration, restart the server node(s) Setup of Single Sign-On on Monitored Systems This operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. 32 February 2006

33 The certificates created within the J2EE Engine of the Solution Manager Diagnostics server (refer to Setup of Single Sign-On on SMD Server) have to be imported into the monitored SAP systems. The procedure is different for ABAP systems and systems with active J2EE Engines. Note: - Use full-qualified host names, e.g. p wdf.sap.corp - If you are running a Web AS with both active ABAP and J2EE components, you have to import the certificate for both components - This procedure is valid for both 6.20 & 6.40 J2EE Engines Configuration 1. Importing the certificate on J2EE system: a) Start the Visual Administrator and log on to the J2EE Engine of the monitored system (e.g. Enterprise Portal) b) Navigate to Server Services Key Storage c) In the Runtime tab, first select TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window) d) To import the certificate from file system, choose the pushbutton Load. For exporting certifcates from SMD, refer to refer to Setup of Single Sign-On on SMD Server e) Restart the J2EE Engine of the monitored system 2. 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) or Flag choose SUFFICIENT : ClientCertLoginModule CreateTicketLoginModule CredentialsMappingLoginModule EvaluateAssertionTicketLoginModule EvaluateTicketLoginModule SecuritySessionLoginModule 3. Allow J2EE application (e.g. Enterprise Portal) to accept SSO tickets: a) Start the Visual Administrator and log on to the J2EE Engine of your monitored system 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: February

34 CreateTicketLoginModule EvaluateTicketLoginModule e) Choose ticket in window Components f) In the Authentication tab, choose Login Module com.sap.security.core.server.jaas.evaluateticketloginmodule g) To add properties, choose the pushbutton Modify ume.configuration.active: trustediss1: trusteddn1: trustedsys1: true CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1 Note: O=<company>,C=<country> are optional CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1 Note: O=<company>,C=<country> are optional <SID of Solution Manager Diagnostics>,<client ID> e.g. WA1,169 Confirm settings with the OK pushbutton. Now change the Authentication Template for the following applications in the Components window to ticket (drop-down box): sap.com/sql_trace*opensqlmonitors (SQL Trace) sap.com/sql_trace*opensqltrace (SQL Trace) sap.com/tc~monitoring~systeminfo*sap_monitoring (Systeminfo) 34 February 2006

35 sap.com/tc~wd~dispwda*webdynpro_dispatcher (Web Dynpro Console) sap.com/tc~wd~dispwda*webdynpro_welcome (Web Dynpro Console) Assignment of J2EE Server Roles to the Support User To enable access to the J2EE applications for SQL Trace, System Info and SAP XI, J2EE Server Roles have to be assigned. This operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Component Overview For monitored SAP J2EE Engines 6.40 up to SP Stack 14: Component sap.com/tc~monitoring~systeminfo*sap_monitoring sap.com/sqltrace*opensqlmonitors component Role SystemInfo_Support_Role OpenSQLMonitorLogonRole For monitored SAP J2EE Engines 6.40 as of SP Stack 15: SAP-J2EE-ENGINE Component Role SAP_JAVA_SUPPORT For monitored SAP J2EE engines running on XI: Component sap.com/com.sap.xi.repository*rep sap.com/com.sap.xi.directory*dir sap.com/com.sap.rprof.remoteprofile*exchangeprofile sap.com/com.sap.xi.rwb*rwb sap.com/com.sap.xi.mdt*mdt sap.com/com.sap.aii.af.cpa.app*cpacache sap.com/com.sap.aii.af.app*adapterframework sap.com/tc~techsrv~xml_das*dataarchivingservice Role display display display display display xi_af_cpa_monitor xi_af_adapter_monitor XMLDASSecurityRole Example for Role Assignment To grant the role SystemInfo_Support_Role, start the J2EE Engine Visual Administrator tool on the monitored J2EE system: 1. navigate to Server Services Security Provider 2. select component sap.com/tc~monitoring~systeminfo*sap_monitoring 3. navigate to tab Security Roles 4. select security role SystemInfo_Support_Role 5. use the Add pushbutton to add the SAPSUPPORT user to this role February

36 4.2.4 Setup of HTTP Analysis For SAP J2EE Engines as of 6.40, this operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. The SMD application HTTP Analysis uses a plug-in (can be downloaded within the application, updates are available in SAP Note ) for the web browser to log the requests and responses between the browser and the SAP Enterprise Portal. The user interface of HTTP Analysis displays detailed performance-related information graphically. Activating HTTP log information on J2EE Engine Start the J2EE Configtool of the Enterprise Portal 2. 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. Start the Visual Administrator and log on to the J2EE Engine of the Enterprise Portal 5. Navigate to Server Managers Log Managers 6. In the Properties tab, change the value of LogLevel to 6 and apply it by choosing pushbutton Add 7. Navigate to Server Services Log 8. In the Properties tab, change the value of LogLevel to 6 and apply it by choosing pushbutton Add 36 February 2006

37 Activating HTTP log information on J2EE Engine Start the Visual Administrator and log on to the J2EE Engine of the Enterprise Portal 2. Navigate to Server Services Log Configurator 3. In the Categories tab, open Log Controller Root Category System HTTPAccess Access 4. Set Severity to Info and apply this setting to all cluster nodes by choosing the Save pushbutton 5. Start the J2EE Configtool of the Enterprise Portal 6. Navigate to cluster-data Instance_<ID> Server_<ID> Services http 7. Apply the following parameters by entering into the Value field: LogHeaderValue: X-CorrelationID LogResponseTime: true by choosing the Set pushbutton after every change Note: In case you want to compare the HTTP message headers between client and server (e.g. to find out if proxy servers, IIS, or firewalls modify HTTP headers), then you have to switch on parameter LogRequestResponseHeaders in addition: LogRequestResponseHeaders = true 8. To persist all customized settings, choose the pushbutton (Save) Setup of Thread Dump and GC Analysis For SAP J2EE Engines as of 6.40, this operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. All Java VMs used for SAP Enterprise Portal provide a built-in mechanism to dump a snapshot of the states of all Java threads. This dump is called full thread dump. Analysis of Garbage Collections (GC) provides information about the memory usage of a J2EE cluster node. Prerequisites Startup Framework 6.30/6.40 has to be installed, even on SAP J2EE Engines Setup of Software Change Reporting for SAP Enterprise Portals This step has to be performed manually. Prerequisites The PCD configuration file <J2EE_HOME>\SYS\global\pcd\pcdStartup.properties has to be adapted on each monitored Enterprise Portal server. Per default, the Pcd.Share variable points to Pcd.Home (<J2EE_HOME>\SYS\global\pcd). Make sure the follwing lines are present in pcdstartup.properties: February

38 # Directory for temporary transport files Pcd.TransportApplication.TempDir = ${Pcd.Share} # Directory in which the content migration logs should be stored Pcd.Migration.ContentMigrationLogDirectory=${Pcd.Share}/reports/Migration # Log into an Xml file (true= Xml, false=html, default value false) Pcd.Migration.XmlLogger = true Setup of Session Tracing for SAP J2EE Engines This step has to be performed manually. To enable J2EE session tracing, certain flags have to be activated. 1. Start the Visual Administrator and log on to the J2EE Engine of the monitored system 2. Navigate to Server Services Performance Tracing 3. Open the Trace Config tab and choose the pushbutton (Properties) 4. In the Session Trace Settings screen that appears, choose Enable session trace to enable the function 5. Configure the maximum number of activities to be traced by entering a value in the Tracked Activities field (e.g. 100) 6. Configure the name of the URL Parameter that is used in the request URL to activate the session tracing mechanism, by entering a value in the URL Parameter field. The default name of the parameter is SAP-SAT. 7. To save your settings, choose the Save pushbutton Setup of ICM Logging To enable the analysis of logs written by the Internet Communication Manager (ICM) by using the HTTP Analysis application, an additional parameter has to be maintained. 1. Start transaction RZ10 and add the following parameter to the instance profile <SID>_DVEBMGS<instance no.>_<hostname> of the server where the ICM is running: icm/http/logging_0: set to PREFIX=/, LOGFILE=icmhttp.log, LOGFORMAT=%t - "%r0" %s %b [%L] h[%{x- CorrelationID}i], MAXSIZEKB=10240, SWITCHTF=day, FILEWRAP=on 2. Save and activate the profile, restart the system Note: As this parameter value exceeds 1 line, it has to be maintained carefully. The result should look like shown in the example below: 38 February 2006

39 4.2.9 Setup of SMD Keystore / SSL Application Within SMD, keystore information can be viewed for each monitored J2EE instance. SSL information can be viewed for each monitored J2EE dispatcher node, too. In order to get the SSL data for a dispatcher, the SSL Porvider service has to be activated: 1. Start the Visual Administrator and log on to the J2EE Engine of the monitored system 2. Navigate to Dispatcher Services SSL Provider 3. Move the mouse cursor to the service and choose (Start service) Setup of Portal Activity Reporting The Solution Manager Diagnostic should be configured for the Portal Activity Reporting (PAR) for Enterprise Portal versions of EP 6 SP 2 or less than NW04 SP 14. Portal Activity Reporting is intended to access Enterprise Portal performance statistics. General information for the setup of Portal Activity Reporting can be obtained: EP 6.0 SP 2 o Downloads Developer or Administrator Tool Portal Activity Reporting NW Portal o help.sap.com Documentation SAP NetWeaver People Integration Portal Administration Guide System Administration Monitoring Technology and Logging Portal Activity Report PAR Setup for NW Portals as of SP Stack 13 For enabling PAR reports within SMD, a web service is used what will be configured automatically. As a prerequisite, the security zone of this web service has to be configured. For details, refer to SAP Note PAR Setup for NW Portals < SP Stack 13, EP 6 SP 2 Portals For enabling PAR reports within SMD, a JDBC connection from the SMD Server to the monitored Portal has to be configured. For details, refer to 5 Manual Setup of Portal Activity Reporting. February

40 5 Manual Setup of Portal Activity Reporting Note: Perform this step only for monitored EP 6 SP 2 and NW Portals < SP Stack 13! 5.1 Create the DB Connectivity to the Monitored Systems Configuration Steps Portal Activity Reporting require a database connection from the SMD Server to the database of the monitored Enterprise Portal. If the database type or version is different from the SMD Server db, you have to install the corresponding JDBC driver within the SMD system. Otherwise you can use the driver SYSTEM_DRIVER. If no driver for the database running on 6.20 has been installed yet, you will find the corresponding Java files (extension:.jar) at: <J2EE_HOME>/cluster/server/additionallib/com/sap/data_direct_driver_references If no driver for the database running on 6.40 has been installed yet, you will find the corresponding Java files (extension:.jar) at: <J2EE_HOME>/cluster/server<n>/bin/ext/com.sap.datadirect (MS SQL Server) or <MaxDB home directory>/programs/runtime/jar (MaxDB). The driver for Oracle is part of the Oracle client (db-dependent part of the ABAP kernel). Configuration of JDBC Connector 1. Login to the Visual Administrator of Solution Manager Diagnostics; navigate to Server Services JDBC Connector 40 February 2006

41 2. Setup the Database Driver & Data source, depending on the database of the Portal server Note: - You have to create a DataSource for each Portal instance within your solution / landscape. - Depending on the DBMS, different values have to be entered during the setup a) Select Drivers and choose the pushbutton (Create New Driver or Data Source) in the toolbar, name it according to the table below and choose the Ok pushbutton: 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, sqlserver.jar, util.jar classes12.jar sapdbc.jar db2jcc.jar, db2jcc_license_cu.jar Note: If the SMD is also running on the same type of DBMS, the default SAP J2EE Engine JDBC driver (SYSTEM_DRIVER) can be used instead. c) Select DataSources and choose the pushbutton (Create New Driver or Data Source) in the toolbar d) Go to tab Main February

42 e) Enter Name, e.g. WCR, and Description (optionally), don t enter Application Name f) In the dropdown box Driver Name choose the name created in step a) g) As Driver Class enter: MS SQL SERVER Oracle MAX DB DB2 com.ddtek.jdbc.sqlserver.sqlserverdriver oracle.jdbc.driver.oracledriver com.sap.dbtech.jdbc.driversapdb com.ibm.db2.jcc.db2driver h) As Database URL enter: MS SQL SERVER Oracle MAX DB DB2 jdbc:datadirect:sqlserver://<host>:<port>;databasename=<sid> e.g. jdbc:datadirect:sqlserver://p78293:1433;databasename=p62 jdbc:oracle:thin:@<host>:<port>:<sid> e.g. jdbc:oracle:thin:@us7201:1527:ep0 jdbc:sapdb://<host>/<sid> e.g. jdbc:sapdb://p114280/tyr jdbc:db2://<host>:<port>/<sid> e.g. jdbc:db2://p114280:5912/tyr i) Enter User and Password of the database schema owner SAP<SID>DB, e.g. SAPP62DB j) Choose pushbutton Add Alias to create an unique Alias for the landscape: SAP/BC_WA_WCR<nn> (<nn>= ) e.g. SAP/BC_WA_WCR01 Note: for mapping the alias, only the last 5 characters are used, e.g. WCR01 42 February 2006

43 k) Go to tab Additional l) Change the number of Initial Connections to 1, Max Connections to 5, and choose as SQL Engine Portal: Native SQL (for Portals running on J2EE 6.0) Portal: Open SQL m) Choose the pushbutton (Save) to save the configuration, afterwards you should see a new data source named WcrDataSource 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 February

44 If not, you may restart the sap.com/jdbcconnector_<name>.xml service by choosing the pushbutton (Stop Service) and afterwards the pushbutton (Start Service) 5.2 Mapping of Solution Landscape to DB Alias To integrate a DataSource designed in 5.1 Create the DB Connectivity to the Monitored Systems into a SMD solution, perform the steps listed below. 1. Within Visual Administrator navigate to Server Services Configuration Adapter 2. Open Propertysheet.application.global.properties in edit mode within tree Configurations apps sap.com tc~webadministrator~wcrep~ws appcfg 44 February 2006

45 3. Make an entry for each database alias Description: Name: Datatype: Default: information for the database alias, cannot be changed WCR01 WCR05 (database alias, cannot be changed). The database aliases are created in the Setup Wizard. For detailed information refer to 5.1 Create the DB Connectivity to the Monitored Systems. java.lang.string, cannot be changed default value, cannot be changed February

46 Custom: name of the monitored product within the solution: <Solution name><sid><installation number> e.g. WAS640_SINGLE_HOSTJ2E Note: There must be no spaces in the name! 46 February 2006

47 6 Setup of SMD Scheduler The SMD Scheduler s purpose is to retrieve data from system landscapes connected to the SMD Server. The tasks are scheduled on a regular basis. To open the SMD Scheduler, start the SMD application by launching URL: Afterwards, navigate to tab Configuration Scheduler. As alternative, the SMD Scheduler can be started within the SMD Administration application by launching URL: Afterwards, navigate to tab Scheduler. Note: You have to log on as J2EE administrator to the SMD Administration application. 6.1 First Initialization of the Scheduler This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Choose the pushbutton Default Setup in the Scheduler window. This will trigger all required tasks. 6.2 Setup of Tasks After a new system is connected to the SMD Server, tasks have to be configured. This operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Press the Host List Tab to get the list of monitored hosts from Solution Manager Diagnostics. February

48 Select the host to monitor Press the Add All Tasks button. Afterwards, you should see the following screen: The next step is to schedule these tasks, refer to 6.3 Data Collection from Monitored System. 6.3 Data Collection from Monitored System After all tasks for a new system have been configured (refer to 6.2 Setup of Tasks), these tasks have to be schduled. This operation is performed automatically by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. Press the Host List Tab to get the list of monitored hosts from Solution Manager Diagnostics. 48 February 2006

49 Select the host to monitor Navigate to the Task Viewer section of the screen. Afterwards, you should see the following screen: Select task Collect Configuration Data and choose pushbutton After successful download of a new solution / landscape, you have to refresh the screen within your web browser to get the SMD navigation bar updated. February

50 7 Setup of SMD Agent The SMD Agent is a Java application running on the monitored systems and gathering information for the SMD Server. This chapter contains detailed information for setup of applications running within the SMD Agent. Most of these steps are performed by the Monitored System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well. 7.1 Manual Setup of SMD Agent The SMD Agent is configured by SAPinst (refer to Solution Manager Diagnostics (Standard Guide)), but can be re-configured manually as well Command Line Execution smdsetup <path of JVM 1.4> <host name or ip adr. of SMD Server> <P4 port> <admin. user> <pwd.> Example: c: cd \usr\sap\smd\j97\smdagent smdsetup.bat C:\j2sdk1.4.2 p wdf.sap.corp SMD_ADMIN pwd SMD Agent Setup Steps When running properly, the SMD Agent setup output looks like the example below: SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG SMD Agent Setup is in process STEP 1: checking JDK location JDK location is consistent: C:\j2sdk1.4.2_04\bin - STEP 2: checking JDK Version JDK Version is correct: 1.4.2_04-er - STEP 3: checking Connection to SMD Server SMD Server check completed successfully - STEP 4: generating Runtime Properties runtime.properties has been created. - STEP 5: generating Launcher smdagent.bat has been created. smdagent.sh has been created. - STEP 6: generating SecStore secstore.properties: has been created. secstore.properties: user has been set. secstore.properties generation completed successfully. - STEP 7: checking P4 Connection and SMD Agent Registration SMD Agent Registration succeeded SMD Agent Setup completed successfully February 2006

51 The different operations performed are the following: - Step 1: checks the location of the Java Virtual machine Step 2: makes sure the Java Virtual machine is compliant with the SAP J2EE Security libraries. - Step 3: makes sure the SMD Server machine (host name) is visible and waiting on the P4 port specified. - Step 4: generates a runtime.properties file to persist the parameters specified. - Step 5: generates the scripts used to start the SMD Agent. As of SMD Agent SP 15 these scripts are obsolete, as the JStartup Framework is used for the startup. - Step 6: generates SecStore file required for establishing a secure connection to the SMD Server. - Step 7: checks the generated runtime environment and clearly shows whether the SMD agent registration to the SMD Server can be done. This registration relies on the SAP J2EE P4 protocol SMD Agent Start Profile It is possible to modify the startup parameters of the SMD Agent, to change memory setting, etc. The startup profile is located under /usr/sap/smd/j<nn>/profile/smd.properties. Example Profile # # SMD AGENT instance properties # Created on Tue Oct 25 13:21:54 CEST 2005 # smdagent.name=smdagent smdagent.type=server smdagent.rootpath=../smdagent smdagent.classpath =lib/launcher/smdagentlauncher.jar:lib/launcher/logging.jar smdagent.mainclass = com.sap.smd.agent.launcher.smdagentlauncher smdagent.parameters = run jcontrol smdagent.javaparameters = -Xmx128m -Xms128m smdagent.shutdowntimeout=10000 smdagent.id=1 smdagent.debugmode=no smdagent.debugport=58021 smdagent.debuggable=yes Note: After changing its profile, the SMD Agent has to be restarted. February

52 7.1.4 Change Credentials of SMD Agent To change the logon credentials used by the SMD Agent to logon to the Monitoring System (SMD Server), access the SMD Administration application by launching URL: Note: You have to log on as J2EE administrator to the SMD Administration application. Navigate to tab Agent Administration Agent Credentials. Enter the current user and the password used by the SMD Agent, and enters the new user and password. The new J2EE user must have an Administrator role or to be a member of the group Administrators. Note: Before applying the change, it is important that all SMD Agents are online and connected to the Monitoring Sytem. All agents that are not connected during the password change have to be changed manually as explained in Command Line Execution. It is recommended to create a dedicated J2EE administrator on the SMD Server, used by SMD Agents (e.g. SMD_ADMIN). Otherwise you risk to lock the main J2EE administrator by unsuccessful login attempts (if wrong password provided) of SMD Agents SSL Setup for SMD Agent Prerequisites Configure the SAP J2EE Engine of the SMD Server to receive P4 SSL calls. Refer to the SAP Help Portal ( for detailed information Setup Per default, the communication between the SMD Agents and the Monitoring System (SMD Server) is established via the P4 protocol (unsecured). To enable secure communication, the SSL transport must be configured between the SMD Agent and the SMD Server. Two types of installation are possbile: 52 February 2006

53 the SMD Agent has a separate JDK (used by the SMD Agent exclusively) 1. Configure the JDK to use SSL libraries: Add the iaik libs in the JRE\lib\ext folder of the JDK of the SMD Agent: iaik_jce.jar iaik_jsse.jar iaik_ssl.jar Note: The jre\lib\security folder might contain local_policy.jar and US_export_policy.jar 2. Configure the SMD agent to use SSL: Add the property smd.agent.connection.transport=ssl in \usr\sap\smd\jxx\smdagent\configuration\runtime.properties and modify the property smdserver.port to match the P4 SSL port. (5xxx6 by default) 3. Restart the SMD Agent the SMD Agent uses a common JDK (used by other components as well) 1. Configure the SMD Agent profile to use SSL libraries: a) the SAP installations uses the same JDK that is already configured for SSL: o o if the server hosts a central (main) instance: - location of the iaik libs: /usr/sap/<sid>/sys/global/security/lib/tools - add the path to the iaik files to property smdagent.classpath in the SMD Agent profile at /usr/sap/smd/j<instance no.>/profile/smd.properties if the server hosts a dialog instance: - location of the iaik libs: <J2EE_HOME>/sys/global/security/lib/tools - add the path to the iaik files to property smdagent.classpath in the SMD Agent profile at /usr/sap/smd/j<instance no.>/profile/smd.properties b) the SAP installations is not configured for SSL: you can use either option 1.a) or configure the JDK exclusively for the SMD Agent. Note: Make sure that you don t run into combatibility problems when the SSL-configured JDK is used by other applications as well! 2. Configure the SMD agent to use SSL: Add the property smd.agent.connection.transport=ssl in \usr\sap\smd\jxx\smdagent\configuration\runtime.properties and modify the property smdserver.port to match the P4 SSL port. (5xxx6 by default) 3. Restart the SMD Agent 7.2 Configuration of SMD Agent Applications This section explains the individual setup of applications that are running within the SMD Agent. To access the SMD Agent setup, the SMD Administration application can be launched by URL: February

54 Note: You have to log on as J2EE administrator to the SMD Administration application. Navigate to tab Agent Administration Applications Configuration J2EE Command Console Configuration This application provides access to a read-only set of J2EE commands on the monitored hosts used by the J2EE command console application. The telnet protocol is used for this application. Configuration Configure the following parameters: Application Scope Name Description global.configuration host <sid>/sapj2ee/admin/user The SAP J2EE admin user with telnet execution rights global.configuration host <sid>/sapj2ee/admin/pwd telnet host <sid>/sapj2ee/telnet/port J2EE telnet port 5<instance no.>08, e.g telnet Global or by host <command name> True if the command is allowed, false otherwise Cluster Consideration: In a cluster, only the SMD Agent running on a host with dispatcher node needs to be configured. Commands By default, all J2EE telnet commands are allowed except the following ones (they are set to false): APPLICATION_ALIAS ATTR CACHE [-l] [-list] [-r] [-hitrate] CLEAR_HTTP_CACHE HOST HTTP_ALIAS INTERNAL_LOCKS [-l] [-list] MENV SET TEST_DS Since SMD SP 15, it is possible to disable particular parameters of a telnet command with the syntax: /-<parameter>/ Example: Enabling command CLEAR_HTTP_CACHE and disabling the parameters /-l/ /-list/ /-r/ /-hitrate/ for command CACHE: 54 February 2006

55 7.2.2 File System Access Configuration With this application the file system of a monitored system can be browsed. Files can be displayed or downloaded. Configuration Configure the following parameters: Application Scope Name Description filesystem host root_directories A comma separator list of root folders accessible by SMD applications (e.g. File System Browser, Thread Dump Analyzer) on the monitored host. If the value of this property is empty, access is restricted to folder usr/sap. Note: If root directories are modified, at least the SAP root directory (X:/usr/sap, where X: is the installation drive on Windows systems) must be part of the list. For multi drive installations, all SAP directories must be part of the list (e.g. C:/usr/sap, D:/usr/sap, etc.) SQL Command Console Configuration To enable the execution of queries by the SQL Command Console, the database application has to be configured. February

56 Configuration Configure the following parameters: Application Scope Name Description database host driverclass The class of the JDBC driver to use to connect from the SMD agent to the remote DB database host driverjars The jar files containing the JDBC driver to use for the connection from the SMD agent to the remote DB Note: - the location of the files refers to the server where SMD Agent runs (monitored system) - separate files by semicolon ( ; ), e.g. E:\jars\base.jar;E:\jars\sqlserver.jar database host user The user to use for the DB connection database Host password The password of the user database Host url The URL of the DB. Note: You can find classes, etc. in chapter Configuration Steps OS Command Console Configuration OS Commands Console allows to launch certain operating system commandis by the SMD Agent user. On the monitored system, the user may not have rights to execute all commands. Before using OS Command Console, you should configure correctly SMD Agent user on each monitored system. Configuration Configure the file <component_analyzer>/cca_oscommand.xml: Tag Description Example CMD name Name of the command available in the OS Command Console application IP Config desc Explanation of the command Displays all current TCP/IP network configuration values. OsCmd ostype valid Operating System for the command WINDOWS exec Execution string for the command on OS level ipconfig path param Location of the command (if not in standard search path) true : parameters are allowed false : parameters are not allowed runtime Timeout value in seconds 5 Exclude param If parameters are allowed in general (see tag param), particular parameters can be excluded c:\windows\system32 true ^(/ -)(renew release)$ 56 February 2006

57 Note: Each command defined in file <component_analyzer>/cca_oscommand.xml should be in the SMD Agent user path and has to be accessible by this user only Log Viewer Configuration The Log Viewer application of the SMD Agent will start the J2EE Standalone Logviewer on the monitored system (if available). Configuration Configure the following parameters: Application Scope Name Description logviewer host Logviewer_MonitorablePath This parameter has no meaning for SMD Agent SP 15 (reserved for future usage) logviewer host Logviewer_NI_Port NI port of the Standalone Logviewer logviewer host default.log.pattern Specifies which log file extendsion the logviewer server can read, separate by using a comma, e.g. *.log, *.trc February

58 8 Setup of CCMS Agent The CCMS Agent SAPCCMSR is a program running on OS level with RFC interface to a central monitoring system and an interface to the shared memory. SAPCCMSR triggers SAPOSCOL on the monitored system. SAPCCMSR patch 67 is required, the version can be verified by executing sapccmsr version Note: As of SMD SP Stack 14, SAPCCMSR is only required for CCMS alert monitoring and remote OS monitoring, no more for tasks related to the SMD Scheduler. For more information, refer to CCMS Agents [see page 11] and SAP Notes , The setup procedure of SAPCCMSR depends on the version of the monitored systems and is explained in detail in the next chapters of this guide. 8.1 Download CCMS Agent from SAP Service Marketplace For a SAP solution with release < 6.40, or a SAP solution without ABAP and Java components (e.g. TREX) or a non-sap solution, the CCMS agents delivered with the installation have to be exchanged. Proceed as follows: 1. Download the current version of SAPOSCOL from the SAP Service Marketplace: service.sap.com/swdc Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NetWeaver SAP NetWeaver 04 Entry by Component Central Admin SAP Kernel bit <choose OS> Database independent ccm agent. The file ccmagent<version>.sar contains the CCMS Agent archived. 2. Extract the CCMS Agent with SAPCAR. Refer to SAP Note how to operate SAPCAR. 8.2 Setup of CCMS Agent on a NetWeaver Java Instance Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent: You have a Solution Manager Diagnostics systems that contains the central monitoring system (CEN). There is a CSMREG user in CEN. If this is not yet the case, create the user by proceeding as follows: 1. In CEN, call transaction RZ21 and choose Technical Infrastructure Configure Central System Create CSMREG User. 2. Enter any password for this user, and confirm your entries by choosing the Create CSMREG pushbutton. 58 February 2006

59 During the registration of the agent, you require the connection data from the agent to CEN. We recommend that you generate this data in a CSMCONF file in CEN before the registration. To do this, proceed as follows: 1. In CEN, call transaction RZ21, and choose Technical Infrastructure Configure Central System Create CSMCONF Start File for Agents. 2. Save the file CSMCONF at a location that is centrally available, since you require the file for all agent registrations. Refer to SAP Note for additional information. Configuration 1. Log on to the host of a J2EE Engine of the system as <SID>adm. 2. Copy the start file CSMCONF to the following directory: Windows: UNIX: [drive]:\usr\sap\ccms\<sysid>_<inst. No.>\sapccmsr /usr/sap/ccms/<sysid>_<inst. No.>/sapccmsr 3. Start the Visual Administrator by calling the start script go (UNIX) or go.bat (Microsoft Windows), and log on with your user as the J2EE Engine administrator. 4. In the navigation bar, choose Cluster <SysID> Dispatcher Services Monitoring, and choose the CCMS Agent Configuration tab page. Choose the agent configuration file: CCMSCONF 5. If you want to monitor multiple systems with the same system ID, select the Long SID indicator, and enter in this input field an identifier for the system that is unique in your monitored system landscape. This long system ID must fulfill the following conditions: The first three characters must be the system ID. The name can be a maximum of eight characters long. The name must not contain an underscore (_). 6. In the Password for Administration User input field, enter the password for the user in CEN, recommendation: user SAPSUPPORT. 7. In the Password for CSMREG User input field, enter the password for the CSMREG user in CEN. Click on the register button. 8. To enable log file monitoring, the CCMS agent s configuration file sapccmsr.ini has to be modified. Location of sapccmsr.ini: Windows: UNIX: [drive]:\usr\sap\ccms\<sysid>_<inst. No.>\sapccmsr /usr/sap/ccms/<sysid>_<inst. No.>/sapccmsr 9. Restart the CCMS agent February

60 8.3 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). There is a CSMREG user in CEN. If this is not yet the case, create the user by proceeding as follows: 1. In CEN, call transaction RZ21 and choose Technical Infrastructure Configure Central System Create CSMREG User. 2. Enter any password for this user, and confirm your entries by choosing the Create CSMREG pushbutton. During the registration of the agent, you require the connection data from the agent to CEN. We recommend that you generate this data in a CSMCONF file in CEN before the registration. To do this, proceed as follows: 1. In CEN, call transaction RZ21, and choose Technical Infrastructure Configure Central System Create CSMCONF Start File for Agents. 2. Save the file CSMCONF at a location that is centrally available, since you require the file for all agent registrations. Configuration 1. Follow steps 1 9 of 8.2 Setup of CCMS Agent on a NetWeaver Java Instance Note: During this step, the CCMS agent has to be registered on the ABAP gateway of the same system (e.g. SAP XI) not on the CEN. 2. You must now manually register the relevant agent for each Java instance to the CEN. To do this, on the host of the monitored instance, switch to the directory in which the executable for the CCMS agent SAPCCMSR is located: Windows: UNIX: <J2EE_HOME>\SYS\exe\runU <J2EE_HOME>/SYS/exe/runU 3. To register the agent manually, enter the following command: sapccmsr R j2ee pf=<path of the instance profile> Note: The complete path of the instance profile is (here, for example, for Windows): <J2EE_HOME>\SYS\exe\profile\<SysID>_<Inst. dir.>_<host> In the case of a dialog instance, this path does not exist; in this case, Visual Admin created a profile for the agent in its working directory during registration: 60 February 2006

61 Windows: [drive]:\usr\sap\ccms\<sysid>_<inst. No.>\ sapccmsr\sapccmsr_<sysid>_<inst. No.>.PFL UNIX: /usr/sap/ccms/<sysid>_<inst. Nr.>/ sapccmsr/sapccmsr_<sysid>_<inst. No.>.PFL 4. In this manual registration, you next enter that there is exactly one additional central system, and specify the system ID of the system: additional CENTRAL system y/[n]? : y R/3 system ID: <CEN> additional CENTRAL system y/[n]? : n 5. You must now also enter the connection data for the secondary central system. In this case, this is CEN. If you do not have the data, you can find it in the CSMCONF file that you created in CEN. 6. Confirm additional details, such as system groups to which the monitored system belongs, or details about setting up the service with the ENTER key. 7. To enable log file monitoring, the CCMS agent s configuration file sapccmsr.ini has to be modifed. Location of sapccmsr.ini: Windows: UNIX: [drive]:\usr\sap\ccms\<sysid>_<inst. No.>\sapccmsr /usr/sap/ccms/<sysid>_<inst. No.>/sapccmsr 8. Restart the CCMS agent 8.4 Setup of CCMS Agent on a J2EE 6.20 System Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent: You have a Solution Manager Diagnostics systems that contains the central monitoring system (CEN). There is a CSMREG user in CEN. If this is not yet the case, create the user by proceeding as follows: 1. In CEN, call transaction RZ21 and choose Technical Infrastructure Configure Central System Create CSMREG User. 2. Enter any password for this user, and confirm your entries by choosing the Create CSMREG pushbutton. During the registration of the agent, you require the connection data from the agent to CEN. We recommend that you generate this data in a CSMCONF file in CEN before the registration. To do this, proceed as follows: 1. In CEN, call transaction RZ21, and choose Technical Infrastructure Configure Central System Create CSMCONF Start File for Agents. February

62 2. Save the file CSMCONF at a location that is centrally available, since you require the file for all agent registrations. Configuration 1. Copy the agent s executable to the following directory; if the directory does not exist, create it: Windows: UNIX: \\host\saploc\prfclog /usr/sap/ccms/bin Note: The saploc directory can also have another name. It is important that there is a share available with the name saploc; by default, it is the directory <drive:>\usr\sap. If this share does not exist, create it manually. 2. Copy the start file CSMCONF to the following directory: Windows: UNIX: \\saploc\prfclog\sapccmsr /usr/sap/tmp/sapccmsr 3. Open SAP Note (CCMS agents: Java interface for registration). Copy the file csmagent.jar from the Note s attachment to a temporary directory on the host to be monitored. 4. Start the Java tool by entering the following command at the operating system prompt in the above temporary directory: java -jar csmagent.jar 5. Select the radio button Standalone/TREX/SAP J2EE Engine The input fields Agent Configuration File and Agent Executable should be filled with the correct values. 6. In the Password for Administration User input field, enter the password for the user in CEN, recommendation: user SAPSUPPORT. 7. In the Password for CSMREG User input field, enter the password for the CSMREG user in CEN. 62 February 2006

63 8. Choose the Register button. The registration log is displayed; errors are highlighted in red. Note: For Microsoft Windows, the SMD Agent is entered as a service during the registration, and is automatically started during a restart of the host. Under UNIX, the agent is automatically started by the script startsap when you start the J2EE Engine. For UNIX, you must ensure yourself that the agent is automatically started when you restart the host. To do this, enter the following command in the inittab: su - <SID>adm -c '/usr/sap/ccms/bin/sapccmsr -DCCMS' 9. To enable log file monitoring, the CCMS agent s configuration file sapccmsr.ini has to be modifed. Location of sapccmsr.ini: Windows: UNIX: [drive]:\usr\sap\ccms\<sysid>_<inst. No.>\sapccmsr /usr/sap/ccms/<sysid>_<inst. No.>/sapccmsr 10. Restart the CCMS agent Note: For SAP CRM and SAP XI systems, sapccm4x has to be installed in addition. February