Foglight for SAP NetWeaver. User Guide

Transcription

1 Foglight for SAP NetWeaver

2 Copyright Quest Software, Inc All rights reserved. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser s personal use without the written permission of Quest Software, Inc. If you have any questions regarding your potential use of this material, please contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA info@quest.com Please refer to our Web site for regional and international office information. Trademarks Quest, Quest Software, the Quest Software logo, Aelita, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, InTrust, IT Dad, JClass, JProbe, LeccoTech, LiveReorg, NBSpool, NetBase, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLab Tuner, SQLab Xpert, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, Toad, T.O.A.D., Tag and Follow, Vintela, Virtual DBA, and XRT are trademarks and registered trademarks of Quest Software, Inc. Other trademarks and registered trademarks used in this guide are property of their respective owners. Disclaimer The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. July 2007 Software Version - 2.6

3 Table of Contents iii Table of Contents Table of Contents...iii Preface...9 About This Guide...10 Using this Guide...10 Related Documentation...13 About Quest Software, Inc Contacting Customer Support...14 Installing Foglight for SAP NetWeaver v2.6 Cartridge...17 Installation and Configuration Overview...18 Planning your Installation...18 Installation Procedure...18 SAPServer Agent...23 About the SAPServer Agent...24 Using SAPServer Agent Startup Parameters...29 SAPserver ASP Configuration...29 Setting the Connection Details...29 Setting the SAPserver Data Management Parameters...31 Setting the SAPserver Data Retrieval Parameters...34 Setting SAPServer Parameters...37 Setting SAPServer Monitor Parameters...39 Creating a Monitored Transactions List...41 Editing or Deleting a Monitored Transactions List...43 Creating a Monitored Programs List...44 Editing or Deleting a Monitored Programs List...46 Creating a Monitored Users List...47 Editing or Deleting a Monitored Users List...49 Creating a Monitored System Log Messages List...50 Editing or Deleting a Monitored System Log Messages List...53

4 iv Foglight for SAP NetWeaver v2.6 SAPServer Agent Tables AgentMsgs Table SAPR3_Alert_Summary Table SAPR3_Application_Servers Table SAPR3_Background_Aborted_Jobs Table SAPR3_Background_LongRunning_Jobs Table SAPR3_Buffers Table SAPR3_DB_Load_By_Program Table SAPR3_DB_Load_By_Task_Type Table SAPR3_DB_Load_By_Transaction Table SAPR3_Dispatch_Queue Table SAPR3_Enqueue_Long_Lock_Detail Table SAPR3_Enqueue_Total_Locks Table SAPR3_Extended_Memory Table SAPR3_Heap_Memory Table SAPR3_Instance_Totals Table SAPR3_Long_Steps Table SAPR3_Paging_Area_Memory Table SAPR3_Process_CPU Table SAPR3_Process_Detail Table SAPR3_Process_Exception_Detail Table SAPR3_Process_Overview Table SAPR3_Process_Totals Table SAPR3_Roll_Area_Memory Table SAPR3_Server_RFC_Availability Table SAPR3_Special_Users Table SAPR3_System_Log Table SAPR3_Total_Users Table SAPR3_Workload_By_Program Table SAPR3_Workload_By_Task_Type Table SAPR3_Workload_By_Transaction Table SAPR3_Workload_Overview Table SAPServer Investigations Investigating Aborted Background Jobs Investigating Application Server Dialog Response Time... 92

5 Table of Contents v Investigating Application Server Total Response Time...92 Investigating Availability...92 Investigating Buffer and Directory Allocation...93 Investigating Buffer Hit Ratio and Swaps...93 Investigating Dispatchers...94 Investigating Enqueues...95 Investigating Long Running Background Jobs...95 Investigating Memory...95 Memory Allocation by Dialog Work Processes...96 Memory Allocation by Non-Dialog Work Processes...96 Investigating Program Workload...97 Investigating System Log...98 Investigating Task Type Workload...98 Investigating Total and Long Locks...99 Investigating Transaction Workload Investigating Work Process Status Investigating Work Processes Investigating Workload System-Level Tuning for Dialog Work Process Conditions System-Level Tuning for Update Work Process Conditions Investigating Workload Distribution SAPServer Views SAPServer_Dialog_Resp_Overview Graph SAPServer_Total_Resp_Overview Graph SAPServer_Availability Graph SAPServer_Availability_Process Graph SAPServer_Availability_Process_Details Table SAPServer_Background_Aborted_Jobs_Details Table SAPServer_Background_Long_Running_Jobs_Details Table SAPServer_Buffer_Allocation Graph SAPServer_Buffers Graph SAPServer_Directory_Allocation Graph SAPServer_Dispatch_Queue Graph SAPServer_Locks Graph SAPServer_Long_Locks_Details Table...116

6 vi Foglight for SAP NetWeaver v2.6 SAPServer_Memory_Extended Graph SAPServer_Memory_Heap Graph SAPServer_Memory_Page Graph SAPServer_Memory_Roll Graph SAPServer_Program_DBDetails Table SAPServer_Program_DBTime Graph SAPServer_Program_DBcalls Graph SAPServer_Program_Workload Graph SAPServer_Program_Workload_Details Table SAPServer_Special_Users_Details Table SAPServer_TaskType_DBcalls Graph SAPServer_TaskType_DBtime Graph SAPServer_TaskType_Workload Graph SAPServer_Trans_DBDetails Table SAPServer_Trans_DBcalls Graph SAPServer_Trans_DBtime Graph SAPServer_Trans_Workload Graph SAPServer_Trans_Workload_Details Table SAPServer_Users Graph SAPServer_Work_Process Graph SAPServer_Work_Process_Detail Table SAPServer_Work_Process_Exception_Detail Table SAPServer_Work_Process_Stopped Graph SAPServer Rules Aborted_Jobs Rule Availability_Connection Rule Availability_Process Rule Avg_Response_Time Rule Buf_Free_Dir_Entries Rule Buf_Free_Space Rule Buf_Hit_Ratio Rule Console Rule Dispatch_Req_Waiting Rule Extended_Memory_Use Rule Long_Enqueue_Locks Rule

7 Table of Contents vii Long_Running_Jobs Rule Long_Running_Process Rule Paging_Memory_Used Rule Process_Complete Rule Process_Stopped Rule Process_Utilization Rule Prog_Avg_Resp_Time Rule Roll_Memory_Used Rule SAP_Agent_Status Rule Tcode_Avg_Resp_Time Rule SAP Agent About the SAP Agent Using SAP R/3 Agent Startup Parameters Setting the Collection Rate Setting Purging Parameters Setting Collection Policies Parameters Setting SAP Parameters Setting SAP Monitor Parameters Creating a Monitored Transactions List Creating a Monitored Programs List Creating a Monitored Users List Creating a Monitored System Log Messages List SAP Investigations Investigating SAP R/3 Work Processes Investigating SAP R/3 Work Process Status Investigating SAP R/3 Dispatcher Investigating SAP R/3 Buffer Hit Ratio and Swaps Investigating SAP R/3 Buffer and Directory Allocation Investigating SAP R/3 Memory Investigating SAP R/3 Workload Investigating SAP R/3 Enqueues Investigating SAP R/3 Total and Long Locks Investigating SAP R/3 System Log Investigating SAP R/3 Availability...202

8 viii Foglight for SAP NetWeaver v2.6 Investigating SAP R/3 Workload Distribution Investigating SAP R/3 Task Type Workload Investigating SAP R/3 Transaction Workload Investigating SAP R/3 Program Workload Investigating Sessions and Users Using Cross-Host Views SAP Rules Availability Connection Rule Availability Process Rule Average Response Time Rule Buf Free Dir Entries Rule Buffer Free Space Rule Buffer Hit Ratio Rule Console Rule Dispatch Request Waiting Rule Extended Memory Used Rule Long Enqueue Locks Rule Long Running Process Rule Paging Memory Used Rule Process Complete Rule Process Stopped Rule Process Utilization Rule Program Average Response Time Rule Roll Memory Used Rule Tcode Average Resp Time Rule SAP Agent Tables SAPR3_Application_Servers Table SAPR3_Buffers Table SAPR3_DB_Load_By_Program Table SAPR3_DB_Load_By_Task_Type Table SAPR3_DB_Load_By_Transaction Table SAPR3_Dispatch_Queue Table SAPR3_Enqueue_Long_Lock_Detail Table SAPR3_Enqueue_Total_Locks Table SAPR3_Extended_Memory Table

9 Table of Contents ix SAPR3_Heap_Memory Table SAPR3_Instance_Totals Table SAPR3_Long_Steps Table SAPR3_Paging_Area_Memory Table SAPR3_Process_CPU Table SAPR3_Process_Detail Table SAPR3_Process_Exception_Detail Table SAPR3_Process_Overview Table SAPR3_Process_Totals Table SAPR3_Roll_Area_Memory Table SAPR3_Server_RFC_Availability Table SAPR3_Special_Users Table SAPR3_System_Log Table SAPR3_Total_Users Table SAPR3_Workload_By_Program Table SAPR3_Workload_By_Task_Type Table SAPR3_Workload_By_Transaction Table SAPR3_Workload_Overview Table Glossary...155

10 x Foglight for SAP NetWeaver v2.6

11 Preface Contents About This Guide Related Documentation About Quest Software, Inc.

12 10 Foglight for SAP NetWeaver v2.6 About This Guide This manual describes the steps required to install and configure the Foglight for SAP NetWeaver v2.6 Cartridge. For platform support information, and known issues, please see the Foglight for SAP NetWeaver v2.6 Cartridge Release Notes. The manual consists of the following sections: Preface - Provides overview of this Guide, conventions used, and the related documentation available. Chapter 1 - Installing Foglight for SAP NetWeaver v2.6 Cartridge: Provides an overview of the SAPServer agent installation and configuration processes. Chapter 2- SAPServer Agent: Provides an overview of the SAPServer agent, investigations, tables, views, and rules. Chapter 3- SAP Agent: Provides an overview of the SAP agent, investigations, tables, and rules. Using this Guide Who Should Read this Guide This manual is written for system administrators and other technical personnel responsible for installation, deployment, and administration of the Foglight for SAP NetWeaver v2.6 Cartridge.

13 Preface 11 Conventions Used in this Guide ELEMENT Courier New Font Bold Text Italic Text Bold Italic Text CONVENTION Source code, scripts Commands you enter Path names, files names, URLs, and programs Console output Indicates interface elements the user should select Provides additional comments about a procedure The names of other documents referenced in this manual Introduces a series of procedures Used to provide Best Practice information. A best practice details the recommended course of action for the best result. Used to highlight processes that should be performed with care. + Indicates keys on the keyboard are to be used together > Indicates you must select elements in exact sequence Path Variables Throughout this document, directory paths are referred to based on standard environment variables expected for the root location (for example, SAP_HOME is equivalent to the SAP directory). Typically, these are denoted in UNIX path structure

14 12 Foglight for SAP NetWeaver v2.6 using forward slashes / to separate directories. Note that the variable delimiters for UNIX ($) and Windows (% %) are omitted unless required for clarity. In all cases FGLHOME represents the Foglight Client installation directory on the monitored host. Assumptions This manual assumes that you have a sound understanding of your production environment, and of the architecture of your SAP application server environment. Some operations require SAP administrative and root/administrator access to configuration files and you should be comfortable editing configuration files for those components. You may need to use scripts to perform certain operations. This manual does not contain instructions for installing the Foglight Management Server or the Foglight Client; nor does it contain general information on how to use Foglight. Please refer to the Foglight Administration Guide, the Foglight Installation Guide, the Foglight Operations Console, and the Foglight Management Server online help for the appropriate version.

15 Preface 13 Related Documentation Two additional documents provide information related to the Foglight for SAP NetWeaver v2.6 Cartridge: Release Notes for this Cartridge version Online help for this Cartridge version

16 14 Foglight for SAP NetWeaver v2.6 About Quest Software, Inc. Quest Software, Inc. delivers innovative products that help organizations get more performance and productivity from their applications, databases and infrastructure. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 18,000 customers worldwide meet higher expectations for enterprise IT. Quest Application Advantage lets organizations deliver, manage and control complex application environments. Only Quest provides the deepest understanding of the application from end user to database. Quest Software can be found in offices around the globe and at Contacting Customer Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: Support Guide.pdf Please refer to our Web site for regional and international office information.

17 1 Installing Foglight for SAP NetWeaver v2.6 Cartridge Contents Installation and Configuration Overview

18 18 Foglight for SAP NetWeaver v2.6 Installation and Configuration Overview Planning your Installation Installation Procedure Planning your Installation A Foglight installation consists of three steps: Install the Foglight Management Server A Foglight Management Server functions as the data collection and administration server. Note See the Foglight v4.1 and v4.2 Installation Guide for installation details. Install a Foglight Client on a Monitored Host Foglight Client software runs on remote computers (monitored hosts). The Foglight Client contains monitoring programs called Foglight Agents that collect information about the monitored host at specified intervals and send the information to the Foglight Server. A Foglight Cartridge is a collection of agents. Install and Deploy the Foglight for SAP NetWeaver v2.6 Cartridge The Foglight for SAP NetWeaver Cartridge is installed on the Foglight Server and configured using the Foglight Operations Console. The Foglight Client must be installed on all target SAP server machines in order for the SAP Agents to monitor them. Installation Procedure The installation process is for a new installation of the Foglight for SAP NetWeaver v2.6 Cartridge or for an existing Foglight for SAP NetWeaver pre-v2.6 Cartridge. Installation Recommendations We recommend that you review the following notes prior to running the Cartridge installation. In addition, you should read the Release Notes that accompanied this Cartridge for any last-minute information that did not make it into this document. Please note that the following list is not a comprehensive installation guide. However, it provides sufficient information to get you started.

19 Chapter 1 19 Installing the Foglight for SAP NetWeaver v2.6 Cartridge Prerequisite: Before beginning the installation process for Foglight for SAP NetWeaver Cartridge v2.6, the Foglight Management Server and the Foglight Client must be patched to the v4.1.a, v4.1.2, v 4.1.3, v4.2.1a, v4.2.2 or v4.2.3 level. Note The installation of the Foglight Management Server patches and this Cartridge require that the Foglight Management Server is stopped and restarted. Please ensure this installation is scheduled for an appropriate time. If there are concerns about completing the following procedures see the Contacting Customer Support section. During the installation, the Foglight Agent Compare and Update Utility are invoked. For UNIX, this utility requires an X server, running locally, to enable the display of the dialog controls on your screen. You will need to ensure your DISPLAY variable is set appropriately (see your X-server software documentation). For UNIX installations, you must use a command shell that include job control capabilities, such as ksh or bash. The Foglight for SAP NetWeaver Cartridge installation performs the following operations on the Foglight Management Server: 1 Initially, the Foglight for SAP NetWeaver Cartridge installation will validate your Foglight Management environment. It will require your Foglight Management Server to be at the required level which in this case is Foglight Management Server v4.1.a, v4.1.2, v 4.1.3, v4.2.1a, v4.2.2 or v The next installation step will unzip the package into a temporary directory. Usually this directory is located in the following locations: Windows: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\WZSE0.TMP UNIX: /tmp/selfgzxxxxx 3 At various points during the installation process you will be prompted to either press Enter to continue, q to quit, s to skip, A for all, or choose a Yes (Y)/ No (N) option: Licensing Agreement (Enter/s) Start upgrade process (Enter) Give permission to Quest to perform the updates (Y) Foglight Server shutdown (Enter) Perform Cold backup (optional - Y/N) Migrating existing agent rules or views (optional - Y/N)

20 20 Foglight for SAP NetWeaver v2.6 Post successful Foglight Server update (Enter) Foglight Client update (Y/N) 4 The installation process will create a manifest to install the latest SAP files to the Foglight Server. 5 The process will check for any cloned agents. 6 It will then check for a proper graphical DISPLAY setting prior to proceeding with the installation process. 7 The install process will migrate the agent ASPs, Views, Rules and Registry. Note Pre-existing Foglight Registry values are not replaced automatically during the installation of a Cartridge. You will need to manually edit the existing value if you want to apply the new recommended Registry value. 8 The Foglight Management Server and all agents will be stopped to copy the updated files. 9 The Foglight Management Server will be restarted once all updated processes are completed. 10 The Foglight Agent Compare and Update Utility will be invoked if you select to migrate customized Views and Rules. This utility identifies each different Rule and View setting and allows you to choose whether to keep the installed version or overwrite it with the new default version. Instructions for this utility are in the Foglight Cartridge Compare and Update Utility Guide in Downloads & Updates on Quest Software s SupportLink Page (questsupportlink.quest.com). Click Finish once all Views and Rules are processed. 11 Monitored hosts (Foglight Clients) that are currently attached to the Foglight Management Server will be updated. Select A to update all Foglight Clients or select only those you want to update. Note Monitored Hosts should be updated to ensure that any SAP agents deployed on them monitor correctly. If you choose not to update all Monitored Hosts, or if a Monitored Host fails to update (for example a Monitored Host is not running), you can perform this update

21 Chapter 1 21 Installing the Foglight for SAP NetWeaver v2.6 Cartridge step once the Foglight Client is running. The following command needs to be executed from the Foglight Home on the Foglight Management Server: foglight sethoststate <hostname> 4 where <hostname> is the name of the Monitored Host to be updated and 4 is the value for update.

22 22 Foglight for SAP NetWeaver v2.6

23 2 SAPServer Agent Contents About the SAPServer Agent Using SAPServer Agent Startup Parameters SAPServer Agent Tables SAPServer Investigations SAPServer Views SAPServer Rules

24 24 Foglight for SAP NetWeaver v2.6 About the SAPServer Agent The Foglight SAPServer agent works with other Foglight agents to assess the state of all the components within an SAP R/3 or NetWeaver System. The SAPServer agent also collects data on availability and performance of SAPServer work processes, system log, dispatch queue, memory configuration, users, transactions, and tasks. It also monitors for exception conditions and collects exception detail. Note See the Appendix in the Foglight Installation and Administration Guide AND in the Release Notes for more information. Foglight provides a multidimensional view of R/3 or NetWeaver resource usage for capacity planning, problem determination, and trend analysis, both real-time and historical. This lets an administrator use Foglight drill down capabilities to analyze resource usage of the underlying components in context to determine the cause and effect of response time degradation. In addition, the SAP basis administrator can use the collection of exception detail to focus directly on a problem area without sifting through large amounts of unrelated data.

25 Chapter 2 25 SAPServer Agent ASPs Using SAPServer Agent Startup Parameters Investigations Investigating Aborted Background Jobs Investigating Application Server Dialog Response Time Investigating Application Server Total Response Time Investigating Availability Investigating Buffer and Directory Allocation Investigating Buffer Hit Ratio and Swaps Investigating Dispatchers Investigating Enqueues Investigating Long Running Background Jobs Investigating Program Workload Investigating System Log Investigating Task Type Workload Investigating Total and Long Locks Investigating Transaction Workload Investigating Work Process Status Investigating Work Processes Investigating Workload Investigating Workload Distribution Investigating Memory Views SAPServer_Availability Graph SAPServer_Availability_Process Graph SAPServer_Background_Aborted_Jobs_ Details Table SAPServer_Program_Workload Graph SAPServer_Program_Workload_Details Table SAPServer_Special_Users_Details Table

26 26 Foglight for SAP NetWeaver v2.6 SAPServer_Background_Long_Running_ Jobs_Details Table SAPServer_Buffer_Allocation Graph SAPServer_Buffers Graph SAPServer_Dialog_Resp_Overview Graph SAPServer_Directory_Allocation Graph SAPServer_Dispatch_Queue Graph SAPServer_Locks Graph SAPServer_Long_Locks_Details Table SAPServer_Memory_Extended Graph SAPServer_Memory_Heap Graph SAPServer_Memory_Page Graph SAPServer_Memory_Roll Graph SAPServer_Program_DBcalls Graph SAPServer_Program_DBDetails Table SAPServer_TaskType_DBcalls Graph SAPServer_TaskType_DBtime Graph SAPServer_TaskType_Workload Graph SAPServer_Total_Resp_Overview Graph SAPServer_Trans_DBcalls Graph SAPServer_Trans_DBDetails Table SAPServer_Trans_DBtime Graph SAPServer_Trans_Workload Graph SAPServer_Trans_Workload_Details Table SAPServer_Users Graph SAPServer_Work_Process Graph SAPServer_Work_Process_Detail Table SAPServer_Work_Process_Exception_ Detail Table SAPServer_Work_Process_Stopped Graph SAPServer_Program_DBTime Graph

27 Chapter 2 27 SAPServer Agent Rules Aborted_Jobs Rule Availability_Connection Rule Availability_Process Rule Avg_Response_Time Rule Buf_Free_Dir_Entries Rule Buf_Free_Space Rule Buf_Hit_Ratio Rule Console Rule Dispatch_Req_Waiting Rule Extended_Memory_Use Rule Long_Running_Jobs Rule Long_Running_Process Rule Paging_Memory_Used Rule Process_Complete Rule Process_Stopped Rule Process_Utilization Rule Prog_Avg_Resp_Time Rule Roll_Memory_Used Rule SAP_Agent_Status Rule Tcode_Avg_Resp_Time Rule Long_Enqueue_Locks Rule Tables AgentMsgs Table SAPR3_Alert_Summary Table SAPR3_Application_Servers Table SAPR3_Background_Aborted_Jobs Table SAPR3_Background_LongRunning_ Jobs Table SAPR3_Buffers Table SAPR3_DB_Load_By_Program Table SAPR3_DB_Load_By_Task_Type Table SAPR3_Paging_Area_Memory Table SAPR3_Process_CPU Table SAPR3_Process_Detail Table SAPR3_Process_Exception_Detail Table SAPR3_Process_Overview Table SAPR3_Process_Totals Table SAPR3_Roll_Area_Memory Table SAPR3_Server_RFC_Availability Table

28 28 Foglight for SAP NetWeaver v2.6 SAPR3_DB_Load_By_Transaction Table SAPR3_Dispatch_Queue Table SAPR3_Enqueue_Long_Lock_Detail Table SAPR3_Enqueue_Total_Locks Table SAPR3_Extended_Memory Table SAPR3_Heap_Memory Table SAPR3_Special_Users Table SAPR3_System_Log Table SAPR3_Total_Users Table SAPR3_Workload_By_Program Table SAPR3_Workload_By_Task_Type Table SAPR3_Workload_By_Transaction Table

29 Chapter 2 29 SAPServer Agent Using SAPServer Agent Startup Parameters The SAPServer agent comes with default startup parameters that dictate how the agent will perform. You can change these parameters to suit your system requirements. The parameters listed in the topics below are specific to the SAPServer agent. For information regarding common agent parameters, such as purging, see the About Agent Startup Parameters help topic in the Foglight Management Server online help. Topics Setting the Connection Details Setting the SAPserver Data Management Parameters Setting the SAPserver Data Retrieval Parameters Setting SAPServer Parameters Setting SAPServer Monitor Parameters SAPserver ASP Configuration The SAPServer agent is deployed and started automatically from a successfully configured SAPServer agent. The following steps assume that you have installed the Foglight Client on each of the machines running the SAP server that you want to monitor. For instructions on how to install the Foglight Client, see Installing Foglight on Monitored Hosts in the Foglight v4.x Installation Guide. Configuring the SAPServer agent requires the following steps: 1 The SAPServer agent must be deployed on the server running the SAP R/3 or NetWeaver Server. 2 The ASPs for SAPServer must be configured correctly for the agent to function properly. Setting the Connection Details Use the Connection Details tab in the SAPServer agent ASP Editor to configure the SAP Server connection parameters.

30 30 Foglight for SAP NetWeaver v2.6 To set up the Connection Details 1 Right-click the SAPServer agent icon and choose Edit, ASPs. 2 Select the Connections Details tab. 3 Enter the SAP Client ID in the SAP R/3 Client ID box. 4 Enter the SAP User name in the SAP R/3 CPIC/System User Name box. 5 In the SAP R/3 CPIC/System User Password box, enter the password associated with the User Name needed to access the SAP Server. 6 Enter the SAP System Name to be monitored in the SAP R/3 System Name box. 7 Enter the SAP System number in the SAP R/3 System Number box. 8 Enter the full path for the SAP Server Home Path in the SAP R3 Directory Path box. 9 Click OK to save the entry and close the Edit ASP window, or select another tab to define additional startup parameters.

31 Chapter 2 31 SAPServer Agent Setting the SAPserver Data Management Parameters Use the Data Management tab in the SAPServer agent ASP Editor to set the sample frequency and to specify when data is to be purged. Note The collection rate, or sample frequency, is the number of seconds between the end of a collection period and the start of the next. The sample frequency is controlled at the agent level for all the tables. Caution The sample frequency and availability sampling frequency should not be set to less than 60 seconds because of performance overhead. You can purge tables at the agent or table level. Table level purging is the preferred method. To set the Data Management parameters 1 Right-click the SAPServer agent icon and choose Edit, ASPs.

32 32 Foglight for SAP NetWeaver v2.6 2 Select the Data Management tab. 3 Enter the sample frequency in seconds in the Sample Frequency (seconds) box. The sample frequency is the rate at which the bulk of the metrics get collected. Note The default is 300 seconds. The minimum frequency limit is 60 seconds. Caution The sample frequency should not be set to less than 60 seconds because of performance overhead. 4 Enter the sampling frequency in seconds in the Availability Sample Frequency (seconds) box. Note This sample frequency affects the SAPR3_Server_RFC_Availability Table. The availability sampling frequency is the rate at which the agent will test for the SAP Server connectivity, up/down status, etc. Note The default value is 60 seconds. Caution The availability sampling frequency should not be set to less than 60 seconds because of performance overhead.

33 Chapter 2 33 SAPServer Agent 5 Click the Edit button to the right of the Purge Data After box to open the SAPServer Table Purge Days window. 6 Select the table for which you want to change the purge values. Note The default number of purge days is shown for each table.

34 34 Foglight for SAP NetWeaver v2.6 Click Edit. The Edit Purge Days window displays. From the Edit Purge Days window you can: a Select a table and click Edit to change the default purge rate for that specific table Warning! Do not add or delete tables in the SAPServer Table Purge Days window. Only existing tables should be modified. 7 Click OK to close the Edit SampleFreq window. 8 Click OK to close the SAPServer Table Purge Days box. 9 Click on the other tabs to continue with ASP configuration or click OK to save the entries and close the Edit ASP window. Setting the SAPserver Data Retrieval Parameters Use the Data Retrieval tab in the SAPServer agent ASP Editor to set the data retrieval parameters. Note All fields have a maximum limit of 100 with a default of 20. To set the Data Retrieval parameters 1 Right-click the SAPServer agent icon and choose Edit, ASPs.

35 Chapter 2 35 SAPServer Agent 2 Click the Data Retrieval tab. 3 Enter the number of top programs by database load to monitor in the Top DB Load by Programs box based on the following selection criteria in the drop down menu list: Time_Per_DB_Request (default) Time_Per_Change Time_Per_Direct_Read Time_Per_Sequential_Read Note The data for this defined ASP threshold value is written to the SAPR3_DB_Load_By_Program Table. 4 Enter the number of top transactions by database load to monitor in the Top DB Load by Transactions box based on the following selection criteria in the drop down menu list:

