TrackStudio does not contain graphical libraries for generating colors and fonts and other AWT information. For that, Java relies on the system's libraries for providing that information. Thus an environment capable of providing AWT information and a graphics card (for exporting to static formats) are required. 

In a Windows environment, nothing extra needs to be done to set up such an environment as it already exists. A GUI interface is already running and a graphics card already exists. 

For non-Windows environments (such as Unix and Linux), such is usually not the case. You need to have X or some form of X running on such systems and point the display to the machine running X (such as running the command export DISPLAY=192.168.0.16:0.0 in a korn shell). For best performance, TrackStudio recommends running X on the machine (or setting the DISPLAY to point to another machine running X). However, if that is not an acceptable solution, there are alternative solutions available. 

If your TrackStudio UNIX server does not have an X11 Server installed or the DISPLAY environment variable is not set, you may receive one of the following errors when executing your reports:

Can't connect to X11 window server using ':0.0'
  as the value of the DISPLAY variable., stack:
java.lang.InternalError: Can't connect to X11 window server using
  ':0.0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)

or

Internal error: exception thrown from the servlet service
function (uri=/xxx/xxx2.jsp):
java.lang.NoClassDefFoundError: java/awt/SystemColor, stack:
java.lang.NoClassDefFoundError: java/awt/SystemColor
   at com.sas.visuals.BaseBorder.<init>(BaseBorder.java:209)

Possible circumventions follow: 

1) Install the X11 Server and set the DISPLAY environment variable. 

2) Upgrade to Java 1.4 and pass the parameter -Djava.awt.headless=true to java when you run it. This no longer requires Xvfb to be running, but it does require the X11 packages to be installed. 

Where to specify the options will vary between servlet engines. For example, for Tomcat 3.x, you would specify these options in the tomcat.bat or tomcat.sh file for TOMCAT_OPTS. For Tomcat 4.x, you would specify these options in the catalina.bat or catalina.sh file for CATALINA_OPTS. 

3) If your server does not have a display environment, and you cannot upgrade to jdk 1.4, you can install a virtual frame buffer. Xvfb is available at http://www.x.org . It simulates a display environment, and allows the jdk to drawn the images. 

4) Try using the Eteks pure java AWT classes at http://www.eteks.com/pja/en. We know of one user who got it working, but we haven't tried it ourselves.