Displaying and Changing JARM Settings

Standard Control Elements

In the upper area you can make settings for the entire configuration.

• : Updates entire configuration. The current configuration is called and displayed. Any changes not saved will be lost.

• : Saves the configuration changes.

Configuration Profiles

• : Deactivates JARM completely.

• : Standard JARM configuration suitable for many functions.

• : Activates JARM completely (all switches set to on and all levels set to maximum).

Single Settings

The single options are described below. You can view the possible values using F4 help.

JARM Activation

• jarm/switch: Activates and deactivates JARM. When deactivated JARM instrumentation causes no overhead and therefore does not affect the behavior of the application. Only when JARM is activated is data collected, and the behavior of the application affected depending on other configuration settings.

• jarm/tracemode/switch: JARM trace can be activated independent of whether JARM is active or not. Though only JARM data relevant to the trace is processed and written to the trace files (for instance, B SAT single activity trace).

JARM Configuration

The settings below are relevant only if JARM is active.

• jarm/instrumentation/check: When the instrumentation is checked, errors (but not all of them) can be discovered, such as components that were not closed. Warnings and errors related to instrumentation are written to work process trace files.

• jarm/comp/properties/set/switch: The JARM instrumentation API enables users to define user-specific component properties. Users can also determine how these properties are processed by implementing an interface that supplies several results at runtime. With this switch you can activate and deactivate the processing of these properties.

• jarm/comp/properties/get/switch: Here you specify whether the results of the user-specific settings are displayed by the JARM display API (and with that also in SM53 - Displaying Measurement Results).

• jarm/jts/vmoverview: This property is specific to VMC and provides an overview of the threads instrumented by JARM. This data also contains VM information to identify each thread uniquely.

• jarm/jts/condensing/overview: This VMC-specific property affects how the collected JARM data is compressed for displaying it. To keep the memory requirement in the shared memory as small as possible, the collected JARM data is condensed. Raw data is rejected. Data compression is normally triggered once the defined size (jarm/jts/condensing/memsize in bytes) is exceeded. This means that before the data is compressed, the user cannot view updated JARM results in the display API. When you set this property compression is forced each time the results are called up. You must have bear in mind that it then takes longer to call the results, as possibly the data must be directly compressed before it can be called up.

• jarm/comp/level: The JARM components have a level that can be set by the developer. Depending on the component level configured only those components are processed by JARM whose level is equal to or small than the level configured.

• jarm/comp/trace/level: Determines the processing of trace data of the specified component level.

• jarm/log/level: Detailed level of the JARM log.

• jarm/maxreqcomplow und jarm/maxreqcomphigh: Both values specify the upper and lower limits for components per request (see JARM in the VM Container).

• jarm/jts/condensing/memsize: Maximum memory size for JARM raw data in the shared memory. If this size is exceeded compression (see above) is triggered.