![]() ![]() ![]() ![]() follow me on Twitter |
|
|
| ![]() ![]() |
| ![]() ![]() |
|
| ![]() ![]() |
|
Client SAPGUI/Browser * Configuration | SAP Web AS (WAS) * Configuration * ABAP coding * Java coding # Dialog processes # thread pools | Message server * JMS Configuration | Enqueue server * Configuration | Database server * Configuration * File Distribution * Replication ![]() | Authentication server * Configuration | Reporting server * Configuration | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Connectors from Client SAPGUI/Browser | Connectors from SAP Web AS server | Connectors from Messaging server | Connectors from Enqueue server | Connectors from Database server | Connectors from Authentication server | Connectors from Reporting server | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
JVM in Client SAPGUI/Browser | JVM in SAP Web AS server | JVM in Messaging server | JVM in Enqueue server | JVM in Database server | JVM in Authentication server | JVM in Reporting server | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
OS in Client SAPGUI/Browser | OS in SAP Web AS server | OS in Messaging server | OS in Enqueue server | OS in Database server | OS in Authentication server | OS in Reporting server | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Machine hardware: Memory, Hard Disk, etc. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Network: Hubs, Routers, Proxy, Load Balancer, Firewall, DNS, Gateways, Bridges, Backbone |
Performance problems in large R/3 installations with more than 10 application servers are most often caused by bottlenecks in the database server.
Several application servers may belong to a single SAP System (identified by a SID).
| Experts with SAP's "Remote Support" service log onto systems to resolve problems.
| ![]() ![]() |
|
Interactive Electronic Technical Manual (IETM)
| ![]() ![]() |
| SAP Note 327494 recommends settings for MS SQL Server. |
![]() ![]() |
|
| ![]() ![]() |
|
![]() ![]() |
|
| ![]() ![]() |
|
Server | Service | # in Profile | Description | |
---|---|---|---|---|
Web AS | Dispatcher | - | - | The transaction monitor/control program that (through a request queue) receives screens from presentation services and passes them to work processes in a balanced way. The dispatcher communicates with the task handler within each work process. The task handler coordinates the loading and unloading of user session context for each dialog step. and activates the dynpro interpreter or the ABAP processor, as required. |
Dialog | DIA | rdisp/wp_no_dia | Used for interactive online processing. There is a minimum of 2 of these on each server. Each dialog work process constantly switches among sessions for different users. All work processes reference user contexts in a common memory area. | |
Batch (Background) | BTC | rdisp/wp_no_btc | Used for jobs running consecutively in the background. Each job step is an ABAP or external program. | |
Update (V1) | UPD | rdisp/wp_no_vb | Used for time-critical updates that need to happen immediately. | |
Update (V2) | rdisp/wp_no_vb2 | Used for updates that are not critical and can be delayed until resources are available. | ||
Spool | SPO | rdisp/wp_no_spo | Formats print requests for passing to host spool systems. Scans TemSe (temporal sequential objects) in the spool database for requests lost through queue overflows. As of Release 4.0, SAP allows more than one spool process per instance. | |
ABAP Central Instance | Enqueue (lock manager) | ENQ | rdisp/wp_no_enq | The single "central lock management" mechanism that ensures data consistency by locking/unlocking portions of the database to all application servers during exclusive update. |
Message Server | - | - | Communicates with the different application servers to route messages (includinge licensing) between the servers. Each SAP instance has only one message server. The location of the host running the message server is configured in the DEFAULT.PFL common profile parameter rdisp/mshost = <hostname>. It has its own start execution line in the start profile. | |
Gateway | - | - | Used for transport of bigger amounts of data between application servers as well as external (non-SAP) systems that communicate with SAP using the CPIC (Common Programming Interface Communications) protocol developed by IBM and X/Open the lowest-level protocol used on the TCP/IP socket when connecting through the R/3 Gateway). Displaying Active CPI-C Connections | |
Java | Enqueue | - | - | - |
JMS | - | - | - |
The Global Work Process Overview displays: * The status of each application server * The reason why it is not running * Whether it has been restarted * The CPU and request run time * The user who has logged on and the client that they logged on to * The report that is running
[_] Indicate the number of update work processes of type V1 and V2 inside the profile parameter file for each instance by specifying parameters rdisp/wp_no_vb and rdisp/wp_no_vb2
[_]
The number of available work processes per application server
should be configured using
the SAP system profile parameters values appropriate to hardware capacity and the
peak activity anticipated.
| ![]() ![]() |
[_]
Set dispatcher request que length so that there are enough to the calculated
total number of requests that may que up (be buffered)
during the time it takes for operators to recognize an overflow and the time it takes to add
more servers to handle the overflow.
| ![]() ![]() |
| ![]() ![]() |
|
Path name for the ABAP trace files. | abap/atrapath | - |
Name of the SQL trace file. | rstr/file | - |
Instance profiles named <SID>_<instancename>_<hostname> are automatically generated by the R/3 setup utility when an instance (dialog or central) is installed. By default, the name assigned to them has the format , Instance type profiles for a particular instance can override system profiles in DEFAULT.PFL.
Although the sappad text editor can edit profiles even if the system cannot start, profile maintenance should be performed using SAP R/3 Computer Center Management System (CCMS) transaction RZ10 (Edit Profiles).
sappfpar CHECK pf=C:\SAP\NSP\SYS\profile\NSP_DVEMGS00_BUBBA1
verifies the profile file.
Enter transaction code SMLG or menu Tools > _CCMS > Configuration > _Logon Groups
to configure logon groups and their instance servers
for Load balancing.
This information is used by the SAP logon Windows application on each workstation to decide which system
the user logs on to.
Changes to profile parameters take effect after a system restart.
Using the CCMS profile maintenance tool also requires the profile to be activated.
Operating system | 30 MB | - |
SAP System | - | Check memory usage from initial screen Administration > System administration > Monitor > Performance > Setup/Buffers > Buffers > Goto > Current local data > Additional functions > Storage. Increase SAP buffers until no more object swaps occur. |
Database system | - | - |
[_] Ensure there are enough connections specified with these parameters:
Connection Pool | Max. Parameter | Default Value |
---|---|---|
front-end connections in table tm_adm. | rdisp/tm_max_no | - |
CPIC/RFC connections that can be administered in communication table comm_adm. | rdisp/max_comm_ entries | - |
CPIC/RFC connections that can be administered by the gateway service in table conn_tbl. | gw/max_conn | - |
|
![]() ![]() |
Command $TAB resets Table buffers.
|
by Priority | Buffer for ... | Parameter for Startup | Max. Entries | |||
---|---|---|---|---|---|---|
1. Repository Buffers (ABAP Dictionary buffer) | TTAB (R/3 table definitions) in Table DDNTT | - | entrycount * 100 bytes | rsdb/ntab/entrycount | - | |
FTAB (R/3 field definitions) in Table DDNTF | rsdb/ntab/ftabsize | KB | rsdb/ntab/entrycount | * 2 = max. | ||
SNTAB (Short/Summary names derived from DDNTT & DDNTF | rsdb/ntab/sntabsize | KB | rsdb/ntab/entrycount | * 2 = max. | ||
IRBD (Initial record layout initialized depending on the field type) | rsdb/ntab/irbdsiz | KB | rsdb/ntab/entrycount | * 2 = max. | ||
2. (transparent and pooled) Table Buffers | Single Record (of 100KB - 200KB) of Partial Tables | rtbb/buffer_length | KB | rtbb/maximum_tables | Max. | |
Generic (client) Key Table (for resident/full buffering of all entries in a table) | zcsa/ table_buffer_ area | - | zcsa/database_max_buftab | Max. | ||
SAP Buffers | 3. Program Buffer PXA (Program Execution Area) stores compiled executable versions of ABAP programs from tables D010L (ABAP loads), D010T (texts), and D010Y (symbol table). | abap/buffersize | KB | - | - | |
4. Roll and Paging Buffers | ![]() | - | - | - | ||
5. SAPGUI buffers | Presentation buffer storing Dynpro loads (Screens) | zcsa/presentation_buffer_area | / 2 = bytes | sap/bufdir_entries | Max. | |
CUA (menus, pushbutton definitions) from tables D345T (CUA texts) & D342L (CUA loads) | rsdb/cua/buffersize | KB | - | buffersize / 2 = Max. | ||
Export/Import to/from database (available to several work processes) using ABAP command EXPORT TO/IMPORT FROM SHARED BUFFER. | rsdb/obj/buffersize | KB | rsdb/obj/max_objects | Max. | ||
rsdb/obj/large_object_size = Typical size of the largest objects | bytes | |||||
Calendar (work days and public holidays in db tables TFACS and THOCS) | zcsa/calendar_area | KB | zcsa/calendar_ids | Max. entries |
Set the count of entries approriate to its size,
since an increase in one may lead to a bottleneck in the other.
SAP Cursor Cache (in the shadow process owned by each WP) reduces the number of parsing of SQL statements by storing cursors for SELECT statements to avoid time consuming PREPARE processing. The DBSL (Database SQL Library) creates and maintains statement IDs. Its profile setting of dbs/stmt_cache_size is different for each database (default fixed size of 250), so it should not be changed. The memory space of each entry in the statement cache is allocated dynamically, with a maximum 64KB per entry.
|
SAP's Zero Administration Memory Management
introduced with R/3 Release 4.0
reduces tweaking to one R/3 profile setting:
[_] PHYS_MEMSIZE to specify how much of the computer’s main memory should be used for the R/3 instance. SAP dynamically allocates this memory among roll, extended, heap, and paging memory, which should not have sizing parameters specified in profiles. | R/3 extended memory | - |
fixed local memory | fixed local memory for each R/3 work process | |
R/3 heap memory | variable local memory for R/3 work processes
abap/heap_area_total = how much R/3 heap memory can be allocated in sum by all work processes. abap/heap_area_dia and abap/heap_area_nondia = maximum amount of R/3 heap memory that can be allocated by a dialog or nondialog work process, respectively. | |
R/3 roll memory | Only one work process can access these buffers at a time. rdisp/ROLL_MAXFS specifies the size of the total global roll area (R/3 roll buffer plus the roll file). rdisp/ROLL_SHM specifies the size of the R/3 roll buffer. ztta/roll_area specifies the size of the local roll area for all types of R/3 work processes. | |
R/3 paging memory | - |
User session context information is moved around thus:
If ztta/max_memreq_MB is set too low, message SYSTEM_NO_ROLL will be issued.
| ![]() ![]() |
| ![]()
LoadRunner obtains statistics from CCMS through (after additional HP licensing) port 8888 on a HP SiteScope server with SAP Java Connector (JCO) installed. |
![]() ![]() |
Related Topics:
LoadRunner
SNMP
Rational Robot
Free Training!
Tech Support
![]()
| Your first name: Your family name: Your location (city, country): Your Email address: |
Top of Page ![]() Thank you! |