*************************************************
* Directory: ApplicationRoot/templates
*************************************************

'templates' directory contains two sub directories.
(1) src - contains all source templates - designed by you
(2) preview - may contain .preview files for one or more
          templates. These preview files are basically 
          reversed engineered compiled template files
          that may help in identifying syntax errors in 
          use of ebfTags in your templates.

'templates' directory itself may contain one or more
'.frm' files. These files are compiled templates. ebfServer
template engine uses compiled templates for improved 
performance. 

Don't worry if you have placed source templates in 'src'
directory but you don't see any .frm files in here. Template
engine will automatically compile source files into '.frm' 
file if it can't find one. 

If you made a change in your source templates and would like to
recompile this source file, you have two choices, 
(1) Use ebf Console and issue a 'compile' command.
(2) Remove '.frm' file for related template. 
    Example: remove 'a.html.frm' if you wish to recompile
             'a.html' template.

Suggestion:
===========
If you are running this ebfServer application on multiple
 servers and if you have luxury of having seperate development
server (like we do :-> ), you may want to compile all your
templates on the development server and distribute only '.frm'
files. That is, you may not want to distribute contents of 'src'
on all your servers (you still need to have 'src' and 'preview'
directories).
             



NOTE: 'default' is a standard business unit defined 
      in your application distribution. **DO NOT**
      remove this folder or 'default' business unit
      from your application otherwise, ebfServer may
      not function correctly.

This directory contains folders for all business
units defined in your application.

Each business unit will have a folder containing
unit specific properties and datafiles.

When you add business units using application manager,
app. manager copies contents of 'default' business unit
to your new unit. So, it may be in best interest of your
project to think about all unit variables you need for
each business units, define those variables for 'default'
business unit and then create new business units.

Even if your application does not have multiple business 
units, we recommend that you create one business unit and
define it as 'Default Businesss Unit' using application 
controls in the application manager. i.e. Do not use 'default'
as Default Business Unit but define a new one and call it
default. You will not need to supply business unit id parameter
from the web client because if business unit is not specified
by the client, ebfServer uses 'Default Business Unit' for the
application.
