Friday, December 24, 2010

Upgrading from LAMS 2.3.2 to 2.3.4

Upgrading from LAMS 2.3.2 to 2.3.4

This is a two step process as it is first necessary to upgrade from 2.3.2 to 2.3.3 and then subsequently from 2.3.3 to 2.3.4

Upgrading from 2.3.2 to 2.3.3

The process I followed is explained below:

As the root user download lams-unix-patch-2.3.3.tar.gz into /root:

lynx http://wiki.lamsfoundation.org/display/lams/Downloads#Downloads-unix

Stop LAMS:

service lams2 stop

Unpack the patch and copy the files over:

tar -xzvf lams-unix-patch-2.3.3.tar.gz
cd lams-unix-patch-2.3.3
"cp" -r lams.ear/* /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/

To avoid problems with server cacheing delete the following directories:

rm -rf /usr/local/jboss-4.0.2/server/default/work/
rm -rf /usr/local/jboss-4.0.2/server/default/tmp/

Start LAMS and restart Apache and your upgrade is complete:

service lams2 start
service httpd restart

Note that there is about a one minute wait between restarting LAMS and it becoming available from the browser.

Upgrading from 2.3.3 to 2.3.4

The process I followed is explained below:

As the root user download lams-unix-patch-2.3.4.tar.gz into /root:

lynx http://wiki.lamsfoundation.org/display/lams/Downloads#Downloads-unix

Stop LAMS:

service lams2 stop

Unpack the patch and copy the files over:

tar -xzvf lams-unix-patch-2.3.4.tar.gz
cd lams-unix-patch-2.3.4
"cp" -r lams.ear/* /usr/local/jboss-4.0.2/server/default/deploy/lams.ear/
cp index.jsp /usr/local/jboss-4.0.2/server/default/deploy/jbossweb-tomcat55.sar/ROOT.war

To avoid problems with server cacheing delete the following directories:

rm -rf /usr/local/jboss-4.0.2/server/default/work/
rm -rf /usr/local/jboss-4.0.2/server/default/tmp/

Start LAMS and restart Apache and your upgrade is complete:

service lams2 start
service httpd restart

Note that there is about a one minute wait between restarting LAMS and it becoming available from the browser.