SAP Library - Find your answers

With this monitor, you can perform availability monitoring for selected ABAP and Java systems and their instances. For ABAP systems, you can also monitor the availability of logon groups, and the most important performance attributes for the status of the dialog system are also displayed for the monitored ABAP instances.

For more information about selecting systems and application servers for monitoring, see Configuring Availability Monitoring.

Description of the Tree Structure of the Monitor

Prerequisites

Availability monitoring uses the standalone agent CCMSPING, you must therefore have performed the installation of the availability agent CCMSPING.

Features

Availability of Systems

For availability monitoring, CCMSPING checks the availability of the message server of the corresponding system. A system is regarded as available if the responsible message server responds to the availability agent’s query and at least one application server is registered as active with the message server. The system availability is monitored by one or more CCMSPING agents, depending on the configuration of your availability monitoring.

In the case of ABAP+Java systems, if you have specified both message servers in the configuration of the availability monitoring, both availability values are displayed here.

Availability of ABAP Instances

The monitor displays the following MTEs for the monitored ABAP instances:

For more information about the performance values for the dialog system, see Dialog Overview Monitor.

Availability of Java Instances

Java instances are displayed under different names, depending on which message server (ABAP or Java) is used for the availability monitoring of the system:

· In the case of monitoring purely using the ABAP message server, Java instances are displayed under the name of the assigned ABAP instance with the suffix :Java (such as: Host1_C11_00:Java). This is only possible if the relevant system is a double-stack system).

· In the case of monitoring using the Java message server, Java instances of the relevant system are displayed under their server ID with the prefix J2EE (such as J2EE7305550). This is also the case, if the monitoring is performed using both message servers.

The monitor displays the following MTEs for the monitored Java instances:

Availability of Logon Groups

In the case of ABAP systems, you can monitor logon groups for their availability. A logon group is regarded as available, if it is possible to log on to the application server with the best dialog system quality in this group. In addition to the availability of the logon groups in the last 15 minutes, the system also displays the application server of the group with the best dialog system quality in the monitor.

Analysis Method

If you double-click a node in this monitor, you start the analysis method Configure Availability and Performance Overview. (see Configuring Availability Monitoring).

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Availability and Performance Overview monitor from the list by double-clicking it.

Use

Performance attributes (symbol ) are monitoring attributes that collect certain reported performance data and calculate the average.

Features

In the display of the properties and methods, performance attributes have a number of special characteristics that are described here. To display the properties of a performance attribute, choose the attribute in the alert monitoring tree and choose Properties.

Comparison Value

Threshold values

In this group box, you can edit the threshold values with which an alert is triggered if the reported value exceeds or falls below the appropriate value. Note when doing so that the change applies not only to the concrete monitoring tree element (MTE), but for the whole MTE class. This is displayed at the top of the screen.

You have the option to assign different threshold values for a Change from GREEN to YELLOW and the Reset from YELLOW to GREEN (the same also applies for the Change from YELLOW to RED and the Reset from RED to YELLOW). This prevents a constant switching between the alert levels, if the attribute is wavering around the threshold value, which would generate a new alert every time.

The display of a rule of this type would look as shown in the graphic below. To find out the alert level, start from any value for the performance attribute and move upwards until you meet the curve. If the value is climbing from a lower alert level, the lower part of the curve is valid for determining the alert; if the value is falling from a higher alert level, the upper part of the curve is used.

The unit of the threshold value is determined using the data supplier.

Explanation for an Alert

If an alert is triggered, it is displayed in the Alert Browser. A short explanatory text for the alert is displayed there in the Alert Text column. Choose the relevant line of an alert and choose F1 to display a more detailed text about the alert. The system displays its short text and the associated message class and number here. You can use these to adjust the delivered message texts.

he Central Performance History of the monitoring architecture allows you to save performance values of the monitoring architecture long-term, and to output these values in reports to compare the current performance data with its earlier development.

