Content Management > PTC Server connection Setup > Logging Interactions with a PTC Server
  
Logging Interactions with a PTC Server
You can log all of the interactions between the PTC Server connection and a PTC Server. Logging generates a lot of information, so you should only turn logging on for troubleshooting or similar situations. You can enable logging in the following ways:
Adding a value to the WindchillAdapterLogFile parameter in the userprefs.xml configuration file.
Setting the APTWCLOGFILE environment variable.
This is the preferred method and will override the value of the WindchillAdapterLogFile parameter.
In either case, specify a directory path and base file name for the log to enable logging. Arbortext Editor uses this value to create a log file containing its unique process ID (PID).
The log file name takes the form filename-PID.ext, where the file name and file extension are specified by the logging setting, and PID is the process ID for the active Arbortext Editor executable. The path must be for a directory that already exists. For example, if you set the logging to the following value:
C:\temp\ptcServer.log
The PTC Server connection could create a log file such as the following:
C:\temp\ptcServer-1332.log
Each log file is cumulative for its unique process ID. The log file is not deleted when a session ends. If you use logging, you should delete the log files periodically.