| MX_TRACE_FILE_PATH |
The directory name for
all trace files. Must be set in platform-specific format. If this variable
is not set, the default location is ENOVIAHOME (UNIX) or ENOVIA_INSTALL (Windows). When using RMI Gateway,
if you want separate files for each server process, set MX_TRACE_FILE_PATH
to different directories in the rmireg for each of the rmi processes
and the trace files will be created under each of these directories. |
| MX_MQL_TRACE
|
May be set to a filename for use
with timing tests and debugging of program objects and wizards. Output
is generated that shows start and end of all programs executed (Tcl or
Java), all MQL commands processed within a Tcl program, or calls made
through the ENOVIA Studio Customization Toolkit MQLCommand interface. The file
specified is located in MX_TRACE_FILE_PATH. |
| MX_SQL_TRACE |
May be set to a filename to trace
all SQL commands generated by ENOVIA Live Collaboration for database
access. The file is located in MX_TRACE_FILE_PATH. |
| MX_VERBOSE_TRACE |
May be set to a filename to
contain tracing for all client/server calls. The file specified is located
in MX_TRACE_FILE_PATH. If the ENOVIA Studio Customization Toolkit Origin
Trace Facility is configured on an ENOVIA Live Collaboration Server,
verbose output includes information about the parameters being passed. |
| MX_FTP_TRACE |
May be set to a filename that logs
the interaction of ENOVIA Live Collaboration with the FTP server. The
file specified is located in MX_TRACE_FILE_PATH. It is recommended to use this setting only while troubleshooting FTP problems and then to
disable it again when problems are solved. |
| MX_JPO_TRACE |
May be set to a filename that logs
the compilation and classloader messages of JPOs. The file specified
is located in MX_TRACE_FILE_PATH. |
| MX_SMTP_TRACE |
May be set to a filename that logs
the interaction of ENOVIA Live Collaboration with the SMTP server. The
file specified is located in MX_TRACE_FILE_PATH. |
| MX_LDAP_TRACE |
May be set to a filename that logs
the interaction of ENOVIA Live Collaboration with the LDAP server. The
file specified is located in MX_TRACE_FILE_PATH. |
| MX_TRIGGER_TRACE |
May be set to a filename for
the ENOVIA Live Collaboration event log. The log contains information
for each trigger that is fired during that session. The file specified
is located in MX_TRACE_FILE_PATH. |
| MX_WORKFLOW_TRACE |
May be set to a filename that
traces the logic executed to process workflow events. It is useful for
debugging workflow behavior. The file specified is located in MX_TRACE_FILE_PATH. |
| MX_INDEX_TRACE |
Can be set to a filename to detect queries/expands
that can benefit by using an index. When enabled, a message is logged
whenever a query/expand is executed in which none of the items in the
where clause are included in any index. The file specified is located
in MX_TRACE_FILE_PATH. When this trace type is enabled, trace messages
will be displayed in the format: No index found for field1,field2,field3?
A developer can conclude that adding at least some of
the listed fields to a new or existing index (and enabling it) may improve
system performance. |
| MX_DS_TRACE |
May be set to a filename that logs
most of the interaction between ENOVIA Live Collaboration and the Synchronicity DesignSync Data Manager
server. Errors related to checkin or checkout are not logged. The file
specified is located in MX_TRACE_FILE_PATH. It is recommended to use this
setting only while troubleshooting Synchronicity DesignSync Data Manager File Access problems
and then to disable it again when problems are solved. |