To install and configure TrackStudio Enterprise:

1. Run your DBMS.
2. Create a new database using the corresponding SQL script which you can find in the sql/en directory. If an error occurs during the creation of a new database, TrackStudio may work incorrectly or fail to work completely. Contact us, if such an error occurs.
3. Define the TrackStudio configuration in the files trackstudio.properties, trackstudio.mail.properties and trackstudio.hibernate.properties.
4. Use the TS_CONFIG environment variable to specify the directory name with configuration files (*.properties).
5. Perform the deployment of TrackStudio.war. You can also unpack WAR and perform the deployment of the directory structure.
6. Run the application server.
7. The application is available at http://localhost:port/TrackStudio
8. Use the following to log on: login=root and password=root

JBoss 4.0.1 installation notes:

• After you install TrackStudio, update jboss\jboss-hibernate.deployer\cglib-full-2.0.1.jar to cglib-full-2.0.2.jar and jboss\jboss-hibernate.deployer\hibernate2.jar to hibernate-2.1.8.jar, JBoss has its own outdated version.

ServletExec installation notes:

• After you install TrackStudio, delete xercesImpl.jar reference from the ServletExec startup script (StartServletExec.sh).

You cannot install several TrackStudio instances (test and production, for example) on the same application server instance.

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 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) 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 Tomcat 4.x, you would specify these options in the catalina.bat or catalina.sh file for CATALINA_OPTS.