Use this page to configure cross-component tracing for WebSphere® Process
Servers.
Cross-component tracing allows you to identify trace.log data that is associated
with WebSphere Process
Server and WebSphere Enterprise
Service Bus modules and components. The trace.log data can include error
and event information, such as corrupted data or runtime exceptions, captured
during Service Component Architecture (SCA) processing. The input and output
data passing between WebSphere Process Server and WebSphere Enterprise
Service Bus components can also be captured and used for problem determination
using WebSphere Integration
Developer.
To view this administrative console page, click .
The table on the Cross-Component Trace page lists each server on which
to enable or disable tracing. It has the following columns:
- Select
- Allows you to select a server on which to configure trace levels.
- Server
- Specifies the name of the server.
- Status
- Shows the status of the server: running or not
running. If the status is not running,
runtime tracing for that server is disabled and you can specify only the configuration
value. In this case, the trace level takes effect only when the server starts
or restarts.
- Node
- Specifies the node on which the server is running.
- Configuration
- Displays the current configuration setting for cross-component trace that
is used when the server starts or restarts. You can change this setting to
any of the following values:
- enable: Collects SCA data for the selected server. This
data is added to the trace.log file and is purged as those files are purged.
- enable with data snapshot: Collects SCA data and call
chain data for the selected process server. When input and output data passing
between WebSphere Process
Server and WebSphere Enterprise
Service Bus components is captured, additional files are created in the logs\XCT
directory. Deleting these files when they are no longer needed is a task
for the administrator.
- disable: Trace is disabled. No data is collected.
- Runtime
- Displays the current setting for cross-component trace in the runtime
environment. This setting is used only when the server is running. It is not
saved, and it does not affect the server when it is started or restarted.
For server start or restart, the setting that is specified in Configuration
is used. You can change this setting to any of the following values:
- enable: Collects SCA data for the selected server. This
data is added to the trace.log file and is purged as those files are purged.
- enable with data snapshot: Collects SCA data and call
chain data for the selected server. When input and output data that passes
between WebSphere Process
Server and WebSphere Enterprise
Service Bus components is captured, additional files are created in the logs\XCT
directory. Deleting these files when they are no longer needed is a task
for the administrator.
- disable: Trace is disabled. No data is collected.