Monitoring Response Times of Transactions or Clients

SAP Web Application Server 620


2002 Copyright © Copyright 2002 SAP AG. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP Markets and Commerce One. the Citrix logo. mySAP.SAP Online Help 08. pSeries. Word®. R/3. EXCEL®. UNIX®. SAP Business Workflow. OSF/1®. JAVASCRIPT® is a registered trademark of Sun Microsystems. The information contained herein may be changed without prior notice. All other product and service names mentioned are the trademarks of their respective owners. Management Cockpit. ORACLE® is a registered trademark of ORACLE Corporation. Inc. Massachusetts Institute of Technology. z/OS. AIX®. R/2. 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. WinFrame®. DB2 Universal Database. IBM®. xSeries. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. mySAP. XML. SAPPHIRE. PowerPoint® and SQL Server® are registered trademarks of Microsoft No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. SAP EarlyWatch. RIVA. zSeries. Citrix®. WINDOWS®. Tivoli®. JAVA®is a registered trademark of Sun Microsystems. OS/400®. XHTML are trademarks or registered trademarks of W3C®. NT®. AS/400®. Inc. Intelligent Miner. DB2®. Program Neighborhood®. SAP ArchiveLink. and Motif® are registered trademarks of the Open Group. BAPI. All rights reserved. DHTML. Inc. S/390®.. MVS/ESA. MetaFrame®. WebSphere®. SAP Logo. WebFlow. HTML. SAP. X/Open®. World Wide Web Consortium.07. MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems. used under license for technology invented and implemented by Netscape. Monitoring Response Times of Transactions or Clients 2 620 . Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. Microsoft®. ICA®. OS/390®. Netfinity®. VideoFrame®. AFP. OS/2®. iSeries. Parallel Sysplex®.

Call the SAP Library and choose mySAP Technology Components → SAP Web Application Server → Computing Center Management System (BC-CCM) → Monitoring in the CCMS → The Alert Monitor. This includes file and directory names and their paths.SAP Online Help 08. Variable user entry. table names. Cross-references to other documentation. Names of elements in the system. These include field names. upgrade. transaction codes. Keys on the keyboard. Exact user entry. Emphasized words or phrases in body text. Monitoring Response Times of Transactions or Clients 3 620 . and database tools.07. source code. for example. for example.2002 Symbols Symbol Meaning Caution Example Note Recommendation Syntax Typographic Conventions Format Example text Description Words or characters that appear on the screen. SELECT and INCLUDE. pushbuttons as well as menu names. when surrounded by body text. messages. and options. program names. Pointed brackets indicate that you replace these words and characters with appropriate entries before you enter them in the system. These are words or characters that you enter in the system exactly as they appear in the documentation. see the online documentation. Screen output. titles of graphics. paths. screen titles. names of variables and parameters as well as names of installation. and tables. function keys such as F2 or the ENTER key Example text EXAMPLE TEXT Example text Example text <Example text> EXAMPLE TEXT Additional Information For more detailed information about the Alert Monitor. These include report names. and individual key words of a programming language.

enter * as the transaction name (field TCODE) and specify the client (field MON_CLIENT). as we recommend. The system displays the screen Data Browser: Initial Screen. or. Enter the table name ALTRAMONI and choose Table Contents (Enter) ( ). Prerequisites You have at least SAP Basis 4. 6. To monitor all transactions in a particular client. be based on the response times in a client or on the response times of critical transactions. You can now use the Transaction-Specific Dialog Monitor to monitor the dialog response times of the specified clients and transactions. Save your entries.6C. The name is displayed in the monitoring tree that you define later in transaction RZ20. 2. The system displays the screen Data Browser: Table ALTRAMONI: Selection Screen. This simplifies selection by client or transaction in the monitor definition. Use the same MTE class name for clients or transactions that you want to display in the same monitor. 4. 5. or in a transaction in a client.SAP Online Help 08. 3. Always specify <CURRENT> as the SERVER-ID.07. To monitor a particular transaction in all clients.6B. use the following procedure to create your own monitor. enter the transaction code and * for the client name. Choose Create ( ) and enter the transaction and/or client to be monitored. As of SAP Basis 4. You can either use this monitor. Specify an MTE class (field MTECLASS). If you want to use your own monitor to display the data. for example. The service level agreement could. the Alert Monitor contains the Transaction-Specific Dialog Monitor in the SAP CCMS Monitors for Optional Components monitor set. a specific transaction.2002 Monitor Response Times of Selected Transactions or Clients Use You can use the Alert Monitor to monitor the response times in a specific client. Enter a meaningful name of your choice for the monitoring object (field MO_NAME). with which you can monitor the response times in specific clients or transactions. Choose Execute ( ) . with which service providers offer a contractual obligation to provide their customers with SAP functions within a certain response time. We recommend that you use the same name for the MTE class and the monitoring object. Call transaction SE16. follow the procedure below: Monitoring Response Times of Transactions or Clients 4 620 . Procedure Which client and/or which transaction is to be monitored? 1. Use this function to monitor a service level agreement.

