Backing up client settings
| Info |
|---|
There is currently an update being tested that stores this information in a database, generally negating the need to perform this operation, but this update is not yet generally available. |
...
| Warning |
|---|
Weave 2.4.16 changes the way user settings are stored and removes the need to backup and restore the user settings when performing an upgrade. |
Backing up user settings
Anything the user can save (bookmarks, redlines, etc) will be stored under the Weave installation directory, so they should be exported before the current Weave instance is decommissioned or upgraded.
...
| Info |
|---|
Note that you need to be using version 1.1.0 of the |
| Infowarning |
|---|
To execute these commands the server needs to either be started using |
Upgrading from 2.3 to 2.4
Upgrading Weave from 2.3 to 2.4 currently requires a fresh installation of the new version and migration of an existing configuration.
Installation Sources
There are generally two installation sources for Weave, a CD image .iso file (that can either be burnt to a physical CD or mounted directly with the appropriate software) and a .jar file which is the actual Weave installer.
Starting the software installation is slightly different if you're installing from a CD than if you're installing from the .jar file, but the actual installation process is the same.
The reason for the two different installation media is related to the size of the download, with the installer .jar file being significantly smaller than the CD image, but the .jar file requires a Java runtime to already be installed on the server, whereas the CD image contains the installer .jar file along with a (number of) Java runtime(s) to start it.
Both installation sources end up running the same Weave installer (the afore mentioned installer .jar file) and once the installer is started, the installation process is the same for both.
If you're going to be installing to a server that already has Java installed (any Java version 1.4 or above is sufficient) then using the installer .jar file directly will save you using unnecessary bandwidth. It may be even quicker to download the installer .jar file and a Java runtime (and install it directly) than it would be to download the .iso image, since the .iso image contains four Java runtimes (32 bit and 64 bit for both Windows and Linux). If you are installing to multiple servers or do not want to install unnecessary software (since the .iso installation method doesn't require the installation of the Java runtime just to run the installer) then the .iso image may be a better option.
| Info |
|---|
Another advantage that the CD .iso image has over the installer .jar file and a reason for its larger size, is the fact that the CD image contains both a 32 and a 64 bit Java runtime for running the installer. |
Installing from a CD image .iso file
Launching the Weave installer from the CD image can be done by running the install.cmd or install64.cmd batch files on Windows or install.sh or install64.sh scripts on Linux. These scripts are in the root directory of the CD image.
These scripts are used to launch the Weave installer .jar file using one of the Java runtimes available on the CD, with the install versions installing a 32 bit version of Weave, and the install64 version installing a 64 bit version of Weave.
Installing from an installer .jar file
To install Weave directly from the installer .jar file requires starting the .jar file using the Java runtime already installed on the server.
If you already have an older version of Weave installed on the server then you can use the JDK that was installed with that exisitng version.
Depending upon the file association configured for your server, you may be able to start the Weave installer .jar file directly (by double clicking on it in Windows Explorer for example) but if this does not work then you should open a command prompt and and run the installer directly using the following command.
| No Format |
|---|
java -jar weave-installer.jar
|
| Info |
|---|
In this text when directly referring to the Weave installer .jar file it will be presented as |
You may need to fully qualify the java command if it isn't already in your PATH, for example if you're using an existing Weave installation it may be
...
Updating to the new Database user storage option
The method used to store bookmarks and redlines in earlier versions was not robust enough under load, so it has been replaced by one that stores this information in a database.
If you are running version 2.4.16 you are already using this update. If you are running an earlier version you can follow these instructions to update without having to upgrade to 2.4.16.
The updated bundle is available at:
com.cohga.server.user.storage.db_1.4.2.jar
To use this you must:
- export the existing settings using ustorage save at the osgi prompt
- stop the server
- remove the older com.cohga.server.user.storage.osgi bundle from platform\plugins
- install the newer com.cohga.server.user.storage.db bundle to platform\plugins
- replace com.cohga.server.user.storage.osgi with com.cohga.server.user.storage.db in platform\configuration\config.ini
- clean out the platform\configuration directory (except config.ini)
- start the server
- import the existing settings using ustorage load at the osgi prompt.
Upgrading from 2.3 to 2.4
Upgrading Weave from 2.3 to 2.4 currently requires a fresh installation of the new version and the migration of an existing configuration.
Installation Sources
There are generally two installation sources for Weave, a CD image .iso file (that can either be burnt to a physical CD or mounted directly with the appropriate software) and a .jar file which is the actual Weave installer.
Starting the software installation is slightly different if you're installing from a CD than if you're installing from the .jar file, but the actual installation process is the same.
The reason for the two different installation media is related to the size of the download, with the installer .jar file being significantly smaller than the CD image, but the .jar file requires a Java runtime to already be installed on the server, whereas the CD image contains the installer .jar file along with a (number of) Java runtime(s) to start it.
Both installation sources end up running the same Weave installer (the afore mentioned installer .jar file) and once the installer is started, the installation process is the same for both.
If you're going to be installing to a server that already has Java installed (any Java version 1.4 or above is sufficient) then using the installer .jar file directly will save you using unnecessary bandwidth. It may be even quicker to download the installer .jar file and a Java runtime (and install it directly) than it would be to download the .iso image, since the .iso image contains four Java runtimes (32 bit and 64 bit for both Windows and Linux). If you are installing to multiple servers or do not want to install unnecessary software (since the .iso installation method doesn't require the installation of the Java runtime just to run the installer) then the .iso image may be a better option.
| Info |
|---|
Another advantage that the CD .iso image has over the installer .jar file and a reason for its larger size, is the fact that the CD image contains both a 32 and a 64 bit Java runtime for running the installer. |
Installing from a CD image .iso file
Launching the Weave installer from the CD image can be done by running the install.cmd or install64.cmd batch files on Windows or install.sh or install64.sh scripts on Linux. These scripts are in the root directory of the CD image.
These scripts are used to launch the Weave installer .jar file using one of the Java runtimes available on the CD, with the install versions installing a 32 bit version of Weave, and the install64 version installing a 64 bit version of Weave.
Installing from an installer .jar file
To install Weave directly from the installer .jar file requires starting the .jar file using the Java runtime already installed on the server.
If you already have an older version of Weave installed on the server then you can use the JDK that was installed with that exisitng version.
Depending upon the file association configured for your server, you may be able to start the Weave installer .jar file directly (by double clicking on it in Windows Explorer for example) but if this does not work then you should open a command prompt and and run the installer directly using the following command.
| No Format |
|---|
java -jar weave-installer.jar
|
or for Linux
| No Format |
|---|
| Info |
In this text when directly referring to the Weave installer .jar file it will be presented as |
The installation process
...
, but the file name may be different, for example it may actually be |
You may need to fully qualify the java command if it isn't already in your PATH, for example if you're using an existing Weave installation it may be
| No Format |
|---|
c:\weave\jdk\bin\java -jar weave-installer.jar
|
or for Linux
| No Format |
|---|
/opt/weave/jdk/bin/java -jar weave-installer.jar
|
The installation process
Once started, the installer takes you through a number of steps:
...
| Info |
|---|
As an alternative to installing to a new directory you can rename an existing Weave installation, to get it out of the way, and install to the same location, just make sure you remove any existing Windows service (using the |
Warning: Once you have settled on an installation directory, choose which packages to install. Do not just install all of the packages, especially the Additional Components. It may be tempting to just click all of the check boxes but this is almost certainly not what you want. This will install components that you will never need and don't use. It will add additional memory and performance overheads that you do not want and it will install multiple versions of bundles where there should only be one of that type.
...
Once you have finished the installation you need to migrate your existing Weave configuration to the new instance, and copy over any custom plugins, before you start the new Weave instance.
This process involves renaming the new workspace directory and copying over the one from your existing instance. You could just delete the new workspace directory, but by renaming it you have the option of comparing the old and new version of some of the supplementary files that are included there.
The next migration step is to use the ustorage (and storage) commands to import the user settings from the previous instance.
The next migration step is to use the ustorage (and storage) commands to import the user settings from the previous instance.
| Warning |
|---|
If you're replacing a newly installed workspace with an old production one you may need to copy the org.hsqldb.hsqldb_2.2.5.jar file from the old workspace jdbc directory to the new one. |
Testing
Once the previous workspace is copied to the new instance it should be ready to test and no changes to any configuration files should be required.
It is advisable to do this initial test by starting Weave from the command line, via startup.cmd or debug.sh, so that you can see log messages immediately, but aware that if Weave is then installed as a service and run as a different user, then permission problems may occur. This is generally an issue when the instance is first started as a service and then later started via the command line. It has been mentioned in case you would prefer to install it as a service immediately and do the testing with Weave running as a service.
...