Information

Created in: 2007-06-26 23:45:17

Author: martin

Size: 4700 bytes

Last updated: 2007-06-26 23:45:17

Categories

Help & Support

You may be interested in...

There isn't related documents

jLibrary Migration Guide

This guide will describe the required process to migrate from previous jLibrary verisons to more recent versions.

Updating from jLibrary 1.0.x to jLibrary 1.1

jLibrary will automatically adapt your repositories from 1.0.x versions to 1.1. Basically the only thing you have to do is to export your repositories and import them back in jLibrary 1.1

Updating from jLibrary 1.0 to jLibrary 1.0.1

jLibrary 1.0.1 is a bugfix release and so the process to update from 1.0 to 1.0.1 is very easy as you will see. Obviously, even though the update process does not should give you any problems, you should make an information backup before doing the migration.

Version compatibility

I have bad news here. jLibrary 1.0.1 remote server is not compatible with jLibrary 1.0. This is due to a problem on the web services performance that have been fixed on the 1.0.1 and that forced me to change some of the web services interface. So, you won't be able to connect from a jLibrary 1.0 client to a jLibrary 1.0.1 server and also the opposite. So you must ensure to update the client and the server packages.

Updating the jLibrary server

If you have installed the jLibrary 1.0 standalone server, then you have two different possibilities for upgrading the system:

1. Maintain the old server and upgrade the webapp : You have to go to the webapps directory, remove all the jLibrary related files and directories (that is the jlibrary.war and the jlibrary directory) and finally copy there the jLibrary 1.0.1 WAR file.


2. Use the new jLibrary standalone server bundle : jLibrary 1.0.1 standalone server comes now bundled with the latest tomcat stable distribution, that is the 5.5.17. This new server solves some problems with jLibrary on some linux distributions. If you choose this option, then you have to install this new jLibrary standalone server, and then copy the previous server data directories into the same path on the new server. For example, if your jackrabbit (that's where jLibrary stores the content by default) directory on the 1.0 deployment was under the tomcat bin directory then you only have to copy that jackrabbit folder to a new folder on the 1.0.1 deployment under its bin directory.

On both cases, if you have touched some configuration files on the webapp application you should overwrite the new files with your customized ones, because the 1.0.1 version comes with the default configuration.

Easier but advanced installation

There is another very easy way to update the jLibrary server but it's a little advanced, so I have separated it from the standard update paths. jLibrary 1.0.1 only changes a few .jar files: the jlibrary server jar file, the Apache Derby jar file and the Apache Jackrabbit jar file. So, another easy way to update your application is to copy the changed jar files into your current deployment. There shouldn't be any problem doing this, but remember to make a backup :-)

Updating the jLibrary client

To update the jLibrary client you must first uninstall the previous jLibrary installation, and install the new 1.0.1 jLibrary client. If you have data on your local repository, then remember to use the same local repository data location when running jLibrary 1.0.1 the first time.

Migrating from beta versions to jLibrary 1.0

Currently, jLibrary 1.0 client and server are only compatible between each other. This means that you cannot use a jLibrary 1.0b4 client to access to a jLibrary 1.0 server, or a jLibrary 1.0 client to access to a jLibrary 1.0b4 server.

But, don't worry, jLibrary provides a very easy to use migration system, that would help you to move your old repositories to your new system practically without any effort. You only must follow the following steps:

1. Open your old jLibrary system (client and server), and the repositories that you want to migrate. You can easily export a repository right clicking over it and choosing the "Export repository..." option.
2. Now, proceed to install the new jLibrary server and client as it's described on the installation instructions.
3. Open your new jLibrary 1.0 system and click on the import repository toolbar button.
4. Give a new name to the repository (you can give it the same or a different name), and import it.

And that's all! Very easy, isn't it? Note that on the backgrounds jLibrary is doing extensive process work on the repository data, and also converting old data models to new data models. If you combine this fact with a huge repository you will obtain that maybe you have to wait some minutes to get the data imported.

If you have some problems, leave a message on the forums or mailing lists.