Configuration of the GNU Enterprise Application Server
======================================================

First of all, you have to configure the connection to the database backend.
Please refer to the file "configuration.txt" in the documentation of GNUe
Common for this.


1. Create the basic database
----------------------------

Before you can start gnue-appserver, you have to create a database and populate
it with some system tables.

For PostgreSQL, Firebird/Interbase, MySQL or SQLite:
* execute the script 'gnue-setupdb'

All other database servers:
* create your database as described in your database documentation
* make sure you have access to this database and it fits your settings in your
  connections.conf
* in the directory "/usr/share/gnue/appserver" (if you installed a prepackaged
  version) or "/usr/local/gnue/share/gnue/appserver" (if you installed from the
  source packages), run the command "gnue-schema --connection=gnue gnue.gsd".

At this point, you should be able to run gnue-appserver.


2. Feed applications into the application server
------------------------------------------------

The GNU Enterprise Application Server defines a directory (or a list of
directories) to be the "module path".  Applications written for the GNU
Enterprise Application Server provide files with the ending ".gcd" and ".gld".
These files have to be copied into that directory (or into one of the
directories in the list, respectively), or a subdirectory thereof.

The module path can be defined with the "modulepath" configuration option in
gnue.conf and overridden with the "--modulepath" command line parameter to
gnue-appserver.  If you wish to specify a list of directories to search
through, separate the directories by a semicolon (";").

If the module path is neither configured in gnue.conf nor specified on the
command line, it defaults to "/usr/share/gnue/appserver" for prepackaged
installs, and to "/usr/local/gnue/share/gnue/appserver" for standard installs
from the source packages.

Whenever you change a file in the module path, you can send the running
gnue-appserver process a SIGHUP signal, this will make all changes become
effective.

Some applications also provide files with an extension of ".gsd" that contain
default or sample data.  You can read in those files with the command
"gnue-schema --connection=gnue <filename>".


3. Configure access to gnue-appserver for the front end
-------------------------------------------------------

On the machine running the front ends (gnue-forms, gnue-reports,
gnue-designer), you need an entry in the connections.conf that points to the
Application Server.  If you have the front ends installed on the same machine
as gnue-appserver, there's only a single connections.conf with both entries.

Example for a correct connections.conf entry on the machine running gnue-forms,
gnue-reports or gnue-designer:

  [appserver]
  comment = Connection to the GNUe Application Server
  provider = appserver
  rpctype = xmlrpc
  host = localhost
  port = 8765
  transport = http
