...
| Warning |
|---|
Weave 2.4.16 changes the way user settings are stored which and removes the need to backup and restore the setting 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.
...
Updating to the new Database user storage option
It appears that the method we were using The method used to store bookmarks and redlines wasn't robust in earlier versions was not robust enough under load, so it 's has been replaced by one that stores this information in a database.
If you 're are running version 2.4.16 you 're are already using this update, those on earlier versions . If you are running an earlier version you can follow these instructions to update without having to upgrade to 2.4.16.
...
- 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 promotprompt.
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.
...
| 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.
...