Introduction

The installers will install a standard LAMS setup and will run fine for testing or for a small number of users. If you are setting up a LAMS server for a large number of users you will need to the following information to plan your server. It's a collection of what can be configured and where to configure it, rather than a full guide.

Most of the instructions are written for *nix (Unix/Linux/Macintosh), so if you are running Windows you will need to do what we have described in words, rather than following the exact code given on the page.

Application Server Parameters

Apache and mod_jk

To use Apache w/mod_jk to serve static content, use JkMount and JkUnMount as below. Note this only includes the exploded content under the lams-central.war in the deploy directory, tool content inside each tool's .war will still be served by jboss.

JkMount /lams/* ajp13_worker
JkUnMount /lams/css/* ajp13_worker
JkUnMount /lams/images/* ajp13_worker
JkUnMount /lams/includes/* ajp13_worker
JkUnMount /lams/fckeditor/*.* ajp13_worker
JkUnMount /lams/flashxml/* ajp13_worker
JkUnMount /lams/www/news.html ajp13_worker
JkUnMount /lams/www/images/* ajp13_worker

Note the *.* after 'fckeditor', this is important since there are two LAMS servlets that are mapped under /lams/fckeditor/* and they need to fall outside this JkUnMount directive.

If you are running *nix, you will need to link each of the JkUnmounted directories under your DocumentRoot in Apache. e.g. (assuming your DocumentRoot is /var/www - change the first line if your document root is elsewhere)

cd /var/www
mkdir lams
cd lams
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-central.war/css/ css
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-central.war/images/ images
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-central.war/includes/ includes
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-central.war/fckeditor/ fckeditor
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-central.war/flashxml/ flashxml
mkdir www
cd www
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-www.war/news.html news.html
ln -s /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/lams-www.war/images/ images

If you are running Windows, you cannot link the files. Instead you will need to make two directories "lams" and "www" in your DocumentRoot in Apache. Then copy the following directories (and their contents)

Copy Directory

To

<jboss>/server/default/deploy/lams.ear/lams-central.war/css/

lams/css

<jboss>/server/default/deploy/lams.ear/lams-central.war/images/

lams/images

<jboss>/server/default/deploy/lams.ear/lams-central.war/includes/

lams/includes

<jboss>/server/default/deploy/lams.ear/lams-central.war/fckeditor/

lams/fckeditor

<jboss>/server/default/deploy/lams.ear/lams-central.war/flashxml/

lams/flashxml

<jboss>/server/default/deploy/lams.ear/lams-www.war/news.html

www/news.html

<jboss>/server/default/deploy/lams.ear/lams-www.war/images/

www/images

Files and Logs

Backups

Depending on which operating system you use and how MySQL is configured, you may be able to backup LAMS using the backup utility (see Windows Backup and Restore) otherwise you will need to back it up manually (see Other Backup and Restore).

Moving MySQL To Another Server

If you find your server is heavily loaded and that MySQL is taking a lot of the load, you can try moving the MySQL database to another server. At present this must be done manually as the installers will only install if MySQL is running locally, although the upgraders will support the "split" configuration.