Communication traces contain all the communications traffic associated with a particular session. Unlike the other types of information, your communications traces are not displayed in the Status window. The information is sent directly to a trace file. Each trace creates a separate temporary file which can be saved after the trace is stopped. The Status window displays all the sessions that can be traced, indicating which are running traces and which are not.
Similar to API traces, you can start and stop a trace until you capture all the communications traffic you need.
The Communications Page
This page displays all the sessions that can be traced, indicating which are running traces and which are not. Adding and removing sessions to this page is similar to opening and closing a file. In fact, you use the same buttons or menu commands here as you would to open or close an API trace file.
The Communications page provides:
A Running icon to indicate if the trace is recording or stopped.
The name of the session being traced.
The machine on which the session is running.
The type of connection the session is using.
The number of events in the trace.
The size of the trace (in bytes).
The name of the files used to save the trace, and the temporary file used to build the trace.