Documentation Center

Logging TM and alignment processes

This appendix describes how you can use WorldServer logging facilities to gather information that may help you diagnose TM and alignment issues.

If you are investigating TM or TM alignment-related issues, it is often useful to collect debugging information. To do this, enable the WorldServer debug logging for these processes.
TM Debug Logging
To enable general TM-related logging, add this entry to the general.properties file:
log4j.category.com.idiominc.ws.tm=debug
TMX Alignment and Asset Alignment Logging
To enable alignment-related logging, add this entry to the general.properties file:
log4j.category.com.idiominc.ws.autoalignment=debug
Configuring a Separate File for Collecting Debug Information
The TM- and alignment-related debug options result in a substantial amount of data being added to the WorldServer logs. Instead of writing the information to the standard WorldServer log file, consider configuring dedicated log files for each.
To do this, you can configure a new rolling file appender within the general.properties file, and using this appender to collect the debug data. This example shows how you would do this to capture alignment data in a separate file:
# enable WorldServer alignment debug messages
log4j.category.com.idiominc.ws.autoalignment=debug
# Create an Appender for logging alignment-engine debug messages
log4j.appender.alogfile.File=C:/logs/alignmentlog2.txt
log4j.appender.alogfile=org.apache.log4j.RollingFileAppender
log4j.appender.alogfile.MaxFileSize=100000KB
log4j.appender.alogfile.MaxBackupIndex=100
log4j.appender.alogfile.layout=org.apache.log4j.PatternLayout
log4j.appender.alogfile.layout.ConversionPattern=[%d]: %m%n