Administrator's Guide

How to configure integration with Bazaar

For the purpose of making the integration of TrackStudio and Bazaar workable, you need to install special add-on to Bazaar bzr-xmloutput. It must be installed on that server, where Bazaar is installed, with which TrackStudio will be connected.

For OS GNU/Linux

  1. Download the archive from launchpad
  2. Under the user, by which TrackStudio will be run, create a catalog ~/.bazaar/plugins/xmloutput
  3. Extract the contents of archive into it

Exporting and Importing of Database. Migration

Important! Below described mechanism for transfer of data is intended for transferring only between similar versions of TrackStudio 4. For upgrading from version 3.5 and earlier, upgrade mechanism needs to be used.

Compiling TrackStudio from source code

For the purpose of compiling TrackStudio, you will need Java SDK and Apache Ant. It would be even better if you have some IDE, but for minor changes even a simple text editor will be sufficient.

How to compile the project without using IDE

Make sure that Ant is installed correctly. For this, in the command line or terminal you have to type


How to change TrackStudio URL

By default, TrackStudio opens at the address http://localhost:8888/TrackStudio.
What needs to be done so as to “transfer” TrackStudio to


In the file webapps/TrackStudio.xml , change the following

<Set name="contextPath">/</Set>
  <Set name="war"><SystemProperty name="jetty.home" default="."/>/webapps/TrackStudio</Set>

Thereafter, in the file etc/jetty.xml, write the comment


How to configure JES mail-server

For the purpose of using notifications system and feature of importing messages from email as tasks, TrackStudio requires POP3/SMTP server. And for this purpose, you can use any server you know (or even mail service like Gmail or Yandex Mail). For configuring and testing you can also use pre-configured Java E-mail Server (JES) shipped with in TrackStudio Standalone.

So as to use JES for sending notifications:

How to Localize TrackStudio Interface

This article describes how simple it is to localize TrackStudio interface independently.

Security Settings

Generally we ship the examples of customized configurations, in which the root user has the login — root and password — root, and for all other users the password will be the same as the name of user account. For test copies, do not open access for external IPs, until you have changed all the passwords. For restricting the possibility of accessing the system from external IPs, edit the property in the file jetty/etc/jetty.xml:

<Call name="addConnector">

Using a console app dbtool for exporting and importing a database

In TrackStudio Enterprise 4.0.10 we added a console app dbtool export and import database. Now you can get an anonymized backup file without windows graphic environment.

It's very easy to use the application:

Attention! This app uses TrackStudio properties files for database connection parameters. Please, stop TrackStudio Server before use.
  1. Go to TrackStudio directory
  2. Type following in console
  3. dbtool export -a --file=export-a-20100129.xml

Extending and Overriding the Roles

There can be times when a developer in the project needs to perform the role of tester also. This requires the user permissions to be extended. In this case the user must be once again added in the access control rules, and then the group needs to be edited in one of the entries:

If user is simply added in the access permissions and assigned another role, he will have two roles: his own (corresponding to his user account) and the overridden one.

Syndicate content