Use the information in this
group of topics to identify
and resolve errors in service applications deployed to the run time.
Cross-component trace
Cross-component trace identifies whether a Service Component
Architecture operation completed successfully.
Enabling Cross-Component Trace for the server
You
can enable cross-component trace on a server. Use cross-component
trace to identify trace.log and systemout.log data that is associated with IBM® Process Server and WebSphere® Enterprise Service Bus modules and components.
Enabling Cross-Component Trace for selected SCA modules
You can enable Cross-Component Trace on specific Service
Component Architecture (SCA) modules on a server. Use
Cross-Component Trace to identify trace.log and systemout.log data that is associated with IBM Process Server and WebSphere Enterprise Service Bus modules and components.
Disabling Cross-Component Trace
Disable Cross-Component tracing to stop the collection
of error and event information associated with IBM Process Server and WebSphere Enterprise Service Bus modules
and components captured during Service Component Architecture (SCA)
processing.
Deleting data snapshot files
You can delete
the data snapshot files from the logs\XCT directory
to free up disk space. The data added to the systemout.log and trace.log
files does not need to be deleted as these files are automatically
deleted by WebSphere® Application Server. When the data from the systemout.log
and trace.log is deleted, the corresponding data snapshot files remain
on the disk. You can delete these files manually or you can set a
parameter on the administrative console which results in data snapshot
files being deleted by the system periodically.
Troubleshooting event sequencing
Refer to the information in this topic if you are experiencing
difficulty with event sequencing.
Troubleshooting Service Component Architecture and WebSphere MQ communications
Communication between Service Component Architecture (SCA)
modules and WebSphere MQ queue managers depends on
the binding between the imports and exports within the SCA module
and the queues in WebSphere MQ servers. Use this information to determine
the servers that are not processing WebSphere MQ messages.