Purpose
Example Scenario
Lets say that you suspect there is uneven load balancing between the server nodes. In this case, detailed JAVA dispatcher traces will help. Another example will be that requests are triggered from a 3rd party load balancer to the ICM and this fails. Analyzing the ICM traces will shed more light. This analysis will also help in standard performance tuning and optimization of ICM if needed.
Example Screenshot:
DISPATCHER (SAP Release 6.40 and 7.00/7.01/7.02)
To trace the Dispatcher, enable the property HttpTrace (set it to enable) and HttpTraceTime to true as per as per SAP note 724719.. Also open Visual Admin -> goto Dispatcher node -> services -> LogConfigurator -> Locations tab -> com.sap.engine.services.httpserver and set the severity (of the subtree as well) to DEBUG. Once the issue is reproduced, more detailed trace will be available in req_resp.trc files under Dispatcher folder of each instance. The latest modified DefaultTrace files under dispatcher and server log folders will also have more info.
ICM (SAP Release 7.1/7.2/7.3/7.31/7.4/7.5
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
13 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |