There really aren't that many to worry about. Most of the parameters are configured in build.properties; those are for the scripts to set up LAMS, rather than system or environment variables.
JAVA_HOME
---------
So the most important one is JAVA_HOME, which points LAMS to use that version of java. Note it should point to the root directory of the java installation, e.g. /usr/j2sdk1.4.2.
It's recommended to use the startup script and lams.conf file to manage LAMS startup and shutdown. These are located in the lams-server1.0.2/config/ folder of the server package. In the lams.conf file you can specify JAVA_HOME without having to make it a system-wide variable (useful if you have other Java apps on your machine).
You can also set JAVA_HOME in your current terminal window by doing 'export JAVA_HOME=/usr/path/to/jdk'.
ANT_HOME
--------
The other environment variable is ANT_HOME, which you may or may not need to run 'ant' when installing LAMS. It is non-essential (unless you regularly run ant scripts, in which case you may already have ant installed, and ANT_HOME set). Ant needs to know JAVA_HOME as well, which you can set using 'export JAVA_HOME=/usr/path/to/jdk'.
Other variables are set in build.properties, such as LAMS_JBOSS_HOME and LAMS_HOME. LAMS_JBOSS_HOME is where your jboss folder is, and LAMS_HOME is the folder where LAMS will store some of its records (such as chat logs, reports, etc.) These are described inside the file. They are not system variables, more like parameters for LAMS' installation and startup.
Posted by Jun-Dir Liew
