Intrallect Intralibrary Upgrade Guide: Version 3.1 to 3.3

Intralibrary Upgrade Guide: Version 3.1 to 3.3


Revision: 7

Created: 4th August 2005

Last Revised: 8th June 2010

Contact: support@intrallect.com

Company: Intrallect Ltd

Product: intraLibrary, Digital Repository

Copyright: Intrallect Ltd 2003-2010. All rights reserved.

This document is made available to support Intrallect's customers and users of Intrallect's software. The text of these documents and the design of the intraLibrary software are both the intellectual property of Intrallect Ltd. Intrallect does not provide this document for any other purpose, and offer no warranty nor accept any liability for its use in any other context.


Table of Contents
1. Shutdown intraLibrary
2. Update Dependencies
3. Replace Web Application
4. Remove Indexes
5. Start intraLibrary
6. Common upgrading problems

1. Shutdown intraLibrary
table of contents

Shutdown the current instance of intraLibrary. If you are using Tomcat and are unsure about stopping and starting, see here for more help.


2. Update Dependencies
table of contents

You need to copy dependencies from the install package authenticationLib directory. Instructions can be found in section 2.6 of the installation guide.


3. Replace Web Application
table of contents

The basis of the intraLibrary web application is the intralibrary.war file file. You can put this archive anywhere on the server, but we'd recommended it to be on the same physical volume as the application server (Tomcat).

To avoid confusion between the new and old versions of the web application, rename the previous war file to intralibrary_old.war. Once you are satisfied that the new version of intraLibrary runs correctly the old war file can be removed completely.


4. Remove Indexes
table of contents

While not essential, we strongly advise that you remove the index folder from within your intraLibrary config dir. There have been instances whereby the index has become out of sync with the contents of the intralibrary database. Removing this directory will prevent any inconsistencies.


5. Start intraLibrary
table of contents

It's now time to start the application. The first time that intraLibrary is started, any database changes will be applied on the server to ensure compatibility with the new version. The database changes are fairly minor so the amount of time taken to upgrade should be small.

If you wish to monitor the upgrade process, you can monitor the upgradeReport.log file which can be found in the directory specified as 'configDir' in your properties file. This file will tell you when the process is finished by outputting the line 'finished upgrading'.

If you check the output of the server startup, you should see some text resembling the text below.

****************************************

populating learning object cache with 0 objects...
finished populating learning object cache

****************************************
application version: n.n (nnnnn)
database server version:5.0.27-community-nt
database url:jdbc:mysql://localhost:3306/intralibrary?autoReconnect=true&jdbcCompliantTruncation=false
database driver:MySQL-AB JDBC Driver
max database connections(0=unlimited):0
max upload file size:49Mb
servlet container:Apache Tomcat/5.5.20
java version:1.5.0_10
----------------------------------------
configDir location:/Volumes/projects/intralibrary/config
http proxy:no proxy used
mail host:mail.company.com
admin email:admin@company.com
error email:errors@company.com
return email:intralibrary1@company.com
id prefix:com.comapany.intralibrary1
repository name:intralibrary1
object cache size:250
entry page:browse
debug:false
reindexOnStartup:true
----------------------------------------
total memory assigned:26Mb
maximum memory assigned:112Mb
----------------------------------------
licence assigned to:company
max contributors:10
current contributors:1
expires:
----------------------------------------
IntraLibrary started dd-MMM-yyyy hh:nn:ss
****************************************

Assuming that you have no errors in this output then congratulations, you have successfully upgraded your installation of intraLibrary.


6. Common upgrading problems
table of contents

If you decided to rename the database you use for your installation, make sure you recreate the SQL views for the new database using the script "dbscripts/views/intralibrary-view.sql".