IBM BPM, V8.0.1, All platforms > Tuning > Tuning parameters
Tracing and logging flags
Tracing and logging are often necessary when you are setting up a system or debugging issues. However, because tracing and logging produce significant performance issues, try to avoid using them in production environments and when you are evaluating performance.
Some tracing and logging parameters are common to all or a subset of the products; others are specific to a particular product. Unless stated otherwise, you can use the administrative console to set all of these parameters for tracing and logging flags.
Procedure
- To enable or disable tracing from the administrative console, go to Troubleshooting > Logs and Trace > server_name > Change Log Detail Levels and set both the configuration and runtime values to *=all=disabled.
- To change the PMI level from the administrative console, go to Monitoring and Tuning > Performance Monitoring Infrastructure > server_name and select none.
-
To disable tracing from the z/OS console, issue a modify command for the server. For example, to disable all Java™ traces, from the z/OS console, issue the following command:
f (server name),tracejava=*=all=disabled
- To enable the correlation of Service Component Architecture
(SCA) component information with log entries, use Cross-Component
Tracing (XCT). However, do not use XCT in production or while you are obtaining performance data. There are two levels of XCT settings: enable or enable
with data snapshot. Both incur significant performance issues. The enable with data snapshot setting
is particularly costly because of the additional I/O involved in saving
snapshots in files.
To enable or disable Cross-Component Tracing from the administrative console, go to Troubleshooting > Cross-Component Trace > server_name. Select the XCT settings in the Configuration or Runtime tab. Changes to the runtime environment take effect immediately; changes to the configuration require a server restart to take effect.