The system only collects values for the MTE classes that you have selected for this purpose. You do this by assigning MTE classes to Collection and Reorganization Schemata. These schemata contain information about how long, and in which resolution, performance values should be collected. To obtain an overview of this type of which data is collected in the Central Performance History, you required the collection and reorganization schemata that are assigned to the individual nodes.

The view displays the following information:

· Assigned collection and reorganization schema

· Resolution of the collected performance values

· Collection method (see Collecting and Reorganizing Performance Values)

· Time zone of the data collection (if explicitly specified)

Procedure

To activate the Central Performance History technical view, follow the procedure below:

...

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Expand the monitor set that contains the monitor that you require, and choose Load Monitor.

3. Choose Views ® Collect./Reorg.Schema Assignment, or choose Display Assignments of the Central Performance History (). The alert tree now no longer displays the alert status and reported values, but the assigned Collection and Performance Schemata.

Displaying Central Performance History Reports

Use

You can output Central Performance History (CPH) reports in a number of different ways (see Scheduling and Executing a Report). One of the possibilities is direct output to the screen.

You can also display at any time reports that you have saved in the database. When you do this, the report is not executed again using the report definition, but rather the previously executed report is displayed, with the performance values from the original execution.

The displayed report is identical in both cases.

Procedure

1. You can display a report that is saved in the database from several functions:

¡ In the overview screen of the CPH (transaction RZ23N), choose, in the Reporting group box, the Report Browser pushbutton.

¡ On the screen for scheduling and executing reports (Central Performance History Report Execution), choose Goto® Report Browser.

2. In both cases, the Display Central Performance History Reports screen appears. On the left half of the screen, the system displays all executed reports, grouped by the name under which the reports are stored in the database:

<Date>,

,

By default, the name specified above is the name of the report definition; you can, however, also explicitly specify a name when Scheduling and Executing a Report under which the corresponding report execution is to be grouped in the Report Browser.

3. Expand the desired report definition and select the desired time point of the report execution by double clicking it. Choose the desired report on the right of the screen.

If you display a report directly on the screen, the report is output identically.

4. There are two display modes for displaying reports: one-dimensional and two-dimensional. Choose the Switch Display Mode pushbutton to switch between the two modes. The display modes have the following properties:

5. If you want to display the header data of the report, choose Report Details (see Displaying Report Properties).

Central Performance History of the Monitoring Architecture start page

Keyword: BASIS
Title : Increasing liveCache Performance

Troubleshooting SAP Performance Issues

Is there a document that will help me troubleshoot system performance? What are the steps on how to troubleshoot?

Troubleshooting is a BIG task of itself, there is no single reference document because there are too many reasons why a system can appear "slow" to the user:

- Different Databases

Every database has its own mechanism for optimizing access, even more, each database has BOOKS on performance optimization. This can start from parameters to database layout to operating system configuration, used filesystems, mount parameters...

- Different Operating System

The same goes for operating systems, a standard Windows 2000 (or 2003) isn´t configured for optimal throughput, there is a LOT to tune, e. g. enable "background process priorities", stop non-needed services, network configurations (TCP window sizes) etc. Also the connection between application and database servers can be an issue

- SAP Itself

Almost for each and every long running program there are optimizations, be it on ABAP layer or on selection layer. Out of my experience, most self developed programs (Z*-programs) are the main issue, because developers program "quick-and-dirty"
doing "select *" and other things.

For e.g.:
If CPU is 100% Busy, what action should be taken to keep CPU idle?

This can't be answered generally. One need to check what process is using so much CPU - then one can start digging deeper. To add info regarding this issue, you may use:

st06->details analysis menu->snapshot analysis->top CPU from there, start to narrow down.

SAP System Performance Issues

My server becomes slow when more users login.
What could be the reason? Is it because of less hardware resource?

Server configuration is 104GB HDD, 2GB Ram.
OS:Win 2003 server.
Database:Oracle.

I manage SAP R/3 4.6C systems on Risc 6000 machines, under Oracle 9.2.

