Generic Release Note for Danno/Dannotate Binary Releases
========================================================

This document is a brief starting point for using Danno/Dannotate binary 
releases.  For more extensive information on the software, please refer
to the Danno Project Site at http://metadata.net/sites/danno/.  The
site is intended to be the "one stop shop" for information on using
Danno and Dannotate, and includes 

    * the Dannotate User documentation, 
    * Danno/Dannotate installation and configuration instructions, and
    * technical documentation for system integrators.
    
License
-------

Refer to the LICENSE.txt file.

Contents
--------

A Danno/Dannotate binary release consists of preconfigured WAR files 
for easy demonstration of the Danno and Dannotate software.  There
are currently 3 WAR files:

    * dannodemo.war - this is the WAR file for a webapp that provides
      both Danno and Dannotate services.  This is probably the one
      that you want to use for a trial installation.

    * danno.war - this is the WAR file for a webapp that provides
      the Danno services only.
    
    * dannotate.war - this is the WAR file for a webapp that provides
      the Dannotate services only.  It is intended to demonstrate the
      use-case where Dannotate uses a Danno service installed remotely.
      
All three webapps are preconfigured to use 'localhost' as the hostname
and (for the first two) Sesame as Danno's back-end triple store.
 
Installation
------------
 
The WAR files are designed to be installed on a Tomcat 5.5 server as 
follows:
 
    1. Choose the WAR file to be installed, per the above descriptions.
    
    2. Copy the WAR file to Tomcat webapps directory; for example:
    
           $cp dannodemo.war $CATALINA_HOME/webapps

       Note that you should use the same file name for the deployed WAR file.
       The deployed WAR file name determines the container name, and the 
       container name has to match configuration properties.
       
    3. If you are using (say) an Apache HTTPD front-end as a reverse proxy 
       for your Tomcat server, adjust the Apache configuration so that 
       requests are forwarded.  For example, assuming that you are using
       "localhost" as your hostname, the following will tell HTTPD to 
       forward requests for "http://localhost:80/dannodemo/*" to appropriate
       URLs on the Tomcat server listening on port 8080.
 
           ProxyPreserveHost on
           ProxyPass /dannodemo/ http://localhost:8080/dannodemo/
           ProxyPassReverse /dannodemo/ http://localhost:8080/dannodemo/
       
 Tailoring
 ---------
 
 If you want to change aspects of the binary webapps (for example to
 use a real hostname, use a different triple store, change the container
 name), you can edit the relevant configuration files in the deployed
 webapp(s).  However, we recommend that you create a Maven project
 to host the customizations, in the fashion described on the 
 Danno Project Site at http://metadata.net/sites/danno/.  Details of
 the various configuration parameters may be found in the same place.


                                  -oOo-