Installation instructions for the IMHO system
--------------------------------------------

1. Installing the Apache Jserv module.

 THIS INFORMATION IS WRONG!  USE MOD_WEBAPP

Information on obtaining and installing this module is available at:
http://java.apache.org/jserv/index.html

There is no need for a Java VM to use IMO, although it is helpful to
have one installed to test your installation of Apache JServ.  Follow
all instructions for installing JServ, including having apache load
it's configuration file, jserv.conf

2. Configuring Apache and JServ

After installation JServ we need to tell it how to communication with
the IMO lisp process, and where to find it.  This is done by first
turning off authentication, since IMO does not support it presently,
and then adding an ApJServMount line for the imo process.

To turn of authentication, comment out the ApJServSecretKey directive
and add a new one, with a value of DISABLED, like so:

    #ApJServSecretKey /usr/local/jserv/etc/jserv.secret.key
    ApJServSecretKey DISABLED

Then we add a ApJServMount line for the IMO process:

     ApJServMount /imo ajpv12://localhost:3000

This assumes that you are runnig the Lisp process with IMO on the same
host as the web server, and using the default IMO listener port.  You
can indeed run IMO on a different host or port, changing the above
line appropriatly.

Lastly, we need to tell JServ to not try and start up a Java VM for
our IMO mount point.  We do this by modifying the ApJServManiual
directive, setting it to on, like so;

	   ApJServManual on

3. Installing and configuring The IMO server.

IMO runs inside of a Common Lisp system; CMU Common Lisp is currently
supported.

You must have Mark Kantrowicz's mk-defsystem installed to load the
system properly.  It is best to have the system definition
($IMO/imo/IMO.system) linked into your global system directory.

For instance, if your installation of defsystem searches for systems
in /usr/lib/cmucl/system-definitions/ and you have IMO checked out of
CVS, it's probably best to set up a double indirection, so that the
package appears to be installed in /usr/local/lisp/systems/imo, and
the definition in /usr/lib/cmucl/system-definitions/IMO.system

This would look like:

$ pwd
/usr/lib/cmucl/system-definitions
$ ls -l IMO.system
lrwxrwxrwx   1 jesse    users          38
    Nov 17 22:28 IMO.system -> /usr/local/lisp/systems/imo/IMO.system
$ cd /usr/local/lisp/systems
$ ls -l imo
lrwxrwxrwx   1 jesse    users          28
    Nov 17 22:27 imo -> /home/jesse/cvs-work/IMO/imo

The IMO system will set up its logical paths on the assumption that
it's installed in /usr/local/lisp/systems/imo.

If this stuff is all in place, you should be able to evaluate the
following within your lisp shell:

(oos "IMO" :compile)

This will compile and load the IMO system.

To test, evaluate:

(imo:test-install)

and point a browser at http://<your hostname>/test-install

That's it!