[{ALLOW view All}]
[{ALLOW edit Authenticated}]

[{TableOfContents }]

!! 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
# Browser rendering
# Network bandwidth
# Server side
** slow ABAP code
** strange business logic
** memory consuption
** too many contexts or too big
** inefficient SQL

!! WDA Performance Tools 1-6

! ([1|http://scn.sap.com/docs/DOC-2295]) [Performance Monitor|https://help.sap.com/saphelp_nw70ehp1/helpdata/en/4b/4cdb2ffcf74d39ac958fe21702887b/content.htm]
|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|http://scn.sap.com/docs/DOC-2296]) 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|http://scn.sap.com/docs/DOC-2297]) 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|http://scn.sap.com/docs/DOC-2298]) x.ST05 - SQL Trace
* if the database causes problems
* need to be activated before
 
! ([5|http://scn.sap.com/docs/DOC-2299]) 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
# x.SE80 > "Repository Info System" > Web Dynpro > Web Dynpor Applicat.
# Enter application name > Execute > Pick it and open it
# Menu > Goto > HTTP Service Maintenance
# Mark service
# Menu > Edit > Runtime Analysis > Activate
# Execute any web dynpro application in browser
# (SICF) Menu > Edit > Runtime Analysis > Deactivate
# x.SAT > Evaluate

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

! ([6|http://scn.sap.com/docs/DOC-2300]) Memory Inspector
* memory snapshots allows to analyse memory growth/diffs
# Take snapshots via Performance Monitor > Unfold > Memory > "Write Memory Snapshot"\\
    or: Debugger > Special Tools > Memory Analysis AND Services Tools > Take Memory snapshot
# Menu > System > Utilities > Memory Analysis > Compare Memory Snapshots (x.S_MEMORY_INSPECTOR)
# 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