rh._.exports({"0":[[" ","Qlarius Sample Application"]],"1":[[" ","Qlarius \n Sample Application"," ","To help explain the XML format, this \n section examines a build configuration and export an XML file from the \n Qlarius Java sample application that currently ships with Dimensions. \n This enables you to compare the data displayed in the Build user interface \n with the same information in the XML file. Since the source files for \n this sample are already installed with the qlarius_cm database, setting \n up a build configuration and build area are the only steps that you need \n to do to start using it. Two sample build configurations are described \n that you can place into stand alone files and import into Build."," ","NOTE  ","C","ontact your Dimensions \n administrator if your installation does not contain the Qlarius sample \n database."," ","Log in to Dimensions Build and look \n at the entire Qlarius configuration. Notice that there are two main directories \n with source code in this sample:"," ","qlarius\\interfaces"," ","qlarius\\utilities"," ","Each of these directories contains various \n Java sources that can be built into class files. Some of the sources in \n ’interfaces’ depends on sources in ’utilities’ so you need to be aware \n of this when setting up your build."," ","NOTE  "," ","The Id attribute on most of the tags \n in the configuration file is assigned by Build and is unique to each item \n on the database and in the file. It is mainly used in a configuration \n file to maintain the relationships between source, target, and transition \n items. For example:"," ","Source A has an ID of 1"," ","Source B has an ID of 2"," ","Target AA has an ID of 3"," ","A transition to create Target AA would \n have an output ID of 3 with two source files of ID 1 and ID 2. The ID \n numbers are used to connect the source and target files together."," ","The Id number can be any numeric value \n as long as each Id is unique to the item it is identifying and all the \n pieces can be put together. Once the items are imported into the database, \n they are all assigned new Ids that are unique to the new database. The \n Id fields on other items (build areas, etc.) are ignored as they do not \n provide any relationship information that is required for the import process."]],"id":"331"})