Qlarius Sample Application

To help explain the XML format, we will examine a build configuration and export an XML file from the Qlarius Java sample application that currently ships with Dimensions. This will enable you to compare the data displayed in the Build user interface with the same information in the XML file. Since the source files for this sample are already installed with the qlarius_cm database, setting up a build configuration and build area are the only steps that you need to do to start using it. This appendix contains two sample build configurations that you can place into stand alone files and import into Build.

NOTE  Please contact your Dimensions administrator if your installation does not contain the Qlarius sample database.

Log in to Dimensions Build and look at the entire Qlarius configuration. Notice that there are two main directories with source code in this sample:

Each of these directories contains various Java sources that can be built into class files. Some of the sources in ’interfaces’ depends on sources in ’utilities’ so you need to be aware of this when setting up your build.


The Id attribute on most of the tags in the configuration file is assigned by Build and is unique to each item on the database and in the file. It is mainly used in a configuration file to maintain the relationships between source, target, and transition items. For example:

A transition to create Target AA would have an output ID of 3 with two source files of ID 1 and ID 2. The ID numbers are used to connect the source and target files together.

The Id number can be any numeric value as long as each Id is unique to the item it is identifying and all the pieces can be put together. Once the items are imported into the database, they are all assigned new Ids that are unique to the new database. The Id fields on other items (build areas, etc.) are ignored as they do not provide any relationship information that is required for the import process.