36 36 Foglight for SAP NetWeaver v2.6 Time_Per_DB_Request (default) Time_Per_Change Time_Per_Direct_Read Time_Per_Sequential_Read Note The data for this defined ASP threshold value is written to the SAPR3_DB_Load_By_Transaction Table. 5 Enter the number of top long lock details to monitor in the Top Long Lock Details box based on the start time, i.e., Longest Lock. Note The data for this defined ASP threshold value is written to the SAPR3_Enqueue_Long_Lock_Detail Table. 6 Enter the number of top long steps to monitor in the Top Long Steps box based on the response time. Note The data for this defined ASP threshold value is written to the SAPR3_Long_Steps Table. 7 Enter the number of top CPU processes to monitor in the Top Processes (CPU) box based on CPU time at the SAP application server level. Note The data for this defined ASP threshold value is written to the SAPR3_Process_CPU Table. 8 Enter the number of top detailed CPU processes to monitor in the Top Processes (Detailed) box based on CPU percent at the OS level. Note The data for this defined ASP threshold value is written to the SAPR3_Process_Detail Table. 9 Enter the number of top special users to monitor in the Top Special Users box based on the most current user activity. Note The data for this defined ASP threshold value is written to the SAPR3_Special_Users Table. 10 Enter the number of top system logs to monitor in the Top System Logs box based on the most current log activity. Note The data for this defined ASP threshold value is written to the SAPR3_System_Log Table. 11 Enter the number of top workload by programs to monitor in the Top Workload by Programs box based on the following selection criteria in the drop down menu list: Average_Response_Time (default) Average_CPU_time

37 Chapter 2 37 SAPServer Agent Average_Wait_Time Average_DB_Request_Time Note The data for this defined ASP threshold value is written to the SAPR3_Workload_By_Program Table. 12 Enter the number of top workload by transactions to monitor in the Top Workload by Transactions box based on the following selection criteria in the drop down menu list: Average_Response_Time (default) Average_CPU_time Average_Wait_Time Average_DB_Request_Time Note The data for this defined ASP threshold value is written to the SAPR3_Workload_By_Transaction Table. 13 Enter the number of top aborted background jobs on the SAP system in the Top Aborted Background Jobs box. Note The data for this defined ASP threshold value is written to the SAPR3_Background_Aborted_Jobs Table. 14 Enter the number of long running jobs which have been held longer than the userdefined threshold in the Top Long Running Background Jobs box. Note The data for this defined ASP threshold value is written to the SAPR3_Background_LongRunning_Jobs Table. 15 Click OK to save the entry and close the Edit ASP window, or select another tab to define additional startup parameters. Setting SAPServer Parameters Use the SAP Parameters tab in the SAPServer agent ASP Editor to set various time thresholds. To set SAP parameters 1 Right-click the SAPServer agent icon and choose Edit, ASPs.

38 38 Foglight for SAP NetWeaver v2.6 2 Click the SAP Parameters tab. 3 Enter the threshold (in milliseconds) at which the SAPServer agent writes the dialog step to the SAPR3_Long_Steps Table for the collection interval in the Dialog Step Response Time Threshold (Milliseconds) box. Note The default value is 2000 ms. 4 Enter the threshold (in minutes) at which the SAPServer agent writes an enqueue to the SAPR3_Enqueue_Long_Lock_Detail Table for the collection interval in the Enqueue Lock Threshold (Minutes) box. Note The default value is 30 minutes.

39 Chapter 2 39 SAPServer Agent 5 Enter the threshold (in seconds) at which the SAPServer agent writes a work process to the SAPR3_Process_Exception_Detail Table for the collection interval in the Work Process Execution Time Threshold (Seconds) box. Note The default value is 600 seconds. 6 Enter how often (in seconds) the SAPServer agent tries to connect to R/3 or NetWeaver via RFC in the SAP R/3 RFC Connection Time (Seconds) box. If the agent cannot connect after reaching this threshold, the R/3 or NetWeaver instance is unavailable. Note The default value is 30 seconds. 7 Enter the threshold (in minutes) at which the SAPServer agent writes a long running background job to the SAPR3_Background_LongRunning_Jobs Table for the collection interval in the Long Running Background Jobs Threshold box. Note The default is 30 minutes. 8 Click OK to save the entry and close the Edit ASP window, or select another tab to define additional startup parameters. Setting SAPServer Monitor Parameters Use the SAP Monitor tab to create and edit the Monitored Transactions List, Monitored Programs List, Monitored Users List, and Monitored System Log Messages List. To set SAP Monitor parameters 1 Right-click the SAPServer agent icon and choose Edit, ASPs.

40 40 Foglight for SAP NetWeaver v2.6 2 Click the SAP Monitor tab. 3 Perform any of the following tasks: Create or edit a monitored transaction list. Create or edit a monitored programs list. Create or edit a monitored users list. Create or edit a monitored system log messages list. 4 Click OK to save the entry and close the Edit ASP window, or select another tab to define additional startup parameters.

41 Chapter 2 41 SAPServer Agent Creating a Monitored Transactions List Use the SAPServer agent to monitor business critical or custom transactions independently with the default SAPR3TransactionsList. Note Any change made to the monitored transaction list is a global change; that is, it changes the monitored transactions for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the monitored transaction list a new name. The monitored transactions identified in this list will be written to the following tables: SAPR3_DB_Load_By_Transaction Table SAPR3_Workload_By_Transaction Table You can also edit or delete the monitored transaction entries from the list. To create a Monitored Transactions list 1 Right-click the SAPServer agent icon and choose Edit, ASPs.

42 42 Foglight for SAP NetWeaver v2.6 2 Click the SAP Monitor tab. 3 In the Monitored Transactions box, enter the name of the list to be created, or edit the default list. 4 Click Edit. The SAPR3_Monitored_Transactions window opens, showing a default list of transaction codes.

43 Chapter 2 43 SAPServer Agent 5 Click New. The Edit Transaction Code window opens. 6 In the Transaction Code box, enter a transaction code. Note The transaction name is not case sensitive, and you can use the wildcard character (*). The SAPServer agent provides Y* and Z* as default values. 7 Click Apply on the Edit Transaction Code window to save the entry and keep the window open to add another transaction code. or Click OK to save the updated entries and close the window. 8 Click OK to save the updated transaction entry and close the Edit ASP window, or select another tab to define additional startup parameters. Editing or Deleting a Monitored Transactions List The Monitored Transaction list contains the transaction code. Note The monitored transactions identified in this list will be written to the following tables: SAPR3_DB_Load_By_Transaction Table SAPR3_Workload_By_Transaction Table To edit a transaction code 1 Right-click the SAPServer agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored Transaction List and click Edit. 4 From the SAPR3_Monitored_Transactions window, click Edit. 5 In the Transaction_Code box, click Select to choose a previously entered Transaction_Code. Note 6 Click OK. The transaction name is not case sensitive, and you can use the wildcard character (*). The SAPServer agent provides Y* and Z* as default values.

44 44 Foglight for SAP NetWeaver v2.6 To delete a transaction code 1 In the SAPR3_Monitored_Transactions window, highlight the transaction code to be deleted. 2 Click Delete. 3 On the Confirm delete record window, click Yes. Creating a Monitored Programs List In an R/3 or NetWeaver environment, a custom program might not be associated with a Code. For example, a custom program might be executed directly from transactions se38, sa38, or report trees. Monitoring workload activity only at the task type or transaction level does not let you monitor resource usage of an individual custom program. For this reason, the SAP agent lets you monitor business critical or custom programs independently using a default list called the SAPServer Programs List. Note Any change made to the monitored programs list is a global change; that is, it changes the monitored programs for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the monitored programs list a new name. The monitored programs identified in this list will be written to the following tables: SAPR3_DB_Load_By_Program Table SAPR3_Workload_By_Program Table You can also edit or delete the monitored program from the list. To create a Monitored Programs list 1 Right-click the SAPServer agent and choose Edit, ASPs.

45 Chapter 2 45 SAPServer Agent 2 Click the SAP Monitor tab. 3 In the Monitored Programs box, enter the name of the list to be created, or edit the default list. 4 Click Edit. The SAPR3_Monitored_Programs window opens, showing a default list of programs.

46 46 Foglight for SAP NetWeaver v2.6 5 Click New. The Edit Monitored Programs window opens. 6 In the Program box, enter the name of the SAP program to be monitored. Note The program name is not case sensitive, and you can use the wildcard character (*). The SAPServer agent provides Y* and Z* as default values. 7 Click Apply on the Edit Monitored Programs window to save the entry and keep the window open to add another program entry. or Click OK to save the updated entries and close the window. 8 Click OK to save the updated program entry and close the Edit ASP window, or select another tab to define additional startup parameters. Editing or Deleting a Monitored Programs List The Monitored Program list contains the program name. Note The monitored programs identified in this list will be written to the following tables: SAPR3_DB_Load_By_Program Table SAPR3_Workload_By_Program Table To edit a program 1 Right-click the SAPServer agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored Program list and click Edit. 4 Highlight the program you wish to modify and click Edit. 5 In the Program box, click Select to choose a previously entered program. Note The program name is not case sensitive, and you can use the wildcard character (*). The SAPServer agent provides Y* and Z* as default values. 6 Click OK.

47 Chapter 2 47 SAPServer Agent To delete a program 1 On the SAPR3_Monitored_Programs window, highlight the program to be deleted. 2 Click Delete. 3 On the Confirm delete record window, click Yes. Creating a Monitored Users List The SAPServer agent lets you monitor the activity of a specific R/3 or NetWeaver user. It also contains a default list called the SAPServer Users List. Note Any change made to the Users List is a global change; that is, it changes the monitored users for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the users list a new name. The monitored users identified in this list will be written to the following tables: SAPR3_Special_Users Table You can also edit or delete the monitored user entries from the list. To create a Monitored Users list 1 Right-click the SAPServer agent icon and choose Edit, ASPs.

48 48 Foglight for SAP NetWeaver v2.6 2 Click the SAP Monitor tab. 3 In the SAPR3_Monitored_Users box, enter the name of the list to be created, or edit the default list. 4 Click Edit. The SAPR3_Monitored_Users window opens, showing a default list of users.

49 Chapter 2 49 SAPServer Agent 5 Click New. The Edit Monitored Users window opens. 6 In the User box, enter the name of the SAP user to be monitored. Note The user name is not case sensitive, and you can use the wildcard character (*). The SAPServer agent provides SAP* and DDIC as default values. 7 Click Apply on the Edit Monitored Users window to save the entry and keep the window open to add another user entry. or Click OK to save the updated entries and close the window. 8 Click OK to save the changes to the users list and close the Edit ASP window, or select another tab to define additional startup parameters. Editing or Deleting a Monitored Users List The Monitored Users list contains user names. Note The monitored users identified in this list will be written to the following tables: SAPR3_Special_Users Table To edit a user 1 Right-click the SAPServer agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored Users list and click Edit. 4 From the SAPR3_Monitored_Users window, click Edit. 5 In the User box, click Select to choose a previously entered user. Note The user name is not case sensitive, and you can use the wildcard character(*). The SAPServer agent provides SAP* and DDIC as default values. 6 Click OK. To delete a user 1 In the SAPR3_Monitored_Users window, highlight the user to be deleted.

50 50 Foglight for SAP NetWeaver v2.6 2 Click Delete. 3 On the Confirm delete record window, click Yes. Creating a Monitored System Log Messages List The basis administrator can use the SAPServer agent to monitor an R/3 or NetWeaver System by trapping critical system messages and generating an alert condition to the Foglight event log. The SAPServer agent R/3 or NetWeaver log filter comes with the default list SAPServer Messages List for monitoring the most critical events. Each message is filtered based on its message number. You can choose a severity level for each message and add a short text string to be displayed next to the error text provided by SAPServer. Note Any change made to the monitored system log messages list is a global change; that is, it changes the monitored system log messages for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the monitored system log messages list a new name. The monitored system log messages identified in this list will be written to the following table: SAPR3_System_Log Table You can also edit and delete the monitored system log message entries from the list. To create a Monitored System Log Messages list 1 Right-click the SAPServer agent and choose Edit, ASPs.

51 Chapter 2 51 SAPServer Agent 2 Click the SAP Monitor tab. 3 In the Monitored System Log Messages box, enter the name of the list to be created, or edit the default list.

52 52 Foglight for SAP NetWeaver v2.6 4 Click Edit. The SAPR3_Monitored_Messages window opens, showing a default list of message numbers. 5 Click New. The Edit Message window opens. 6 In the Message_Number box, enter the R/3 or NetWeaver log message number you want the SAPServer agent to trap. or Click Select to choose a previously entered Message_Number. 7 From the Severity drop-down, select the Foglight severity level associated with the SAPServer message number. The syslog message displays in the Foglight event log in one of the following colors:

53 Chapter 2 53 SAPServer Agent INFORMATIONAL (white) WARNING (yellow) CRITICAL (orange) FATAL (red) 8 In the Text box, enter the message text to be issued when the SAPServer agent encounters the R/3 or NetWeaver message number specified in the Message_Number box. or Click Select to choose a previously entered Text. 9 Click Apply on the Edit Message window to save the entry and keep the window open to add another message number. or Click OK to save the updates to the monitored messages list and close the window. 10 Click OK to save the changes to the messages list and close the Edit ASP window, or select another tab to define additional startup parameters. Editing or Deleting a Monitored System Log Messages List Message number, severity, and text display on the Monitored System Log Messages list. Note The monitored system log messages identified in this list will be written to the following tables: SAPR3_System_Log Table To edit a message number 1 Right-click the SAPServer agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored System Message list and click Edit. 4 Highlight the message you wish to modify and click Edit. 5 In the Message_Number box, click Select to choose a previously entered Message_Number.

54 54 Foglight for SAP NetWeaver v2.6 6 From the Severity drop-down, select the Foglight severity level associated with the SAPServer message number. The syslog message displays in the Foglight event log in one of the following colors: INFORMATIONAL (white) WARNING (yellow) CRITICAL (orange) FATAL (red) 7 In the Text box, enter the message text to be issued when the SAPServer agent encounters the R/3 or NetWeaver message number specified in the Message_Number box, or click Select to choose a previously entered Text. 8 Click OK to close the window. To delete a message number 1 In the SAPR3_Monitored_Messages window, highlight the message number to be deleted. 2 Click Delete. 3 On the Confirm delete record window, click Yes.

55 Chapter 2 55 SAPServer Agent SAPServer Agent Tables The SAPServer agent stores data in the following tables in the Foglight Database. Click the hyperlinks to view field descriptions. AgentMsgs Table SAPR3_Alert_Summary Table SAPR3_Application_Servers Table SAPR3_Background_Aborted_Jobs Table SAPR3_Background_LongRunning_ Jobs Table SAPR3_Buffers Table SAPR3_DB_Load_By_Program Table SAPR3_DB_Load_By_Task_Type Table SAPR3_DB_Load_By_Transaction Table SAPR3_Dispatch_Queue Table SAPR3_Enqueue_Long_Lock_Detail Table SAPR3_Enqueue_Total_Locks Table SAPR3_Extended_Memory Table SAPR3_Heap_Memory Table SAPR3_Paging_Area_Memory Table SAPR3_Process_CPU Table SAPR3_Process_Detail Table SAPR3_Process_Exception_Detail Table SAPR3_Process_Overview Table SAPR3_Process_Totals Table SAPR3_Roll_Area_Memory Table SAPR3_Server_RFC_Availability Table SAPR3_Special_Users Table SAPR3_System_Log Table SAPR3_Total_Users Table SAPR3_Workload_By_Program Table SAPR3_Workload_By_Task_Type Table SAPR3_Workload_By_Transaction Table

56 56 Foglight for SAP NetWeaver v2.6 AgentMsgs Table The following table describes the fields in the AgentMsgs table. Message Field Description The text provided by the agent describing the error condition. This text will be displayed in the agent error rule. MessageID Number of Identical Message for current collection cycle - helps to avoid messages storms. MessageID Severity Unique agent message id, each error would start with an agent prefix followed by a 3-digit number. For example, Oracle = ORA001, Sybase = SYB002, Weblogic6 = WLS6001. Each agent would be responsible for providing help text describing the possible error conditions to be associated with an agent error rule. Severity of the agent error condition i.e., Informational, Warning, Critical, Fatal The following are Common Agent Message Headers and Severities defined internally in the Agent Errors: Message ID Severity Message Text User Action SAP_SRV_501 Critical Version/DCMs mismatched. SAP_SRV_502 Critical Process ASPs: Failed to get call: There was a problem in the installation of the agent due to a mismatch between agent and DCM. Please call Technical Support. Verify ASP input.