Enter the SAP system to be monitored in the R3System field. 2. Choose the CCMS_GET_MTE_BY_CLASS rule and choose Continue. select the monitor set in which you want to create the monitor. Choose Continue and then choose Generate Monitor ( Monitoring Response Times of Transactions or Clients 5 620 . 5. Ensure that it is a set that you can modify ( ). Choose Create Node ( and choose Continue. In the Create Node window. ). 6. it contains: • • Reference nodes to the entries made in table ALTRAMONI Monitoring objects and performance attributes that display information for all clients and transactions selected for monitoring Name of an MTE class that you entered in the MTECLASS field in the ALTRAMONI table A monitor created with this class contains only the clients and transactions that you assigned to the corresponding MTE class in the table ALTRAMONI. 3. 7.SAP Online Help 08. The system displays the Edit Rule Node dialog screen. Call transaction RZ20 and choose Extras → Activate Maintenance Functions.2002 Creating a new monitor with the response times of the monitored transactions/clients 1. Enter one or both of the following MTE classes in the MTEClass field: Input ContextR3DialogFocus Meaning A monitor created with this class corresponds to the Transaction-Specific Dialog Monitor. ). Create a new monitor definition.07. To do this. 4. select the Rule Node radio button. and choose Monitor(set) → Create ( ).

C u r r e n t S t a t u s ( 20. green Selected performance attributes of the dialog system Features The monitor contains the following performance attributes: Attribute ResponseTime Description Average response time of the dialog service including the database processing time. green .2001 . graphical user interfaces and screen information from the database Average time for processing logical database requests (calls to the SAP database interface) Average time that the user waits at the frontend for his or her request to be processed (that is.08. green .2002 Transaction-Specific Dialog Monitor Use You can use this monitor to monitor the response times for individual transactions or clients.SAP Online Help 08. but not including the network transfer time or the frontend processing time Average wait time in the dispatcher wait queue (with a normal workload. there should always be free dialog work processes available. green . 17:08:45 ) Nod e Display Off Transaction-Specific Dialog Monitor CEN\Dialog_Host1_CEN_01 CEN\Dialog_Host2_CEN_01 CEN\Dialog_Host3_CEN_01 Client 000 Transaction RZ20 RZ21 ST03N ClientTransaction 003_VA01 CLIENT_000 MONITORING CUSTOMIZING SYSTEMLASTMONITOR SALES_ORDER_003 ResponseTime QueueTime Load+GenTime DBRequestTime xxx FrontendResonseTime >SALES ORDERS 003 >MONITORING >CUSTOMIZING >WORKLOADMONITOR >CLIENT_000 Name of the monitor Application servers with client-specific or transaction-specific monitoring Which clients are being monitored (with all transactions)? Which transactions are being monitored (in all clients)? Which transactions are being monitored in specific clients? Monitoing objects with the performance attributes of the monitored transactions/clients 718 msec 4 msec 35 msec 39 msec 997 msec . the wait time is then only a few milliseconds) Average load and generation time for source code.07. the ResponseTime with network transfer time and the frontend processing time) QueueTime Load+GenTime DBRequestTime FrontendResponseTime Monitoring Response Times of Transactions or Clients 6 620 . green .

follow the procedure below: 1. Start the Alert Monitor using transaction RZ20. Monitoring Response Times of Transactions or Clients 7 620 . see the documentation for the monitors Dialog Overview and Entire System. expand the SAP CCMS Monitors for Optional Components monitor set. 2. On the CCMS Monitor Sets. or call CCMS → Control/Monitoring → Alert Monitor. 3. Activities To start the monitor.SAP Online Help 08. Start the Transaction-Specific Dialog Monitor from the list of monitors by double clicking it.07.2002 For more information about the attributes of the dialog system with recommendations about what action you should take if performance needs to be improved.