To enable, from the Desktop Client Console window or when logged into DMCLI, run the following command: set sdp_ trace on /user_directory=<drive:\path to a directory> Once this is set, reproduce the issue which you wish to trace.
The most obvious way to perform custom actions at login/logout is to implement HttpSessionListener interface - which is standard Java interface - (with methods sessionCreated/sessionDestroyed) and declare custom listener in web.xml.
A problem arose where tracing of the Dimensions listener was required so -trace and -tracedir were added to the listener.dat in order to generate the logs. However following an attempted restart of the listener no logs were produced in the target directory specified by -tracedir.
The listener then needs to be restarted in order for this to take effect. However all commands run to the server will be logged. This option must be used for server based or standalone Dimensions commands that are run outside of DMCLI, such as: replicator, pdiff, upload, download etc.
DM_ROOT %DM_ROOT%<BLANK> A listener trace will not create any trace files, but the event viewer on the server will show this error for the Dimensions Listener Service: "dmlsnr 2007/11/12 10:15:42 E P5216 T5280 Failed to start pool manager C:\Serena\Dimensions 10.1\CM\ prog\dmpool.exe"
We would expect to see the dmemail.exe and dmschedule.exe processes started but they are not. In the dmpool trace file there is an error similar to the following:
