Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note
titleWhy Upgrade

Customers still on 2.5 will not have access to new features or updates to features that are in the 2.6 releases. Weave 2.5 will no longer be receiving any new functionality.

The functionality provided by Weave is supported by the underlying technology Weave is built upon, and provided as part of the base install of Weave. But as with all technology, these things sometimes need to be updated and as part of the release cycle of Weave it is now time for another one of these technology updates.

At the moment the core Weave functionality provided by Weave 2.5 and Weave 2.6 are exactly the same, that is they both contain the same "Weave" functionality, even though the underlying technology is being updated, and both versions are in fact made up of exactly the same set of bundles/plugins. However, from now on, all new development will be based on the updated 2.6 platform. As time goes by, the functionality provided by the new platform will be used more and more and will not be available for Weave 2.5, it is for this reason that upgrading from 2.5 to 2.6 should be done at the earliest opportunity, while the two releases of Weave are still closely aligned.


Warning

In-Place Upgrade

New functionality added to Weave requires updates to underlying technologies that Weave is built upon. These updates are generally made as part of a point release, e.g. 2.4 to 2.5, 2.5 to 2.6, etc., and as such it is not possible to directly update a Weave 2.5 instance to Weave 2.6.

You must install Weave 2.6 to a new location, but you can copy your existing 2.5 configuration configurations over to the new installation and you do not need to uninstall your previous Weave 2.5 instance.

Note: If you're using encrypted passwords in your existing Weave configuration, you will either need to re-encrypt them in the new installation or copy the private.key file from the existing workspace to the new one. See this page for more information.

...

Warning

Base Directory Change

The base directory (the directory that is taken to be the "current working directory" when Weave is running) has changed from being in the jetty sub-directory to being the root of the Weave installation.

On a clean installation this will not cause any problems because the installer is aware of this change, but if you copy configuration files from a previous instance of Weave, for example logging.properties or wrapper.conf, and they contain relative paths, then these will now point to the wrong location.

You should check any configuration files that are being copied from an older Weave instance and ensure relative paths are changed to reflect the new startup directory. For example in logging.properties, the log4j.appender.file.File setting would change from ../logs/weave.log to ./logs/weave.log (note the two full stops have been replaced with one).

If in doubt, compare the new file installed as part of the clean Weave 2.6 installation with the old one you wish to replace it with before overwriting the newer file.

Additionally, support dumps will now be placed in the root directory rather than under the jetty sub-directory.

...

Info

As part of the update of Jetty and the Java Service Wrapper a number of system properties that were previously set in jetty.ini and jetty.xmlstartup.cmd/startup.sh or wrapper.conf are now set as part of Jetty at jetty_base\start.d\.

Note that if you're using a Web Application server other that than the Jetty installed as part of Weave then you will also need to duplicate some of the settings within the other Web Application Server.

HTTP Settings

The settings related to the HTTP server, which ports to listen on, etc., were previously set in jetty.ini or jetty.xml. These values are now stored in jetty_base\start.d\http.ini.

Proxy Settings

The settings required for the Weave server to know which HTTP proxy to use to access the internet, if required, were previously set in startup.cmd/startup.sh and service\conf\wrapper.conf but are now stored at jetty_base\start.d\proxy.ini.

Weave Settings

There are a number of customisable settings available for Weave, which were previously set in startup.cmd/startup.sh and service/conf/wrapper.conf but are now stored at jetty_base\start.d\weave.ini.
If you have your own settings that you have added to startup.cmd/startup.sh and service/conf/wrapper.conf you could either copy them to jetty_base\start.d\weave.ini or, better yet, create your own .ini file at that location containing your settings.

Telnet Settings

The setting related to enabling telnet access to the Weave server OSGi console was previously set in startup.cmd/startup.sh and service/conf/wrapper.conf but is now stored at jetty_base\start.d\telnet.ini. There appears to be an isse issue with starting the Telnet service when this setting is moved so it had been moved back until the issue is resolved.


Warning: The ini files referenced above must use ISO-8859-1 encoding, not UTF-8. Ensure that the text editor you're using to edit the files is using the correct encoding when saving the files or the file contents may not get processed.


Installation

Starting the installer

...

To use the .jar file you will need to open a command prompt (sometimes double-clicking on the .jar file may start the installer, depending upon how the server is setup) and start the installer manually.

The Weave installer .jar file requires an existing version of Java to be available on the server. If the server already contains a Weave instance then you already have Java available, and you just need to specify that Java be is used when starting the installer.

...

The installation process

Step 1

Installing Weave 2.6.0 is similar to the process required for a standard Weave upgrade, which starts with a Welcome screen.



Step 2

This is followed by the Licence screen, where you must accept the licence agreement before you can proceed.

Step 3

Next you need to choose the location (Target Path) where you want to install the new instance of Weave. If you specified an install location on the command line when starting the installer, then the Target Path should already be showing on the Target Path menu.

Step 4

At this step you are presented with the available installation options.

...

The first group of options are the main components. Since we are upgrading an existing Weave instance, select the same set of extensions that you had installed in the previous instance of Weave that you are upgrading.

Step 5

The next step is to choose the port numbers that Weave will be listening on. If you choose the same as those used for your existing Weave instance you can only run one instance of Weave on that server at the one time.

...