Transaction Transaction ST03N
Global Workload Monitor Purpose The Global Workload Monitor (transaction ST03G) display statistical records for entire landscapes and therefore therefore allows you to analyze statistics data for both SAP R/3 and non-SAP R/3 systems. You can use this data to analyze the workload of the monitored components in great detail. The monitor is organized as a one-screen transaction so that its operation is very intuitive, and so that you can query all desired data with only a few mouse clicks. While statistics records for an SAP R/3 system can only trace actions that are processed by SAP R/3 components, components, you can use Distributed Statistics Records (DSRs) to trace actions that are processed across the non-SAP R/3 components J2EE Engine, ITS, and BC. This also works across component boundaries. Components Components that write statistics records send data from the statistics record with their communication with other components (their “passport”), meaning that the originator of an action or a data flow of a business process can be traced even beyond component boundaries. The DSRs are first stored locally on the relevant component and are transferred to a monitoring system hourly by CCMS agents, agents, where the aggregated statistical data is stored in a performance database and regularly reorganized. Integration o
o
The operation of the global workload monitor is largely similar to the operation of the SAP R/3 workload monitor (transaction monitor (transaction ST03N), ST03N), which displays statistical data for the local ABAP system. The Global Workload Monitor actually actually uses functions of the SAP R/3 W orkload orkload Monitor when you analyze the workload of SAP R/3 Systems. The Global Workload Monitor displays statistical data aggregated by the collector. You can display raw statistical data (individual records) from SAP R/3 and non-SAP R/3 Systems from complex system landscapes using the functional trace (transaction STATTRACE). STATTRACE). The functional trace offers a finer resolution. You can use the functional trace to trace actions that belong to a business process across system boundaries.
The differences between the functional trace and the Global Workload Monitor are explained in the section Difference Between the Functional Trace and the Global Workload Monitor . Monitor . Features You can perform the following analyses, among others, in the Global Workload Monitor: o
How is the workload distributed among the individual service types? (For more information about service types, see
Displaying the Workload Overview.) Overview .)
o
What is the workload of individual actions?
o
How is the workload distributed over the individual hours of the day?
o
Which action steps have the longest response and wait time?
o
What workload data is created when calling external components?
o
What is the workload of individual users and which actions has a user performed?
o
What workload is created in a component on the basis of actions of external components?
o
o
What is the response time distribution for individual service types (required, for example, for Service Level Agreements)? What is the availability of the statistical data for the individual components?
The following applies to all of these analyses:
Page: 1 of 5
File: 130452986.doc
Transaction ST03N
o
You can choose the period for which you want to display data between day, week, and month, or specify the
o
Last Minutes’ Load as you require.
You can display data for any component or optionally totaled for all components of a type.
See also:
Operating the Global Workload Monitor Configuring/Self-Monitoring of the Global Workload Workload Collector Monitor
Page: 2 of 5
Monitor
File: 130452986.doc
Transaction ST03N
The ST03 Workload Monitor is the central access point for analyzing performance problems in the SAP system. ST03N is a revised version of transaction ST03. In current SAP Releases transaction ST03N replaces transaction ST03 and is automatically started when you enter transaction code ST03. Here you can compare the performance values for all instances, and compare the performance of particular instances over a period of time. Due to the number of possible analysis views for the data determined in transaction ST03, you can quickly determine the cause of performance problems. You can use the workload monitor to display the following, among other things: • • • •
• • • • • • • •
Number of instances configured for your system Number of users working on the different instances Response time distribution Distribution of workload by transaction steps, transactions, packages, subapplications, and applications Transactions with the largest response times and database time Memory usage for each transaction or each user per dialog step Workload caused by RFC, broken down by transactions, function modules, and destinations Number and volume of spool requests Statistics about response time distribution, with or without the GUI time Optional: table accesses Workload and transactions used by users, broken down by users, accounting numbers, and clients Workload generated by requests from external systems
Calling up transaction •
Switch to advanced mode.
•
Choose an analysis period.
•
Choose an analysis view.
•
Look at the DB time. It should not be more than 40% of the response time.
The following are important analysis views in transaction ST03: • •
•
System load overview: general response time distribution across different task types Time profile: How does the response time react over the day? Are there peak times with bad response times? Transaction profile: Can you observe response time problems in general or only in certain transactions?
ST03 Workload Overview:
Page: 3 of 5
File: 130452986.doc
Transaction ST03N
Important information in
are time and transaction profile as well.
In the Workload Monitor you can also determine which transactions have accessed which database tables and how often. Since the number of statistics records greatly increases by logging table accesses of this t ype, this option is deactivated by default.
You should only activate it temporarily for individual analyses, and for individual transactions, since performance problems can occur in the statistics collector otherwise.
Refer to the SAP documentation in http://help.sap.com/ for more documentation on this transaction. Because of the inherent complexity of the SAP ERP system, system performance depends upon many factors. Factors such as the operating system, network, database and SAP configuration itself contribute to the system performance. SAP system comes with tools for system performance monitoring. Several SAP transactions are available to monitor the performance. Some of the important ones are mentioned below: 1. ST03N - Workload Monitor 2. SM50 / SM66 - Work Process Overview 3. ST06 - Operating System Performance 4. ST04 - Database Monitor 5. ST02 - Setup Buffers The above are some of the central monitoring transactions used in SAP R3 performance analysis. To move a bit in detail, transaction ST06 can provide valuable information on the operating system performance at the server level. CPU usage, memory allocation etc can be looked at in detail using this transaction. SQL request on the underlying system database can be monitored using ST04 i.e. the database monitor. In real Page: 4 of 5
File: 130452986.doc
Transaction ST03N life instances, many factors can be responsible for slow SAP system performance. The root cause normally is not that apparent. In some cases due to peak workload, even system administrators will not be able to call transactions. In such rare cases, it is better to use tools at the operating system to solve performance problems.
Page: 5 of 5
File: 130452986.doc
