Trace Setup

Tracing can be enabled on a 7i server through a series of registry values. This can be a cumbersome process for some users and mistakes made in the registry editor can have an adverse impact on the software or even the operating system.

To simplify the process, an editor was put in place to allow those values to be edited in an easier way. The result of these settings is the same in the registry as they would have been before.

Performance note: Tracing can have an adverse impact on the performance of the software. The more modules are traced and the more server activity, the more of an impact tracing may have.

File Path: This is the path on the server that will be used to store the trace files. Typically, one text file is stored per process (Message Processing Host, Click Drag & Drill instance, etc.). When the log/trace file size exceeds 10 MB, a new file is generated for the same process ID.
Enabled: Checkbox used to enable or disable all tracing on the server.
Add Module: If a module is missing from the list it can be added by using the Add Module edit field in combination with the Add button to the right. Some of the .Net modules such as Console or Capture need to be explicitly added if trace is needed for those.
Import: Used to select a reglist.xml file locally on the server to import a group of modules. The user can select available modules from the xml file to be imported into the Trace module list.
All Modules: Enables tracing on all modules. For performance reasons, this is not recommended.
ModuleName: The list of modules to be traced. A checked box next to a module enables tracing for that module.