Cross-component tracing allows you to identify systemout.log
or 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 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.
Events that can be captured include:
- Errors that occur during processing because of corrupted data.
- Errors when resources are not available, or are failing.
- Interpretation of code paths.
You can access the Cross-Component Trace page from the administrative
console and then clicking . On this
page, you can select the servers from which you want to collect trace
data. Use the Configuration column to specify
trace settings for servers that will be used when the server starts
or restarts. Use the Runtime column to specify
trace settings for servers that are running.
For each server, you can use any of the following settings:
- enable
- This setting enables tracing for SCA processing. Data collected
from this setting is added to the systemout.log and trace.log files
and is purged as those files are purged.
- enable with data snapshot
- This setting enables tracing for SCA processing and input and
output data that passes between WebSphere Process
Server and WebSphere Enterprise
Service Bus components. Data from SCA processing is added to the systemout.log
and trace.log files. Input and output data from WebSphere Process Server and WebSphere Enterprise Service Bus components
is placed in files that are created in the logs\XCT directory.
- disable
- This setting disables tracing on the selected server.
Handling and deleting collected data
- Data collected from SCA processing is added to added to the systemout.log
and trace.log files and is purged as those files are purged.
- Input and output data added as files in the logs\XCT directory
can be moved to a location where it can be viewed by WebSphere Integration Developer for problem
determination. The files can then be manually deleted. These input
and output files in logs\XCT are related to the systemout.log and
trace.log files that were created at the same time. When WebSphere Application Server
deletes old systemout.log and trace.log files, the associated input
and output files in logs\XCT can also be deleted. Generally, there
will be many input and output files for a given systemout.log file.
The timestamps in the systemout.log and trace.log files can be used
to identify what input and output files to delete. It is safe to
delete all input and output files older than the oldest date in the
systemout.log and trace.log files.