source: fedd/abac-src/ttg/INSTALL @ eec716b

Installation Instructions for the ABAC demo
#       $Id: INSTALL,v 1.8 2003/07/21 16:25:49 jjacobs Exp $    

0. Pre-requisites: JVM v1.3 or higher, Tomcat v4.x, ant (a java make tool)

   J2SE v.1.4 - http://java.sun.com/j2se/

   Tomcat v.4 - http://jakarta.apache.org/tomcat/index.html
   ( http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4/rpms/ )

   Ant -        http://jakarta.apache.org/ant/index.html 


   Note: In these examples, the source code is placed in the users home
         directory, which is denoted by the '~' character (substitute as needed)

1. Setup the classpath variable to include the RBTM and ABAC packages:

   For bash use the following:

        export CLASSPATH=${CLASSPATH}:~/rbtm/classes/rbtm.jar
        export CLASSPATH=${CLASSPATH}:~/ttg/classes/abac.jar

   For c-shell variants use the following:

        setenv CLASSPATH ${CLASSPATH}:~/rbtm/classes/rbtm.jar
        setenv CLASSPATH ${CLASSPATH}:~/ttg/classes/abac.jar

2. Build the java libraries for RBTM packages. You will see some output from 
   the java compiler.  If the build is sucessful there will also be jar tool 
   output.

        cd ~/rbtm
        make

3. Build the java libraries for the RTML packages. You see some output from
   the java compilier. If the build is successful there be a jar file 
   generated.

        cd ~/rtml/src
        ant clean 
        ant compile 
        ant jar

4. Build the java libraries for ABAC packages. You will see some output from 
   the java compiler. If the build is sucessful there will also be jar tool 
   output.

        cd ~/ttg
        make

5. Compile and deploy the servlet. You will need to have tomcat installed. The
   ant build.xml file uses classes to deploy and reload the servlet directly
   (see http://jakarta.apache.org/tomcat/tomcat-4.0-doc/RUNNING.txt and 
    http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/processes.html for 
   detailed instructions). Make sure the catalina-ant.jar file included in this
   distribution is in the classpath environment variable.

        cd demo                 # the demo subdirectory contains the sources
        ant clean all           # make sure there are no left over files
        dtomcat4 stop           # stop the running tomcat server (if necessary)
        ant deploy              # deploys the servlet into /var/tomcat4/webapps
        dtomcat4 start          # restart the tomcat server
        
   Note: alternately you can use /etc/init.d/tomcat instead of dtomcat4

6. On the client side, run the launch script in the ttg/test directory. The
   script defines a property java.rmi.server.hostname which needs to be 
   customized for the correct hostname (IP addresses also work).

        cd ttg
        cd test
        ./launch

7. By default tomcat serves web pages on port 8080 and 8180. Point your client
   browser at http://your.host.name:8180/demo/session to authenticate with the
   servlet and then use http://your.host.name:8180/demo/sweden to access the
   demo apllication.

   Note: If RMIExceptions are encountered, try turning on RMI debugging 
         facilities, using the following:

         For csh variants: setenv CATALINA_OPTS -Dsun.rmi.client.logCalls=true

         For bash variants: export CATALINA_OPTS=-Dsun.rmi.client.logCalls=true


8. Servlet logs can be found in /var/tomcat4/logs directory in the files 
   catalina.out and localhost_log*.txt


9. Visualization requirements - the visualizer relies on Grappa, which is a 
   subset Java port of GraphViz. Grappa can be found at:
   http://www.research.att.com/~john/Grappa/   and GraphViz is available at:
   http://www.research.att.com/sw/tools/graphviz/

   After installing the GraphViz package, the visualization tool is launch by 
   typing the following:

   cd atnvis
   cd demo
   java -jar ../atnvis.jar USSH.prop SAdmir.prop

   In the above example USSH.prop and SAdmir.prop are visualization logs 
   created during the negotiation process. For scenarios involving complex 
   policies, it may be desirable to show only one visualization log (e.g. in 
   the above example remove SAdmir.prop from the command line)