head	1.3;
access;
symbols
	TIGRIS_1_1_0RC2:1.1
	TIGRIS_1_1_0RC1:1.1
	TIGRIS_1_1:1.1.0.12
	TIGRIS_1_0_8:1.1
	TIGRIS_1_0_8RC3:1.1
	TIGRIS_1_0_8RC2:1.1
	TIGRIS_1_0_8RC1:1.1
	TIGRIS_1_0_7:1.1
	TIGRIS_1_0_7RC3:1.1
	TIGRIS_1_0_7RC2:1.1
	TIGRIS_1_0_7RC1:1.1
	TIGRIS_1_0_6:1.1
	TIGRIS_1_0_6RC5:1.1
	TIGRIS_1_0_6RC4:1.1
	TIGRIS_1_0_6RC3:1.1
	TIGRIS_1_0_6RC2:1.1
	TIGRIS_1_0_6RC1:1.1
	TIGRIS_1_0_5:1.1
	TIGRIS_1_0_5RC6:1.1
	TIGRIS_1_0_5RC5:1.1
	TIGRIS_1_0_5RC4:1.1
	TIGRIS_1_0_5RC3:1.1
	TIGRIS_1_0_5RC2:1.1
	TIGRIS_1_0_5RC1:1.1
	TIGRIS_1_0_4:1.1
	TIGRIS_1_0_3:1.1
	TIGRIS_1_0_2:1.1
	TIGRIS_1_0_1:1.1
	TIGRIS_1_0:1.1.0.14
	TIGRIS_1_0_0:1.1
	TIGRIS_1_0_0_RC1:1.1.0.10
	HELM_PEER_PORT_BRANCH:1.1.0.8
	TIGRIS_0_9_2_4:1.1
	TIGRIS_0_9_2_3:1.1
	TIGRIS_0_9_2:1.1.0.6
	TIGRIS_0_9_0:1.1.0.4
	TIGRIS_0_8_4:1.1.0.2
	TIGRIS_710_FF:1.1;
locks; strict;
comment	@# @;


1.3
date	2001.07.23.20.36.04;	author dlr;	state Exp;
branches;
next	1.2;

1.2
date	2001.07.23.20.35.39;	author dlr;	state Exp;
branches;
next	1.1;

1.1
date	2000.10.31.03.29.29;	author edk;	state Exp;
branches;
next	;


desc
@@


1.3
log
@Clarification.
@
text
@        INSTALLATION

If you're installing Anzu in a standalone fashion, you'll need to do a
number of things manually; and the servlets haven't been tested
carefully.  You'll need to set up access control within Apache (or your
servlet engine) for the URIs which correspond to the Anzu servlets,
since the servlets in this package make no attempt to check permissions.

You'll need to edit each of the *.in files, replacing __{token}__ with
reasonable values.  You'll need to put helm.jar in your classpath, and
run make.  Make will produce bin/anzu-{version}.jar -- you'll need to
put that in the same place where you point the zone.properties line
(from 45anzu.zone.properties.in).  You'll need to include
45anzu.servlets in your jserv.properties (or make equivalent conf file
additions to whatever servlet engine you use).  

        HELM

These steps are appropriate for an install within Helm.

Check Anzu out into whatever directory you'd like.  Go into the root
anzu directory; make sure you've sourced env.sh; then:

$ configure.pl ./
$ make
$ make install

(Note that the make step requires that Helm be installed into the
 sandbox.  Anzu compiles against Helm, and it looks for helm.jar in
 $SANDBOX/site/lib/helm.jar)

At this point, Anzu is installed, but not yet integrated into the
sandbox.  The following steps should integrate it:

$ reconfigure.pl
$ cd $SANDBOX
$ sandboxctl restart
$ helm/scripts/anzu_initialize.sh

Now Anzu is installed, it knows about your domain and one of the test
projects (bsdchess).
@


1.2
log
@Removed Joist reference (changing some to Helm).
@
text
@d19 1
a19 1
These steps are appropriate for an install w/in helm.
@


1.1
log
@add basic instructions
@
text
@d3 1
a3 1
If you're installing anzu in a standalone fashion, you'll need to do a
d6 1
a6 1
servlet engine) for the URIs which correspond to the anzu servlets,
d10 1
a10 1
reasonable values.  You'll need to put joist.jar in your classpath, and
d21 1
a21 1
Check anzu out into whatever directory you'd like.  Go into the root
d28 3
a30 3
(Note that the make step requires that joist be installed into the
 sandbox.  anzu compiles against joist, and it looks for joist.jar in
 $SANDBOX/site/lib/joist.jar)
d32 1
a32 1
At this point, anzu is installed, but not yet integrated into the
d40 1
a40 1
Now anzu is installed, it knows about your domain and one of the test
@

