The trace viewer is provided with Flynet Viewer to assist in diagnosing common problems encountered during testing. You use the trace viewer anytime your application is working incorrectly and debugging information is needed to resolve the issues.
You will need to ensure trace is active on your Flynet Viewer Server--you can check this with the Administration Window Setting for Tracing.
How it Works
The Trace Viewer utilizes XML-over-HTTP requests to the Flynet Viewer Service, so you can run the Trace Viewer on any machine that can open an HTTP request to your Flynet Viewer server.
On the Flynet Viewer Server, there are one or more trace files that are combined to produce the output you see in the Trace Viewer. Both of these files reside in the active Logging Folder which is set using the Service Settings in the Admin Window:
•FlyHL.log Contains log entries produced by the FlyHLLAPI interface or the FlyScreen COM object
•FlyServ.Log Contains log entries produced by the FlyServer service itself
Accurate Sequencing of Trace Events
Based on your filter options, these two files are merged into a single HTML document which is then displayed in the viewer in perfect sequence. What that means is that during runtime activity, there is a common trace counter shared between all tracing threads. This counter is used in addition to a timestamp to ensure that the activities viewed in the trace window are displayed in the exact sequence that they are produced.
Since timing bugs are so common while testing screen integration applications, "correct order" of trace elements is crucial to your ability to properly interpret the trace output.