Configuring System Environments > Configuration Files
  
Configuration Files
For system administrators, the default configuration files are consolidated in a TomcatInstallDir/webapps/qadhome/configurations/
default
directory. This directory includes the following:
Client bootstrap configuration file (client-bootstrap.xml): defines parameters for the QAD .NET UI client that apply to all system environments associated with the home server (TomcatInstallDir/webapps/qadhome). For more information, see Client Bootstrap Configuration File.
Client session configuration file (client-session.xml): defines session characteristics of a client session. For more information, see Client Session Configuration File. Note that the client-session.xml.sample file included in the configurations directory provides an example backup copy of client-session.xml.
Menu extension configuration file (.../menus/plugin-menu.xml): defines menu items added to the QAD .NET UI outside of the standard programs and functions, along with security settings. For more information, see Menu Extension Configuration File.
In the configurations directory, the default directory provides the system-wide default settings for the home server (TomcatInstallDir/webapps/qadhome). Because it is the default, the default system environment does not appear in the “Log on to” pull-down on the Login window. Be sure not to delete the /configurations/default directory, which specifies the system-wide defaults and is a useful reference when you define other system environments.
You define additional system environments by creating additional directories under the configurations directory. For example, to create a system environment named demo, create a /configurations/demo directory. Copy the client-session.xml file from the /configurations/default directory to the /configurations/demo directory, and copy /configurations/default/menus/plugin-menu.xml to /configurations/demo/menus/plugin-xml. You can now modify the settings in /demo/client-session.xml and /demo/menu/plugin-menu.xml to the demo system environment. Meanwhile, the /default/client-bootstrap.xml file continues to define system-wide settings. (You should not remove or rename the default directory.) When users log in to the QAD .NET UI client, they will now see the demo system environment available in the “Log on to” pull-down menu on the Login window.
In the configurations directory, the storage directory is where menu collections and browse collections are stored when they are saved from Menu Collection Maintenance or Browse Collection Maintenance. The /configurations/storage/menu-collections directory contains XML files representing menu collections and the /configurations/storage/browse-collections directory contains XML files representing browse collections. Menu and browse collections included with the QAD .NET UI are in the menu-collections and browse-collections directories under the .../default/storage directory (TomcatInstallDir/webapps/qadhome/configurations/
default
). To access the menu and browse collections when you set up a system environment, you must copy the menu-collections and browse-collections directories (and their contents) under the appropriate system environment directory. For example, if you have set up a system environment named demo, you need to set up a /configurations/demo/storage directory with the menu-collections and browse-collections subdirectories.
Note: Starting with QAD .NET UI 2.9.3, for QAD Enterprise Applications–Enterprise Edition, you no longer have to copy the files from the default directory. Instead, the QDT-based installation process does that for you based on the system environments you specify while using QDT. This only applies to Enterprise Edition, which uses QDT; for Standard Edition, you must copy the files from the default directory.