Tracing Types

This topic describes the types of information that can be captured in traces.

See Also
Configuring Server Diagnostics with the INI File
Studio Customization Toolkit Origin Trace Facility
ENOVIA Live Collaboration Memory Management

Server diagnostic tools allow the following trace information to be sent to either a file or standard output (the "destination"):

  • SQL output
  • MQL trace: program execution, including both tcl and Java program objects
  • VERBOSE trace of client/server dispatches
  • Server Memory Usage
  • FTP and FTPS communication
  • SMTP communication
  • LDAP communication
  • Trigger execution
  • Workflow debugging
  • Index tracing—to identify queries that could be improved by defining an Index
  • Studio Customization Toolkit calls
  • JPO compilation and classloader messages
  • DesignSync tracing for troubleshooting when implementing a designsync store
  • User-defined trace types

Tracing for the various 3DSpace kernel operations may be turned on and off using:

  • environment variables in the server's UNIX startup script or .ini file settings
  • MQL trace command
  • Studio Customization Toolkit logwriter methods

The directory that will hold the tracing file is defined via the MX_TRACE_FILE_PATH setting in the .ini file or startup script. At any time there is only one file (or output stream) used to receive the tracing output for all types of tracing. The trace settings are read in the following order, and the first one found establishes the output stream or filename for all of them:

  1. VERBOSE
  2. MEMORY
  3. SQL
  4. MQL
  5. INDEX
  6. WORKFLOW
  7. FTP
  8. SMTP
  9. LDAP
  10. TRIGGER
  11. DESIGNSYNC
  12. JPO
  13. LOGWRITER (Studio Customization Toolkit)

For example, if a filename is specified for TRIGGER and SQL tracing, and if VERBOSE tracing is enabled without a filename, the output for all three kinds of tracing will go to stdout. Or, if SQL and MQL tracing are both set to a filename and no other trace variables are set, the output for both will go to the file specified for SQL trace.

The sections that follow describe how to configure tracing using environment variables as well as the output format for tracing. Refer to the MQL Concepts or the Programming Guide for information on using tracing from MQL or the Studio Customization Toolkit.