Analysis#

1. You can right click and use the context menu > Technical Help
2. SE80 > Web Dynpro Components/Interface > {Application Name} > Assistance Class

Performance#

Areas of possible problems#

1. Browser rendering
2. Network bandwidth
3. Server side
   • slow ABAP code
   • strange business logic
   • memory consuption
   • too many contexts or too big
   • inefficient SQL

WDA Performance Tools 1-6#

(1) Performance Monitor#

sap-wd-perfMonitor=X	URL parameter
Shift+Ctrl+Alt+p	Start shortcut

• a little bar upper right will appear
• Memory = SAP session memory on server
• ">>" shows more information

(2) Browser Debugging Tools#

Note: IE Addon "HTTP Watch" is not necessary anymore as every modern browser provides analysis tools under F12.

• All browsers provide debugging tools with F12
• In Firefox "Firebug" can be used alternatively
• Fiddler (for IE) is even more detailed

(3) x.STAD - SAP Workload: Business Transaction Analysis #

• to analyse server side problems
• no activation necessary
• drill in shows breakdown more detailed (see database activity)

(4) x.ST05 - SQL Trace#

• if the database causes problems
• need to be activated before

(5) Runtime Analysis#

• if code causes problems
• In x.SAT you can create settings/filters to be used as variant later !
• Runtime diagramm in x.SAT possible

1. x.SE80 > "Repository Info System" > Web Dynpro > Web Dynpor Applicat.
2. Enter application name > Execute > Pick it and open it
3. Menu > Goto > HTTP Service Maintenance
4. Mark service
5. Menu > Edit > Runtime Analysis > Activate
6. Execute any web dynpro application in browser
7. (SICF) Menu > Edit > Runtime Analysis > Deactivate
8. x.SAT > Evaluate

x.SICF => Authorization Profile, Debugging, Trace?

(6) Memory Inspector#

• memory snapshots allows to analyse memory growth/diffs

1. Take snapshots via Performance Monitor > Unfold > Memory > "Write Memory Snapshot"
   or: Debugger > Special Tools > Memory Analysis AND Services Tools > Take Memory snapshot
2. Menu > System > Utilities > Memory Analysis > Compare Memory Snapshots (x.S_MEMORY_INSPECTOR)
3. Get delta between two snapshots with the "Memory Snapshot" Dropdown list (t_1 - t_0), (+)red, (-)blue, (o)black

WD_TRACE_TOOL#

x.WD_TRACE_TOOL (RAT Trace/ Runtime Analysis Tool)

Correction notes:

1967934	FPM runtime analysis tool: Dump in IDR
1999338	Beim Einschalten der Trace 'FPM Components' kommt es zu einem Abbruch
1978395	ASSERTION_FAILED im Web Dynpro Trace Tool	<== PAGE_TRACE_ENTRY error
1980034	FPM runtime analysis tool: Dump in IDR

Get WDA component class (for full text search)#

1. x.SE24 > CL_WDY_WB_NAMING_SERVICE
2. Execute > GET_CLASSNAME_FOR_COMPONENT( )
3. Enter component name
4. Execute

Transactions#

ST03N: Statistics Regards Locallly
ST03G: Statistics Regards Golbally
STAD: Individual Statistics Regards
STATTRAACE: Individual Statistics Regards Trace
ST07	User Distribution
SLG1	System logs (You can see the logs based on user, transaction, programs , time etc)
SM66	Global work process overview

Buffers and Memory

ST02	Buffers and Memory and swaps monitoring
ST04	DB monitoring
ST10	Table Acess

OS Monitoring

OS04	Locally monitoring
OS06
OS07	Remotely monitoring
OS01	LAN check

DataBase Side

ST04	Performance overview
DB01	Exclusive locks
DB02	Tables/Indexes
SM21	System logs
ST22	Abap Dumps
SM12	Lock Entries
SM56	NumberRange Buffers
SU56	User Buffer