SAP NetWeaver™ ‘04SAP NetWeaver™ ‘04s sss...functions for efficient and safe root cause...
Transcript of SAP NetWeaver™ ‘04SAP NetWeaver™ ‘04s sss...functions for efficient and safe root cause...
Advanced Supportability Setup Guide Advanced Supportability Setup Guide Advanced Supportability Setup Guide Advanced Supportability Setup Guide
for Solution Manager Diagnosticsfor Solution Manager Diagnosticsfor Solution Manager Diagnosticsfor Solution Manager Diagnostics
Web AS 7Web AS 7Web AS 7Web AS 7.00 SPS Stack 08 and higher.00 SPS Stack 08 and higher.00 SPS Stack 08 and higher.00 SPS Stack 08 and higher
SAP NetWeaver™ ‘04SAP NetWeaver™ ‘04SAP NetWeaver™ ‘04SAP NetWeaver™ ‘04ssss
Document Version 1.01 – October 2006
© Copyright 2006 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted
in any form or for any purpose without the express
permission of SAP AG. The information contained herein
may be changed without prior notice.
Some software products marketed by SAP AG and its
distributors contain proprietary software components of other
software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered
trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, and Informix are trademarks
or registered trademarks of IBM Corporation in the United
States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks
of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,
VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or
registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems,
Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP
NetWeaver, and other SAP products and services mentioned
herein as well as their respective logos are trademarks or
registered trademarks of SAP AG in Germany and in several
other countries all over the world. All other product and
service names mentioned are the trademarks of their
respective companies. Data contained in this document
serves informational purposes only. National product
specifications may vary.
These materials are subject to change without notice. These
materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes
only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with
respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the
express warranty statements accompanying such products
and services, if any. Nothing herein should be construed as
constituting an additional warranty.
Disclaimer
Some components of this product are based on Java™. Any
code change in these components may cause unpredictable
and severe malfunctions and is therefore expressively
prohibited, as is any decompilation of these components.
Any Java™ Source Code delivered with this product is only
to be used by SAP’s Support Services and may not be
modified or altered in any way.
Documentation on SAP Service Marketplace
You can find this documentation at
service.sap.com/instguidesNW04service.sap.com/instguidesNW04service.sap.com/instguidesNW04service.sap.com/instguidesNW04
SAP AGSAP AGSAP AGSAP AG
Neurottstraße 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20
www.sap.comwww.sap.comwww.sap.comwww.sap.com
T yp o g r a ph i c C o n ve n t i o n s
Type Style Represents
Example Text
Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text
Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT
Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Example text
Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example text
Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text>
Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
EXAMPLE TEXT
Keys on the keyboard, for example, F2 or ENTER.
I c o ns
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Contents October 2006
Advanced Supportability Setup Guide for Solution Manager Diagnostics I
Contents
1 INTRODUCTION .................................................................................................................1 1.1 History of Changes................................. ..................................................................2 1.2 Naming Conventions................................. ...............................................................2
2 INSTALLATION – STEP BY STEP........................ .............................................................4 3 INSTALLATION PLANNING.............................. .................................................................6
3.1 Required Documentation ............................. ............................................................6 3.1.1 Composite SAP Note about Solution Manager Diagnostics...........................6 3.1.2 Information in the SAP Service Marketplace ..................................................6 3.1.3 Components for Problem Messages ..............................................................7
3.2 Hardware and Software Requirements for SMD Server .. .....................................7 3.3 Software Requirements for Monitored Systems ........ ...........................................8
4 INSTALLATION PROCESS............................... .................................................................9 4.1 Detailed Description of Automated Setup Tasks on SM D Server .......................9
4.1.1 Java Parameter Settings on SMD Server.......................................................9 4.1.2 SAP IGS........................................................................................................10 4.1.3 Setup of Single Sign-On on SMD Server......................................................14 4.1.4 Creation of Support Roles for J2EE Engine .................................................17 4.1.5 Connection to SLD........................................................................................20 4.1.6 Connection to NWA ......................................................................................21
4.2 Detailed Description of Automated Setup Tasks on Mo nitored Systems ........22 4.2.1 Java Parameter Settings on Monitored J2EE Engines.................................22 4.2.2 Setup of Single Sign-On on Monitored Systems ..........................................22 4.2.3 Assignment of J2EE Server Roles to the Support User ...............................25 4.2.4 Setup of HTTP Analysis................................................................................26 4.2.5 Setup of Thread Dump and GC Analysis......................................................27
5 SETUP OF SMD SCHEDULER ........................................................................................28 5.1 First Initialization of the Scheduler.............. .........................................................28 5.2 Setup of Tasks ..................................... ...................................................................29 5.3 Data Collection from Monitored System .............. ................................................30
6 SETUP OF SMD AGENT ..................................................................................................31 6.1 Manual Setup of SMD Agent.......................... ........................................................31
6.1.1 Command Line Execution.............................................................................31 6.1.2 SMD Agent Setup Steps ...............................................................................31 6.1.3 SMD Agent Start Profile................................................................................32 6.1.4 Change Credentials of SMD Agent...............................................................32 6.1.5 SSL Setup for SMD Agent ............................................................................33
6.2 Configuration of SMD Agent Applications............ ...............................................34 6.2.1 J2EE Command Console Configuration .......................................................37 6.2.2 File System Access Configuration ................................................................39 6.2.3 SQL Command Console Configuration ........................................................39 6.2.4 OS Command Console Configuration ..........................................................41 6.2.5 Log Viewer Configuration..............................................................................42 6.2.6 LDAP Browser Configuration........................................................................42
Introduction October 2006
History of Changes
Advanced Supportability Setup Guide for Solution Manager Diagnostics 1
1 Introduction Support Infrastructure with Solution Manager 4.0 – Solution Manager Diagnostics
As part of Solution Manager 4.0, Solution Manager Diagnostics (SMD) provides essential functions for efficient and safe root cause analysis of customer solutions based on SAP NetWeaver 2004 and SAP NetWeaver 2004S.
It especially provides functionality to support Java based components – it runs on the Java side of your Solution Manager 4.0 system. The abap stack of Solution Manager system has also to be used as central system for collecting and handling alerts (CCMS alert handling) as done for the previous Solution Manager releases – therefore we recommend setting up SMD for any SAP NetWeaver landscape.
For measuring performance as well as to troubleshoot problems of the J2EE Engine and its applications, Wily Introscope is integrated into the SMD but installed separately. The Introscope tool consists of a display, a server part (Introscope Enterprise Server) and a client part (Introscope agent).
Finally, SMD is linked to the Mercury Interactive load generator tool that enables remote load testing by SAP Support (e.g. during Going Live checks) in order to detect performance bottlenecks.
It is mandatory to install one complete Solution Manager 4.0 including SMD within your SAP NetWeaver solution landscape. One SMD system can monitor any number of SAP NetWeaver solutions.
High-level overview of the support infrastructure:
For detailed information about Solution Manager Diagnostics including end user documentation, see Solution Manager Diagnostics (Standard Guide).
Solution Manager Diagnostics Landscape
To monitor a SAP 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.
Introduction October 2006
History of Changes
Advanced Supportability Setup Guide for Solution Manager Diagnostics 2
• SMD Navigation : Java Web Dynpro component providing access to all tools related to monitor a SAP NetWeaver system. The list of monitoring tools is depending on the type of the monitored SAP NetWeaver system.
• SMD Monitoring Tools : Java Web Dynpro applications offering monitoring capabilities.
• SMD Agent : Java application running on the monitored systems and gathering information for the SMD Server.
• Solution Manager – landscape definition : Standard Solution Manager landscape definition (transaction SMSY). Provide to SMD the Netweaver components to monitor, publish the configuration and monitoring information used by the SMD Server through the agent
Implementation
This guide explains in detail the setup of Solution Manager Diagnostics and connected systems.
1.1 History of Changes Document Version Main Change
1.0 - September 2006
Advanced Supportability Setup Guide for Solution Manager Diagnostics
1.01- October 2006 Setup ICM added
1.2 Naming Conventions In this documentation, the following naming conventions apply:
SA
P S
olManD
iag
SMD Navigation
SA
P S
olManD
iag
SMD Navigation
SMD Monitoring Tools
SMD Agent
NetW
eaver
Solution Landscape
Solution M
anager
Java stack
Abap stack
Landscape definition
(SMSY)
SMD wizard
(SMDIAG_WIZARD)
Publish
Publish
Introduction October 2006
Naming Conventions
Advanced Supportability Setup Guide for Solution Manager Diagnostics 3
Terminology
• 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)
Variables
Variables Description
<SID> SAP system ID
<DBSID> Database system ID
<INSTDIR> Installation directory of the SAP system
<J2EE_HOME> Installation directory of the J2EE Engine
<JAVA_HOME> Installation directory of the JDK (Java Development Kit)
<OS> Operating system name within a path
Installation – Step by Step October 2006
Naming Conventions
Advanced Supportability Setup Guide for Solution Manager Diagnostics 4
2 Installation – Step by Step
Advanced (Non-Standard) Installation
Advanced (Non-standard) Installation
This guide contains all information to perform a Solution Manager Diagnostics installation on systems that need additional manual configuration steps.
This documentation is based on the current version of Solution Manager Diagnostics. Make sure that you have applied the newest version from SAP Service Marketplace.
Standard Installation Refer to Solution Manager Diagnostics (Standard Guide) for a standard installation step list, e.g. wizard-based setup of a monitored SAP J2EE Engine 6.40.
Manual Steps for the SMD Server If you want to configure particular settings for monitored systems based on SAP J2EE Engine 6.40 , follow the matrix below:
!!!! Step Remarks
4.1.1 Java Parameter Settings on SMD Server [on page 9]
4.1.2 SAP IGS [on page 10]
4.1.3 Setup of Single Sign-On on SMD Server [on page 14] optional
4.1.4 Creation of Role for ABAP User
As of NetWeaver 2004 SP Stack 13, the according role SAP_SOLMANDIAG_SAPSUPPORT is part of SAP standard delivery. If required, the role can be created (name: Z_SAPSUPPORT) or verified manually as explained here.
In addition to the J2EE role, the SMD user needs an ABAP role on the monitoring system. Role name Z_SAPSUPPORT is recommended.
1. Call transaction PFCG
2. Enter Z_SAPSUPPORT in field Role
3. Choose pushbutton (Create Role)
4. In the next screen, click the Authorizations tab and choose
pushbutton (Profile Generator expert mode)
5. By choosing pushbutton (Manual entry of authorization objects) and enter the following authorizations sequentially:
� S_ADMI_FCD authorization object that has to
Installation – Step by Step October 2006
Naming Conventions
Advanced Supportability Setup Guide for Solution Manager Diagnostics 5
contain:
ACTVT: NADM, ST0R
� S_RZL_ADM authorization object that has to contain:
ACTVT: 01, 03
� S_RFC authorization object that has to contain:
ACTVT: 16 RFC_NAME: RFC1, SAL_RFC, SALF, SALS, SCSMROUTE, SDIFRUNTIME, SYFU, SYST RFC_TYPE: FUGR
� S_TCODE authorization object that has to contain:
TCD: DB59, DB6COCKPIT, ST04M, ST04_MSS,OS07, RZ20, ST03G
6. Choose pushbutton (Generate), as a result you will get the technical name of the generated profile
7. Return with the F3 key and choose the Users tab
8. Assign the SMD user (e.g. SAPSUPPORT) to the generated profile by choosing the User comparison pushbutton
Installation – Step by Step October 2006
Naming Conventions
Advanced Supportability Setup Guide for Solution Manager Diagnostics 6
For enabling Single Sign-On, the user names for SMD (refer to Setup of Single Sign-On on Monitored Systems [on page 22]) and the monitored systems have to be identical. SAPSUPPORT is the recommended user name.
Creation of Support Roles for J2EE Engine [on page 17]
4.1.6 Connection to SLD [on page 20]
4.1.7 Connection to NWA [on page 21]
5.1 Initialization of the Scheduler [on page 28]
5.2 Setup of Tasks [on page 29]
5.3 Data Collection from Monitored System [on page 30]
Manual Steps for a Monitored 6.40 System If you want to configure particular settings for monitored systems based on SAP J2EE Engine 6.40 , follow the matrix below:
!!!! Step Remarks
4.2.1 Java Parameter Settings on Monitored J2EE Engines [on page 22]
4.2.2 Setup of Single Sign-On on Monitored Systems [on page 22]
optional
4.2.3 Assignment of J2EE Server Roles to the Support User [on page 25]
4.2.4 Setup of HTTP Analysis [on page 26]
4.2.5 Setup of Thread Dump and GC Analysis [on page 27]
6.1 Manual Setup of SMD Agent [on page 31]
6.2 Configuration of SMD Agent Applications [on page 34]
Installation Planning October 2006
Required Documentation
Advanced Supportability Setup Guide for Solution Manager Diagnostics 7
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.
• Information in the SAP Service Marketplace
• Components for problem messages
3.1.1 Composite SAP Note about Solution Manager Diagnostics
Last up-to-date information about SMD can be found in SAP Note 829218 . This SAP Note contains the most recent information on the installation, as well as corrections to the installation documentation.
You can find the up-to-date version of this note in the SAP Service Marketplace at the Internet address: service.sap.com/notes .
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)
• The current version of Solution Manager Diagnostics setup guide at service.sap.com/ operationsnw2004s � Supportability � Solution Manager Diagnostics - Setup Guide SPS 17.
• The general documentation for Solution Manager Diagnostics: at service.sap.com/diagnostics (Solution Manager Diagnostics area).
Solution Manager Diagnostics (Advanced Guide)
In addition to the standard guide, the advanced guide provides more detailed information on the setup procedure of automated tasks, plus some information for non-standard SMD scenarios.
You will find the current version of the Solution Manager Diagnostics advanced setup guide at service.sap.com/ operationsnw2004s � Supportability � Solution Manager Diagnostics - Advanced Setup Guide.
Solution Manager (Standard Guide)
You will find the current version of Solution Manager setup guide at service.sap.com/solutionmanager � Installation Guides � Release 4.0.
Installation Planning October 2006
Hardware and Software Requirements for SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 8
Wily Introscope
You will find the current version of Wily Introscope installation guide at service.sap.com/ operationsnw2004s � Supportability � Installation Guide Wily Introscope <version>.
When releasing this document, Wily Introscope 6.1 was the current version.
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 .
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.
Solution Manager Implementation guide (IMG)
This documentation is available online on the Abap system with the transaction SPRO.
Press the button 'SAP Reference IMG' and navigate to:
SAP Solution Manager Implementation Guide->SAP Solution Manager->Basic Settings->SAP Solution Manager System->Operations->Solution Manager Diagnostics
3.1.3 Components for Problem Messages In case of problems, contact SAP Support by creating a message in Service Marketplace, components:
• SV-SMG-DIA: issues related to Solution Manager Diagnostics
• SV-SMG-DIA-AGT : issues related to SMD Agent
• SV-SMG-DIA-IC: issues related to Integration Content for SMD
� SV-SMG-DIA-IC-CRM: issues related to CRM Integration Content for SMD
� SV-SMG-DIA-IC-EP: issues related to EP Integration Content for SMD
� SV-SMG-DIA-IC-ERP: issues related to ERP Integration Content for SMD
� SV-SMG-DIA-IC-MDM: issues related to MDM Integration Content for SMD
� SV-SMG-DIA-IC-XI: issues related to XI Integration Content for SMD
• SV-SMG-DIA-SRV: issues related to SMD Server Infrastructure / Framework
• XX-PART-MIC: issues related to Mercury LoadGenerator
• XX-PART-WILY : issues related to Wily Introscope
3.2 Hardware and Software Requirements for SMD 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:
Installation Planning October 2006
Software Requirements for Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 9
Requirement Type Requirement
Hardware Requirements
Disk Space: 40 GB
RAM: 4 GB
Virtual Memory: 3 x size of physical memory Number of CPU: 2
Software Requirements
SAP Web AS 6.40 Java Add-In, SP Stack 17
Platform-dependent information is available on service.sap.com/pam , refer to for SAP Web AS 6.40.
For detailed sizing information, refer to SAP Note 915676 .
3.3 Software Requirements for Monitored Systems For systems monitored by Solution Manager Diagnostics, make sure to apply the mentioned program versions or newer versions. All packages can be downloaded from SAP Service Marketplace. The following table lists the requirements:
Software Component
Requirement
SAP NetWeaver 2004 Portal
J2EE Engine 6.40 SP Stack 14
Other SAP NetWeaver 2004 systems
SP Stack 14
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 10
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.
As SMD is part of Solution Manager 4.0, the setup for the abap stack should be performed on the system where Solution Manager (abap) was installed (normally it is the Abap side of the NW2004s double stack installation).
4.1 Detailed Description 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:
http://<host>:<port>/smd/admin
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.
4.1.1 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:
9. Start the J2EE Configtool where the Solution Manager Diagnostics is running
10. For each server node, navigate to cluster-data → Instance_<ID> → Server_<ID>
11. In the General tab, apply the Java parameters
� -verbose:gc
� -XX:+PrintGCTimeStamps (except on IBM JVM-based systems, see SAP Note 723909 )
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 11
12. Navigate to cluster-data → Instance_<ID> → Server_<ID> → Services → http
13. In the Global properties tab, apply the parameters by entering into the Value field:
� CompressedOthers: true
� MinimumGzipLength: 1024
� NeverCompressed: remove entries for *.js, *.cs, *.css by choosing the Set pushbutton after every change
14. To persist all customized settings, choose the pushbutton (Save)
4.1.2 SAP IGS SAP IGS (Internet Graphics Server) enables the output of graphics within ABAP based transactions. General information for the setup of SAP IGS is available in the SAP Library.
IGS Port Number Determination
SMD uses by default the SAP IGS installed on the same stack as it is running (the Java Stack). The default port is predefined, but if it as been customized you will need to change it in SMD configuration.
Under Java Stack
To find out the IGS port, open file /usr/sap/<SID>/<INSTANCE>/igs/conf/igs.xml, you will find the port used by IGS by getting the value of element LISTENERHTTP, attribute port (e.g. <LISTENERHTTP port="40080" />)
To test the IGS service, start your browser and launch the following URL:
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 12
http://<host>:<igs_port> (e.g. http://localhost:40080)
If example graphics are displayed, the IGS service is running properly.
Under ABAP Stack
The following RFC destinations have to be updated by using transaction SM59 on the ABAP stack. Make sure that field Program ID contains IGS.<SID>, e.g. IGS.SMD.
• GFW_ITS_RFC_DEST
• IGS_RFC_DEST
To test the IGS service, start ABAP transaction SA38 and run program GRAPHICS_IGS_ADMIN, use as IGS RFC destination IGS_RFC_DEST.
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 13
If example graphics are displayed, the IGS service is running properly.
To find out the IGS port, choose the pushbutton Status. You will find the port number in table CONNECTED_LISTENER, line Http, row Parameter (e.g. 40080):
Configuration of IGS
This operation is performed automatically by the Monitoring System Setup Wizard (refer to Solution Manager Diagnostics (Standard Guide)), but can be performed manually as well.
Get the IGS Port as described in chapter IGS Port Number Determination [on page 10].
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
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 14
2. Navigate to Server → Services → Configuration Adapter
3. In the Display configuration tab, open the branch for webdynpro → sap.com → tc~wd~dispwda
4. To switch to edit mode, choose the pushbutton (Display/Change); you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton
5. To modify data, choose the pushbutton (Change) or just double-click on Propertysheet default
6. Now you can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter
7. A single mouse click will open a new window where you can change the configuration data.
Change parameter IGSUrl to URL & port of the IGS, e.g. http://p135809.wdf.sap.corp:40080
Example screenshot for changing settings:
You can verify IGSUrl by entering this URL directly into your web browser
8. To save the data, choose the Apply custom pushbutton
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 15
4.1.3 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 [on page 22] – even if both Java and ABAP parts are installed on the same machine.
Always use full-qualified hostnames, e.g. p135809.wdf.sap.corp
For SSO scenarios, the Solution Manager Diagnostics system has to be in the same network domain as the monitored systems
Configuration
1. Preparation of the J2EE server of Solution Manager Diagnostics. The Client ID of the J2EE system has to be changed. This ID will be stored in every ticket and has to be unique. If the SSO module logs on the client with the ticket it uses this Client ID
a. Start the Visual Administrator and log on to the J2EE Engine where the Solution Manager Diagnostics is running
b. Navigate to Server → Services → Configuration Adapter
c. In the Display configuration tab, open the branch for cluster_data → server → cfg → services
d. Choose the pushbutton (Display/Change) to switch to the edit mode; you will receive a popup with an accordingly warning that has to be confirmed with the yes pushbutton
e. Choose the pushbutton (Change) or just double-click on Propertysheet com.sapsecurity.core.ume.service
f. You can change customizing entries by positioning the mouse to the line where you find the information that has to be adapter
g. A single mouse click will open a new window where you can change the configuration data:
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 16
Change parameter login.ticket_client to a number <> 000, e.g. 169
h. To save the data, choose the pushbutton Apply custom.
i. Restart the J2EE Engine of SMD.
2. Exporting certificates from the J2EE server
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, first select the view TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window)
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 17
d. To export the certificate on file system, choose pushbutton Export and enter any file name. This certificate has to be imported into the monitored systems, refer to Setup of Single Sign-On on Monitored Systems [on page 22].
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
� EvaluateAssertionTicketLoginModule
� EvaluateTicketLoginModule
� SecuritySessionLoginModule
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 18
4.1.4 Creation of Role for ABAP User As of NetWeaver 2004 SP Stack 13, the according role SAP_SOLMANDIAG_SAPSUPPORT is part of SAP standard delivery. If required, the role can be created (name: Z_SAPSUPPORT) or verified manually as explained here.
In addition to the J2EE role, the SMD user needs an ABAP role on the monitoring system. Role name Z_SAPSUPPORT is recommended.
2. Call transaction PFCG
3. Enter Z_SAPSUPPORT in field Role
4. Choose pushbutton (Create Role)
5. In the next screen, click the Authorizations tab and choose pushbutton (Profile Generator expert mode)
6. By choosing pushbutton (Manual entry of authorization objects) and enter the following authorizations sequentially:
� S_ADMI_FCD authorization object that has to contain:
ACTVT: NADM, ST0R
� S_RZL_ADM authorization object that has to contain:
ACTVT: 01, 03
� S_RFC authorization object that has to contain:
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 19
ACTVT: 16 RFC_NAME: RFC1, SAL_RFC, SALF, SALS, SCSMROUTE, SDIFRUNTIME, SYFU, SYST RFC_TYPE: FUGR
� S_TCODE authorization object that has to contain:
TCD: DB59, DB6COCKPIT, ST04M, ST04_MSS,OS07, RZ20, ST03G
7. Choose pushbutton (Generate), as a result you will get the technical name of the generated profile
8. Return with the F3 key and choose the Users tab
9. Assign the SMD user (e.g. SAPSUPPORT) to the generated profile by choosing the User comparison pushbutton
For enabling Single Sign-On, the user names for SMD (refer to Setup of Single Sign-On on Monitored Systems [on page 22]) and the monitored systems have to be identical. SAPSUPPORT is the recommended user name.
4.1.5 Creation of Support Roles for J2EE Engine As of NetWeaver 2004 SP Stack 13, the according role SAP_JAVA_SUPPORT is part of SAP standard delivery. SAP_JAVA_NWADMIN_CENTRAL_READONLY is part of SAP standard delivery as of SP Stack 12. If required, these roles can be created or verified manually as explained here.
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 20
All users for Solution Manager Diagnostics have to be assigned to the role SAP_JAVA_SUPPORT.
1. Open the User Management menu within the local J2EE Engine: http://<host>:5<instance no.>00, navigate to User Management
2. Login as J2EE administrator
Navigate to Search and choose Get role.
3. Create role SAP_JAVA_SUPPORT , go to the tab Assigned Actions and in Available Actions choose the role action sap.com_com~sap~tc~webdynpro.Administrate. Choose the Add pushbutton. SAPSUPPORT is recommended as user name:
4. Create role SAP_JAVA_NWADMIN_CENTRAL_READONLY within user management, add the role actions
� UME.Read_All
� tc~lm~webadmin~permissions.Applications_Display
� tc~lm~webadmin~permissions.LocalSLD.Display
� tc~lm~webadmin~permissions.Log_Display
� tc~lm~webadmin~permissions.Monitoring_Display
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 21
� tc~lm~webadmin~permissions.Performance_Display
� tc~lm~webadmin~permissions.SystemInfo_Display
� tc~lm~webadmin~permissions.User_Access_All
� tc~lm~webadmin~permissions.WebAdmin_Central
and apply the roles to the user created for SMD. SAPSUPPORT is recommended as user name:
5. Verify that the Solution Manager Diagnostics users are member of both roles SAP_JAVA_SUPPORT and SAP_JAVA_NWADMIN_CENTRAL_READONLY:
4.1.6 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:
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
Installation Process October 2006
Detailed Description of Automated Setup Tasks on SMD Server
Advanced Supportability Setup Guide for Solution Manager Diagnostics 22
3. In the Runtime tab, select the HTTP Settings tab
4. Enter the connection information to the SLD server of your solution landscape.
4.1.7 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: text information for the selected item (cannot be changed)
� Name: name of the property (cannot be changed)
� Datatype: data type of the property item (cannot be changed)
� Default: SAP-delivered value (cannot be changed)
� Custom: if this field contains a value, the default value
8. The following parameters should be modified to match the NetWeaver Administration Console:
Name SAP default Example Description
nwahost protocol://host:port http://p135809.wdf.sap.corp:2040
By default the nwahost will be setup to http://<smdserver>:<smdport>
Server & port where the NWA is running
The protocol can be https or http. If no protocol is specified, http:// will be added by SMD
Use fully-qualified host names
Installation Process October 2006
Detailed Description of Automated Setup Tasks on Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 23
nwaadmin Administrator The administrator of the SAP NetWeaver administration server
nwauser Password The administrator of the SAP NetWeaver Administration server
9. To save modified parameters, choose the Apply custom pushbutton
4.2 Detailed Description 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:
http://<host>:<port>/smd/admin
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 (explained here in detail).
4.2.1 Java Parameter Settings on Monitored J2EE Eng ines 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 Engine, the output of garbage collections is required. Proceed as follows:
1. Start the J2EE Configtool where the monitored system is running
2. For each server node, navigate to cluster-data → Instance_<ID> → Server_<ID>
3. In the General tab, apply the Java parameters
� -verbose:gc
� -XX:+PrintGCTimeStamps
4. Choose the Save pushbutton to save the configuration, restart the server node(s)
4.2.2 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.
The certificates created within the J2EE Engine of the Solution Manager Diagnostics server (refer to Setup of Single Sign-On on SMD Server [on page 14]) have to be imported into the monitored SAP systems. The procedure is different for ABAP systems and systems with active J2EE Engines.
Installation Process October 2006
Detailed Description of Automated Setup Tasks on Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 24
- Use full-qualified host names, e.g. p135809.wdf.sap.corp - If you are running a Web AS with both active ABAP and J2EE components, you have to import the certificate for both components - This procedure is valid for 6.40 J2EE Engines
Configuration
1. Importing the certificate on J2EE system:
a. Start the Visual Administrator and log on to the J2EE Engine of the monitored system (e.g. Enterprise Portal)
b. Navigate to Server → Services → Key Storage
c. In the Runtime tab, first select TicketKeystore (Views window) and then SAPLogonTicketKeypair-cert (Entries window)
d. To import the certificate from file system, choose the pushbutton Load. For exporting certifcates from SMD, refer to refer to Setup of Single Sign-On on SMD Server [on page 14]
e. Restart the J2EE Engine of the monitored system
2. Allow J2EE application (e.g. Enterprise Portal) to accept SSO tickets:
a. Start the Visual Administrator and log on to the J2EE Engine of your monitored system
b. Navigate to Server → Services → Security Provider
c. Choose SAP-J2EE-Engine (Components window) and open the Authentication tab
d. Choose the pushbutton Add New to add the following login module:
� EvaluateTicketLoginModule
e. Choose ticket in window Components
f. In the Authentication tab, choose Login Module:
� com.sap.security.core.server.jaas.EvaluateTicketLoginModule
g. To add properties, choose the pushbutton Modify
Installation Process October 2006
Detailed Description of Automated Setup Tasks on Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 25
� ume.configuration.active: true
� trustediss1: CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1
O=<company>,C=<country> are optional
� trusteddn1: CN=<SID of SMD>,O=<company>,C=<country> e.g. CN=WA1
O=<company>,C=<country> are optional
� trustedsys1: <SID of Solution Manager Diagnostics>,<client ID> e.g. WA1,169
Confirm settings with the OK pushbutton.
Now change the Authentication Template for the following applications in the Components window to ticket (drop-down box):
� sap.com/SQL_Trace*OpenSQLMonitors (SQL Trace)
� sap.com/SQL_Trace*OpenSQLTrace (SQL Trace)
� sap.com/tc~monitoring~systeminfo*sap_monitoring (Systeminfo)
� sap.com/tc~wd~dispwda*webdynpro_dispatcher (Web Dynpro Console)
Installation Process October 2006
Detailed Description of Automated Setup Tasks on Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 26
� sap.com/tc~wd~dispwda*webdynpro_welcome (Web Dynpro Console)
4.2.3 Assignment of J2EE Server Roles to the Suppor t 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 Role
sap.com/ tc~monitoring~systeminfo*sap_monitoring
SystemInfo_Support_Role
sap.com/ SQLTrace*OpenSQLMonitors component
OpenSQLMonitorLogonRole
For monitored SAP J2EE Engines 6.40 as of SP Stack 15:
Component Role
SAP-J2EE-ENGINE SAP_JAVA_SUPPORT
For monitored SAP J2EE engines running on XI:
Component Role
sap.com/com.sap.xi.repository*rep display
sap.com/com.sap.xi.directory*dir display
sap.com/ com.sap.rprof.remoteProfile* exchangeProfile
display
sap.com/com.sap.xi.rwb*rwb display
sap.com/com.sap.xi.mdt*mdt display
sap.com/com.sap.aii.af.cpa.app*CPACache xi_af_cpa_monitor
sap.com/ com.sap.aii.af.app*AdapterFramework
xi_af_adapter_monitor
sap.com/ tc~TechSrv~XML_DAS*DataArchivingService
XMLDASSecurityRole
Example for Role Assignment
To grant the role SystemInfo_Support_Role, start the J2EE Engine Visual Administrator tool on the monitored J2EE system:
1. navigate to Server → Services → Security Provider
2. select component sap.com/tc~monitoring~systeminfo*sap_monitoring
3. navigate to tab Security Roles
4. select security role SystemInfo_Support_Role
5. use the Add pushbutton to add the SAPSUPPORT user to this role
Installation Process October 2006
Detailed Description of Automated Setup Tasks on Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 27
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 834568 ) for the web browser to log the requests and responses between the browser and the SAP Enterprise Portal. The user interface of HTTP Analysis displays detailed performance-related information graphically.
Activating HTTP log information on J2EE Engine 6.40 (all SP Stacks)
1. Start the Visual Administrator and log on to the J2EE Engine of the Enterprise Portal
2. Navigate to Server → Services → Log Configurator
3. In the Categories tab, open Log Controller Root Category → System → HTTPAccess → Access
4. Set Severity to Info and apply this setting to all cluster nodes by choosing the Save pushbutton
5. Start the J2EE Configtool of the Enterprise Portal
6. Navigate to cluster-data → Instance_<ID> → Server_<ID> → Services → http
7. Apply the following parameters by entering into the Value field:
� LogHeaderValue: X-CorrelationID
� LogResponseTime: true by choosing the Set pushbutton after every change
Installation Process October 2006
Detailed Description of Automated Setup Tasks on Monitored Systems
Advanced Supportability Setup Guide for Solution Manager Diagnostics 28
In case you want to compare the HTTP message headers between client and server (e.g. to find out if proxy servers, IIS, or firewalls modify HTTP headers), then you have to switch on parameter LogRequestResponseHeaders in addition: LogRequestResponseHeaders = true
8. To persist all customized settings, choose the pushbutton (Save)
9. Navigate to Server → Services → HTTP Provider
10. In the Runtime tab, open tab Virtual Hosts → General
11. Make sure that parameter Log Responses is checked
12. To persist all customized settings, choose the Save properties pushbutton
4.2.5 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.
4.2.6 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.
13. 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
14. Save and activate the profile, restart the system
As this parameter value exceeds 1 line, it has to be maintained carefully. The result should look like shown in the example below:
Setup of SMD Scheduler October 2006
Initialization of the Scheduler
Advanced Supportability Setup Guide for Solution Manager Diagnostics 29
5 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:
http://<host>:<port>/smd
Afterwards, navigate to tab Configuration → Scheduler.
As alternative, the SMD Scheduler can be started within the SMD Administration application by launching URL:
http://<host>:<port>/smd/admin
Afterwards, navigate to tab Scheduler.
You have to log on as J2EE administrator to the SMD Administration application.
5.1 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.
This button is available only if no task is created in Scheduler.
Setup of SMD Scheduler October 2006
Setup of Tasks
Advanced Supportability Setup Guide for Solution Manager Diagnostics 30
5.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.
• 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 Data Collection from Monitored System [on page 30].
Setup of SMD Scheduler October 2006
Data Collection from Monitored System
Advanced Supportability Setup Guide for Solution Manager Diagnostics 31
5.3 Data Collection from Monitored System After all tasks for a new system have been configured (refer to Setup of Tasks [on page 29]), these tasks have to be scheduled. 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.
• 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.
Setup of SMD Agent October 2006
Manual Setup of SMD Agent
Advanced Supportability Setup Guide for Solution Manager Diagnostics 32
6 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.
6.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.
6.1.1 Command Line Execution smdsetup <path of JVM 1.4> <host name or ip adr. of SMD Server> <P4 port> <admin. user> <pwd.>
c: cd \usr\sap\SMD\J97\SMDAgent smdsetup.bat C:\j2sdk1.4.2 p135809.wdf.sap.corp 50004 SMD_ADMIN pwd
6.1.2 SMD Agent Setup Steps When running properly, the SMD Agent setup output looks like the example below: --------------------------------------------------------------------- SAP Solution Manager Diagnostic - SMD Agent Setup - Copyright (c) 2005 SAP AG --------------------------------------------------------------------- SMD Agent Setup is in process --------------------------------------------------------------------- - STEP 1: checking JDK location JDK location is consistent: C:\j2sdk1.4.2_04\bin - STEP 2: checking JDK Version JDK Version is correct: 1.4.2_04-er - STEP 3: checking Connection to SMD Server SMD Server check completed successfully - STEP 4: generating Runtime Properties runtime.properties has been created. - STEP 5: generating Launcher smdagent.bat has been created. smdagent.sh has been created. - STEP 6: generating SecStore secstore.properties: has been created. secstore.properties: user has been set. secstore.properties generation completed successfully. - STEP 7: checking P4 Connection and SMD Agent Registration SMD Agent Registration succeeded --------------------------------------------------------------------- SMD Agent Setup completed successfully ---------------------------------------------------------------------
Setup of SMD Agent October 2006
Manual Setup of SMD Agent
Advanced Supportability Setup Guide for Solution Manager Diagnostics 33
The different operations performed are the following:
• Step 1: checks the location of the Java Virtual machine 1.4.
• 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.
6.1.3 SMD Agent Start Profile It is possible to modify the startup parameters of the SMD Agent, to change memory setting, etc. The startup profile is located under /usr/sap/SMD/J<NN>/profile/smd.properties.
Example Profile
#-------------------------------------------------------------------- # SMD AGENT instance properties # Created on Tue Oct 25 13:21:54 CEST 2005 #-------------------------------------------------------------------- smdagent.name=SMDAgent smdagent.type=server smdagent.rootPath= ../SMDAgent smdagent.classPath =lib/launcher/smdagentlauncher.jar:lib/launcher/logging.jar smdagent.mainClass = com.sap.smd.agent.launcher.SMDAgentLauncher smdagent.parameters = run jcontrol smdagent.javaParameters = -Xmx128m -Xms128m smdagent.ShutdownTimeout=10000 smdagent.Id=1 smdagent.DebugMode=no smdagent.DebugPort=58021 smdagent.Debuggable=yes
After changing its profile, the SMD Agent has to be restarted.
6.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:
http://<host>:<port>/smd/admin
Setup of SMD Agent October 2006
Manual Setup of SMD Agent
Advanced Supportability Setup Guide for Solution Manager Diagnostics 34
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.
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 [on page 31]. 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.
6.1.5 SSL Setup for SMD Agent
Prerequisites
Configure the SAP J2EE Engine of the SMD Server to receive P4 SSL calls. Refer to the SAP Help Portal (http://help.sap.com/saphelp_nw04s/helpdata/en/f1/2de3be0382df45a398d3f9fb86a36a/frameset.htm) for detailed information
Setup
By default, the communication between the SMD Agents and the Monitoring System (SMD Server) is established via the P4 protocol (unsecured).
To enable secure communication, the SSL transport must be configured between the SMD Agent and the SMD Server. Two types of installation are possible:
1. The SMD Agent has a separate JDK (used by the SMD Agent exclusively)
a. Configure the JDK to use SSL libraries: Add the iaik libs in the JRE\lib\ext folder of the JDK of the SMD Agent: iaik_jce.jar iaik_jsse.jar iaik_ssl.jar
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 35
The jre\lib\security folder might contain local_policy.jar and US_export_policy.jar
b. Configure the SMD agent to use SSL: Add the property smd.agent.connection.transport=ssl in \usr\sap\SMD\JXX\SMDAgent\configuration\runtime.properties and modify the property smdserver.port to match the P4 SSL port. (5xxx6 by default)
c. Restart the SMD Agent
2. The SMD Agent uses a common JDK (used by other components as well)
a. Configure the SMD Agent profile to use SSL libraries:
� the SAP installations uses the same JDK that is already configured for SSL:
• if the server hosts a central (main) instance: - location of the iaik libs: /usr/sap/<SID>/sys/global/security/lib/tools - add the path to the iaik files to property smdagent.classPath in the SMD Agent profile at /usr/sap/SMD/J<instance no.>/profile/smd.properties
• if the server hosts a dialog instance: - location of the iaik libs: <J2EE_HOME>/sys/global/security/lib/tools - add the path to the iaik files to property smdagent.classPath in the SMD Agent profile at /usr/sap/SMD/J<instance no.>/profile/smd.properties
� the SAP installations is not configured for SSL:
• you can use either the first point in option 2.a or configure the JDK exclusively for the SMD Agent.
Make sure that you don’t run into combatibility problems when the SSL configured JDK is used by other applications as well!
b. Configure the SMD agent to use SSL: Add the property smd.agent.connection.transport=ssl in \usr\sap\SMD\JXX\SMDAgent\configuration\runtime.properties and modify the property smdserver.port to match the P4 SSL port. (5xxx6 by default)
c. Restart the SMD Agent
6.2 Configuration of SMD Agent Applications This section explains the individual setup of applications that are running within the SMD Agent.
Prerequisites
Initial Setup of SMD Agent Applications (refer to Solution Manager Diagnostics (Standard Guide), chapter Initial Setup of SMD Agent Applications) has to be executed before. The
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 36
SMD Agents have to be in status (started) – what can be verified in tab Agent Administration, sub-tab Agents of the SMD Administration application.
With exception of the LDAP browser application, all SMD Agent applications are configured automatically during the step Initial Setup of SMD Agent Applications (refer to Solution Manager Diagnostics (Standard Guide), chapter Initial Setup of SMD Agent Applications).
Thus, the following setup steps have to be performed only when the automatic configuration failed or has to be customized.
Setup Steps
Start the SMD Administration application by launching URL:
http://<host>:<port>/smd/admin
You have to log on as J2EE administrator to the SMD Administration application.
Navigate to tab Agent Administration and then sub-tab Application Configuration.
Example screenshot of the Application Configuration screen:
Overview of the Agent Application Configuration
Each application running in the SMD Agent has its own configuration stored centrally in the SMD system.
The configuration can have two different scopes:
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 37
• Global : The configuration is common and shared by all SMD Agents connected to SMD
• Host : The configuration is available for a specific host only
The SMD Agent infrastructure stores the configuration of the remote agent applications secured and publishes this configuration to the connected SMD Agents. When an agent application gets its configuration from the SMD Server, its configuration is the merger of the values defined for the Global and the Host scope.
Furthermore, a global configuration named com.sap.smd.agent.application.global.configuration is available for all agent applications and is maintained by the SMD infrastructure. Therefore, a remote agent application has access to its own configuration or the global configuration.
For SMD SP Stack 08, the following agent applications can be configured:
Application Name SMD Use Case
com.sap.smd.agent.application.connectors Provide P4 or JMX connection to the monitored SAP J2EE engine
com.sap.smd.agent.application.telnet Provides remote access to the J2EE telnet console for the SMD J2EE command console application
com.sap.smd.agent.application.remoteos Provides remote access of J2EE standalone logviewer to log files for SMD application Log Display
com.sap.smd.agent.application.database Access to the DB of the remote system to return table information to the SMD SQL Command Console application
com.sap.smd.agent.application.global.configuration Global configuration of the SMD Agents
com.sap.smd.agent.application.logviewer Provides an access to the file system of a monitored system. Files can be displayed or downloaded
com.sap.smd.agent.application.ldap
Manual configuration is required.
Provides remote access to connect to a LDAP server for the SMD LDAP browser application
com.sap.smd.agent.application.datacollector Collects XML based data from monitored systems (replaces the Component Analyzer download feature)
com.sap.smd.agent.application.filesystem Provides access to the remote file system for the SMD File System Browser application, and the Gather/Upload functionality
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 38
com.sap.smd.agent.application.switch Used for the migration between SAP NetWeaver 2004 to 2004s
com.sap.smd.agent.application.portalactivityreport Retrieves data for Portal Activity Reporting (PAR) from monitored SAP Enterprise Portals
com.sap.smd.agent.application.remotesetup Enables to setup the J2EE engine of a monitored system for SMD usage, from the smd/admin application
A property editor is used to change the configuration for SMD Agent applications.
After choosing the Edit pushbutton, you can change the property values in the Custom Value field. The default value delivered by the agent application is always displayed in the Default Value column. To change a property to its default value, choose pushbutton Reset Property or Reset All.
The Add Property pushbutton will open a popup window where the following fields can be entered:
Field Description Comment
Property Name The name of the property
Property Value The value of the property
Property Attribute Indicates if the property is secure or not
In the case of a secure property, the value is not displayed in the screen.
Choose the Save pushbutton to store the configuration and send it to the selected SMD Agent.
6.2.1 J2EE Command Console Configuration This application provides access to a read-only set of J2EE commands on the monitored hosts used by the J2EE command console application. The telnet protocol is used for this application.
Configuration
Configure the following parameters:
Application Scope Name Description
global.configuration host <sid>/sapj2ee/admin/user The SAP J2EE admin user with telnet execution rights
global.configuration host <sid>/sapj2ee/admin/pwd
telnet host <sid>/sapj2ee/telnet/port J2EE telnet port 5<instance no.>08, e.g. 50008
telnet Global or by host
<command name> True if the command is allowed, false otherwise
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 39
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>/
Enabling command CLEAR_HTTP_CACHE and disabling the parameters /-l/ /-list/ /-r/ /-hitrate/ for command CACHE:
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 40
6.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.
If root directories are modified, at least the SAP root directory (X:/usr/sap, where X: is the installation drive on Windows systems) must be part of the list. For multi drive installations, all SAP directories must be part of the list (e.g. C:/usr/sap, D:/usr/sap, etc.).
6.2.3 SQL Command Console Configuration To enable the execution of queries by the SQL Command Console, the database application has to be configured.
Configuration
Configure the following parameters:
Application Scope Name Description
database host <SID>|config.db.driverclass
The class of the JDBC driver to use to connect from the SMD agent to the remote DB
database host <SID>|config.db.driverjars
The jar files containing the JDBC driver to use for the connection from the SMD agent to the remote DB
- the location of the files refers to the server where SMD Agent runs (monitored system) - separate files by semicolon ( ; ), e.g. E:\jars\base.jar; E:\jars\sqlserver.j
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 41
ar
database host <SID>|config.db.user
The user to use for the DB connection
database Host <SID>|config.db.password
The password of the user
database Host <SID>|config.db.url
The URL of the DB.
<SID>|config.db.driverclass
MS SQL SERVER com.ddtek.jdbc.sqlserver.SQLServerDriver
Oracle oracle.jdbc.driver.OracleDriver
MAX DB com.sap.dbtech.jdbc.DriverSapDB
DB2 com.ibm.db2.jcc.DB2Driver
If the database running on 6.20, you will find the corresponding Java files (extension: .jar) at: <J2EE_HOME>/cluster/server/additional-lib/com/sap/data_direct_driver_references
If the database running on 6.40, you will find the corresponding Java files (extension: .jar) at: <J2EE_HOME>/cluster/server<n>/bin/ext/com.sap.datadirect (MS SQL Server) or <MaxDB home directory>/programs/runtime/jar (MaxDB). The driver for Oracle is part of the Oracle client (db-dependent part of the ABAP kernel).
<SID>|config.db.driverjars
MS SQL SERVER base.jar, sqlserver.jar, util.jar
Oracle classes12.jar
MAX DB SAPDBC.JAR
DB2 db2jcc.jar, db2jcc_license_cu.jar
<SID>|config.db.user/password
Enter User and Password of the database schema owner SAP<SID>DB, e.g. SAPP62DB
<SID>|config.db.url
MS SQL SERVER jdbc:datadirect:sqlserver://<host>:<port>;DatabaseName=<SID> e.g. jdbc:datadirect:sqlserver://p78293:1433;DatabaseName=P62
Oracle jdbc:oracle:thin:@<host>:<port>:<SID> e.g. jdbc:oracle:thin:@us7201:1527:EP0
MAX DB jdbc:sapdb://<host>/<SID>
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 42
e.g. jdbc:sapdb://P114280/TYR
DB2 jdbc:db2://<host>:<port>/<SID> e.g. jdbc:db2://P114280:5912/TYR
Starting from SP17 the old format properties (user, url, driverclass, driverjars, password) is not supported anymore. The database configuration task is migrating each of the old properties to the new format <SID>|config.db.<oldpropertyname>.
As the configuration task is not available in 620 the migration is not performed and the new properties have to be created manually and filled with the correct values.
6.2.4 OS Command Console Configuration OS Commands Console allows to launch certain operating system commands by the SMD Agent user.
On the monitored system, the user may not have rights to execute all commands. Before using OS Command Console, you should configure correctly SMD Agent user on each monitored system.
Configuration
Configure the following parameters:
Application Scope Name Description
remoteos host oscommand.unix.shell.command
The shell used by Os Command Console on an UNIX monitored system
All commands are describe in resource oscommand.xml delivered with application com.sap.smd.agent.application.remoteos. To configure the following parameters please download the file, edit parameters and then upload it again in your Application Configuration.
Tag Description Example
Cmd name Name of the command available in the OS Command Console application
IP Config
Cmd desc Explanation of the command Displays all current TCP/IP network configuration values.
OsCmd ostype
Valid Operating System for the command
WINDOWS
OsCmd exec
Execution string for the command on OS level
ipconfig
OsCmd path
Location of the command (if not in standard search path)
c:\Windows\system32
OsCmd param
“true”: parameters are allowed
“false”: parameters are not allowed
true
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 43
OsCmd runtime
Timeout value in seconds 5
Exclude param
If parameters are allowed in general (see tag param), particular parameters can be excluded
^(/|-)(renew|release)$
Help ref Reference the command which need to be executed to get help content
You can put the help content directly under tag Help (remove attribute ref)
If this tag is not available the help content would be the Cmd desc value
IOStatHelp
Each command defined in file oscommand.xml should be in the SMD Agent user path and has to be accessible by this user only.
6.2.5 Log Viewer Configuration The Log Viewer application of the SMD Agent will start the J2EE Standalone Logviewer on the monitored system (if available).
Configuration
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
6.2.6 LDAP Browser Configuration
This step has to be performed when a LDAP system should be connected to Solution Manager Diagnostics. It allows browsing the LDAP only.
Navigate to tab Agent Administration and then sub-tab Application Configuration and click on com.sap.smd.agent.application.ldap . The system where LDAP is running and a SMD Agent is installed can be selected from drop-down box Scope.
Setup of SMD Agent October 2006
Configuration of SMD Agent Applications
Advanced Supportability Setup Guide for Solution Manager Diagnostics 44
Enter the following data:
Name Description
ldap.hostname Full qualified name of LDAP Server
ldap.port LDAP server port
ldap.user Use which have credentials to read the data in LDAP Server
ldap.pwd Password, can be hidden by choosing the Secure Property option