
Xprint F.A.Q. Document revision 10 (16.09.2008)
Page 66/89
Go to the properties of the “My computer” icon and click on the “Advanced” tab, there click on
the button “Environment variable”. Create DIST _DBG in the system list. Restart the
DMG_Distributor service.
All the debug information is written in $DMGRelay_HOME/Xp_Distributor.d/jointfilesconvert/458560/bg.
Q.8 How to get debugging for the DMG Relay – callback collector
Create the file Xp_Collector.d/jointfilesconvert/458560/bg in the directory $DMG_COLLECTOR_HOME/
- touch Xp_Collector.d/jointfilesconvert/458560/bg
- chmod 777 Xp_Collector.d/jointfilesconvert/458560/bg (or give the write permission to the user who started the collector)
Q.9 How to get debugging for the DMG Interface
You will find a few log files in $DMG_SERVER_HOME/LOG/
- xpCallback.log – provides you with information about the callback retrieved and processed by
the DMG Interface
- xpStartgui.log – provides you with information about the users connections.
You can get debugging information regarding the callbacks retrieved and processed by the DMG
Interface by editing the file $DMG_SERVER_HOME/CALLBACK/xpIni.ini and by setting up the
directive “debug” to “TRUE”.
Q.10 How to get debugging from the callback daemon
This operation can only be done if requested by the development team. Edit
$DMG_HOME/DAEMON/callbackDaemon.php, switch the constant “DEBUGMODE” to true.
You can find the debugging information in the following file:
$DMG_SERVER_HOME/LOG/callBackDaemonDefaultLog.log
Q.11 How to get debugging for xpexpimpdata:
For this unix shell script two levels for diagnose are possible:
Kommentare zu diesen Handbüchern