Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Unix Installation Help

In this page you'll find all the necessary software you need to install LAMS 2.0 using the unix installer.

If you want to build LAMS from source, you can follow the instructions in Building LAMS.

Before You Run the Installer...

Make sure you have the software LAMS needs! If you are unsure of what software is needed to run LAMS, go to the Development Environmentpage.

MySQL Database Server

See the Installing MySQL page.

Java SE Development Kit (JDK)

Sun JAVA JDK is available from the Sun Java site. 5.0 or 6.0 will work, you can get the one that says:

JDK 5.0 Update 9

The Java SE Development Kit (JDK) includes:

  • the Java Runtime Environment (JRE)
  • command-line development tools, such as compilers and debuggers, that are necessary or useful for developing applets and applications

This is about 50 MB. See the installation instructions.

Note: Java 1.4.x won't work.

Wildfire Jabber Server

For our Chat tool, we use the Wildfire Jabber Server. See the Installing Wildfire page.

 Check  that you have the latest LAMS 2 Unix installer

See the downloads page.

Running the installer

Once you have your installer, extract it into any desired location eg: /usr/local. 

Editing the File

The file outlines where and how you will install LAMS 2.0, It  also configures some of the settings you want for the install. Most of the defualt configurations can be left, but you wiil need to change some to suit the setup of your personal machine. The file comes with directions on what you need to alter and what needs to be left unchanged. Pay particular attention to "Essential Settings" section because LAMS 2.0 will not install or run properly if these are incorrect. Below is the skeleton for the file.

Setting up the Language Locale

You will see about a quarter of the way through the file there is a line that says: 


In LAMS 2.0 you can set the defualt language of your server to be one of many languages, and more to come, see the internationalization page. Look out for unix language packs to add to your list of language locales.

For the 2.0 installer, the following default languages are available. The locale options for LAMS-2.0 available are listed below, simply put in your file (under Installation Options):

LOCALE - (locale)
LOCALE_DIRECTION - (locale direction)

Language               Locale    Locale-Direction
English(Australia)    en_AU    LTR
Español                  es_ES     LTR
Deutsch                 de_DE     LTR
????                  zn_CN    LTR
Français                 fr_FR      LTR
Italiano                  it_IT       LTR
Norsk                    no_NO     LTR
???                    ko_KR     LTR
Polski                    pl_PL       LTR
Português (Brasil)  pr_BR      LTR
????????               el_GR      LTR
????(Arabic)            ar_JO      RTL
Ti?ng Vi?t              vi_VN      LTR
Chinese (Taiwan)    zh_TW    LTR

Running the Ant script 

Once you have updated the file (located in the root directory of the extracted package), then installation is easy. Run the installation ant script by typing:
>$ sudo ant/bin/ant install

Please use the included Ant by typing ">$ sudo ant/bin/ant install" instead of using your own version of ant to ensure the SQL scripts run correctly

Running Lams

If you chose to install LAMS 2.0 without the wrapper, you should be able to run LAMS 2.0 by simply going into the <jboss-4.0.2 dir>/bin and typing:

>$ ./ &

 It will take a few minutes for jboss to start, then you can access LAMS using the server url you put into you file.

Using the Java Wrapper

If you chose to install the java wrapper, then you should have a few extra files in your <jboss-4.0.2 dir>/bin, namely "" and "wrapper". Make these executable by typing:

>$ chmod a+x *

If you wish to make LAMS a service that starts every time your machine starts up, you need to copy the init.d script ( into the /etc/init.d folder. For more inforamtion about setting up a service, see  the web tutorial

  • No labels