... h1. Windows Installer Help
|
In this page you'll find all the necessary software you need to *install LAMS using the windows installer*. If you want to build LAMS from source, you can follow the instructions in [Building LAMS|lams:Building LAMS].
|
*For production environments, we recommend you use the [Installing LAMS 2.4 Production in Windows] guide.*
|
{info:title=Upgrading LAMS?}
|
... If you already have a previous version of LAMS installed, see [Windows Upgrading Help] {info} {anchor:getsoftware} h2. LAMS pre-requisites LAMS needs:
|
* A database: MySQL Server * Sun Java JDK
|
* Openfire (formerly called WildFire) Jabber server (not needed for LAMS 2.4.1 and later)
|
Make sure you have installed this software *before* you attempt to install LAMS. See the instructions below:
|
... {anchor:mysql} h3. MySQL Database Server See the [Installing MySQL|Installing MySQL on Windows for LAMS] page. If you are using MySQL as part of an existing XAMPP setup, please read the notes on the [Installing MySQL|Installing MySQL on Windows for LAMS]as you may need to set up a my.ini file before installing LAMS.
|
h3. Java SE Development Kit (JDK)
|
LAMS requires the Sun JDK 5 or 6. See the [Installing Java] page for more details.
|
{warning:title=Java 7} LAMS has not being tested with Java 7. Please user Java JDK 6 instead. {warning}
|
|
LAMS requires the Sun JDK or 6. See the [Installing Java] page for more details.
|
|
|
h3. Openfire (formerly called WildFire) Jabber Server
|
{info:title=Attention LAMS v 2.4.1+ users} You not longer require a Jabber server for LAMS version 2.4.1 and later (see [details here|http://lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/message-view?message_id=1501757]) {info}
|
For our Chat tool, we use the Openfire Jabber Server. See the [Installing Openfire|Installing Wildfire for LAMS] page.
|
h2. Installing LAMS
|
Get the latest installer from the [downloads|lams:Downloads#windows] page.
|
... Here's a three minute animation that shows how installation works (for LAMS 2.3): {html} <center> <object id='stWEpUSkxIR19YRlpcXVpYXlJd' width='425' height='344' type='application/x-shockwave-flash' data='http://www.screentoaster.com/swf/STPlayer.swf' codebase='http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=9,0,115,0'><param name='movie' value='http://www.screentoaster.com/swf/STPlayer.swf'/><param name='allowFullScreen' value='true'/><param name='allowScriptAccess' value='always'/><param name='flashvars' value='video=stWEpUSkxIR19YRlpcXVpYXlJd'/></object> </center> {html} Things you need to know: h2. Setting Up MySQL Database Access (1/4) !step1.JPG|thumbnail! _Click for larger view_ h4. MySQL directory Directory where you installed MySQL. It should be detected automatically. If you installed MySQL without the installer, or via a 3rd party package such as EasyPHP or XAMPP, you will need to specify the MySQL directory here. h4. Root password Your MySQL root password. If your password is blank, leave empty. h4. Database name Name that LAMS will use for its database. Don't change unless you need to. h4. MySQL Username Username that LAMS will use to access its database. Don't change unless you need to. h4. MySQL Password Password that LAMS will use to access its database. You don't need to remember this, as it is used automatically by LAMS. {anchor:lams} h2. Setting Up LAMS (2/4) !step2.JPG|thumbnail! _Click for larger view_ h4. Java JDK directory Directory where you installed the JDK that you wish to use with LAMS. It should be detected automatically. h4. Content repository directory Directory where most of the uploaded files will be installed e.g. the online and offline instruction files, plus any files uploading in the Forum or Submit Files tool. If the disk drive on which LAMS is installed does not have a lot of free space, then change the content repository to another drive. If you do change the location then you will need to make sure you backup both the normal LAMS directory (usually c:\lams) AND the content repository directory. {anchor:lams2} h2. Setting Up LAMS (3/4) !step3.JPG|thumbnail! _Click for larger view_ h4. Domain name The domain name of your LAMS server. For use on your own PC _only_ you can leave the default value of "localhost". For production/server use, please change to the domain name of your server. If your server has multiple names, use the one by which users will access LAMS. {note:title=Important} You must access LAMS using [http://servername:portnumber/lams/]. So if you do not get the servername right now, you will need to change it in the database directly later. Once you have LAMS up and running, you can change the servername if you change the name of the server - but you have to be able to log in with the old name to change it to the new name. {note} h4. Port Port that LAMS will run on. Don't change unless you need to. {note:title=Important} Note that you need to make sure that there's no other application using the port you entered\! {note} For instance if you have another webserver or application that is currently using that port, then LAMS won't be able to start. If you use Skype note that it might be binding port 80\! So shutdown skype before you start LAMS. h4. Default locale Choose the default language for your LAMS server. {anchor:wildfire}
|
h2. Setting Up Wildfire Chat Server (4/4)
|
{info:title=Attention LAMS v 2.4.1+ users} You not longer require a Jabber server for LAMS version 2.4.1 and later (see [details here|http://lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/message-view?message_id=1501757]) {info} *Starting with LAMS 2.4.1 Wildfire is no longer needed. For previous LAMS versions please follow instructions below.*
|
!step4.JPG|thumbnail! _Click for larger view_
|
... {info:title=A note on configuring Wildfire...} If you don't intend to [install Wildfire|Installing Wildfire for LAMS], you don't need to worry about this screen. {info} h4. Domain name Domain name of your Wildfire server. Should be the same as the one used when Wildfire was configured. If unsure, leave the default. h4. Admin username Username of the Wildfire administrator - 'admin' by default. Don't change unless you need to. h4. Admin password Password of the Wildfire administrator. Should be the same as the one used when Wildfire was configured. You don't need to remember this, as it is used automatically by LAMS. h3. Still having problems? {info} \\ Read the [Troubleshooting Windows Installer Problems] page and then post your issues/problems in [this forum|http://lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/forum-view?forum%5fid=4929] in the LAMS Community \\ If you have just run the LAMS 2.0.x updater to upgrade from LAMS 2.0, and you want to go back to a previous version of LAMS, then these [manual instruction|Revert To Windows Backup] will tell you how to go back to the backup created by the installer. {info}
|