The overall performance problem for me is to know if SAP response time is acceptable ; if not, do this :
- at AIX level : utilities are topas, to catch what's wrong : Disk I/O ? CPU bottleneck ? Too much swap ?
- at Oracle level : tkprof but don't know much about this.
- at SAP level : you can manage SAP memory, Oracle and OS too.

If SAP response time is acceptable, then try this :

Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.

Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.

Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads / logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo logging.

I use this kind of procedure to manage my systems.

SAP Tips by: Christophe Rabeau

It depends how much you allocated for SGA (database buffers, shared pool buffer, redo log buffers), how much you allocated for SAP buffers esp. Program buffers and whether the server have any other external processes/programs running.

How many Dialog Work Processes you allocated…I think your problem most likely is you don’t have enough of these Dialog processes. Also maybe users running inefficient reports/programs which are holding the Dialog processes, goto SM50 & check all DIA (Dialog) with status “waiting”…if ALL are “running” then you have wait time (problems !) for other users wanting to process transactions .

To troubleshoot performance, you need these tcode tools:-

ST04 – Database ß in here, check especially for Expensive SQLs (Detail Analysis à SQL Request)

ST02 – SAP buffers

ST06 – OS stats

ST05 – SQL trace

SE30 – Abap runtime analysis

SAP Tips by: Derek Phung

A few step which you can exercise to sort/identify performance issues.

* ST03, ST02, ST04 are the tcode for workload, tuning and DB Performance Monitoring codes.

* ST06 FOR Operation System Monitoring.

** SM51 OR SM50 is process overview which tells you the workprocess sequence. ( Ideally 10-15 process with OLTP and batch process scheduled at peak and off peak times respectively) say 8-17 hrs and 17-8 hrs for Batch Process)

Operation Mode can be configured in RZ04 tcode.

** Check for top CPU in ST06 tcode. CPU should not exceed more than 60% for long time for any process.

** Based of No. of instances ( Application Servers ) should have adequately sized.

** Most resources intensive process have to be scheduled in Batch Process ( in Background in Non Peak Hours )

** Look for unnecessary Jobs Active During Prime Time
** Look for Parameters Set To Your Business Process.
( RZ10, RZ11 ) Check Snote:0124361

** Refer Early Watch Alert Periodically for Overall System Performance.. ( Tcode SDCC )

Is there a document that will help me troubleshoot system performance? What are the steps on how to troubleshoot?

Troubleshooting is a BIG task of itself, there is no single reference document because there are too many reasons why a system can appear "slow" to the user:

- Different Databases

Every database has its own mechanism for optimizing access, even more, each database has BOOKS on performance optimization. This can start from parameters to database layout to operating system configuration, used filesystems, mount parameters...

- Different Operating System

The same goes for operating systems, a standard Windows 2000 (or 2003) isn´t configured for optimal throughput, there is a LOT to tune, e. g. enable "background process priorities", stop non-needed services, network configurations (TCP window sizes) etc. Also the connection between application and database servers can be an issue

- SAP Itself

Almost for each and every long running program there are optimizations, be it on ABAP layer or on selection layer. Out of my experience, most self developed programs (Z*-programs) are the main issue, because developers program "quick-and-dirty"
doing "select *" and other things.

For e.g.:
If CPU is 100% Busy, what action should be taken to keep CPU idle?

This can't be answered generally. One need to check what process is using so much CPU - then one can start digging deeper. To add info regarding this issue, you may use:

st06->details analysis menu->snapshot analysis->top CPU from there, start to narrow down.

My server becomes slow when more users login.
What could be the reason? Is it because of less hardware resource?

Server configuration is 104GB HDD, 2GB Ram.
OS:Win 2003 server.
Database:Oracle.

I manage SAP R/3 4.6C systems on Risc 6000 machines, under Oracle 9.2.

