Install Guide for the glite-data-transfer-fts component.

0. Prerequisites
   =============
   
   We assume there is tomcat5 installed at the usual location.
   We assume that a database backend has been installed at the usual 
   location and is running (we have tested with MySQL 4.0.20).

1. Simple Configuration
   ====================

   Using the default values from the 
   	$GLITE_LOCATION/etc/glite-data-transfer-fts/config.properties
   file, you only have to run the 
   	$GLITE_LOCATION/sbin/glite-data-transfer-fts-configure.sh
   program and restart tomcat5, using "service tomcat5 restart".

   For example, if $GLITE_LOCATION is "/opt/glite", then the command is

     /opt/glite/sbin/glite-data-transfer-fts-configure.sh --vo site-fts

   You can test the service by looking at the following URL:
    
     http://localhost:8080/site-fts/glite-data-transfer-fts

   and use it, trying a test method:

     http://localhost:8080/site-fts/glite-data-transfer-fts/services/FileTransfer?method=getVersion

2. Unconfigure
   ===========

   Run the VO specific unconfigure script:
    
     $GLITE_LOCATION/etc/glite-data-transfer-fts/glite-data-transfer-fts-site-fts.unconfigure

   IMPORTANT: the unconfigure script will remove the database without any question!
   Please edit the file or back up your database, if it has to be preserved!

3. Explained
   =========

   The service needs a context.xml file for Tomcat. This is 
   generated into the 'etc' directory and then copied to the tomcat
   configuration directory: /etc/tomcat5/Catalina/localhost.

   For the database connection the JDBC driver has to be copied into 
   Tomcat's 'common/lib' directory. The jar files are not part of the
   RPM (due to license restrictions), so the configuration script 
   cannot copy them to the appropriate place, but it prints out the 
   exact commands on how to do this by hand.

   One can run the script only to instanciate the templates and print
   the commands using the '--dryrun' option. This way one can do the
   steps one-by-one to debug possible errors.