57 Chapter 2 57 SAPServer Agent Message ID Severity Message Text User Action SAP_SRV_503 Critical For getting SAP system type SAP_SRV_504 Critical Process ASPs: getpwname failed to get UID for: SAP_SRV_505 Critical Failed to Logon to SAP RFC Interface on SAP_SRV_506 Critical Failed to connect to SAP RFC XMI Interface on SAP_SRV_507 Critical Failed to inspect startup log File: SAP_SRV_508 Critical Invalid SAP System Type [ SAP_SRV_509 Critical ] Check SAP System Name = [ 503 is bound to 502 Verify ASP input. Failure in the connection to SAP, verify the application server is up and the ASP input is correct. Failure in the connection to SAP, verify the application server is up and the ASP input is correct. Verify Log files exist and the permissions are set correctly. Failed to get SAP System type due to an incorrect System name or System number. 509 is bound to 508 & 510 SAP_SRV_510 Critical ] System Num = [ 510 is bound to 509 & 508

58 58 Foglight for SAP NetWeaver v2.6 Message ID Severity Message Text User Action SAP_SRV_511 Critical Invalid SAP Home Directory SAP_SRV_512 Warning Top DB Load by Program ASP value exceeds the maximum and will be reset SAP_SRV_513 Warning Top Long Steps ASP value exceed the maximum and will be reset SAP_SRV_514 Warning Top Long Lock Details ASP value exceed the maximum and will be reset SAP_SRV_515 Warning Top Long Steps ASP value exceed the maximum and will be reset SAP_SRV_516 Warning Top Processes (CPU) ASP value exceed the maximum and will be reset Verify SAP Home directory is defined in the ASPs. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support.

59 Chapter 2 59 SAPServer Agent Message ID Severity Message Text User Action SAP_SRV_517 Warning Top Processes (Detailed) ASP value exceed the maximum and will be reset SAP_SRV_518 Warning Top Special Users ASP value exceed the maximum and will be reset SAP_SRV_519 Warning Top System Logs ASP value exceed the maximum and will be reset SAP_SRV_520 Warning Top Workload by Programs ASP value exceed the maximum and will be reset SAP_SRV_521 Warning Top Workload by Transaction ASP value exceed the maximum and will be reset The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support.

60 60 Foglight for SAP NetWeaver v2.6 Message ID Severity Message Text User Action SAP_SRV_522 Warning Failed to Collect OS information SAP_SRV_523 Critical Failed to locate Sapstart binary, verify Sap Home Path and System name ASPs SAP_SRV_524 Critical Failed to connect to SAP RFC XBP Interface SAP_SRV_525 Warning Top Background Aborted Jobs asp value exceed the maximum and will be reset to SAP_SRV_526 Warning Top Background Long Running Jobs asp value exceed the maximum and will be reset to SAP_SRV_999 Fatal Failed to initialize icu adapter validate resource file. Verify Application server is up and running. Failed to identify the SAP Process. Incorrect ASPs verify them and restart the agent. Failure in the connection to SAP, verify the app serve r is up and the asps input is correct also verify User Permissions for XBP interface. The number of rows that return back for this table is limited for changing the ceiling value contact support. The number of rows that return back for this table is limited for changing the ceiling value contact support. Verify resource file was installed properly.

61 Chapter 2 61 SAPServer Agent SAPR3_Alert_Summary Table The following table describes the fields in the SAPR3_Alert_Summary table. Field Alert_Type Number Description Alert type so a specific rule can be activated. To clear the rule send 0 and display how many alerts were in a specific cycle. SAPR3_Application_Servers Table The following table describes the fields in the SAPR3_Application_Servers table. Field Availability Host_Name Server_Name System_Name Description The availability of the application server. The name of the application server host. The name of the application server. The name of the application server system. SAPR3_Background_Aborted_Jobs Table The following table describes the fields in the SAPR3_Background_Aborted_Jobs table. Field Description End_Date End_Time Executing_ Server_Name The job end date. The batch job end time. The server name.

62 62 Foglight for SAP NetWeaver v2.6 Initiator_Name Job_ Classification Job_ID Job_Name Number_Of_Pre decessor_jobs Number_Of_Suc cessor_jobs Periodic Field Server_Name Start_Date Start_Time Step_ID_ Number Target_System Work_Process_ ID Work_Process_ Number Description The user that scheduled the job/step. The job classification. A- High Priority B- Middle Priority C- Low Priority The job identification number. The background job name. The number of previous jobs. The number of successor job(s). The periodic jobs indicator ('X') (Yes/No). The server name. The job start date. The batch job start time. The job step ID number. The target system to run background job. The work process ID. The work process number.

63 Chapter 2 63 SAPServer Agent SAPR3_Background_LongRunning_Jobs Table The following table describes the fields in the SAPR3_Background_LongRunning_Jobs table. Field Description Executing_ Server_Name Initiator_Name Job_ Classification Job_ID Job_Name Job_Time Number_Of_ Predecessor_ Jobs Number_Of_ Successor_Jobs Periodic Server_Name Start_Date Start_Time Step_ID_ Number The server name. The user that scheduled the job/step. The job classification. A- High Priority B- Middle Priority C- Low Priority The job identification number. The background job name. The calculated job running time in seconds. The number of previous jobs. The number of successor job(s). The periodic jobs indicator ('X') (Yes/No). The server name. The job start date. The batch job start time. The job step ID number.

64 64 Foglight for SAP NetWeaver v2.6 Field Target_System Work_Process_ ID Work_Process_ Number Description The target system to run background job. The work process ID. The work process number. SAPR3_Buffers Table The following table describes the fields in the SAPR3_Buffers table. Field Allocated Buffer_Hit_ Ratio Buffer_Name Buffer_Swap Description The maximum amount of memory area that can be occupied by the respective buffer, as defined by the parameter limiting the buffer size. The percentage of data accesses that are satisfied by the buffer and do not require database accesses during the sampled period. R/3 or NetWeaver Buffer name and map of known names: "TTAB" -> "Table_Definition_Buffer" "FTAB" -> "Field_Description_Buffer" "SNTAB" -> "Short_Nametab_Buffer" "IRBD" -> "Initial_Record_Buffer" "TABLP" -> "Single_Record_Table_Buffer" "TABL" -> "Generic_Key_Table_Buffer" "PXA" -> "Program_Buffer" "CUA" -> "CUA_Buffer" "CALE" -> "Calendar_Buffer" "PRES" -> "Screen_Buffer" "EIBUF" -> "Export_Import_Buffer" The number of buffer objects displaced from the buffer.

65 Chapter 2 65 SAPServer Agent Field Database_ Accesses Directory_ Entries_Free_ Percent Directory_ Entries_Used Directory_Size_ Entries Free_Space_ Percent Space_Used Description The number of database accesses, which include the number of data transfers from the database into the buffer. The percentage difference between the current number of objects stored in the buffer and the maximum possible number of objects. The current number of objects stored in the buffer. The maximum number of objects that can be stored in the buffer. The percentage of currently unoccupied memory space in the respected buffer. The currently occupied memory space in the respective buffer. SAPR3_DB_Load_By_Program Table The following table describes the fields in the SAPR3_DB_Load_By_Program table. Field Number_ Changes Number_ Database_Calls Description The number of database changes per program during the sample period. The number of parsed requests sent to the database per program during the sample period.

66 66 Foglight for SAP NetWeaver v2.6 Field Number_ Database_ Requests Number_Direct _Reads Number_ Sequential_ Reads Program Time_Per_ Change Time_Per_DB_ Request Time_Per_ Direct_Read Time_Per_ Sequential_ Read The number of logical ABAP/4 requests for data in the database per program during the sample period. Note These requests are passed through the SAP DB interface and parsed into individuals database calls. The proportion of database calls to database requests is of interest. If access to information is buffered in the SAP buffers, database calls to the database server are not needed. Therefore, the ratio of calls/ requests gives an overall indication as to the efficiency of table buffering. A good ratio would be 1:10. The number of database direct reads per program during the sample period. The number of database sequential reads per program during the sample period. The program name. Description The time per change in milliseconds per program during the sample period. The time per database request in milliseconds per program during the sample period. The time per direct read in milliseconds per program during the sample period. The time per sequential read in milliseconds per program during the sample period.

67 Chapter 2 67 SAPServer Agent SAPR3_DB_Load_By_Task_Type Table The following table describes the fields in the SAPR3_DB_Load_By_Task_Type table. Field Number_ Changes Number_ Database_Calls Number_ Database_ Requests Number_Direct_ Reads Number_ Sequential_ Reads Task_Type Time_Per_ Change Time_Per_DB_ Request Time_Per_Direct _Read Description The number of database changes per task type during the sample period. The number of parsed requests sent to the database per task type during the sample period. The number of logical ABAP/4 requests for data in the database per task type during the sample period. Note These requests are passed through the SAP DB interface and parsed into individuals database calls. The proportion of database calls to database requests is of interest. If access to information is buffered in the SAP buffers, database calls to the database server are not needed. Therefore, the ratio of calls/ requests gives an overall indication as to the efficiency of table buffering. A good ratio would be 1:10. The number of database direct reads per task type during the sample period. The number of database sequential reads per task type during the sample period. Type of task can include total, dialog, background, update, RFC. The time per change in milliseconds per task type during the sample period. The time per database request in milliseconds per task type during the sample period. The time per direct read in milliseconds per task type during the sample period.

68 68 Foglight for SAP NetWeaver v2.6 Field Time_Per_ Sequential_Read Description The time per sequential read in milliseconds per task type during the sample period. SAPR3_DB_Load_By_Transaction Table The following table describes the fields in the SAPR3_DB_Load_By_Transaction table. Field Number_ Changes Number_ Database_Calls Number_ Database_Reque sts Number_Direct_ Reads Number_ Sequential_ Reads Time_Per_ Change Time_Per_DB _Request Time_Per_Direct _Read Time_Per_ Sequential_Read Description The number of database changes per transaction during the sample period. The number of parsed requests sent to the database per transaction during the sample period. The number of logical ABAP/4 requests for data in the database per transaction during the sample period. The number of database direct reads per transaction during the sample period. The number of database sequential reads per transaction during the sample period. The time per change in milliseconds per transaction during the sample period. The time per database request in milliseconds per transaction during the sample period. The time per direct read in milliseconds per transaction during the sample period. The time per sequential read in milliseconds per transaction during the sample period.

69 Chapter 2 69 SAPServer Agent Field Transaction_ Code Description The name of the monitored transaction. SAPR3_Dispatch_Queue Table The following table describes the fields in the SAPR3_Dispatch_Queue table. Field Request_Type Request_Waiting Maximum_Requ est_waiting Request_Written Request_Read Description The type of work process. A dispatcher queue exists for each work process type: DIA - dialog UPD - update ENQ - enqueue BTC - batch SPO - spool UP2 - update 2 The number of currently waiting user requests. The maximum number of user requests waiting at any one time since the R/3 or NetWeaver instance was started. The number of user requests received by the dispatcher. The number of user requests dispatched to a work process. SAPR3_Enqueue_Long_Lock_Detail Table This table will report detailed information about the local locks which are held in the system for longer than 30 minutes determined according to the field GTTIME in ENQ table (structure SEQG3). Subtract the time in the column GTTIME from the time when

70 70 Foglight for SAP NetWeaver v2.6 the monitor was called to provide the information. The following table describes the fields in the SAPR3_Enqueue_Long_Lock_Detail table. Field Backup_Flag_ for_lock_entry Client Counter_1 Counter_2 Lock_Argument Lock_Date Lock_Mode Lock_Time Object_Name Origin_Host Owner_1 Owner_2 System_Number Table_Name Transaction_ Code User_Name Description The backup flag for the lock entry. The SAP client. Cumulative counter for a lock entry. Cumulative counter of lock entry. The argument (key fields) of the lock entry. The date when the lock was set. Indicates if the lock is shared. If the lock object is shared, then more than one user at a time may lock the same data. The time when the lock was set. The name of the lock object in the lock entry. The host name of the application server where the lock was generated. The owner of the lock, ID of logical unit of work (LUW). The owner of the lock, ID of logical unit of work (LUW). The SAP system number for the monitored R/3 or NetWeaver instance. The name of the table in which rows are locked. The transaction holding the lock. The name of the SAP user holding the lock.

71 Chapter 2 71 SAPServer Agent Field WP_Number Description The number of the work process holding the lock. SAPR3_Enqueue_Total_Locks Table The following table describes the fields in the SAPR3_Enqueue_Total_Locks table. Field Local_Locks Local_Long Locks Long_Locks Description The number of local lock entries held by clients and users on a specific application server. The number of local long lock entries held by clients and users on a specific application server as defined by the thresholds set in the ASPs. The number of all lock entries held by clients and users across the entire landscape. The number of all long lock entries held by clients and users across the entire landscape as defined by the thresholds set in the ASPs. SAPR3_Extended_Memory Table The following table describes the fields in the SAPR3_Extended_Memory table. Field Currently_Used Currently_Used_ Percent Description The amount of memory currently in use in the respective memory area. The percent of Extended Memory currently used.

72 72 Foglight for SAP NetWeaver v2.6 Field In_Memory Maximum_Use Description The amount of main memory allocated to this area at system startup. The maximum amount of this memory area that has been used since the R/3 or NetWeaver instance was started. SAPR3_Heap_Memory Table The following table describes the fields in the SAPR3_Heap_Memory table. Field Currently_Use Maximum_Use Description The amount of memory currently in use in the respective memory area. The maximum amount of this memory area that has been used since the R/3 or NetWeaver instance was started, high-water mark. SAPR3_Instance_Totals Table The following table describes the fields in the SAPR3_Instance_Totals table. Field Application_ Server_Name Availability Description The configuration of the SAP instance. The name consists of the SAP system name (SID), the work process configuration, the SAP system number and server host name. The ability to connect to the monitored R/3 or NetWeaver instance via an RFC connection. A value of 100 means the connection was successful; a value of 0 means the connection was not successful.

73 Chapter 2 73 SAPServer Agent Field Instance_Name Percent_CPU Percent_ Memory System_Name System_Number Virtual_Set_Size The name of the SAP instance. The name consists of the server host name, the SAP system name (SID) and the SAP system number. The percent of CPU resources used for all the OS processes for the R/3 or NetWeaver instance. The percent of memory used for all the OS processes for the R/3 or NetWeaver instance. The SAP system name (SID). Description The SAP system number for the monitored R/3 or NetWeaver instance. The total size (KB) of the instance (memory and swap). SAPR3_Long_Steps Table The following table describes the fields in the SAPR3_Long_Steps table. Field Average_Roll_In _Time Average_Roll_ Out_Time Bytes_Requested Description Average processing time for roll ins in milliseconds per dialog step. Note Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per dialog step. Note Roll-out time is the amount of time required to roll out user context information from the work process to the roll buffer or roll file. The amount of kilobytes transferred within the system per dialog step during the interval.

74 74 Foglight for SAP NetWeaver v2.6 CPU_Time DB_Request_ Time Dispatch_Time End_Date End_Time Enqueue_Time Load_Time Number_Of_ Roll_Ins Number_Of_ Roll_Outs Program Response_Time Screen Field Description CPU time used in the work process in milliseconds per dialog step. The logical database request time required in milliseconds per dialog step. The time depends on the CPU capacity of the database server, network and buffering, and on the input/ output capabilities of the database server. The amount of time occupying a work process in milliseconds per dialog step. (Response time - wait time). The end date of the dialog step. The end time of the dialog step. The amount of time during which a work process sets an enqueue request in milliseconds per dialog step. The time needed to load and generate objects such as ABAP/4 source code and screen information from a database in milliseconds per dialog step. The number of rolled-in user contexts. The number of rolled-out user contexts. The program name executed for the dialog step. Response time is measured from the time a work process is instructed by the dispatcher to perform the execution to the time the result is returned to the SAPGUI in milliseconds per dialog step. The response time between the SAPGUI and the dispatcher is not included in this value. The screen number executed for the dialog step.

75 Chapter 2 75 SAPServer Agent Task_Type Transaction_ Code User Field Wait_Time Description The type of task for the dialog step can include dialog, background or update. The transaction code of the dialog step. The name of the user who executed the dialog step. The time an unprocessed dialog step waits in the dispatch queue for a free work process in milliseconds. A high server workload could produce higher wait times. SAPR3_Paging_Area_Memory Table The following table describes the fields in the SAPR3_Paging_Area_Memory table. Field Currently_Used Currently_Used_ Percent In_Memory Maximum_Use On_Disk Description The amount of Paging Area Memory currently used in kilobytes. The percent of Paging Area Memory currently used. The amount of memory allocated to Paging Area Memory in kilobytes. The maximum amount of Paging Area Memory that has been used since the R/3 or NetWeaver instance was started - high water mark in kilobytes. The size of the file (if any) in kilobytes that is part of this area and is located on the application server disk.

76 76 Foglight for SAP NetWeaver v2.6 SAPR3_Process_CPU Table The following table describes the fields in the SAPR3_Process_CPU table. Field Description CPU Number Process_ID Process_Type The amount of CPU utilized by the work process since R/3 or NetWeaver instance startup. The R/3 or NetWeaver work process number. The work process PID can trace PID changes and create a correlation to the SAPR3_Process_Exception_Detail Table. The work process type: Dialog, Batch, Enqueue, Update, Update 2, or Spool. SAPR3_Process_Detail Table The following table describes the fields in the SAPR3_Process_Detail table. Field Percent_CPU Percent_ Memory Process Process_ID Process_Unique Resident_Set_ Size Description The percent of CPU resources that this OS process used for the monitored R/3 or NetWeaver instance. The percent of memory that this OS process used for the monitored R/3 or NetWeaver instance. The name of the monitored R/3 or NetWeaver OS process. The process ID of this R/3 or NetWeaver OS process. The unique name of the monitored OS process. The name consists of the process ID and process name. The amount (KB) of the OS process that is in memory.

77 Chapter 2 77 SAPServer Agent Uptime Field Virtual_Set_Size Description The number of hours the R/3 or NetWeaver OS process has been running. The total size (KB) of the OS process (memory and swap). SAPR3_Process_Exception_Detail Table The following table describes the fields in the SAPR3_Process_Exception_Detail table. Field Accessed_Table CPU Current_Activity Errors Executing_User Execution_Time Number PID Process_Type Reason_For_ Wait Description The name of the table that was last accessed by the work process. The amount of CPU utilized by the work process since R/3 or NetWeaver instance startup. If a work process is in a running status, this is the current action being executed i.e. sequential read. The number of times that an error has occurred for the work process that may have terminated the work process. The SAP user executing the current dialog step. The amount processing time for the current request utilizing the work process. The R/3 or NetWeaver work process number. The R/3 or NetWeaver work process OS PID. The work process type: Dialog, Batch, Enqueue, Update, Update 2, and Spool. The reason for the wait time if a work process is in a Stopped status.

78 78 Foglight for SAP NetWeaver v2.6 Field Report_Running SAP_Client Semaphore Status Description The ABAP/4 program or report currently executing in the work process. The SAP client of the session currently executing. Indicates the semaphore number on which the work process is waiting. The status of the work process: Waiting, Running, and Stopped. SAPR3_Process_Overview Table The following table describes the fields in the SAPR3_Process_Overview table. Field Description CPIC The number of work processes by type where Status = Stopped and Reason = CPIC. Completed The number of work processes by type where Status = Complete. DB Action Load Long_Running PRIV The number of Dialog, Batch, Update or Update 2 work processes where Action = Direct Read, Sequential Read, Insert, Update, Delete, or Commit. The number of dialog work processes where Action = Load Report. The number of dialog work processes where the execution time has exceeded the ASP parameter Work Process Execution Time Threshold. The number of work processes by type where Status = Stopped and Reason = PRIV.

79 Chapter 2 79 SAPServer Agent Process_Type Roll Field Description The work process type: Dialog, Batch, Enqueue, Update, Update 2, or Spool. The number of dialog work processes where Action = Roll-in or Roll-out. Running The number of work processes by type where Status = Running. Stopped The number of work processes by type where Status = Stopped. Total Utilization The total number of work processes configured by type for the R/3 or NetWeaver instance. The percent of work processes being utilized by type: (running / total) * 100. SAPR3_Process_Totals Table The following table describes the fields in the SAPR3_Process_Totals table. Field Application_ Server_Name Percent_CPU Percent_Found Percent_ Memory Process Description The name of the SAP instance. The name consists of the server host name, the SAP system name (SID) and the SAP system number. The percent of CPU resources that all the OS processes of this type use for the monitored R/3 or NetWeaver instance. The percent of found OS processes of this type. The percent of memory that all the OS processes of this type use for the monitored R/3 or NetWeaver instance. The name of the monitored R/3 or NetWeaver OS process.

80 80 Foglight for SAP NetWeaver v2.6 Field Resident_Set_ Size Total_Processes_ Expected Total_Processes_ Found Virtual_Set_Size Description The amount (KB) of the OS process that is in memory. The number of OS processes of this type that are expected to be running, based on R/3 or NetWeaver instance profile. The actual number of OS processes of this type that were found to be running for the monitored R/3 or NetWeaver instance. The total size (KB) of the OS process (memory and swap). SAPR3_Roll_Area_Memory Table The following table describes the fields in the SAPR3_Roll_Area_Memory table. Field Currently_Used Currently_Used_ Percent In_Memory Maximum_Used On_Disk Description The amount of Roll Area Memory currently used in kilobytes. The percent of Roll Area Memory currently used. The amount of memory allocated to Roll Area Memory in kilobytes. The maximum amount of Roll Area Memory that has been used since the R/3 or NetWeaver instance was started - high water mark in kilobytes. The size of the file (if any) in kilobytes that is part of the area and is located on the application server disk.

81 Chapter 2 81 SAPServer Agent SAPR3_Server_RFC_Availability Table The following table describes the fields in the SAPR3_Server_RFC_Availability table. Field Host_Name Instance_Name RFC_ Availability System_Name System_Number Description The host name where the R/3 or NetWeaver instance is running. The name of the SAP instance. The name consists of the server host name, the SAP system name (SID) and the SAP system number. The ability to connect to the monitored R/3 or NetWeaver instance via an RFC connection. A value of 100 means the connection was successful; a value of 0 means the connection was not successful. The SAP system name (SID). The SAP system number for the monitored R/3 or NetWeaver instance. SAPR3_Special_Users Table The following table describes the fields in the SAPR3_Special_Users table. Field Description Client Last_Active_ Time Mbytes Name The SAP client number of the special user defined in the Setting the Connection Details ASP. The last active time for any session. The size of this connection. The name of the SAP special user defined in the ASPs.

82 82 Foglight for SAP NetWeaver v2.6 Field Sessions Terminal Transaction Type Description The number of active sessions in this connection. The terminal connected from. The transaction ID. The type of connection. SAPR3_System_Log Table The following table describes the fields in the SAPR3_System_Log table. Field Log_Time Message_ Number Program Severity Text User User_Message Description The time the log entry was written. The log message code associated with the type of log event. The name of the program. Foglight severity level associated with the R/3 or NetWeaver error generated to the Foglight event log. The value is defined in the ASP log filter parameter. The message text associated with the type of log event. The SAP user who caused the log entry. User message text associated with the R/3 or NetWeaver error generated to the Foglight event log. The value is defined in the ASP log filter parameter.

83 Chapter 2 83 SAPServer Agent SAPR3_Total_Users Table The following table describes the fields in the SAPR3_Total_Users table. Field Total_Sessions Total_Users Total number of user sessions. Description Total number of logged on users. SAPR3_Workload_By_Program Table The following table describes the fields in the SAPR3_Workload_By_Program table. Field Average_CPU_ Time Average_DB_ Request_Time Average_ Dispatch_Time Average_ Enqueue_Time Average_Load_ Time Description Average CPU time in milliseconds per program during the sampled period. CPU time for a dialog step is the amount of time a user request sits in the dispatcher queue until beginning of processing. Average database request time in milliseconds per program during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result. Average dispatch time in milliseconds per program during the sampled period. Dispatch time is the amount of time the request occupies a work process (response time - wait time). Average enqueue time in milliseconds per program during the sampled period. Enqueue time is the time during which a work process sets an enqueue request. Average load time in milliseconds per program during the sampled period. Load time is the amount of time required to load programs, CUA interface and screen information from the database.

84 84 Foglight for SAP NetWeaver v2.6 Field Average_ Response_Time Average_Roll_In _Time Average_Roll_ Out_Time Average_Wait_ Time Bytes_Requested Number_Dialog_ Steps Number_Of_ Roll_Ins Number_Of_ Roll_Outs Program Total_CPU_ Time Description Average response time in milliseconds per program during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average roll-in time in milliseconds per program during the sampled period. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per program during the sampled period. Roll-out time is the amount of time required to roll out user context information from the work process to the roll buffer or roll file. Average wait time in milliseconds per program during the sampled period. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing. The amount of kilobytes transferred within the system per program during the sampled period. The number of dialog steps executed per program during the sampled period The number of roll-ins per program during the sampled period. The number of roll-outs per program during the sampled period. The name of the monitored program. Total CPU time in seconds per program during the sampled period.

85 Chapter 2 85 SAPServer Agent Field Total_DB_ Request_Time Total_Response_ Time Total_Wait_ Time Description Total database request time in seconds per program during the sampled period. Total response time in seconds per program during the sampled period. Total wait time in seconds per program during the sampled period. SAPR3_Workload_By_Task_Type Table The following table describes the fields in the SAPR3_Workload_By_Task_Type table. Field Average_CPU_ Time Average_DB_ Request_Time Average_ Dispatch_Time Average_ Enqueue_Time Average_Load_ Time Description Average CPU time in milliseconds per task type during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average database request time in milliseconds per task type during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface until the database interface returns the result. Average dispatch time in milliseconds per task type during the sampled period. Dispatch time is the amount of time the request occupies a work process (response time - wait time). Average enqueue time in milliseconds per task type during the sampled period. Enqueue time is the time during which a work process sets an enqueue request. Average load time in milliseconds per task type during the sampled period. Load time is the amount of time required to load programs, CUA interface, and screen information from the database.

86 86 Foglight for SAP NetWeaver v2.6 Field Average_ Response_Time Average_Roll_In _Time Average_Roll_ Out_Time Average_Wait_ Time Bytes_Requested Number_Dialog_ Steps Number_Of_ Roll_Ins Number_Of _Roll_Outs Task_Type Total_CPU_ Time Description Average response time in milliseconds per task type during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average roll-in time in milliseconds per task type during the sampled period. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per task type during the sampled period. Roll-out time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average wait time in milliseconds per task type during the sampled period. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing. The amount of kilobytes transferred within the system per task type during the sampled period. The number of dialog steps executed per task type during the sampled period. The number of roll-ins per task type during the sampled period. The number of roll-outs per task type during the sampled period. The task type: Total, Dialog, Batch, Update, Spool, or RFC. Total CPU time in seconds per task type during the sampled period.

87 Chapter 2 87 SAPServer Agent Field Total_DB_ Request_Time Total_Response_ Time Total_Wait_ Time Description Total database request time in seconds per task type during the sampled period. Total response time in seconds per task type during the sampled period. Total wait time in seconds per task type during the sampled period. SAPR3_Workload_By_Transaction Table The following table describes the fields in the SAPR3_Workload_By_Transaction table. Field Average_CPU_ Time Average_DB_ Request_Time Average_ Dispatch_Time Average_ Enqueue_Time Average_Load_ Time Description Average CPU time in milliseconds per transaction during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average database request time in milliseconds per transaction during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result. Average dispatch time in milliseconds per transaction during the sampled period. Dispatch time is the amount of time the request occupies a work process (response time - wait time). Average enqueue time in milliseconds per transaction during the sampled period. Enqueue time is the time during which a work process sets an enqueue request. Average load time in milliseconds per transaction during the sampled period. Load time is the amount of time required to load programs, CUA interface, and screen information from the database.

88 88 Foglight for SAP NetWeaver v2.6 Field Average_ Response_Time Average_Roll_In _Time Average_Roll_ Out_Time Average_Wait_ Time Bytes_Requested Number_Dialog_ Steps Number_Of_ Roll_Ins Number_Of_ Roll_Outs Total_CPU_ Time Total_DB_ Request_Time Description Average response time in milliseconds per transaction during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average roll-in time in milliseconds per transaction during the sampled period. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per transaction during the sampled period. Roll-out time is the amount of time required to roll out user context information from the work process to the roll buffer or roll file. Average wait time in milliseconds per transaction during the sampled period. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing. The amount of kilobytes transferred within the system per transaction during the sampled period. The number of dialog steps executed per transaction during the sampled period. The number of roll-ins per transaction during the sampled period. The number of roll-outs per transaction during the sampled period. Total CPU time in seconds per transaction during the sampled period. Total database request time in seconds per transaction during the sampled period.

89 Chapter 2 89 SAPServer Agent Field Total_Response_ Time Total_Wait_ Time Transaction_ Code Description Total response time in seconds per transaction during the sampled period. Total wait time in seconds per transaction during the sampled period. The name of the monitored transaction. SAPR3_Workload_Overview Table The following table describes the fields in the SAPR3_Workload_Overview table. Field Average_CPU_ Time_Dialog Average_CPU_ Time_Total Average_DB_ Request_Time_D ialog Average_DB_ Request_Time_T otal Description Average CPU time in milliseconds for task type Dialog during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average CPU time in milliseconds for task type Total during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average database request time in milliseconds for task type Dialog during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result. Average database request time in milliseconds for task type Total during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result.

90 90 Foglight for SAP NetWeaver v2.6 Field Average_ Response_Time_ Dialog Average_ Response_Time_ Total Number_Dialog_ Steps_Dialog Number_Dialog_ Steps_Total WP_Utilization_ Dialog Description Average response time in milliseconds for task type Dialog during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average response time in milliseconds for task type Total during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. The number of dialog steps executed for task type Dialog during the sampled period. The number of dialog steps executed for task type Total during the sampled period. The percent of work processes being utilized for Dialog type (running / total) * 100.

91 Chapter 2 91 SAPServer Agent SAPServer Investigations Investigating Aborted Background Jobs Investigating Application Server Dialog Response Time Investigating Application Server Total Response Time Investigating Availability Investigating Buffer and Directory Allocation Investigating Buffer Hit Ratio and Swaps Investigating Dispatchers Investigating Enqueues Investigating Long Running Background Jobs Investigating Program Workload Investigating System Log Investigating Task Type Workload Investigating Total and Long Locks Investigating Transaction Workload Investigating Work Process Status Investigating Work Processes Investigating Workload Investigating Workload Distribution Investigating Memory Investigating Aborted Background Jobs Use the SAPServer_Background_Aborted_Jobs_Details Table view to investigate background processes that are running in the SAP system that have been aborted. Start with the SAPServer_Backround_Aborted_Jobs_Details table Use the SAPServer_Background_Aborted_Jobs_Details Table view to assess the different factors that have a negative influence on aborted background processes.

92 92 Foglight for SAP NetWeaver v2.6 Investigating Application Server Dialog Response Time Use the SAPServer_Dialog_Resp_Overview Graph view to analyze dialog response time, throughput, and work process usage levels per R/3 or NetWeaver application server. Start with the SAPServer_Dialog_Resp_Overview graph Use the SAPServer_Dialog_Resp_Overview Graph view to assess the different factors that have a negative influence on dialog response time and throughput. Drill down on the Avg. Response Time Dialog (ms) line to analyze the breakdown of dialog response time with the SAPServer_TaskType_Workload Graph view. Investigating Application Server Total Response Time The SAPServer_Total_Resp_Overview Graph provides a single display to analyze total response time, throughput, and user load for an application server. Start with the SAPServer_Total_Resp_Overview graph Use the SAPServer_Total_Resp_Overview Graph view to assess the different factors that negatively impact dialog response time, throughput, and user load. Drill down on the Avg. Response Time Total (ms) line to get an average of task time breakdown with the SAPServer_TaskType_Workload Graph view. Investigating Availability The SAPServer agent monitors R/3 or NetWeaver availability from two perspectives: the ability to connect to an R/3 or NetWeaver instance and the availability of R/3 or NetWeaver operating system processes. The SAPServer agent reads the R/3 or NetWeaver instance profile located in the /usr/sap/sid/sys/profile directory to determine the current work process configuration. The SAPServer agent also monitors availability for all R/3 or NetWeaver operating systems processes including: Collector and Sender Message Server Dispatcher Process Gateway Server Spool, Dialog, Update, Enqueue, and Batch Processes

93 Chapter 2 93 SAPServer Agent The SAPServer agent generates a process failure alert when the total number of operating system processes found does not match the number expected and generates a connection failure alert when the agent is not able to connect to an R/3 or NetWeaver instance via RFC. Start with the SAPServer_Availability or SAPServer_Availability_Process graph The SAPServer_Availability Graph view shows whether an RFC connection was made to the R/3 or NetWeaver instance or if the connection failed. The SAPServer_Availability_Process Graph shows the total processes expected, total processes found, and percent availability for each R/3 or NetWeaver operating system process type. Investigating Buffer and Directory Allocation The SAPServer agent alerts you when the percent of free space for a buffer or percent of free directory entries falls below the user-defined threshold. If an R/3 or NetWeaver buffer hit ratio is low or if a number of swaps have occurred, investigate the level of free space and free directory entries. If the directory for the buffer is full but the buffer has space available, the remaining space is not used. Also make sure the directory has free entries. Free directory entries are as important as having space in the buffer; otherwise, objects begin swapping and performance degrades. Note Increase the buffer size or the number of allowed entries by increments of 10%. Many R/3 or NetWeaver buffers are contained in shared memory pools. When the sizes of these buffers are changed, adjust the size of the corresponding pool. Before increasing the buffer size, ensure that the operating system has sufficient memory resources to avoid a memory bottleneck. Start with the SAPServer_Buffer_Allocation graph The SAPServer_Buffer_Allocation Graph view displays the buffer space allocated and used in kilobytes. Investigating Buffer Hit Ratio and Swaps The SAPServer agent alerts you when the hit ratio for a buffer falls below the userdefined threshold. Configuring a buffer without enough space to store an object requires

94 94 Foglight for SAP NetWeaver v2.6 increased buffer reloading and unnecessary database accesses to make the necessary space available. Buffer configurations that are too large waste memory and cause OS paging, which results in memory bottlenecks. Swaps should not occur in the buffers of a production system. If this happens, increase the buffer size or maximum number of entries. The exception is the Program buffer, where some swaps are unavoidable. Note Hit ratios less than 95% are acceptable for the Program buffer and the Single Key buffer. The Single Key buffer quality increases very slowly from system startup. Therefore, investigate hit ratios of less than 90% only if the buffer has no free space left. Start with the SAPServer_Buffers graph The SAPServer_Buffers Graph view displays the efficiency of R/3 or NetWeaver buffers, amount of swapping activity, and percent of free directory entries. Drill down on the Number of Buffer Swaps bar for a specific R/3 or NetWeaver buffer to investigate the buffer space allocation for an individual buffer with the SAPServer_Buffer_Allocation Graph view. Drill down on the Directory Free Percent (%) bar for a specific R/3 or NetWeaver buffer to investigate the directory allocation for an individual buffer with the SAPServer_Directory_Allocation Graph view. Investigating Dispatchers The SAPServer agent alerts you when a dispatcher queue length exceeds a user-defined threshold. Monitoring the length of the dispatcher queue provides an early warning of problems with load distribution or work processes in a Stopped status. Another possible cause for a long dispatcher queue is one or more long running dialog steps. In this case, you might need to perform database or program analysis, move to batch mode, or execute at non-peak processing times. Note See Investigating Work Processes for information about identifying and resolving problem work processes. Start with the SAPServer_Dispatch_Queue graph The SAPServer_Dispatch_Queue Graph view displays the number of requests and maximum requests waiting for each dispatcher type. The values are derived from the

95 Chapter 2 95 SAPServer Agent Max. Request Waiting and Request Waiting fields in the SAPR3_Dispatch_Queue Table. Investigating Enqueues An R/3 or NetWeaver enqueue work process administers enqueues in the table that is buffered in the R/3 or NetWeaver main memory. A local file exists on an enqueue server to retain enqueues even when an R/3 or NetWeaver instance is shut down. To set an enqueue, an ABAP program must explicitly call the enqueue module. To remove the enqueue, the same ABAP program explicitly calls the dequeue module. This lets the enqueue remain in place through several steps of a R/3 or NetWeaver transaction. At the completion of the transaction, all enqueues are automatically removed. Monitoring enqueues is one of the system administrator's regular duties. An enqueue that lasts for an extended period of time (more than 30 minutes) might indicate either incorrect programming or incorrect use of the program. Unreleased locks can block other users from working in the same transactions for updating information. When programs use too many enqueues, the enqueue table in main memory can become full, preventing new enqueues from being set and bringing your system to a standstill. See Investigating Total and Long Locks for more information. Investigating Long Running Background Jobs Use the Long_Running_Jobs Rule to identify that one or more long running background jobs have been identified within the last collection interval, based on Long Running Background Jobs Threshold set in the Setting SAPServer Parameters ASP tab. Start with the SAPServer_Background_Long_Running_Jobs_Details table Use the SAPServer_Background_Long_Running_Jobs_Details Tableview to assess the different factors that have a negative influence on long running background processes. Investigating Memory The memory management system allocates storage to user contexts from four different types of storage: Roll area storage Extended memory

96 96 Foglight for SAP NetWeaver v2.6 Process-local storage (heap) Page area memory The order in which storage is allocated to a user context from these storage types depends upon the release of R/3 or NetWeaver, version of the operating system, and whether the user context is running in an R/3 or NetWeaver Dialog or non-dialog work process. Topics Memory Allocation by Dialog Work Processes Memory Allocation by Non-Dialog Work Processes Memory Allocation by Dialog Work Processes Dialog work processes allocate memory in the following order: From the roll area up to profile parameter ztta/roll_first. Up to profile parameter ztta/roll_extension or until em/initial_size is full, whichever comes first, if additional memory is required. From the remaining roll area ztta/roll_area - ztta/roll_first if the user context needs more memory. Up to abap/heap_area_dia or abap/heap_area_total. R/3 or NetWeaver application servers are significant users of swap space. Depletion of swap space in a host system can cause serious system problems. For this reason, use the Foglight Management Server agent to monitor swap space usage. Memory Allocation by Non-Dialog Work Processes Non-Dialog work processes allocate memory in the following manner: From the roll area up to ztta/roll_area.

97 Chapter 2 97 SAPServer Agent Up to abap/heap_area_nondia or abap/heap_area_total if additional memory is required. Up to ztta/roll_extension or until em/initial_size is full, whichever comes first, if no more process-local storage can be allocated. R/3 or NetWeaver application servers are significant users of swap space. Depletion of swap space in a host system can cause serious system problems. For this reason, use the Foglight Management Server agent to monitor swap space usage. Investigating Program Workload The SAPServer agent alerts you when the average response time for a program exceeds the user-defined threshold. In an R/3 or NetWeaver environment, custom programs may not be associated with a Tcode. For example, custom programs may be executed directly from transactions se38, sa38, or report trees. Monitoring workload activity only at the task type or transaction level does not let you monitor resource usage of an individual custom program. For this reason, the SAPServer agent provides response time breakdown by monitored program. Because you can specify a business critical or custom program using wild card substitution, you can monitor programs in Z* and Y* customer name space independently. In this manner, custom-developed programs are subject to proper quality assurance procedures, and you can track response time over the performance of the entire system. Start with the SAPServer_Program_Workload graph The SAPServer_Program_Workload Graph displays the average response time, average CPU time, average DB Request time, average Wait time, and average Load time in milliseconds and number of dialog steps per monitored program. Drill down on the Avg. Response Time (ms) bar for a program to get a DB Response Time breakdown with the SAPServer_Program_Workload_Details Table view. Drill down on the Avg. Wait Time (ms) bar for a program to analyze work process usage with the SAPServer_Work_Process Graph view. Drill down on the Avg. Load Time (ms) bar for a program to investigate R/3 or NetWeaver Buffer usage with the SAPServer_Buffers Graph view. Drill down on the Avg. DB Request Time (ms) bar for a program to get a DB Request Time breakdown with the SAPServer_Program_DBcalls Graph view.

98 98 Foglight for SAP NetWeaver v2.6 From the SAPServer_Program_DBcalls Graph view, drill down on the Number Database Calls bar to investigate database time with the SAPServer_Program_DBTime Graph view. From the SAPServer_Program_DBcalls Graph view, drill down on the Number Database Requests bar for a program to investigate database requests with the SAPServer_Program_DBDetails Table view. Investigating System Log All R/3 or NetWeaver instances use system logs to list events or problems that occurred during system operation. In a distributed environment, each application server registers a local log while the central log can be configured to collect all the local logs from all the application servers. The local log files are updated continuously, while a short delay always occurs in the update of the central log. Basis administrators must check R/3 or NetWeaver System logs regularly for systemrelated problems, ABAP short dumps, and problems with system startup or shutdown. They periodically perform a string search for problems related to ORA, PAG, and ROL. The basis administrator can use the SAPServer agent to trap critical R/3 or NetWeaver system messages and generate alert conditions to the SAP map. This provides a single point of control for monitoring and managing heterogeneous enterprise applications that include multiple R/3 or NetWeaver Systems. The SAPServer agent R/3 or NetWeaver log filter comes with a default configuration for monitoring the most critical events. Each message is filtered based on its message number. You can choose a severity level for each message and add a short text string to be displayed next to the error text provided by SAP. See Setting SAPServer Monitor Parameters to update the log filter. If the agent detects a system log event, it writes the system log information to the SAPR3_System_Log Table for historical analysis. Investigating Task Type Workload The SAPServer agent alerts you when the average response time for a task type exceeds the user-defined threshold. The agent provides response time breakdown by task type. If a Dialog step exceeds the user-defined response time threshold during the collection interval, Dialog step details are written to the SAPR3_Long_Steps Table for historical analysis of the dialog steps exception detail.

99 Chapter 2 99 SAPServer Agent Start with the SAPServer_TaskType_Workload graph The SAPServer_TaskType_Workload Graph view displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per task type. Drill down on the Avg. Wait Time (ms) bar for a task type to analyze work process utilization with the SAPServer_Work_Process Graph view. Drill down on the Avg. Load Time (ms) bar for a task type to investigate R/3 or NetWeaver Buffer utilization with the SAPServer_Buffers Graph view. Drill down on the Avg. DB Request Time (ms) bar for a task type to get a DB Request Time breakdown with the SAPServer_TaskType_DBcalls Graph view. From the SAPServer_TaskType_DBcalls Graph view, drill down on the Number Database Calls bar to investigate database time. The SAPServer_TaskType_DBtime Graph view opens. Use the Data Browser to analyze further task type details including task type load with the SAPR3_Workload_By_Task_Type Table. Investigating Total and Long Locks The SAPServer agent monitors the volume of enqueues and alerts you when an enqueue is held longer than the user-defined threshold identified in the Setting SAPServer Parameters ASP. Note The default setting for the Enqueue Lock Threshold setting is 30 minutes. Start with the SAPServer_Locks graph The SAPServer_Locks Graph view displays the total number of locks and the number of long locks that occurred during the collection interval locally and across the entire landscape. Drill down on the Local Long Locks line to see a breakdown of the local enqueue locks details which have been held longer than the user-defined threshold with the SAPServer_Long_Locks_Details Table view.

100 100 Foglight for SAP NetWeaver v2.6 Investigating Transaction Workload The SAPServer agent provides response time breakdown by monitored transaction. You can monitor a business critical or custom transaction independently. The SAPServer agent alerts you when the average response time for a transaction exceeds the userdefined threshold. Start with the SAPServer_Trans_Workload graph The SAPServer_Trans_Workload Graph view displays, in milliseconds, the average response time, average CPU time, average DB request time, average wait time, and average load time. It also displays the number of dialog steps per transaction. Drill down on the Avg. Response Time (ms) bar for a transaction to get an average response time breakdown with the SAPServer_Trans_Workload_Details Table view. Drill down on the Avg. Wait Time (ms) bar for a transaction to analyze work process utilization with the SAPServer_Work_Process Graph view. Drill down on the Avg. Load Time (ms) bar for a transaction to investigate R/3 or NetWeaver Buffer utilization with the SAPServer_Buffers Graph view. Drill down on the Avg. DB Request Time (ms) bar for a transaction to get a DB Request Time breakdown with the SAPServer_Trans_DBcalls Graph view. From the SAPServer_Trans_DBcalls Graph view, drill down on the Number Database Calls bar to investigate database time. The SAPServer_Trans_DBtime Graph view opens. From the SAPServer_Trans_DBcalls Graph view, drill down on the Number Database Requests for a transaction to investigate number of database requests details with the SAPServer_Trans_DBDetails Table view. Investigating Work Process Status Always identify when and why a work process is in a Stopped or Complete status. A single defective work process can negatively impact other work processes and cause a chain reaction. The SAPServer agent alerts you when a certain percentage of work processes enters Stopped or Complete status or when a work process exceeds your defined execution time threshold. Foglight collects detailed information for the problem work process. For example, an alert for a stopped work process with a reason of PRIV typically indicates a problem with R/3 or NetWeaver memory. In this case, use the

101 Chapter SAPServer Agent SAPServer_Work_Process_Exception_Detail Table view to analyze work process detail data and the SAPServer agent R/3 or NetWeaver memory views to analyze R/3 or NetWeaver memory usage. See Investigating Memory for more information on analyzing memory usage. Start with the SAPServer_Work_Process graph The SAPServer_Work_Process Graph view displays the total number of work processes, the number of running work processes, and the number of work process load and exception conditions such as stopped work processes or long running dialog steps for each work process type. Drill down on the Running or Long Running bars to investigate running work processes with the SAPServer_Work_Process_Detail Table view. From the SAPServer_Work_Process_Detail Table view, drill down on the CPIC, PRIV, Stopped or Completed column to investigate these work processes. The SAPServer_Work_Process_Exception_Detail Table view opens. Drill down on the Stopped bar to investigate the reason for a stopped work process with the SAPServer_Work_Process_Stopped Graph view. From the SAPServer_Work_Process_Stopped Graph view, drill down on the Total Stopped bar for a specific stopped work process to investigate detailed process type information with the SAPServer_Work_Process_Exception_Detail Table view. Investigating Work Processes Review the usage and state of your work processes to gain a high-level view of your R/ 3 or NetWeaver System performance. Use the SAPServer_Work_Process Graph view to view work process usage by type and identify instances with too few or too many processes. For example, if an R/3 or NetWeaver instance has 20 dialog work processes but only 50% of them are used after the system completes several normal business cycles, eliminate the unused work processes to save memory. Often a key indication of a performance problem is when all the work processes of a particular type, such as Dialog or Update, are occupied. The SAPServer agent alerts you when the percent usage of Dialog or Update work processes exceeds the userdefined threshold. Note Before increasing the number of work processes for an R/3 or NetWeaver instance, use the FGLServerMonitor agent to check that the system has enough CPU and memory

102 102 Foglight for SAP NetWeaver v2.6 resources. If CPU usage is consistently at or above 80%, increasing the number of work processes might actually decrease performance. Investigating Workload R/3 or NetWeaver System workload statistics provide reliable data for analysis of application throughput, load, and response times. Use this data to identify the application components causing response time problems and reveal the workload distribution of your applications. Always begin a detailed application analysis with a workload analysis. To perform a workload analysis, first establish a baseline of application behavior. As the workload mix changes during the day, week, month, so do the bottlenecks. Determine whether the average response time increases certain times of the day when the load increases or response time is high even when the load is low. If the latter is true, the performance problem is load-independent. Compare the average response time to operating system resource usage for the same time period to determine whether an increase in response time correlates with a large CPU load or high paging rates. Many different factors negatively impact response time and throughput. High CPU load or paging rates can result in high load times, processing times, or database times. For dialog tasks, database time greater than 400ms and direct read time greater than 2ms or sequential read time greater than 10ms might indicate a database problem. Improper R/3 or NetWeaver memory configuration can cause increased load times and roll in or roll out times. Work process long execution times or too few work processes configured can create large wait times. These performance factors can cause poor response times and unsatisfactory throughput in a single transaction or all transactions. Topics System-Level Tuning for Dialog Work Process Conditions System-Level Tuning for Update Work Process Conditions System-Level Tuning for Dialog Work Process Conditions Consider system-level tuning or more detailed investigation when the following conditions exist for Dialog work processes: Average response greater than 1000ms Time per database request greater than 5ms

103 Chapter SAPServer Agent Average CPU time greater than 40% of response time Average database request time greater than 40% of response time or greater than 400ms Average wait time greater than 50ms Average load time greater than 50ms Direct reads greater than 2ms Sequential reads greater than 10msChanges and commits greater than 25ms Changes and commits greater than 25ms Response time for main menu greater than 100ms Average roll in, roll out time greater than 20ms System-Level Tuning for Update Work Process Conditions Consider system-level tuning or more detailed investigation when the following conditions exist for Update work processes: Average response time greater than 500ms Average database request time greater than 10% of request time Average wait time greater than 100ms Direct reads greater than 10ms Sequential reads greater than 15ms Changes and commits greater than 40ms Average load time greater than 50ms Investigating Workload Distribution Use the SAP agent to analyze resource usage and throughput across R/3 or NetWeaver instances to determine whether the R/3 or NetWeaver System workload is optimally distributed. To optimize performance, distribute the load across the CPU resources of all

104 104 Foglight for SAP NetWeaver v2.6 available servers. Use the View Editor to identify non-optimal load distribution by comparing the CPU and memory resources used, response times, work process usage, and user levels across your R/3 or NetWeaver application servers. Use the SAPServer_Dialog_Resp_Overview Graph view or the SAPServer_Total_Resp_Overview Graph view to analyze response time, throughput, and user load and work process usage levels on a SAPServer application server. Topics Investigating Application Server Dialog Response Time Investigating Application Server Total Response Time

105 Chapter SAPServer Agent SAPServer Views SAPServer_Dialog_Resp_Overview Graph Use the SAPServer_Dialog_Resp_Overview graph to assess the different factors that have a negative influence on dialog response time and throughput. The values are derived from the following fields in the SAPR3_Workload_Overview Table: Avg. CPU Time Dialog (ms) Avg. DB Request Time Dialog (ms) Avg. Response Time Dialog (ms) WP Utilization Dialog (%) To open the Dialog_Resp_Overview graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Dialog_Resp_Overview graph icon. To continue your investigation Drill down on the Avg. Response Time Dialog (ms) line to analyze the breakdown of dialog response time with the SAPServer_TaskType_Workload Graph view.

106 106 Foglight for SAP NetWeaver v2.6 SAPServer_Total_Resp_Overview Graph Use the SAPServer_Total_Resp_Overview graph to assess the different factors negative impacting Dialog response time and throughput. The values are derived from the following fields in the SAPR3_Workload_Overview Table: Avg. CPU Time Total (ms) Avg. DB Request Time Total (ms) Avg. Response Time Total (ms) Number Dialog Steps Total as well as the Number Total Users field in the SAPR3_Total_Users Table. To open the Total_Resp_Overview graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Total_Resp_Overview graph icon. To continue your investigation Drill down on the Avg. Response Time Total (ms) line to get a average task time breakdown with the SAPServer_TaskType_Workload Graph view.

107 Chapter SAPServer Agent SAPServer_Availability Graph The SAPServer_Availability graph displays 100 if an RFC connection was made to the R/3 or NetWeaver instance or 0 if the connection failed. The values are derived from the following fields in the SAPR3_Application_Servers Table: Connection Availability To open the Availability graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Availability graph icon. SAPServer_Availability_Process Graph The SAPServer_Availability_Process graph displays the total processes expected, total processes found, and percent availability for each R/3 or NetWeaver operating system process type. The values are derived from the following fields in the SAPR3_Process_Totals Table: Number Processes Expected

108 108 Foglight for SAP NetWeaver v2.6 Number Processes Found Percent Found (%) To open the Availability_Process graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Availability_Process graph icon To continue your investigation Drill down on the Number Processes Found bar to investigate the number of work processes details with the SAPServer_Availability_Process_Details Table view. SAPServer_Availability_Process_Details Table The SAPServer_Availability_Process_Details table displays the total processes details. The values are derived from the following fields in the SAPR3_Process_Detail Table: Process Process ID CPU (%) Memory (%) Resident Set Size Virtual Set Size

109 Chapter SAPServer Agent Uptime To open the Availability_Process_Details table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Availability_Process_Details table icon. SAPServer_Background_Aborted_Jobs_Details Table The SAPServer_Background_Aborted_Jobs_Details table provides details of the top aborted background jobs that have been identified on the SAP system during the last collection interval. Note By default, this table collects the top 20 aborted jobs. This parameter can be modified in the Data Retrieval ASP tab for the Top Aborted Background Jobs field. The values are derived from the following fields in the SAPR3_Background_Aborted_Jobs Table. Job ID Job Name Initiator Name Start Date Start Time End Date

110 110 Foglight for SAP NetWeaver v2.6 End Time Job Classification Periodic Server Name Target System Executing Server Name Work Process ID Work Process Number Step ID Number Number of Predecessor Jobs Number of Successor Jobs To open the Background_Aborted_Jobs_Details table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Background_Aborted_Jobs_Details table icon.

111 Chapter SAPServer Agent SAPServer_Background_Long_Running_Jobs_Details Table The SAPServer_Background_Long_Running_Jobs_Details table provides details of the top long running background jobs that have been identified on the SAP system during the last collection interval. These long running background jobs have been held longer than the Long Running Background Jobs Threshold set in the Setting SAPServer Parameters ASP tab. Note By default, this table collects the top 20 long running jobs. This parameter can be modified in the Setting the SAPserver Data Retrieval Parameters ASP tab for the Top Long Running Background Jobs field The values are derived from the following fields in the SAPR3_Background_LongRunning_Jobs Table. Job ID Job Name Initiator Name Start Date Start Time Job Classification Periodic Server Name Target System Executing Server Name Work Process ID Work Process Number Step ID Number Number of Predecessor Jobs Number of Successor Jobs To open the Background_Long_Running_Jobs_Details table 1 Click the SAPServer agent icon. A list of graph icons displays.

112 112 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Background_Long_Running_Jobs_Details table icon. SAPServer_Buffer_Allocation Graph The SAPServer Buffer_Allocation graph displays the buffer space allocated and used in kilobytes. The values are derived from the following fields in the SAPR3_Buffers Table: Used (KB) Allocated (KB) To open the Buffer_Allocation graph 1 Click the SAPServer agent icon. A list of graph icons displays.

113 Chapter SAPServer Agent 2 Double-click the SAPServer_Buffer_Allocation graph icon. SAPServer_Buffers Graph The SAPServer_Buffers graph displays the efficiency of R/3 or NetWeaver buffers, amount of swapping activity, and percent of free directory entries. The values are derived from the following fields in the SAPR3_Buffers Table. Buffer Hit Ratio (%) Number of Buffer Swaps Directory Free Percent (%) To open the Buffers graph 1 Click the SAPServer agent icon. A list of graph icons displays.

114 114 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Buffers graph icon. To continue your investigation Drill down on the Number of Buffer Swaps bar for a specific R/3 or NetWeaver buffer to investigate the buffer space allocation for an individual buffer with the SAPServer_Buffer_Allocation Graph view. Drill down on the Directory Free Percent (%) bar for a specific R/3 or NetWeaver buffer to investigate the directory allocation for an individual buffer with the SAPServer_Directory_Allocation Graph view. SAPServer_Directory_Allocation Graph The SAPServer_Directory_Allocation graph displays the maximum and current number of objects stored in the buffer. The values are derived from the following fields in the SAPR3_Buffers Table: Directory Entries Size Directory Entries Used To open the Directory_Allocation graph 1 Click the SAPServer agent icon. A list of graph icons displays.

115 Chapter SAPServer Agent 2 Double-click the SAPServer_Directory_Allocation graph icon. SAPServer_Dispatch_Queue Graph The SAPServer_Dispatch_Queue graph displays the number of requests and maximum requests waiting for each dispatcher type. The values are derived from the following fields in the SAPR3_Dispatch_Queue Table: Max. Request Waiting Request Waiting To open the Dispatch_Queue graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Dispatch_Queue graph icon.

116 116 Foglight for SAP NetWeaver v2.6 SAPServer_Locks Graph The SAPServer_Locks graph displays the total number of locks and the number of long locks that occurred during the collection interval. The values are derived from the following fields in the SAPR3_Enqueue_Total_Locks Table: Local Locks Totals Locks Local Long Locks Long Locks Totals To open the Locks graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Locks graph icon. To continue your investigation Drill down on the Local Long Locks to view long lock exception details with the SAPServer_Long_Locks_Details Table view. SAPServer_Long_Locks_Details Table The SAPServer_Long_Locks_Details table provides a breakdown of all the long enqueue details which have been held longer than the user-defined threshold across the entire landscape.

117 Chapter SAPServer Agent The values are derived from the following fields in the SAPR3_Enqueue_Long_Lock_Detail Table: Client User Name Table Name Lock Time Lock Date Lock Argument Origin Host Transaction Code Object Name Owner 1 Owner 2 Counter 1 Counter 2 System Number WP Number To open the Long_Locks_Details table 1 Click the SAPServer agent icon. A list of graph icons displays.

118 118 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Long_Locks_Details table icon. SAPServer_Memory_Extended Graph The SAPServer agent alerts you when the percent currently used for extended memory exceeds the user-defined threshold. Analyze extended memory usage when Currently Used Percent exceeds 80%. Extreme performance degradation can occur when R/3 or NetWeaver extended memory is full. Therefore, you should monitor utilization trends of SAPServer extended memory. The SAPServer_Memory_Extended graph displays, in kilobytes, the amount of memory allocated and currently used. The values are derived from the following fields in the SAPR3_Extended_Memory Table: Currently Used (KB) Allocated Memory (KB) To open the Memory_Extended graph 1 Click the SAPServer agent icon. A list of graph icons displays.

119 Chapter SAPServer Agent 2 Double-click the SAPServer_Memory_Extended graph icon. SAPServer_Memory_Heap Graph When batch programs use large amounts of heap memory and increase OS swap space requirements, use the Foglight System agent to verify that you have enough OS swap space. The SAPServer_Memory_Heap graph displays, in kilobytes, the amount of memory currently used and the maximum used since SAPServer instance startup. The values are derived from the following fields in the SAPR3_Heap_Memory Table: Currently Used (KB) Maximum Used (KB) To open the Memory_Heap graph 1 Click the SAPServer agent icon. A list of graph icons displays.

120 120 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Memory_Heap graph icon. SAPServer_Memory_Page Graph The SAPServer agent alerts you when the percent currently used for the paging area exceeds the user-defined threshold. Analyze paging area memory when the Currently Used Percent consistently exceeds 80%. The SAPServer_Memory_Page graph displays the amount of memory allocated, currently used, and on disk in kilobytes. The values are derived from the following fields in the SAPR3_Paging_Area_Memory Table: Currently Used (KB) Allocated Memory (KB) On Disk (KB) To open the Memory_Page graph 1 Click the SAPServer agent icon. A list of graph icons displays.

121 Chapter SAPServer Agent 2 Double-click the SAPServer_Memory_Page graph icon. SAPServer_Memory_Roll Graph The SAPServer agent alerts you when the percent currently used for the roll area exceeds the user-defined threshold. Analyze roll area memory when the Currently Used Percent consistently exceeds 80%. If the roll area Currently Used exceeds In Memory, then the roll file is being used instead of real memory. The SAPServer_Memory_Roll graph displays the amount of memory allocated, currently used, and on disk in kilobytes. The values are derived from the following fields in the SAPR3_Roll_Area_Memory Table: Currently Used (KB) Allocated Memory (KB) On Disk (KB) To open the Memory_Roll graph 1 Click the SAPServer agent icon. A list of graph icons displays.

122 122 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Memory_Roll graph icon. SAPServer_Program_DBDetails Table The SAPServer_Program_DBDetails table provides program database details including program database load. The values are derived from the following fields in the SAPR3_DB_Load_By_Program Table: Program Number of Changes Number of DB Calls Number Database Requests Number of Direct Reads Number of Sequential Reads Time per Change (ms) Time per DB Request (ms) Time per Direct Read (ms) Time per Sequential Read (ms) To open the Program_DBDetails table 1 Click the SAPServer agent icon. A list of graph icons displays.

123 Chapter SAPServer Agent 2 Double-click the SAPServer_Program_DBDetails table icon. SAPServer_Program_DBTime Graph The SAPServer_Program_DBTime graph displays the time per DB request, sequential read time, direct read time, and changes and commit time per millisecond for a program. The values are derived from the following fields in the SAPR3_DB_Load_By_Program Table: Changes and commits (ms) Time per DB Request (ms) Direct Read (ms) Sequential Reads (ms) To open the Program_DBTime graph 1 Click the SAPServer agent icon. A list of graph icons displays.

124 124 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Program_DBTime graph icon. To continue your investigation Drill down on the Time Per DB Request (ms) bar for a program to get a DB Request Time breakdown with the SAPServer_Program_DBDetails Table view. SAPServer_Program_DBcalls Graph The SAPServer_Program_DBcalls graph displays the number of database calls, database requests, direct reads, sequential reads, and changes per program. The values are derived from the following fields in the SAPR3_DB_Load_By_Program Table: Number Database Calls Number Changes Number Database Requests Number Direct Reads Number of Sequential Reads To open the Program_DBcalls graph 1 Click the SAPServer agent icon. A list of graph icons displays.

125 Chapter SAPServer Agent 2 Double-click the SAPServer_Program_DBcalls graph icon. To continue your investigation Drill down on the Number Database Calls bar for a program to investigate database time with the SAPServer_Program_DBTime Graph view. Drill down on the Number Database Requests bar for a program to investigate database requests with the SAPServer_Program_DBDetails Table view. SAPServer_Program_Workload Graph The SAPServer_Program_Workload graph displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per monitored program. The values are derived from the following fields in the SAPR3_Workload_By_Program Table: Avg. CPU Time (ms) Avg. Response Time (ms) Avg. DB Request Time (ms) Avg. Load Time (ms) Avg. Wait Time (ms) Number of Dialog Steps To open the Program_Workload graph 1 Click the SAPServer agent icon. A list of graph icons displays.

126 126 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Program_Workload graph icon. To continue your investigation Drill down on the Avg. Response Time (ms) bar for a program to get a DB Response Time breakdown with the SAPServer_Program_Workload_Details Table view. Drill down on the Avg. DB Request Time (ms) bar for a program to get a DB Request Time breakdown with the SAPServer_Program_DBcalls Graph view. Drill down on the Avg. Load Time (ms) bar for a program to investigate R/3 or NetWeaver Buffer usage with the SAPServer_Buffers Graph view. Drill down on the Avg. Wait Time (ms) bar for a program to analyze work process usage with the SAPServer_Work_Process Graph view. SAPServer_Program_Workload_Details Table The SAPServer_Program_Workload_Details table displays the program details including program load. The values are derived from the following fields in the SAPR3_Workload_By_Program Table: Program Avg. CPU Time (ms) Avg. DB Request Time (ms) Avg. Dispatch Time (ms) Avg. Enqueue Time (ms)

127 Chapter SAPServer Agent Avg. Load Time (ms) Avg. Response Time (ms) Avg. Roll In Time (ms) Avg. Roll Out Time (ms) Avg. Wait Time (ms) KBytes Requested Number of Dialog Steps Number of Roll Ins Number of Roll Outs Total CPU Time (s) Total DB Request Time (s) Total Response Time (s) Total Wait Time (s) To open the Program_Workload_Details table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Program_Workload_Details table icon.

128 128 Foglight for SAP NetWeaver v2.6 SAPServer_Special_Users_Details Table The purpose of this table is to monitor activity of the selected users identified by the Creating a Monitored Users List secondary ASP in the Setting SAPServer Monitor Parameters tab. This table will be populated only when these users are logged on. If the customer wants to extend this feature then the include list could be configured to monitor activity of selected users. The values are derived from the following fields in the SAPR3_Special_Users table. User Name Client Terminal Transaction ID Connection Type Last Active Session Time Number of User Sessions Memory Used (MB) To open the Special_Users_Details table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Special_Users_Details table icon.

129 Chapter SAPServer Agent SAPServer_TaskType_DBcalls Graph The SAPServer_TaskType_DBcalls graph displays the number of database calls, database requests, direct reads, sequential reads, and changes per task type. The values are derived from the following fields in the SAPR3_DB_Load_By_Task_Type Table: Number Changes Number Database Calls Number Database Requests Number Direct Reads Number Sequential Reads To open the TaskType_DBcalls graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_TaskType_DBcalls graph icon. To continue your investigation Drill down on the Number Database Calls bar for a task type to investigate database time with the SAPServer_TaskType_DBtime Graph view. SAPServer_TaskType_DBtime Graph The SAPServer_TaskType_DBtime graph displays the time per DB request, sequential read time, direct read time, and changes and commit time per millisecond for a task type.

130 130 Foglight for SAP NetWeaver v2.6 The values are derived from the following fields in the SAPR3_DB_Load_By_Task_Type Table: Time per DB Request (ms) Direct Reads (ms) Sequential Reads (ms) Changes and commits (ms) To open the TaskType_DBtime graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_TaskType_DBtime graph icon. SAPServer_TaskType_Workload Graph The SAPServer_TaskType_Workload graph displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per task type. The values are derived from the following fields in the SAPR3_Workload_By_Task_Type Table: Avg. CPU Time (ms) Avg. Response Time (ms) Avg. DB Request Time (ms) Avg. Load Time (ms)

131 Chapter SAPServer Agent Avg. Wait Time (ms) Number Dialog Steps To open the TaskType_Workload graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_TaskType_Workload graph icon. To continue your investigation Drill down on the Avg. DB Request Time (ms) bar for a task type to get a DB Request Time breakdown with the SAPServer_TaskType_DBcalls Graph view. Drill down on the Avg. Load Time (ms) bar for a task type to analyze work process usage with the SAPServer_Buffers Graph view. Drill down on the Avg. Wait Time (ms) bar for a task type to investigate R/3 or NetWeaver Buffer usage with the SAPServer_Work_Process Graph view. SAPServer_Trans_DBDetails Table The SAPServer_Trans_DBDetails table displays the transaction database details including transaction database load. The values are derived from the following fields in the SAPR3_DB_Load_By_Transaction Table: Transaction Code Number Changes Number Database Calls

132 132 Foglight for SAP NetWeaver v2.6 Number of DB Requests Number of Direct Reads Number of Sequential Reads Time per Change (ms) Time per DB Request (ms) Time per Direct Read (ms) Time per Sequential Read (ms) To open the Trans_DBDetails table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Trans_DBDetails table icon. SAPServer_Trans_DBcalls Graph The SAPServer_Trans_DBcalls graph displays the number of database calls, database requests, direct reads, sequential reads, and changes per transaction. The values are derived from the following fields in the SAPR3_DB_Load_By_Transaction Table: Number Database Calls Number Database Requests

133 Chapter SAPServer Agent Number Direct Reads Number Sequential Reads Number Changes To open the Trans_DBcalls graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Trans_DBcalls graph icon. To continue your investigation Drill down on the Number Database Calls bar for a transaction to investigate database time with the SAPServer_Trans_DBtime Graph view. Drill down on the Number Database Requests for a transaction to investigate number of database requests details with the SAPServer_Trans_DBDetails Table view. SAPServer_Trans_DBtime Graph The SAPServer_Trans_DBtime graph displays the time per DB request, sequential read time, direct read time, and changes and commit time per millisecond for a transaction. The values are derived from the following fields in the SAPR3_DB_Load_By_Transaction Table: Changes and Commits (ms) Time per DB Request (ms)

134 134 Foglight for SAP NetWeaver v2.6 Direct Reads (ms) Sequential Reads (ms) To open the Trans_DBtime graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Trans_DBtime graph icon. To continue your investigation Drill down on the Time Per DB Request (ms) bar for a transaction to investigate time per database information with the SAPServer_Trans_DBDetails Table view. SAPServer_Trans_Workload Graph The SAPServer_Trans_Workload graph displays, in milliseconds, the average response time, CPU time, DB request time, wait time, and load time. It also displays the number of dialog steps per transaction. The values are derived from the following fields in the SAPR3_Workload_By_Transaction Table: Avg. CPU Time (ms) Avg. Response Time (ms) Avg. DB Request Time (ms) Avg. Wait Time (ms) Avg. Load Time (ms) Number Dialog Steps

135 Chapter SAPServer Agent To open the Trans_Workload graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Trans_Workload graph icon. To continue your investigation Drill down on the Avg. Response Time (ms) bar for a transaction to get an average response time breakdown with the SAPServer_Trans_Workload_Details Table view. Drill down on the Avg. DB Request Time (ms) bar for a transaction to get a DB Request Time breakdown with the SAPServer_Trans_DBcalls Graph view. Drill down on the Avg. Wait Time (ms) bar for a transaction to analyze work process usage with the SAPServer_Work_Process Graph view. Drill down on the Avg. Load Time (ms) bar for a transaction to investigate R/3 or NetWeaver Buffer usage with the SAPServer_Buffers Graph view. SAPServer_Trans_Workload_Details Table The SAPServer_Trans_Workload_Details table displays the transaction details including transaction load. The values are derived from the following fields in the SAPR3_Workload_By_Transaction Table: Transaction Code

136 136 Foglight for SAP NetWeaver v2.6 Avg. CPU Time (ms) Avg. DB Request Time (ms) Avg. Dispatch Time (ms) Avg. Enqueue Time (ms) Avg. Load Time (ms) Avg. Response Time (ms) Avg. Roll In Time (ms) Avg. Roll Out Time (ms) Avg. Wait Time (ms) KBytes Requested Number of Dialog Steps Number of Roll Ins Number of Roll Outs Total CPU Time (s) Total DB Request Time (s) Total Response Time (s) Total Wait Time (s) To open the Trans_Workload_Details table 1 Click the SAPServer agent icon. A list of graph icons displays.

137 Chapter SAPServer Agent 2 Double-click the SAPServer_Trans_Workload_Details table icon. SAPServer_Users Graph The SAPServer_Users graph displays total number of users and sessions. The values are derived from the following fields in the SAPR3_Total_Users Table: Total Sessions Total Users To open the Users graph 1 Click the SAPServer agent icon. A list of graph icons displays.

138 138 Foglight for SAP NetWeaver v2.6 2 Double-click the SAPServer_Users graph icon. SAPServer_Work_Process Graph The SAPServer_Work_Process graph displays the total number of work processes, the number of running work processes, and the number of work process load and exception conditions such as stopped work processes or long running dialog steps for each work process type. The values are derived from the following fields in the SAPR3_Process_Overview Table: Max Allocated Running Long Running Stopped To open the Work_Process graph 1 Click the SAPServer agent icon. A list of graph icons displays.

139 Chapter SAPServer Agent 2 Double-click the SAPServer_Work_Process graph icon. To continue your investigation Drill down on the Running or Long Running bar for a specific work process to investigate running and long running work processes with the SAPServer_Work_Process_Detail Table view. Drill down on the Stopped bar to stopped work processes with the SAPServer_Work_Process_Stopped Graph view. SAPServer_Work_Process_Detail Table The SAPServer_Work_Process_Detail table provides details for the work processes. The values are derived from the following fields in the SAPR3_Process_Overview Table: Process Type Utilization (%) Total Running Stopped CPIC Completed DB Action Load

140 140 Foglight for SAP NetWeaver v2.6 Long Running PRIV Roll To open the Work_Process_Detail table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Work_Process_Detail table icon. To continue your investigation Drill down on the Stopped, CPIC, Completed or PRIV columns to investigate work processes details with the SAPServer_Work_Process_Exception_Detail Table view. SAPServer_Work_Process_Exception_Detail Table The SAPServer_Work_Process_Exception_Detail table displays a list of exception conditions, such as Stopped or Completed work processes or long running Dialog steps. The values are derived from the following fields in the SAPR3_Process_Exception_Detail Table. Process Type table.work Process Number Work Process PID

141 Chapter SAPServer Agent Reason For Waiting Status CPU Execution Time SAP Client Executing User Report Running Accessed Table Current Activity Semaphore Errors To open the Work_Process_Exception_Detail table 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Work_Process_Exception_Detail table icon.

142 142 Foglight for SAP NetWeaver v2.6 SAPServer_Work_Process_Stopped Graph The SAPServer_Work_Process_Stopped graph displays the total number of stopped processes, the number of stopped processes with a CPIC reason code, and the number of stopped processes with a PRIV reason code. The values are derived from the following fields in the SAPR3_Process_Overview Table. Reason CPIC Reason PRIV Total Stopped To open the Work_Process_Stopped graph 1 Click the SAPServer agent icon. A list of graph icons displays. 2 Double-click the SAPServer_Work_Process_Stopped graph icon. To continue your investigation Drill down on the Total Stopped bar for a specific stopped work process to investigate detailed process type information with the SAPServer_Work_Process_Exception_Detail Table view.

143 Chapter SAPServer Agent SAPServer Rules Aborted_Jobs Rule Availability_Connection Rule Availability_Process Rule Avg_Response_Time Rule Buf_Free_Dir_Entries Rule Buf_Free_Space Rule Buf_Hit_Ratio Rule Console Rule Dispatch_Req_Waiting Rule Extended_Memory_Use Rule Long_Running_Jobs Rule Long_Running_Process Rule Paging_Memory_Used Rule Process_Complete Rule Process_Stopped Rule Process_Utilization Rule Prog_Avg_Resp_Time Rule Roll_Memory_Used Rule SAP_Agent_Status Rule Tcode_Avg_Resp_Time Rule Long_Enqueue_Locks Rule Aborted_Jobs Rule The SAPServer Aborted_Jobs rule fires when there is an aborted background job. Rule Condition SAPServer.SAPR3_Alert_Summary.Alert_Type == "Aborted Jobs" && SAPServer.SAPR3_Alert_Summary.Number == 0 Severity Level Normal Action Log Message

144 144 Foglight for SAP NetWeaver v2.6 Rule Condition SAPServer.SAPR3_Alert_Summary.Alert_Type == "Aborted Jobs" && SAPServer.SAPR3_Alert_Summary.Number > 0 Severity Level Warning Action Log Message Interpreting the Rule The Agent will provide detailed information about the aborted background jobs. To start your investigation Right-click or drill down to the SAPServer_Background_Aborted_Jobs_Details Table view. Availability_Connection Rule The SAPServer Availability_Connection rule monitors the ability to connect to a SAP Server via RFC. Rule Condition SAPServer.SAPR3_Server_RFC_Availability.RFC_ Availability == 100 SAPServer.SAPR3_Server_RFC_Availability.RFC_ Availability < 100 Severity Level Normal Fatal Action Log Message Log Message System administrator Interpreting the Rule The Agent will verify connectivity through the RFC calls to the SAP Server. To start your investigation Right-click or drill down to the SAPServer_Availability Graph view.

145 Chapter SAPServer Agent Availability_Process Rule The SAPServer Availability_Process rule monitors the availability of operating system processes for an SAP Server. Rule Condition SAPServer.SAPR3_Process_Totals.Percent_Found >= #WORLD::AvailabilityProcessFatal# SAPServer.SAPR3_Process_Totals.Percent_Found < #WORLD::AvailabilityProcessFatal# Severity Level Normal Fatal Action Log Message Log Message System administrator Note #WORLD::AvailabilityProcessFatal# is a Foglight Registry entry with a default value of 100. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why a process availability problem occurred when one or more processes are not available. To start your investigation: Right-click or drill down to the SAPServer_Availability_Process Graph view.

146 146 Foglight for SAP NetWeaver v2.6 Avg_Response_Time Rule The SAPServer Avg_Response_Time Rule determines when the average response time for a task type is too high. Rule Condition SAPServer.SAPR3_Workload_By_Task_Type.Aver age_response_time < #WORLD::AvgResponseTimeWarning# SAPServer.SAPR3_Workload_By_Task_Type.Aver age_response_time >= #WORLD::AvgResponseTimeWarning# SAPServer.SAPR3_Workload_By_Task_Type.Aver age_response_time >= #WORLD::AvgResponseTimeCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::AvgResponseTimeWarning# is a Foglight Registry entry with a default value of #WORLD::AvgResponseTimeCritical# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating bottle necks causing average response time to be high. To start your investigation: Right-click or drill down to the SAPServer_TaskType_Workload Graph view.

147 Chapter SAPServer Agent Buf_Free_Dir_Entries Rule The SAPServer Buf_Free_Dir_Entries rule traces free directory entries. Rule Condition SAPServer.SAPR3_Buffers.Directory_Entries_Free _Percent > #WORLD::BufDirFreeEntiresPercentWarning# SAPServer.SAPR3_Buffers.Directory_Entries_Free _Percent <= #WORLD::BufDirFreeEntiresPercentWarning# SAPServer.SAPR3_Buffers.Directory_Entries_Free _Percent <= #WORLD::BufDirFreeEntiresPercentCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::BufDirFreeEntiresPercentWarning# is a Foglight Registry entry with a default value of 15. #WORLD::BufDirFreeEntiresPercentCritical# has a default value of 2. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why percentage of Free Directory Entries is below a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Buffers Graph view.

148 148 Foglight for SAP NetWeaver v2.6 Buf_Free_Space Rule The SAPServer Buf_Free_Space rule traces buffer free space. Rule Condition SAPServer.SAPR3_Buffers.Free_Space_Percent > #WORLD::BufFreeSpacePercentWarning# SAPServer.SAPR3_Buffers.Free_Space_Percent <= #WORLD::BufFreeSpacePercentWarning# SAPServer.SAPR3_Buffers.Free_Space_Percent <= #WORLD::BufFreeSpacePercentCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::BufFreeSpacePercentWarning# is a Foglight Registry entry with a default value of 15. #WORLD::BufFreeSpacePercentCritical# has a default value of 2. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating the R/3 or NetWeaver buffer free memory. To start your investigation: Right-click or drill down to the SAPServer_Buffer_Allocation Graph view.

149 Chapter SAPServer Agent Buf_Hit_Ratio Rule The SAPServer Buf_Hit_Ratio rule traces the buffer hit ratio. Rule Condition SAPServer.SAPR3_Buffers.Buffer_Hit_Ratio > #WORLD::BufHitRatioWarning# SAPServer.SAPR3_Buffers.Buffer_Hit_Ratio <= #WORLD::BufHitRatioWarning# SAPServer.SAPR3_Buffers.Buffer_Hit_Ratio <= #WORLD::BufHitRatioCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::BufHitRatioWarning# is a Foglight Registry entry with a default value of 90. #WORLD::BufHitRatioCritical# has a default value of 80. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why the R/3 or NetWeaver buffer hit ratio percentage is below a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Buffers Graph view. Console Rule The SAPServer Console rule detects any SAP System Log abnormalities. Rule Condition Severity Level Action SAPR3_System_Log.Severity == "NORMAL" Normal Log Message

150 150 Foglight for SAP NetWeaver v2.6 Rule Condition Severity Level Action SAPR3_System_Log.Severity == "WARNING" Warning Log Message SAPR3_System_Log.Severity == "CRITICAL" Critical Log Message System administrator SAPR3_System_Log.Severity == "FATAL" Fatal Log Message System administrator Interpreting the Rule Use this rule to begin investigating error conditions listed on the system log. Dispatch_Req_Waiting Rule The SAPServer Dispatch_Req_Waiting rule detects when a dispatch queue has a high number of currently waiting user requests. Rule Condition SAPServer.SAPR3_Dispatch_Queue.Request_Waiti ng < #WORLD::DispatchReqWaitingWarning# SAPServer.SAPR3_Dispatch_Queue.Request_Waiti ng >= #WORLD::DispatchReqWaitingWarning# Severity Level Normal Fatal Action Log Message Log Message System administrator Note #WORLD::DispatchReqWaitingWarning# is a Foglight Registry entry with a default value of 3. Use the Foglight Registry to change thresholds for rules by modifying registry entries.

151 Chapter SAPServer Agent Interpreting the Rule Use this rule to begin investigating why the number of waiting user requests is above a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Dispatch_Queue Graph view. Extended_Memory_Use Rule The SAPServer Extended_Memory_Use rule determines when SAP Server extended memory is near capacity. Rule Condition SAPServer.SAPR3_Extended_Memory.Currently_ Used_Percent < #WORLD::ExtendedMemoryUsedPercentWarning# SAPServer.SAPR3_Extended_Memory.Currently_ Used_Percent >= #WORLD::ExtendedMemoryUsedPercentWarning# SAPServer.SAPR3_Extended_Memory.Currently_ Used_Percent >= #WORLD::ExtendedMemoryUsedPercentCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::ExtendedMemoryUsedPercentWarning# is a Foglight Registry entry with a default value of 80. #WORLD::ExtendedMemoryUsedPercentCritical# has a default value of 95. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why the Currently Memory Percent used is above a registry threshold.

152 152 Foglight for SAP NetWeaver v2.6 To start your investigation: Right-click or drill down to the SAPServer_Memory_Extended Graph view. Long_Enqueue_Locks Rule The SAP Long_Enqueue_Locks identifies a long local lock that is defined by a specific lock threshold in the ASPs. Rule Condition SAPServer.SAPR3_Enqueue_Total_Locks.Local_L ong < #WORLD::LongLocksWarning SAPServer.SAPR3_Enqueue_Total_Locks.Local_L ong >= #WORLD::LongLocksWarning# Severity Level Normal Warning Action Log Message Log Message Note #WORLD::LongLocksWarning# is a Foglight Registry entry with a default value of 1. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating the number of SAP Server long local locks that exceeds the long local locks threshold set in the Setting SAPServer Parameters ASP. To start your investigation: Right-click or drill down to the SAPServer_Long_Locks_Details Table view.

153 Chapter SAPServer Agent Long_Running_Jobs Rule The SAP Long_Running_Jobs rule traces long running background jobs. Rule Condition SAPServer.SAPR3_Alert_Summary.Alert_Type == "Long Running Jobs" && SAPServer.SAPR3_Alert_Summary.Number == 0 SAPServer.SAPR3_Alert_Summary.Alert_Type == "Long Running Jobs" && SAPServer.SAPR3_Alert_Summary.Number > 0 Severity Level Normal Warning Action Log Message Log Message Interpreting the Rule The Agent will provide detailed information about the long running background jobs that exceeds the long running background job threshold. To start your investigation: Right-click or drill down to the SAPServer_Background_Long_Running_Jobs_Details Table view.

154 154 Foglight for SAP NetWeaver v2.6 Long_Running_Process Rule The SAPServer Long_Running_Process rule detects when the executing dialog step for a work process has a long run time. Rule Condition SAPServer.SAPR3_Process_Overview.Long_Runni ng <= (#WORLD::LongRunningMult# * SAPServer.SAPR3_Process_Overview.Total) && SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::LongRunningProcess# SAPServer.SAPR3_Process_Overview.Long_Runni ng > (#WORLD::LongRunningMult# * SAPServer.SAPR3_Process_Overview.Total) && SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::LongRunningProcess# Severity Level Normal Warning Action Log Message Log Message Note #WORLD::LongRunningProcess# is a Foglight Registry entry with a default value of DIA. #WORLD::LongRunningMult is a Foglight Registry entry with a default value of 0.2. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why the Number of Long Running Processes exceed a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Work_Process Graph view.

155 Chapter SAPServer Agent Paging_Memory_Used Rule The SAPServer Paging_Memory_Used rule determines when SAP Server paging area memory is near capacity. Rule Condition SAPServer.SAPR3_Paging_Area_Memory.Currentl y_used_percent < #WORLD::PagingMemoryUsedPercentWarning# SAPServer.SAPR3_Paging_Area_Memory.Currentl y_used_percent >= #WORLD::PagingMemoryUsedPercentWarning# SAPServer.SAPR3_Paging_Area_Memory.Currentl y_used_percent >= #WORLD::PagingMemoryUsedPercentCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::PagingMemoryUsedPercentWarning# is a Foglight Registry entry with a default value of 80. #WORLD::PagingMemoryUsedPercentCritical# has a default value of 95. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why the Paging area memory is above a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Memory_Page Graph view.

156 156 Foglight for SAP NetWeaver v2.6 Process_Complete Rule The SAPServer Process_Complete rule detects if any work processes are in Complete status. Rule Condition SAPServer.SAPR3_Process_Overview.Completed < #WORLD::ProcessCritical# SAPServer.SAPR3_Process_Overview.Completed >= #WORLD::ProcessCritical# Severity Level Normal Critical Action Log Message Log Message System administrator Note #WORLD::ProcessCritical# is a Foglight Registry entry with a default value of 1. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to trace work processes that changed status to Complete. To start your investigation: Right-click or drill down to the SAPServer_Work_Process_Exception_Detail Table view.

157 Chapter SAPServer Agent Process_Stopped Rule The SAPServer Process_Stopped rule detects when a certain percentage of the work processes in a Stopped status is too high. Rule Condition SAPServer.SAPR3_Process_Overview.Stopped < (#WORLD::ProcessStoppedMult# * SAPServer.SAPR3_Process_Overview.Total) SAPServer.SAPR3_Process_Overview.Stopped >= ( #WORLD::ProcessStoppedMult# * SAPServer.SAPR3_Process_Overview.Total ) Severity Level Normal Critical Action Log Message Log Message System administrator Note Note: #WORLD::ProcessStoppedMult# is a Foglight Registry entry with a default value of 0.4. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule A stopped process indicates that the process is waiting and a single user holds it. Having too many processes in stopped status affects the system performance. To start your investigation: Right-click or drill down to the SAPServer_Work_Process_Exception_Detail Table view.

158 158 Foglight for SAP NetWeaver v2.6 Process_Utilization Rule The SAPServer Process_Utilization rule traces processes utilization. Rule Condition SAPServer.SAPR3_Process_Overview.Utilization < #WORLD::ProcessUtilizationWarning# && ( SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess1# SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess2# SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess3# ) SAPServer.SAPR3_Process_Overview.Utilization >= #WORLD::ProcessUtilizationWarning# && ( SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess1# SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess2# SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess3# ) SAPServer.SAPR3_Process_Overview.Utilization == #WORLD::ProcessUtilizationCritical# && ( SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess1# SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess2# SAPServer.SAPR3_Process_Overview.Process_Typ e == #WORLD::UtilizedProcess3# ) Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::ProcessUtilizationWarning# is a Foglight Registry entry with a default value of 90. #WORLD::UtilizedProcess1# has a default value of DIA. #WORLD::UtilizedProcess2# has a default value of UPD. #WORLD::UtilizedProcess3# has a default value of UP2. Use the Foglight Registry to change thresholds for rules by modifying registry entries.

159 Chapter SAPServer Agent Interpreting the Rule Use this rule to verify Process Utilization is within the limits of registry threshold values. To start your investigation: Right-click or drill down to the SAPServer_Work_Process Graph view. Prog_Avg_Resp_Time Rule The SAPServer Prog_Avg_Resp_Time rule determines when the average response time for a monitored program is too high. Rule Condition SAPServer.SAPR3_Workload_By_Program.Averag e_response_time < #WORLD::ProgAvgRespTimeWarning# SAPServer.SAPR3_Workload_By_Program.Averag e_response_time >= #WORLD::ProgAvgRespTimeWarning# SAPServer.SAPR3_Workload_By_Program.Averag e_response_time >= #WORLD::ProgAvgRespTimeCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::ProgAvgRespTimeWarning# is a Foglight Registry entry with a default value of #WORLD::ProgAvgRespTimeCritical# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why Average Response time is above a registry threshold.

160 160 Foglight for SAP NetWeaver v2.6 To start your investigation: Right-click or drill down to the SAPServer_Program_Workload Graph view. Roll_Memory_Used Rule The SAPServer Roll_Memory_Used rule determines when SAP Server roll area memory is near capacity. Rule Condition SAPServer.SAPR3_Roll_Area_Memory.Currently_ Used_Percent < #WORLD::RollMemoryUsedPercentWarning# SAPServer.SAPR3_Roll_Area_Memory.Currently_ Used_Percent >= #WORLD::RollMemoryUsedPercentWarning# SAPServer.SAPR3_Roll_Area_Memory.Currently_ Used_Percent >= #WORLD::RollMemoryUsedPercentCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::RollMemoryUsedPercentWarning# is a Foglight Registry entry with a default value of 80. #WORLD::RollMemoryUsedPercentCritical# has a default value of 95. Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why roll area memory is above a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Memory_Roll Graph view.

161 Chapter SAPServer Agent SAP_Agent_Status Rule The SAP_Agent_Status rule fires when the SAPServer Agent has encountered an error that prevents it from functioning properly. Rule Condition Severity Level Action AgentMsg.Severity == "Informational" Normal Log Message AgentMsg.Severity == "Warning" Warning Log Message AgentMsg.Severity == "Critical" Critical Log Message Interpreting the Rule The SAPServer agent populates the AgentMsgs Table with informational and error messages that represent the status of SAPServer agent. The messages are internally assigned a severity, i.e., Informational, Warning, Critical, and Fatal. The SAP_Agent_Status rule alerts the SAP Administrator when the SAPServer agent has encountered an error that prevents it from properly functioning. Refer to the following table for a list of the possible messages and resolutions. The following are Common Agent Message Headers and Severities defined internally in the Agent Errors: Message ID Severity Message Text User Action SAP_SRV_501 Critical Version/DCMs mismatched. SAP_SRV_502 Critical Process ASPs: Failed to get call: There was a problem in the installation of the agent due to a mismatch between agent and DCM. Please call Technical Support. Verify ASP input.

162 162 Foglight for SAP NetWeaver v2.6 Message ID Severity Message Text User Action SAP_SRV_503 Critical For getting SAP system type SAP_SRV_504 Critical Process ASPs: getpwname failed to get UID for: SAP_SRV_505 Critical Failed to Logon to SAP RFC Interface on SAP_SRV_506 Critical Failed to connect to SAP RFC XMI Interface on SAP_SRV_507 Critical Failed to inspect startup log File: SAP_SRV_508 Critical Invalid SAP System Type [ SAP_SRV_509 Critical ] Check SAP System Name = [ 503 is bound to 502 Verify ASP input. Failure in the connection to SAP, verify the application server is up and the ASP input is correct. Failure in the connection to SAP, verify the application server is up and the ASP input is correct. Verify Log files exist and the permissions are set correctly. Failed to get SAP System type due to an incorrect System name or System number. 509 is bound to 508 & 510 SAP_SRV_510 Critical ] System Num = [ 510 is bound to 509 & 508

163 Chapter SAPServer Agent Message ID Severity Message Text User Action SAP_SRV_511 Critical Invalid SAP Home Directory SAP_SRV_512 Warning Top DB Load by Program ASP value exceeds the maximum and will be reset SAP_SRV_513 Warning Top Long Steps ASP value exceed the maximum and will be reset SAP_SRV_514 Warning Top Long Lock Details ASP value exceed the maximum and will be reset SAP_SRV_515 Warning Top Long Steps ASP value exceed the maximum and will be reset SAP_SRV_516 Warning Top Processes (CPU) ASP value exceed the maximum and will be reset Verify SAP Home directory is defined in the ASPs. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support.

164 164 Foglight for SAP NetWeaver v2.6 Message ID Severity Message Text User Action SAP_SRV_517 Warning Top Processes (Detailed) ASP value exceed the maximum and will be reset SAP_SRV_518 Warning Top Special Users ASP value exceed the maximum and will be reset SAP_SRV_519 Warning Top System Logs ASP value exceed the maximum and will be reset SAP_SRV_520 Warning Top Workload by Programs ASP value exceed the maximum and will be reset SAP_SRV_521 Warning Top Workload by Transaction ASP value exceed the maximum and will be reset The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support. The number of rows that report for this table is limited for changing the ceiling value contact support.

165 Chapter SAPServer Agent Message ID Severity Message Text User Action SAP_SRV_522 Warning Failed to Collect OS information SAP_SRV_523 Critical Failed to locate Sapstart binary, verify Sap Home Path and System name ASPs SAP_SRV_524 Critical Failed to connect to SAP Rfc XBP Interface SAP_SRV_525 Warning Top Background Aborted Jobs asp value exceed the maximum and will be reset to SAP_SRV_526 Warning Top Background Long Running Jobs asp value exceed the maximum and will be reset to SAP_SRV_999 Fatal Failed to initialize icu adapter validate resource file. Verify Application server is up and running. Failed to identify the SAP Process. Incorrect ASPs verify them and restart the agent. Failure in the connection to SAP, verify the app serve r is up and the asps input is correct also verify User Permissions for XBP interface. the number of rows that return back for this table is limited for changing the ceiling value contact support the number of rows that return back for this table is limited for changing the ceiling value contact support Verify resource file was installed properly.

166 166 Foglight for SAP NetWeaver v2.6 Tcode_Avg_Resp_Time Rule The SAPServer Tcode_Avg_Resp_Time rule determines when the average response time for a monitored transaction is too high. Rule Condition SAPServer.SAPR3_Workload_By_Transaction.Ave rage_response_time < #WORLD::TcodeAvgRespTimeWarning# SAPServer.SAPR3_Workload_By_Transaction.Ave rage_response_time >= #WORLD::TcodeAvgRespTimeWarning# SAPServer.SAPR3_Workload_By_Transaction.Ave rage_response_time >= #WORLD::TcodeAvgRespTimeCritical# Severity Level Normal Warning Critical Action Log Message Log Message Log Message System administrator Note #WORLD::TcodeAvgRespTimeWarning# is a Foglight Registry entry with a default value of #WORLD::TcodeAvgRespTimeCritical# has a default value of Use the Foglight Registry to change thresholds for rules by modifying registry entries. Interpreting the Rule Use this rule to begin investigating why Transaction Average Response time is above a registry threshold. To start your investigation: Right-click or drill down to the SAPServer_Trans_Workload Graph view.

167 3 SAP Agent Contents About the SAP Agent Using SAP R/3 Agent Startup Parameters SAP Investigations SAP Rules SAP Agent Tables

168 168 Foglight for SAP NetWeaver v2.6 About the SAP Agent The Foglight mysap.com agent works with other Foglight agents to assess the state of all the components within an SAP R/3 System. The mysap.com agent also collects data on availability and performance of R/3 work processes, system log, dispatch queue, memory configuration, users, transactions, and tasks. It also monitors for exception conditions and collects exception detail. Note See the Foglight Release Notes for information about creating an SAP user and assigning an SAP authorization profile. The release notes can be found on the product CD. Foglight provides a multidimensional view of R/3 resource usage for capacity planning, problem determination, and trend analysis, both real-time and historical. This lets an administrator use Foglight drill down capabilities to analyze resource usage of the underlying components in context to determine the cause and effect of response time degradation. In addition, the SAP basis administrator can use the collection of exception detail to focus directly on a problem area without sifting through large amounts of unrelated data.

169 Chapter SAP Agent ASPs Using SAP R/3 Agent Startup Parameters Investigations Investigating SAP R/3 Work Processes Investigating SAP R/3 Work Process Status Investigating SAP R/3 Dispatcher Investigating SAP R/3 Buffer Hit Ratio and Swaps Investigating SAP R/3 Buffer and Directory Allocation Investigating SAP R/3 Memory Investigating SAP R/3 Workload Investigating SAP R/3 Enqueues Investigating SAP R/3 Total and Long Locks Investigating SAP R/3 Availability Investigating SAP R/3 Workload Distribution Investigating SAP R/3 Task Type Workload Investigating SAP R/3 Transaction Workload Investigating SAP R/3 Program Workload Investigating Sessions and Users Investigating SAP R/3 Availability Investigating SAP R/3 Workload Distribution Investigating SAP R/3 System Log Views Using Cross-Host Views Rules Availability Connection Rule Availability Process Rule Long Enqueue Locks Rule Long Running Process Rule

170 170 Foglight for SAP NetWeaver v2.6 Average Response Time Rule Buf Free Dir Entries Rule Buffer Free Space Rule Buffer Hit Ratio Rule Console Rule Dispatch Request Waiting Rule Extended Memory Used Rule Paging Memory Used Rule Process Complete Rule Process Stopped Rule Process Utilization Rule Program Average Response Time Rule Roll Memory Used Rule Tcode Average Resp Time Rule Tables SAPR3_Application_Servers Table SAPR3_Buffers Table SAPR3_DB_Load_By_Program Table SAPR3_DB_Load_By_Task_Type Table SAPR3_DB_Load_By_Transaction Table SAPR3_Dispatch_Queue Table SAPR3_Enqueue_Long_Lock_Detai l Table SAPR3_Enqueue_Total_Locks Table SAPR3_Extended_Memory Table SAPR3_Heap_Memory Table SAPR3_Instance_Totals Table SAPR3_Instance_Totals Table SAPR3_Process_Detail Table SAPR3_Process_Exception_Detail Table SAPR3_Process_Overview Table SAPR3_Process_Totals Table SAPR3_Roll_Area_Memory Table SAPR3_Server_RFC_Availability Table SAPR3_Process_Detail Table SAPR3_Special_Users Table SAPR3_System_Log Table SAPR3_Total_Users Table

171 Chapter SAP Agent SAPR3_Long_Steps Table SAPR3_Paging_Area_Memory Table SAPR3_Process_CPU Table SAPR3_Workload_By_Program Table SAPR3_Workload_By_Task_Type Table SAPR3_Workload_By_Transaction Table SAPR3_Workload_Overview Table

172 172 Foglight for SAP NetWeaver v2.6 Using SAP R/3 Agent Startup Parameters The mysap.com agent comes with default startup parameters that dictate how the agent will perform. You can change these parameters to suit your system requirements. The parameters listed in the topics below are specific to the SAP agent. Topics Setting the Collection Rate Setting Purging Parameters Setting Collection Policies Parameters Setting SAP Parameters Setting SAP Monitor Parameters Creating a Monitored Transactions List Creating a Monitored Programs List Creating a Monitored Users List Creating a Monitored System Log Messages List Setting the Collection Rate The collection rate, or sample frequency, is the number of seconds between the end of a collection period and the start of the next. Use the Collection Rate tab in the ASP dialog to set the sample frequency. To set the sample frequency 1 Right-click the SAPR3 agent icon and choose Edit, ASPs.

173 Chapter SAP Agent 2 Enter the sample frequency in seconds in the Sample Frequency text box. 3 Enter how often (in seconds) the SAP agent checks R/3 instance availability via RFC connection and at the operating system process level. The default value is 60 seconds. 4 Click OK to save the action and close the dialog. Setting Purging Parameters To control the growth of the Foglight database, you may wish to purge data from tables in the Foglight database. Use the Database tab in the ASP dialog to set the purging parameters. Note Any change made to a table purge list is a global change; that is, it changes the table purge parameters for all SAPR3 agents on all host Foglight monitors. If you do not want to make the change global, give the table purge list a new name. To set the purging parameters 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the Database tab.

174 174 Foglight for SAP NetWeaver v2.6 3 Click Edit. The Table Purging window opens. Caution Do not click New or Delete. Table purge lists are tied to the agent executable and should not be modified. 4 Highlight the record to be edited and click Edit. The Edit: SAPR3PurgingTemplate dialog box opens. 5 Complete the following fields:

175 Chapter SAP Agent Enter the name of the collection table in the Table Name text box. Enter the number of days to retain data in the Purge Days text box. Note You can also click Select to choose from values already entered. 6 Click Apply. Note You should not delete tables from a table purge list. Setting Collection Policies Parameters Use the Collection Policies tab in the ASP dialog to set various time thresholds. To set collection policy parameters 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the Collection Policies tab. 3 Enter the threshold (in milliseconds) at which the SAP agent writes the dialog step to the SAPR3 Long Steps exception table for the collection interval in the Dialog Step Response Time Threshold text box. The default value is 2000 ms. 4 Enter the threshold (in minutes) at which the SAP agent writes an enqueue to the SAPR3 Long Lock Detail exception table for the collection interval in the Enqueue Lock Threshold text box. The default value is 30 minutes. 5 Enter the threshold (in seconds) at which the SAP agent writes a work process to the SAPR3 Process Exception Detail exception table for the collection interval in the Work Process Execution Time Threshold text box. The default value is 600 seconds.

176 176 Foglight for SAP NetWeaver v2.6 6 Enter how often (in seconds) the SAP agent tries to connect to R/3 via RFC in the SAP R/3 RFC Connection Timeout threshold text box. If the agent cannot connect after reaching this threshold, the R/3 instance is unavailable. The default value is 30 seconds. 7 Click OK to save the entry and close the ASP dialog. Setting SAP Parameters The SAP agent collects R/3 performance and availability statistics via an RFC connection. Depending on the release of R/3, create a CPIC user or System user for each R/3 system to be monitored. Use the SAP tab in the ASP dialog to create a CPIC or System user. To create a CPIC or System user 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP tab. 3 Enter the SAP client number for the Foglight user in the SAP R/3 Client ID text box. 4 Enter the Foglight user name reserved for RFC data collection in the SAP R/3 CPIC/System User Name text box. 5 Enter the Foglight user password in the SAP R/3 CPIC/System User Password text box.

177 Chapter SAP Agent 6 Enter the SAP system name (SID) in the SAP R/3 System Name text box. 7 Enter the SAP system number for the monitored R/3 instance in the SAP R/3 System Number text box. 8 Click OK to save the entry and close the ASP dialog. Setting SAP Monitor Parameters Use the SAP Monitor tab to create and edit the Monitored Transactions List, Monitored Programs list, Monitored Users list, and Monitored System Log Messages list. To set SAP Monitor parameters 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Perform any of the following tasks: Creating a Monitored Transactions List Creating a Monitored Programs List Creating a Monitored Users List Creating a Monitored System Log Messages List 4 Click OK to save the entry and close the ASP dialog.

178 178 Foglight for SAP NetWeaver v2.6 Creating a Monitored Transactions List Use the SAP agent to monitor business critical or custom transactions independently with the default SAPR3 TransactionsList. Note Any change made to the monitored transaction list is a global change; that is, it changes the monitored transactions for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the monitored transaction list a new name. You can also edit or delete entries from the list. 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 In the Monitored Transactions text box, enter the name of the list to be edited, or use the default list. 4 Click Edit. The SAPR3_Monitored_Transactions window opens, showing a default list of transaction codes.

179 Chapter SAP Agent 5 Click New. 6 Enter a transaction code or click Select to choose a code previously entered Note The transaction name is not case sensitive, and you can use the wildcard character (*). The SAP agent provides Y* and Z* as default values. 7 Click Apply to save the entry and keep the dialog open to add another transaction code. Click OK to save the entry and close the dialog. Editing or Deleting a Transaction Code The Monitored Transaction list contains the transaction code. To edit a transaction code 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored Transaction List and click Edit. 4 From the SAPR3_Monitored_Transactions window, click Edit. 5 In the Transaction_Code text box, enter the name of the SAP transaction code to be monitored, or click Select to choose a previously entered Transaction_Code. Note The transaction name is not case sensitive, and you can use the wildcard character (*). The SAP agent provides Y* and Z* as default values.

180 180 Foglight for SAP NetWeaver v2.6 6 Click OK. To delete a transaction code 1 In the SAPR3_Monitored_Transactions window, highlight the transaction code to be deleted. 2 Click Delete. 3 On the Delete Confirmation dialog box, click Yes. Creating a Monitored Programs List In an R/3 environment, a custom program might not be associated with a Tcode. For example, a custom program might be executed directly from transactions se38, sa38, or report trees. Monitoring workload activity only at the task type or transaction level does not let you monitor resource usage of an individual custom program. For this reason, the SAP agent lets you monitor business critical or custom programs independently using a default list called the SAPR3ProgramsList. Note Any change made to the monitored programs list is a global change; that is, it changes the monitored programs for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the monitored programs list a new name. You can also edit or delete programs from the Monitored Programs list. To create a Monitored Programs list 1 Right-click the SAPR3 agent and choose Edit, ASPs. 2 Click the SAP Monitor tab.

181 Chapter SAP Agent 3 In the Monitored Programs text box, enter the name of the list to be edited or use the default list. 4 Click Edit. The SAPR3_Monitored_Programs window opens, showing a default list of programs. 5 Click New. 6 In the Program text box, enter the name of the SAP program to be monitored or click Select to choose a previously entered program.

182 182 Foglight for SAP NetWeaver v2.6 7 Click Apply to save the entry and keep the dialog open to add more entries. Click OK to save the entry and close the dialog. Editing or Deleting a Program The Monitored Program list contains the program name. To edit a program 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored Program list and click Edit. 4 Highlight the program you wish to modify and click Edit. 5 In the Program text box, enter the name of the SAP program to be monitored, or click Select to choose a previously entered program. 6 The program name is not case sensitive, and you can use the wildcard character (*). The SAP agent provides Y* and Z* as default values. 7 Click OK. To delete a program 1 In the SAPR3_Monitored_Programs window, highlight the program to be deleted. 2 Click Delete. 3 On the Delete Confirmation dialog box, click Yes. Creating a Monitored Users List The SAP agent lets you monitor the activity of a specific R/3 user. It also contains a default list called the SAPR3UsersList. Note Any change made to the Users List is a global change; that is, it changes the monitored users for all the SAP agents on all the host Foglight monitors. If you do not want to make the change global, give the users list a new name. You can also edit or delete entries from the list. To create a Monitored Users list 1 Right-click the SAPR3 agent icon and choose Edit, ASPs.

183 Chapter SAP Agent 2 Click the SAP Monitor tab. 3 In the Monitored Users text box, enter the name of the list to be edited, or use the default list. 4 Click Edit. The SAPR3_Monitored_Users window opens, showing a default list of users. 5 Click New.

184 184 Foglight for SAP NetWeaver v2.6 6 In the User text box, enter the name of the SAP user to be monitored, or click Select to choose a previously entered user. 7 Click Apply to save the entry and keep the dialog open to add another user. 8 Click OK to save the entry and close the dialog. Editing or Deleting a User The Monitored Users list contains user names. To edit a user 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored Users list and click Edit. 4 From the SAPR3_Monitored_Users window, click Edit. 5 In the User text box, enter the name of the SAP user to be monitored, or click Select to choose a previously entered user. Note The user name is not case sensitive, and you can use the wildcard character (*). The SAP agent provides SAP* and DDIC as default values. 6 Click OK. To delete a user 1 In the SAPR3_Monitored_Users window, highlight the user to be deleted. 2 Click Delete. 3 On the Delete Confirmation dialog box, click Yes. Creating a Monitored System Log Messages List The basis administrator can use the SAP agent to monitor an R/3 System by trapping critical system messages and generating an alert condition to the Foglight event log. The SAP agent R/3 log filter comes with the default list SAPR3 Messages List for monitoring the most critical events. Each message is filtered based on its message number. You can choose a severity level for each message and add a short text string to be displayed next to the error text provided by SAP. Note Any change made to the monitored system log messages list is a global change; that is, it changes the monitored system log messages for all the SAP agents on all the host Foglight

185 Chapter SAP Agent monitors. If you do not want to make the change global, give the monitored system log messages list a new name. You can also edit and delete entries from the list. To create a Monitored System Log Messages list 1 Right-click the SAPR3 agent and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 In the Monitored System Log Messages text box, enter the name of the list to be edited, or use the default list. 4 Click Edit. The SAPR3_Monitored_Messages window opens, showing a default list of message numbers.

186 186 Foglight for SAP NetWeaver v2.6 5 Click New. 6 In the Message Number text box, enter the R/3 log message number you want the SAP agent to trap, or click Select to choose a previously entered Message_Number. 7 From the Severity drop-down, select the Foglight severity level associated with the R/3 message number. The syslog message displays in the Foglight event log in one of the following colors: INFORMATIONAL (white) WARNING (yellow) CRITICAL (orange) FATAL (red) 8 In the Text text box, enter the message text to be issued when the SAP agent encounters the R/3 message number specified in the Message_Number text box, or click Select to choose a previously entered Text. 9 Click Apply to save the entry and keep the dialog open to add another message. 10 Click OK to save the entry and close the dialog. Editing or Deleting Message Number Message number, severity, and text display on the Monitored System Log Messages list. To edit a message number 1 Right-click the SAPR3 agent icon and choose Edit, ASPs. 2 Click the SAP Monitor tab. 3 Enter the name of the Monitored System Message list and click Edit. 4 Highlight the message you wish to modify and click Edit.

187 Chapter SAP Agent 5 In the Message_Number text box, enter the R/3 log message number you want the SAP agent to trap, or click Select to choose a previously entered Message_Number. 6 From the Severity drop-down, select the Foglight severity level associated with the R/3 message number. The syslog message displays in the Foglight event log in one of the following colors: INFORMATIONAL (white) WARNING (yellow) CRITICAL (orange) FATAL (red) 7 In the Text text box, enter the message text to be issued when the SAP agent encounters the R/3 message number specified in the Message_Number text box, or click Select to choose a previously entered Text. 8 Click OK to close the dialog. To delete a message number 1 In the SAPR3_Monitored_Messages window, highlight the message number to be deleted. 2 Click Delete. 3 On the Delete Confirmation dialog box, click Yes.

188 188 Foglight for SAP NetWeaver v2.6 SAP Investigations Investigating SAP R/3 Work Processes Investigating SAP R/3 Work Process Status Investigating SAP R/3 Dispatcher Investigating SAP R/3 Buffer Hit Ratio and Swaps Investigating SAP R/3 Buffer and Directory Allocation Investigating SAP R/3 Memory Investigating SAP R/3 Workload Investigating SAP R/3 Enqueues Investigating SAP R/3 Total and Long Locks Investigating SAP R/3 Availability Investigating SAP R/3 Workload Distribution Investigating SAP R/3 Task Type Workload Investigating SAP R/3 Transaction Workload Investigating SAP R/3 Program Workload Investigating Sessions and Users Investigating SAP R/3 Availability Investigating SAP R/3 Workload Distribution Investigating SAP R/3 System Log Investigating SAP R/3 System Log Investigating SAP R/3 Work Processes Review the usage and state of your work processes to gain a high-level view of your R/ 3 System performance. Use the SAPR3 Work Process graph to view work process usage by type and identify instances with too few or too many processes. For example, if an R/ 3 instance has 20 dialog work processes, but only 50% of them are used after the system completes several normal business cycles, eliminate the unused work processes to save memory. Or you might use the SAPR3 System User Overview graph to discover that a high number of users are running work processes on R/3 instance and keeping other users waiting while other R/3 instances have fewer users or work processes running. To counter such an uneven distribution, review your logon load balancing.

189 Chapter SAP Agent Often a key indication of a performance problem is when all the work processes of a particular type, such as Dialog or Update, are occupied. The SAP agent alerts you when the percent usage of Dialog or Update work processes exceeds the user-defined threshold. Note Before increasing the number of work processes for an R/3 instance, use the Foglight System Agent to check that the system has enough CPU and memory resources. If CPU usage is consistently at or above 80%, increasing the number of work processes might actually decrease performance. Investigating SAP R/3 Work Process Status Always identify when and why a work process is in a Stopped or Complete status. A single defective work process can negatively impact other work processes and cause a chain reaction. The SAP agent alerts you when a certain percentage of work processes enters Stopped or Complete status, or when a work process exceeds your defined execution time threshold. Foglight collects detailed information for the problem work process. For example, an alert for a stopped work process with a reason of PRIV typically indicates a problem with R/3 memory. In this case, use the Data Browser to analyze work process detail data from the SAPR3 Process Exception Detail table and the SAP agent R/3 memory views to analyze R/3 memory usage. See Investigating SAP R/3 Memory for more information on analyzing memory usage. Start with the Work Process Graph The Work Process graph displays the total number of work processes, the number of running work processes, and the number of work process load and exception conditions such as stopped work processes or long running dialog steps for each work process type. Drill down on the Stopped bar to investigate the reason for a stopped work process with the Work Process Stopped graph. SAPR3 Work Process Graph The Work Process graph displays the total number of work processes, the number of running work processes, and the number of work process load and exception conditions such as stopped work processes or long running dialog steps for each work process type. The values are derived from the Long_Running, Running, Stopped, and Total fields in the Process Overview table.

190 190 Foglight for SAP NetWeaver v2.6 To open the Work Process graph Drill down on the WP Utilization Dialog data point of the SAPR3 Dialog Response Overview Graph, OR Drill down on the Avg. Wait Time bar of the Task Type Workload graph or the Program Workload graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Work_Process graph icon. To continue your investigation Drill down on the Total bar for a specific work process to isolate the analysis to a single work process. To investigate the reason for a stopped work process, drill down on the Stopped bar for a work process type with the Work Process Stopped graph. SAPR3 Work Process Stopped Graph The Work Process Stopped graph displays the total number of stopped processes, the number of stopped processes with a CPIC reason code, and the number of stopped processes with a PRIV reason code. The values are derived from the CPIC, PRIV, and Stopped fields in the Process Overview table. To open the Work Process Stopped graph

191 Chapter SAP Agent Drill down on the Stopped bar of the Work Process graph, OR Click the SAPR3 agent icon, and double-click the SAPR3_Work_Process_Stopped graph icon. To continue your investigation Use the Data Browser to view work process exception details with the Process Exception Detail table. This table lists exception conditions such as Stopped or Completed work processes or long running Dialog steps. Use the Data Browser to view CPU utilization per work process and configure the required number of work processes with the Process CPU table. CPU usage of the last dialog work process should be close to 0:00 to ensure the availability of a free dialog work process for a user request. Investigating SAP R/3 Dispatcher The SAP agent alerts you when a dispatcher queue length exceeds a user-defined threshold. Monitoring the length of the dispatcher queue provides an early warning of problems with load distribution or work processes in a Stopped status. Another possible cause for a long dispatcher queue is one or more long running dialog steps. In this case, you might need to perform database or program analysis, move to batch mode, or execute at non-peak processing times. Note See Investigating SAP R/3 Work Processes for information about identifying and resolving problem work processes.

192 192 Foglight for SAP NetWeaver v2.6 To open the Dispatch Queue Graph The SAPR3 Dispatch Queue graph displays the number of requests and maximum requests waiting for each dispatcher type. The values are derived from the Maximum_Request_Waiting and Request_Waiting fields in the Dispatch Queue table. 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Dispatch_Queue graph icon. Investigating SAP R/3 Buffer Hit Ratio and Swaps The SAP agent alerts you when the hit ratio for a buffer falls below the user-defined threshold. Configuring a buffer without enough space to store an object requires increased buffer reloading and unnecessary database accesses to make the necessary space available. Buffer configurations that are too large waste memory and cause OS paging, which results in memory bottlenecks. Swaps should not occur in the buffers of a production system. If this happens, increase the buffer size or maximum number of entries. The exception is the Program buffer, where some swaps are unavoidable. Note Hit ratios less than 95% are acceptable for the Program buffer and the Single Key buffer. The Single Key buffer quality increases very slowly from system startup. Therefore, investigate hit ratios of less than 90% only if the buffer has no free space left. Start with the Buffers Graph The Buffers graph displays the efficiency of R/3 buffers, amount of swapping activity, and percent of free directory entries.

193 Chapter SAP Agent Drill down on the Buffer Hit Ratio bar for a specific R/3 buffer to isolate the analysis to a single buffer with the Buffers graph. Drill down on the Number of Buffer Swaps bar for a specific R/3 buffer to investigate the buffer space allocation for an individual buffer with the Buffers Allocation graph. Drill down on the Directory Free Percent bar for a specific R/3 buffer to investigate the directory allocation for an individual buffer with the Directory Allocation graph. SAPR3 Buffers Graph The Buffers graph displays the efficiency of R/3 buffers, amount of swapping activity, and percent of free directory entries. The values are derived from the Buffer_Hit_Ratio, Buffer_Swap, and Directory_Entries_Free_Percent fields in the Buffers table. To open the Buffers graph Drill down on the Avg. Load Time bar on the Task Type Workload graph, Program Workload graph, or the Transaction Workload graph. OR Click the SAPR3 agent icon and double-click the SAPR3_Buffers graph icon. To continue your investigation Drill down on the Buffer Hit Ratio bar for a specific R/3 buffer to isolate the analysis to a single buffer.

194 194 Foglight for SAP NetWeaver v2.6 Drill down on the Number of Buffer Swaps bar for a specific R/3 buffer to investigate the buffer space allocation for an individual buffer with the Buffer Allocation graph. Drill down on the Directory Free Percent bar for a specific R/3 buffer to investigate the directory allocation for an individual buffer with the Directory Allocation graph. After each drill down, choose Graph Type, Line from the graph menu for historical analysis. Investigating SAP R/3 Buffer and Directory Allocation The SAP agent alerts you when the percent of free space for a buffer or percent of free directory entries falls below the user-defined threshold. If an R/3 buffer hit ratio is low or if a number of swaps have occurred, investigate the level of free space and free directory entries. If the directory for the buffer is full, but the buffer has space available, the remaining space is not used. Also make sure the directory has free entries. Free directory entries are as important as having space in the buffer; otherwise, objects begin swapping and performance degrades. Note Increase the buffer size or the number of allowed entries by increments of 10%. Many R/3 buffers are contained in shared memory pools. When the sizes of these buffers are changed, adjust the size of the corresponding pool. Before increasing the buffer size, ensure that the operating system has sufficient memory resources to avoid a memory bottleneck. Start with the Buffer Allocation Graph The Buffer Allocation graph displays the buffer space allocated and used in kilobytes. Drill down on the Allocated bar for a specific R/3 buffer to isolate the analysis to a single buffer. SAPR3 Buffer Allocation Graph The Buffer Allocation graph displays the buffer space allocated and used in kilobytes. The values are derived from the Allocated and Space_Used fields in the Buffers talble. To open the Buffer Allocation graph

195 Chapter SAP Agent Drill down on the Number of Buffer Swaps bar of the SAPR3 Buffers graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Buffer_Allocation graph icon. To continue your investigation Drill down on the Allocated bar of a specific R/3 buffer to isolate the analysis to a single buffer. From the graph menu, choose Graph Type, Line for historical analysis of R/3 instance availability. Investigating SAP R/3 Memory The memory management system allocates storage to user contexts from three different types of storage: Roll area storage R/3 extended memory Process-local storage (heap) The order in which storage is allocated to a user context from these storage types depends upon the release of R/3, version of the operating system, and whether the user context is running in an R/3 Dialog or non-dialog work process.

196 196 Foglight for SAP NetWeaver v2.6 Topics Memory Allocation by Dialog Work Processes Memory Allocation by Non-Dialog Work Processes Memory Allocation by Dialog Work Processes Dialog work processes allocate memory in the following order: 1 From the roll area up to profile parameter ztta/roll_first. 2 Up to profile parameter ztta/roll_extension or until em/initial_size is full, whichever comes first, if additional memory is required. 3 From the remaining roll area ztta/roll_area - ztta/roll_first if the user context needs more memory. 4 Up to abap/heap_area_dia or abap/heap_area_total. R/3 application servers are significant users of swap space. Depletion of swap space in a host system can cause serious system problems. For this reason, use the Foglight System agent to monitor swap space usage. Memory Allocation by Non-Dialog Work Processes Non-Dialog work processes allocate memory in the following manner: 1 From the roll area up to ztta/roll_area. 2 Up to abap/heap_area_nondia or abap/heap_area_total if additional memory is required. 3 Up to ztta/roll_extension or until em/initial_size is full, whichever comes first, if no more process-local storage can be allocated. R/3 application servers are significant users of swap space. Depletion of swap space in a host system can cause serious system problems. For this reason, use the Foglight System agent to monitor swap space usage. SAPR3 Memory Roll Graph The SAP agent alerts you when the percent currently used for the roll area exceeds the user-defined threshold. Analyze roll area memory when the Currently Used Percent consistently exceeds 80%. If the roll area Currently Used exceeds In Memory, then the roll file is being used instead of real memory.

197 Chapter SAP Agent The Memory Roll graph displays the amount of memory allocated, currently used, and on disk in kilobytes. The values are derived from the Currently_Used, In_Memory, and On_Disk fields in the Roll Area Memory table. To open the Memory Roll graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Memory_Roll graph icon. SAPR3 Memory Extended Graph The SAP agent alerts you when the percent currently used for extended memory exceeds the user-defined threshold. Analyze extended memory usage when Currently Used Percent exceeds 80%. Extreme performance degradation can occur when R/3 extended memory is full. Therefore, you should monitor utilization trends of R/3 extended memory. The Memory Extended graph displays, in kilobytes, the amount of memory allocated and currently used. The values are derived from the Currently_Used and In_Memory fields in the Extended Memory table. To open the Memory Extended graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Memory_Extended graph icon.

198 198 Foglight for SAP NetWeaver v2.6 SAPR3 Memory Heap Graph When batch programs use large amounts of heap memory and increase OS swap space requirements, use the Foglight System agent to verify that you have enough OS swap space. The Memory Heap graph displays, in kilobytes, the amount of memory currently used and the maximum used since R/3 instance startup. The values are derived from the Currently_Used and Maximum_Use fields in the Heap Memory table. To open the Memory Heap graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Memory_Heap graph icon.

199 Chapter SAP Agent Investigating SAP R/3 Workload R/3 System workload statistics provide reliable data for analysis of application throughput, load, and response times. Use this data to identify the application components causing response time problems and reveal the workload distribution of your applications. Always begin a detailed application analysis with a workload analysis. To perform a workload analysis, first establish a baseline of application behavior. As the workload mix changes during the day, week, month, so do the bottlenecks. Determine whether the average response time increases certain times of the day when the load increases, or response time is high even when the load is low. If the latter is true, the performance problem is load-dependent. Compare the average response time to operating system resource usage for the same time period to determine whether an increase in response time correlates with a large CPU load or high paging rates. Many different factors negatively impact response time and throughput. High CPU load or paging rates can result in high load times, processing times, or database times. For dialog tasks, database time greater than 400ms, and direct read time greater than 2ms, or sequential read time greater than 10ms might indicate a database problem. Improper R/3 memory configuration can cause increased load times and roll in or roll out times. Work process long execution times or too few work processes configured can create large wait times. These performance factors can cause poor response times and unsatisfactory throughput in a single transaction or all transactions. Topics System-Level Tuning for Dialog Work Process Conditions System-Level Tuning for Update Work Process Conditions System-Level Tuning for Dialog Work Process Conditions Consider system-level tuning or more detailed investigation when the following conditions exist for Dialog work processes: Average response greater than 1000ms Time per database request greater than 5ms Average CPU time greater than 40% of response time Direct reads greater than 2ms Average database request time greater than 40% of response time or greater than 400ms

200 200 Foglight for SAP NetWeaver v2.6 Sequential reads greater than 10ms Average wait time greater than 50ms Changes and commits greater than 25ms Average load time greater than 50ms Response time for main menu greater than 100ms Average roll in, roll out time greater than 20ms System-Level Tuning for Update Work Process Conditions Consider system-level tuning or more detailed investigation when the following conditions exist for Update work processes: Average response time greater than 500ms Direct reads greater than 10ms Average database request time greater than 10% of request time Sequential reads greater than 15ms Average wait time greater than 100ms Changes and commits greater than 40ms Average load time greater than 50ms Investigating SAP R/3 Enqueues An R/3 enqueue work process administers enqueues in the table that is buffered in the R/3 main memory. A local file exists on an enqueue server to retain enqueues even when an R/3 instance is shut down. To set an enqueue, an ABAP program must explicitly call the enqueue module. To remove the enqueue, the same ABAP program explicitly calls the dequeue module. This lets the enqueue remain in place through several steps of a R/3 transaction. At the completion of the transaction, all enqueues are automatically removed. Monitoring enqueues is one of the system administrator's regular duties. An enqueue that lasts for an extended period of time (more than 30 minutes) might indicate either incorrect programming or incorrect use of the program. Unreleased locks can block other users from working in the same transactions for updating information. When programs use too many enqueues, the enqueue table in main memory can become full, preventing new enqueues from being set and bringing your system to a standstill. See Investigating SAP R/3 total and long locks for more information.

201 Chapter SAP Agent Investigating SAP R/3 Total and Long Locks The SAP agent monitors the volume of enqueues and alerts you when an enqueue is held longer than the user-defined threshold. If the agent detects a long enqueue, it writes the enqueue details to the Long Lock Detail table for historical analysis. Start with the Locks The Locks graph displays the total number of locks and the number of long locks that occurred during the collection interval. Use the Data Browser to view long lock exception details with the Long Lock Detail table. SAPR3 Locks Graph The Locks graph displays the total number of locks and the number of long locks that occurred during the collection interval. The values are derived from the Local_Locks, Local_Long, Locks, and Long_Locks fields in the Enqueue Total Locks talble. To open the Locks graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Locks graph icon. To continue your investigation Use the Data Browser to view long lock exception details with the Long Lock Detail table.

202 202 Foglight for SAP NetWeaver v2.6 Investigating SAP R/3 System Log All R/3 instances use system logs to list events or problems that occurred during system operation. In a distributed environment, each application server registers a local log while the central log can be configured to collect all the local logs from all the application servers. The local log files are updated continuously, while a short delay always occurs in the update of the central log. Basis administrators must check R/3 System logs regularly for system-related problems, ABAP short dumps, and problems with system startup or shutdown. They periodically perform a string search for problems related to ORA, PAG, and ROL. The basis administrator can use the SAP agent to trap critical R/3 system messages and generate alert conditions to the SAP map. This provides a single point of control for monitoring and managing heterogeneous enterprise applications that include multiple R/3 Systems. The SAP agent R/3 log filter comes with a default configuration for monitoring the most critical events. Each message is filtered based on its message number. You can choose a severity level for each message and add a short text string to be displayed next to the error text provided by SAP. See Using SAP Startup Parameters to update the log filter. Investigating SAP R/3 Availability The SAP agent monitors R/3 availability from two perspectives: the ability to connect to an R/3 instance and the availability of R/3 operating system processes. The SAP agent reads the R/3 instance profile located in the /usr/sap/sid/sys/profile directory to determine the current work process configuration. The SAP agent also monitors availability for all R/3 operating systems processes including: Collector and Sender Examples: - co. sapd10_dvebmgs10 - se. sapd10_dvebmgs10 Message server Example: ms. sapd10_dvebmgs10 Dispatcher process Example:

203 Chapter SAP Agent One of the dw.sapd10_dvebmgs10 processes Gateway server Example: Started by dispatcher - gwrd The Spool, Dialog, Update, Enqueue, and Batch processes Example: Run at the OS level under the dw.sapd10_dvebmgs10 processes The SAP agent generates a process failure alert when the total number of operating system processes found does not match the number expected and generates a connection failure alert when the agent is not able to connect to an R/3 instance via RFC. Open the Availability or Availability Process Graph Open the Availability graph or the Availability Process graph. The Availability graph shows whether an RFC connection was made to the R/3 instance or if the connection failed. The Availability Process graph shows the total processes expected, total processes found, and percent availability for each R/3 operating system process type. Choose Graph Type, Line from the graph menu on either of these graphs for historical analysis. SAPR3 Availability Graph The Availability graph displays 100 if an RFC connection was made to the R/3 instance or 0 if the connection failed. The value is derived from the RFC_Availability field in the Server RFC Availability table. To open the Availability graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Availability graph icon.

204 204 Foglight for SAP NetWeaver v2.6 To continue your investigation From the graph menu, choose Graph Type, Line to investigate historical analysis SAPR3 Availability Process Graph The Availability Process graph displays the total processes expected, total processes found, and percent availability for each R/3 operating system process type. The values are derived from the Percent_Found, Total_Processes_Expected, and Total_Processes_Found fields in the Process Totals table. To open the Availability Process graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Availability_Process graph icon. To continue your investigation From the graph menu, choose Graph Type, Line to investigate historical analysis of operating system process availability.

205 Chapter SAP Agent Investigating SAP R/3 Workload Distribution Use the SAP agent to analyze resource usage and throughput across R/3 instances to determine whether the R/3 System workload is optimally distributed. To optimize performance, distribute the load across the CPU resources of all available servers. Use the View Editor to identify non-optimal load distribution by comparing the CPU and memory resources used, response times, work process usage, and user levels across your R/3 application servers. Use the Dialog Response Overview graph or the Total Response Overview graph to analyze response time, throughput, and user load and work process usage levels on an R/3 application server. Topics Investigating Application Server Dialog Response Investigating Application Server Total Response Investigating Application Server Dialog Response Use the Dialog Response Overview graph to analyze Dialog response time, throughput, and work process usage levels per R/3 application server. Start with the Dialog Response Overview Graph Use the Dialog Response Overview graph to assess the different factors that have a negative influence on dialog response time and throughput. Drill down on the WP Utilization Dialog data point to analyze work process usage with the Work Process graph. Drill down on the Avg. Response Time Dialog or Avg. DB Request Time Dialog data point to analyze the breakdown of Dialog response time with the Task type Workload graph. SAPR3 Dialog Response Overview Graph Use the Dialog Response Overview graph to assess the different factors that have a negative influence on dialog response time and throughput. The values are derived from the Average_CPU_Time_Dialog, Average_DB_Request_Time_Dialog, Average_Response_Time_Dialog, Number_Dialog_Steps_Dialog, and WP_Utilization_Dialog fields in the Workload Overview table. To open the Dialog Response Overview graph

206 206 Foglight for SAP NetWeaver v2.6 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_DIALOG_Resp_Overview graph icon. To continue your investigation Drill down on the WP Utilization Dialog data point to analyze work process utilization with the Work Process graph. Drill down on the Avg. Response Time Dialog or Avg. DB Request Time Dialog data point to analyze the breakdown of dialog response time with the Task Type Workload graph. Investigating Application Server Total Response The Total Response Overview graph provides a single display to analyze total response time, throughput, and user load for an application server. Start with the Total Response Overview Graph Use the Total Response Overview graph to assess the different factors that negatively impact Dialog response time and throughput. Drill down on the Avg. Response Time Total or Avg. DB Request Time Total data point to analyze the breakdown of response time by task type with the Task Type Workload graph. SAPR3 Total Response Overview Graph Use the Total Response Overview graph to assess the different factors negative impacting Dialog response time and throughput. The values are derived from the Average_CPU_Time_Dialog, Average_DB_Request_Time_Total, Average_Response_Time_Total, and Number_Dialog_Steps_Total fields in the Workload Overview table, as well as the Total_Users field in the Total User Table.

207 Chapter SAP Agent To open the Total Response Overview graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Total_Resp_Overview graph icon. To continue your investigation Drill down on the Avg. DB Request Time Total or Average Response Time Total bar to get a task type breakdown with the Task Type Workload graph. Investigating SAP R/3 Task Type Workload The SAP agent alerts you when the average response time for a task type exceeds the user-defined threshold. The agent provides response time breakdown by task type. If a Dialog step exceeds the user-defined response time threshold during the collection interval, Dialog step details are written to the SAPR3_Long_Steps table for historical analysis. Start with the Task Type Workload Graph The Task Type Workload graph displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per task type. Drill down on the Avg DB Request Time bar for a task type to get a DB Request Time breakdown with the Task Type DB Calls graph. From the Task Type DB Calls graph, drill down on the Number Database Calls bar to investigate database time. The Task Type DB Calls graph opens. Drill down on the Avg Wait Time bar for a task type to analyze work process utilization with the Work Process graph. Drill down on the Avg Load Time bar for a task type to investigate R/3 Buffer utilization with the Buffers graph. Drill down on the Number Dialog Steps bar for a task type to isolate your analysis to a single task type with the Task Type Workload graph. Choose Graph Type, Line from the graph menu for a historical analysis. Use the Data Browser to analyze further task type details including task type load with the Workload By Task Type table. Use the Data Browser to view dialog step exception details with the Long Steps table. This table is populated when a dialog step exceeds the userdefined response time threshold.

208 208 Foglight for SAP NetWeaver v2.6 SAPR3 Task Type Workload Graph The Task Type Workload graph displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per task type. The values are derived from the Average_CPU_Time, Average_DB_Request_Time, Average_Load_Time, Average_Response_Time, Average_Wait_Time, and Number_Dialog_Steps fields in the Workload By Task Type table. To open the Task Type Workload graph Drill down on the Avg. DB Request Time Total or Average Response Time Total bar of the Total Response Overview graph, OR Drill down on the Avg. Response Time Dialog or Avg. DB Request Time Dialog data point of the Dialog Response Overview graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Tasktype_Workload graph icon. To continue your investigation Drill down on the Avg. DB Request Time bar for a task type to get a DB Request Time breakdown with the Task Type DB Calls graph. Drill down on the Avg. Wait Time bar for a task type to analyze work process usage with the Work Process graph.

209 Chapter SAP Agent Drill down on the Avg. Load Time bar for a task type to investigate R/3 Buffer usage with the Buffers graph. To isolate your analysis to a single task type, drill down on the Number Dialog Steps bar for a task type, then choose Graph Type, Line from the graph menu for a historical analysis. Use the Data Browser to analyze further task type details, including task type load, with the Workload By Task Type table. Use the Data Browser to view dialog step exception details with the Long Steps table. This table is populated when a Dialog step exceeds the user-defined response time threshold. SAPR3 Task Type DB Calls Graph The Task Type DB Calls graph displays the number of database calls, database requests, direct reads, sequential reads, and changes per task type. The values are derived from the Number_Changes, Number_Database_Calls, Number_Database_Requests, Number_Direct_Reads, and Number_Sequential_Reads fields in the DB Load By Task Type table. To open the Task Type DB Calls graph Drill down on the Avg. DB Request Time bar of the Task Type Workload graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Tasktype_DBcalls graph icon. To continue your investigation

210 210 Foglight for SAP NetWeaver v2.6 Drill down on the Number Database Calls bar for a task type to investigate database time with the Task Type DB Time graph. SAPR3 Task Type DB Time Graph The Task Type DB Time graph displays the time per DB request, sequential read time, direct read time, and changes and commit time per millisecond for a task type. The values are derived from the Time_Per_Change, Time_Per_DB_Request, Time_Per_Direct_Read, Time_Per_Sequential_Read fields in the DB Load By Task Type table. To open the Task Type DB Time graph Drill down on the Number Database Calls bar of the Task Type DB Calls graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Tasktype_DBtime graph icon. Investigating SAP R/3 Transaction Workload The SAP agent provides response time breakdown by monitored transaction. You can monitor a business critical or custom transaction independently. The SAP agent alerts you when the average response time for a transaction exceeds the user-defined threshold.

211 Chapter SAP Agent Start with the SAPR3 Transaction Workload Graph The Transaction Workload graph displays, in milliseconds, the average response time, CPU time, DB request time, wait time, and load time. It also displays the number of dialog steps per transaction. Drill down on the Avg. DB Request Time bar for a transaction to get a DB Request Time breakdown with the Trans DB Calls graph. From the Trans DB Calls graph, drill down on the Number Database Calls bar to investigate database time. The Trans DB Time graph opens. Drill down on the Avg. Wait Time bar for a transaction to analyze work process utilization with the Work Process graph. Drill down on the Avg. Load Time bar for a transaction to investigate R/3 Buffer utilization with the Buffers graph. Drill down on the Number Dialog Steps bar for a transaction to isolate your analysis to a single transaction with the Trans Workload graph. Choose Graph Type, Line from the graph menu for a historical analysis. Use the Data Browser to analyze further transaction details including transaction load with the Workload By Transaction table. Use the Data Browser to view dialog step exception details with the Long Steps table. This table is populated when a dialog step exceeds the userdefined response time threshold. SAPR3 Transaction Workload Graph The Transaction Workload graph displays, in milliseconds, the average response time, CPU time, DB request time, wait time, and load time. It also displays the number of dialog steps per transaction. The values are derived from the Average_CPU_Time, Average_DB_Request_Time, Average_Load_Time, Average_Response_Time, Average_Wait_Time, and Number_Dialog_Steps fields in the Workload By Transaction table. To open the Transaction Workload graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Trans_Workload graph icon.

212 212 Foglight for SAP NetWeaver v2.6 To continue your investigation Drill down on the Avg. DB Request Time bar for a transaction to get a DB Request Time breakdown with the Transaction DB Calls graph. Drill down on the Avg. Wait Time bar for a transaction to analyze work process usage with the Work Process graph. Drill down on the Avg. Load Time bar for a transaction to investigate R/3 Buffer usage with the Buffers graph. Use the Data Browser to analyze further transaction details including transaction load with the Workload By Transaction table. To isolate your analysis to a single transaction, drill down on the Number Dialog Steps bar for a transaction, then choose Graph Type, Line from the graph menu for a historical analysis. SAPR3 Transaction DB Calls Graph The Transaction DB Calls graph displays the number of database calls, database requests, direct reads, sequential reads, and changes per transaction. The values are derived from the Number_Changes, Number_Database_Calls, Number_Database_Requests, Number_Direct_Reads, and Number_Sequential_Reads fields in the DB Load By Transaction table. To open the Transaction DB Calls graph Drill down on the Avg. DB Request Time bar of the Transaction Workload graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Trans_DBcalls graph icon.

213 Chapter SAP Agent To continue your investigation Drill down on the Number Database Calls bar for a transaction to investigate database time with the Transaction DB Time graph. SAPR3 Transaction DB Time Graph The Transaction DB Time graph displays the time per DB request, sequential read time, direct read time, and changes and commit time per millisecond for a transaction. The values are derived from the Time_Per_Change, Time_Per_DB_Request, Time_Per_Dirsect_Read, and Time_Per_Sequential_Read fields in the DB Load By Transaction table. To open the SAPR3 Transaction DB Time graph Drill down on the Number Database Calls bar of the Transaction DB Calls graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Trans_DBtime graph icon.

214 214 Foglight for SAP NetWeaver v2.6 Investigating SAP R/3 Program Workload The SAP agent alerts you when the average response time for a program exceeds the user-defined threshold. In an R/3 environment, custom programs may not be associated with a Tcode. For example, custom programs may be executed directly from transactions se38, sa38, or report trees. Monitoring workload activity only at the task type or transaction level does not let you monitor resource usage on an individual custom program. For this reason, the SAP agent provides response time breakdown by monitored program. Because you can specify a business-critical or custom program using wild card substitution, you can monitor programs in Z* and Y* customer name space independently. In this manner, custom-developed programs are subject to proper quality assurance procedures, and you can track response time over the performance of the entire system. Start with the Program Workload Graph The Program Workload graph displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per monitored program. Drill down on the Avg. DB Request Time bar for a program to get a DB Request Time breakdown with the Program DB Calls graph. From the SAPR3 Program DB Calls graph, drill down on the Number Database Calls bar to investigate database time. The Program DB Time graph opens. Drill down on the Avg. Wait Time bar for a program to analyze work process usage with the Work Process graph.

215 Chapter SAP Agent Drill down on the Avg. Load Time bar for a program to investigate R/3 Buffer usage with the Buffers graph. Drill down on the Number Dialog Steps bar for a program to isolate your analysis to a single program with the Program Workload graph, then choose Graph Type, Line from the graph menu for a historical analysis. Use the Data Browser to analyze further program details, including program load with the Workload by Program table. SAPR3 Program Workload Graph The Program Workload graph displays the average response time, CPU time, DB Request time, Wait time, and Load time in milliseconds and number of dialog steps per monitored program. The values are derived from the Average_CPU_Time, Average_DB_Request_Time, Average_Load_Time, Average_Response_Time, Average_Wait_Time, and Number_Dialog_Steps fields in the Workload By Program table. To open the Program Workload graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Program_Workload graph icon. To continue your investigation Drill down on the Avg. DB Request Time bar for a program to get a DB Request Time breakdown with the Program DB Calls graph. Drill down on the Avg. Wait Time bar for a program to analyze work process usage with the Work Process graph. Drill down on the Avg. Load Time bar for a program to investigate R/3 Buffer usage with the Buffers graph. To isolate your analysis to a single program, drill down on the Number Dialog Steps bar for a program, then choose Graph Type, Line from the graph menu for a historical analysis. Use the Data Browser to analyze further program details including program load with the Workload By Program table. SAPR3 Program DB Calls Graph The Program DB Calls graph displays the number of database calls, database requests, direct reads, sequential reads, and changes per program. The values are derived from the Number_Changes, Number_Database_Calls, Number_Database_Requests,

216 216 Foglight for SAP NetWeaver v2.6 Number_Direct_Reads, Number_Sequential_Reads fields in the DB Load By Program table. To open the Program DB Calls graph Drill down on the Avg. DB Request Time bar of the Program Workload graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Program_DBCalls graph icon. To continue your investigation Drill down on the Number Database Calls bar for a program to investigate database time with the Program DB Time graph. SAPR3 Program DB Time Graph The Program DB Time graph displays the time per DB request, sequential read time, direct read time, and changes and commit time per millisecond for a program. The values are derived from the Time_Per_Change, Time_Per_DB_Request, Time_Per_Direct_Read, and Time_Per_Sequential_Read fields in the DB Load By Program table. To open the Program DB Time graph Drill down on the Number Database Calls bar of the Program DB Calls graph, OR Click the SAPR3 agent icon and double-click the SAPR3_Program_DBTime graph icon.

217 Chapter SAP Agent Investigating Sessions and Users The SAP R3 Users graph displays total number of users and sessions. The values are derived from the Total_Sessions and Total_Users fields in the SAPR3 Total User table. To open the Users graph 1 Click the SAP agent icon. A list of graph icons displays. 2 Double-click the SAPR3_Users graph icon.

218 218 Foglight for SAP NetWeaver v2.6 Using Cross-Host Views In order to maximize the ROI and exploit all of the information collected by Foglight, it is recommended to create custom views during Foglight implementation and bind them to the SAP Map. Suggested cross-host custom views comparing the SAP R/3 response time, users, dialog work process utilization, CPU and memory utilization are recommended. The following table lists suggested views. Suggested view: SAPR3_System_User_Overview SAPR3_System_Dialog_Resp_Overvie w SAPR3_System_Total_Resp_Overview SAPR3_System_Total_Steps_Overview SAPR3_System_Dialog_Steps_Overvie w SAPR3_System_Dialog_WP_Util_ Overview SAPR3_System_CPU_Util_Overview SAPR3_System_OS_Memory_Overvie w Using: Total_Users in the SAPR3_Total_Users table from the SAP agent. Average_Response_Time_Dialog in the SAPR3_Workload_Overview table from the SAP agent. Average_Response_Time_Total in the SAPR3_Workload_Overview table from the SAP agent. Number_Dialog_Steps_Total in the SAPR3_Workload_Overview table from the SAP agent. Number_Dialog_Steps_Dialog in the SAPR3_Workload_Overview table from the SAP agent. Using WP_Utilization_Dialog in the SAPR3_Workload_Overview table from the SAP agent. CPU_Utilization in the Client table from Sun_System or HPUX_System agents. Using Scan_Rate and Available_Swap in the Client table from the Sun_System or HPUX_System agents.

219 Chapter SAP Agent SAP Rules Availability Connection Rule Availability Process Rule Average Response Time Rule Buf Free Dir Entries Rule Buffer Free Space Rule Buffer Hit Ratio Rule Console Rule Dispatch Request Waiting Rule Extended Memory Used Rule Long Enqueue Locks Rule Long Running Process Rule Paging Memory Used Rule Process Complete Rule Process Stopped Rule Process Utilization Rule Program Average Response Time Rule Roll Memory Used Rule Tcode Average Resp Time Rule Availability Connection Rule The SAP Availability Connection Rule monitors the ability to connect to a SAP R/3 instance. Code Level Action SAP.SAPR3_Server_RFC_Availability. RFC_Availability < 100 Fatal Log message Open the SAPR3 Availability Graph to get started with an investigation into R/3 instance connectivity issues.

220 220 Foglight for SAP NetWeaver v2.6 Availability Process Rule The SAP Availability Process Rule monitors the availability of operating system processes for an SAP R/3 instance. Code Level Action SAP.SAPR3_Process_Totals.Percent_Found < 1 Fatal Log message SAP.SAPR3_Process_Totals.Percent_Found < 100 Warning Log message Open the SAPR3 Availability Process Graph to get started with an investigation into operating system process availability issues. Average Response Time Rule The SAP Average Response Time Rule determines when the average response time for a task type is too high. Code Level Action SAP.SAPR3_Workload_By_Task_Type.Average_ Response_Time >= 3000 SAP.SAPR3_Workload_By_Task_Type.Average_ Response_Time >= 2000 Critical Warning Log message Log message Open the SAPR3 Task Type Workload Graph to get started with an investigation into operating system process availability issues. Buf Free Dir Entries Rule The SAP Buf Free Dir Entries Rule determines when the space available for R/3 buffer objects is low. Code Level Action

221 Chapter SAP Agent SAP.SAPR3_Buffers.Directory_Entries_Free_Percent <= 2 SAP.SAPR3_Buffers.Directory_Entries_Free_Percent <= 15 Critical Warnin g Log message Log message Open thesapr3 Buffers Graph to get started with an investigation into issues pertaining to R/3 buffer object space. Buffer Free Space Rule The SAP Buffer Free Space Rule determines when the R/3 buffer free memory space is low. Code Level Action SAP.SAPR3_Buffers.Free_Space_Percent <= 2 Critical Log message SAP.SAPR3_Buffers.Free_Space_Percent <= 15 Warning Log message Open the SAPR3_Buffers Table to get started with an investigation into the R/3 buffer free memory. Buffer Hit Ratio Rule The SAP Buffer Hit Ratio Rule determines when the R/3 buffer hit ratio is low. Code Level Action SAP.SAPR3_Buffers.Buffer_Hit_Ratio <= 80 Critical Log message SAP.SAPR3_Buffers.Buffer_Hit_Ratio <= 90 Warning Log message Open the SAPR3 Buffers Graph to get started with an investigation into the R/3 buffer hit ratio.

222 222 Foglight for SAP NetWeaver v2.6 Console Rule The SAP Console Rule detects monitored error conditions from the SAP R/3 system log. Code Level Action SAP.SAPR3_System_Log.Severity == "FATAL" Fatal Log message SAP.SAPR3_System_Log.Severity == "CRITICAL" Critical Log message SAP.SAPR3_System_Log.Severity == "WARNING" Warning Log message Open the SAPR3_System_Log Table to get started with an investigation into error conditions listed on the system log. Dispatch Request Waiting Rule The SAP Dispatch Request Waiting Rule detects when a dispatcher queue has a high number of currently waiting user requests. Code Level Action SAP.SAPR3_Dispatch_Queue.Request_Waiting >= 3 Warning Log message Open the SAPR3 Dispatch Queue graph to get started with an investigation into currently waiting user requests. Extended Memory Used Rule The SAP Extended Memory Used Rule determines when R/3 extended memory is near capacity. Code Level Action

223 Chapter SAP Agent SAP.SAPR3_Extended_Memory.Currently_Used_Percen t >= 95 SAP.SAPR3_Extended_Memory.Currently_Used_Percen t >= 80 Critical Warnin g Log message Log message Open the SAPR3_Extended_Memory Table to get started with an investigation into issues pertaining to R/3 extended memory. Long Enqueue Locks Rule The SAP Long Enqueue Locks detects if any R/3 locks are being held too long. Code Level Action SAP.SAPR3_Enqueue_Total_Locks.Long_Locks >= 1 Warning Log message Open the SAPR3 Locks Graph to get started with an investigation into R/3 locks that are being held too long. Long Running Process Rule The SAP Long Running Process Rule detects when the executing dialog step for a work process has a long run time. Code Level Action SAP.SAPR3_Process_Overview.Long_Running > (0.2 * SAP.SAPR3_Process_Overview.Total) && SAP.SAPR3_Process_Overview.Process_Type == "DIA" Warning Log message Open the SAPR3 Work Process Graph or SAPR3 Work Process Stopped Graph to get started with an investigation into work processes with long run times.

224 224 Foglight for SAP NetWeaver v2.6 Paging Memory Used Rule The SAP Paging Memory Used Rule determines when R/3 paging area memory is near capacity. Code Level Action SAP.SAPR3_Paging_Area_Memory.Currently_Used_Per cent >= 95 SAP.SAPR3_Paging_Area_Memory.Currently_Used_Per cent >= 80 Critical Warnin g Log message Log message Open the SAPR3_Paging_Area_Memory Table to get started with an investigation into R/3 paging area memory capacity. Process Complete Rule The SAP Process Complete Rule detects if any work processes are in Complete status. The rule code displays in the table below. Code Level Action SAP.SAPR3_Process_Overview.Completed >= 1 Critical Log message Open the SAPR3_Process_Overview Table to get started with an investigation into work processes in Complete status. Process Stopped Rule The SAP Process Stopped Rule detects when the percent of work processes in Stopped status is too high. Code Level Action SAP.SAPR3_Process_Overview.Stopped >= (0.4 * SAP.SAPR3_Process_Overview.Total) Critical Log message

225 Chapter SAP Agent Open the SAPR3 Work Process Graph or SAPR3 Work Process Stopped Graph to get started with an investigation into work processes in Stopped status. Process Utilization Rule The SAP Process Utilization Rule determines when the percent of work processes in stopped status is too high. Code Level Action SAP.SAPR3_Process_Overview.Utilization == 100 && (SAP.SAPR3_Process_Overview.Process_Type == "DIA" SAP.SAPR3_Process_Overview.Process_Type == "UPD" SAP.SAPR3_Process_Overview.Process_Type == "UP2") Critical Log message Code Level Action SAP.SAPR3_Process_Overview.Utilization >= 90 && (SAP.SAPR3_Process_Overview.Process_Type == "DIA" SAP.SAPR3_Process_Overview.Process_Type == "UPD" SAP.SAPR3_Process_Overview.Process_Type == "UP2") Warning Log message Open the SAPR3 Work Process Graph, the SAPR3 Work Process Stopped Graph, or the SAPR3_Process_Overview Table to get started with an investigation into process utilization issues. Program Average Response Time Rule The SAP Program Average Response Time Rule determines when the average response time for a monitored program is too high. Code Level Action

226 226 Foglight for SAP NetWeaver v2.6 SAP.SAPR3_Workload_By_Program.Average_ Response_Time >= 5000 SAP.SAPR3_Workload_By_Program.Average_ Response_Time >= 3500 Critical Warning Log message Log message Open the SAPR3 Program Workload Graph to get started with an investigation into average response times that are too high. Roll Memory Used Rule The SAP Roll Memory Used Rule determines when R/3 roll area memory is near capacity. Code Level Action SAP.SAPR3_Roll_Area_Memory.Currently_Used_Perc ent >= 95 SAP.SAPR3_Roll_Area_Memory.Currently_Used_Perc ent >= 80 Critical Warning Log message Log message Open the SAPR3_Roll_Area_Memory Table to get started with an investigation into R/ 3 roll area memory capacity. Tcode Average Resp Time Rule The SAP Tcode Average Resp Time Rule determines when the average response time for a monitored transaction is too high. Code Level Action SAP.SAPR3_Workload_By_Transaction.Average_Respon se_time >= 2500 SAP.SAPR3_Workload_By_Transaction.Average_Respon se_time >= 1500 Critical Warning Log message Log message

227 Chapter SAP Agent Open the SAPR3 Transaction Workload Graph to get started with an investigation into R/3 locks that are being held too long.

228 228 Foglight for SAP NetWeaver v2.6 SAP Agent Tables The SAP agent stores data in the following tables in the Foglight Database. Click the the hyperlinks to view field descriptions. SAPR3_Application_Servers Table SAPR3_Buffers Table SAPR3_DB_Load_By_Program Table SAPR3_DB_Load_By_Task_Type Table SAPR3_DB_Load_By_Transaction Table SAPR3_Dispatch_Queue Table SAPR3_Enqueue_Long_Lock_Detai l Table SAPR3_Enqueue_Total_Locks Table SAPR3_Extended_Memory Table SAPR3_Heap_Memory Table SAPR3_Instance_Totals Table SAPR3_Long_Steps Table SAPR3_Paging_Area_Memory Table SAPR3_Process_CPU Table SAPR3_Instance_Totals Table SAPR3_Process_Detail Table SAPR3_Process_Exception_Detail Table SAPR3_Process_Overview Table SAPR3_Process_Totals Table SAPR3_Roll_Area_Memory Table SAPR3_Server_RFC_Availability Table SAPR3_Process_Detail Table SAPR3_Special_Users Table SAPR3_System_Log Table SAPR3_Total_Users Table SAPR3_Workload_By_Program Table SAPR3_Workload_By_Task_Type Table SAPR3_Workload_By_Transaction Table SAPR3_Workload_Overview Table

229 Chapter SAP Agent SAPR3_Application_Servers Table The following table describes the fields in the SAPR3_Application_Servers table. FIELD Availability Host_Name Server_Name System_Name Type DESCRIPTION The availability of application servers. The name of the host. The name of the server. The name of the system. The type of server. SAPR3_Buffers Table The following table describes the fields in the SAPR3_Buffers table. Field Allocated Buffer_Hit_Ratio Buffer_Name Buffer_Swap Database_Accesses Description The amount of memory area allocated for the respective buffer in kilobytes. Percentage of data accesses that are satisfied by the buffer and do not require database accesses during the sampled period. The name of the R/3 buffer. The number of buffer objects displaced from the buffer during the sampled period. The number of database accesses, including the number of data transfers from the database into the buffer during the sampled period.

230 230 Foglight for SAP NetWeaver v2.6 Directory_Entries_Free_Percent Directory_Entries_Used Directory_Size_Entries Free_Space_Percent Space_Used The percent difference of the current number of objects stored in a buffer and the maximum possible number of objects. The current number of objects stored in a buffer. The maximum number of objects that can be stored in a buffer. The percent of free memory space available for the respective buffer. Current used memory space for the respective buffer in kilobytes. SAPR3_DB_Load_By_Program Table The following table describes the fields in the SAPR3_DB_Load_By_Program table. Field Number_Changes Number_Database_Calls Number_Database_ Requests Number_Direct_Reads Number_Sequential_Reads Program Description The number of database changes per program during the sampled period. The number of parsed requests sent to the database per program during the sampled period. The number of logical ABAP/4 requests for data in the database per program during the sampled period. The number of database direct reads per program during the sampled period. The number of database sequential reads per program during the sampled period. The name of the monitored program.

231 Chapter SAP Agent Time_Per_Change Time_Per_DB_Request Time_Per_Direct_Read Time_Per_Sequential_Read The time per change in milliseconds per program during the sampled period. The time per database request in milliseconds per program during the sampled period. The time per direct read in milliseconds per program during the sampled period. The time per sequential read in milliseconds per program during the sampled period. SAPR3_DB_Load_By_Task_Type Table The following table describes the fields in the SAPR3_DB_Load_By_Task_Type table. Field Number_Changes Number_Database_Calls Number_Database_ Requests Number_Direct_Reads Number_Sequential_Reads Task_Type Time_Per_Change Description The number of database changes per task type during the sampled period. The number of parsed requests sent to the database per task type during the sampled period. The number of logical ABAP/4 requests for data in the database per task type during the sampled period. The number of database direct reads per task type during the sampled period. The number of database sequential reads per task type during the sampled period. The task type: Total, Dialog, Batch, Update, Spool, or RFC. The time per change in milliseconds per task type during the sample period.

232 232 Foglight for SAP NetWeaver v2.6 Time_Per_DB_Request Time_Per_Direct_Read Time_Per_Sequential_Rea d The time per database request in milliseconds per task type during the sampled period. The time per direct read in milliseconds per task type during the sampled period. The time per sequential read in milliseconds per task type during the sampled period. SAPR3_DB_Load_By_Transaction Table The following table describes the fields in the SAPR3_DB_Load_By_Transaction table. Field Number_Changes Number_Database_Calls Number_Database_Requests Number_Direct_Reads Number_Sequential_Reads Time_Per_Change Time_Per_DB_Request Time_Per_Direct_Read Description The number of database changes per transaction during the sampled period. The number of parsed requests sent to the database per transaction during the sampled period. The number of logical ABAP/4 requests for data in the database per transaction during the sampled period. The number of database sequential reads per transaction during the sampled period. The number of database sequential reads per transaction during the sampled period. The time per change in milliseconds per transaction during the sampled period. The time per database request in milliseconds per transaction during the sampled period. The time per direct read in milliseconds per transaction during the sampled period.

233 Chapter SAP Agent Time_Per_Sequential_Read Transaction_Code The time per sequential read in milliseconds per transaction during the sampled period. The name of the monitored transaction. SAPR3_Dispatch_Queue Table The following table describes the fields in the SAPR3_Dispatch_Queue table. Field Maximum_Request_ Waiting Request_Read Request_Type Request_Waiting Request_Written Description The maximum number of user requests waiting at any one time since the R/3 instance was started - high water mark. The number of user requests dispatched to a work process. The type of work process. A dispatcher queue exists for each work process type: Dialog, Batch, Enqueue, Update, Update 2, or Spool. The number of currently waiting user requests. The number of user requests received by the dispatcher. SAPR3_Enqueue_Long_Lock_Detail Table The following table describes the fields in the SAPR3_Enqueue_Long_Lock_ Detail table. Field Backup_Flag_for_Lock_ Entry Description The backup flag for the lock entry.

234 234 Foglight for SAP NetWeaver v2.6 Client Counter_1 Counter_2 Lock_Argument Lock_Date Lock_Mode Lock_Time Object_Name Origin_Host Owner_1 Owner_2 The SAP client. Cumulative counter for a lock entry. Cumulative counter for lock entry. The argument (key fields) of the lock entry. The date when the lock was set. Indicates if the lock is shared. If the lock object is shared, then more than one user at a time may lock the same data. The time when the lock was set. The name of the lock object in the lock entry. The host name of the application server where the lock was generated. The owner of the lock, ID of logical unit of work (LUW). The owner of the lock, ID of logical unit of work (LUW). System_Number The SAP system number for the monitored R/3 instance. Table_Name Transaction_Code User_Name WP_Number The name of the table in which rows are locked. The transaction holding the lock. The name of the SAP user holding the lock. The number of the work process holding the lock.

235 Chapter SAP Agent SAPR3_Enqueue_Total_Locks Table The following table describes the fields in the SAPR3_Enqueue_Total_Locks table. Field Local_Locks Local_Long Locks Long_Locks Description The number of lock entries for local clients and users. The number of lock entries for local clients and users held longer than the user-defined threshold during the sampled period. The number of lock entries for all clients and all users. The number of lock entries for all clients and users held longer than your defined threshold during the sampled period. SAPR3_Extended_Memory Table The following table describes the fields in the SAPR3_Extended_Memory table. Field Currently_Used Currently_Used_Percent In_Memory Maximum_Use Description The amount of Extended Memory currently used in kilobytes. The percent of Extended Memory currently used. The amount of memory allocated to Extended Memory in kilobytes. The maximum amount of Extended Memory that has been used since the R/3 instance was started - high water mark in kilobytes.

236 236 Foglight for SAP NetWeaver v2.6 SAPR3_Heap_Memory Table The following table describes the fields in the SAPR3_Heap_Memory table. Field Currently_Used Maximum_Use Description The amount of heap memory currently used in kilobytes. The maximum amount of heap memory that has been used since the R/3 instance was started - high water mark in kilobytes. SAPR3_Instance_Totals Table The following table describes the fields in the SAPR3_Instance_Totals table. Field Application_Server_Name Availability Instance_Name Percent_CPU Percent_Memory Description The configuration of the SAP instance. The name consists of SAP system name (SID), the work process configuration, the SAP system number, and server host name. The ability to connect to the monitored R/3 instance via an RFC connection. A value of 100 means the connection was successful; a value of 0 means the connection was not successful. The name of the SAP instance. The name consists of the server host name, the SAP system name (SID), and the SAP system number. The percent of CPU resources used for all the OS processes of the R/3 instance. The percent of memory used for all the OS processes for the R/3 instance.

237 Chapter SAP Agent System_Name The SAP system name (SID). System_Number The SAP system number for the monitored R/3 instance. Virtual_Set_Size The total size of the instance (memory and swap). SAPR3_Long_Steps Table The following table describes the fields in the SAPR3_Long_Steps table. Field Average_Roll_In_Times Average_Roll_Out_Time Bytes_Requested CPU_Time DB_Request_Time Dispatch_Time Description Average roll-in time in milliseconds per dialog step. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per dialog step. Roll-out time is the amount of time required to roll out user context information from the work process to the roll buffer or roll file. The amount of kilobytes transferred per dialog step. CPU time in milliseconds per dialog step. CPU time for a dialog step is the amount of CPU time spent to process the request. Database request time in milliseconds per dialog step. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns a result. Dispatch time in milliseconds per dialog step. Dispatch time is the amount of time the request occupies a work process (response time - wait time).

238 238 Foglight for SAP NetWeaver v2.6 End_Date End_Time Enqueue_Time Load_Time Number_Of_Roll_Ins Number_Of_Roll_Outs Program Response_Time Screen Task_Type Transaction_Code User Wait_Time The end date of the dialog step. The end time of the dialog step. Load time in milliseconds per dialog step. Load time is the amount of time required to load programs, CUA interface, and screen information from the database. Load time in milliseconds per dialog step. Load time is the amount of time required to load programs, CUA interface, and screen information from the database. The number of roll-ins per dialog step. The number of roll-outs per dialog step. The program name of the dialog step. Response time in milliseconds per dialog step. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. The screen number of the dialog step. The task type: Dialog, Batch, and Update of the dialog step. The transaction code of the dialog step. The name of the user who executed the dialog step. Wait time in milliseconds per dialog step. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing.

239 Chapter SAP Agent SAPR3_Paging_Area_Memory Table The following table describes the fields in the SAPR3_Paging_Area_Memory table. Field Currently_Used Currently_Used_Percent In_Memory Maximum_Use On_Disk Description The amount of Paging Area Memory currently used in kilobytes. The percent of Paging Area Memory currently used. The amount of memory allocated to Paging Area Memory in kilobytes. The maximum amount of Paging Area Memory that has been used since the R/3 instance was started - high water mark in kilobytes. The size of the file (if any) in kilobytes that is part of this area and is located on the application server disk. SAPR3_Process_CPU Table The following table describes the fields in the SAPR3_Process_CPU table. Field CPU Number Process_Type Description The amount of CPU utilized by the work process since R/3 instance startup. The R/3 work process number. The work process type: Dialog, Batch Enqueue, Update, Update 2, or Spool.

240 240 Foglight for SAP NetWeaver v2.6 SAPR3_Process_Detail Table The following table describes the fields in the SAPR3_Process_Detail table. Field Percent_CPU Percent_Memory Process Process_ID Process_Unique Resident_Set_Size Uptime Virtual_Set_Size Description The percent of CPU resources that this OS process used for the monitored R/3 instance. The percent of memory that this OS process used for the monitored R/3 instance. The name of the monitored R/3 OS process. The process ID of this R/3 OS process. The unique name of the monitored OS process. The name consists of the process ID and process name. How much of the OS process is in memory in KB. The number of hours the R/3 OS process has been running. The total size of the OS process (memory and swap). SAPR3_Process_Exception_Detail Table The following table describes the fields in the SAPR3_Process_Exception_Detail table. Field Accessed_Table Description The name of the table that was last accessed by the work process. CPU The amount of CPU utilized by the work process since R/3 instance startup.

241 Chapter SAP Agent Current_Activity Errors Executing_User Execution_Time Number PID Process_Type Reason_For_Wait Report_Running SAP_Client Semaphore Status If a work process is in a running status, this is the current action being executed. The number of times that an error has occurred for the work process that may have terminated the work process. The SAP user executing the current dialog step. The amount of processing time for the current request utilizing the work process. The R/3 work process number. The R/3 work process OS PID. The work process type: Dialog, Batch, Enqueue, Update, Update 2, and Spool. The reason for the wait time if a work process is in a Stopped status. The ABAP/4 program or report currently executing in the work process. The SAP client of the session currently executing. Indicates the semaphore number on which the work process is waiting. The status of the work process: Waiting, Running, and Stopped. SAPR3_Process_Overview Table The following table describes the fields in the SAPR3_Process_Overview table. Field Description

242 242 Foglight for SAP NetWeaver v2.6 Completed The number of work processes by type where Status = Complete. CPIC The number of work processes by type where Status = Stopped and Reason = CPIC. DB Action Load Long_Running The number of Dialog, Batch, and Update or Update 2 work processes where Action = Direct Read, Sequential Read, Insert, Update, Delete, or Commit. The number of dialog work processes where Action = Load Report. The number of dialog work processes where the execution time has exceeded the ASP parameter Work Process Execution Time Threshold. PRIV The number of work processes by type where Status = Stopped and Reason = PRIV. Process_Type Roll The work process type: Dialog, Batch, Enqueue, Update, Update 2, or Spool. The number of dialog work processes where Action = Roll-in or Roll-out. Running The number of work processes by type where Status = Running. Stopped The number of work processes by type where Status = Stopped. Total Utilization The total number of work processes configured by type for the R/3 instance. The percent of work processes being utilized by type: (running/total) * 100.

243 Chapter SAP Agent SAPR3_Process_Totals Table The following table describes the fields in the SAPR3_Process_Totals table. Field Application_Server_Name Percent_CPU Percent_Found Percent_Memory Process Resident_Set_Size Total_Processes_Expected Total_Processes_Found Virtual_Set_Size Description The name of the SAP instance. The name consists of the server host name, the SAP system name (SID) and the SAP system number. The percent of CPU resources that all the OS processes of this type use for the monitored R/3 instance. The ratio of found-to-expected OS processes of this type. The percent of memory that all the OS processes of this type use for the monitored R/3 instance. The name of the monitored R/3 OS process. How much of the OS process is in memory in KB. The number of OS processes of this type that are expected to be running, based on R/3 instance profile. The actual number of OS processes of this type that were found to be running for the monitored R/3 instance. The total size of the OS process (memory and swap). SAPR3_Roll_Area_Memory Table The following table describes the fields in the SAPR3_Roll_Area_Memory table. Field Description

244 244 Foglight for SAP NetWeaver v2.6 Currently_Used Currently_Used_Percent In_Memory Maximum_Used On_Disk The amount of Roll Area Memory currently used in kilobytes. The percent of Roll Area Memory currently used. The amount of memory allocated to Roll Area Memory in kilobytes. The maximum amount of Roll Area Memory that has been used since the R/3 instance was started - high water mark in kilobytes. The size of the file (if any) in kilobytes that is part of the area and is located on the application server disk. SAPR3_Server_RFC_Availability Table The following table describes the fields in the SAPR3_Server_RFC_Availability table. Field Host_Name Instance_Name RFC_Availability System_Name System_Number Description The host name where the R/3 instance is running. The name of the SAP instance. The name consists of the server host name, the SAP system name (SID) and the SAP system number. The ability to connect to the monitored R/3 instance via an RFC connection. A value of 100 means the connection was successful; a value of 0 means the connection was not successful. The SAP system name (SID). The SAP system number for the monitored R/3 instance.

245 Chapter SAP Agent SAPR3_Special_Users Table The following table describes the fields in the SAPR3_Special_Users table. Field Client Name Description The SAP client number of the SAP* or DDIC user. The name of the SAP* or DDIC user. SAPR3_System_Log Table The following table describes the fields in the SAPR3_System_Log table. Field Category Log_Time Message_Number Program Severity Text User User_Message Description The error message classes. The time the log entry was written. The log message code associated with the type of log event. The name of the program. Foglight severity level associated with the R/3 error generated to the Foglight event log. The value is defined in the ASP log filter parameter. The message text associated with the type of log event. The SAP user who caused the log entry. User message text associated with the R/3 error generated to the Foglight event log. The value is defined in the ASP log filter parameter.

246 246 Foglight for SAP NetWeaver v2.6 SAPR3_Total_Users Table The following table describes the fields in the SAPR3_Total_Users table. Field Total Sessions Total Users Description Total number of user sessions. Total number of logged on users. SAPR3_Workload_By_Program Table The following table describes the fields in the SAPR3_Workload_By_Program table. Field Average_CPU_Time Average_DB_Request_ Time Average_Dispatch_Time Average_Enqueue_Time Description Average CPU time in milliseconds per program during the sampled period. CPU time for a dialog step is the amount of time a user request sits in the dispatcher queue until beginning of processing. Average database request time in milliseconds per program during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result. Average dispatch time in milliseconds per program during the sampled period. Dispatch time is the amount of time the request occupies a work process (response time - wait time). Average enqueue time in milliseconds per program during the sampled period. Enqueue time is the time during which a work process sets an enqueue request.

247 Chapter SAP Agent Average_Load_Time Average_Response_Time Average_Roll_In_Time Average_Roll_Out_Time Average_Wait_Time Bytes_Requested Number_Dialog_Steps Number_Of_Roll_Ins Number_Of_Roll_Outs Program Average load time in milliseconds per program during the sampled period. Load time is the amount of time required to load programs, CUA interface and screen information from the database. Average response time in milliseconds per program during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average roll-in time in milliseconds per program during the sampled period. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per program during the sampled period. Roll-out time is the amount of time required to roll out user context information from the work process to the roll buffer or roll file. Average wait time in milliseconds per program during the sampled period. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing. The amount of kilobytes transferred within the system per program during the sampled period. The number of dialog steps executed per program during the sampled period. The number of roll-ins per program during the sampled period. The number of roll-outs per program during the sampled period. The name of the monitored program.

248 248 Foglight for SAP NetWeaver v2.6 Field Total_CPU_Time Total_DB_Request_Time Total_Response_Time Total_Wait_Time Description Total CPU time in seconds per program during the sampled period. Total database request time in seconds per program during the sampled period. Total response time in seconds per program during the sampled period. Total wait time in seconds per program during the sampled period. SAPR3_Workload_By_Task_Type Table The following table describes the fields in the SAPR3_Workload_By_Task_Type table. Field Average_CPU_Time Average_DB_Request_ Time Average_Dispatch_Time Description Average CPU time in milliseconds per task type during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average database request time in milliseconds per task type during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result. Average dispatch time in milliseconds per task type during the sampled period. Dispatch time is the amount of time the request occupies a work process (response time - wait time).

249 Chapter SAP Agent Average_Enqueue_Time Average enqueue time in milliseconds per task type during the sampled period. Enqueue time is the time during which a work process sets an enqueue request.

250 250 Foglight for SAP NetWeaver v2.6 Field Average_Load_Time Average_Response_Time Average_Roll_In_Time Average_Roll_Out_Time Average_Wait_Time Bytes_Requested Number_Dialog_Steps Description Average load time in milliseconds per task type during the sampled period. Load time is the amount of time required to load programs, CUA interface, and screen information from the database. Average response time in milliseconds per task type during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average roll-in time in milliseconds per task type during the sampled period. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per task type during the sampled period. Roll-out time is the amount of time required to roll out user context information to the work process from the roll buffer or roll file. Average wait time in milliseconds per task type during the sampled period. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing. The amount of kilobytes transferred within the system per task type during the sampled period. The number of Dialog steps executed per task type during the sampled period.

251 Chapter SAP Agent Field Number_Of_Roll_Ins Number_Of_Roll_Outs Task_Type Total_CPU_Time Total_DB_Request_Time Total_Response_Time Total_Wait_Time Description The number of roll-ins per task type during the sampled period. The number of roll-outs per task type during the sampled period. The task type: Total, Dialog, Batch, Update, Spool, or RFC. Total CPU time in seconds per task type during the sampled period. Total database request time in seconds per task type during the sampled period. Total response time in seconds per task type during the sampled period. Total wait time in seconds per task type during the sampled period. SAPR3_Workload_By_Transaction Table The following table describes the fields in the SAPR3_Workload_By_Transaction table. Field Average_CPU_Time Description Average CPU time in milliseconds per task type during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request.

252 252 Foglight for SAP NetWeaver v2.6 Average_DB_Request_ Time Average_Dispatch_Time Average database request time in milliseconds per transaction during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result. Average dispatch time in milliseconds per transaction during the sampled period. Dispatch time is the amount of time the request occupies a work process (response time - wait time).

253 Chapter SAP Agent Field Average_Enqueue_Time Average_Enqueue_Time Average_Load_Time Average_Response_Time Average_Roll_In_Time Average_Roll_Out_Time Average_Wait_Time Bytes_Requested Description Average enqueue time in milliseconds per task type during the sampled period. Enqueue time is the time during which a work process sets an enqueue request. Average enqueue time in milliseconds per task type during the sampled period. Enqueue time is the time during which a work process sets an enqueue request. Average load time in milliseconds per task type during the sampled period. Load time is the amount of time required to load programs, CUA interface, and screen information from the database. Average response time in milliseconds per transaction during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average roll-in time in milliseconds per transaction during the sampled period. Roll-in time is the amount of time required to roll in user context information to the work process from the roll buffer or roll file. Average roll-out time in milliseconds per transaction during the sampled period. Roll-out time is the amount of time required to roll out user context information from the work process to the roll buffer or roll file. Average wait time in milliseconds per transaction during the sampled period. Wait time is the amount of time a user request sits in the dispatcher queue until the beginning of processing. The amount of kilobytes transferred within the system per transaction during the sampled period.

254 254 Foglight for SAP NetWeaver v2.6 Number_Dialog_Steps Number_Of_Roll_Ins Number_Of_Roll_Outs Total_CPU_Time The number of dialog steps executed per transaction during the sampled period. The number of roll-ins per transaction during the sampled period. The number of roll-outs per transaction during the sampled period. Total CPU time in seconds per transaction during the sampled period.

255 Chapter SAP Agent Field Total_DB_Request_Time Total_Response_Time Total_Wait_Time Transaction_Code Description Total database request time in seconds per transaction during the sampled period. Total response time in seconds per transaction during the sampled period. Total wait time in seconds per transaction during the sampled period. The name of the monitored transaction. SAPR3_Workload_Overview Table The following table describes the fields in the SAPR3_Workload_Overview table. Field Average_CPU_Time_Dialog Average_CPU_Time_Total Average_DB_Request_Time _Dialog Description Average CPU time in milliseconds for task type Dialog during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average CPU time in milliseconds for task type Total during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. Average database request time in milliseconds for task type Dialog during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result.

256 256 Foglight for SAP NetWeaver v2.6 Average_DB_Request_Time _Total Average database request time in milliseconds for task type Total during the sampled period. Database request time measures the time a user request spends in the database, from when the request is put through the database interface until the database interface returns the result.

257 Chapter SAP Agent Field Average_Response_Time_ Dialog Average_Response_Time_ Total Number_Dialog_Steps_ Dialog Number_Dialog_Steps_Total WP_Utilization_Dialog Description Average response time in milliseconds for task type Dialog during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. Average response time in milliseconds for task type Total during the sampled period. Response time is measured from the time a request is put into the dispatcher queue to the time the result is returned. The response time between the SAPGUI and the dispatcher is not included in this value. The number of dialog steps executed for task type Dialog during the sampled period. The number of dialog steps executed for task type Total during the sampled period. The percent of work processes being utilized for Dialog type (running / total) * 100.

258 258 Foglight for SAP NetWeaver v2.6

259 Glossary A Accessed Table The name of the table that was last accessed by the work process. This maps to the In Accessed_Table column in the SAPR3_Process_Exception_Detail Table. Allocated (KB) The maximum amount of memory area that can be occupied by the respective buffer, as defined by the parameter limiting the buffer size. This maps to the Allocated column in the SAPR3_Buffers Table. Allocated Memory (KB) The amount of main memory allocated to this area at system startup. This maps to the In_Memory column in the SAPR3_Extended_Memory Table. Allocated Memory (KB) The amount of memory allocated to Paging Area Memory in kilobytes. This maps to the In_Memory column in the SAPR3_Paging_Area_Memory Table. Allocated Memory (KB) The amount of memory allocated to Roll Area Memory in kilobytes. This maps to the In_Memory column in the SAPR3_Roll_Area_Memory Table. Avg. CPU Time (ms) Average CPU time in milliseconds per program during the sampled period. CPU time for a dialog step is the amount of time a user request sits in the dispatcher queue until beginning of processing. This maps to the Average_CPU_Time column in the SAPR3_Workload_By_Program Table. Avg. CPU Time (ms) Average CPU time in milliseconds per task type during the sampled period. CPU time for a dialog step is the amount of CPU time spent to process the request. This maps to the Average_CPU_Time column in the SAPR3_Workload_By_Task_Type Table.