The overall performance problem for me is to know if SAP response time is acceptable ; if not, do this :
- at AIX level : utilities are topas, to catch what's wrong : Disk I/O ? CPU bottleneck ? Too much swap ?
- at Oracle level : tkprof but don't know much about this.
- at SAP level : you can manage SAP memory, Oracle and OS too.

If SAP response time is acceptable, then try this :

Try to have a look at OS response time : ST06 : look at CPU, Memory, Swap, Disk and Lan response time.

Try to have a look at buffer quality : ST02, if many fields are red, investigate each fields dependant parameters.

Try to have a look at DB response time : ST04N, databuffer quality (SGA zone), how much physical reads / logical reads Ratio, wait times, number of user calls, Shared Pool cache hit ratio should be >96%, Sort usage, Redo logging.

I use this kind of procedure to manage my systems.

SAP Tips by: Christophe Rabeau

It depends how much you allocated for SGA (database buffers, shared pool buffer, redo log buffers), how much you allocated for SAP buffers esp. Program buffers and whether the server have any other external processes/programs running.

How many Dialog Work Processes you allocated…I think your problem most likely is you don’t have enough of these Dialog processes. Also maybe users running inefficient reports/programs which are holding the Dialog processes, goto SM50 & check all DIA (Dialog) with status “waiting”…if ALL are “running” then you have wait time (problems !) for other users wanting to process transactions .

To troubleshoot performance, you need these tcode tools:-

ST04 – Database ß in here, check especially for Expensive SQLs (Detail Analysis à SQL Request)

ST02 – SAP buffers

ST06 – OS stats

ST05 – SQL trace

SE30 – Abap runtime analysis

SAP Tips by: Derek Phung

A few step which you can exercise to sort/identify performance issues.

* ST03, ST02, ST04 are the tcode for workload, tuning and DB Performance Monitoring codes.

* ST06 FOR Operation System Monitoring.

** SM51 OR SM50 is process overview which tells you the workprocess sequence. ( Ideally 10-15 process with OLTP and batch process scheduled at peak and off peak times respectively) say 8-17 hrs and 17-8 hrs for Batch Process)

Operation Mode can be configured in RZ04 tcode.

** Check for top CPU in ST06 tcode. CPU should not exceed more than 60% for long time for any process.

** Based of No. of instances ( Application Servers ) should have adequately sized.

** Most resources intensive process have to be scheduled in Batch Process ( in Background in Non Peak Hours )

** Look for unnecessary Jobs Active During Prime Time
** Look for Parameters Set To Your Business Process.
( RZ10, RZ11 ) Check Snote:0124361

** Refer Early Watch Alert Periodically for Overall System Performance.. ( Tcode SDCC )

Evaluation Based on Completeness of Vision and Ability to Execute

PALO ALTO, Calif. and WALLDORF, Germany - December 22, 2008 - Business Objects, an SAP company (NYSE: SAP) and the world's leading provider of solutions that optimize business performance, today announced it has been positioned by Gartner, Inc. in the leaders quadrant of the "Magic Quadrant for Corporate Performance Management (CPM) Suites"1 report.

According to Gartner, "Leaders' performances excel in the CPM suite market segment. They can deliver breadth and depth of CPM suite functionality, as well as provide enterprisewide implementations to support a broad CPM strategy. Leaders successfully articulate a business proposition that resonates with buyers, and are supported by the viability and operational capability to deliver on a global basis."

Given the current economic climate, Business Objects believes that it is critical for organizations to have a comprehensive enterprise performance management (EPM) strategy that goes beyond finance and optimizes operational performance in all areas of the business. With its portfolio of EPM solutions, Business Objects provides customers with performance management capabilities that span the entire organization, giving them a holistic view of their business performance and the ability to quickly identify and address financial and operational challenges. The EPM portfolio from SAP and Business Objects enables profitable and compliant business performance.

