At the end of Performance Optimization article you will handle below sessions ;
BC315 - Workload Analysis
BC490 - Optimization of ABAP Programs
PART 1 - Overview to structure
Performance Management :
At the end of this part you will able to answer below questions;
1) Which preventative measures must be taken to guarantee the optimal performance ıf mySAP Solution ?
2) What performance tuning measures should be taken into consideration?
3) Who is involved to the tuning process?
- there is a plan for the continuous monitoring of availability and performance of the business process.
Service Level Management : is of central instance for long term monitoring and optimization.
Arranging Service Level Management : First you should come to Service Level Agreement in which you record which objectives are to be attained by the individual service partners.
SLM should be cover following agreements: Definition of business hours , Database backup and restoration , Performance , Content of reports
Performance: To reach a useful SLM , proceed as follows ;
1) Choose around 10 to 20 critical transactions
2) Measure the average response time of the transaction in production operation over a given period of time
3) Agree that weekly details on the response times for the selected transactions will be given in SLReporting.
4) Link the selected transactions to the CCMS
5) Agree that in the event threshold value is exceeded.
Problem Solving : In the Service Level Agreement you should set out priorities for errors and reaction times for problem solving. In communication between SAP and customers , four priorities are user (SAP NOTE: 67739) : Very High , High , Medium , Low.
You should also describe which error situations are to be monitored by the monitoring team these include: Interrupted updates , interrupted by processes , interrupted interface processes ( transactional RFC , queued RFC , IDOC , ALE)
Service Level Reporting :
Number of users logged on and number of tcode steps.
Average response time for dialog and update tasks.
Average response time during the hour with greatest system load.
CPU and main memory load during the hour with the greatest system load.
Size of DB and it's rate of growth.
Linking systems with RFC : Data can be exchanged between components using RFC. Data is converted into IDOCs and sent via RFC. With RFC components of different versions can communicate with each other.
User Connection : 3 ways ; a-SAP GUI (Windows , Java) , b-Web Browser in HTML format , c-Mobile Clients.
Client / Server Architecture : Presentation server ; once user has ended a data entry. Presentation Server sends data to the application level. Application level also forms the integrated Internet connection of the SAP Web Application Server. (SAP Web AS , from SAP BASIS 6.10)
Application logic is encapsulated in transactions, screens, reports or function modules.
Three possibilities for connecting Internet users to the SAP application level;
1) Use SAP Internet Transaction Server (ITS) and a Web Server provided by a third party. Typical SAP ITS applications are self-service applications in the area of human resources. (ESS applications such as time recording and travel accounting), B2B Procurement applications (Enterprise Buyer Professional), Internet Sales (Product catalog, online store in SAP R/3).
2) Business Server Pages (BSP) ; HTML Pages can be dynamically generated using ABAP or Javascript as the scripting language. Technical advantage of this programming is that no other software components need to be installed.
3) To use a JSP Server or a Java application server.
The Monitoring and Optimization Plan for a mySAP Solution :
1) Requirement of a Monitoring and Optimization mySAP Solution
Monitoring and Optimization Plan :
Responsibilities / Viewpoints
*Systems *Interfaces *Business Processes
2) Tools & Methods for the Monitoring and Optimization Plan
a) CCMS : Checks all components are available and work well. If not an alarm is triggered.
TCODE : RZ20
Define one SAP System as a central monitoring system and all reports of errors from all SAP components will be sent to this system. (databases , instances , operating systems and all other components such as SAP IT. Also for non-SAP components ; catalog software , Clarify & Commerce one.
b) Central Workload Monitor: Gives you an overview of the workload distribution in your mySAP Solution throughout all Software Components with a technical analysis. For ex: problems on database, in SAP Basis System or Internet transaction server can be identified and analyzed. In an application analysis , transactions , programs and users that generate hight system load can be identified and analyzed.
c) Expert Monitors for Performance Analysis :
TCODE : STUN
Monitors for technical analysis :
OS Monitor :
TCODE : ST06 Monitors the load on CPU & Physical Main Memory
Database Monitor :
TCODE : ST04 Check load on DB buffers , db locks andpther wait situations. Also monitors SQL treatments.
SAP Memory Configuration Monitor :
TCODE : ST02 Monitor the load on the SAP buffer and other memory areas SAP Work processes.
Work Process Overview :
TCODE : SM50 Monitor load on SAP Workflow.
Work Monitor :
TCODE : ST03 Overview of load distribution in the SAP System. In a technical analysis problems on DB, SAP Memory Management and SAP buffers.
Monitors for application analysis :
Work Monitor :
TCODE : ST03 , ST03N , ST03G
Single Record Statistics :
TCODE : STAD , STATTRACE Overview of load distribution, in a application analysis , transactions , programs and users that place a heavy load on the system can be identified and analyzed.
Application Monitors :
TCODE : ST07 , ST14 To monitor the use of resources according to SAP Modules.
SQL & ABAP Trace :
TCODE : ST05 , SE30 Trace functions for a detailed analysis of ABAP and SQL programs.
SAP Solution Manager :
SAP Solman is the portal for accessing these services and fives you centralized access to tools and services procedures for performance monitoring and optimization. Difference from Solution Monitoring , Solman focus on business processes.
Based on data, SAP SolMan draws up a service level report each week. Includes following functions;
Automated setup
Presentation of selected performance indicators , error messages , optimization advice for all components of a mySAP Solution. Based on the results of SAP Early Watch Alert Services.
Presentation of performance indicators , error messages and optimization recomendations, grouped according to system and according to business area.
Graphic presentation of the time spans of selected performance indicators, For Ex: Hardware Load.
Automatic generation of instruction and reference to other SAP services.
Continous Monitoring :
CCMS contains a monitor with which you can monitor all aspects of your mySAP Solution together with SAP SolMan this forms a complete solution for the continuous monitoring.
Working with Alert Monitor :
TCODE : RZ20 The system displays the CCMS monitor collections.
Plan for Continuous Performance Optimization :
1) Technical Tuning Actions : OS , DB , SAP Application Server & Networks.
2) Application Tuning Actions : Works at program level. Aim is to minimize the use of main memory and CPU resources, network transfers and hard disk accesses.
Tuning Measures :
A performance analysis has come up with the following results;
1) SM50 shows that several programs repeatedly spend a long time reading from table RESB
2) An analysis of the database shows that all tables with transaction data reside on one harddisk. All transaction data together amounts to 8GB of which table RESB accounts for 2GB.
3) The Operating System monitor shows that the harddisk on which , among other things , the RESB table resides is fully loaded (80-100 % load , response times of over 100 ms per access).
from system administration point of view following technical solution strategies need to be discussed
1) the data buffer on the db server could be made bigger , it will be able to hold a large part of RESB table on the main memory of the db server.
2) the RESB table could be placed on a separate hard disk. The db hard disk layout could also be changed so that the RESB table could be distributed over several hard disks.
3) the use of the ATP Server would make it possible to buffer partial RESB table results on the application server main memory and thus reduce database accesses to this table.
4) As a last resort , the installation of faster hard disks could be considered.
SUMMARY :
There are 2 important prerequisites for good system performance ;
1) cooperation of all those involved in setting up a mySAP Solution and in the execution and administration of customizing or developments.
2) long term planning of performance monitoring and optimization for this you can use Service Level Management methods and the central monitoring architecture of CCMS in the SAP Solution Manager.
PART 2 : Memory Management to be uploaded soon.
Reference : SAP Performance Optimization Guide by Thomas Schneider, SAP Press.
