Version attribute of configuration types is required. This element holds the location of the configuration file. In a complete configuration file, this element cannot exist. If this elements exists, then the rest of the file will be disregarded and configuration information will be uploaded from either FileURL or FileLocation. File URLs are platform independent addresses for files, i.e. file:///home/user or file://c:/documents/user. First this element is checked. If it does not exist, then FileLocation is tried. This holds the physical location of the configuration file, and it is file system dependent name. It is checked after FileURL is tried. Configuration information for the database manager. All the database implementations need to be registered through here. This is the namespace prefix which is associated with the given database implementation, i.e. gxos as in gxos://database/xmlobject/a/b/c Java class name of the database implementer. This is a vendor/developer specific name and must implement org.gxos.xml.Database interface. Parameters are name/value pairs. These value are inserted into a hashtable before sent to database initialization. These values are implementation specific. Java class name of the personal information interface, org.gxos.users.PersonalInfo. This is a list of user defined GXOS objects. At the time initialization, all of these Java classes are loaded into memory and registered with the XML unmarshaller. Configuration file cannot have ConfigFile with DatabaseManager and CustomObjects elements defined at the same time.