In addition, Business Objects has an integrated solution that allows companies to define their business strategy while taking into account both external and internal risk factors. By combining the SAP® Strategy Management application with the SAP® GRC Risk Management application, Business Objects gives customers a way to enact a risk-adjusted approach to strategy. Particularly important given the current economy, companies can create their business plans while proactively addressing any risks that might inhibit their success, all as part of their daily business operations.

"We believe our leadership position in the Gartner Magic Quadrant for CPM Suites is a result of the synergies being achieved between SAP and Business Objects," said Anthony Reynolds, general manager, Enterprise Performance Management Solutions, Business Objects. "Since 2007, we have grown tremendously-growing more quickly than other EPM vendors. One of the cornerstones of our success, as well as a key differentiator, has been our vision for the convergence of EPM, GRC and BI. We understand that in order to respond quickly and effectively to changing business conditions, customers need a unified approach that includes all three business disciplines. Business Objects sees this report as a strong validation of our enterprise performance management vision and strategy, which has been developed in alignment with our customers."

Business Objects offers a broad and deep set of EPM solutions that cover the following areas: strategy management, business planning and consolidation, profitability and cost management, financial consolidation and spend analytics

1Gartner "Magic Quadrant for Corporate Performance Management (CPM) Suites" by Neil Chandler, Nigel Rayner, John E. Van Decker, Dec. 19, 2008.

About the Magic Quadrant
The Magic Quadrant is copyrighted December 2008 by Gartner, Inc. and is reused with permission. The Magic Quadrant is a graphical representation of a marketplace at and for a specific time period. It depicts Gartner's analysis of how certain vendors measure against criteria for that marketplace, as defined by Gartner. Gartner does not endorse any vendor, product or service depicted in the Magic Quadrant, and does not advise technology users to select only those vendors placed in the "Leaders" quadrant. The Magic Quadrant is intended solely as a research tool, and is not meant to be a specific guide to action. Gartner disclaims all warranties, express or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.

About Business Objects
Business Objects, an SAP company, transforms the way the world works by connecting people, information and businesses. With open, heterogeneous applications in the areas of governance, risk and compliance; enterprise performance management; and business intelligence, Business Objects enables organizations of all sizes worldwide to close the gap between business strategy and execution. Together with a strong and diverse partner network, Business Objects allows customers to optimize business performance across all major industries including banking, retail, consumer-packaged goods and public sector. Business Objects is committed to helping customers turn raw data into actionable decisions, regardless of their underlying database, operating system, applications or IT system.

For more information about Business Objects, visit: www.businessobjects.com.
For more information about SAP, visit: www.sap.com.

Any statements contained in this document that are not historical facts are forward-looking statements as defined in the U.S. Private Securities Litigation Reform Act of 1995. Words such as "anticipate," "believe," "estimate," "expect," "forecast," "intend," "may," "plan," "project," "predict," "should" and "will" and similar expressions as they relate to SAP are intended to identify such forward-looking statements. SAP undertakes no obligation to publicly update or revise any forward-looking statements. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. The factors that could affect SAP's future financial results are discussed more fully in SAP's filings with the U.S. Securities and Exchange Commission ("SEC"), including SAP's most recent Annual Report on Form 20-F filed with the SEC. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates.

Copyright © 2008 SAP AG. All rights reserved.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in several other countries. All other names mentioned herein may be trademarks of their respective owners.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serve informational purposes only. National product specifications may vary.

For customers interested in learning more about Business Objects products:
Global Customer Center: +49 180 534-34-24
United States Only: 1 (800) 872-1SAP (1-800-872-1727)

For more information, press only:
Scott Behles, SAP, +1 (917) 494-2009, scott.behles@sap.com, EST
SAP Press Office, +49 (6227) 7-46315, CET; +1 (610) 661-3200, EST; press@sap.com
Kimberly Cole, Burson-Marsteller, +1 917-325-4492, kimberly.cole@bm.com, EST
Nicole Urhahn-Schmitt, Burson-Marsteller, +49 (0)69 2 38 09-43, nicole.urhahn-schmitt@bm.com, CEST