Application Tracing
Settings
Procedure
The application tracing settings are stored persistently in the database. Different profiles may be created and only one of them is active at a time. To access the service settings:
...
1. Choose Server → Services → Performance Tracing → Runtime → Application tracing.
2.
Choose 
Settings.
The Apptracing service settings dialog box appears.
a. Use the Profile dropdown listbox to select a profile.
b. Choose Set active to activate a particular profile.
c. Choose Copy to add the current settings to a new profile.
d. Choose Delete to remove a profile.
Options are available for:
· the complexity of the displayed information:
Display Settings
Option |
Description |
Display only modified classes from applications |
Normally only classes loaded by ApplicationLoader instances are displayed. The server may contain classes that are modified for some other purpose, but since they are not relevant to application tracing they are hidden. This setting is activated by default. |
Use different colour while refreshing nodes |
The nodes are temporarily colored in the specified color while they are being refreshed. After refreshing, the normal color is restored. The Color for refreshed nodes subentry shows the current color. This setting is deactivated by default. |
Array paging in the object browser |
Arrays are displayed in scrollable portions in the object browser. This setting specifies the size of a portion. Affects only array objects that will be browsed in the future. The default value is 10 items. |
Display the class of an object as a field |
When the setting is activated, the object browser imitates a class field for each object, although it does not exist physically. This affects objects that will be browsed in the future only. This setting is activated by default. |
Expand tree node on select |
Toggles single-click and double-click tree expansion. This setting is activated by default. |
· filtering the method invocation records
Invocation Recording Settings
Option |
Description |
Record coverage |
If enabled, an additional handler is added that records how many times each method was invoked. The results will be visible under the classes management node. This setting is deactivated by default. |
Record only invocations with durations greater than |
A way of filtering out unnecessary information. Only invocations whose duration exceeds the given value will be recorded in the tree. The rest will be discarded. The Microseconds subentry sets the threshold to optimize the amount of data recorded. This setting is deactivated by default. |
Threshold for the number of recorded invocations |
Using the Limit subentry you can set a threshold above which no data will be recorded for the invocations. |
Log recorded invocations |
Use the standard SAP logging to store the invocations, apart from recording them in the tree. Logging every invocation may significantly slow down the execution process. This setting is deactivated by default. |
· source code retrieval
Source Code Retrieval Settings
Option |
Description |
Use sourcepath |
Having the sources is the simplest way to retrieve them. Use the Sourcepath subentry to specify the host where the Visual Administrator is running. |
Use a java decompiler |
An external command line decompiler can be used to produce a decent overview of what a class looks like. Use the Decompiler location subentry to specify the host where the Visual Administrator is running. Use the Decompiler option subentry to adjust the decompiler according to your code convention. |
Use the built-in jasmin decompiler |
Decompiles classfiles to an assembly-like language. Can be used as a last resort when all other source-retrieval methods fail. |