Oracle Enterprise Manager SAP Monitoring Guide 10g Release 4 (10.2.0.4.0) E11037-02 February 2008 This document provides a brief introduction to SAP Monitoring using Oracle Enterprise Manager Grid Control. It guides you through the process of creating and configuring SAP Landscape targets and discusses SAP transactions. It covers the following sections: Introduction to SAP Monitoring with Oracle Enterprise Manager Grid Control Monitoring SAP Targets Installing NimBUS Server On Windows Configuring SAP Landscape Targets Reports SAP Metrics Troubleshooting SAP Monitoring 1 Introduction to SAP Monitoring with Oracle Enterprise Manager Grid Control This section covers the following topics: Overview New SAP-Specific Targets Additional Sources of Information System Requirements Installing Oracle Enterprise Manager Grid Control 10g Release 4 1.1 Overview The NimBUS SAP R/3 Plug-in for Oracle Enterprise Manager 10g provides multi-instance SAP R/3 monitoring designed to deliver comprehensive, efficient and vital health status information. The plug-in provides Enterprise Manager with performance metrics, availability and end-user experience monitoring for SAP R/3 applications. Figure 1 shows the various components of SAP monitoring and the connection between each. 1
Figure 1 SAP Monitoring Components 1.2 New SAP-Specific Targets Several new targets, as discussed in Table 1, have been added to Enterprise Manager in order to facilitate the management of SAP applications. These targets model the entities within an SAP environment so that they can be managed within Enterprise Manager. Table 1 New SAP-Specific Targets in Enterprise Manager Enterprise Manager Target SAP Entity Purpose SAP Landscape SAP Landscape Representation of SAP enterprise providing access to metrics and associated SAP servers. SAP Application Instance Server SAP Application Server Representation of SAP server providing access to related metrics and configuration information. SAP NimBUS SAP NimBUS Representation of NimBUS bus interacting with SAP 1.3 Additional Sources of Information Refer to the documentation listed in Table 2 for additional information about SAP monitoring. Because the SAP Monitoring leverages many of Enterprise Manager's underlying capabilities, the base documentation is applicable in many cases. 2
Table 2 Additional Documentation for the SAP Monitoring Book Chapter Information Enterprise Manager Concepts Guide All Overall information on the capabilities of Oracle Enterprise Manager Grid Control Enterprise Manager Grid Control Installation and Basic Configuration Enterprise Manager Advanced Configuration System Monitoring Information Publisher All All Sizing and Maximizing the Performance of Oracle Enterprise Manager Setting up Thresholds and Alerts Creating Custom Reports Installing Enterprise Manager Grid Control Server and Agents Advanced Configuration Topics Capacity Planning and Tuning for Oracle Enterprise Manager Refer to the URB below to access the documents mentioned in the table from Oracle Technology Network (OTN): http://www.oracle.com/technology/documentation/oem.html. 1.4 System Requirements Before you begin configuring Grid Control 10g Release 4 (10.2.0.4) to manage your SAP applications, you must install and configure Grid Control 10gR4 on at least one host computer on your network. Oracle recommends that you install the Grid Control components on their own host or hosts. For example, if the SAP monitoring middle tier is installed on host1.us.oracle.com, then install and configure the Oracle Management Service and Oracle Management Repository on host2.us.oracle.com. Install the Grid Control 10.4 Oracle Management Agent on every host that includes components that you want to manage with Grid Control. See Oracle Enterprise Manager Basic Installation and Configuration for Oracle Enterprise Manager Grid Control 10.2 at: http://www.oracle.com/technology/documentation/oem.html 1.5 Installing Oracle Enterprise Manager Grid Control 10g Release 4 Before you begin configuring Grid Control 10g Release 4 (10.2.0.4) to manage your SAP application, you must install and configure Grid Control 10g Release 2 (10.2.0.2) on at least one host computer on your network. Oracle recommends that you install the Grid Control components on their own host or hosts. For example, if the SAP is installed on host1.us.oracle.com, then install and configure the Oracle Management Service and Oracle Management Repository on host2.us.oracle.com. Install the Grid Control 10.2 Oracle Management Agent on every host that includes the components you want to manage with Grid Control. 3
Refer to Enterprise Manager Grid Control Installation and Basic Configuration guide for details on performing these steps. To enable the SAP Services tab: 1. Enable SAP Services tab under the Targets tab. The Preferences page appears. Click Preferences located at the top-right corner of the user interface. Click the Target Subtabs link located on the left pane. The Target Subtabs page appears. 2. Select SAP Services from Available Target Subtabs and move it to the Selected Target Subtabs by clicking the Move arrow. Your selection is moved. 3. Click Finish. 2 Monitoring SAP Targets Oracle Enterprise Manager Grid Control 10gR4 enables the monitoring of SAP R/3 applications along with other Oracle and non-oracle technologies through a single Oracle Enterprise Manager Grid Control console. It provides: Centralized, multi-tier, multi-instance SAP R/3 monitoring Discovery of SAP R/3 servers and instances for each monitored SID Comprehensive, efficient, and secure health status data collection End-user experience monitoring for SAP R/3 application modules SAP R/3 business service dashboards and performance trend reports Note: Use of this capability requires NimBus SAP Plug-in for Oracle Enterprise Manager 10g, available separately through NimSoft. Use of other Oracle Enterprise Manager capabilities may require additional licenses. 2.1 Prerequisites for Monitoring SAP Targets After deploying SAP, you must perform the following steps to monitor an SAP target by using Enterprise Manager Grid Control: 1. Install Enterprise Manager Grid Control with licenses. You must install EMGC 10.2.0.02 before you upgrade to 10.2.0.04. Refer to Installing Oracle Enterprise Manager Grid Control 10g Release 4 for details. 2. Obtain NimBUS SAP Plug-in for Oracle Enterprise Manager from NimSoft. 3. Install NimBUS in another box. Refer to Installing NimBUS Server for details. 4. Configure SAP monitoring probe. Refer to Configuring SAP Monitor Probe for details. 4
5. Create two queues, Alerts and Metrics, in the NimBUS bus, by using Doctor NimBUS, which comes with NimBUS. The queues should be named OEM_AGENTS and OEM_METRICS. Refer NimBUS documentation for more information. 6. Install Enterprise Manager 10g R4 agent on the machine where NimBUS is installed. 3 Installing NimBUS Server On Windows This section cover the following topics: NimBUS Server Installation Prerequisites Installing NimBUS Server SAP Monitoring Requirements Configuring SAP Monitor Probe 3.1 NimBUS Server Installation Prerequisites To install NimBUS Server on Microsoft Windows, you need a management station running Windows (2000/2003/XP) system with: Pentium III-class processor or better 512 Megabytes or more of memory, and 500 Megabytes of available disk space 3.2 Installing NimBUS Server Here is an overview of the steps for installing the NimBUS server: 1. On the management server, run NimBUS Server.exe. This initiates the installation of NimBUS Server, initialize the security system. When offered a selection of products, select NimBUS Availability Server and select Typical for Setup Type. When prompted for the NimBUS Domain Name, accept the default or enter one of your choice. Accept the default Hub name. When prompted for the Hub License, accept the default or copy and paste the license key you have been provided. The server installation begins. 2. As this is the initial installation, you have to provide an administrator password for the NimBUS server. The installation program now attempts to log into the newly initialized system. You must provide the NimBUS administrator user name and password you have provided. The installation continues and the NimBUS client are installed onto the management server. 3. Click Yes, when the confirmation message is displayed to install the NimBUS manager locally. When the final client installer is completed, the NimBUS Server installation is completed. 5
4. Launch the NimBUS Manager by returning to the NimBUS Server portal window. Refer NimBUS documentation for detailed installation instructions. 3.3 SAP Monitoring Requirements The requirements of SAP Monitor Probe for NimBUS are: Windows NT, Windows 2000, or Windows XP Installed NimBUS Function module in every monitored SAP R/3 system Installed and configured SAP GUI 3.4 Configuring SAP Monitor Probe To configure the SAP monitor probe: 1. Drag and drop the SAP Monitor probe from the Archive to the NimBUS Hub server (left hand navigation pane of the NimBUS Manager GUI. 2. Click the NimBUS Hub server icon in the navigation pane of the NimBUS Manager. Then, double click on the SAP-Monitor probe in the top right hand pane of the NimBUS Manager to bring up the configuration GUI. 3. Copy and paste the provided probe license key into the Key field on the Setup tab. Use the wizard to configure a new monitoring profile. 4 Configuring SAP Landscape Targets This section covers the following topics: Adding an SAP Landscape Removing Application Instances from an Existing Landscape 4.1 Adding an SAP Landscape SAP Landscape enables administrators to logically organize distributed targets for efficient and effective management and monitoring. To create an SAP Landscape, perform the following steps: 1. From the Enterprise Manager Console, click the Targets tab. 2. Click the SAP tab. 3. Click the Add button. The Add SAP Landscape page appears. 4. Define the values for all the parameters and click OK. The progress page notifies you when the SAP Landscape and its associated targets are created. 6
4.2 Removing Application Instances from an Existing Landscape After creating an SAP Landscape and associated targets, you may manually remove individual application instances from that Landscape. This, however, deletes the respective target information from the Enterprise Manager repository. After that entry is deleted, Enterprise Manager does not monitor that target anymore. The two possible paths for manually removing application instances from an existing Landscape are: Go to the All Targets tab, search for the application instances you want to delete, select the radio button next to the application instance, and click the Remove button. Go to the SAP Applications tab, select SAP Landscape View, navigate to the enterprise that you want to remove, select the radio button next to the enterprise name, and click the Remove button. This option removes the SAP server, targets, and all the application instances. 5 Reports With NimBUS and Enterprise Manager, you can either do real-time monitoring or historical monitoring. The administrators can then view these reports to monitor the health of targets. With each NimBUS installation, you must configure the SAP monitoring probe that provides metrics details to the NimBUS hub. When EM agent is installed, the agent receives the alerts and messages from the EM queue and stores the statistics in the EM repository. You have three options for types of reports: 24 hours - provides the statistics for last 24 hours Seven days - provides the statistics for a week 31 days - provides the statistics for last 31 days 6 SAP Metrics This section provides descriptions for all SAP metrics that are monitored by using NimBUS. The table lists and describes the metrics. Table 3 Metric SAP Metrics Maximum CPU Usage (%) Maximum DB time (ms) Maximum Dialog Response Time (ms) Actual Number of Users Description The maximum usage of CPU usage. Usage of database time for single dialog program. Average dialog response time. The current number of users logged in to the SAP system. There exists the current numbers of users system wide and for each application server instance 7
Table 3 Metric Maximum usage of extended memory (%) Minimum for program buffer hitratio (%) Waiting Queue for dialog process (Cont.) SAP Metrics Hit Ratio Table Definition Maximum% of memory paged out Maximum usage of roll area (%) Description The maximum usage of extended memory. Hitratio of Program buffer. The dispatcher queue that measures the number of dialog process requests waiting for a free dialog process. This should be zero in an optimally tuned landscape (SID). Hit ration table definition. Paging out rate. Maximum usage of roll area. 7 Troubleshooting SAP Monitoring This section describes common problems that you may encounter when monitoring and managing SAP Landscapes with Grid Control. It contains the following topics: Failure to Discover an SAP Landscape SAP NimBUS Target Down Status SAP Application Instance Target Down Status Certain Metrics Are Not Collected Failure to rediscover the SAP Landscape 7.1 Failure to Discover an SAP Landscape This section describes the discover an SAP landscape problem and provides the possible cause and solution. 7.1.1 Problem The SAP Landscape discovery fails and, consequently, Enterprise Manager does not create the corresponding SAP Landscape targets. 7.1.2 Possible Cause Agent box specified is not right. Name that you provided does not match the actual agent installed hostname. 7.1.3 Solution Provide the correct agent host name. 7.1.4 Possible Cause The specified install location for NimBUS is wrong. 8
7.1.5 Solution Ensure that the install location of NimBUS is provided correctly, as based on this the required SAP configuration file is parsed. Incorrect path would results in the file not found error. 7.1.6 Possible Cause The specified System name is incorrect 7.1.7 Solution The System name specified is required to determine the SAP instances information. The SAP system name specified is the SAP SID for the SAP environment. 7.2 SAP NimBUS Target Down Status This section describes SAP NimBUS target down status problem and provides the possible cause and solution. 7.2.1 Problem The NimBUS administrative password given is incorrect. 7.2.2 Solution Re-discover the target with correct password. 7.2.3 Possible Cause The NimBUS bus could be down 7.2.4 Solution Restart the NimBUS probes in the NimBUS manager console 7.3 SAP Application Instance Target Down Status This section describes SAP application instance target down status problem and provides the possible cause and solution. 7.3.1 Problem The SAP application instance target is down. 7.3.2 Possible Cause The NimBUS bus could be down. The NimBUS bus probes the status of each application instance at regular intervals. 7.3.3 Solution Restart the NimBUS probes in the NimBUS manager console. 7.4 Certain Metrics Are Not Collected This section describes the problem of some metrics not being collected and provides the possible cause and solution. 9
7.4.1 Problem The metrics are not collected. 7.4.2 Possible Cause The NimBUS bus could be down. The NimBUS bus probes the status of each application instance at regular intervals. 7.4.3 Solution Restart the NimBUS probes in the NimBUS manager console 7.4.4 Possible Cause The metric collection frequency to check in SAP maybe higher value.these informations are configurable under NimBUS update status console. 7.4.5 Solution Try changing the update intervals acceptable to SAP standard limit. 7.5 Failure to rediscover the SAP Landscape This section describes the failure to rediscover SAP landscape and provides the possible cause and solution. 7.5.1 Problem The SAP Landscape are not rediscovered. 7.5.2 Possible Cause The SAP Landscape deletion takes a while to be reported to OMS repository. Immediate rediscovery of SAP landscape after deletion will introduce inconsistent state in OMS and hence the error. 7.5.3 Solution Wait for a few minutes before re-discovering the targets. 8 Documentation Accessibility Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/ Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should 10
appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace. Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites. TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398. Oracle Enterprise Manager Grid Control Release Notes, 10g Release 4 (10.2.0.4.0) Getting Started Guide E11037-02 Copyright 2006, 2008 Oracle. All rights reserved. The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. 11
12