Prev   Next

9.2. Upgrading from 6.3.x to 7.0.x

OLAT Configuration mechanism changed for the 7.0 release.

OLAT is configured by the placeholder replacement mechanism from Spring Framework. Spring searches for two files: serviceconfig/olat.properties and classpath: olat.local.properties. The entries in the second file overwrite the default entries in the first file.

To overwrite the defaults create an empty olat.local.propeties file and place it in /yourTomcatDir/lib (part of the classpath) or in the root of your OLAT classpath (e.g. webapp/WEB-INF/classes). See OLAT Administration tab (Setup entry) for your running configuration. When you start OLAT with an empty olat.local.propeties file for development reasons, your userdata will be written to java.io.tmpdir which is platform dependent (e.g. linux: /tmp). You can overwrite this location with a VM parameter -Djava.io.tmpdir=/home/user/data to have userdata in a convenient place.

Example for olat.local.propeties properties for MySQL. 

# DB-properties of your 6.3 installation
db.name=olat_63
db.user=olat_63
db.pass=****

db.vendor=mysql
db.database.dialect=org.hibernate.dialect.MySQL5Dialect
# Important because validation would failed because validation is done before upgrade!
db.hibernate.ddl.auto=none

# Path-properties of your 6.3 installation
userdata.dir=/opt/olatdata
archive.dir=${userdata.dir}/archive
log.dir=${userdata.dir}/logs
upgrade.dir=${userdata.dir}/upgrades
folder.root=${userdata.dir}/bcroot
temp.dir=${userdata.dir}/tmp

Upgrade steps :

  1. Create an olat.local.propeties file for your OLAT configuration.

  2. Define the properties in olat.local.propeties file with value of your existing OLAT configuration. Minimum db- and path-properties.

  3. Copy olat.local.propeties to TOMCAT_HOME/lib directory.

  4. Create an log4j.xml file for your OLAT application. See Log4J XML Configuration

  5. Copy log4j.xml to TOMCAT_HOME/lib directory.

  6. Download 7.0 WAR File from www.olat.org

  7. Deploy WAR File like any standard WAR into your Tomcat installation. E.g. copy WAR file to webapps directory.

  8. Now start tomcat.

  9. Upgrade will be done at first startup.

  10. If you customized your 6.3 OLAT installation, check first olat.properties for available properties. You can overwrite any value in your olat.local.propeties file. For advanced changes look at Chapter 4, The config files. Probably you have to update some _spring/***Context.xml files and rebuild olat.war.

Prev Up Next
 Home