Config.txt
  This file stores a number of site configuration parameters used at runtime by a zeroCode-generated site. The format of each entry is identical - the name of a configuration element followed by an equals sign (=) and the value of that element. Below are the standard entries that you will see in a generated site.
  siteRoot
This parameter specifies the location of the generated site.
  udmFilesDirectory
This parameter specifies the location of the UDM files. You can make subdirectories in this directory to segment part of your site or its functionality
  templatesDirectory
This parameter specifies the location of the HTML templates of the site. Under this directory, you can create multiple sub-directories that carry the templates. The structure of the subdirectories must be identical to that of the UDM directory, unless otherwise specified in the HTML-to-UDM mapping mechanism.
  schemaFileName
This parameter specifies the path and name of the database schema file - the file that shows the SQL CREATE statements that were used when the site was created or when the Java objects were last regenerated.
  udmCacheSize
This specifies the number of UDMs that the zDE caches when a designer logs in. Caching dramatically improves run-time performance, but increases the demands the zDE makes on system memory.
  defaultHandlerClass
This is the default Java-based program that handles requests for the site. This can be changed for specific URIs by specifying the request handlers for those URIs in the dispatch.xml file.
  database.type
This parameter identifies the type of database used. "Oracle 8" is a typical value.
  database.hostName
This is IP address or the name of the database server.
database.portNumber
This parameter specifies the port number that the site uses to connect to the database server. For an Oracle installation, this is usually 1521. database.name This parameter specifies the name of the database to be used.
database.userName
This parameter specifies the user id to be used to login to the database. This is a typical mechanism, but for specific applications, it may be required to specify different login IDs for different users. This is the default login ID to be used.
database.password This is the password to be used with the default login ID to login to the database.
timeZone This specifies the time zone that is to be used to display time wherever used. A typical value is PST.
databaseObjPkgPrefix All the zeroCode generated Java objects belong to the package specified by this parameter. Typically, the package is called com.siteName.
  In addition to the items above, you can add other name-value pairs with the same syntax that can be used anywhere in your site, in the HTM templates. For example, you may want to set up a site-level webmaster email ID that you would like to control in one location. You would then specify an entry like appWebMaster=john@mycompany.com, say. You can then use the FreeMarker tag $appWebMaster on any HTML template - that parameter will be automatically substituted with the email ID before display.
 

dispatch.xml
This is an XML file that is used customize the request handlers that handle request for certain specific pages. The default request handler specified in the config.txt handles all requests that are not specified in this file.

The following is a sample dispatch.xml file. Each element node in this file corresponds to a request for a page that needs to be handled by a request handler that is different from the default request handler. The following example specifies that request to the appStatus.html should be handled by a request handler zerocode.udm.AppStatusDisplay. The attribute type specifies the data type of the attribute name and in this case should be java.lang.string.