General Administration

Tracing an Error

 

Client Side Tracing
 

Java Client - Preferences Mask
In Java Client, the trace settings can be done with <ep_root>/java/ini/jacc.defaults.
Open the Preferences mask.
Select Logging.

Select the Info checkbox for:

  • com.agile.eci.DefaultEciCallbackServer
  • com.agile.eci.EciClient
  • com.agile.eci.EciCon
For these ECI classes, the Trace checkbox has to be deselected.
On the Preferences > Logging mask, select the Show log and Display milliseconds checkboxes.
Click OK to confirm the changes and to close the mask.
   
 

Java Client - Tools > Tracing
Information about tracing in the UI can be found in the Online Help Getting Started > Tracing.
   
 

Batch Client

Use the testclient.properties file for the trace settings.
<batch_root>/cmd/testclient.properties

At the following section,
%batch_root%\cmd\batchclient.cmd -p %batch_root%\ppo\ppo.properties -i %batch_root%\ppo\ppo.java

Add the tracing properties.
%batch_root%\cmd\batchclient.cmd -T %batch_root%\cmd\testclient.properties -p %batch_root%\ppo\ppo.properties -i %batch_root%\ppo\ppo.java
If the testclient.properties are missing, use the Java Client properties from jacc.defaults.
   
 

Server Side Tracing
 

EP_DEBUG Optional
   
 

The variable EP_DEBUG controls the amount of debug messages generated by the PLM server. It is usually set in the customization script of a PLM environment.
In debug mode, the server will redirect stderr and stdout to the following files:

- stderr: $ep_root/tmp/axalant-<hostname>-<pid>.err
- stdout: $ep_root/tmp/axalant-<hostname>-<pid>.out

The syntax for the variable contents is a comma separated list of three-letter modules IDs like, e.g. "Cfg, Mod, Dux".

This, for example, will activate the debug output of the server's main routine and of these three modules. The IDs correspond to the modules IDs used in the module configuration of the PLM environment.

The following special values are also supported:

Value Description
0 No debug output
MenuFilter No menu filtering is performed
_all_ Debug output for all modules and no menu filtering
Main Debug output for main.
Since Agile e6, the deprecated variables EDB_DEBUG and AXALANT_DEBUG are ignored by the server.
   
 

In Case of an Error
   
  If EP_DEBUG is enabled, the C++ modules can display a callstack in the message window. This allows to quickly find the error producing location and the error message module is able to point to a specific source location.
   
 

Tracing C++ Modules

Create a file %ep_root%\init\<environment>_trace.edb.
This file should contain class and option pairs.

The value for option can be:

  • debug
    To trace the module
  • silent
    To switch the tracing for the module off
 

Example:

The modules CPS, Classification, and Changemanagement have been used.

In the file %ep_root%\init\<environment>.xml, add TraceConfig = <environment>_trace.edb to the section GENERAL.

[General]
ModuleConfig = axalant.edb
TraceConfig = <environment>_trace.edb
UseCommonTraceFile = 1
   
 

Specific Tracing
 

Business Server
For detailed information on Workflow tracing and related Log4J information please refer to the Online Help for Workflow > Manager Information > Tracing.