This page last changed on Nov 14, 2005.

Quick Overview

  1. Download update
  2. Stop LAMS and make a full backup
  3. Copy over new files and update database

Got the Update?

  • Need the updated lams-package directory, which is distributed in the lams-server-1.0.2-{build_date}.[zip|tar.gz] LAMS Server Package.
  • LAMS 1.0.2 Server Package
+---> \lams-package
  +---> \ant
  +---> \bin
  +---> \conf
  +---> \deploy (3 lams binaries)
  +---> \doc
  +---> \lib (updated libraries)
  +---> \sql (sql script)

Stop the Server

  • by stopping the service
    • Windows: Control Panel->Administrative Tools->Computer Management->Services, then right-click the LAMS service and select Stop.
    • Unix: '/etc/init.d/lams stop'; replace 'lams' with whatever your service name is.
  • alternate way:
    • Windows: $JBOSS_HOME/bin/shutdown.bat
    • Unix: $JBOSS_HOME/bin/shutdown.sh
  • alteralternate way:
    • Unix: 'ps -ef | grep java', 'kill $PID' where $PID is the pid of the LAMS server.
  • remember to inform users of downtime

Backup Existing Data

  • Copy lams-1.0.jar, lams-hibernate.sar and lams.war to a backup location. These files live in $JBOSS_HOME/server/default/deploy.
  • Copy $JBOSS_HOME/server/default/lib to a backup location.
  • Copy $LAMS_HOME/chat, $LAMS_HOME/reports, $LAMS_HOME/simpleassessment to a backup location.
  • Copy $JBOSS_HOME/server/default/deploy/upload.war directory to a backup location.
  • Backup the MySQL database
    • 'mysqldump -c -a --add-drop-table -B $DATABASE_NAME -r /path/to/backups/lams-101-backup.sql -u $MYSQL_USER_NAME -p'
    • You will be prompted for the password of the MySQL user.
    • The database name, user and password will have been specified during the initial installation and configuration of the LAMS server.

Update Files and Database

  • Copy /path/to/lams-package/deploy/lams-1.0.jar, lams-hibernate.sar, and lams.war to $JBOSS_HOME/server/default/deploy.
  • Copy /path/to/lams-package/lib/*.jar to $JBOSS_HOME/server/default/lib
  • Make sure your lib folder contains these files (delete anything else that does not appear here - they are outdated):
    activation.jar                 jbossmq.jar
    ant.jar                        jbossmx.jar
    autonumber-plugin.jar          jbosssx.jar
    axis-ant.jar                   jcert.jar
    axis.jar                       jcommon-1.0.0-rc1.jar
    bcel.jar                       jdom.jar
    bindingservice-plugin.jar      jfreechart-1.0.0-rc1.jar
    bsh-core-1.2b7.jar             jmx-adaptor-plugin.jar
    bsh-deployer.jar               jnet.jar
    c3p0-0.8.4.5.jar               jnpserver.jar
    castor.jar                     jpl-pattern.jar
    cglib-full-2.0.2.jar           jpl-util.jar
    commons-beanutils.jar          jsse.jar
    commons-codec-1.1.jar          jstl.jar
    commons-collections-2.1.1.jar  jts.jar
    commons-discovery-0.2.jar      lams-valve.jar
    commons-fileupload-1.0.jar     log4j.jar
    commons-httpclient-2.0.jar     mail.jar
    commons-lang-2.1.jar           mail-plugin.jar
    commons-logging-1.0.4.jar      mysql-connector-java-3.0.12-production-bin.jar
    commons-modeler.jar            mysql-connector-java-3.1.10-bin.jar
    commons-validator.jar          odmg-3.0.jar
    counter-plugin.jar             poi-2.5.1-final-20040804.jar
    dom4j-1.4.jar                  process-plugin.jar
    ehcache-1.0.jar                properties-plugin.jar
    hibernate2.jar                 saaj.jar
    hsqldb.jar                     scheduler-plugin-example.jar
    hsqldb-plugin.jar              scheduler-plugin.jar
    jaxen-full-1.0.jar             standard.jar
    jaxrpc.jar                     struts-el.jar
    jboss-common-jdbc-wrapper.jar  struts.jar
    jbossha.jar                    tomcat41-service.jar
    jboss-j2ee.jar                 tyrex.jar
    jboss-jaas.jar                 wddx.jar
    jboss.jar                      wsdl4j-1.5.1.jar
    jboss-jsr77.jar                xalan.jar
    jboss-management.jar
  • Update the database:
    • Enter the mysql client 'mysql -u lams -p'
    • Type 'use lams' (change to whatever your LAMS database is called)
    • Type '\. /path/to/lams-package/sql/update_from101_to102.sql;'

Restart the Server

If your update didn't work

  • If your version of LAMS was installed before the release of 1.0.1, LAMS may not start properly.
  • In this case, reinstall LAMS from scratch. Once that is done, replace the fresh database with the old one, and run the update script on it.
Document generated by Confluence on Nov 04, 2005 15:47