-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
85 lines (55 loc) · 2.28 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
Building instructions
---------------------
If you have a binary version of Jamm, go down to "Installing Jamm."
To build Jamm, you need to have the following installed:
* Java 1.3.x or Java 1.4.x
http://java.sun.com/
* The Servlet 2.3 and JSP 1.2 APIs
http://java.sun.com/
* XDoclet version 1.2.1
http://xdoclet.sourceforge.net/
* Log4j version 1.2.8
http://jakarta.apache.org/log4j/
* Checkstyle version 3.1
http://checkstyle.sourceforge.net/
* Struts version 1.1 or better
http://jakarta.apache.org/struts/
* Ant version 1.4.1 or better
http://jakarta.apache.org/ant/
* JUnit 3.8.1
http://www.junit.org/
* Jakarta Commons CLI 1.0
http://jakarta.apache.org/commons/cli/index.html
JUnit must be installed into the ${ANT_HOME}/lib/ directory.
Once all that is installed, if you need to make changes to the
values in the src/build.properties file, just make a top level
build.properties file overriding the values you need to change.
Once that is done, you can build the war file by typing:
% ant dist
The war file will be created in the dist directory.
If you need to clean it up
% ant clean
Installing Jamm
---------------
OpenLDAP
--------
Put jamm.schema in your schema directory and make sure that its
included in the slapd.conf. Then create an ldif file to lay down
the basic structure of the top level and the Manager. Use ldapadd
to add them to LDAP, and you should be ready to start using JAMM.
The web parts
-------------
To install Jamm, unjar the war file in the directory you would like
to deploy to. Do not simply just drop the war file there as you
need to do some configuration first.
Once its unjared, go into the WEB-INF directory. Copy
jamm.properties.dist to jamm.properties and edit it so it has that
it matches the configuration for your site.
At this point you should be good to go. You may need to restart
your servlet container, check with your server documentation.
Filesystem cleaner
------------------
cd into the vmail user's home directory and untar the
jammUtils distribution. This will drop a shell-script into
the bin directory and a few jars in the lib directory. jammCleaner
is now ready to be run as the vmail user manually or out of cron.