Use this page to view and set the Cross-Component Trace parameters for V8.0.1 servers. You can set the parameters for a server or for a specific module. If you want to perform Cross-Component Trace on specific modules on the server, you can access a list of SCA modules from this page. The parameters that you set on the Configuration tab apply when the server is restarted. The parameters that you set on the Runtime tab apply immediately.
To view this administrative console page, click V8.0.1 server.
, where server_name is the name of aUse this page to enable or disable a Cross-Component Trace (for the server or specific modules), specify where trace data is stored, and choose how to configure Cross-Component Trace logging.
Configuration parameters for Cross-Component Trace display on the Configuration tab. The parameters you set on the Configuration tab are applied by the system when the server is restarted.
Enable Cross-Component Trace in the Configuration collects data when the server starts or restarts.
Trace is the default and recommended option. Selecting Trace maps to the WebSphere Application Server logging level of Fine and provides the best performance for collecting Cross-Component Trace data. If you select this option, it results in trace data being written to the trace.log file.
Selecting System.Out maps to the WebSphere Application Server logging level of Info. Selecting System.Out results in Cross-Component Trace data being written to the systemout.log file.
Choosing System.Out takes the system more time to write out the log. However, the SystemOut.log has less data in it, making it less time consuming to review it's contents.
When you select Trace all, the server honors Cross-Component Trace call chains for modules coming from (inbound) other servers. When Trace all is selected, the server also checks if Cross-Component Trace is on for any modules in the server and honors those settings so that calls to those modules result in application-specific Cross-Component call chains.
When data snapshot is enabled, the system captures data sent in and passed between SCA components. This extra data (about what was passed between SCA components) can be large and is kept in separate files and not in the trace.log or systemout.log.
You can delete data snapshot files from the administrative console. For information on managing Cross-Component Trace disk use, select Cross-Component Trace disk use from the Additional properties section of this console page.
This table provides a list of modules for which Cross-Component Trace has been enabled.
Try to keep the list of SCA modules in Enable tracing for the selected Service Component Architecture (SCA) modules to a small number. If the number of modules listed in the table begins to grow, consider selecting Trace all instead. There is a small affect on performance for each SCA module added to the list.
This table has multiple functions as follows:
Choosing Add brings you to a page listing all of the SCA modules running on the server. From the list of SCA modules, you can choose those on which want to enable Cross-Component Trace.
Choosing Remove removes the SCA module you have selected from the list. By selecting a module and clicking Remove, you disable Cross-Component Trace functionality on that module.
When data snapshot is enabled, the system captures data sent in and passed between SCA components. This extra data (about what was passed between SCA components) can be large and is kept in separate files and not in the trace.log or systemout.log.
Runtime parameters for Cross-Component Trace display on the Runtime tab. The parameters you set on the Runtime tab are applied to the server immediately.
If you select Save all runtime changes to the server configuration file the changes you make are applied by the system when the server starts or restarts.
Enable Cross-Component Trace in the Configuration collects data when the server starts or restarts.
Trace is the default and recommended option. Selecting Trace maps to the WebSphere Application Server logging level of Fine and provides the best performance for collecting Cross-Component Trace data. If you select this option, it results in trace data being written to the trace.log file.
Selecting System.Out maps to the WebSphere Application Server logging level of Info. Selecting System.Out results in Cross-Component Trace data being written to the systemout.log file.
Choosing System.Out takes the system more time to write out the log. However, the SystemOut.log has less data in it, making it less time consuming to review it's contents.
When you select Trace all, the server honors Cross-Component Trace call chains for modules coming from (inbound) other servers. When Trace all is selected, the server also checks if Cross-Component Trace is on for any modules in the server and honors those settings so that calls to those modules result in application-specific Cross-Component call chains.
When data snapshot is enabled, the system captures data sent in and passed between SCA components. This extra data (about what was passed between SCA components) can be large and is kept in separate files and not in the trace.log or systemout.log.
You can delete data snapshot files from the administrative console. For information on managing Cross-Component Trace disk use, select Cross-Component Trace disk use from the Additional properties section of this console page.
This table provides a list of modules for which Cross-Component Trace has been enabled.
Try to keep the list of SCA modules in Enable tracing for the selected Service Component Architecture (SCA) modules to a small number. If the number of modules listed in the table begins to grow, consider selecting Trace all instead. There is a small affect on performance for each SCA module added to the list.
This table has multiple functions as follows:
Choosing Add brings you to a page listing all of the SCA modules running on the server. From the list of SCA modules, you can choose those on which want to enable Cross-Component Trace.
Choosing Remove removes the SCA module you have selected from the list. By selecting a module and clicking Remove, you disable Cross-Component Trace functionality on that module.
When data snapshot is enabled, the system captures data sent in and passed between SCA components. This extra data (about what was passed between SCA components) can be large and is kept in separate files and not in the trace.log or systemout.log.
Links marked (online) require access to the Internet.
Check for updates to this topic (online)