IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Troubleshooting > Use the Server Logs view for problem determination
Overview of cross-component tracing
By default, the Server Logs view displays standard server console and log records. However, if you enable cross-component tracing, the Server Logs view will also display invocation records that can contain the invocation data that was passed between the components in your application. The invocation records are displayed in hierarchical format in the Server Logs view, which enables you to more easily understand the relationships that exist between the records. When you enable cross-component tracing, the Server Logs view becomes an even more powerful tool for problem determination.
When you enable cross-component tracing on a server, invocation records are generated during Service Component Architecture processing of modules and components. The invocation records include information about any errors or events that had occurred during processing, such as runtime exceptions. If you choose to enable cross-component tracing with the data snapshot feature, the generated invocation records will also contain the invocation input and output data that was passed between the components during processing.
You can enable or disable cross-component tracing for a server from either the Server Logs view or the server administrative console.
If you enable cross-component tracing from the Server Logs view, the tracing is only enabled for the duration of the server session. When you next stop or restart the server, the cross-component trace state will automatically be disabled by default. By comparison, if you enable cross-component tracing for a server from the server administrative console, the cross-component tracing will remain enabled for all sessions of the server until you choose to disable it again.
When you enable or disable cross-component tracing, you can choose from one of the following options:
- Disabled
- This option disables cross-component tracing. No invocation records are generated in the server console and logs.
- Enabled
- This option enables cross-component tracing. Invocation records are generated into both the server console and the System.Out and trace.log files, but the record properties do not include any invocation input and output data. The System.Out and trace.log files are located in the server log directory.
For example: D:\Program Files\IBM\WID62\pf\wps\logs\server1
- Enabled with Data Snapshot
- This option enables cross-component tracing with the data snapshot feature. Invocation records are generated into both the server console and the System.Out and trace.log files, but the record properties do include invocation input and output data. This data is captured in input and output files under the logs\xct directory.
For example: C:\Program Files\IBM\WID62\pf\wps\logs\xct