Managing Plugins
Use the Performance Tracing → Runtime → Application tracing → Plugins tab to manage plugins along with the available handlers and patterns.
The
bytecode-modification plugins in the application tracing are marked with
or
.

The plugins
root node will be visible in the tree only if the relevant setting (
) is selected.
This node is necessary, for example, if an application has a heavy start-up. The developer may wish to disable the plugin temporarily before the application is started, and then enable it only for a single request.
You can apply different actions to each plugin:
Plugin Actions
Action |
Description |
Browse as an object |
Adds the com.sap.engine.library.bytecode.TracingPlugin object to the object browser. |
Disable temporarily |
There is the option to disable certain plugins for short periods of time. While a plugin is disabled it is still “plugged" but does not dispatch events to its handlers. |
Enable |
Enables a plugin. |
The
bytecode-modification handlers in the application tracing are marked with
.
You can apply different actions to each handler:
Handler Actions
Action |
Description |
Browse as an object |
Adds the com.sap.engine.library.bytecode.tracing. TracingHandler object to the object browser. |
A TracingPattern is an object that determines the
associations between a plugin and the modified classes from which it needs to
receive events. Each TracingPlugin has a TracingPattern. The patterns in the application tracing are
marked with
.
You can apply different actions to each pattern:
Pattern Actions
Action |
Description |
Browse as an object |
Adds the com.sap.engine.library.bytecode. TracingPattern object to the object browser. |