WebGUI, Service, Webserver, Web Service#

SICFWebDynpro Applications
SMICMICM Monitor
SOAMANAGER
WSCONFIG
WSADMIN
SPROXY
SE80

Tree: /sap/bc/webdynpro/<namespace>/<application name>

Timeout#

see SAP

1. SE38 > r.RSPARAM
2. See parameter icm/server_port_<x>

TIMEOUTNetzwerk-Timeout
PROCTIMEOUTBearbeitungs-Timeout (ICM Request)
Example: icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600

See also

icm/keepalive_timeoutUsed if icm/server_port_<x>=0
rdisp/plugin_auto_logoutAS ABAP (Benutzerkontext im Workprozess) 0=never

Trace Web Applications#

Option 1
  1. SICF > F8#
  2. Menu > Bearbeiten > Auszeichnung aktivieren (mit "Request + Response", Pfad =/)
  3. <Run web application>
  4. Menu > Bearbeiten > Auszeichnung deaktivieren
  5. Menu > Bearbeiten > Auszeichnung anzeigen

Option 2, HTTP-Aufzeichnung für den Service CRM_UI_FRAME

  1. SICF
  2. Filter ICF Hierarchy to Service = CRM_UI_FRAME
  3. Switch on runtime analysis (SICF: Edit -> Runtime Analysis -> Activate)
  4. Start WebUI (SICF: context menu on node 'crm_ui_frame' -> Test Service)
  5. Do whatever is of interest for your analysis
  6. Switch off runtime analysis (SICF: Edit -> Runtime Analysis -> Deactivate)
  7. Now switch to transaction SE30 (or SAT) to analyse the data

Option 3, 'On-Demand' measurements

  1. Transaction SE30.
  2. Click For User/Service.
  3. Create new Task. (It should have Process Type: HTTP & Object Type: URL)
  4. Execute your scenario.
  5. Come back to Tasks and Delete your Task that you have created at step 3. This stops the measurement.
  6. Select Other File to view your trace.

Options 4, Benutzervorgaben (?)

CRM_EVENT_TRACE=X
CRM_UI_PROFILE=Xx1234567

Others

  • Activate the checkpoint group BSP_WD_EXCEPTION_DISPLAY. You can do so in transaction SAAB. In the tab page "Activation" and its area "Assertions" set the radio button "Break". This will display information about runtime exceptions in the WebClient UI
  • In your user data (transaction SU3) add the parameter BSPWD_USER_LEVEL with the value 9. This will display all messages including technical information within the message area of the WebClient UI.
  • Check also: Note 1244321 - Simplifying error analysis in CRM WebClient UI: Wenn Sie den Internet Explorer verwenden, wählen Sie "Extras -> Internetoptionen". Entfernen Sie auf der Registerkarte "Erweitert" das Kennzeichen "Kurze HTTP-Fehlermeldungen anzeigen"
  • Das Trace in Transaktion STAUTHTRACE ist die ausführliche Version des in Transaktion SU22 über die Tracetaste verfügbaren Traces. Es funktioniert wie das Systemtrace (Transaktion ST01). Allerdings wertet es ausschließlich Berechtigungsprüfungen aus

Shared Memory#

SHMMShared Memory Areas Overview
SHMAShared Memory Area Administration

We had a system dump SYSTEM_NO_SHM_MEMORY for CX_SHM_OUT_OF_MEMORY at area CL_BSP_WD_SHM_AREA and solved it by increasing "abap/shared_objects_size_MB" from 120 to 300.

Notes on this <note-no>

972757Occurence of the SYSTEM_NO_SHM_MEMORY runtime error
1232973SYSTEM_NO_SHM_MEMORY short dump
1281896Hoher Speicherverbrauch und CRM WebClient
1042618Shared memory für Design layer nach Systemneustart

SSL#

STRUSTICM Certificates

SAP Doku: SSL Einrichten | SAP Doku: WS-Security | Forum SSL

Setup Note 510007 | Note 1094342

Note:
When you setup your SSL standard server certificate, make sure the CN is the FQDN of your SAP system as seen by and connected to from your browser clients.

You should be able to view the certificate in your browser, if the hostname in the certificate does not match the FQDN of the server you are connecting to you will get an error. Check SMICM -> Goto -> Trace File -> Display All ...for more information on the issue.

Tipp: In der SM59 eine “HTTP-Verbindung zu ext. Server” anlegen, damit kann man in der Regel schneller testen, als jedes Mal den Webservice zu debuggen.

My own findings:
1. STRUST "SSL-Server Standard": root CN must be "*.<domain>"
2. Import all instance certificates into the root certificate (the * one)
3. STRUST "SSL-Client SSL-Client(Standard)" must import the instance and the root certificate
4. when you import/generate certificates you must restart the ICM