1 | Installation Instructions for the ABAC demo |
---|
2 | # $Id: INSTALL,v 1.8 2003/07/21 16:25:49 jjacobs Exp $ |
---|
3 | |
---|
4 | 0. Pre-requisites: JVM v1.3 or higher, Tomcat v4.x, ant (a java make tool) |
---|
5 | |
---|
6 | J2SE v.1.4 - http://java.sun.com/j2se/ |
---|
7 | |
---|
8 | Tomcat v.4 - http://jakarta.apache.org/tomcat/index.html |
---|
9 | ( http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4/rpms/ ) |
---|
10 | |
---|
11 | Ant - http://jakarta.apache.org/ant/index.html |
---|
12 | |
---|
13 | |
---|
14 | Note: In these examples, the source code is placed in the users home |
---|
15 | directory, which is denoted by the '~' character (substitute as needed) |
---|
16 | |
---|
17 | 1. Setup the classpath variable to include the RBTM and ABAC packages: |
---|
18 | |
---|
19 | For bash use the following: |
---|
20 | |
---|
21 | export CLASSPATH=${CLASSPATH}:~/rbtm/classes/rbtm.jar |
---|
22 | export CLASSPATH=${CLASSPATH}:~/ttg/classes/abac.jar |
---|
23 | |
---|
24 | For c-shell variants use the following: |
---|
25 | |
---|
26 | setenv CLASSPATH ${CLASSPATH}:~/rbtm/classes/rbtm.jar |
---|
27 | setenv CLASSPATH ${CLASSPATH}:~/ttg/classes/abac.jar |
---|
28 | |
---|
29 | 2. Build the java libraries for RBTM packages. You will see some output from |
---|
30 | the java compiler. If the build is sucessful there will also be jar tool |
---|
31 | output. |
---|
32 | |
---|
33 | cd ~/rbtm |
---|
34 | make |
---|
35 | |
---|
36 | 3. Build the java libraries for the RTML packages. You see some output from |
---|
37 | the java compilier. If the build is successful there be a jar file |
---|
38 | generated. |
---|
39 | |
---|
40 | cd ~/rtml/src |
---|
41 | ant clean |
---|
42 | ant compile |
---|
43 | ant jar |
---|
44 | |
---|
45 | 4. Build the java libraries for ABAC packages. You will see some output from |
---|
46 | the java compiler. If the build is sucessful there will also be jar tool |
---|
47 | output. |
---|
48 | |
---|
49 | cd ~/ttg |
---|
50 | make |
---|
51 | |
---|
52 | 5. Compile and deploy the servlet. You will need to have tomcat installed. The |
---|
53 | ant build.xml file uses classes to deploy and reload the servlet directly |
---|
54 | (see http://jakarta.apache.org/tomcat/tomcat-4.0-doc/RUNNING.txt and |
---|
55 | http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/processes.html for |
---|
56 | detailed instructions). Make sure the catalina-ant.jar file included in this |
---|
57 | distribution is in the classpath environment variable. |
---|
58 | |
---|
59 | cd demo # the demo subdirectory contains the sources |
---|
60 | ant clean all # make sure there are no left over files |
---|
61 | dtomcat4 stop # stop the running tomcat server (if necessary) |
---|
62 | ant deploy # deploys the servlet into /var/tomcat4/webapps |
---|
63 | dtomcat4 start # restart the tomcat server |
---|
64 | |
---|
65 | Note: alternately you can use /etc/init.d/tomcat instead of dtomcat4 |
---|
66 | |
---|
67 | 6. On the client side, run the launch script in the ttg/test directory. The |
---|
68 | script defines a property java.rmi.server.hostname which needs to be |
---|
69 | customized for the correct hostname (IP addresses also work). |
---|
70 | |
---|
71 | cd ttg |
---|
72 | cd test |
---|
73 | ./launch |
---|
74 | |
---|
75 | 7. By default tomcat serves web pages on port 8080 and 8180. Point your client |
---|
76 | browser at http://your.host.name:8180/demo/session to authenticate with the |
---|
77 | servlet and then use http://your.host.name:8180/demo/sweden to access the |
---|
78 | demo apllication. |
---|
79 | |
---|
80 | Note: If RMIExceptions are encountered, try turning on RMI debugging |
---|
81 | facilities, using the following: |
---|
82 | |
---|
83 | For csh variants: setenv CATALINA_OPTS -Dsun.rmi.client.logCalls=true |
---|
84 | |
---|
85 | For bash variants: export CATALINA_OPTS=-Dsun.rmi.client.logCalls=true |
---|
86 | |
---|
87 | |
---|
88 | 8. Servlet logs can be found in /var/tomcat4/logs directory in the files |
---|
89 | catalina.out and localhost_log*.txt |
---|
90 | |
---|
91 | |
---|
92 | 9. Visualization requirements - the visualizer relies on Grappa, which is a |
---|
93 | subset Java port of GraphViz. Grappa can be found at: |
---|
94 | http://www.research.att.com/~john/Grappa/ and GraphViz is available at: |
---|
95 | http://www.research.att.com/sw/tools/graphviz/ |
---|
96 | |
---|
97 | After installing the GraphViz package, the visualization tool is launch by |
---|
98 | typing the following: |
---|
99 | |
---|
100 | cd atnvis |
---|
101 | cd demo |
---|
102 | java -jar ../atnvis.jar USSH.prop SAdmir.prop |
---|
103 | |
---|
104 | In the above example USSH.prop and SAdmir.prop are visualization logs |
---|
105 | created during the negotiation process. For scenarios involving complex |
---|
106 | policies, it may be desirable to show only one visualization log (e.g. in |
---|
107 | the above example remove SAdmir.prop from the command line) |
---|